"Solving" Math vs. "Processing" Math: Why Processing Math Has a Ceiling

There are two very different ways a student can "do" math, and most people never learn to tell them apart.

The first is what I'll call "processing math". "Processing" math is fundamentally limited: it can only take you to a destination whose route you already know. You've seen this exact type of problem before, you recognize the pattern, you run the procedure, you arrive. That's it. That's the whole trip.

The trouble is that real math problems don't work that way. A well-designed problem doesn't ask you to walk a road you've already memorized. It deliberately names a destination whose route you don't know, and asks you to find your own way there.

The tell: inconsistent test scores

If you want to spot a student who is relying on "processing" math, look at their test scores. These are the students who sometimes score very high and sometimes score surprisingly low, with no obvious pattern in between.

That inconsistency isn't bad luck. It's a direct symptom of processing math. A student who has only trained routes to known destinations will do beautifully on any test that happens to ask for those destinations and will stall out the moment a problem asks for somewhere new. Their score isn't measuring their math ability so much as it's measuring how closely that particular test happened to match the routes they'd already memorized.

What "solving" math looks like instead

A student who has trained "solving math", on the other hand, has built something different: the capacity to arrive at a destination without already knowing the route. This is a skill in its own right, separate from the accumulation of known methods. And because it's a general-purpose capacity rather than a lookup table, it doesn't care whether the destination is familiar or not. Known route, unknown route, the student can get there either way.

This is why "solving-math" students tend to have more stable, predictable scores over time. Their performance isn't gated by whether this specific test happened to overlap with what they'd memorized.

Why "just study harder" doesn't fix "processing" math

When a "processing-math" student's grades are shaky, the typical response is to teach them more routes: expand the list of destinations they know how to reach, or drill the existing routes until they're rock-solid. Both are reasonable-sounding fixes, and both are still "processing" math. They don't touch the underlying limitation.

To reach a genuinely new destination, a student needs something that no amount of memorized routes can give them: the knowledge and the patience to handle detours, dead ends, and roadblocks along the way. Without that, most students simply give up part way through an unfamiliar problem, not because they lack ability, but because they've never practiced tolerating the discomfort of not immediately knowing the way.

Keep a student on a steady diet of "processing" math, and the outcome is predictable: no matter how hard they work, their growth plateaus, and eventually they come to dislike math altogether. Effort stops translating into progress, and that disconnect is demoralizing in a way that's hard to recover from.

The slower path that goes further

Training solving ability is a different bargain entirely. It takes longer to reach unfamiliar or confusing destinations. There's no shortcut around the detours and roadblocks. In the early stages, scores may not improve as quickly as they would under a "processing-math" regimen. That's the trade-off, and it's real.

But the ceiling is completely different. Over time, a student built on solving math has much more room to grow than one built on processing math ever will, precisely because their growth isn't capped by the size of their memorized route list.

So what does "solving" math actually look like in practice? What are strong "solvers" specifically doing that "processing-math" students aren't? That's a question for another post.