Skip to content
BENIBIX Learn

Design Rationale

Design🚀 Product DevelopmentReviews and Specs

Also known as Design Decision Record, Design Decision Log, Design Reasoning

The written reason for a design choice. It is kept so nobody has to guess later.

Think of it like

It is like writing in a recipe why you used less salt. The next cook will not undo it.

Example

Leo notes why the delete button sits apart from save: in testing, 3 of 8 users hit delete by mistake. A year on, a new designer keeps it there.

Why it matters

Without the reason, good choices get undone. New people redo old debates or repeat old mistakes.

Definition

Design rationale is the written reason behind a design choice. It says what was chosen, what else was tried and why the choice won. It often points to the test or data that settled it. It lives beside the spec or in a shared log. Later, anyone can see why a screen looks the way it does.
The reason for a choice is written at review and travels with the spec to the build.

Common mistake

Writing only what was decided. The options you dropped and why matter just as much.

Key takeaways

  1. 1
    What and why. The choice and its reason.
  2. 2
    What else was tried. The options you dropped.
  3. 3
    Kept with the spec. Easy to find later.

Compare