Teaching Mathematical Problem-Solving (Not Just Procedures)

The most common complaint math teachers hear from students is "just tell me what formula to use." The students who say this aren't lazy — they've been trained. Years of math instruction that prioritized procedure execution over mathematical reasoning has taught them that math is about following steps correctly. When they encounter a problem without an obvious procedure to follow, they freeze.

Teaching mathematical problem-solving means teaching a different way of being in relationship with a problem — one characterized by curiosity, persistence, and strategy rather than procedure retrieval. This is harder to teach than algorithms, but it produces students who can actually use mathematics.

What Mathematical Problem-Solving Actually Is

George Pólya's How to Solve It (1945) identified four phases of problem-solving that remain accurate: understand the problem, devise a plan, carry out the plan, look back. This sounds simple. The hard part is the second phase — devising a plan — which requires mathematical knowledge, pattern recognition, and judgment that doesn't come from memorizing procedures.

A student who can only execute procedures they've been shown is doing mathematics the way a cook follows a recipe: following instructions to produce a predetermined result. A student who can problem-solve is doing mathematics the way a chef cooks: using knowledge of ingredients, techniques, and flavor to create something without a predefined script.

Both skills matter. Students need to know their procedures. But procedure knowledge without problem-solving ability produces students who can execute steps and nothing else.

Teach Problems Before Procedures

One of the most powerful shifts a math teacher can make is introducing problems before teaching the procedures that solve them. This is counterintuitive — students can't solve the problem without the tool yet, so why show them the problem first?

Because struggling with a problem before you have the tool to solve it does something that the reverse cannot: it creates the need for the tool. When students have genuinely wrestled with a problem and seen that their current strategies don't work, the new procedure doesn't feel like an arbitrary rule to memorize. It feels like the answer to a question they actually had.

This is sometimes called "productive failure" — intentional design of learning experiences where students attempt a problem before instruction, fail instructively, and then receive the concept or procedure that unlocks the problem. Research consistently shows that students who struggle productively before instruction learn more deeply and remember longer than students who receive direct instruction first.

The Launch: How You Introduce a Problem Matters

The way you launch a problem shapes how students engage with it. A strong problem launch:

Gives just enough context, not too much. Don't pre-teach the solution strategy. Don't solve a similar example first. Give students the information they need to understand the problem and let them encounter the difficulty themselves.

Ensures everyone understands the problem. Before students begin working, do a quick sense-check: "What are we trying to find out? What information do we have? What would a wrong answer look like?" This isn't solving the problem — it's establishing what the problem is.

Sets the expectation that difficulty is the point. Explicitly tell students that this problem is designed to be hard, that struggling is part of it, and that you're not looking for them to get the answer quickly. Many students need explicit permission to find a problem hard.

Productive Struggle vs. Unproductive Struggle

Not all struggle is good. Productive struggle is generative — students are thinking, trying strategies, making connections, and refining approaches even if they're not succeeding. Unproductive struggle is paralysis — students don't know where to begin and aren't doing any mathematical thinking.

Your role during problem-solving is to keep students in productive struggle and rescue them from unproductive struggle. This requires recognizing the difference, which means circulating and listening rather than standing at the front.

Questions that move students from unproductive to productive struggle:

• "What do you know? What are you trying to find?"
• "Have you seen a problem that looks like this before? How was it different?"
• "What would happen if you started with a simpler version of this problem?"
• "What have you tried? What happened when you tried it?"

These questions activate thinking without giving away the solution. The goal is to get students doing mathematics again, not to do the mathematics for them.

Making the Work Visible

Mathematical problem-solving should happen visibly — on whiteboards, on chart paper, in student journals that can be shared. When students' thinking is visible, several things happen: students can see different approaches and compare them, you can assess thinking in process rather than only at the end, and the norm of "multiple paths are possible" becomes apparent.

After problem-solving, bring the class together to compare approaches. "Three groups solved this, and they did it three different ways. Let's look at what's the same and what's different." This debrief is where much of the learning consolidates. Students who used one approach see another and expand their repertoire. Students who found the elegant solution see it recognized publicly. The debrief also allows you to name the mathematical idea at the center of multiple approaches — making the concept visible across different methods.

The Transfer Problem

Students often can problem-solve within the context where they learned the strategy and fail to transfer that strategy to new contexts. Transfer doesn't happen automatically; it has to be taught.

Help students build transferable problem-solving strategies by naming the strategies explicitly: "What you just did — simplifying the problem to a special case and then generalizing — is a strategy that works in many contexts. Where else could you use it?" Metacognitive prompts like this train students to see their problem-solving strategies as tools in a toolkit, not responses to specific problems.

The goal is students who encounter an unfamiliar problem and think: "I don't know the answer to this yet, but I know how to start working on it." That disposition — confident engagement with uncertainty — is what mathematical problem-solving instruction is really building.