Designing with less: a case for restraint

Fewer decisions for the reader

Most interfaces fail by accretion. A badge is added because one stakeholder asked for it, a second accent colour appears to separate two tabs, a shadow arrives to fix a contrast problem nobody traced to its source. Each addition is defensible alone. Together they ask the reader to decode a system that was never designed.

We start from the opposite end. Before adding anything, we ask what the screen would lose without it. If the answer is nothing, it stays out. On the Fieldnote journaling app that rule removed three of five type sizes and one of two accent colours, and testers finished the daily entry flow noticeably faster.

Restraint is not minimalism

Restraint is not about looking sparse. A dense data table can be restrained if every column earns its place and every state is accounted for. What we avoid is decoration that carries no information: the tinted card, the gradient button, the icon that repeats its label.

The practical test is simple. Remove it, then look again. If nobody notices, it was noise. You can see where this approach landed in our recent client work, where most screens use two weights and a single accent.