# Design Rationale

Design rationale records the reasoning behind a product decision, including the question considered, alternatives examined, evidence used, and tradeoffs accepted.

- Type: practice
- Domain: Experience & interface
- Level: Advanced
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/design-rationale/>)

## What it means

Design rationale is a durable account of why a design took its present form. It connects a decision to its context: the user or business problem, constraints, options, evaluation criteria, evidence, and unresolved concerns. Structured approaches such as Questions, Options, and Criteria can help, but a useful rationale may be a concise decision note rather than a formal diagram.

## Why it matters

Screens show outcomes, not the reasoning that produced them. Without rationale, later teams may reverse a deliberate tradeoff, repeat discarded exploration, or treat an old constraint as permanent. A compact record improves critique, onboarding, governance, and change review because people can challenge the assumptions and evidence instead of debating personal preference.

## When to use it

Capture rationale for consequential, surprising, contested, regulated, or difficult-to-reverse choices. It is especially useful when several plausible options exist, multiple disciplines contribute, or the decision may outlive its authors. Routine spacing adjustments rarely need a full record.

## How it works

1. Frame the decision as a specific question and state the outcome or user need at stake.
2. List credible options, including maintaining the current design, and identify relevant constraints.
3. Define criteria before selecting an option; distinguish evidence, assumptions, and preferences.
4. Record the chosen option, rejected alternatives, tradeoffs, owners, and conditions that would trigger reconsideration.
5. Link the note to research, prototypes, requirements, and implementation records, then keep its status current.

## A practical example

A payments team must decide whether failed transfers should retry automatically. The rationale compares immediate retry, scheduled retry, and manual recovery against fraud exposure, user control, support burden, and network behavior. It selects one scheduled retry with prominent cancellation, notes that outage data is limited, and sets a review after three months of production evidence.

## Where it breaks

Documentation can become ceremonial, stale, or biased toward justifying a decision already made. It cannot replace research, prototypes, or accountable judgment. Excessive detail discourages maintenance and can expose sensitive strategy or personal data, so teams should record the minimum reasoning needed and apply appropriate access controls.

## Common mistakes

- Recording only the winning option and making rejected alternatives disappear.
- Mixing evidence, constraints, and stakeholder preferences into one unexplained conclusion.
- Treating an old rationale as permanent even after its assumptions or operating conditions change.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/design-rationale/#visualization-design-rationale>)

## Sources

1. [Design Spaces and How Software Designers Use Them: A Sampler](<https://cmu-swdesign.github.io/reading/ShawDesignSpace-b.pdf>) — Carnegie Mellon University · Academic paper
2. [Evaluating Design Rationale in Architecture](<https://research-portal.uu.nl/ws/files/236342633/Evaluating_Design_Rationale_in_Architecture.pdf>) — Utrecht University Research Portal · Academic paper
3. [Capturing Design Rationale with QOC](<https://notesforgrowth.github.io/Capturing-Design-Rationale/>) — Notes for Growth · Professional reference

## Related topics

- [Design Documentation](<https://wiki.soroush.uk/topic/design-documentation/>)
- [Design Review](<https://wiki.soroush.uk/topic/design-review/>)
- [Decision Rights](<https://wiki.soroush.uk/topic/decision-rights/>)
