Contents
Engine-independent guidance
Know your audience — design for a specific player, not "everyone"
On this page
The principle
Design for a specific player, not an abstract "everyone." Know who the game is for — what they enjoy, expect, and find hard — and let that knowledge inform decisions. A game aimed at everyone usually delights no one; a game that knows its audience can be sharp, coherent, and loved by the people it's for.
Applies when
Throughout design, and especially at the outset (who is this for?) and whenever a decision has no obvious answer — check it against the target player. Foundational to vision, scope, difficulty, and tone.
Does not apply / Exceptions
"Know your audience" is not "chase the biggest market" or "give players only what they ask for" (players report symptoms, not cures — PLAYTEST-0004); a designer can know their audience deeply and still surprise or challenge them. Personal/art games may be made for an audience of one (the creator) — that's a valid, known audience, not an absence of one. And a genuinely broad game can serve a wide audience if it understands what that audience shares — breadth done knowingly, not by averaging blindly.
Rationale
Every design decision — difficulty, tone, complexity, controls, monetization — has a right answer only relative to who's playing, so "is this good?" is unanswerable without "good for whom?" [S-schell-artofgamedesign]. Trying to please everyone forces averaging: the game gets sanded down to offend no one and excite no one, and its decisions pull in incompatible directions (a game can't be both a hardcore sim and a pick-up-and-play casual game without becoming incoherent). Knowing the audience is what makes "design for the experience produced" (DESIGN-0001) actionable — the intended experience is intended for someone. It also grounds the vision (VISION-0001) and disciplines scope (you build what your audience needs, not every possible feature). This is not pandering or market-chasing; it's the basic act of designing for real people rather than a phantom universal player.
Implementation
Define the target player early (their tastes, skills, expectations, context) and make it explicit (part of the vision, VISION-0001). Check ambiguous decisions against them: would this player enjoy this? Use it to set difficulty, complexity, tone, and scope. Validate assumptions with real representative players (PLAYTEST-0006's sampling).
Disagreement
Audience-first design (coherent, sharp, loved by its people — but narrower reach) vs. broad-appeal design (bigger market — but risk of averaging into blandness). And how much to give the known audience what it expects vs. surprise it. The resolution: know the audience deeply, then decide deliberately how much to comfort vs. challenge them — breadth and surprise are choices made with audience knowledge, not substitutes for it.
Notes
A foundational player-centric principle the corpus implied everywhere but hadn't stated outright (added in the 2026-07-15 audit). Confidence 4.
Connected principles
Source trail
Evidence strength describes support for this guidance, not a probability that it is right for your situation.
Citation and record details
GDC-L1-DESIGN-0008 · contextual guidance · canonical
Recorded verification date: 2026-07-15. This is not a claim of an engine test.