Checklist Download

Learning Game Design Series, Part 7: Thinking About the Learning and Then the Game

I am a firm believer that most games teach. However, not all games are explicitly designed to be learning games. If your intention is to create a learning game that achieves specific learning outcomes for the players, then you have to think about the learning before you begin crafting the game design.

Learning First Then Game Design

So far, I’ve covered two steps of the five-step process I advocate for getting started in learning game design.  Today we’ll focus on the third step.

  1. Play games and evaluate what you play. (One post)
  2. Get familiar with game elements and how to use them. (Three posts)
  3. Think about the learning design – and then the game design.
  4. Dump ADDIE – and go agile instead.
  5. Playtest, playtest, playtest.

It’s critical to have a strong understanding of game goals, core dynamics, game mechanics, and game elements—but that understanding doesn’t guarantee you a learning game if you don’t also have solid instructional design skills. Why? Because an effective learning game requires a solid instructional goal and learning objectives, as well as a clear understanding of the backgrounds and preferences of the target audience for the game.

The phrase “learning game” says it all—you are creating games that help people learn. What distinguishes a serious game from a commercial game is its intention to help people learn something specific. Players will either know something or be able to do something as a result of playing the game. In many instances, there may be attitudinal adjustments you’re seeking as well.

Questions You Need to Answer Before Designing Any Game

As part of our Play to Learn learning game design workshop (being offered at DevLearn 2013 in October and in Indy next week), Karl Kapp and I put together a checklist of questions learning game designers need to answer before starting on game design. Here are the questions, which are pretty straightforward needs analysis kind of stuff:

What is the business need that is driving the use of a learning game?

  • A need to increase sales or to support the launch of a new product?
  • Customer complaints or ineffective customer service?
  • A need to comply with gov’t regs?
  • Quality issues?
  • Safety issues?
  • A need to build knowledge or skill on a business-critical process?
  • Something else? What is it?

After playing this game, what will learners be able to DO in their jobs? (This should be your instructional goal).

  • As part of achieving the instructional goal, what do learners need to know, do, and believe? (These statements convert into your game’s learning objectives.)

Want the full checklist? Enter your name and email below to receive a free PDF version.


Use the checklist to guide your own game design efforts. In my next post (which covers Step 4, Dump ADDIE. Go agile instead) I’ll show you one of our design documents for a game, along with several iterations of the game so you can see the transformation that takes place from prototype to finished product. The instructional goal and the learning objectives are the drivers for this iterative process so you have to nail down the learning goal and objectives FIRST.

6 replies

Trackbacks & Pingbacks

  1. […] I am a firm believer that most games teach. However, not all games are explicitly designed to be learning games.  […]

  2. […] “ I am a firm believer that most games teach. However, not all games are explicitly designed to be learning games.”  […]

  3. […] “ I am a firm believer that most games teach. However, not all games are explicitly designed to be learning games.”  […]

  4. […] I am a firm believer that most games teach. However, not all games are explicitly designed to be learning games.  […]

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>