On Monday, we invited guest lecturer Sophie Artemigi, who delivered a talk on how to create an effective Game Design Document (GDD). The session focused on clarifying the purpose of a GDD and how it differs from other design documents, as well as what makes a GDD genuinely useful in a development context.
Pitch Deck vs GDD
- Pitch Deck
A Pitch Deck is focused on vibe and ambition. It is designed to look exciting and sound appealing, and is mainly used to attract collaborators, funding, or attention from publishers and investors. - GDD
A GDD is specific, practical, and actionable. It is written for internal development teams and breaks ideas down into clear, executable tasks. Its main purpose is to ensure that everyone involved shares the same mental image of the game being developed.
What Makes a GDD Readable
Sophie emphasised that a successful GDD is one that people actually want to read. This means structuring information into clear sections, highlighting important points with bold or underlined text, and prioritising diagrams over long blocks of writing. Visual elements such as gameplay flows, system diagrams, and gameplay loops are far more effective than dense text when explaining how a game works.
Core Components of a GDD
- Overview
Introduces the core idea, experience, and overall direction of the game. - Gameplay
The most critical section, where core systems are broken down into clear, detailed components. - Visuals
Defines the visual direction precisely rather than relying on vague stylistic references. - Level Design
Focuses on spatial structure, player progression, and how mechanics are introduced. - Narrative
Explains how story, character, and player choice are communicated. - Audio
Covers sound design, implementation, and the role of audio within gameplay. - Project Management
Addresses scope, the minimum viable product (MVP), and which elements can be scaled down if necessary.