CALM: Protecting Purpose Under Pressure

At the start of the year, it’s worth asking a quiet but consequential question:
What should a system help people do—without asking them to think about the system itself?

A system’s job is not to display everything it can do. It’s to make the most important work easy to complete—quickly, confidently, and under pressure.

That is the strategic choice. Miller’s Law is the guardrail that protects it: working memory is limited, and when interfaces exceed that limit, capability turns into friction.

Years ago, while redesigning a patient monitor UI, we were given a larger, higher-resolution display. The obvious move was to add more fast-access buttons to the core navigation at the bottom. Instead, we treated the space as a safety budget.

We limited the core navigation to a maximum of seven buttons, increased touch target size to reduce use errors, and switched to single-line labels for faster scanning. The older design used a carousel—multiple pages of buttons. In theory it was flexible; in reality it hid state. Whenever we spoke with nurses, they consistently described feeling disoriented—they couldn’t tell where they were, and that uncertainty slowed them down.

So we replaced the carousel with progressive disclosure. Secondary functions moved behind a clear “More” button—available when needed, but no longer fragmenting orientation or demanding recall. Nurses consistently described the redesign as calmer and easier to use—faster to scan, easier to hit, and less disorienting because the core navigation stayed stable while secondary actions lived behind “More.”

By doing so, we protected the system’s purpose. We also reduced decision time. As discussed in the previous episode on Hick’s Law, every additional visible choice slows action and increases hesitation. Fewer primary options meant faster recognition and more confident action when seconds mattered.

When we later asked nurses what they actually do most often with patient monitors, the answer was remarkably consistent: a small set of actions, repeated constantly, under pressure.

This is the strategic leap.

Miller’s Law tells us what not to exceed.
Purpose defines the focus.

High-performance systems behave less like instruction manuals—listing everything that’s possible—and more like flight checklists. They foreground the specific actions needed in critical moments. Everything else remains accessible, but never competes for attention at the wrong time.

Designing within human memory means shaping the core navigation around real use, making the state visible, and letting the system carry context forward. Calm systems reduce what people must hold in mind. The interface does the remembering.

Asset: Purpose-First Interface Checklist
Use this to turn observation into design decisions—across healthcare, enterprise software, or consumer tools.

Resource: Miller’s Law — “The Magical Number Seven, Plus or Minus Two”
Miller’s Law is often treated as a numeric rule. In practice, it’s a design instrument: a way to protect the actions that matter most from being diluted by excess choice and hidden state. Use it not to count buttons, but to defend clarity where purpose is highest.

In the product, service, or interface you are shaping, which elements quietly compete for attention without supporting what truly matters—and what could step aside so the critical actions stay clear and available when pressure rises?

Pick one interface you use often. In one sentence, name its true purpose. Then look at the visible buttons and options and ask: Which of these directly support that purpose, right now? Choose one element that does not, and reduce it—remove it, group it, or move it behind “More.” Finally, check the result: Would a user now need to remember less to do the right thing?

Best,
Andreas Walden

Share this with someone designing for clarity.