Where game elements fit naturally

In maths, levelled problem sets let pupils work at the right difficulty and see their progress. In science, an investigation can be framed as a mission with stages: predict, test, record, explain. In engineering and computing, design challenges have built-in feedback, because a bridge holds or it does not, and a program runs or shows an error.

Tools such as Scratch, micro:bit and LEGO Education kits give immediate, visible results, which makes them well suited to challenge-based tasks. PhET, the free simulation project from the University of Colorado Boulder, lets pupils change variables and see effects quickly, which works well alongside a points-for-predictions structure.

Keep the reasoning central

Speed rewards can push pupils to guess. In STEM subjects this undermines the skills you want. Award progress for a correct prediction with a reason, for a clear table of results, or for finding and fixing a bug. Encourage teams to explain failed attempts, since these often show the most learning. A short class log of "best failures", where teams record what went wrong and what they changed, makes this habit visible and gives it status.

Mastery checklists also suit STEM well. A list of skills for a unit, such as reading a scale, drawing a line graph or writing a loop, lets pupils tick off each one once they have shown it, so progress reflects what they can do.

Classroom activity: Egg-drop engineering challenge

Ages 11 to 13, two 45-minute lessons, teams of three. Materials: one raw egg per team (or a small water balloon), paper, straws, tape, string and a measured drop point about two metres high.

• Lesson 1, 10 minutes: set the mission and three rules (limited materials, one test drop per round, record every design change).

• Lesson 1, 35 minutes: teams design, build and predict whether the egg will survive, giving a reason.

• Lesson 2, 25 minutes: three test rounds. Teams earn a star for each accurate prediction with a reason and a star for each recorded improvement.

• Lesson 2, 20 minutes: teams present which change made the biggest difference and link it to forces and energy.

Mixed-attainment groups

Rotate roles such as builder, recorder and tester so every pupil contributes. Team scores reduce the pressure on individuals, and shared stars for good recording give credit to pupils whose strengths are in careful observation rather than building. Brief pupils on each role before the challenge begins, so that no one waits for instructions.

Key points

• Frame investigations as missions with clear stages.

• Reward predictions with reasons, careful records and fixed errors.

• Use tools with instant feedback, such as Scratch, micro:bit or simulations.

• Rotate roles so every pupil earns team progress.

Photos: Vitaly Gariev, UK Black Tech / Unsplash