DAC 204: Game Design Fundamentals

Sources and References

Primary textbook — Tracy Fullerton, Game Design Workshop: A Playcentric Approach to Creating Innovative Games, 4th ed. (CRC Press). Supplementary texts — Jesse Schell The Art of Game Design: A Book of Lenses; Salen & Zimmerman Rules of Play; Brenda Romero & Ian Schreiber Challenges for Game Designers; Raph Koster A Theory of Fun for Game Design. Online resources — Ian Schreiber “Game Design Concepts” open course; Hunicke, LeBlanc, Zubek “MDA: A Formal Approach to Game Design and Game Research”; MIT Game Lab open materials; DiGRA proceedings.

Chapter 1 — What Is Game Design? Designers and Their Work

Game design is the discipline of crafting the rules, systems, and experiences that shape how people play. A designer’s output is not primarily art, code, or story — although those may be involved — but the structured set of constraints and feedback loops that produce meaningful choices for a player. Tracy Fullerton frames the work as “playcentric”: the designer’s loyalty belongs to the player’s experience, not to any personal vision that ignores what actually happens when a human sits down with the artifact. Jesse Schell offers a complementary definition — a game is a problem-solving activity approached with a playful attitude — which highlights that the designer’s job is to invent problems that are worth solving for their own sake.

Crucially, game design predates digital technology by thousands of years. Chess, Go, mancala, backgammon, and tag are products of design choices, even if no named author can be credited. Sports, too, are designed: the offside rule in soccer, the three-point line in basketball, the tiebreaker in tennis, each was introduced, playtested in the real world, and revised. A course in game design fundamentals emphasizes this continuity because the essentials — rules, goals, conflict, outcome — are identical across media. A designer who can make a good board game has mastered something transferable; digital tools only change the means of implementation.

The designer’s daily work mixes several roles. They are systems architects, deciding how parts interact. They are writers, specifying rules in language precise enough to avoid dispute at the table. They are psychologists, anticipating what players will feel after three turns or thirty minutes. They are anthropologists, watching playtests the way an ethnographer watches a ritual, noting what people actually do rather than what they say they did. And they are editors, cutting mechanics that sound clever in theory but add nothing at the table.

Fullerton emphasizes two habits for aspiring designers. First, play widely and analytically — not only the genres you like, but the ones you avoid, because every game you have never considered is a blind spot in your toolkit. Second, keep a design journal. The most valuable entries are not grand ideas but small observations: a moment when a playtester laughed, a rule that needed to be explained twice, a decision that felt forced because the only reasonable move was obvious. Over years, such notes compose a private library of design intuitions no textbook can supply.

A final point distinguishes design from adjacent crafts. Programmers and artists are evaluated by artifacts — does the code run, does the image look right — while designers are evaluated by behavior: what do players do, and does it match what the designer intended to evoke? Because behavior is emergent, design is inherently empirical. A design is never “finished” on paper; it is only provisional until playtesting confirms or refutes its predictions.

Chapter 2 — Conceptualization and Idea Generation

Students often believe that great designs begin with a flash of inspiration. In practice, the origin of a workable concept is usually mundane: a constraint, a mechanic borrowed from another game, an emotion the designer wants players to feel, or a topic they want to explore. The skill is not waiting for lightning but generating enough candidate ideas that some prove viable under scrutiny.

Fullerton recommends beginning from an experience goal — a short sentence describing what the game should make players feel or do. “I want players to feel the tension of betrayal in a trusted group,” or “I want players to experience the satisfaction of small systems snapping together into a big one,” are examples. Because the experience goal is emotional and behavioral rather than mechanical, it leaves room for many implementations. A designer who starts from “this will be a deck-builder with four resources” has already committed to a shape before knowing what it is for.

Techniques for generating candidate concepts abound. Brainstorming works when treated seriously: set a timer, forbid criticism, demand quantity, record everything, and prune afterward. Mashups combine two familiar games or genres — hidden-role mechanics plus economic trading, tile-laying plus real-time pressure — and examine the frictions that emerge. Theme-first design begins with a subject (migration, gardening, logistics) and asks what verbs best express it. Mechanic-first design begins with an interesting rule (one-time-use cards, simultaneous planning, hidden information that is eventually revealed) and asks what themes fit it. Neither direction is superior; strong designers move fluidly between them.

Brenda Romero and Ian Schreiber’s Challenges for Game Designers treats conceptualization as a skill trained through constrained exercises: design a game with no randomness, design a game using only a deck of ordinary playing cards, design a game about a historical event you did not live through. The constraints serve two purposes. They prevent paralysis by limiting the search space, and they force unfamiliar moves that break habitual patterns.

A trap for beginners is to fall in love with a concept before stress-testing it. Fullerton recommends asking, early and repeatedly: what is the core activity? If you had to describe in one sentence what players will mostly be doing, what would it be? “Making small bets about an opponent’s intentions” is a core activity. “Moving pieces and drawing cards” is not — it is a description of the surface, not the experience. Concepts without a clear core activity tend to bloat when prototyped, because the designer adds features hoping something will feel like the game.

Ideas should also be evaluated against practical constraints. How many players? How long? What components? What audience? A brilliant four-hour strategy game is unsuitable for a course assignment that expects a twenty-minute playtest with strangers. Part of learning to design is calibrating ambition to the scope of what can actually be prototyped, tested, and iterated within available time.

Chapter 3 — Formal Elements of Games: Fullerton’s Framework

Fullerton offers a vocabulary of eight formal elements that describe any game’s structure. These are the load-bearing parts of a design; specifying them makes vague ideas concrete enough to prototype.

Applied to checkers, the formal elements are transparent. Two players, alternating turns, with the objective of capturing or immobilizing the opponent’s pieces. Procedures govern movement and jumping; rules bound which moves are legal and define kinging. Resources are the pieces themselves and the board squares they command. Conflict is direct and zero-sum. Boundaries are the 8x8 board and the agreement to play. The outcome is the player who cannot move losing. Every element is present; none is extraneous.

Applied to soccer, the same framework still fits. Players (eleven on each side), objective (more goals), procedures (kickoffs, throw-ins, corner kicks, time periods), rules (offside, fouls, handball), resources (time, field position, player stamina), conflict (direct and physical over the ball), boundaries (the field, the match duration), outcome (the score at final whistle, or the tiebreaker if needed).

Learning to see these elements in any game is the first practical skill a designer needs. It is what allows you to analyze another designer’s work without being fooled by theme or spectacle, and it is what allows you to specify your own designs precisely enough that a stranger can play them from written rules alone.

Chapter 4 — Dramatic Elements: Premise, Character, Story

Alongside the formal elements, Fullerton identifies dramatic elements: the parts of a design that give the mathematics emotional weight. Two games with the same underlying mechanics can produce very different experiences depending on how their dramatic elements are handled.

The premise is the short, evocative setup that answers “what is this about?” It is not the rules and not the back-story; it is the single sentence that positions the player. “You are rival merchants in a medieval spice market.” “You are stranded explorers rationing supplies in an arctic camp.” “You are animals in a forest preparing for winter.” A strong premise does three things: it clarifies the player’s role, it suggests the kinds of decisions that will matter, and it makes the game easier to learn because players can reason from real-world analogies.

Character is the sense that players (or the entities they control) are distinctive and meaningful. Character can be portrayed by art and text, but it is also enforced by mechanics: if each player has different abilities, starting resources, or objectives, they will experience play through different frames. Asymmetric roles strengthen character because they give each player a specific vantage point. Even in strictly symmetric games, the personality a player brings to choices — aggressive, cautious, opportunistic — can constitute a kind of emergent character.

Story in games is not always an authored narrative. Fullerton distinguishes embedded story, which the designer writes in advance (the campaign, the back-story, the scripted cutscene), from emergent story, which arises from the events of play. A poker table generates emergent story every night: the unlikely bluff, the cold streak, the moment a timid player suddenly raises. Board games like Diplomacy or Battlestar Galactica are prized for the retellings they produce the next day. Designing for emergent story means building systems where consequential, memorable, and shareable events are likely to arise.

A common mistake is to layer heavy narrative scaffolding onto mechanics that do not support it. If a game claims to be about betrayal but players have no real incentives to betray each other, the story fails to emerge and the theme feels pasted on. The opposite mistake is to strip out theme entirely, leaving an abstract system that is mathematically interesting but gives players nothing to hold onto emotionally. Dramatic and formal elements should be designed in conversation with each other, not sequentially.

Chapter 5 — Games as Systems

Once a design moves beyond its initial concept, it is useful to think of it as a system: a set of interrelated parts whose behavior emerges from their interactions. Salen and Zimmerman’s Rules of Play devotes substantial attention to systems thinking, and Fullerton adopts similar vocabulary.

A system has objects (things — pieces, cards, tokens, players), attributes (properties of those objects — a card’s value, a piece’s speed), internal relationships (how objects affect each other), and an environment (the context the system operates in — the table, the players’ minds). Changing any of these ripples through the rest. Raising a card’s cost by one coin seems minor but may completely reshape which strategies are viable, because cost interacts with the whole economy of the deck.

Designers distinguish closed from open systems. A closed system has fixed inputs and outputs — chess, go, and most purely abstract games. An open system interacts with something beyond the rules — player conversation in social deduction games, real-world knowledge in trivia games, physical skill in dexterity games. Open systems are harder to balance but can produce experiences closed systems cannot.

Two ideas from systems thinking recur throughout design practice: feedback loops and emergence.

Positive feedback loops amplify: the winner gets advantages that help them win more. Monopoly famously punishes latecomers because accumulating property yields rents that fund more property. Positive loops can create momentum and climactic endings, but unchecked they cause games to snowball, deciding the outcome long before the final turn. Negative feedback loops dampen: the leader is hindered, the laggard is helped. Mario Kart’s rubber-banding items are a famous example. Negative loops keep races close and maintain hope for losing players, but overdone they can feel unfair to the player who has been playing well. Most good designs balance both, sometimes layering several loops at different scales.

Emergence is the phenomenon where simple rules generate complex behavior no single rule predicts. Go has a handful of rules and is inexhaustible; poker’s value comes not from its cards but from the reading of opponents that the cards enable. Designers cultivate emergence by keeping rules few but consequential, and by ensuring that decisions interact — a move is interesting when it has implications beyond its immediate effect. Rules that produce only isolated outcomes, never combining into patterns, yield shallow games regardless of how many there are.

A useful diagnostic question is: what does the system reward? If the most effective strategy is also the most obvious, the system is not producing interesting decisions. If the most effective strategy is the most boring (turtle and hoard), the system is misaligned with the designer’s experience goal. Balancing a game is, in large part, tuning the system so that the strategies it rewards are the ones the designer wants players to pursue.

Chapter 6 — Chance and Skill: Types of Challenges

All games provide challenges, but they differ in how those challenges are adjudicated. The two poles are chance and skill, though most games mix them.

Skill challenges are ones where a more practiced or clever player reliably outperforms a less practiced one. Chess is extreme: luck plays no role, and a grandmaster will defeat a beginner every time. Skill in turn subdivides into physical skill (reflex, dexterity, precision — darts, table tennis, shooter video games), mental skill (calculation, memory, pattern recognition — chess, Sudoku, crosswords), and social skill (reading and persuading others — poker, Diplomacy, negotiation-heavy Euro games).

Chance challenges introduce randomness: dice, card draws, shuffled tiles, hidden setup. Randomness serves several functions. It generates variety, so repeated plays do not repeat identically. It creates drama, because moments of uncertainty produce stronger emotions than determined ones. It levels the field, giving weaker players a real possibility of winning and stronger players the need to adapt. And it enables input and output randomness distinctions, explored by designers like Geoff Engelstein: input randomness sets up a situation the player then reasons about (draw a tile, then decide where to place it), while output randomness resolves a player’s chosen action uncertainly (attack and roll for damage). Input randomness tends to feel fair and strategic; output randomness can feel like the game punishing correct decisions.

The blend of chance and skill shapes who enjoys a game. Pure skill games appeal to players who want mastery and dislike losing to factors outside their control. Pure chance games appeal to players who want a light social experience where nobody can be blamed. Mixed games broaden the audience: Catan’s dice rolls create variance that lets less-experienced players compete, while its trading and building decisions reward experienced ones. The mix also affects pacing — randomness creates punctuation, decisions create rhythm.

Beyond chance and skill, Fullerton and others recognize additional categories of challenge. Puzzle challenges have a correct solution and test the player’s ingenuity in finding it. Strategic challenges require long-term planning in the face of incomplete information and opposing intent. Tactical challenges involve short-term positioning and maneuver. Economic challenges are about managing scarce resources across time. Exploration challenges reward discovery of the space. Creative challenges reward imagination and expression. Most games combine several, and part of analyzing an existing game is noticing which kinds dominate and how they interlock.

A final note on difficulty. Raph Koster’s A Theory of Fun argues that fun in games is the sensation of learning — of a pattern clicking into place. If a challenge is too easy, the pattern is already learned and the game feels boring. If too hard, the pattern refuses to resolve and the game feels frustrating. Good difficulty curves move players along the edge where they are always recognizing new patterns. Designers achieve this by layering mechanics (introducing one new wrinkle at a time), scaling opposition, and providing clear feedback so that players can tell whether they are succeeding.

Chapter 7 — The MDA Framework

Hunicke, LeBlanc, and Zubek’s 2004 paper “MDA: A Formal Approach to Game Design and Game Research” introduced a three-level model that has become standard vocabulary. MDA stands for Mechanics, Dynamics, Aesthetics.

Mechanics are the rules and components at the designer’s level of specification: the cards in the deck, the legal moves, the numerical values, the victory conditions. Mechanics are what a designer writes down.

Dynamics are the runtime behaviors that emerge when players engage with the mechanics: what strategies become viable, what tempo the game settles into, what situations arise repeatedly. Dynamics are not specified directly; they are consequences of mechanics interacting with players. A deck of cards and a shuffle produce the dynamics of bluffing, hand-management, and lucky streaks.

Aesthetics are the emotional responses the dynamics evoke: tension, triumph, camaraderie, surprise, frustration, catharsis. Aesthetics are what players actually experience and what they remember. The MDA authors propose a preliminary taxonomy of eight aesthetics: sensation (game as sense-pleasure), fantasy (game as make-believe), narrative (game as drama), challenge (game as obstacle course), fellowship (game as social framework), discovery (game as uncharted territory), expression (game as self-discovery), and submission (game as pastime). This list is not exhaustive but gives designers a vocabulary for talking about what they want players to feel.

The power of MDA lies in recognizing that designers and players traverse these levels in opposite directions. Designers begin with an aesthetic goal, invent dynamics that would produce it, and then build mechanics that would generate those dynamics. Players encounter the mechanics first, experience the dynamics as they play, and only afterward articulate — if at all — the aesthetics they enjoyed. This mismatch explains many design failures. A designer who specifies mechanics without reasoning about what dynamics they will produce is working blind. A designer who insists on a beloved mechanic despite its yielding dynamics that contradict the aesthetic goal is defending the wrong level of the model.

MDA also clarifies that balancing, tuning, and playtesting operate primarily at the dynamics layer. The question is rarely “is this rule correct?” — rules are just specifications — but “what happens when people play?” When playtesting reveals that a dynamic is wrong, the fix is usually a mechanical change, but it might also be a change in presentation, context, or player communication.

A lightweight complement to MDA is Schell’s elemental tetrad: every game can be seen as composed of mechanics, story, aesthetics (in the sensory sense), and technology. These four interact, and a good design ensures none dominates at the expense of the others. Combined with MDA, the tetrad reminds designers that narrative and presentation are not afterthoughts but co-equal design surfaces.

Chapter 8 — Narrative Design

Narrative in games occupies an unusual position. Unlike novels or films, where the author fully controls the sequence of events, games must accommodate player agency. A story that unfolds identically regardless of what the player does reduces the game to a delivery mechanism for a pre-written narrative; a story that bends entirely to player whim risks incoherence. Narrative design is the craft of finding productive middle grounds.

Several structures are widely used. Linear narratives present a fixed sequence of events, with gameplay serving as the transport between beats. Most early computer adventures and many modern cinematic games take this form; they maximize authorial control but minimize player agency over outcome. Branching narratives give players choices that lead to different paths, usually converging at key points to keep production costs manageable. Emergent narratives arise from systemic play, as discussed in Chapter 4; here the designer sets up conditions from which memorable events can arise but does not script them. Environmental storytelling conveys narrative through the state of the world — what the ruined room implies about what happened there — without requiring the player to experience events in order.

Non-digital games lean heavily on emergent and environmental techniques because they cannot easily store branching text or scripted cutscenes. The back of a board game box sets premise and tone; the artwork on cards and the flavor text embed hints of a larger world; and the events that unfold over play generate the stories players actually tell afterward. When a designer of a non-digital game wants stronger authorial narrative, they can use devices like scenario cards that introduce events at intervals, chapter breaks that alter the rules part-way through, or campaign play across multiple sessions where state persists.

Character design in games also operates differently from in other media. Because players sometimes inhabit characters and sometimes direct them, character must be legible and memorable rather than psychologically intricate. Strong game characters tend to have a few striking traits that distinguish them from other characters, visible goals, and abilities or limits that players immediately grasp. In cooperative games, asymmetric roles function as character: each player’s distinctive abilities give them a perspective and a niche, which invites both identification and social dynamics (who is the healer, who is the scout).

A recurring pitfall is ludonarrative dissonance: the mismatch between what a story tells players and what the mechanics ask them to do. A game that narrates its protagonist as a merciful hero while requiring the player to mow down hundreds of enemies for experience points is preaching one thing while practicing another. Beginners often write elaborate premises and characters into games that mechanically ignore them. The remedy is to audit mechanics against theme: is each rule consistent with what the premise promises?

Designers who want to study narrative in games should look beyond game-industry sources to writing craft in general, and in particular to interactive fiction, theater, and tabletop role-playing games, where narrative and agency have been negotiated for decades.

Chapter 9 — Player Psychology and Player Types

A design is not finished until it meets players, and players are not uniform. Two people with the same game can have opposite experiences because they approach it with different motives, tolerances, and habits. Designers benefit from frameworks that help anticipate this variation.

Richard Bartle’s 1996 essay “Hearts, Clubs, Diamonds, Spades: Players Who Suit MUDs” remains the most cited typology. Studying players of text-based multi-user dungeons, Bartle proposed four broad categories defined by what players find rewarding:

Achievers want to accomplish the game’s explicit objectives. They collect points, complete quests, unlock achievements, and optimize their builds. They are the players who read strategy guides and compare times. A game that fails to give Achievers clear goals and measurable progress bores them.

Explorers want to understand the game’s systems and spaces. They enjoy discovering what a rule can do, finding hidden corners, experimenting with unusual combinations. They are the players who read the manual cover to cover before the first turn. A game that is too linear or whose systems are opaque frustrates them because there is nothing to probe.

Socializers want to use the game as a pretext for interaction with other people. They care less about winning than about the laughs, alliances, and betrayals at the table. They are drawn to party games and games that reward conversation. A game too absorbing for chat, or too abstract for banter, fails them.

Killers want to impose themselves on other players. This is not necessarily violent; it is the pleasure of direct competition, of outwitting a specific opponent, of being the cause of another player’s frustration or respect. Killers push Achievers to improve, give Explorers meaningful obstacles, and push Socializers to take sides. Games without opportunities for direct player-versus-player interaction leave them unsatisfied.

Bartle plotted these types on two axes — acting on versus interacting with, and the world versus other players — yielding the four categories as quadrants. Most players are mixtures, and the same person may shift between types across games or even across sessions.

Subsequent researchers have proposed more elaborate models. Nick Yee’s empirical work on massively multiplayer online game players, for example, identified three broad components — achievement, social, immersion — each with sub-dimensions. Quantic Foundry’s more recent analyses identify twelve motivation dimensions. For the purposes of a beginning designer, though, Bartle’s four remain practical precisely because they are simple enough to use while prototyping. Before a playtest, ask: is there something in my game for each type?

Player psychology also includes understanding flow, Mihaly Csikszentmihalyi’s concept of the state of absorbed engagement that arises when challenge and skill are matched. Games that are too easy produce boredom; too hard, anxiety. A well-paced difficulty curve, with occasional lulls for recovery, aims to keep players near flow for most of their session. Related concepts include intrinsic motivation (playing for the activity itself rather than external reward), self-determination theory (competence, autonomy, and relatedness as basic psychological needs that games can satisfy), and the magic circle (Johan Huizinga’s and later Salen and Zimmerman’s notion that games create a temporary social space in which ordinary rules are suspended).

Finally, designers should be aware of negative patterns. Games can exploit rather than serve players: compulsion loops that reward without meaning, manipulative monetization, social pressure used to force engagement. A playcentric designer holds players’ long-term wellbeing in view, not only their short-term engagement metrics. This ethical stance is not an add-on; it is part of treating design seriously.

Chapter 10 — The Iterative Design Process

Game design is iterative by necessity. Because a design’s behavior emerges only when it is played, and because emergence is hard to predict from rules alone, the only reliable way to develop a game is to build something rough, try it, learn from what happened, and revise. Fullerton centers her entire book on what she calls the playcentric iterative cycle.

The cycle has several phases, typically presented as a loop:

Conceptualize — articulate an experience goal, brainstorm mechanics and themes, and write a short design document.

Prototype — build a playable version as quickly as possible. The first prototype is usually ugly, incomplete, and full of placeholders; its purpose is to make the design testable, not to impress.

Playtest — put the prototype in front of players. Watch carefully, take notes, ask targeted questions afterward.

Evaluate — analyze what happened. Did the dynamics match the aesthetic goal? What broke? What was boring? What surprised you?

Revise — change the design in response. Add, cut, adjust, and return to prototyping.

The crucial discipline is speed. Beginners often spend weeks polishing a prototype before testing, which means their first piece of feedback is delayed and their revisions have more sunk cost to defend. Fullerton urges the opposite: make the roughest possible prototype, test it within days, and expect to throw much of it away. The games that emerge from many fast cycles outperform those that come from few slow ones.

Iteration also applies at multiple scales. Macro iteration revises the overall design — swapping out major mechanics, changing player count, reframing the premise. Micro iteration tunes numbers and edges — raising a cost, clarifying a rule, adjusting a card. Early iterations should be macro, because changing details is wasteful while fundamentals are still unstable. As the design stabilizes, iterations become increasingly micro.

A common failure mode is the death spiral, in which each playtest reveals problems, each revision introduces new ones, and the designer loses faith. The usual cause is that the design lacks a clear core activity — the designer keeps trying to fix symptoms rather than diagnose the underlying mismatch between what the game does and what it is supposed to feel like. The remedy is to return to the experience goal and ask whether the design, as a whole, can plausibly reach it. Sometimes it cannot, and a designer’s hardest but most valuable decision is to abandon a concept and start another.

The opposite failure is premature polish: spending time on art, written rules, and production quality while the underlying game is still unfinished. Polish is for stabilizing good designs, not for compensating for weak ones. An elegant rulebook for a dull game is wasted labor.

Experienced designers track iteration through a design journal, recording each playtest, each change, and each hypothesis. Over time the journal becomes both a memory aid and an evidence base: when a question arises about why something is the way it is, the journal recalls which version failed and why.

Chapter 11 — Playtesting

Playtesting is where designs meet reality. The purpose is not to confirm the designer’s preferences but to learn what actually happens when people play. Good playtesting is a skill that must be practiced with intention.

Fullerton distinguishes several kinds of playtests, each appropriate at a different stage:

Internal or self-playtesting: the designer plays the game alone, often simulating multiple players. Useful for catching obvious rule failures and dead ends, but limited because the designer cannot be surprised by their own game.

Playtesting with trusted colleagues: the designer plays with friends, classmates, or other designers. These testers are more forgiving and better at discussing design, which helps early when the rules are still unstable.

Playtesting with target audience: the designer gives the game to players who resemble the intended audience, ideally strangers who have no personal stake in the designer’s feelings. This is the most revealing kind of test. Players who do not know the designer will not try to spare them.

Blind playtesting: testers are given the rules and components with no explanation from the designer. If they cannot learn the game from the materials alone, the rules need work. Blind playtesting is essential before publication or final submission, because it reveals which parts of the design live only in the designer’s head.

Several techniques improve what the designer learns from a playtest. Observe, do not coach. If players misread a rule, the designer’s instinct is to correct them, but the mistake itself is data: the rule is unclear. Let the misinterpretation run if it will not ruin the session, and note it. Prepare questions in advance. General questions (“did you like it?”) produce bland answers. Specific questions (“did the third round feel longer than the first?” “when were you most engaged?” “when were you confused?”) produce actionable ones. Watch faces and body language. Players often say the game was fine when their expressions during play said otherwise. Record turn-by-turn notes of what happened, what was said, and what felt off. After the session, reconstruct the play while it is fresh. Debrief honestly. Thank testers; ask what they remembered most; ask what they would tell a friend about the game.

A subtle point is the difference between what players say and what players do. Players often verbalize generous praise even for games they would not voluntarily play again. They also offer solutions (“you should add a card that does X”) that may not fit the designer’s goals. The productive response is to treat complaints and suggestions as symptoms — “something is wrong here” — and to diagnose the underlying problem yourself rather than adopting the prescription literally.

Quantitative data complements observation. Tracking win rates across strategies, turn durations, how often certain actions are used, and how often players complete objectives can reveal imbalance that intuition misses. In non-digital games, this often means counting from notes rather than collecting telemetry, but the principle is the same.

Finally, a playtest is a social occasion. Testers are donating their time and attention. Designers owe them clarity about what is expected, warmth during the session, and gratitude afterward. A reputation for running good playtests attracts willing testers; a reputation for defensive arguments with testers repels them.

Chapter 12 — Prototyping Non-Digital Games

A prototype is a working approximation of a design: enough game to be played, not yet enough to be pretty. For non-digital games, prototyping is especially inviting because the tools are cheap and the iteration cycle can be measured in hours rather than weeks.

The essential supplies are ordinary. Index cards and sticky notes serve as cards, tiles, and event markers. A sharpie and a stack of blank cards can become almost any deck. Dice, counters, pennies, beads, or bits from other games serve as tokens. A large sheet of paper becomes a board. A notebook holds the rules. Even a game intended for commercial production begins this way, because the purpose of the first prototype is not to look like the final product but to let the designer test the underlying system.

A few practical principles guide non-digital prototyping.

Make components fungible. Write on cards in pencil, or use cards that can be reshuffled and relabeled. If a card’s cost changes, you want to update it in seconds, not remake the deck. The faster it is to change, the more willing you will be to try alternatives.

Scale down first. A game that is supposed to be played with a hundred cards and twenty tokens may be prototyped with twenty cards and five tokens. Scale introduces its own problems, but they are easier to diagnose once the core dynamics are known to work at small scale.

Strip out theme temporarily. Use abstract labels like “red card” and “blue token” rather than “fire elemental” and “mana crystal.” Theme can distract from whether the underlying system is interesting. Once the system works, reintroduce theme to test its fit.

Playtest early and often. A prototype you have not played is worthless. A rule you have not written down may change between sessions without your noticing. The first playtest should happen as soon as possible — sometimes within hours of the initial sketch. Many beginners resist because the prototype feels embarrassing, but embarrassment fades and the information gained does not.

Expect to throw it away. The first prototype’s purpose is to be surpassed. Later prototypes incorporate what you learned. A design’s fourth prototype is often unrecognizable from its first, which means that polishing the first was wasted effort. Keep everything rough until the shape is stable.

Write the rules as you go. A game is its rules, and a game whose rules only live in the designer’s head cannot be blind-tested. Writing the rules clearly is itself a design exercise: it surfaces ambiguities and forces decisions you have been postponing.

Isolate variables. When a playtest reveals a problem, change one thing at a time in response. Changing three things and retesting tells you nothing about which change helped.

Use paper prototypes even for digital games. Many successful video games began as non-digital prototypes because the designers wanted to test their core systems without spending programming time. If a mechanic is not fun with paper and pencils, code will not save it. Conversely, if the paper version is already compelling, the digital version has a foundation to build on.

A final word on the attitude that distinguishes productive prototyping from unproductive tinkering. Productive prototyping is hypothesis-driven: “I think X will feel tense because of Y, and I’m building this to find out.” Unproductive tinkering is feature-driven: “wouldn’t it be cool if the game also had Z?” The first mode generates evidence that improves design judgment. The second mode generates complexity that has to be removed later. A designer who can keep asking “what am I trying to learn?” rather than “what can I add?” will develop faster than one who cannot.

Closing Notes

Game design as a discipline rewards breadth. The designer must think like a mathematician about systems, like a playwright about character and premise, like a psychologist about motivation, like an engineer about components, and like an ethnographer at playtests. The skills compose rather than compete: understanding formal elements sharpens your eye for dramatic ones; understanding player types sharpens your observation during playtesting; understanding iteration sharpens every other phase of the work.

What makes a course on fundamentals valuable is that these ideas are portable. Whether you go on to design board games, sports, classroom activities, training simulations, digital experiences, or something that does not yet have a name, the questions are the same. Who plays? What do they do? What constrains them? What do they want? What tests tell you whether the answers you gave are right? A designer who keeps asking those questions, and who treats playtesting as the arbiter rather than their own preference, can develop meaningful games in any medium. The rest — the polish, the production, the marketing — grows out of the soil those fundamentals prepare.

The most practical advice with which to close is Fullerton’s: make a game this week. Not an elaborate one, not a perfect one, but a playable one, with rules on paper and pieces on a table, and get three people around it before the week ends. Then write down what you learned. Do this repeatedly and the craft will come. Read every book on the reading list and make nothing, and it will not.