Subtractive Design
Design is subtractive. Absence creates hierarchy, calm, and focus. Adding feels productive; removing is usually the harder and better move.
Defaults
- Require a demonstrable purpose for every element, token, and interaction.
- Prefer fewer decisions for the user at each step.
- Use space, silence, and restraint as active design materials.
- Hide necessary complexity rather than celebrating it.
- Cut anything that exists only because it was easy to generate.
Prefer / Reject
| Prefer | Reject |
|---|---|
| Clear primary action | Equal-weight button forests |
| Progressive disclosure | Showing every option up front |
| Shared tokens and patterns | One-off flourishes per screen |
| Defaults that remove setup | Preference panels for undecided design |
| Calm empty space | Filling space because it is empty |
Process
- List what the screen must accomplish.
- Mark every element that does not serve that list.
- Remove or demote the marked set.
- Recheck whether the remaining pieces still need labels, chrome, or motion.
- Stop when further removal would hide a needed decision or affordance.
Review checklist
- Can any control be removed without harming the task?
- Is there a single clear primary action?
- Are secondary actions visually secondary?
- Is any copy repeating what the UI already shows?
- Are decorative layers earning their keep?
- Would a quieter version communicate the same intent faster?
Source essays
- Beauty comes from absence
- Designing the invisible
- Hygge in interface design
