GDnD Wiki

GDnD Wiki

This site is for Ulster University students and staff. Enter the class access password to continue.

MDA Framework

7 min read

Summary

MDA (Mechanics, Dynamics, Aesthetics) is a formal framework for game design analysis proposed by Robin Hunicke, Marc LeBlanc, and Robert Zubek (2004). It breaks a game into three interacting layers and argues that designers and players access those layers from opposite directions. This asymmetry is the framework’s central insight and its most practically useful idea.

(Hunicke, LeBlanc & Zubek, MDA, see source-mda)

The three layers

Mechanics

“Mechanics describes the particular components of the game, at the level of data representation and algorithms.” — Hunicke, LeBlanc, Zubek (source-mda)

Mechanics are the formal rules, components, and procedures — the coded logic at the lowest level. In MDA, “Mechanics” is narrower than Schell’s usage (see elemental-tetrad): it refers to the specific data representations and algorithms, not to the broader category of “what players can do.”

Examples: the exact collision detection parameters; a damage formula; the rules governing turn order; shuffling and trick-taking in a card game. (CRE342 Lectures, see source-cre342-lectures)

Dynamics

“Dynamics describes the run-time behavior of the mechanics acting on player inputs and each others’ outputs over time.” — Hunicke, LeBlanc, Zubek (source-mda)

Dynamics are not designed directly — they emerge from the mechanics when players interact with them. A designer specifies mechanics and attempts to predict what dynamics will result; the gap between intended and actual dynamics is where most design problems live.

Examples from the paper:

  • Card games: shuffling + trick-taking mechanics → bluffing dynamics
  • Shooters: weapon + spawn point mechanics → camping and sniping dynamics
  • Monopoly: property accumulation mechanics → rich-get-richer feedback loop dynamics

Aesthetics

“Aesthetics describes the desirable emotional responses evoked in the player, when she interacts with the game system.” — Hunicke, LeBlanc, Zubek (source-mda)

In MDA, aesthetics are emotional responses — not visual or audio presentation (which is how Schell uses the word). The paper identifies eight aesthetic categories:

#AestheticDescription
1SensationGame as sense-pleasure
2FantasyGame as make-believe
3NarrativeGame as drama
4ChallengeGame as obstacle course
5FellowshipGame as social framework
6DiscoveryGame as uncharted territory
7ExpressionGame as self-discovery
8SubmissionGame as pastime

Important vocabulary clash: Schell’s “Aesthetics” = sensory presentation (visuals, audio, feel). MDA’s “Aesthetics” = emotional response categories. These are different uses of the same word — be explicit when cross-referencing. (see foundational-vocabulary)

Aesthetic examples from the paper

GamePrimary aesthetics
CharadesFellowship, Expression, Challenge
QuakeChallenge, Sensation, Competition, Fantasy
The SimsDiscovery, Fantasy, Expression, Narrative
Final FantasyFantasy, Narrative, Expression, Discovery, Challenge, Submission

Most games pursue multiple aesthetics in varying degrees. There is no grand unified formula — the taxonomy helps designers describe and target experiences deliberately.

The asymmetry: designer vs. player

The framework’s core insight:

Designers work forwards: design Mechanics → which produce Dynamics → which produce Aesthetic experiences.

Players encounter games backwards: they experience Aesthetics first → discover Dynamics through play → rarely see Mechanics directly at all.

Designer perspective:  Mechanics → Dynamics → Aesthetics
Player perspective:    Aesthetics ← Dynamics ← Mechanics

“From the designer’s perspective, the mechanics give rise to dynamic system behavior, which in turn leads to particular aesthetic experiences. From the player’s perspective, aesthetics set the tone, which is born out in observable dynamics and eventually, operable mechanics.” — Hunicke, LeBlanc & Zubek (source-mda)

This asymmetry has a critical implication: a mechanic that seems elegant in design may produce unanticipated dynamics, which may produce the wrong aesthetic. The only way to close this gap is playtesting — observing what dynamics actually emerge and what aesthetics players actually experience.

Games as artifacts, not media

“Games are more like artifacts than media. By this we mean that the content of a game is its behavior — not the media that streams out of it towards the player.” — Hunicke, LeBlanc & Zubek (source-mda)

This is MDA’s philosophical foundation. Books, films, and music stream content toward a passive audience. Games produce behaviour through interaction — the content is the interaction. This positions games alongside physical artefacts (tools, toys, instruments) rather than alongside broadcast media.

This distinction aligns with Poole’s argument that interactivity is the essential defining property of games (see player-agency, games-vs-film).

The Monopoly example

The paper uses Monopoly to demonstrate MDA at work. The rich-get-richer feedback loop (a dynamics phenomenon) undermines dramatic tension and player investment (aesthetics) late in the game:

Roll dice → Move → Pay rent → Losers pay more → Winners gain more → Gap widens → Players disengage

Proposed mechanic-level fixes:

  • Subsidies/bonuses for lagging players
  • Taxes or penalties for wealthy players when passing Go or exercising monopolies
  • Time pressure mechanics (resource depletion, doubled payouts) to speed differentiation

Each fix operates at the mechanics level but is motivated by the aesthetic goal (sustained dramatic tension).

MDA vs. Schell’s Elemental Tetrad

Compatible but distinct frameworks with overlapping vocabulary:

ConceptMDASchell (Tetrad)
MechanicsNarrow: specific rules and data structuresBroad: all player-facing rules and procedures
AestheticsEmotional response categories (fun types)Sensory presentation: visuals, audio, feel
DynamicsRuntime emergent behaviourNot a distinct layer (subsumed into Mechanics or Emergence)
Story/TechnologyNot separated outExplicit Tetrad elements

When reading game-design literature, clarify which framework is being used whenever “mechanics” or “aesthetics” appears. The vocabulary collision between these two texts is a frequent source of confusion.

(see elemental-tetrad)

In practice

As a design tool: Specify target aesthetics first (what emotional experience should this mechanic produce?), then reason about what dynamics would support those aesthetics, then specify mechanics to produce those dynamics.

As a diagnostic tool: When something feels wrong, MDA gives vocabulary. Is it a mechanics problem (the rule is wrong)? A dynamics problem (the rule is right but produces unexpected emergent behaviour)? Or an aesthetics problem (the dynamics are as intended but the emotional response is wrong)?

As a communication tool: The eight aesthetic categories give teams a shared vocabulary for design goals. “This level should feel like Discovery and Sensation, not Challenge” is more actionable than “this level should be fun.”

Relationship to Sellers’ systems framework

Sellers (Advanced Game Design, 2018) uses MDA as a reference point but works at a level below MDA — specifically within the mechanics layer. Where MDA takes “mechanics” as an atomic concept, Sellers decomposes mechanics into parts (state, boundaries, behaviours) and loops (reinforcing and balancing), providing a formal language for designing mechanics rather than merely categorising them.

The two frameworks are complementary:

FrameworkPrimary useLevel of abstraction
MDAAnalysing design goals; diagnosing mismatches between intent and experienceHigh — mechanics → dynamics → aesthetics
Sellers’ systems modelDesigning and debugging mechanics; modelling emergent behaviourLow — parts → loops → wholes

Sellers also deepens the MDA dynamics layer: where MDA notes that dynamics emerge from mechanics but provides limited guidance on predicting or designing for that emergence, Sellers’ causal loop diagrams and systems thinking tools provide practical methods for modelling emergence before the game is fully built.

Second-order design (Sellers) extends the MDA asymmetry: designers work in the mechanics layer; the dynamics they produce are not fully predictable even to themselves; the aesthetics players experience emerge from dynamics the designer did not fully anticipate. This is the systemic argument for why the designer-player asymmetry is not a failure of communication but an inherent property of emergent design.

(Sellers, Advanced Game Design, see source-advanced-game-design, second-order-design, systems-thinking)

Open questions

  • The eight aesthetics were proposed without empirical validation. Are they exhaustive? Is “Competition” (mentioned in passing in the Quake example) a ninth aesthetic?
  • MDA focuses on designed intent vs. player experience. How does it handle emergent communities, metagames, and player-generated content?
  • The dynamics layer is the least directly designable. Are there better tools for predicting emergent dynamics from mechanic specifications before playtesting? (Sellers argues causal loop diagrams partially address this.)

Graph View

Backlinks