How I Treat Waiting as a Design Surface
You’ve probably lived this moment: clicking through a list, trying to delete a batch of items, only to have the buttons shift after each click. What should’ve been a breeze turns into a mild existential crisis. This isn’t a bug—it’s a failure of interface empathy. And it reveals something deeper about speed: it’s not just about response time. It’s about how fast something feels.
Designing for speed, then, is as much about perception as it is about performance. And the two don’t always align.
When Speed Isn’t About Speed
Consider Houston Airport in the 1990s. Passengers kept complaining about baggage delays—even after the airport brought average wait times down to industry norms. Digging deeper, the real issue emerged: people walked for one minute and then stood idly for seven. The airport's solution? Move the gates farther away and send bags to a distant carousel. Now passengers walked longer—and waited less. Complaints dropped to near zero.
Nothing got faster. But the experience felt faster.
In digital products, the same principle applies. Use load screens to communicate progress. Insert subtle animations. Show something—anything—while the system catches up. Time isn’t the enemy. Boredom is.
Designing for Systems You Can’t Fix
Sometimes, you can’t make the backend faster. The legacy system is slow. The APIs are sluggish. So what do you do?
Treat it like a slow elevator.
Most buildings don’t rip out old elevators. They put up mirrors. Or play music. In UX terms, this means:
Reinforce progress (“Uploading 2 of 5 files…”)
Add microcopy or tips during waits
Use placeholders and skeleton loaders
Show the user that something is happening
These interventions don’t eliminate slowness. They reframe it.
Search, Reconsidered
Speed in search isn’t just how fast the results show up. It’s how fast users get what they want. That’s why Google won. It wasn’t just infrastructure. It was simplicity, smart suggestions, and content classification that aligned with how humans think.
The lesson? Fast is not just technical. It’s semantic. Are you organizing things in a way that makes sense to people? Do they feel like they’re making progress?
The Subjective Side of Speed
Users don’t measure milliseconds. They notice:
Clear vs. confusing paths
Blank screens vs. immediate feedback
Wandering vs. directed flow
They also bring their own context. A stressed user trying to complete a critical task will feel even a short delay as excruciating. A relaxed user browsing a store might not notice. The same loading time can feel fine or infuriating, depending on the stakes.
Practical Techniques That Punch Above Their Weight
Compress images, but preserve quality
Group actions logically to reduce scanning time
Use a mix of text and iconography for instant comprehension
Reinforce movement with subtle animations
Use loaders that reassure, not annoy
Let users do something during waiting time
In short: remove ambiguity, not just latency.