Game Design Document Version 2.0

What the talk is about

Oleg Medved explains how to build a game design document that actually works for the team, walking through it from top to bottom. It opens with a change log that links to the edited sections, followed by goals (ideally concrete, so they can be checked later), a table of contents, a general overview, competitors and references, and the main section with conditions and limits. Next come wireframes with planned texts, animation and sound descriptions, tracking and push notifications planned in advance, use cases, a screen map, flowcharts, and requirements for the admin tool. The document should be updated to match final designs and agreements. He advises short numbered points without filler, and rereading the text as a developer would. Useful for game designers and producers setting up documentation.