Skip to content

Learning Mechanic

Element · All elements
Evidence · 1 claim (1 for) · 1 study (1 theoretical), q2 · 0 of 1 report an effect size · 1 claim rests on one study

Description

A game mechanic is what a game lets you do — "the various actions, behaviors and control mechanisms afforded to the player within a game context" (Hunicke, LeBlanc, & Zubek, 2004, p. 3), or more narrowly the core mechanic, "the essential play activity players perform again and again and again" (Salen & Zimmerman, 2003, p. 316). A learning mechanic is the same idea asked of the learning, and Plass and colleagues define it in deliberate parallel:

Learning mechanics are patterns of behavior or building blocks of learner interactivity, which may be a single action or a set of interrelated actions that form the essential learning activity that is repeated throughout a game.

The distinction this element exists to make is that a learning mechanic is not itself playable. It is a design pattern — a meta-mechanic, in Christopher Alexander's sense of a general solution to a recurring problem — that has to be instantiated as a concrete game mechanic before anyone can play it. "Apply rules to solve problems" is a learning mechanic. Flinging objects at targets, dragging them into place, or jetpacking them across a screen are three game mechanics that could each instantiate it. The relationship is one-to-many, and the choice among instantiations is a design decision with consequences for what actually gets learned.

That separation is what makes the common failure diagnosable. When a learning game bolts a popup quiz onto a racing or shooter mechanic, the game has a game mechanic and a question, not a learning mechanic — the essential repeated activity is still racing, and the learning is an interruption of it. Designers interviewed by Isbister, Flanagan and Hash (2010) made the same point from the practitioner's side: learning has to be embedded in the core mechanic rather than added to an existing one. Game play cannot be a reward for answering questions about facts, and factual quizzes cannot be forced into unrelated game play. See Learning Embedded in the Core Mechanic for the design principle and the three requirements that follow from it.

The worked example in the source is Noobs vs. Leets, a middle-school geometry game built at the Games for Learning Institute around the angle rules in the Grades 6–8 common core — complementary, supplementary, opposite, and sum-of-angles-in-a-triangle. Its learning mechanic is apply rules to solve problems: the learner selects among rules and indicates which problems each applies to. That mechanic was chosen over the obvious alternative — type the missing angle — precisely because it keeps the repeated activity at the conceptual level of the rules rather than at the level of arithmetic, which is where the learning goal lives.

Design Implications

Context

Requirements

  • Grounded in learning theory. The source is explicit that this is the first criterion, not a nicety: a learning mechanic is derived from the learning sciences, and the examples given are Cognitive Flexibility Theory (Spiro et al., 1988), Cognitive Apprenticeship (Collins, 1988), Anchored Instruction (CTGV, 1990–1993), and Situated Learning (Lave, 1988; Lave & Wenger, 1990). Noobs vs. Leets draws on Schoenfeld's account of mathematical problem solving, Lave's situated learning, and schema theory.
  • A theoretical model of the interactivity itself, not just of the content. The source points at the INTERACT model, which separates behavioral, cognitive and emotional interactivity and relates them through feedback and guidance (Domagk, Schwartz, & Plass, 2010).
  • Repetition. The definition turns on repeated throughout a game — a one-off activity is a level, not a mechanic.
  • Learner-generated solutions. Where the subject matter admits different but equally appropriate answers, the mechanic should let the learner generate their own rather than select from the designer's.
  • A game mechanic that preserves the goal. Instantiation is where learning mechanics are usually lost; see the principle page for the three requirements a candidate game mechanic has to meet.

Constraints

  • A learning mechanic does not describe a tool. It says the learner should be able to apply rules to solve problems; it says nothing about whether that is flinging, dragging, or jetpacking. Designers looking for buildable specifications will find the abstraction frustrating, and that abstraction is the point — it is what allows one mechanic to be reused across games.
  • Player agency has to survive. The tension between the player's agency and the game's rule system is what makes a game worth playing; a learning mechanic that removes choice removes the reason to play.
  • Not every instantiation is equally valid. Each game mechanic that could instantiate a given learning mechanic may only be suitable under specific conditions, and which conditions can often only be settled empirically.
  • "Fun and engaging" is not the bar. When a game is designed with the explicit goal of facilitating learning, the mechanics have to go beyond engagement and engage players in a meaningful learning activity — engagement is necessary and nowhere near sufficient.

Target Learners

  • Learners for whom the target performance is a repeated decision rather than a recalled fact — the definition's insistence on repetition means the mechanic has to be worth doing many times
  • Learners whose difficulty is conceptual rather than procedural, where a mechanic that surfaces the reasoning step is worth more than one that collects the answer
  • Learners who can be given genuine choice within the rule system without the goal being lost

Target Learning Goals

Affordances

  • Game-based Learning — the learning mechanic is the unit that makes a game's mechanics carry the learning rather than surround it
  • Immediate Feedback — feedback mechanisms are how a mechanic guides behaviour, and how the designer communicates what actions should and should not be taken

Claims

Examples

  • Apply rules to solve problems (Noobs vs. Leets): the learner selects among the angle rules and indicates which problems each applies to, keeping the repeated activity at the level of the rules rather than at the level of subtraction.
  • Candidate instantiations of that one mechanic, all considered by the G4LI team: the Fling mechanic from Angry Birds, the Drag mechanic from Implode!, and the Bounce mechanic from Doodle Jump. The one-to-many relationship is what a library of mechanics is for.
  • A counter-example, named as such by the source: an established racing or shooter mechanic with a popup question gating the next round. The learning is an addendum to the mechanic, not the mechanic.
  • The G4LI library of learning mechanics — an ongoing catalogue pairing each learning mechanic with the game mechanics that can instantiate it, published for designers to draw on.

Key Sources

  • Plass, J. L., Homer, B. D., Kinzer, C., Frye, J., & Perlin, K. (2011). Learning mechanics and assessment mechanics for games for learning (G4LI White Paper #01/2011, Version 0.1). Games for Learning Institute (New York University, CUNY Graduate Center, Teachers College Columbia University). researchgate.net/publication/272815253
  • Isbister, K., Flanagan, M., & Hash, C. (2010). Designing games for learning: Insights from conversations with designers. CHI '10 Extended Abstracts on Human Factors in Computing Systems, 2041–2044. doi:10.1145/1753326.1753637
  • Domagk, S., Schwartz, R. N., & Plass, J. L. (2010). Interactivity in multimedia learning: An integrated model. Computers in Human Behavior, 26(5), 1024–1033. doi:10.1016/j.chb.2010.03.003
  • Kirschner, P. A., Sweller, J., & Clark, R. E. (2006). Why minimal guidance during instruction does not work: An analysis of the failure of constructivist, discovery, problem-based, experiential, and inquiry-based teaching. Educational Psychologist, 41(2), 75–86. doi:10.1207/s15326985ep4102_1
  • Schnotz, W., Böckler, J., & Grzondziel, H. (1999). Individual and co-operative learning with interactive animated pictures. European Journal of Psychology of Education, 14(2), 245–265. doi:10.1007/bf03172968
  • Hunicke, R., LeBlanc, M., & Zubek, R. (2004). MDA: A formal approach to game design and game research. Proceedings of the Challenges in Game AI Workshop, 19th National Conference on Artificial Intelligence (AAAI '04). AAAI Press.
  • Salen, K., & Zimmerman, E. (2003). Rules of play: Game design fundamentals. MIT Press.
  • Bogost, I. (2008). The rhetoric of video games. In K. Salen (Ed.), The ecology of games: Connecting youth, games and learning (pp. 117–140). MIT Press.
  • Alexander, C. (1977). A pattern language: Towns, buildings, construction. Oxford University Press.
Page metadata
Field Value
type element
id learning-mechanic
title Learning Mechanic
description The repeated learner-facing activity at the heart of a game for learning — a design pattern, grounded in learning theory, that a concrete game mechanic instantiates without displacing the learning goal.
status review
canonical True
generated by claude/unspecified on 2026-09-03
trust unverified — no one has confirmed this page's content
sources 5 — plass-et-al-2011, kirschner-2006, schnotz-1999, domagk-2010, isbister-2010

Frontmatter is the page's machine-readable record — see the Schema & Guide.