Game Design

Game design is the craft of inventing the rules, systems, and experiences that make a game work.

10 frameworks, from 1824 to today · Game Studies & Design · Games

still a working view ended · each leads to its entry below

Overview

Game design is the craft of inventing the rules, systems, and experiences that make a game work1. A game designer decides what players can do, what constrains them, what rewards them, and what the whole thing feels like moment to moment1. The field matters because games are among the most complex cultural artifacts humans make: a single commercial game can contain thousands of interlocking rules, and a small change to one number can transform how millions of players behave. The history of game design is the history of how practitioners learned to think about those interlocking parts—first as hobbyists and tinkerers, then as a recognized profession with its own vocabulary, methods, and schools of thought.

Precursors: Wargames, Puzzles, and the First Rulebooks

Before there were video games, there were designed games whose makers wrote down their reasoning. The nineteenth-century Prussian Kriegsspiel—a wargame using dice, maps, and a referee—was designed to train officers in decision-making, and its refinement by the von Reisswitz family in the 1820s established that a game's rules could be engineered for a purpose. In the twentieth century, hobby wargaming produced designers who thought explicitly about simulation: Avalon Hill's Tactics II (1958) and its successors sold rules systems as products, and their designers debated realism versus playability in magazines like The General.

Puzzle design developed its own lineage. Sam Loyd and Henry Dudeney built careers in the late nineteenth century on mechanical and mathematical puzzles, and the puzzle's core design principle—a solvable problem with a satisfying "aha"—became a staple of later game design. The crossword puzzle, launched in the New York World in 1913, showed that a designed information structure could become a mass pastime.

The Arcade and the Birth of the Video Game Designer

When video games emerged in the 1960s and 1970s, their makers were often programmers first2. Nolan Bushnell's Computer Space (1971) and Pong (1972) were designed by engineers who discovered, through trial and error, that simple rules and immediate feedback could hold attention. Pong's design was almost accidental—the game's difficulty and pacing were tuned by observing players in bars—but it established a principle that would define the field: the designer's job is to shape the player's experience, not just the machine's behavior.

The arcade era produced the first recognizable design auteurs. Toru Iwatani designed Pac-Man (1980) around the idea of eating and being chased, deliberately aiming for a non-violent game that would appeal to women—a design goal stated explicitly by its maker. Shigeru Miyamoto's Donkey Kong (1981) introduced character, narrative framing, and a sequence of distinct screens, showing that a game could be designed as a progression of experiences rather than a single loop. These designers worked without formal training; they learned by making games and watching players.

Systems and Simulation Design

The 1980s and 1990s saw designers increasingly think of games as systems—interlocking rules whose interactions produce emergent behavior. Will Wright's SimCity (1989) was a landmark: a game with no win condition, in which the player manipulates variables (taxes, zoning, infrastructure) and watches a simulation respond. Wright described his approach as building a "possibility space" rather than a scripted experience. Sid Meier's Civilization (1991) applied similar systemic thinking to history, and the "one more turn" feeling became a design goal in itself.

Simulation design drew on earlier traditions: flight simulators, management games like Hamurabi (a 1968 text game), and the tabletop wargaming heritage. The key insight was that a well-designed system could generate stories and challenges without a designer authoring every moment. This idea—that the designer builds the machine and the player discovers what it does—became central to the field.

Teaching Through Play

A parallel tradition concerned games as learning environments. The Oregon Trail (1971, later widely distributed in schools) was designed by student teachers to teach history and decision-making, and it became one of the most-played educational games ever made. In the 1980s and 1990s, edutainment titles like Where in the World Is Carmen Sandiego? (1985) tried to make learning a game mechanic rather than a wrapper. The design challenge was consistent: how do you make the learning itself the source of fun, rather than a reward for enduring it? Designers learned that immediate feedback, clear goals, and a sense of progress—the same principles that make entertainment games work—could be applied to teaching, though the tension between educational rigor and engagement remained unresolved.

Narrative and Puzzle Design

Adventure games of the 1980s, from Infocom's text adventures to LucasArts' Maniac Mansion (1987), made puzzle design a central craft. Designers like Ron Gilbert articulated principles for fair puzzles: the player should have enough information to solve a problem, and solutions should feel inevitable in retrospect. The "puzzle dependency chart"—a diagram mapping how puzzles unlock one another—became a standard design tool.

Narrative design evolved alongside. Early adventure games told stories through text and static images; later games like Myst (1993) used environmental storytelling and integrated puzzles into a coherent world. The 2000s brought debates about whether games could tell stories with the sophistication of novels or films, and designers experimented with branching narrative, dialogue systems, and player-authored stories. The puzzle and narrative traditions converged in genres like the immersive sim, where multiple solutions to a problem are designed in advance.

Player Psychology and Motivation Design

As games reached mass audiences, designers became increasingly interested in why players keep playing. The 2000s saw the rise of explicit psychological frameworks. Nicole Lazzaro's research on player emotions identified distinct categories of fun—hard fun, easy fun, serious fun, and people fun—and designers used such models to tune experiences. The concept of "flow," borrowed from psychologist Mihaly Csikszentmihalyi, described the state of absorbed engagement that occurs when challenge matches skill, and designers used it to calibrate difficulty curves.

The most influential and controversial framework was the "player types" model from Richard Bartle's 1996 analysis of MUD (multi-user dungeon) players, which categorized players as achievers, explorers, socializers, and killers. Though later researchers questioned its universality, it gave designers a vocabulary for thinking about different motivations. The 2010s brought behavioral economics into design: variable rewards, loss aversion, and streaks were analyzed and sometimes deliberately exploited, prompting ethical debates that continue today.

Playtesting and Iterative Design

The most fundamental methodological shift in game design was the rise of playtesting as a core practice. Early designers tested games informally—watching players in arcades or at trade shows—but by the 1990s, studios like Valve and Blizzard institutionalized playtesting, observing players behind one-way glass and revising designs based on what they saw. The principle was simple: designers cannot predict how players will experience a game, so they must watch and iterate.

This iterative approach—build a prototype, test it, revise, repeat—became the dominant design methodology. It drew on earlier traditions in software development and industrial design, but game designers adapted it to the specific challenge of designing for play. The "vertical slice"—a small, fully polished section of a game used to test whether the core experience works—became a standard milestone. Playtesting revealed that players often behave in ways designers never anticipated, and the best designers learned to design for those behaviors rather than against them.

Mechanic-First Prototyping

Alongside iterative testing grew a philosophy of prototyping around mechanics rather than themes or stories. Designers like those at indie studios in the 2000s and 2010s argued that the core mechanic—the fundamental action the player repeats—should be fun before anything else is added. Tetris (1984), designed by Alexey Pajitnov, was a pure mechanic: falling blocks, rotation, line-clearing. Its designer had no theme in mind; the game's appeal came entirely from the interaction of simple rules.

The mechanic-first approach led to "game jams"—time-limited events where designers build small games around a prompt—and to rapid paper prototyping, where designers test rules with cards and tokens before writing code. The approach also shaped the indie game movement, where small teams could afford to explore a single mechanic deeply rather than build large content pipelines.

Social and Live-Service Design

The rise of online games in the 2000s and 2010s created a new design problem: how to design for communities that persist over time. World of Warcraft (2004) and its successors showed that social systems—guilds, raids, economies—could be designed as deliberately as combat mechanics. Designers learned to manage player behavior through incentives, to design for group dynamics, and to build content that could be updated continuously.

The "live-service" model—games designed to be updated and monetized over years—became dominant in the 2010s. Designers now had to think about retention curves, seasonal content, and monetization systems alongside traditional game design. The field developed new specializations: economy designers, progression designers, and community managers. The ethical questions multiplied: when does a retention mechanic become manipulation? When does a monetization system exploit rather than serve?

The Present: A Profession with Many Schools

Game design today is a global profession with distinct traditions. The Japanese console tradition emphasizes tight control of player experience and character-driven design. The Western PC tradition emphasizes systems, simulation, and player agency. The indie scene emphasizes experimentation and personal expression. Mobile design emphasizes accessibility and short-session engagement. These traditions borrow from one another constantly, and designers move between them.

The field's core methods—playtesting, iterative prototyping, mechanic-first thinking, systems design—are now taught in university programs and practiced in studios worldwide. The open questions are substantial: how to design games that are ethical as well as engaging; how to design for diverse audiences without flattening experience; how to reconcile artistic ambition with commercial pressure; and how to understand the long-term effects of games designed to be played for thousands of hours. The history of game design is, in many ways, the history of learning to take play seriously as a designed experience—and the field is still working out what that responsibility entails.

References

  1. Game design (introduction, Game designer), Wikipedia
  2. Video game design, Wikipedia

The frameworks of Game Design

Each framework is a way of working the field has used: when it held, and the question it answers.

  1. 1824-1995

    Wargame and Simulation Design Tradition

    How can rules simulate a real system for training?

    Fly to its tower in Nousfarer

  2. 1880-Present

    Adventure and Puzzle Design

    How do you build a fair, satisfying solvable problem?

    Fly to its tower in Nousfarer

  3. 1971-Present

    Educational game

    How can a game make learning itself fun?

    Fly to its tower in Nousfarer

  4. 1971-1985

    Golden age of arcade video games

    What simple rules hold a player's attention?

    Fly to its tower in Nousfarer

  5. 1987-Present

    Narrative Design

    How can games tell stories through play?

    Fly to its tower in Nousfarer

  6. 1989-Present

    Systems and Emergence Design

    How do interlocking rules produce emergent behavior?

    Fly to its tower in Nousfarer

  7. 1990-Present

    Playtesting and Iterative Design

    How do designers learn what players actually experience?

    Fly to its tower in Nousfarer

  8. 1996-Present
  9. 2000-Present
  10. 2004-Present

How the ideas connect

Each arrow runs from an earlier idea to the later one it shaped. The list below says what passed between them.

Wargame and Simulation Design Traditi…Adventure and Puzzle DesignEducational gameGolden age of arcade video gamesNarrative DesignSystems and Emergence DesignPlaytesting and Iterative DesignPlayer Psychology and Motivation Desi…Mechanic-First PrototypingSocial and Live-Service Design

Beyond the field

Where Game Design's ideas came from in other fields, and what they led to there: the strongest 12 of 52 links.

A city in Nousfarer: a red-carpeted stair climbing terraces to a crowned tower on an acropolis, more towers round it, forest and snowy mountains beyond.
A city in Nousfarer, the game played in the browser.

Game Design is a planet in Nousfarer

Its city has a tower for each of these 10 frameworks. Land, walk in, and climb one concept at a time.

Land on Game Design

Related fields

Fields its ideas are linked to

More in Game Studies & Design

See where Game Design sits on the Map of Human Knowledge