A Solution Is More Than an Answer
Suppose a problem asks for the area of a right triangle and gives the lengths of the two legs:
\[ a=9,\qquad b=12. \]We could immediately compute:
\[ A=\frac12ab=\frac12(9)(12)=54. \]The numerical answer is correct, but Malone Math asks for a little more:
- Did we identify what the problem actually asked?
- Did we choose a useful representation?
- Did we select an appropriate method?
- Did we preserve units?
- Did we check whether the result makes sense?
- Could we explain why the method worked?
A strong solution leaves a trail another person can follow.
\[ \boxed{\text{problem solving}=\text{understanding}+\text{strategy}+\text{execution}+\text{verification}} \]The Seven-Step Framework
1. Understand
Identify the question, conditions, and constraints.
2. Organize
Separate known quantities, unknowns, units, and relationships.
3. Represent
Choose symbols, diagrams, tables, equations, graphs, or another useful form.
4. Strategize
Select a method that connects the known information to the unknown.
5. Execute
Carry out the mathematics carefully and visibly.
6. Verify
Check the result using logic, units, substitution, estimation, or another method.
7. Reflect
Ask what the solution reveals and what can be reused elsewhere.
1. Understand the Problem
Before calculating, determine what the problem is asking.
Ask:
- What is the unknown?
- What information is given?
- What conditions or constraints matter?
- Are any words being used in a technical mathematical sense?
- What would count as a complete answer?
For a word problem, restating the question in your own words can expose hidden assumptions before arithmetic begins.
If the question asks for a rate, a length alone is not enough. If it asks for area, the final unit should be squared. Understanding the requested object comes first.
2. Organize What Is Known
Separate the information into useful categories.
| Category | Example |
|---|---|
| Known quantity | \(r=5\text{ cm}\) |
| Unknown | \(A=?\) |
| Relationship | \(A=\pi r^2\) |
| Constraint | \(r>0\) |
| Units | centimeters and square centimeters |
Organization reduces cognitive load. Instead of holding an entire paragraph in memory, we turn it into mathematical objects we can work with.
3. Choose a Useful Representation
The same problem can often be represented in several ways:
- equation,
- diagram,
- table,
- number line,
- graph,
- matrix,
- verbal rule,
- algorithm or pseudocode.
The best representation is the one that makes the important relationship visible.
Example
“Three more than twice a number is eleven” becomes
\[ 2x+3=11. \]The symbolic representation makes inverse operations immediately useful.
4. Select a Strategy
A strategy is the overall method used to connect known information with the unknown.
Strategies include:
- use a direct formula,
- work backward,
- draw a diagram,
- set up an equation,
- make a table,
- search for a pattern,
- break the problem into smaller cases,
- use proportional reasoning,
- apply an algorithm,
- approximate and refine.
Do not choose a method merely because it was used in the previous exercise. Choose it because the structure of the current problem supports it.
5. Execute Carefully
Once the plan is clear, carry out the mathematics in visible steps.
- preserve equality correctly,
- keep track of units,
- respect signs and grouping,
- avoid unnecessary rounding,
- record substitutions clearly,
- show enough work to reconstruct the reasoning.
A clean solution is easier to verify because each transformation can be checked independently.
6. Verify Independently
Verification is not decoration after the “real” work. It is part of the solution.
- Can I substitute the answer back into the original equation?
- Do the units match the requested quantity?
- Is the magnitude reasonable?
- Does the sign make sense?
- Does the answer satisfy the stated constraints?
- Can I solve or estimate the problem a second way?
Example
If
\[ 2x+3=11 \]gives
\[ x=4, \]then substitute:
\[ 2(4)+3=11. \]The original condition is satisfied.
7. Reflect and Generalize
After the result is secure, ask what can be learned from the method.
- Was there a faster representation?
- Did the problem use a reusable pattern?
- Could the method solve a broader family of problems?
- What assumption mattered most?
- Where was error most likely?
- What would change if one condition changed?
Reflection turns one solved problem into a reusable mathematical tool.
\[ \boxed{\text{experience}\to\text{pattern}\to\text{future strategy}} \]The Framework Is Not Always Linear
Real problem solving often requires revision.
You may discover during execution that the representation is awkward, an assumption was wrong, the strategy creates unnecessary complexity, or verification exposes a contradiction.
Then return to an earlier step. This is normal mathematical work. The framework is structured, but it is not rigid.
Build from the Mathematical Toolbox
Malone Math treats mathematical objects as tools that become more useful as they are reused.
Depending on the problem, useful tools may include number lines, sets, functions, proportions, graphs, vectors, matrices, logical conditions, algorithms, estimation, and approximation.
An advanced-looking object can be the simplest tool if it represents the problem well.
The goal is not to use the most elementary method. It is to use the clearest method that the learner understands well enough to justify.
Kinds of Verification
Substitution
Put the result back into the original condition.
Estimation
Compare with an approximate mental or numerical expectation.
Dimensional Check
Confirm that units and dimensions are compatible.
Independent Method
Solve or compute the quantity a different way.
Constraint Check
Confirm that the result lies in the permitted domain.
Structural Check
Verify known identities, invariants, symmetry, or other relationships.
The strongest check is often independent of the original computation. Repeating the same mistaken method usually repeats the same mistake.
Communicating the Solution
A finished solution should make the reasoning recoverable.
- state what is known and what is sought,
- show the selected relationship or method,
- perform the transformations,
- state the result with appropriate units,
- show at least one meaningful verification.
Not every problem needs a page of explanation. The amount of work shown should be enough to communicate the logic without burying the main idea.
Worked Example: A Rectangle Problem
A rectangle has perimeter \(34\text{ m}\) and length \(10\text{ m}\). Find its width.
1. Understand
We need the width \(w\).
2. Organize
\[ P=34\text{ m},\qquad \ell=10\text{ m},\qquad w=? \]3. Represent
\[ P=2\ell+2w. \]4. Select a Strategy
Substitute the known values and solve the resulting linear equation.
5. Execute
\[ 34=2(10)+2w, \] \[ 34=20+2w, \] \[ 14=2w, \] \[ \boxed{w=7\text{ m}}. \]6. Verify
\[ 2(10)+2(7)=20+14=34. \]The perimeter matches the given value.
7. Reflect
This is a “known formula + missing variable” problem. The same framework works for area, distance, rate, finance, geometry, and many other formulas.
Worked Example: A Percentage Problem
A jacket costs \$80 and is discounted by \(25\%\). What is the sale price?
Understand
We need the price after the discount, not merely the amount of the discount.
Organize
\[ P=80,\qquad r=0.25. \]Represent
\[ D=rP,\qquad S=P-D. \]Execute
\[ D=0.25(80)=20, \] \[ S=80-20=\boxed{\$60}. \]Verify
A \(25\%\) discount leaves \(75\%\) of the original price:
\[ 0.75(80)=60. \]The independent method agrees.
What to Do When You Are Stuck
When no strategy is obvious, do not immediately search for a formula. Try changing the problem's form.
- draw a picture,
- make a smaller example,
- list known and unknown quantities,
- write a table,
- try an extreme or simple case,
- work backward from the desired result,
- look for an invariant or repeated pattern,
- translate words into symbols,
- translate symbols back into words.
Often the obstacle is not the mathematics itself. It is the current representation.
Common Problem-Solving Errors
1. Calculating before Understanding the Question
A correct computation can answer the wrong question.
2. Choosing a Method by Habit
Use the structure of the current problem, not the topic label of the previous exercise.
3. Carrying Too Much Information Mentally
Organize the givens, unknowns, and constraints visibly.
4. Rounding Too Early
Preserve exact forms until approximation is actually useful.
5. Ignoring Units
Units help both calculation and verification.
6. Treating the Calculator Output as Verification
A calculator can execute a wrongly entered expression perfectly.
7. Stopping at the First Numerical Answer
Check whether the value satisfies the original problem.
8. Failing to Learn from the Solution
Reflection is what turns a single exercise into future problem-solving skill.
Practice
Framework Order
Which should usually happen first: selecting a strategy or understanding what the problem asks?
Check Answer
\[\boxed{\text{understand the problem first}}\]Representation
A problem describes how two quantities change together over time. Name one representation that may help reveal the relationship.
Check Answer
A table or graph would often be useful. An equation or function may also be appropriate once the relationship is recognized.
Verification
You solve \(3x-2=10\) and obtain \(x=4\). Verify by substitution.
Check Answer
\[3(4)-2=12-2=10.\]So \(\boxed{x=4}\) satisfies the original equation.
Units
A rectangle has side lengths measured in centimeters. What unit should its area use?
Check Answer
\[\boxed{\text{cm}^2}\]Reflection
Why is reflection part of problem solving rather than merely an optional comment at the end?
Check Answer
Reflection identifies reusable patterns, better representations, assumptions, and strategies that improve future problem solving.
The Deeper Idea
Problem solving is the process of building a bridge between what is known and what is sought.
\[ \boxed{\text{known information}\longrightarrow\text{representation}\longrightarrow\text{strategy}\longrightarrow\text{verified result}} \]The framework unifies many ideas already introduced in Malone Math:
- mathematical language clarifies the problem,
- representations expose structure,
- algorithms organize procedure,
- measurement supplies units and tolerances,
- logic checks conditions,
- verification tests whether the result belongs to the original problem.
This is why Malone Math treats problem solving as a reusable structure rather than a separate chapter of tricks.
Every new mathematical object expands the toolbox, but the framework for using those tools remains recognizable.
Summary
- The Malone Math problem-solving framework has seven recurring stages: understand, organize, represent, strategize, execute, verify, and reflect.
- Understanding identifies what is asked and what constraints matter.
- Organization separates known quantities, unknowns, relationships, and units.
- Representation turns the problem into a form that exposes useful structure.
- Strategy connects the known information to the unknown.
- Execution carries out the mathematics carefully and visibly.
- Verification checks the result against the original problem using substitution, estimation, units, constraints, or an independent method.
- Reflection extracts reusable ideas from the completed solution.
- The framework is iterative rather than rigid; later discoveries may require returning to an earlier step.
- Problem solving improves as the mathematical toolbox expands.
- A finished solution should be understandable enough that another reader can reconstruct and check the reasoning.
The purpose of the framework is not to slow down easy mathematics. It is to make difficult mathematics more manageable and successful mathematics more reliable. With practice, the steps become habits: understand before acting, represent before forcing a method, verify before trusting an answer, and reflect before moving on.
Problem Solving and Verification
- Previous: Communicating Algorithms Clearly
- Problem Solving and Verification — return to the lesson directory.