What it is
One row per significant design decision — title, rationale (why this choice), alternatives considered (what was rejected), outcome, tags, and author. The audit trail you wish your previous projects had.
When to use it
- Recording the "why" behind a non-obvious design choice for future-you.
- Settling repeat-debates by pointing at the existing decision.
- Onboarding a new designer who needs the reasoning behind weird-looking systems.
- Documenting a difficult cut (feature, character, mechanic) and why.
How to use it
- 1Click "+ New Decision" — title is the decision itself ("Use turn-based combat").
- 2Rationale: 2-3 sentences on why this option won.
- 3Alternatives: list 2-3 options that were considered and rejected.
- 4Outcome: brief note added later if the decision was revisited or reversed.
Tips you should know
- →Tag decisions by area (combat / story / monetisation) for grouped review.
- →Author is auto-set from the current user — viewable in history.
- →Decisions are append-only by convention — if you change your mind, write a new decision that supersedes the old one (link via tag).
- →A well-maintained decision log is the single highest-leverage doc on the project.