The Doherty Threshold: Why 400ms Is the UX Magic Number
When system response time drops below 400ms, productivity and engagement sharply increase. Explore the Doherty Threshold and how performance UX shapes product success.
What Is the Doherty Threshold?
In 1982, Walter Doherty and Ahrvind Thadani published research showing that productivity and user engagement dramatically increase when a computer responds to user input in under 400 milliseconds. At this speed, the interaction feels continuous — the user maintains their flow state and does not disengage to wait. Above 400ms, users begin to notice the delay; above 1000ms (1 second), the cognitive thread breaks entirely.
"Productivity soars when a computer and its users interact at a pace (<400ms) that ensures that neither has to wait on the other."— Walter Doherty & Ahrvind Thadani, 1982 / Laws of UX
Flow State and Interaction Pace
Csikszentmihalyi's concept of flow — complete immersion in a challenging but manageable task — requires uninterrupted momentum. Every time your interface makes a user wait beyond the threshold, you risk breaking that state. In creative tools, data-heavy dashboards, and any product where users work in sustained sessions, the Doherty Threshold is not a nice-to-have; it's the difference between a tool users love and one they endure.
Response Time Guidelines
- 0–100ms: Feels instantaneous. Users perceive the response as caused by their own action.
- 100–300ms: Slight perceptible lag but generally accepted. Most micro-interactions should target this.
- 300–1000ms: User notices delay. Show a loading indicator if response will take more than 300ms.
- 1000ms+: User's flow breaks. Show a progress bar or spinner; explain what's happening.
- 10,000ms+: Explain the delay and offer a way to notify when complete (email/notification).
Design Techniques for Perceived Performance
- Optimistic UI: Update the interface immediately on user action; confirm with the server in the background. (Instagram likes, Twitter retweets.)
- Skeleton screens: Show a structural placeholder before content loads — perceived as faster than a blank spinner.
- Lazy loading: Load what's visible first; defer below-the-fold content.
- Animation as bridge: A 200ms transition can mask a 300ms network call, keeping the interaction within threshold.
Key Takeaways
- Sub-400ms responses maintain user flow; above that, engagement and productivity drop.
- Performance is a UX feature — measure it and design for it deliberately.
- Optimistic UI and skeleton screens improve perceived performance even when actual load time is unchanged.
- Animation can bridge sub-threshold delays without adding cognitive overhead.
Response time thresholds: 0–100ms feels instant, 100–300ms barely perceptible, 300–1000ms noticeable, 1000ms+ breaks user flow.
