Game Design Document Version 2.0
summary
A live-ops manager from Plarium explains how to reduce conflicts caused by unclear game design documents (GDDs). The talk outlines practical ways to improve GDD version 2.0 so teams stop saying “this wasn’t in the specification” by clarifying requirements and communication.
AI-written summary · about
chapters (17)
- 0:00GDD v2 intro
- 1:04Document structure
- 2:55Goals and meaning
- 4:16Table of contents
- 5:20Competitors and references
- 5:43Core functionality
- 6:26Art and text elements
- 8:56Animation details
- 10:50Updating docs
- 11:52Sound design
- 12:35Tracking and analytics
- 13:39Localization
- 15:05Player use cases
- 16:30Screen map and flow
- 17:56Admin requirements
- 19:24Doc tips
- 20:51Template and conclusion
related talks
18mThe Game Designer's Toolkit: What It Should Be
21mManaging live operations game design
34mArchitecting Content for a Live Service Game
36mDesktop-like Games — How Not to Make Them
16mCreative process in distributed teams
01h 02mLevel Design Dead Ends and How to Escape Them
23mHow to Prepare BizDev So It’s Useful for Game Dev
50mDeveloper Experience in Mobile GameDev: How We Rebuilt a Plane in Flight