What is the Doherty threshold in UX design?
The Doherty threshold was established by Walter Doherty and Ahrvind Thadani in a 1982 IBM Systems Journal paper. It states that computer productivity soars and user engagement increases significantly when system response times drop below 400 milliseconds. Above this threshold, users experience the interface as sluggish and begin to disengage. The threshold represents the boundary between a system that feels responsive and one that feels like it is making users wait.
Why does the Doherty threshold matter for UX design?
Response time is one of the most powerful factors in perceived quality and user satisfaction. Users who experience fast, responsive interfaces rate them as more capable, more trustworthy, and more enjoyable to use, even when functionality is identical to a slower alternative. Response times above the Doherty threshold interrupt the user's cognitive load management and break the sense of direct manipulation that makes digital interfaces feel natural.
What should designers do when response times exceed 400ms?
When technical constraints make response times above 400ms unavoidable, designers should use feedback to maintain the user's sense of engagement. Skeleton screens and progress indicators communicate that the system is working and provide a sense of forward movement. Optimistic UI patterns update the interface immediately to reflect the expected result of an action while the actual processing happens in the background, making the interaction feel instantaneous even when it isn't. Animation and transitions can also mask latency by giving users something to watch during brief waits.
How does the Doherty threshold relate to Core Web Vitals?
Google's Core Web Vitals, particularly Largest Contentful Paint and Interaction to Next Paint, are directly related to the Doherty threshold. They measure how quickly pages load and respond to user interactions, and they affect search rankings. Meeting Core Web Vitals standards and designing within the Doherty threshold are largely aligned goals: both require minimizing the time between user action and system response.