Esc
↑↓ navigate   Enter open   Esc close
Intermediate Writing 11 min read

How to Write a Game Design Document (GDD) in English

A complete guide for game developers: how to write a professional Game Design Document — structure, vocabulary, key sections, and English phrases for GDD writing.

#writing#gdd#game-design#game-development#documentation#game-developer

A Game Design Document (GDD) is the central design reference for a game project — a living document that describes what the game is, how it plays, and how it should be built. It aligns developers, artists, producers, and QA around a shared vision. Writing a clear GDD in English is an essential skill for any game developer working on a team, pitching to publishers, or collaborating internationally. This guide covers the structure, vocabulary, and key writing patterns.

What Is a GDD?

A Game Design Document (GDD) is a structured document describing the design of a game. Depending on the project size, it may be:

  • A 10-page overview for a small indie game
  • A 200-page specification for an AAA title

GDDs serve multiple purposes:

  • Alignment — ensures everyone on the team understands what is being built
  • Scope definition — prevents feature creep during development
  • Reference — a source of truth for design decisions
  • Communication — lets new team members onboard quickly

“Before we start any feature, I check the GDD — if it’s not documented there, we need to design it before building it.”

GDD Structure

Section 1: Game Overview

Start with a high-level description anyone can read in 2 minutes.

Include:

  • Game title and working title if different
  • Genre — platformer, RPG, FPS, puzzle, strategy, simulation
  • Platform — PC, console (PS5/Xbox), mobile, browser, VR
  • Target audience — age range, gaming experience level, preferences
  • Core concept — one to three sentences describing what makes this game unique

Template:

## Game Overview

**Title**: Shadow Protocol
**Genre**: Top-down tactical stealth RPG
**Platform**: PC (Steam), with console port planned for Year 2
**Target audience**: Core gamers ages 18–35 with interest in strategy and stealth
**Player count**: Single-player with optional co-op for 2 players

**Concept**:
Shadow Protocol is a tactical stealth game in which the player controls a
team of three agents navigating procedurally generated Cold War-era facilities.
Players switch between agents in real time, combining unique abilities to
bypass security, neutralise threats covertly, and extract without detection.

Section 2: Core Gameplay / Core Loop

The core gameplay loop is the fundamental repeating cycle of player actions — what the player does, how the game responds, and what reward brings them back.

Vocabulary:

Core loop — the primary cycle: Action → Feedback → Reward → New challenge → Action Gameplay mechanics — the rules and interactions that make up the gameplay Player agency — the meaningful choices the player makes

Template:

## Core Gameplay Loop

1. **Mission briefing** — Player selects an operation and receives objectives
2. **Deployment** — Player places agents at entry points
3. **Execution** — Player moves agents, uses abilities, eliminates threats covertly
4. **Extraction** — Player reaches the extraction zone with objectives complete
5. **Debrief** — Player receives XP, loot, unlocks — fuels progression

**Session length**: 15–40 minutes per mission

Section 3: Player Experience Goals

Describe how the player should feel — not just what they do. This guides design decisions.

“The player should feel like a master of controlled chaos — juggling multiple threats while maintaining elegant, unseen control.”

Common experience design vocabulary:

  • Player fantasy — the power or identity experience the game fulfils
  • Flow state — the optimal challenge-skill balance where the player is fully engaged
  • Tension — designed stress that makes resolution satisfying
  • Agency — the feeling that your choices matter

Section 4: Mechanics

Document each gameplay mechanic in detail.

For each mechanic include:

  • Name and category
  • Description
  • Controls / input
  • Rules and constraints
  • Interaction with other mechanics
  • Balance notes

Example: Stealth Mechanic

## Mechanic: Awareness / Alert System

**Category**: Core stealth
**Description**: Guards have a detection cone displayed visually. If an agent
enters the cone, a bar fills. A full bar triggers an Alert state.

**Alert States**:
- Undetected — guards patrol normally
- Suspicious — guard investigates the area for 10 seconds
- Alert — guard calls reinforcements and starts active search
  (timer 60 seconds before mission fails)
- Compromised — all agents detected; mission objective changes to escape

**Detection factors**:
- Distance — longer range reduces detection speed by 50%
- Lighting — dark areas reduce detection cone by 40%
- Noise — agents moving at speed attract nearby guards even outside vision cones

**Interaction**: Alert state resets if player neutralised the guard and used
the 'Hide Body' action within 5 seconds.

Section 5: Characters

Document playable characters (and key NPCs) with structured entries.

Template:

## Character: Voss (The Infiltrator)

**Background**: Former SIGINT analyst, specialises in electronic warfare
**Class**: Infiltrator
**Role**: Hacking, bypassing electronic security, reconnaissance

**Abilities**:
| Ability | Cooldown | Description |
|---------|----------|-------------|
| Signal Jam | 30s | Disables cameras in a 10m radius for 15 seconds |
| Data Tap | Passive | Voss can extract data from terminals 40% faster |
| Ghost Mode | 60s | Voss becomes undetectable to cameras (not guards) for 20 seconds |

**Weakness**: Lowest health pool; detected instantly if in direct guard line of sight

Section 6: Level Design

Describe the types of levels, layout principles, and design goals.

Vocabulary:

Level beat — a self-contained challenge unit within a level Chokepoint — a narrow passage that forces a specific type of interaction Sandbox — an open level with multiple ways to solve a challenge Critical path — the main route through a level; not the only path

Example:

## Level Design Principles

- All missions have a **critical path** but at least two alternative paths
- Each mission features one mandatory **encounter** and 2–3 optional encounters
- Guards are placed to create **dynamic chokepoints** — players must work around rather than through
- At least one **sandbox environment** per act — a large area with multiple objectives
  and no prescribed order

Section 7: Progression System

Document how the player grows and unlocks content.

Vocabulary:

Progression loop — the long-term cycle of growth: earn XP → level up → unlock abilities → face harder challenges → earn more XP Skill tree — a branching diagram of learnable abilities and upgrades Unlock — a reward that grants access to new content Power progression — increasing strength/stats over time

Example:

## Progression System

**XP sources**: Mission completion, bonus objectives, clean extractions (undetected)

**Agent levelling**:
- Agents earn XP separately
- Each agent has a 20-node skill tree across 4 branches:
  - Combat (lethal abilities)
  - Stealth (evasion, passive reduction)
  - Tech (gadgets, hacking)
  - Command (team buffs and coordination)

Section 8: UI / UX Design Notes

Document key UI elements and design intent.

Vocabulary:

HUD (Heads-Up Display) — on-screen information during gameplay Diegetic UI — UI that exists within the game world (e.g., a health bar on the character’s armour) Affordance — visual cue that communicates how an element can be interacted with

Example:

“The HUD should be minimal — only show the detection cone overlay when an agent is selected. Health and ability cooldowns appear on the agent portrait, not as floating numbers in the world. Everything should be readable in 720p.”

Section 9: Out of Scope / Not in This Version

Explicitly document what is NOT in this version — prevents scope creep.

## Out of Scope (v1.0)

- Multiplayer beyond 2-player co-op
- Console release (planned post-launch)
- Procedural mission generation (designed for v1.1)
- Player-created agent customisation skins

Language Tips for GDD Writing

Use present tense

GDDs describe the game as it will be, using present tense:

  • ✅ “The player selects an agent and moves them with the mouse.”
  • ❌ “Players will select an agent and will move them.”

Be specific, not vague

  • ❌ “The game should have good stealth mechanics.”
  • ✅ “Guards have a 90° detection cone and a 12-metre detection range. Detection speed at range beyond 6m is reduced by 50%.”

Define jargon on first use

“The detection cone (a visual indicator of a guard’s field of view) fills the Alert meter when an agent enters it.”

Practice

Deepen your game development vocabulary with the Game Development English exercise set and explore the Game Developer learning path.