Doherty Threshold
Productivity and engagement rise sharply when a system responds in under about 400 milliseconds, so neither the user nor the computer is left waiting on the other.
Key takeaways
- Aim for feedback within 400 ms for every user action.
- When real work takes longer, respond instantly with progress, skeletons or optimistic UI.
- Perceived speed matters as much as measured speed.
Origin
Walter J. Doherty and Ahrvind J. Thadani, researchers at IBM, published 'The Economic Value of Rapid Response Time' in 1982. They found that when system response time fell below roughly 400 ms, people worked faster and stayed engaged instead of switching attention while they waited.
How to apply it
- Give visible feedback to every tap or click within about 100 milliseconds, even if the full result takes longer.
- Aim for core interactions to complete in under 400 milliseconds, and measure real-user performance, not just lab results.
- Use optimistic UI for actions that almost always succeed, with clear recovery if they fail.
- Use skeleton screens and progress indicators for longer waits, and explain what is happening for waits over a few seconds.
- Prioritise loading what users need first and defer the rest.
How Science of Apps uses this law
5 checks in every investigation rely on Doherty Threshold, for example: “Does every action give immediate feedback, and long operations show progress?”
Get your product investigated