Rules of Thumb

Key Principle

This is a collection of the most actionable heuristics from across The Art of Game Design: A Book of Lenses by Jesse Schell, organized thematically. Each rule is a decision-shortcut distilled from the book's frameworks, examples, and hard-won lessons.

Why This Matters

Designers face hundreds of micro-decisions daily. Full framework analysis is not always possible in the moment. These rules of thumb encode the book's deepest patterns into quick-reference form — punchy enough to recall under pressure, grounded enough to produce good outcomes. They are not substitutes for the lenses, but they are what the lenses reduce to when you need to move fast.

Good Examples

On Experience

Design the feeling, not the feature. The product is an experience, not a game. Every element must answer: "What must the player feel?" (Ch. 2)
Fun = Pleasure + Surprise. If it's pleasant but not fun, diagnose surprise deficit. (Ch. 4)
Whoever must play cannot play. The moment engagement becomes obligation, play becomes work. (Ch. 4, Santayana)
Simplicity + Transcendence. Successful game worlds combine a world simpler than reality with powers greater than normal. (Ch. 17)

On Mechanics and Balance

If it's not fun, add triangularity. Low-risk/low-reward vs. high-risk/high-reward. Eight of ten "not fun" prototypes are missing this. (Ch. 13)
Elegance = purposes per element. Count them. If an element serves fewer than two purposes, cut it. (Ch. 13)
When balancing, double or halve — never adjust by 10%. You need to feel the difference to learn from it. (Ch. 13, Sid Meier)
Variable rewards beat fixed rewards. A 1/3 chance of 30 points sustains longer than a guaranteed 10. (Ch. 13)
Reframe punishment as reward. Same mechanic, opposite frame, vastly different reception. (Ch. 13)
Information asymmetry is the cheapest design lever. Changing who knows what transforms a game more than changing the rules. (Ch. 12)
Emergence ratio = strategic actions / basic actions. High ratio means depth. Low ratio means add combinatorial possibility, not more content. (Ch. 12)

On Iteration and Process

The Rule of the Loop: More iterations = better game. No exceptions. (Ch. 8)
Commit fast, observe honestly, reverse fast. Ideas are paper cups, not fine china. (Ch. 8)
Attack the scariest risk first. Build targeted prototypes for your biggest unknowns, not the parts you feel confident about. (Ch. 8)
Build the toy before the game. Validate that the core interaction is fun without goals. Then layer game structure on top. (Ch. 8)
Plan to cut 50%. All core gameplay should be fully playable at the schedule's halfway mark. (Ch. 8)
Prototype ugly on purpose. Polish hides problems and discourages honest feedback. (Ch. 8)
You are in preproduction until you have two publishable levels. Only then do you know enough to schedule. (Ch. 8, Mark Cerny)

On Inspiration and Ideas

Fall in love with your problem, not your solution. (Ch. 7)
Competitors can copy your moves but never your inspiration. Draw from outside games. (Ch. 7)
Record every idea immediately. The subconscious offers more when it knows you're listening. (Ch. 7)
Brainstorm alone first, then combine. Groups of max 4, after individual ideation. (Ch. 7)

On Story and Worlds

Design bottom-up: Fantasy > Action > Economy > World > Story. Starting from story traps you. (Ch. 17)
If someone says "we can't — it goes against the story," story has taken over your game. (Ch. 17)
Accessibility beats accuracy. The audience's mental model, not physics, determines what feels right. (Ch. 17)

On Interface and Presence

If players say "the character won't..." instead of "I can't...", the interface is broken. First-person projection requires invisible interface. (Ch. 15)
Juiciness: more response to the same input. A game that feels lifeless often has a feedback deficit, not a mechanics deficit. (Ch. 15)
The more primal the interaction, the less tutorial it needs. If an animal could do it, you're tapping evolutionary depth. (Ch. 15)
Small and rich beats big and shallow. Especially in VR — rich object interaction over vast empty worlds. (Ch. 22)

On Teams and Clients

"What problem are you trying to solve?" The single question that resolves most bad suggestions from clients. (Ch. 30)
Leave design ambiguity for the builders. Overfleshing kills ownership. The people closest to each section fill in details best. (Ch. 26)
Who eats lunch together reveals trust patterns. If disciplines eat separately, expect pipeline problems. (Ch. 26)
Players start for the game, stay for the community. Community extends the "period of contagion" that drives viral growth. (Ch. 25)

On Business

Barriers to entry determine profitability more than game quality. High-barrier markets: ~90% profitable. Low-barrier: ~90% lose money. (Ch. 32)
Frame monetization as heroic, not transactional. Sell adventures that yield rewards, not the rewards directly. (Ch. 32)

Counterpoints

Elegance vs. Character: Pure elegance produces sterile systems. Mario being a plumber serves no function but gives the game its soul. Balance efficiency with personality. (Ch. 13)
Freedom vs. Experience: True freedom makes designed experiences impossible. The feeling of freedom is what matters, not actual freedom. (Ch. 18)
Story first is a trap: Even Pixar chose plastic toys because their rendering technology demanded it — not because the story came first. No element is inherently primary. (Ch. 5 endnote)
Fidelity vs. Learning: A flawed simulation can teach better than a perfect one, because exploiting loopholes provokes the question "why doesn't this work in reality?" (Ch. 33)
Save systems kill drama: Irreversibility, not narrative quality, creates dramatic weight. Time-travel (save/reload) destroys tragedy. (Ch. 17, endnotes)
Removing a dominant strategy feels bad but is good. The disorientation is a false signal — the game got harder to reason about, which is what makes it interesting to play. (Ch. 13)

Key Quotes

"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

"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

"If you give a good idea to a mediocre group, they'll screw it up. If you give a mediocre idea to a good group, they'll fix it." — Ed Catmull / Pixar, quoted Chapter 26

The master list, compressed for rapid scanning:

Experience: Design feelings, not features | Fun = Pleasure + Surprise | Mandatory fun is not fun Mechanics: Add triangularity when stuck | Count purposes per element | Change who knows what before changing rules Balance: Double or halve, never 10% | Variable > fixed rewards | Reframe punishment as reward Iteration: More loops = better game | Commit fast, reverse fast | Attack scariest risk first | Ugly prototypes only Inspiration: Love your problem | Steal from outside games | Record every idea | Brainstorm solo first Story: Build bottom-up (fantasy first) | Accessibility > accuracy | Story is cheapest to change, so don't protect it Interface: Invisible = working | Juiciness = response richness | Primal = intuitive Teams: Ask "what problem are you solving?" | Leave room for builders | Trust = lunch proximity Business: Barriers > quality for profit | Frame transactions as adventures Purpose: Is making this game worth my time? (Lens of the Raven, Ch. 35)

Related References

The Lens Methodology and Essential Experience - Core framework these rules operationalize
The Rule of the Loop and Iteration - Process for applying these rules
Game Balance and Economy - Detailed balance principles behind the mechanics heuristics
Indirect Control and Player Freedom - Methods for guiding players without removing freedom