Mechanics, dynamics, aesthetics

Why it matters

Everyone can say whether they liked a game. A designer has to say why, and then change the right thing. "The combat feels boring" is not something you can fix directly; "enemies always attack one at a time, so players never have to choose a target" is. A shared framework turns vague feelings into causes you can work on.

The most widely taught framework is MDA, from a 2004 paper by Robin Hunicke, Marc LeBlanc and Robert Zubek. It splits a game into three layers.

The three layers

The key insight is the direction of each view:

• The designer builds mechanics, hoping they create certain dynamics, which create the aesthetics they want.
• The player experiences the aesthetics first, notices some dynamics, and may never think about the mechanics at all.

So you design from the aesthetic you want back down to the mechanics that might produce it, then test whether it actually happens.

Naming aesthetics precisely

"Fun" is too vague to design for. The MDA paper lists eight kinds of fun, which give you better words:

• Sensation: the game as sense-pleasure (sound, visuals, game feel)
• Fantasy: make-believe, being someone else
• Narrative: the game as drama
• Challenge: an obstacle course to master
• Fellowship: a social framework, playing together
• Discovery: uncharted territory to explore
• Expression: self-discovery and creativity
• Submission: a relaxing pastime

Most games target two or three of these. A cosy farming game leans on submission, expression and fantasy; a competitive fighting game leans on challenge and fellowship.

Worked example: why does tag work?

Analyse playground tag with MDA.

• Mechanics: one player is "it"; touching another player makes them "it"; there is a play area.
• Dynamics: players keep their distance from "it", taunt from just out of reach, and team up loosely to distract "it". "It" picks the slowest or nearest target and tries to corner people.
• Aesthetics: challenge (escaping), fellowship (laughing together), sensation (running).

Now change one mechanic: "it" must hop on one foot. The dynamics shift (players get bolder, taunting increases) and the aesthetics shift too (less tension, more comedy). One small rule changed the whole experience. That is the MDA loop in action.

Worked example: a design problem

A team's dungeon game is meant to feel tense (challenge), but playtesters say it feels like a chore. Work backwards:

1. Aesthetic missing: tension.
2. Dynamic observed: players fully clear every room, heal to full and move on. There is never a risky decision.
3. Mechanic causing it: healing potions are plentiful and resting is free.
4. Change to try: make resting cost a resource or advance a danger timer.

The fix is in the mechanics, but you found it by starting from the aesthetic.

Common mistakes

• Describing only mechanics. A feature list is not a design. Always ask what dynamic each rule creates and what players feel as a result.
• Assuming dynamics. You cannot be sure what players will do until you watch them. MDA is a way to form hypotheses that playtests confirm or reject.
• Targeting every aesthetic. A game that tries to be relaxing, punishing and story-heavy at once usually does none of them well. Choose.
• Treating MDA as the only lens. It is a starting vocabulary. Later frameworks add story, technology and context, but the core idea of rules -> behaviour -> feeling stays useful.

Quick recap

• Mechanics are rules you write, dynamics are behaviour that emerges, aesthetics are feelings players have.
• Designers work from aesthetics back to mechanics; players experience them the other way round.
• Name aesthetics precisely (challenge, discovery, fellowship...) instead of "fun".
• Small mechanical changes can change dynamics and aesthetics completely, so test every change.