Doherty Threshold
The principle from IBM research that system response times under 400 milliseconds keep users in a state of flow and productivity, while delays beyond this threshold break concentration and reduce engagement.
What Is the Doherty Threshold?
A 1982 IBM Research report by Walter Doherty and Arvind Thadani found that when system response times fell below 400 milliseconds, productivity and user satisfaction jumped dramatically. Below this threshold, interactions feel instantaneous and users enter a flow state. Above it, each additional millisecond of delay is a perceptible interruption that breaks concentration. This single threshold has become one of the most cited benchmarks in performance-driven UX.
Also Known As
- UX and design: "flow threshold," "instant-feel target"
- Product and engineering: "400ms budget," "responsiveness SLA"
- Marketing and growth: "page speed impact on conversion"
- Performance teams: "interaction latency target"
How It Works
A filtering feature on an ecommerce site takes 1.2 seconds to repaint results after a user clicks a category. Users click, wait, lose their mental thread, sometimes click again thinking nothing happened (double-filtering), and bounce rates climb. Engineering adds optimistic UI — the filter visually applies instantly while the API call resolves in the background — and perceived latency drops below 400ms. Engagement with filters and downstream conversions both rise without any actual speed improvement beyond perception.
Best Practices
- Budget for 400ms response on every click, tap, filter, and form interaction; instrument and alert when exceeded.
- Use optimistic UI, skeleton screens, and progressive loading to maintain the feel of responsiveness even when the network is slow.
- Show immediate visual feedback (button press state, spinner within 100ms) so the user knows the click registered.
- Prioritize first-interaction latency over average latency; a fast initial response sets expectations for the session.
Common Mistakes
- Optimizing only total page load time while ignoring post-load interaction latency, where most flow breaks occur.
- Showing a full-screen spinner for sub-second operations, which actually emphasizes delay instead of hiding it.
Industry Context
SaaS and B2B: dashboard filters, search-as-you-type, and document saves all live and die by the Doherty Threshold; slow tools train users to multitask elsewhere. Ecommerce and DTC: PDP variant swaps, filter application, and cart updates must feel instant — delays here depress add-to-cart rates. Lead generation: form field validation and autocomplete suggestions need sub-400ms response or users lose confidence.
The Behavioral Science Connection
Flow state (Csikszentmihalyi) requires continuous feedback; latency above 400ms pulls attention out of the task and into waiting, which shifts the user from System 1 engagement to System 2 skepticism.
Key Takeaway
Every interaction should feel instant within 400ms — real speed when possible, perceived speed (optimistic UI, skeletons) when not.