Problem Solving Is Domain Specific

I’ve sat through enough “innovation seminars” to know the drill: some consultant in a slim-fit suit stands at the front of a hall, presenting a colourful slide deck about how problem solving develops through “divergent thinking frameworks” and “open-ended inquiry.” It sounds lovely on paper, doesn’t it? But here is the reality: those frameworks rarely survive the moment a Year 9 student decides their primary goal for the lesson is to see how many pens they can balance on their nose. We’ve been sold this idea that problem solving is a mystical spark that happens when you simply step back and let them struggle, but in a classroom of thirty, unstructured struggle is usually just chaos.

I’m not here to give you another theoretical model to add to your pile of half-read CPD handouts. Instead, I want to talk about the actual, messy mechanics of how problem solving develops when you’re actually teaching. We’re going to look at how to scaffold that thinking without doing the work for them, and more importantly, how to spot the difference between a student who is deeply engaged in a challenge and one who has simply given up because they’ve hit a wall. No fluff, no expensive kits—just the stuff that actually works when you’re tired and the bell is about to ring.

Beyond the Textbook Real World Analytical Skill Building

We’ve all seen it: a student can recite the steps of a method perfectly for a test, but the moment you give them a scenario that isn’t in the textbook, they freeze. That’s because we often mistake memorisation for actual analytical skill building. Real growth doesn’t happen when they are following a recipe; it happens when the recipe fails. I’ve found that the most profound moments of cognitive development and reasoning occur when I stop providing the scaffold and instead let them sit in the discomfort of a messy, unstructured problem. It’s uncomfortable for us as teachers, too, because it feels like losing control, but that’s where the real work begins.

If we want them to actually use these tools, we have to move toward metacognition in problem solving. This isn’t about teaching them a new trick; it’s about getting them to look at their own mental process and ask, “Why did I just assume that was the right path?” It’s about moving away from “finding the answer” and toward understanding the logic of the struggle. When they start questioning their own shortcuts, you know they’re actually learning.

Metacognition in Problem Solving When Time Is Running Out

Now, let’s talk about metacognition. If you look it up in a textbook, it sounds like this lofty, high-level mental process involving deep reflection. But in a classroom where the bell is about to ring and you’ve still got six kids staring at a blank page, metacognition in problem solving is much more practical. It’s simply the art of teaching them to think about why they are stuck. Instead of handing them the answer when they groan, you ask, “What was your first move, and why did it hit a wall?” It’s about turning that moment of frustration into a tiny bit of self-awareness.

The problem is that most schemes of work treat critical thinking skill acquisition like it’s something that happens in a vacuum, during a quiet study period. It doesn’t. It happens in the mess. When we model our own thought processes—admitting when we’ve misread a prompt or how we’re narrowing down options—we are showing them how to navigate the fog. It isn’t about a perfect, linear progression; it’s about giving them the tools to audit their own logic while the chaos is still happening around them.

Survival Tactics: How Problem-Solving Actually Sticks

• Stop treating every problem like a high-stakes exam question; sometimes the best way to develop a skill is to let them struggle with a messy, low-stakes task where the “right” answer isn’t even on the whiteboard.
• Model the mess, not the perfection; show them your own scratchpad where you’ve made a mistake, because if they only see the polished final result, they’ll think problem-solving is a magic trick rather than a process of trial and error.
• Use “scaffolded release” instead of constant intervention; give them just enough of a hint to keep them from hitting the wall, but not so much that you’ve done the cognitive heavy lifting for them while they’re just staring at you.
• Prioritise the “why” over the “how”; it doesn’t matter if they can follow a five-step procedure to get an answer if they can’t explain why they took the second step when you inevitably change the variables halfway through the lesson.
• Value the “productive struggle” even when the room is loud; it’s tempting to jump in and fix everything to keep the lesson on track, but real development happens in that uncomfortable gap between them being stuck and them finding the thread.

What Actually Sticks When the Bell Rings

Stop treating problem-solving like a standalone lesson; it’s a muscle that only grows when you let students struggle through a messy, imperfect process during their regular work.

Metacognition isn’t a fancy buzzword to write on a whiteboard—it’s just the habit of asking a student, “Why did you choose that route?” when they’ve hit a dead end.

If a strategy requires twenty minutes of perfect silence and a pristine classroom to work, it isn’t a teaching tool; it’s a fantasy. Focus on the small, gritty wins that survive a chaotic Period 5.

## The Myth of the 'Eureka' Moment

We talk about problem-solving as this grand, sudden spark of genius, but in a real classroom, it’s much messier than that. It’s actually just the slow, frustrating process of a student learning how to sit with a mistake without looking to you to fix it for them. Real development isn’t about finding the right answer immediately; it’s about building the stamina to stay in the struggle when the lesson is moving too fast and the instructions were clearly misunderstood.

Ellery Mwangi-Selkirk

The Reality of the Long Game

At the end of the day, developing problem-solving skills isn’t about ticking off a list of high-level cognitive strategies or implementing some shiny new pedagogical framework that looks great on a slide deck. It’s about the messy, unscripted moments where a student realizes that the first three attempts at a task were dead ends and decides not to shut down. It’s about moving from the safety of a textbook to the unpredictable friction of real-world application, and teaching them to navigate that friction using the metacognitive tools we’ve managed to squeeze into a forty-minute period. We aren’t building perfect logic machines; we are helping them build the resilience to stay in the room when the answer isn’t immediately obvious.

I know how it feels when you’re staring at a lesson plan that’s falling apart and you feel like you’re failing to teach these “essential life skills.” But remember, the most profound problem-solving often happens in the gaps between the planned activities. If you can create a classroom where it is safe to be wrong, where the struggle is seen as the work rather than an interruption to it, you have already won. Don’t worry about the perfect curriculum; just focus on the kids. If they leave your room knowing how to face a mess without panicking, then you’ve done more than enough.

About Ellery Mwangi-Selkirk

Most educational advice is written for a classroom that does not exist — twenty motivated pupils, unlimited preparation time, no behaviour to manage. I write for the room you are actually in. What retrieval practice looks like when marking is already three weeks behind, why the seating plan matters more than the starter activity, and which of the last decade's initiatives left anything behind. Nineteen years taught me that the good ideas survive contact with a wet Wednesday and the rest do not.