You tap the elevator button. Nothing happens. So you tap it again. And again. Even though you know, deep in your rational brain, that the elevator isn't going to arrive faster because of your finger workout. But that little light? The one that glows when you press? That's not really about the elevator. That's about you.

Design is full of these tiny reassurances. Buttons that glow, spinners that spin, checkmarks that appear before anything has actually been checked. They're not just decoration. They're a psychological handshake between the interface and your impatient brain, and understanding them is one of the most powerful tools in a designer's kit.

Here's a fun bit of research: an app that responds in 100 milliseconds but shows nothing feels slower than an app that takes 500 milliseconds but flashes a loading indicator immediately. Your brain doesn't care about the stopwatch. It cares about whether it feels heard.

This is why the best-designed apps acknowledge your tap the instant it happens. A button darkens. A ripple spreads. A tiny spinner appears. Whatever it is, the message is the same: I heard you, I'm on it, please don't tap me eleven more times. Compare this to that one government website we've all suffered through, where clicking submit leads to eight seconds of nothing, then suddenly a new page. Was it working? Did it break? Who knows.

The lesson for anyone making visual choices: prioritize the moment of feedback over the moment of completion. A well-timed acknowledgment buys you enormous patience. Silence, even brief silence, breeds anxiety and rage-clicking.

Takeaway

Speed is a feeling before it's a fact. Design the feedback first, and the underlying performance becomes almost secondary.

When you like a post on Instagram, that little heart fills in instantly. But your phone hasn't actually told Instagram's servers anything yet. It's making a polite assumption: this will probably work, so let's just act like it did. This is called an optimistic update, and it's a tiny act of design confidence.

The reasoning is elegant. Most actions succeed. Sending a message, liking a photo, adding something to a cart — these things almost always work. So why make users wait for confirmation of the obvious? Show them the result immediately. If something goes wrong, quietly walk it back and apologize. The math favors optimism.

For non-designers making decisions about their own tools and forms, this is a mindset shift. Instead of asking how do I confirm this worked?, ask how do I make the successful path feel instant? Handle failure gracefully in the corner, but let success feel like magic. Users will remember the magic, not the rare misfire.

Takeaway

Design for the case that happens 95% of the time, and treat the rare failure with grace rather than warnings.

Ever notice how airport baggage claims are often placed a long walk from the arrival gate? That's not laziness. Airports figured out that if you spend eight minutes walking, then two minutes waiting for bags, you complain less than if you walk two minutes and wait eight. The total time is the same. The feeling is completely different.

Digital design borrows this trick constantly. Skeleton screens show ghostly outlines of content while it loads, so your brain thinks the page is nearly ready. Progress bars fill up (sometimes with completely fictional milestones) to give waiting a sense of momentum. Some apps even show you interesting facts or tips during longer loads, turning dead time into something almost pleasant.

The principle underneath is simple: occupied time feels shorter than unoccupied time. When you can't make something faster, you can still make it feel faster by giving the mind something to do. Even a well-designed animation, one that has rhythm and personality, transforms waiting from suffering into a small performance.

Takeaway

You can't always shorten the wait, but you can almost always shorten how long the wait feels. That distinction is where good design lives.

Speed, it turns out, is less about milliseconds and more about attention. The interfaces we love aren't necessarily the fastest ones. They're the ones that respect our impatience and design around it thoughtfully.

Next time you're building something — a slideshow, a form, a website — ask yourself where the waiting happens. Then ask what you can add, animate, or acknowledge to make that waiting feel like part of the experience rather than a punishment. Your users won't notice the trick. They'll just think you're fast.