Library
The Art of Game Design: A Book of Lenses · 6 of 14
The Art of Game Design: A Book of Lenses
ARG Design CRITICAL

Implementation Playbook

The Art of Game Design: A Book of Lenses Jesse Schell
implementation workflow process design-methodology

Key Principle

The full design process, synthesized across the book, follows a bottom-up sequence: start from the essential experience, build through the elemental tetrad, unify around a theme, prototype the riskiest unknowns first, and iterate relentlessly with playtesting. Every step is governed by diagnostic lenses and filtered through eight simultaneous constraints. The process is not linear -- it is a loop executed as many times as schedule permits. The designer's job throughout is to listen deeply to five sources -- team, audience, game, client, and self -- and to commit quickly, observe honestly, and reverse fast when wrong (Ch. 1, Ch. 8).

Why This Matters

Without a structured process, designers default to building what they know how to build rather than what the game needs. They start from story instead of fantasy, polish before prototyping, and skip playtesting out of emotional avoidance. Schell's methodology exists to counteract these natural tendencies. "The more times you test and improve your design, the better your game will be" (Ch. 8) -- the entire process is engineered to maximize the number and quality of iteration loops.

A structured workflow also resolves team alignment. When everyone understands the sequence -- essential experience first, then mechanics, then story layered on top -- peripheral team members make aligned decisions independently. Without it, individuals optimize their own domain (art, engineering, writing) at the expense of the whole (Ch. 5, Ch. 6).

Good Examples

Wii Sports Baseball: The team identified the essential experience as "swinging the bat" (Ch. 2). Nine innings, base-stealing, and fielding were cut. The subtractive process -- driven by a named essential experience -- produced a focused game that outsold complex baseball simulations. This illustrates Steps 1-2: define the experience, then cut everything that does not serve it.

Pirates of the Caribbean: Battle for Buccaneer Gold: Theme was "the fantasy of being a pirate" (Ch. 6). Every design decision -- modified 3D glasses renamed "Eyes of Bluebeard," ship's wheel controller, pneumatic motion, sea-breeze AC vents -- was evaluated against this theme. Enemy ships used collusion (Ch. 18): they attacked players then fled toward interesting content, guiding players organically. This illustrates Steps 3-5: unify around theme, use indirect control, and let every element serve one coherent experience.

GTA's "Build the Toy First": Before layering on missions and narrative, the team built "a living, breathing city that was fun to play" (Ch. 8). The toy -- driving around a reactive city -- was validated before the game was designed on top of it. David Jones: "GTA came from Pac-Man. The dots are the little people." This illustrates Step 4: validate the interactive foundation before adding goal structures.

Counterpoints

Starting from story (top-down design): The Pixie Hollow case -- designers built activities from movie plot. Focus groups rejected everything because the fantasy (being a fairy) demanded flying as the primary action, not story-derived tasks. "If ever you find yourself saying 'we can't do that... it goes against the story,' story has tricked you, trapped you, and taken over your game." (Ch. 17)

Skipping prototyping: The naive "start building and hope" approach discovers fatal problems after months of investment. Psychologically, designers gravitate toward parts they feel confident about rather than facing the scariest problems first. Risk-first prototyping -- building small tests for each potential project-killer -- is the antidote (Ch. 8).

Avoiding playtesting out of fear: "The primary reason playtesting doesn't happen early or often enough is not logistics -- it's the designer's fear that people will not like their game." (Ch. 28) This fear manifests as delays, excuses, and distractions. The antidote is frequency: WUBALEW -- "When Useful, But At Least Every Week."

Analysis paralysis and over-planning: "Game design is not a set of principles, it is an activity." (Introduction) Designers who study endlessly and ship nothing never enter the iteration loop where all quality is produced. "Your first ten games will suck -- so get them out of the way fast." (Introduction)

Key Quotes

"The Rule of the Loop: The more times you test and improve your design, the better your game will be." — Jesse Schell, Chapter 8

"Don't fall in love with your solution. Fall in love with your problem." — Jesse Schell, Chapter 7

"Ideas are not like fine china, ideas are like paper cups -- they are cheap to manufacture." — Jesse Schell, Chapter 8

"It seems that perfection is reached not when there is nothing left to add, but when there is nothing left to take away." — Saint-Exupery, quoted Chapter 13

Rules of Thumb

  • Step 1 — Define the Essential Experience: Ask "What must the player feel?" not "What must the game contain?" (Ch. 2, Lens #2). Name it explicitly. This becomes the evaluation standard for every subsequent decision.
  • Step 2 — Frame as a Problem Statement: "How can I create [experience] for [audience] on [platform]?" Calibrate breadth -- too narrow embeds assumptions, too broad prevents evaluation (Ch. 7).
  • Step 3 — Build the Toy First: Before adding goals, rules, or win conditions, validate that the core interaction is fun on its own (Ch. 8). If the toy is not fun, no game structure will rescue it.
  • Step 4 — Choose a Unifying Theme: Experience-based ("fantasy of being a pirate") or truth-based ("war changes a world"). Every element must reinforce it. Use Lens #11: "What is my theme? Am I using every means possible to reinforce it?" (Ch. 6)
  • Step 5 — Sketch the Elemental Tetrad: Map initial ideas across Mechanics, Story, Aesthetics, and Technology. Check each element separately, then check interactions (Ch. 5).
  • Step 6 — Identify and Attack Risks First: List everything that could kill the project. Build small, ugly prototypes targeting each risk. Paper prototyping works even for real-time games -- Halo used graph paper and a metronome (Ch. 8). Prototype ugliness is a feature: polish hides problems and discourages honest feedback.
  • Step 7 — Iterate Through the Eight Filters: Every design pass must satisfy: artistic impulse, demographics, experience design, innovation, business, engineering, social/community, and playtesting. A fix in one filter can break another (Ch. 8).
  • Step 8 — Playtest Relentlessly (WUBALEW): Watch faces, not screens. Use the FFWWDD protocol (Frustrating, Favorite, Wanted, Wand, Doing, Describe). Stay alert for "the second what" -- observations you did not anticipate (Ch. 28).
  • Step 9 — Balance by Doubling and Halving: Change values by 2x, not 10%. You need to feel the difference to learn from it. Half of development time should be spent balancing (Ch. 13).
  • Step 10 — Apply the 50% Rule: Design so the game ships even if half the budget is cut. All core gameplay should be fully playable at the schedule's halfway mark (Ch. 8).
  • Throughout — Listen to Five Sources: Team, audience, game, client, and self. "The most important skill for a game designer is listening." (Ch. 1)
  • Throughout — Use Lenses as Diagnostic Tools: No single lens is sufficient. Triangulate across many. "Good game design happens when you view your game from as many perspectives as possible." (Introduction)
  • Throughout — Monitor Passion: Passion is the subconscious signaling excitement about the design. Its absence indicates something has gone wrong even when rational analysis has not identified the problem. If passion is lost, either find it again or consider abandoning the project (Ch. 8).
  • Throughout — Prefer Elegance Over Addition: When something feels wrong, ask "what should I remove?" before "what should I add?" Count the purposes each element serves; if an element does not serve at least two, cut it (Ch. 13).

Related References