Summary
Player-centric game design is the philosophy, developed by Ernest Adams and others, that the designer’s primary obligations are to the player: first, to entertain them (duty to entertain), and second, to imagine every design decision from the player’s perspective (duty to empathise). The philosophy is opposed to designer-driven and market-driven approaches, both of which tend to produce poor games.
(Adams, Fundamentals of Game Design, see source-fundamentals-game-design)
Key ideas
Two obligations
“PLAYER-CENTRIC GAME DESIGN is a philosophy of design in which the designer envisions a representative player of a game the designer wants to create. The designer then undertakes two key obligations to that player: the duty to entertain [and] the duty to empathize.” — Adams, Ch. 2
Duty to entertain: A game’s primary function is entertainment. Every design decision must be tested against the question: does this contribute to the player’s enjoyment? Features that do not entertain should be eliminated or minimised.
Duty to empathise: The designer must mentally become a representative player — a hypothetical person who resembles the intended audience — and evaluate the game from that perspective. This requires active research into the target audience’s preferences, not assumption.
Two misconceptions
Misconception 1: “I am my own typical player.” The assumption that the designer’s own tastes represent the player’s tastes. Historically, this produced games designed implicitly for young men by young men, excluding large portions of the potential audience. Player-centric design requires the designer to think like their intended player, even when that player is very different from themselves.
“Design Rule: You are not your player. Do not assume that you epitomise your typical player.” — Adams, Ch. 2
Misconception 2: “The player is my opponent.” An attitude inherited from arcade (coin-op) game design, where making the game hard was a revenue mechanism. In non-arcade contexts, treating the player as an opponent produces games that equate “hard” with “fun” and ignore the variety of ways games entertain. The designer’s job is to entertain, not to obstruct.
“Design Rule: The player is not your opponent.” — Adams, Ch. 2
The representative player
Player-centric design requires the designer to define a representative player — a hypothetical person who resembles the intended audience — and make design decisions on behalf of that player. This is not about giving players everything they say they want (market research is useful but not determinative), but about understanding what genuinely entertains them.
Design motivations
Adams identifies four problematic design motivations (and notes how each tends to fail):
| Motivation | Description | Typical failure |
|---|---|---|
| Market-driven | Built to capture a demographic or follow a trend | Lacks harmony; feels assembled rather than designed |
| Designer-driven | Designer retains all creative control | Ignores playtesting feedback; often botched (e.g. Daikatana) |
| Technology-driven | Designed to showcase technology | Too much time on tech, not enough on experience |
| Art-driven | Designed to showcase visual or aesthetic vision | Strong visuals, weak gameplay |
A good designer integrates all motivations in service of one goal: entertaining the player. The successful approach has vision, understands the audience, respects the license/tech/art without being enslaved to any of them.
Game design as craft
“Game design is not purely an art because it is not primarily a means of aesthetic expression. Nor is game design an act of pure engineering. The goal of a game is to entertain through play, and designing a game requires both creativity and careful planning.” — Adams, Ch. 2
Adams defines game design as a craft — combining artistic and functional elements. The highest expression of craft is elegance: a quality produced when artistic and functional elements come together brilliantly. Elegance in a game design usually means the rules are few but deep, aesthetics reinforce mechanics, and nothing feels bolted on.
In practice
- Before design: Define your representative player. Who are they? What do they play? What motivates them? What frustrates them?
- During design: For every decision, ask: “Does this contribute to my representative player’s enjoyment?” If the answer is unclear or no, challenge the decision.
- During development: Conduct playtesting with representative players. Their experience is the ground truth, not your experience as designer.
- Pitfall to avoid: Spending time in the game’s world without observing players. The designer’s perception of the game is fundamentally different from the player’s — only observation closes the gap.
Evidence
The principle is stated in Adams Ch. 2 as the book’s central design philosophy. It is applied throughout all subsequent chapters: level design (Ch. 16) explicitly instructs designers to “never lose sight of your audience.”
Adams notes that professionalism — the willingness to work hard on a game for an audience unlike yourself — is as important as passion. A true professional can create a game for an audience outside their own experience.
Implications
- Player-centric design is not the same as feature-parity or market research. It requires the designer to synthesise what players want with what makes a coherent, harmonious game.
- It is compatible with having a strong creative vision — the duty is to entertain, not to surrender all authorial intent. But when vision conflicts with entertainment, entertainment takes precedence.
- Player-centric design is most challenged in serious games (educational, persuasive), where entertainment may be secondary to another goal. Adams notes the duty to entertain can be “adapted” in these cases.
Open questions
- Does player-centric design have limits? Can a designer simultaneously maintain a strong aesthetic or artistic vision while fully subordinating design decisions to player preference?
- How does player-centric design interact with accessibility? Adams addresses this in Ch. 12; the “representative player” model may implicitly exclude disabled or minority players unless explicitly expanded.
Related
- playtesting — Primary tool for applying player-centric design; observing actual players
- game-definition — Understanding what a game is for informs who it is for
- holographic-design — Schell’s parallel concept: seeing the game from the player’s perspective simultaneously with the designer’s
- flow — Target state for the player; player-centric design aims to keep players in flow
- design-lenses — Many of Schell’s lenses are player-centric perspective-taking tools
- interest-curves — Player-centric pacing model
- source-fundamentals-game-design