Skip to content
Back to blog
Insights

Software is finally getting slower on purpose

For two decades we treated every millisecond of friction as a bug. Some of the best products of the past year add it back — deliberately, and with good reason.

Priya Raman

Head of Design

Published
Reading time
3 min
A small hourglass standing in gravel, with blue sand running through it
Photograph via Unsplash

There is a button in our own product that takes about 600 milliseconds to do something it could do in twenty. We put the delay there on purpose, and it is the change that has generated the fewest support tickets of anything we shipped this year.

The button confirms a payout. For years it was instant: click, done. It was also the single most common source of the sentence "I didn't mean to do that." Now it holds for a beat, shows the amount and destination, and lets the person back out. Completion rates didn't move. Regret did.

The religion of speed

Product teams of my generation were raised on a simple creed: speed is a feature, friction is a tax, and every extra step costs you a percentage of users. That creed produced real gains. Checkout flows got shorter. Sign-up forms lost half their fields. Entire categories of software became usable by people who would have given up in 2008.

But a creed that has no exceptions eventually starts to cause harm. We optimized so thoroughly for doing that we neglected deciding. The same frictionlessness that makes it easy to send a message makes it easy to send the wrong one to the wrong person.

A close-up of a steel watch face with a running second hand
Time spent is not the same as time wasted.Photograph via Unsplash

Three kinds of useful friction

Not all friction is the same, and it's worth being precise. In the products we admire, deliberate slowness tends to fall into one of three buckets.

1. Friction that lets you notice

A short pause before an irreversible action — a payout, a deletion, a publish — turns an automatic gesture into a decision. The pause doesn't have to be long. It has to be perceptible, and it has to show the person what they are about to do.

2. Friction that signals effort

We trust results more when we can see that work was done. Several search and analysis tools now show their reasoning as it happens, even when the answer was ready sooner. Users rate the same answer as more reliable when it arrives with a visible trail.

People don't want the answer faster. They want to believe the answer.

— A researcher we interviewed in September

3. Friction that protects the system

Rate limits, cooling-off periods and review queues are friction the product asks for, on behalf of everyone else. These are the least popular and the most necessary. The trick is to explain them like a colleague would, not enforce them like a bouncer.

How to tell good friction from bad

We use three questions when someone proposes adding, or removing, a step. They aren't a formula — they're a way of making the argument concrete.

  • Who benefits? If the person doing the task doesn't benefit, the friction needs a very good explanation.
  • Is it proportional? The cost of the pause should scale with the cost of the mistake.
  • Can it be skipped by experts? The best friction is a default, not a wall.

None of this is an argument for slow software. It's an argument for intentional software, where every second the user spends has an owner and a reason. The goal was never to be fast. It was to be unhurried where it matters and invisible everywhere else.

Written by

Priya Raman

Head of Design

Priya leads product and brand design. She is interested in the unglamorous parts of interfaces: empty states, error messages and the second visit.

Keep reading

All stories