Design Rationale
Design rationale records the reasoning behind a product decision, including the question considered, alternatives examined, evidence used, and tradeoffs accepted.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/design-rationale/
01What 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.[1][2][3]
- Decision question
- What required a choice
- Context + constraints
- Users, system, policy, time, and risk
- Evidence
- Research, data, standards, and technical facts
- Alternatives
- Credible options considered
- Chosen direction
- The decision and its scope
- Tradeoffs
- Benefits, costs, risks, and excluded outcomes
- Consequences
- Expected follow-up and operational effects
- Revisit trigger
- Evidence or change that should reopen the decision
Rationale records why a choice was reasonable at the time; it is not proof that the decision remains correct when context changes.
02Why 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.
03When 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.
04How it works
- Frame the decision as a specific question and state the outcome or user need at stake.
- List credible options, including maintaining the current design, and identify relevant constraints.
- Define criteria before selecting an option; distinguish evidence, assumptions, and preferences.
- Record the chosen option, rejected alternatives, tradeoffs, owners, and conditions that would trigger reconsideration.
- Link the note to research, prototypes, requirements, and implementation records, then keep its status current.
05A 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.
06Where 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.
07Sources
- Design Spaces and How Software Designers Use Them: A SamplerCarnegie Mellon University · Academic paperDesign Spaces and How Software Designers Use Them: A Sampler
- Evaluating Design Rationale in ArchitectureUtrecht University Research Portal · Academic paperEvaluating Design Rationale in Architecture
- Capturing Design Rationale with QOCNotes for Growth · Professional referenceCapturing Design Rationale with QOC