Library
The Cores of Game Design · 11 of 12
The Cores of Game Design
ARG Design CRITICAL

Rules of Thumb — Quick Design Heuristics

The Cores of Game Design Yvens R. Serpa
heuristics rules quick-reference balancing pacing diagnosis

Key Principle

Cross-cutting heuristics distilled from across the book, organized for rapid lookup during design work. Each rule encodes a failure mode the author observed repeatedly in teaching, game jams, and interviews. (Chapters 1-17)

Why This Matters

Designers need fast decision-support during prototyping and playtesting. Returning to first principles for every choice is impractical. These heuristics encode the book's most actionable patterns and guard against its most common failure modes.

Good Examples

  • Diagnose before fixing: When a player struggles, determine whether it is inaptitude (knows what to do, lacks skill) or ignorance (doesn't know what to do). They require opposite responses — graduated repetition vs. teaching. (Chapter 3)
  • Cross-core problem solving: A boring mechanic may need a narrative or aesthetic fix, not a mechanical one. A seashell-collection prototype improved more from a protagonist monologue than from mechanical iteration. (Chapter 2)
  • Fairness over balance: A 1% distribution skew in cosmetic banners is unbalanced but functionally irrelevant. Pursue fairness (subjective appropriateness), not mathematical perfection. (Chapter 8)

Counterpoints

  • "Fun" as design target: Too vague, subjective, and unstable. Designers who target "fun" without specificity produce clone games or fail to sustain engagement. Target a specific emotional experience instead. (Chapter 2)
  • Perfect balance trap: "Perfect balance tends to be a boring experience and takes away the meaning of choice." If all options are equal, none feels worth choosing. (Chapter 10)
  • Universal process: "Applying the same steps in the same order will lead to different results." No single framework works for all games or teams. (Chapter 17)

Key Quotes

"The goal and the reward must be separate elements. The reward is there to give extra motivation to the player, as the goal is going to be achieved anyway." — Yvens R. Serpa, Chapter 3

"Players make economic decisions in games just as they do in real life, which is, to the dismay of many, uninformed, intuitive and irrational." — Yvens R. Serpa, Chapter 10

"Before you consider adding more gameplay elements, consider first improving the juice of the existing gameplay elements." — Yvens R. Serpa, Chapter 15

Rules of Thumb

Process

  • Start from whichever core is strongest for your concept — there is no "correct" entry point
  • Build a complete prototype (one mechanic + one goal) before iterating
  • Change fewer variables per iteration; isolate what you are testing
  • Prefer improvements over additions in late-stage work
  • Planning is prediction, not prescription — plans are disposable, deliberation is not
  • The most crucial point in planning is team stability, not efficiency

Difficulty and Teaching

  • Diagnose difficulty as inaptitude OR ignorance — they require opposite design responses
  • Use the Forced Action Framework for tutorials: Force -> Practice -> Assess
  • First-play moments should be trivially easy by design
  • Mandatory knowledge needs active (in-game) teaching; advanced knowledge can be passive (manuals, wikis)

Economy and Balance

  • Design for fairness (subjective appropriateness), not perfect mathematical balance
  • An economy needs at least two distinct investment paths to produce meaningful choice
  • Test for positive feedback loops — they cause runaway escalation if unchecked
  • Keep economic mechanisms as simple as possible — economy lies in the realm of player ignorance
  • More resources always mean a more complex economy; reuse before adding

Motivation and Pacing

  • Keep GAR cycle elements distinct — conflating goals with rewards kills motivation
  • Balance known and unknown rewards for ethical and experiential reasons
  • Sawtooth difficulty: escalate overall but drop back between peaks for recovery
  • Risk-reward only works when the player chooses whether to accept the risk
  • Reward type must match player motivation, not just challenge magnitude

Aesthetics and Polish

  • Add juice early — audiovisual polish reduces perceived difficulty and maintains motivation
  • Establish mood early to constrain and align all downstream creative decisions
  • Shape language is the lowest-cost, highest-signal visual tool
  • UI polish is strategic investment — it buys forgiveness for small flaws (Aesthetic-Usability Effect)

Narrative

  • All games carry political messages through mechanics — design them consciously
  • Theme provides coherence; message is what mechanics actually communicate
  • Audit tropes deliberately: keep, modify, or subvert — never leave them unexamined

Completion

  • Three-question checklist: Does the game serve its purpose? Is the experience fair? Would I recommend it?
  • If you want to know if your game is good, do not judge it yourself — playtest

Related References