The Click of the Kettle: Waiting as a Design Material

This morning, as I waited for the kettle to boil, I watched the red switch hold its breath. There was no spinning throbber, no percentage crawl. Just a still chrome dome and the promise of a sound. Then, the click. A definitive, physical, satisfying punctuation mark that meant the process—the only one I cared about—was complete. The water’s actual temperature was irrelevant; the click was the event. It made me wonder: on the web, what is our click? Where is that clean, honest signal that the thing you wanted has happened?

We talk about performance as a race, a relentless shaving of milliseconds. But the human experience of waiting isn't just about duration; it's about certainty. A three-second load with no indication of life feels infinitely longer than a five-second load with calm, credible progress. The kettle doesn't humiliate us with a false ‘90% complete’ only to stall. It is silent, then decisive. Our interfaces often fail at both: they chatter with skeleton screens that dance meaninglessly, or they stay stubbornly blank, abandoning the user in a void of uncertainty.

The Honest Interval

This is about more than a loading spinner. It’s about identifying the ‘honest interval’—the genuine, unavoidable processing gap—and owning it with design. A form submission, a search filter applying, a comment posting. These are our kettles. They require a moment. The worst thing we can do is pretend they don't, to paint over the gap with an immediate but fake state. The user will discover the deceit when they try to interact with a facade.

Instead, what if we designed the click itself? The moment the button depresses, it could change not to a shaky ‘loading...’ but to a quiet, immutable ‘processing.’ The state is locked, the action acknowledged, the wait sanctioned. It has the weight of the kettle’s switch. The user’s mental model shifts from “Is it broken?” to “It is working.” The interface borrows the kettle’s authority.

We have fetishized perceived performance, sometimes at the cost of truthful performance. We lazy-load, we skeletonize, we promise above-the-fold miracles while the real content gathers itself. But the click—the moment of intent—is sacred. It is the contract. To honour that contract, we must sometimes do the unpopular thing: declare a brief, clear pause. We must design the waiting, not just try to hide it.

The kettle’s click works because it is a sensory full stop. It appeals to our innate understanding of mechanical cause and effect. Our digital ‘clicks’ feel ephemeral, lost in abstraction. By designing the honest interval—giving it a clear start, a reliable, non-frantic middle, and a definitive end—we build not just speed, but trust. We build an interface that, like a good kettle, doesn't keep you guessing.

Notes & further reading

A few pages I came back to while writing this: