How To Teach Problem Solving In Math

The Reality of Teaching Math Problem Solving

Most teachers I've worked with treat problem solving as something you add on at the end of a unit instead of something you build into every lesson from day one. That approach doesn't work. Kids see problem solving as a separate event — a word problem worksheet after they've already learned the procedure. By then the damage is done. They think math is about applying a memorized algorithm, and whenever a problem doesn't fit the pattern they just sit there. I spent about twelve years teaching middle school math and then another four training other teachers, and the thing that surprised me most was how few educators actually understand what's happening when a student gets stuck on a problem. It's not laziness. It's not even always a gap in content knowledge. More often it's that the student has been trained to recognize which operation to use rather than to think about what the problem is asking.

The core skill nobody teaches well

The central issue is that we rarely teach students how to read a problem before they try to solve it. I used to hand out a blank piece of paper and make students write three things before they touched a calculator or drew a diagram: what do I know, what do I need to find, and what connection could link them. That was it. No fancy framework. Just three questions. Here's the thing nobody wants to admit: most kids can do the math. Their procedural fluency is fine. What they lack is the habit of slowing down enough to map the problem before attacking it. I had a student once who could solve systems of equations in his sleep but would draw a blank on a simple rate problem that required setting up the equation. When I asked him to slow down and translate the words into variables, he kept jumping straight to numbers. He'd been rewarded for speed his whole academic life. That was the actual bottleneck, not algebra itself. When you work on How To Teach Problem Solving In Math, the first adjustment is behavioral. You're trying to interrupt a habit that's probably been reinforced for six to eight years. Kids who are fast and accurate get praise and good grades. Asking them to pause and think differently feels slower and riskier. It also exposes them to failure more visibly because they can't just power through with a memorized method.

A practical method that actually works

Start with the bar model. It sounds elementary and plenty of people dismiss it for that reason, but it's one of the most effective tools for building genuine problem solving habits across grade levels. The bar model forces students to represent quantities visually before they write any equation. That visual step is where the actual thinking happens. Without it, kids default to keyword scanning — "total" means add, "leftover" means subtract — which falls apart the moment a problem is slightly unfamiliar. Here's how I ran it in class. I'd project a problem and ask everyone to draw a quick sketch representing the situation. No numbers yet. Just boxes and lines showing the relationships between quantities. Once they had the diagram, then we translated it into an equation. The separation between understanding the structure and performing the calculation matters more than most teachers realize. It gives you a clear window into where each student is actually struggling. One edge case that still sticks with me involved a student who could draw perfect bar models for every type of problem we practiced but couldn't transfer the method to a novel problem on a test. The problem described a situation involving discounts and tax in a way that mixed two processes. She drew two separate bars, solved each correctly in isolation, and then couldn't figure out how to combine them. What I did was pull her aside and have her physically draw the discount calculation first on one side of a whiteboard, then the tax on the other, and finally connect them with an arrow showing that the discounted price becomes the base for the tax calculation. It was a two-minute intervention but it shifted something in how she approached the problem structurally instead of procedurally.

The method requires consistency. If you only do it once a week during test prep, you're not teaching problem solving. You're teaching test taking. You need to embed it into daily work for at least a full semester before you see the transfer effect. Most schools measure progress by standardized test scores, which creates pressure to move quickly through content. That's the tradeoff. You lose ground on coverage initially but gain it back when students stop needing you to tell them which operation to use for each new problem type.

What most teachers miss about student thinking

Students don't struggle with problem solving because they're bad at math. They struggle because they've never been shown how to sit with uncertainty. A well-structured problem leaves a gap between what they know and what they need to find, and that gap creates discomfort. Most kids have been trained to avoid that discomfort as fast as possible by reaching for the nearest familiar procedure. Teaching problem solving means teaching them to tolerate not knowing the answer yet. Counterintuitively, giving students access to worked examples early on slows their learning in the short term but speeds it up significantly over a semester compared to purely discovery-based approaches. This goes against the popular intuition that students should figure things out entirely on their own. Research from Sweller and others supports this, and I saw it play out in my own classroom repeatedly. Students who studied carefully annotated examples of problem solving — where each step included a verbal explanation of why that step was chosen — outperformed students who tried to solve similar problems blind from the start. The key detail is that the examples must include the reasoning, not just the procedure. A worked example that only shows steps is just another way to reinforce mindless pattern matching. Another common pitfall is selecting problems that are too closely matched to what was just taught. If you introduce factoring and then give ten factoring problems, students aren't learning to solve problems. They're learning to recognize which chapter they're on. Mixed practice is harder to design and more uncomfortable for students, but it's the only way to build actual problem solving ability. I used a system where every homework set contained three problems from the current topic and two from previous units. It made grading take longer because students made different kinds of mistakes, but within a term their performance on cumulative assessments improved noticeably.

How To Teach Problem Solving In Math beyond the classroom

Parents and tutors often try to help by solving the problem for the student or explaining the solution step by step. That's the wrong move every single time. The student needs to be the one doing the translating and planning. Your role is to ask questions that force them to articulate what they're doing. "What does this number represent?" "What are you trying to find?" "How do these two pieces connect?" Those questions take more patience than just showing the work, but they're the only ones that change how the student thinks. There's also a real limitation here that nobody likes to discuss. This approach works well for students who have at least basic procedural fluency. If a student can't perform the arithmetic or doesn't understand the operations themselves, working on problem solving strategies won't help much. You need to address the foundational gaps first. I've seen teachers try to teach reasoning skills to kids who are struggling with multiplication facts, and it's frustrating for everyone involved. The student can't access the strategy because the underlying math isn't secure yet. In those cases, go back to building fluency with targeted practice before layering in the problem solving work. The other hard truth is that this method requires class time that many curricula don't allocate. If you're behind on state-mandated content, pulling out twenty minutes a day for problem solving feels like a luxury you can't afford. It is, honestly. The realistic workaround is to weave it into existing lessons instead of adding it as a separate block. Use the first five minutes of class for a low-stakes problem from a previous topic. Use the last ten minutes for a shared problem solving session where the class works through one problem together using the bar model or translation steps. Over a year that adds up to significant practice without requiring extra scheduling.

If you're looking for resources to support this work, the NCTM has a solid collection of tasks organized by practice standards rather than just content standards. The Illustrative Mathematics project also provides open-source problems that are intentionally designed for sense-making rather than algorithm application. Both are free. Commercial workbooks tend to focus on drill disguised as problem solving, so I'd steer clear of those unless you've reviewed the actual problems inside. The bottom line is that teaching problem solving is slow and unglamorous. It doesn't produce immediate visible results the way a test score boost from drill practice does. But the students who go through it develop a way of approaching unfamiliar problems that lasts well beyond any single math class. That's the actual goal, even if it's hard to measure on a standardized rubric.