Game-Based Learning Strategies in the Classroom

A worksheet with points and a leaderboard bolted on isn’t game-based learning — it’s gamification, and the two get treated as interchangeable in most staff-room conversations about using games in class. That confusion isn’t harmless: it’s the reason so many “gamified” lessons end up feeling like homework wearing a costume.

In 2003 James Paul Gee catalogued 36 learning principles he found built into well-designed video games. Many of those principles do not depend on a screen. That is the test this week runs: which of them can move into a classroom that has no game engine at all? No programming or game-design experience is needed.

• Monday — you play a short game together, learn the working difference between game-based learning and gamification, and choose three of Gee’s principles as your lens.
• Tuesday — you take a gamified lesson apart and rebuild it as a game-based one.
• Wednesday — you look at games that need no screen — cards, dice, puzzles, role-play — and design your first paper prototype for your own curriculum.
• Thursday — colleagues play your prototype as students while you watch, and you revise it from what you see.
• Friday — you play-test again, fit the activity into your unit, and plan how to try it with your own students.

By Friday you have a tested game-based activity for your own subject, a 20-minute first version that is easy to run, and a plan for trying it with your students within your first two weeks back.

Two ideas are often mixed up. Game-based learning uses a game, or something built like one, as the learning activity itself: learners play, and what they do while playing is what they learn. Gamification takes an existing lesson and adds game elements to it — points, badges, a leaderboard. This week uses those as working definitions, and treats gamification as a tool rather than an enemy: points and badges are sometimes useful, and the week compares them with a game-based rebuild so that you can choose.

The lens for the comparison is James Paul Gee’s 2003 book What Video Games Have to Teach Us About Learning and Literacy, which lists 36 learning principles he found in well-designed video games. Gee was describing how good games teach; he was not writing a rule book for classrooms. So the course does not work through all 36. It picks a short list — for example, learning where mistakes cost little, tasks that stay at the edge of what you can do, and learning by trying something and rethinking it — and asks you to look for those in your own activity. Whether a principle shows up is something you check by watching people play, not something you assume.

Everything is done at a scale a teacher can manage. A first prototype rarely works perfectly, and the week says so: you plan for what to change and what to keep, and you try it with your own students only after colleagues have tested it. Where a screen version would help — a slide deck, a quiz tool such as Kahoot or Socrative, a spreadsheet — you build one round of it on Thursday and check what it needs first: accounts, devices and connection.