Calm Defaults
A pattern for restraint — shipping software with a quiet first impression, restrained feature scope, and the highest number of users who never notice the product exists.
Most products arrive at their calmest version by editing themselves down, not by designing more in. The default state — the first thing a new user sees — should be as close to finished as possible: no tour, no notification badge, no empty state begging for content.
Let the surface stay quiet so the work is the loudest thing in the room.
When to use it
- New dashboards, settings screens, and editor surfaces for early-stage tools.
- Anywhere an empty state is tempting you to add a tutorial pop-up.
- When the team proposes a feature to fill a screen that was already working.
When to avoid it
- Products whose value is discoverability — marketplaces, search engines.
- Highly opinionated creative tools where prompts are features.
What it looks like in practice
A blank new account should feel like a fresh notebook, not an empty restaurant waiting to seat you. The buttons that exist should be the buttons you need. The buttons that don’t exist shouldn’t be hinted at. The user discovers the surface by using it, not by being shown a tour of features they have not earned yet.