The Most Overlooked UX Pattern in Tech

Here’s the problem: Waiting is inevitable.

But the way we handle it? That’s a design decision. And most products today still get it wrong. Generic spinners. Empty “Loading…” messages. Or worse — nothing at all. When users are left in the dark, they don’t just get impatient. They get anxious. Distrustful. Uncertain.

The interface has gone silent. And the brain starts asking:

• “Is this broken?”

• “Did it hear me?”

• “Should I refresh?”

That moment — the psychology of the pause — is one of the most human moments in any digital experience.

Why It Matters

Back in the 1980s, HCI pioneer Brad A. Myers noticed this exact phenomenon. He was working on early graphical interfaces at CMU when he observed something subtle but profound:

Even when the system wasn’t any faster. Even when it was just a bar crawling slowly across the screen. So he helped invent one of the most iconic patterns in UX history:

➡️ The progress bar.

Not because it made systems faster. Because it made users feel seen. And yet decades later, we’ve somehow forgotten that lesson. We’ve traded the reassuring “Here’s what’s happening” for abstract, aesthetic loops. Looking at you, AI dots.

⚫️ An alternative

When designing Seena Labs’ interface, I took Brad’s insight seriously. Even though I did not use a progress bar, I made a loading state that does three things:

1. Moves with purpose (animated brand logo)

2. Speaks with context (microcopy like “Setting up your interview…”)

3. Signals care (the system is working on your behalf)

How to make better loading screens

If you’re designing an AI experience — or any product with pause moments — here’s how to turn silence into trust:

1. Show visible progress: Bar, text, steps — doesn’t matter. Just don’t leave users guessing.

2. Add contextual copy: “Synthesizing your insights…” is better than “Loading…” Be specific, not vague.

3. Avoid fake feedback: If nothing’s happening, don’t animate like it is. Users can tell.

4. Make the wait feel purposeful: Use your brand identity or tone to reinforce care.

5. Treat loading as UX, not just engineering: The system may be paused. But the experience shouldn’t be.

One Last Thought

You don’t need a progress bar. But you do need progress your users can feel. Design it with intention. Because trust isn’t built in features — It’s built in the spaces between.

This one’s personal. Brad Myers was my academic grand-advisor (my PhD Advisor’s Advisor). His work still shapes how I build.