CALM: Make Waiting Legible

When a system takes time to become ready, the hardest part is often not the delay itself, but the gap between the action and any readable sign that the system has started moving.

When people are waiting, they are not asking for entertainment; they are asking for evidence that their action was received and that the system is moving toward readiness. Under pressure, a silent or vague transition creates extra glances, manual checks, and restart attempts.

So we make waiting legible: show real progress, name intermediate states clearly, and use motion and sound only when they reduce uncertainty.

In interviews and usability testing, nurses described a patient monitor’s boot-up as feeling long and uncertain. After pressing the power button, the screen stayed static for too long, and the first strong signal was a harsh peak sound at the end.

Our analysis showed that the boot sequence was technically functioning as intended, but the state change was hard to read: there was no immediate acknowledgment, no visible progress, and no clear cue that the monitor was moving toward operating mode. We redesigned the startup experience as a first-class transition, using an animated splash screen and calmer sound cues to make the path to readiness easier to follow.

Every unreadable transition exports verification work: more glances, more restart attempts, and more edge-case recovery.

In follow-up evaluations, nurses described the new startup as more professional and shorter-feeling, even though the underlying boot time changed little. The same pattern shows up in software when a dashboard, workspace, or report is loading: if the system does not show its current state, people fill the gap by rechecking, manually refreshing, and re-verifying.

One thing to remember: A slow wait becomes costly when the system hides its state.

How teams ship this: Define loading, syncing, restoring, stale, and ready as explicit product states, and bind each state to a cue, a meaning, and one trustworthy next step.

Asset: Transition Readiness Review — a simple 5-point checklist for evaluating any high-risk wait or handoff: confirm start, show believable progress, label intermediate states, preserve key context, and make the next reliable action obvious.

Resource: Nielsen Norman Group’s article on the Peak–End Rule helps explain why a boot sequence can feel worse than its raw duration suggests. People tend to remember the most intense moment and the ending, so a vague or abrupt transition leaves a stronger mark than a calm, readable one. That is why legible progress and clear readiness cues can improve the experience even when the underlying system time changes only slightly.

When a system stays silent during an important transition, people do not experience calm. They experience doubt. If this wait had to explain itself without words, would it show what changed, what is still happening, and when you can trust the next step?

Think of one small wait in your day that reliably feels longer than it is.

What first signal tells you the process actually started?

What would let you stop monitoring it?

Next time the wait appears, notice whether the cue lowers your need to check again.

Best,
Andreas Walden

Share this with someone designing for clarity.

P.S. This episode was a little late, which felt almost too on-theme.