Good problem solving activities for students make the reasoning audible. At a bomb, each module becomes a four-step problem: observe what is there, look up the matching rule, decide what it means, then act. Because one student sees the bomb and others hold the rules, every step has to be spoken, and a skipped step shows up as a strike.
What problem solving activities for students practise that worksheets miss
Problem solving activities for students practise something worksheets rarely reach: reasoning with other people, live, when the facts are incomplete and a wrong move has a cost. A worksheet problem sits still and waits. A live problem changes, needs information from someone else, and punishes a confident guess.
On a worksheet, a student reads a problem that contains everything they need. They can reread it, skip it and come back, or work backwards from the answer at the back of the book. Most of the reasoning happens silently, so a teacher sees only the final answer and has to guess where things went wrong.
A bomb round in Bomb Appétit, a free co-op browser game, puts the problem in two places at once. The Defuser sees a bomb covered in modules, which are small puzzles. The Experts hold the manual with the rules, but they cannot see the bomb. Neither side can solve a module alone, so each step of the reasoning is said out loud across the table.
That gives a teacher something rare: a recording, in effect, of every step. You can hear when a student observed carefully, when they looked up the wrong rule, when they decided too early and when they acted before checking. The debrief then talks about steps, not about who was "good at it".
It also teaches students that a problem can be solved by a group in which nobody holds all the facts, which is closer to how most real problems arrive.
Problem solving inside one module: observe, look up, decide, act
Inside one module, problem solving runs in four steps. Observe: the Defuser says what is on the module and the edgework. Look up: an Expert finds the right list in the manual. Decide: the Expert reads down the list and stops at the first line that is true. Act: the Defuser repeats the instruction and does it.
Each step has a typical failure:
- Observe fails when the Defuser describes only part of what is there, or when nobody asked about the edgework (the labels on the casing: serial number, batteries, indicators and ports).
- Look up fails when the Expert opens the wrong page or the wrong list on the page.
- Decide fails when the Expert stops at a line that looks right instead of reading from the top.
- Act fails when the Defuser acts before saying the instruction back.
Worked example: the Big Button (invented values)
The values and rules below are invented for this example. A real manual's rules depend on its rule seed, so read your own page.
The Big Button page in the manual describes a single button with a color and a word on it. The Experts decide whether the Defuser should tap it (press and release in under half a second) or hold it. The page lists rules from the top; the first true line wins, and an "Otherwise" line catches everything else. If the answer is hold, a colored strip lights up beside the button, and a table on the page gives a digit for each strip color. The Defuser lets go when the countdown shows that digit in any position.
| Step | Who speaks | What they say (example) |
|---|---|---|
| Observe | Defuser | "Big Button. It's blue. The word on it is HUSH. Edgework: two batteries, a lit indicator, serial ends in four." |
| Observe | Expert 1 | "Blue, HUSH, two batteries, one lit indicator. What are the indicator's letters?" |
| Observe | Defuser | "The letters on the lit one are…" (reads them, letter by letter) |
| Look up | Expert 2 | "Big Button page. One list, read from the top." |
| Decide | Expert 2 | "Line one: the button is red. No. Line two: more than two batteries. No, two is not more than two. Line three: the button is blue. Yes. Hold the button." |
| Act | Defuser | "Hold the button. Holding. The strip is yellow." |
| Look up | Expert 2 | "Strip table. Yellow is five." |
| Decide | Expert 1 | "Let go when any digit on the timer is a five." |
| Act | Defuser | "Let go on a five. Waiting… letting go now." |
Notice where the work happens. Expert 2 reads each line and says "yes" or "no" aloud, so the whole group can follow and Expert 1 can catch an error. "Two is not more than two" is a small point that many students miss. Saying it aloud is how the group catches it.
How do students solve a problem when no one has all the facts?
Students solve a problem with split facts by asking for what they lack before trying to decide. The Experts list the facts their rule needs, ask the Defuser for each one, and only then read down the list. Split information changes problem solving from "think hard" into "find out first, then think".
In a normal classroom problem, the facts are on the page and the work is reasoning. At the bomb, half the work is gathering facts from someone who does not know which ones matter. The Defuser cannot tell which details are important, because they cannot see the rules. The Experts cannot see the details, because they cannot see the bomb.
That teaches three habits:
- Name what you need. An Expert who says "I need the count, the colors from the top and the last digit of the serial number" gets a better answer than one who says "tell me about the wires".
- Gather before you judge. Reading the rule list before the facts are complete leads to stopping at the wrong line.
- Check the source. If a fact looks odd, ask again. "You said six wires?" costs two seconds.
A useful variation is to give the Experts different pages. The manual itself suggests splitting pages so that two Experts never search for the same thing. Then the group must also decide who should be asked, which adds another layer of coordination.
Is time pressure good for student problem solving?
Some time pressure helps student problem solving because it gives a reason to organise the steps, but too much makes students guess. Start with a mission that has generous time per module, such as First bite, which gives five minutes for one module, and add pressure only once the steps are steady.
The timer in Bomb Appétit counts down for the whole bomb. Mistakes count as strikes. Each strike makes the timer run faster: by a quarter after the first and by half after the second. On most missions the third strike sets the bomb off. The bomb also goes off if the timer reaches zero.
That design rewards careful work. A student who takes ten seconds to check the edgework has lost ten seconds. A student who guesses and earns a strike has made every remaining second shorter. The guide to why time attack games punish guessing more than slowness works through that trade-off in detail.
For a class, think of time pressure as a dial:
- Low: First bite (one module, five minutes) and Button up (two modules, five minutes).
- Medium: Strange symbols (three modules, five minutes) and Table for three (three modules, four minutes).
- High: Quick snack (four modules, four minutes) and the longer missions in later sections.
Move up the dial only when a group can run all four steps without being reminded.
The problem solving mistake: guessing to beat the timer
The main problem solving mistake at the bomb is guessing to save time. A student sees the clock, skips a step, and acts on a hunch. The guess either works, which teaches them to guess again, or earns a strike, which speeds the timer and leaves less time for everything else. Over a round, guessing nearly always costs more.
Guessing tends to appear in three places:
- Skipping observe. "It's probably the usual." The Expert assumes a fact rather than asking.
- Stopping early in decide. The Expert reads the first line that seems close and stops, without checking the lines above it are false.
- Acting without the repeat. The Defuser hears half an instruction and moves.
The fix is a short, fixed script for each step, which the think-aloud sheet below provides. Once the script is a habit, it becomes faster than guessing because nobody stops to argue about what was said.
Choice of module also matters. A group that starts on the hardest module tends to guess more. The post on the eleven regular modules explains which modules a new Expert should learn first, and starting there keeps the early rounds about method rather than survival.
Student problem solving think-aloud sheet
A think-aloud sheet gives each student a sentence to say at each of the four steps. Print it and put it beside the manual. The sentences are examples: students can change the wording, but they should say something at every step, so the group always knows where the reasoning is.
| Step | Defuser says (example) | Expert says (example) |
|---|---|---|
| Observe | "Module: [name]. I see [count] [things]. From the top: [details]." | "I need [fact], [fact] and [fact]. Tell me [fact]." |
| Look up | "Ready when you are." | "I'm on the [module] page, the list for [count]." |
| Decide | (waits) | "Line one: [condition]. Yes or no? … First true line: [rule]." |
| Act | "You want me to [action]. Doing it now." | "Yes, [action]." or "Stop. Let me check." |
| After a strike | "That was a strike. What did I describe?" | "Let's go back to observe." |
Use the sheet for the first two rounds, then take it away and see whether the steps stay. Many groups keep the "Line one, yes or no" habit without being told, because it works.
After the round, the reflection questions for students after a bomb round help students look back at which step went wrong. For a club that wants to practise these steps every week, see after school club ideas built on a bomb defusal club. And for a tour of what each module asks, the bomb defusal puzzle game guide to the 11 modules is the place to start. The standard manual is free to open or print.