How to write a Game Design Document

---------------------------------------------------

00:00 Intro
00:55 Why would you need a Game Design Document?
02:45 How to make a Game Design Document
06:10 Picking a format
07:59 The One-Page Method
11:52 Outro

Game Design Documents are extremely useful for keeping your game development project on track. But, not all GDD's are helpful. In this video, I'll show you when to use a game design document, how to write one of your own, and how to do it in a way that's actually useful.

#indiegamedev #gamedesign #gamedevelopment

CREDITS:
---------------------------------------------------

Music:

In the Atmosphere - Bad Snacks
New Year - Bad Snacks

[Hersatz]

Couple of additional tips for aspiring developers here.

1.
Avoid walls of text as much as possible.

It is the worst way to transfer the complexity of game design information.
Text should only be used to specify things that cannot be properly explained otherwise.

2.

Try to separate things into different design documents also.
A system should not be detailed in a level design document, for example.
Nobody wants to have to find how an AI should behave through the design document of dungeon number 6.

It's all about defining through encapsulation and teaching multi-faceted elements of a game in the fastest way possible.

3.
Use a variety of design document format. Some things are more easily explained through specific design document formats.
Here's a short non-exhaustive list:
- Storyboard
- Mind map
- One pager
- Flowchart
- greyboxing

[advaitadvait]

This is the most simplest explanation of a Game Design Document I have seen till date.

[konichiwatanabi]

Thanks for this. This helped me distill my infinite zoom mind map into a 1 page design doc that I'm super proud of. It felt like rediscovering my game all over again and the whole project feels more real than it ever has. Powerful approach!

[nicolasm.bronner]

That was really helpful! Thanks a lot! I'm doing my first GDD for a game jam, the timing is perfect! 🙏🏻

It's true, you really sound like GDTK 😂, keep the great work!

[whynotanyting]

I've found Miro quite handy to organize our thoughts for a game we're making. It's pretty good since there isn't the limit of paper space and you can technically fit the whole thing on "one page". Very handy for art references and music as we can collaborate some sort of "mood board" together. Plus, if we ever need to add someone to the team we can just invite them.

[NO]

1:25 I will need it to explain it myfelf in few month

[Krummelz]

I used to keep a draft email where I'd just jot down all my game ideas as I get them, and work on them over time as and when I can. I moved to using Obsidian more recently, but typically still use a one-pager for all my ideas, and if it grows too large, I can just give it it's own page and link back to the main one.

[TheMightyThor]

Crucial for all game devs. This video tought me alot 😀

[JoshwaLaw]

This is perfect! I'm working on a game right now and it's so hard to stay organized!

[TurkiKAlqou]

Great video! Could you please go into more details with an example in another video? Like a video focused on Game Design as well as writing an effective GDD with a full example from start to finish (One-Page example).

[diefrogman]

Thank you this video was incredibly helpful

[drekke]

What a great, useful video! Subscribed! I'm in the very beginning of my journey, so this channel will definitely be one of my 'go-to''s! Thanks and have a great day!

[blossomcherrypink]

Very cool idea for a video. Thanks for the epic knowledge.

[VividRem]

I'm making my game in the most ADHD way possible. Introducing one bug at a time 🎉

[Qewbicle]

It sounds good, and seems to simplify, but it's not as easy as it sounds.

It's like when first learning how to build a resume or a business plan.

Dozens of templates, dozens of advice, dozens of opinions. Which leaves you with too many possible decisions.
Until that day when it clicks, that you put whatever the heck you want because you're a pro in your industry and know what matters, and then you min max, the minimum effort for maximum impact.

You express it adamantly, as a statement of fact. No begging, no fluff, no buzzword salad. As a real pro.

This means. You'll probably write it. Struggle with execution. Start other intermediate projects. Rewrite. Write for something else. Pivot. Give up. Start over. Each step, side stepping but learning.

Then. If you trust the process of learning from the struggles, you'll find yourself knowledgeable in the many hats.

Your iterative changes didn't seem to be much further. But now twenty or thirty iterations along, they add up. Two steps forward, one and a half back. I thought I learned this, I did it before, but now I'm having to do it again, and that again, but I remember that.

The process. The grind. The set backs. The determination.

If you have grit, then you'll eventually accomplish it.

[KyleJMitchell]

It would be useful for you to add a link to that GDC talk to the description of this video.

[Alohomora]

I’m 34 years old Engineer, can i start to become a Game Designer from now?

[deadtoadsoup]

Best use for a Game Design Document: explaining it to Copilot to write all the C# for you!

[TheYashakami]

A one page design document is complete nonsense.