How to improve problem-solving skills quickly begins before the solution. Strong problem solving means representing a problem accurately, identifying the goal and constraints, finding the information that matters, generating or selecting a method, carrying it out, checking the result and learning from the attempt. Faster problem solving is therefore not simply faster calculation or faster guessing. It is reducing avoidable wrong turns while protecting accuracy and judgement.
Students searching for problem solving skills, critical thinking, analytical skills, decision making, mathematical problem solving, creative problem solving and how to solve problems often receive lists of techniques. Working backwards, drawing diagrams, breaking problems into parts, using examples, estimating and brainstorming can all help, but no technique is universally correct. The fastest responsible route is diagnostic: identify what kind of obstacle is present and choose a representation or test that makes the next decision more informative.
This complete guide connects reasoning, critical thinking, creativity, mathematics, science, reading, writing, decision making, feedback and verification. It is an add-only child of How to Improve Anything Quickly and complements The Importance of Problem Solving. The central proposition is: improve the representation of the problem, make the next attempt informative, and keep the method only when it survives checking and transfer.
The 50-second route
If you are stuck, restate the goal and known conditions. If the problem feels too large, isolate a smaller dependency. If you have many ideas, choose a test that can eliminate weak options. If a familiar method fails, ask which assumption made it seem applicable. If the answer looks right, verify it independently. If a teacher’s hint unlocks the solution, identify exactly what the hint supplied and test that decision on a fresh problem.
1. Improve problem solving through define the problem
Define the decision. define the problem matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
2. Improve problem solving through represent the situation
Define the decision. represent the situation matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
3. Improve problem solving through separate facts from assumptions
Define the decision. separate facts from assumptions matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
4. Improve problem solving through identify the goal
Define the decision. identify the goal matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
5. Improve problem solving through identify constraints
Define the decision. identify constraints matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
6. Improve problem solving through find missing information
Define the decision. find missing information matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
7. Improve problem solving through break a large problem into parts
Define the decision. break a large problem into parts matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
8. Improve problem solving through find prerequisites
Define the decision. find prerequisites matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
9. Improve problem solving through choose a useful model
Define the decision. choose a useful model matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
10. Improve problem solving through draw a diagram
Define the decision. draw a diagram matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
11. Improve problem solving through make a table
Define the decision. make a table matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
12. Improve problem solving through write an equation
Define the decision. write an equation matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
13. Improve problem solving through use examples
Define the decision. use examples matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
14. Improve problem solving through use counterexamples
Define the decision. use counterexamples matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
15. Improve problem solving through compare alternatives
Define the decision. compare alternatives matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
16. Improve problem solving through generate options
Define the decision. generate options matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
17. Improve problem solving through prioritise by consequence
Define the decision. prioritise by consequence matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
18. Improve problem solving through estimate before calculating
Define the decision. estimate before calculating matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
19. Improve problem solving through reason from units
Define the decision. reason from units matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
20. Improve problem solving through look for patterns
Define the decision. look for patterns matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
21. Improve problem solving through test a hypothesis
Define the decision. test a hypothesis matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
22. Improve problem solving through ask better questions
Define the decision. ask better questions matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
23. Improve problem solving through use analogies carefully
Define the decision. use analogies carefully matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
24. Improve problem solving through work backwards
Define the decision. work backwards matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
25. Improve problem solving through solve a simpler version
Define the decision. solve a simpler version matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
26. Improve problem solving through change representation
Define the decision. change representation matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
27. Improve problem solving through check boundary cases
Define the decision. check boundary cases matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
28. Improve problem solving through verify a result
Define the decision. verify a result matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
29. Improve problem solving through explain the method
Define the decision. explain the method matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
30. Improve problem solving through spot hidden assumptions
Define the decision. spot hidden assumptions matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
31. Improve problem solving through distinguish correlation and cause
Define the decision. distinguish correlation and cause matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
32. Improve problem solving through handle uncertainty
Define the decision. handle uncertainty matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
33. Improve problem solving through make decisions with incomplete information
Define the decision. make decisions with incomplete information matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
34. Improve problem solving through avoid premature closure
Define the decision. avoid premature closure matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
35. Improve problem solving through avoid confirmation bias
Define the decision. avoid confirmation bias matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
36. Improve problem solving through learn from errors
Define the decision. learn from errors matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
37. Improve problem solving through use feedback
Define the decision. use feedback matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
38. Improve problem solving through collaborate without outsourcing thinking
Define the decision. collaborate without outsourcing thinking matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
39. Improve problem solving through communicate the solution
Define the decision. communicate the solution matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
40. Improve problem solving through mathematics problem solving
Define the decision. mathematics problem solving matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
41. Improve problem solving through science problem solving
Define the decision. science problem solving matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
42. Improve problem solving through reading comprehension problems
Define the decision. reading comprehension problems matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
43. Improve problem solving through writing problems
Define the decision. writing problems matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
44. Improve problem solving through project problems
Define the decision. project problems matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
45. Improve problem solving through everyday planning
Define the decision. everyday planning matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
46. Improve problem solving through team problems
Define the decision. team problems matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
47. Improve problem solving through digital tools and AI
Define the decision. digital tools and AI matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
48. Improve problem solving through twenty-minute workshop
Define the decision. twenty-minute workshop matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
49. Improve problem solving through seven-day experiment
Define the decision. seven-day experiment matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
50. Improve problem solving through thirty-day system
Define the decision. thirty-day system matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
51. Improve problem solving through plateaus
Define the decision. plateaus matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
52. Improve problem solving through casebook: wrong problem
Define the decision. casebook: wrong problem matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
53. Improve problem solving through casebook: right method wrong execution
Define the decision. casebook: right method wrong execution matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
54. Improve problem solving through casebook: too many options
Define the decision. casebook: too many options matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
55. Improve problem solving through casebook: familiar pattern trap
Define the decision. casebook: familiar pattern trap matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
56. Improve problem solving through casebook: unsupported answer
Define the decision. casebook: unsupported answer matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
57. Improve problem solving through parents
Define the decision. parents matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
58. Improve problem solving through teachers
Define the decision. teachers matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
59. Improve problem solving through advanced learners
Define the decision. advanced learners matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
60. Improve problem solving through measurement
Define the decision. measurement matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
61. Improve problem solving through independence
Define the decision. independence matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
62. Improve problem solving through transfer
Define the decision. transfer matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
63. Improve problem solving through FAQ and next routes
Define the decision. FAQ and next routes matters only when it changes what the solver can do next. Begin with a representative problem and preserve the first attempt. State the goal, available information, constraints and required standard. Avoid labels such as ‘careless’ or ‘not a problem solver’; they compress many possible failure points into a judgement that does not tell us what to practise.
Diagnose before adding difficulty. Ask what the solver believed the problem was asking, what they noticed first, which method they selected and why. A wrong result can arise from a poor representation, missing prerequisite, unsuitable strategy, execution error, unchecked assumption or verification failure. Those are different instructional problems. More questions of the same type may simply reproduce the same error.
Use a model and a near miss. Show one solution whose important decisions are visible and one plausible solution that fails at a specific point. Ask the learner to locate the first divergence. The useful lesson is not ‘copy the correct steps’; it is the condition that makes one step valid and the other invalid. Then change the surface details so the learner must recognise the condition rather than remember the page.
Practise the bottleneck. Reduce irrelevant load while keeping the target decision. If method selection is weak, use simple numbers but mixed relationships. If verification is weak, provide candidate solutions that include a subtle error. If representation is weak, ask for diagrams, tables, equations or verbal models before execution. Practice should make the uncertainty legible enough for feedback.
Check and explain. A solution is stronger when another route, substitution, estimate, unit check, counterexample or source can test it. Verification should be meaningfully independent where possible; repeating the same reasoning in the same form can reproduce the same mistake. Ask the solver to explain why the method fits, what assumption it uses and what result would have shown that the approach was wrong.
Transfer. Move from the isolated decision back to a whole unfamiliar problem. Record prompts honestly. A learner who succeeds after ‘draw a bar model’ has demonstrated supported execution; a learner who independently decides that a representation is useful has demonstrated strategy selection. Both are progress. The long-term aim is flexible judgement: selecting, adapting and abandoning methods according to evidence rather than loyalty to a favourite trick.
Evidence and limits
The Education Endowment Foundation metacognition and self-regulation synthesis supports explicit planning, monitoring and evaluation in learning, while implementation and context matter. The examples, laboratories and schedules here are eduKateSG instructional designs, not a single independently evaluated problem-solving programme.
Continue through How Mathematics Works, How Science Works, the English Learning Hub and the general How to Improve Anything Quickly owner. Good problem solving is not possession of the longest strategy list. It is the ability to represent the current problem, choose a defensible next move, check what happened and revise when the evidence says the model was wrong.
