Software shouldn't create more work

Work already comes with enough notifications, deadlines, messages, and decisions.

The software we use shouldn't make that feeling worse.

Yet many modern products are designed around constant engagement.

More notifications.

More badges.

More alerts.

More dashboards.

More things asking to be checked.

We think there is another way.

Calm doesn't mean empty

A calm interface isn't an empty interface.

It's an interface that understands priorities.

It knows that not every update deserves a notification.

It knows that secondary information doesn't need to compete with the primary task.

It knows that users shouldn't have to constantly reorganize the interface just to understand what's happening.

Calm is about reducing unnecessary cognitive load.

Make important things obvious

The most useful information should be easy to see.

What's happening?

What's blocked?

What's changed?

What needs attention?

A good product answers these questions without requiring users to search through menus, filters, and dashboards.

Fewer interruptions

Notifications are useful when they help someone act.

They're frustrating when they simply announce that something happened.

That's why we think notifications should be purposeful.

If something can wait, let it wait.

If something requires action, make that action clear.

If something isn't useful, don't interrupt someone with it.

Build software around attention

Attention is one of the most limited resources people bring to work.

Software should respect it.

That means designing experiences that help people understand, act, and move on.

Not experiences that constantly pull them back.

Our definition

Calmer software is software that helps you feel more in control of your work.

It doesn't make work disappear.

It simply removes some of the unnecessary noise around it.

That's the kind of software we want to build.