Doherty Threshold

Productivity soars when a computer and its users interact at a pace (≤400ms) that ensures neither has to wait on the other.

Overview

The Doherty Threshold establishes that a system response time of under 400 milliseconds is the point at which users remain in a state of focused engagement. Above 400ms, users begin to notice the delay — attention drifts, the chain of thought breaks, and the interaction starts to feel sluggish rather than fluid.

This isn't just about user satisfaction. Response time directly affects productivity and perceived quality. A product that consistently responds within 400ms feels fast, intelligent, and reliable. One that regularly exceeds it — even slightly — feels clunky and unpolished regardless of its underlying functionality. The threshold isn't a comfort metric; it's a productivity metric.

Takeaways

01
Provide system feedback within 400ms of user input to maintain engagement and the perception of a responsive interface.
02
Use animation and progress indicators during operations that exceed 400ms — this maintains perceived responsiveness even when the system is working.
03
Perceived performance matters as much as actual performance: optimistic UI updates, skeleton screens, and loading states all keep users engaged while the system catches up.

How to Apply This

Prioritise time-to-first-interaction.
Even if a full page load takes 3 seconds, getting critical content or interactive elements in front of the user within 400ms maintains the sense of responsiveness. Load what matters first — defer everything else.
Use optimistic UI.
Show the result of a user action immediately (before the server confirms it), then reconcile later if needed. This makes interactions feel instant even when network latency means they aren't. Likes, saves, and form submissions are ideal candidates.
Never leave users waiting without feedback.
If a process takes longer than 400ms, acknowledge it. A progress bar, spinner, skeleton screen, or subtle animation signals that the system is working — removing the uncertainty that often feels worse than the wait itself.

Common Misconception

The Doherty Threshold isn't about making everything fast — some tasks genuinely take time. It's about ensuring users always have visual confirmation that the system is responsive. A well-designed loading state can maintain engagement through a 10-second operation; a blank screen at 500ms feels broken.

Origin

The threshold was defined by Walter J. Doherty and Ahrvind J. Thadani in a 1982 IBM Systems Journal paper titled "The Economic Value of Rapid Response Time." Their research found that response times under 400ms significantly improved user productivity — not just satisfaction — because they kept users in a continuous flow state. The economic case they made helped justify the cost of faster hardware at a time when computing time was expensive and measurable.

FAQ

What is the Doherty Threshold?: The Doherty Threshold is the principle that computer systems should respond to user input within 400 milliseconds to maintain a state of flow and peak productivity. Below this threshold, the interaction feels continuous and engaging. Above it, users consciously experience a wait.
Why is 400ms the threshold for UX responsiveness?: 400ms is roughly the point at which a delay becomes consciously perceptible to most users and begins to disrupt their chain of thought. Below 400ms, most people experience the interaction as immediate. The exact figure comes from Doherty and Thadani's 1982 research measuring the productivity impact of system response times.
How do you meet the Doherty Threshold in web design?: Through a combination of technical performance (reducing server response time, optimising assets, using CDNs) and perceived performance (skeleton screens, optimistic UI, instant visual feedback on interaction). Meeting the threshold technically and meeting it perceptually are both valid — and often the latter is faster to ship.
What is the difference between response time and load time?: Load time refers to how long it takes a page or resource to fully load. Response time refers to how quickly the system reacts to a specific user action. The Doherty Threshold applies primarily to response time — the feedback loop between user input and system acknowledgement — rather than to total page load.