Teaching Math Problem Solving: How to Help Students Think, Not Just Calculate

The gap between students who are good at math computations and students who can actually solve problems is one of the most persistent challenges in math education. A student can know every multiplication fact, understand the algorithm for long division, and still be completely lost when a word problem asks them to apply those skills in a situation they haven't seen before.

Problem solving is a distinct skill from computation. It requires understanding the problem, selecting relevant information, choosing a strategy, executing it, and evaluating whether the answer makes sense. Most math instruction teaches computation; problem-solving instruction requires something additional.

George Polya's Four-Step Framework

George Polya's 1945 book "How to Solve It" articulated a framework for mathematical problem solving that still dominates how the skill is taught and understood:

1. Understand the problem — What is asked? What information is given? What are the constraints? Can you restate the problem in your own words?
2. Devise a plan — What strategy or approach might work? Have you seen a similar problem before? Can you break this into smaller problems?
3. Carry out the plan — Execute the strategy, checking each step.
4. Look back — Does the answer make sense? Can you verify it? Is there another approach that would work?

The fourth step — looking back — is the most commonly skipped by students and teachers alike. Students who check their answers only for arithmetic errors are not looking back in Polya's sense. Looking back means evaluating whether the answer is reasonable in context, whether the strategy was efficient, and whether the problem reveals anything generalizable.

The Problem with "Key Words"

Many students are taught a shortcut: look for "key words" that signal which operation to use. "Altogether" means addition; "difference" means subtraction; "product" means multiplication.

This approach fails regularly, and the failure is predictable. Word problems are deliberately written with language that doesn't follow the key-word formula. Students who rely on key words rather than comprehending the problem structure often pick the wrong operation, especially on non-routine problems.

The alternative is teaching students to understand the problem situation — what is happening, what relationship exists between the quantities — rather than pattern-matching to words. "If 4 students each have 3 books, how many books total?" — the answer is multiplication not because the word "each" appears but because equal groups exist and total is asked. Understanding the structure of the situation produces reliable operation selection; key word matching doesn't.

Problem-Solving Strategies Worth Teaching

Students need a repertoire of strategies to apply when the obvious approach isn't obvious. Explicitly teaching and naming strategies gives students language for their own thinking and tools to try when they're stuck.

Draw a picture or diagram. Representing the problem visually often reveals relationships that aren't apparent in the verbal description. Area and perimeter problems, fraction problems, ratio problems, and many others are more tractable when represented spatially.

Make a table. Organizing information in a table reveals patterns. Rate problems, pattern problems, and proportional reasoning problems often yield to systematic tabulation.

Guess and check. Systematic trial and error with organized tracking is a legitimate mathematical strategy. Students who try a value, see whether it produces the right result, and adjust based on what they find are reasoning mathematically even when the approach looks informal.

Work backward. When the final state is known and the starting state is unknown, reverse reasoning from the end backward to the beginning often solves the problem directly.

Look for a pattern. Mathematical patterns — in sequences, in function outputs, in geometric figures — are powerful problem-solving tools. Students who look for and articulate patterns are doing genuine mathematical thinking.

Simplify the problem. Working through a simpler version of a hard problem — fewer quantities, smaller numbers, fewer variables — reveals the structure that applies to the harder problem.

The goal isn't to teach students to rotate through these strategies mechanically; it's to build a repertoire of approaches they can draw on when the first thing they try doesn't work.

Making the Process Visible

Problem solving is largely invisible — it happens in students' heads. Making it visible is both instructional and assessment:

Think-alouds. Model your own problem-solving process out loud: "I'm reading this problem... okay, I'm not sure what it's asking. Let me reread... I think it's asking how many are left after some are removed, so I'll think about subtraction. But wait — let me reread to make sure..."

Written problem-solving documentation. Ask students to show not just the computation but the process: restating the problem, identifying the strategy chosen, showing the work, and checking the answer. This slows students down (often productively) and makes the process graditable.

Comparing solution strategies. After students solve a problem, having two or three students share different approaches — and discussing which approach is more efficient, more generalizable, or more elegant — teaches students that multiple solution paths exist and that evaluating strategies is part of mathematical thinking.

Unfinished problems for discussion. Showing a student's half-finished solution (with the student's permission) and asking "what did this student do so far? What might they do next? Is there a problem with their approach?" drives analytical thinking about the process.

Non-Routine Problems

The best way to develop problem-solving skills is to give students genuine problems — problems they haven't seen a template for, that don't have an obvious first step. Non-routine problems are uncomfortable for students and for teachers because neither group can rely on pattern recognition.

Well-designed non-routine problems are accessible (students have the mathematical tools to solve them even if the path isn't obvious) but not routine (students can't immediately recall how to do this from prior practice). Open Middle problems, three-act tasks, and NRICH problems are sources of well-designed non-routine problems across grade levels.

Your Next Step

Take one problem from your current unit and redesign how you present it. Instead of demonstrating the solution strategy and then having students practice, present the problem cold — no hints about which strategy to use — and give students 10 minutes to work on it individually or in pairs. Then facilitate a discussion in which students share different approaches. What happened? Which strategies appeared? Where did students get stuck? Use what you observe to plan explicit strategy instruction targeted at the actual sticking points.