Skip to content
BENIBIX Learn

Design Spec vs Design Rationale

People think the spec says why a screen looks the way it does, and it does not. A spec says what to build: sizes, states and behavior. The rationale says why each choice won and what was tried instead. Keep both, so nobody undoes a good choice later.

Design🚀 Product Development

Design Spec

The exact details a builder needs to make a design. Sizes, colors, fonts and how it acts.

A design spec is the set of details a builder needs to make a design exactly. It lists sizes, spacing, colors, fonts and how each part behaves. It also covers states like empty, loading and error. Older specs were drawn as red lines over a screen, which is why they are called redlines. Today many tools show the numbers when a developer clicks on a part.

Example
Lucy's spec shows the button is 48 pixels tall with 16 pixels of padding. It also shows the error state the mockup left out.
Why it matters
Builders should not have to guess. A clear spec means the shipped product matches the design.
Full entry
Design🚀 Product Development

Design Rationale

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

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.

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.
Full entry

In one line

Design Spec
The exact details a builder needs to make a design. Sizes, colors, fonts and how it acts.
Design Rationale
The written reason for a design choice. It is kept so nobody has to guess later.