How to Teach Math Problem-Solving When Students Just Want the Answer

There's a version of math instruction that produces students who can follow any procedure they've been shown and can't solve any problem they haven't. They can execute the algorithm flawlessly. They can't figure out which algorithm to use, or what to do when the problem doesn't fit any they've seen.

This isn't a student failure — it's an instruction failure. Procedure teaching and problem-solving teaching are different activities. A curriculum of procedures produces procedural skill. It does not, on its own, produce problem-solving ability.

What Problem-Solving Actually Requires

Problem-solving requires students to do several things that procedure execution doesn't:

Understand the situation: What is this problem about? What's being asked? What do I know and what do I need to find?

Select an approach: Which strategy or tool is appropriate here? Have I seen something like this before? What's a reasonable first step even if I'm not sure it's the right one?

Monitor progress: Is this working? Does my answer make sense so far? Do I need to try something different?

Evaluate the result: Does this answer make sense given the problem? Is it the right type of answer? Is it in reasonable range?

None of these four skills come from practice with procedures. They come from practice with genuine problems — problems where the approach isn't obvious and the path isn't predetermined.

The Problem With Worked Examples as the Default

When procedure instruction is the primary mode of math teaching, students develop a model of mathematics as "apply the procedure shown to problems that look like the example." This works efficiently for low-complexity tasks and fails systematically on novel problems.

The limitation becomes visible on word problems, multi-step tasks, and open-ended problems — exactly the kinds of problems that appear on standardized tests and in real-world applications. Students who have only practiced algorithm execution don't have the problem-solving skills to navigate ambiguity.

This doesn't mean worked examples are bad. They're highly effective for building procedural fluency. The issue is when they're the only instructional mode and when students never encounter problems where the procedure isn't obvious.

Using Low-Floor, High-Ceiling Tasks

One of the most effective ways to build problem-solving is through tasks with a low entry point and a high ceiling — problems where everyone can start somewhere, and where the problem can be pushed further by those who finish quickly.

A low-floor task doesn't require advanced prior knowledge to make an initial attempt. A high-ceiling task has extensions that remain challenging even for students who complete the core problem quickly. This combination reduces the stratification that often happens in math class where some students are done in two minutes and others haven't started.

Examples of low-floor, high-ceiling prompts:

• "Find as many ways as you can to make 100."
• "What questions could you ask about this graph?"
• "Is it always, sometimes, or never true that...?"

These prompts don't have single correct answers, which means students can't wait to be told what to do. They have to think.

Teaching Problem-Solving Strategies Explicitly

Students benefit from having a repertoire of problem-solving strategies they can draw on when they're stuck. Common strategies worth teaching explicitly:

• Draw a picture or diagram
• Make a table
• Look for a pattern
• Try a simpler version of the problem first
• Work backward from the answer
• Guess and check, then refine

The goal isn't to memorize strategies. It's to know that when you're stuck, there are things you can try. Students who have no strategy for what to do when they don't know what to do give up. Students with a repertoire of approaches have something to reach for.

Teach each strategy explicitly with problems where it's useful. Then provide problems where students have to select the strategy — not just apply the one that was just demonstrated.

Making Thinking Visible

The most important shift in problem-solving instruction is making the thinking process visible, not just the final answer. When you model problem-solving, narrate your reasoning: "I don't know where to start, so I'm going to draw a picture and see if that helps me understand the situation." "I got an answer of 500. That seems way too high — let me check my reasoning."

When students share their work, ask about the process, not just the product. "How did you decide to start there?" "What did you try first?" "What would you do differently if you got stuck again?" These questions signal that the process matters, not just getting the right answer.

Your Next Step

In your next math class, give students one problem where the procedure isn't immediately obvious. Before they begin, tell them: "You have five minutes to think about what you know and what you might try. You don't have to be right — you have to be thinking." After five minutes, have three students share what they tried, including approaches that didn't work. This one practice — making initial strategies visible regardless of whether they succeed — begins to shift student identity from "I need to know the procedure" to "I can figure out where to start."