Reflecting on Problem Solving Strategies

Solving a math problem is only half the task. The other half is stepping back afterward to ask how you solved it, whether a different strategy would have worked better, and what that comparison tells you about your own reasoning. This lesson focuses on reflecting specifically on problem solving strategies in math: talking through your steps, weighing one method against another, and deciding which approach deserves to become your default next time.

Two students can arrive at the same correct answer through very different paths, one efficient and one clumsy. If you only check whether the final number is right, you learn nothing about the quality of the reasoning that got you there. Reflecting on the strategy itself means asking questions such as: Did I choose this method because it was familiar, or because it actually fit the problem? Did I waste steps? Could I have caught my mistake sooner?

This kind of evaluation is what separates a student who slowly repeats the same errors from one who improves. Building this habit connects to analyzing your own mathematical reasoning, where you examine the logic behind each step rather than the outcome alone.

Talking through a problem out loud, or writing your reasoning in full sentences as you go, forces vague thinking into precise language. For example, instead of silently trying numbers to solve \( 2x + 3 = 11 \), you might say: "I'll subtract 3 from both sides to isolate the term with \(x\), which gives \( 2x = 8 \), then divide both sides by 2 to get \( x = 4 \)." Saying the reasoning aloud makes each decision visible, so if a step is unjustified, you notice immediately instead of discovering it three steps later.

This verbal habit is especially useful when a strategy fails. If you can explain why you tried something, you can also explain why it did not work, which is the first move toward choosing a better strategy.

Reflection becomes concrete when you solve one problem two different ways and compare them directly. Consider the equation \( 2x + 3 = 11 \) again.

Reflecting on this comparison, guess and check worked here because the answer was a small whole number, but it depended on luck and would struggle with a decimal or negative solution. The algebraic method took fewer steps and would work for any value of \(x\), which is the kind of judgment that turns a one-time success into a transferable strategy.

When you judge whether a strategy was effective, three questions keep the evaluation focused rather than vague.

• Accuracy: Did the strategy lead to a correct, verifiable answer, or did it introduce room for error?
• Efficiency: How many steps, guesses, or calculations did it require compared to an alternative?
• Transferability: Would this same strategy still work if the numbers in the problem changed, for example if the equation had fractions or negative coefficients?

A strategy that scores well on all three is worth adopting as a first choice for similar problems. A strategy that only works under narrow conditions, like guess and check on small whole numbers, is worth keeping as a backup rather than a default.

The point of comparing strategies is not to prove one method is always superior, but to build a personal record of which approach fits which situation. After solving several problems, review your reflections and look for patterns: Do you consistently lose time on a particular type of step? Does one method repeatedly produce careless errors? Adjusting your default strategy based on this evidence is different from simply trying harder next time, since it targets the specific weakness the comparison revealed.

This same evaluative habit supports performance under time pressure, which is explored further in self-monitoring for test performance, where quick strategy checks help you decide when to abandon a slow method mid-problem.

Strategy Reflection: The process of reviewing how a problem was solved, not just whether the answer was correct.

Verbalizing Reasoning: Speaking or writing out each step of a solution to make hidden thinking visible and checkable.

Strategy Comparison: Solving the same problem with two or more methods to judge their relative accuracy and efficiency.

Transferability: Whether a strategy would still work if the numbers or conditions of a problem were changed.

Strategy Revision: Adjusting a chosen method based on evidence from past reflection rather than repeating the same approach automatically.

Try solving one equation two different ways, such as by substitution and by isolating the variable, then write two or three sentences comparing the number of steps each took and where each method could go wrong. Over time, keep a short log of which strategy you chose for which type of problem and whether that choice paid off. This log becomes evidence you can use the next time a similar problem appears, replacing guesswork with a deliberate, evaluated choice.

Related lessons

• Metacognitive strategies talking thinking reflect