FORGE
Services About Blog
Restraint as a design principle
Design 2 March 2026 · 4 min read

Restraint as a design principle

Every animation, every shadow, every gradient is a decision. The best design work is almost always the result of removing things, not adding them.

RO
Robert Okoroafor
FORGE

Every designer has a draft that is too much. The one with six typefaces, a gradient on the gradient, a scroll animation on the scroll animation. It is not a failure of taste — it is the first draft doing what first drafts do. Proving that you can.

The second draft is where design starts. The second draft asks: what earns its place?

The cost of excess

Every element on a page asks something of the user. It asks for attention, for interpretation, for a moment of cognitive processing. That cost is real even when the element is decorative. Especially when it is decorative.

A page with twelve things competing for attention communicates nothing. The hierarchy collapses. The eye has nowhere to rest. The user reads it as noise and moves on.

Restraint is not minimalism for its own sake. Minimalism can be as self-conscious as maximalism. Restraint is the decision to include only what the design needs to work — and to trust that what remains is enough.

What gets cut

The drop shadow that was added because a card felt flat. The second CTA that was added because someone was worried the first one was not clear enough. The background texture that was added because the page felt empty. The animation that was added because someone saw it on another site.

None of these additions are wrong in isolation. The drop shadow might be right. The second CTA might be right. What makes them wrong is when they are added without a specific problem they are solving. When the answer to why is this here is: it felt like something was missing.

Something being missing is not a reason to add something. It is a reason to examine whether the existing elements are doing their job.

The discipline of the reason

A useful practice: for every element on a page, state the reason it is there. Not a justification — a reason. Justifications defend what is already present. Reasons precede the decision.

If you cannot state the reason, the element does not have one. That is useful information. It does not always mean the element should go — sometimes the reason is aesthetic and that is legitimate. But forcing the articulation of a reason catches the additions that exist only because no one removed them.

What restraint looks like in practice

It looks like whitespace that is uncomfortable to leave there. It looks like a heading without a subtitle because the heading is already clear. It looks like a button without an icon because the label says enough. It looks like a palette with three colours instead of six because three is sufficient.

It looks like the version you almost shipped before you added one more thing.

New project

Start a
project.

Discovery call
Loading calendar…