Every teacher knows that problem-solving is important. It appears in curriculum documents, Ofsted frameworks, and school development plans with reliable frequency. But what does it actually look like in practice, and how do we build it deliberately rather than hoping it just happens?
The Link Between Puzzles and Computational Thinking
Computational thinking — the ability to break down complex problems, spot patterns, and design step-by-step solutions — underpins not just computing but maths, science, and design technology. It’s the skill that lets a student look at a problem and think “right, where do I start?” rather than “I don’t know what to do.”
Puzzles are one of the best training grounds for this kind of thinking. Not the jigsaw-on-a-rainy-afternoon kind (though those have their place), but structured challenges where students must analyse, hypothesise, test, and refine. The cognitive benefits are well-documented: improved spatial reasoning, stronger working memory, better logical deduction.
From Puzzles to Programming
There’s a direct line from puzzle-solving to programming. When a student writes code to make a robot navigate a maze, they’re doing exactly what they do with a good puzzle: breaking the task into steps, predicting what will happen, testing their prediction, and adjusting when it doesn’t work. The robot just makes the feedback loop faster and more tangible.
In our Intermediate STEMbotics workshops, students build and program robots to solve increasingly complex challenges. They start with straightforward navigation tasks and progress to multi-step problems that require sequencing, conditional logic, and iteration. Each challenge is essentially a puzzle with a physical outcome.
Practical Ways to Build Problem-Solving in Your Classroom
- Start with the struggle. Resist the urge to scaffold everything. Give students a challenge, let them hit the wall, and then facilitate rather than instruct. The productive struggle is where the learning happens.
- Make thinking visible. Ask students to explain their approach before they try it. Prediction forces them to think systematically rather than guess-and-check.
- Use physical manipulatives. Whether it’s robots, circuits, or building materials, physical objects create a feedback loop that screens alone can’t match.
- Celebrate the debugging. When something goes wrong, that’s the most valuable moment in the lesson. Normalise error as part of the process.
Building a Problem-Solving Culture
The schools that do this best aren’t the ones with the biggest budgets. They’re the ones where teachers model problem-solving themselves, where “I don’t know yet” is an acceptable answer, and where challenges are designed to be genuinely challenging. If you’re looking for structured STEM challenges that build computational thinking through hands-on robotics, take a look at our workshop options and see what might work for your school.
