Fox Studios logo Fox StudiosGame projects, devlogs and Scratch builds
Studio

Writing a Game Design Document a Small Team Will Use

Three weeks into a project, two people on the team are building different versions of the same mechanic, and nobody can say which one is right.

Two people at a shared desk with a laptop showing a planning document beside sticky notes and sketches of pixel art characters

Three weeks into a project, two people on the team are building different versions of the same mechanic, and nobody can say which one is right. That is the moment most small studios decide they need a game design document, and it is usually the moment they write one nobody reads.

We have written long ones and short ones at Fox Studios. The long ones went stale within a month. The short ones are still open in a browser tab on every machine. This is the format we settled on for teams of two to six people.

What a game design document is for on a small team

On a large team, a design document is partly a contract between departments. On a team of three, it has one job: make sure everyone is building the same game. It answers questions before they turn into arguments, and it gives a new collaborator a way to catch up in 15 minutes instead of three meetings.

That means the audience is your own team on a busy Tuesday, not a publisher. Write for someone who has 5 minutes and needs to know whether the jump should feel floaty or snappy.

The counter-take: skip the 60 page bible

Plenty of tutorials tell beginners to write a complete design bible before touching code: every enemy, every level, every menu, every line of story. I think that advice hurts small teams more than it helps.

The reason is simple. Your design will change the first time you play a rough build. Mechanics that sounded fun in text feel flat, and something you added as a joke becomes the core of the game. A 60 page document written before that point is mostly guesses, and once the team notices it is wrong in a few places, they stop trusting the rest. Then nobody updates it, and you are back to arguing in chat.

A short document that is correct is worth far more than a long one that is partly fiction. Write the minimum, prototype, then write down what you learned. It fits the same thinking behind why small games beat big unfinished ones.

Our one page core and what goes in it

The first page is the only part everyone must read. We keep it under 400 words and it has six headings.

  1. Pitch in two sentences. What the player does and why it is fun. Example: "You run a tiny lighthouse during a storm. Keep the light turning and guide ships past the rocks while repairs pile up."
  2. Three pillars. Three words or short phrases that every feature must support, such as "calm, readable, one more night." If a feature does not serve a pillar, it waits.
  3. Core loop. The 30 second cycle the player repeats, written as a short chain: spot ship, rotate light, fix damage, earn parts.
  4. Target platform and controls. For us this is often Scratch in the browser first, so we note keyboard only, no right click and a 480 by 360 stage.
  5. Scope line. A hard limit in plain numbers, for example "5 nights, 3 ship types, 1 upgrade tree, 6 weeks."
  6. Not in this game. A list of things we have decided against. This section saves more arguments than any other.

Supporting pages that stay short

Behind the core page we add separate pages only when a topic needs more than a paragraph. Each one has an owner whose name sits at the top.

Mechanics sheet

One row per mechanic with the actual numbers: jump height in pixels, move speed, cooldown in seconds, damage values. A table beats prose because people look up one value at a time. When the numbers change in the build, they change here the same day.

Content list

Every level, enemy, item and sound effect with a status column: idea, placeholder, final. This doubles as our task list, and crossing items off is one of the small milestones that keep a game project alive.

Art and audio direction

Palette, sprite size, font and three to five reference images described in words. For Scratch projects we note costume dimensions so sprites do not get scaled and blurred.

Open questions

A running list of things we have not decided yet, with a date for each one. When a question is answered, it moves into the right page and gets deleted here.

Keeping the game design document alive during production

A design document only stays useful if updating it is part of the work, not extra work. These rules have held up for us across five projects.

  • Update after every playtest. Spend 10 minutes after each test session changing what turned out to be wrong.
  • One source of truth. Decisions made in chat do not count until someone writes them into the document. We say "doc it" out loud, and whoever made the call writes the line.
  • Date the changes. A short change log at the bottom, with one line per change and a date, lets returning teammates see what moved.
  • Delete freely. Cut features belong in the Not in this game list, not in a graveyard section that keeps growing.
  • Review weekly. Our Monday meeting starts with the core page on screen. If the pitch or pillars no longer match the build, we fix one or the other.

Use whatever tool your team already opens every day. A shared document, a wiki page or a pinned note all work. The tool matters far less than the habit.

When the document has to grow

There are a few moments when a short document is not enough. Bringing in a contractor, applying for a grant, or pitching to a publisher all need more detail, and splitting income means writing down who owns what, which we cover in revenue split agreements for a small indie game team.

Even then, we do not expand the core page. We write a separate document for that audience and link it from the core. The team keeps working from the version they trust.

Frequently asked questions

How long should a game design document be?

For a small team, the core should fit on one page, roughly 300 to 400 words. Supporting pages can add a few thousand words over a project, but each page should stay short enough to read in a couple of minutes. If nobody reads a page, cut it.

Do solo developers need a game design document?

A solo developer benefits from a one page version even more than a team does. It keeps scope honest when motivation dips and new ideas start to creep in. The Not in this game list is especially useful when you are your own only critic.

What should be in a game design document template?

Start with a pitch, design pillars, the core loop, platform and controls, a scope limit and a list of what is out. Add a mechanics table, a content list and open questions as the project grows. Skip sections that do not help your team make decisions.

RD
Reyansh Dole

Reyansh started making small games as a teenager and now writes the devlogs and tutorials here, focused on how beginners actually ship a first project.

More posts by Reyansh

More in Studio

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto ankertoto