← Back to list

Why Faster Is Not Always Better

A simple idea called Labor Perception Bias, and what it taught me about designing trust.

Ankur · 2026-06-10 04:25 · 0 claps · 2.7 min read
#ux-design #user-psychology #research
Open on Medium ↗
Wiki topics: SAF · Safety & Alignment UX · UI/UX Design PSY · Psychology 📊 · Economic Policy

Why Faster Is Not Always Better

A simple idea called Labor Perception Bias, and what it taught me about designing trust.

Imagine you order a fancy dish at a nice restaurant, and the waiter brings it in fifteen seconds. Are you impressed? No. You are suspicious. “Did they just microwave this?”

That small doubt is the whole idea. And once you see it, you will notice it everywhere, especially on your phone.

The idea has a name

It is called Labor Perception Bias. People trust and value a result more when they can see the work behind it. When something finishes too fast, we quietly stop believing it. This comes from research on the “labor illusion,” studied at Harvard in 2011.

Software does the same thing. There was a time when a popular tool could import lakhs of contacts in a flash. Sounds great, but users panicked. The screen said “Done” instantly, and people thought, “Wait, did that actually work?”

The fix is to show the work

Good products put the effort on display instead of hiding it.

Think of a delivery app. Order food on Swiggy or book a ride on Uber, and you see a live screen. “Confirmed. Preparing. Rider on the way. Arriving in 18 minutes.” Your food does not cook any faster because of that tracker. But the wait now feels handled, not broken.

What the data says

That 2011 Harvard study found that a good “show the work” effect can raise perceived value by about 15%. One honest warning, though: that is the best case, not a promise. The real lift depends on your users, the wait, and the task. So treat it as a reason to test the idea yourself, not a number to copy.

But here is the catch

This is where people go wrong. It only works when the user expects the task to be hard. Sending money. Big reports. Migrations. The moment you use it on a simple, everyday task, it stops helping and starts annoying.

I will tell you from my own work. I design admin tools for event ticketing. Picture a box office checking in two thousand guests at one gate. For that staff member, a reassuring animation after every scan is not comforting. It is a wall. They want the green tick instantly, so the queue keeps moving. Here, speed is the trust signal. The same idea that builds trust in a money app would ruin a ticket gate.

The line you must not cross

One more thing, and it matters most. Showing the work must be honest.

In the 2016 US election, a news website showed a live forecast needle. The data is updated every 15 seconds, but the needle keeps twitching about 10 times a second. That shaking created a sense of nervous uncertainty, which kept people glued to the page. That is not reassurance. That is manufactured anxiety dressed up as live data. Use this idea to reassure people, never to manipulate them.

The real skill

The lesson is not “add loading screens everywhere.” It is judgment. Know the few moments where your user expects effort, show it only there, keep everything else fast, and keep it honest.

Reassure people when the stakes are high. Get out of their way when they are not. That is the whole game.

I am Ankur Vadadoriya, a product and UX designer. If this made you look at your favorite apps a little differently, that was the idea.


메타데이터
post_id
2b689bf890fa
slug
why-faster-is-not-always-better-2b689bf890fa
url
https://medium.com/@ankur_vadadoriya/why-faster-is-not-always-better-2b689bf890fa
canonical_url
https://medium.com/@ankur_vadadoriya/why-faster-is-not-always-better-2b689bf890fa
author_url
https://medium.com/@ankur_vadadoriya
status
ok
fetched_at
2026-06-22 05:41:33