← Archives01 · 1st JULY 2026
Design Psychology

Why a beautiful interface feels faster, even when it isn't

In 1995, two Hitachi researchers tested dozens of ATM interface layouts and asked people to rate how usable each one felt. The best-looking screens won by a wide margin — including several that were objectively harder to operate than the plainer ones sitting next to them.

Written by HET RAJYAGURU
Why a beautiful interface feels faster, even when it isn't
Kurosu and Kashimura's ATMs all ran on identical logic. The only thing that changed between machines was how they looked — and that was enough to change what people believed about how well they worked.
(01)

The finding that embarrassed a lot of usability testing

Masaaki Kurosu and Kaori Kashimura built over two dozen versions of the same ATM interface — same functions, same underlying logic, different visual layouts — and had people rate two separate things: how easy each one actually was to use, measured by task completion, and how easy each one felt to use, based on nothing but looking at it.

The two ratings barely tracked each other. Interfaces people rated as highly usable were, far more often than chance would explain, simply the ones that looked the most put-together. Objective efficiency had a real but much smaller pull on the same rating.

(02)

Your brain treats good looks as a credibility signal

Don Norman's explanation in Emotional Design still holds up: attractive things put people in a better mood, and a better mood makes people more forgiving, more patient, and more willing to work around a small problem instead of concluding the whole product is broken.

That's the mechanism worth remembering — not that beauty makes software faster, but that it changes how much slack a user is willing to extend before deciding something is wrong.

(03)

Where the effect quietly turns into a liability

The same forgiveness that makes a beautiful product pleasant to use also makes its real problems harder to catch. A polished screen earns the benefit of the doubt from whoever is testing it, not just whoever is using it — which is exactly how a broken validation state or a confusing empty state survives a design review that a plainer version wouldn't have.

The fix isn't to make things uglier on purpose. It's noticing when "this feels fine" is quietly standing in for "we checked that this works."

In practice
01

Treat visual polish as a budget for patience, not a substitute for correctness — spend on both.

02

Put the most polish where trust is most fragile: onboarding, payment, anything asking for sensitive information.

03

When a review goes smoothly because a screen "feels" right, that's the moment to check it harder, not less.

The uncomfortable part of this effect is that it works on the people building the product too. A screen that looks finished feels finished — which is exactly when it's worth looking again.

More from the archive

View all →