Designing for calm

We are drowning in notifications, dashboards, and infinite feeds. Calm design is not about removing features — it is about respecting attention.

What is calm technology?

Calm technology, a term coined by Mark Weiser and John Seely Brown in 1995, is the idea that the best technology recedes into the background and only demands our attention when it truly matters.

In 2024, most software does the opposite. It pings, it badges, it auto-plays. Calm design pushes back.

Three principles of calm software

1. Default to silence

Notifications should be opt-in, not opt-out. A new user should not receive 5 welcome emails and a push notification in their first hour.

2. Respect the focal depth

Software should match the cognitive depth a task requires. A quick check of your bank balance should not look like a data dashboard. A deep work session should not be interrupted by a toast.

3. Make the important visible

When something genuinely needs attention — a security alert, a deadline, a message from a loved one — make it impossible to miss. The corollary: when something does not need attention, make it easy to ignore.

Applying the principles

In a recent project, we reduced push notifications by 73% (mostly by removing them) and increased the click-through rate on the remaining notifications by 5x. Less, but better.

The hard part

Calm design is politically hard inside companies. Every team believes their feature deserves attention. Saying "no" requires a strong product leader who is willing to defend the user's attention against internal pressure.

Closing

Calm is not minimalism. A complex dashboard can be calm if it respects attention; a simple landing page can be loud if it uses manipulative patterns. Calm is a stance toward the people who use our software.