Quick definition:A written plan describing a game's concept, rules, features, art direction and technical approach, used to keep a development team working towards the same vision.
Meaning
A game design document, usually called a GDD, describes what a game is and how it should work. It typically covers the overall idea, the audience, the rules and mechanics, the structure of levels, the story, the look and sound, and sometimes the technical plan and schedule.
Its main job is communication. Designers, programmers, artists and producers use it as a shared reference, so that decisions do not depend on one person's memory. It can also help to explain a project to publishers or investors who need to understand the plan before supporting it.
Modern teams often treat the document as a living record rather than a fixed rulebook. Games change during development as ideas are tested, and a plan that is not updated can mislead. Some teams use short pitch documents, boards or wikis, which they update as the project moves forward.
Origin:The name is descriptive: a document that records the design of a game. Such plans have been used since developers began working in teams, and they are often shortened to GDD. There is no single inventor, and the form varies widely, from long formal manuals to short, flexible outlines that change as work continues.
Example:A small studio starts a puzzle game, and its designer, Fiona, writes a short document listing the main idea, the controls, the types of level and the art style. When a new programmer joins, she reads it in an afternoon and knows what to build. Later, the team updates it as ideas change.
Did you know?Opinions differ about how long a design document should be. Some teams favour a large, detailed one, while others prefer a short summary or a shared online page, because long documents can become out of date quickly as a game changes.
