What it is
The practice of capturing design decisions, rationale, specifications, and context in durable, shareable form so teams understand not just what was decided but why.
When to use it
During Implement, and throughout, whenever decisions need to persist beyond the people in the room.
Why (value)
Preserves rationale, speeds onboarding, prevents relitigating settled decisions, and supports handoff and maintenance.
How to run it
- Decide what must be documented and for whom.
- Capture decisions with their rationale and alternatives.
- Include specs, states, and edge cases.
- Store it where the team will actually find it.
- Keep it current as decisions change.
Inputs and outputs
- Inputs: Design decisions, rationale, and specifications.
- Outputs: Durable, findable documentation.
Time and effort
Medium. Ongoing discipline more than a single effort.
Evidence and limitations
Documentation records expert-review decisions and rationale; it preserves intent but is not evidence that the decisions were correct. Keep it current or it misleads. See Evidence and limitations.
Tips and pitfalls
- Capture the why, not just the what.
- Document decisions as they happen, not later.
- Prune or update stale docs.
Variations
Decision records, design specs, rationale docs, and living design-system docs.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Design handoff and specification — Give engineering everything it needs to build the design correctly, including the edge cases.
- Design annotations — Add notes to designs that explain behavior, logic, and intent for accurate implementation.
- Design system work — Build and maintain the shared components, tokens, and guidelines a product is made from.
