Reviewing Your Problem-Solving Approach

A timed test ends the moment you submit your answers, but the reasoning behind those answers is still worth examining. Reviewing your problem-solving approach means treating a completed test as evidence rather than as a closed event: you go back through your own reasoning, locate exactly where it succeeded or failed, and use that analysis to change what you do next time you are working against a clock.

Most students who miss a question move on without asking why they missed it. That habit leaves the same error pattern intact for the next test. A deliberate review separates two very different problems that feel identical in the moment: not knowing the content, and knowing the content but applying it incorrectly under pressure. Only the second problem is fixed by better test-taking strategy rather than more studying, so the distinction matters before you decide what to change.

Sort every missed or uncertain question into one of three categories. A reasoning error occurs when the method you chose was wrong from the start, meaning no amount of careful arithmetic would have saved the answer. An execution error occurs when your method was sound but a step was misapplied, such as a sign error or a misread condition. A pacing error occurs when you understood the question but ran out of time or rushed the final steps to stay on schedule. These categories require different fixes: reasoning errors call for reworking your conceptual approach, execution errors call for slower, more deliberate checking, and pacing errors call for restructuring how you allocate time across a test.

Running this review as a repeatable cycle keeps it from becoming a vague, one-time glance at your mistakes. The four stages below move from the raw attempt toward a concrete adjustment you can apply on your next timed task.

The flagging stage matters because memory of your own reasoning fades quickly. Marking a question as uncertain the moment you finish it, rather than waiting until scores return, preserves details about why you hesitated that you would otherwise lose.

A short written record turns scattered observations into a pattern you can act on. Rather than simply noting that an answer was wrong, record the error type, the likely cause, and a specific fix stated as an action, not a vague intention.

After several tests, the log itself becomes the evidence. If execution errors cluster in the final third of your log, the cause is almost certainly pacing pressure rather than weak understanding, and the fix belongs in your time budget, not in restudying the content.

Time pressure is often the hidden variable behind errors that look like careless mistakes. Dividing total test time \( T \) by the number of questions \( n \) gives a rough per-question budget \( t = \dfrac{T}{n} \), which you can use afterward to see exactly which questions ran over. If a question consumed triple the budgeted time, that is a pacing failure worth addressing directly, for instance by setting a firmer internal limit on when to guess and move forward instead of continuing to search for certainty.

The final step is converting this analysis into a small number of specific commitments rather than a general resolution to "be more careful." A useful adjustment names a trigger and a response, such as moving to the next question after a fixed amount of time without progress, or rewriting a calculation on paper instead of tracking it mentally when fatigue sets in. Reviewing your approach only pays off once an identified pattern becomes a concrete change in behavior on the next timed attempt.

Reasoning Error: A mistake caused by selecting an incorrect method or misunderstanding a concept, independent of how carefully it was carried out.

Execution Error: A mistake made while carrying out a correct method, such as a computational slip or a misread value.

Pacing Error: A mistake or omission caused by insufficient time rather than by a gap in understanding.

Error Log: A written record of missed or uncertain questions that tracks error type, cause, and intended fix across multiple tests.

Time Budget: A planned allocation of minutes per question or section, calculated by dividing total time by the number of items.

Strategic Flagging: Marking uncertain answers during a test so they can be reviewed immediately afterward while reasoning is still fresh.

Strategy Adjustment: A specific, triggered change in test-taking behavior made in response to a pattern identified during review.

Related lessons

• Metacognitive Strategies: Reflecting on Thinking Process