Skip to content
All news

Designing for calm: why the best products feel quiet

Attention is the scarcest resource your users have. Here is how we design interfaces that respect it, and why calm products convert better.

Illustrated portrait of Elena Vos

Elena Vos

Soft flowing lines over a warm purple gradient

Every notification, badge and modal asks for a slice of someone's attention. Individually they seem harmless. Together they create products that feel exhausting to use, and exhausted users leave.

At Northstar we use a simple principle: an interface should be as quiet as the task allows. A banking app during a transfer should be focused and reassuring. A music app on a Friday night can be louder. The mistake is designing everything at the same volume.

Three habits of calm interfaces

  1. They make the next step obvious. One primary action per screen, clearly labelled, with secondary options available but visually subdued.
  2. They use motion with purpose. Transitions explain where something came from or went to. Decorative animation is the first thing we cut.
  3. They defer, rather than interrupt. Non-urgent information waits in a predictable place until the user is ready for it.

Calm is measurable

Calm sounds subjective, but its effects are not. After simplifying the checkout flow for one retail client, we saw task completion rise by 18% and support tickets drop by a third. Users didn't say the product was beautiful. They said it was easy, which is better.

The goal isn't to remove everything. It's to make sure everything that remains has earned its place.

If you want to try this on your own product, start with an inventory: list every element on your most important screen and ask what would happen if it disappeared. You will be surprised how much you can let go.