Doherty Threshold
Productivity soars when a computer and its users interact at a pace (<400ms) that ensures that neither has to wait on the other.
In 1982 Walter J. Doherty and Ahrvind J. Thadani published, in the IBM Systems Journal, a research paper that set the requirement for computer response time to be 400 milliseconds, not 2,000 (2 seconds) which had been the previous standard. When a human being’s command was executed and returned an answer In under 400 milliseconds, it was deemed to exceed the Doherty threshold, and use of such applications was deemed to be “addicting” to users.
Provide system feedback within 400ms in order to keep users’ attention and increase productivity.
Computer performance improved and response times started to fall under 2 seconds. At IBM, Walter Doherty noticed a beautiful consequence from the improve performance — a massive increase in productivity. He then ran a series of studies to measure the impact.
It turns out that the time the computer took to process a request was highly correlated with the user response time (the time it took the user to type in the next command). In other words, the longer the computer took to respond, the longer the user took to think of what he wanted to do next! Even a few hundred milliseconds in system response time made a huge difference.
Doherty suspected that was happening because a user was storing the series of steps he wanted to take in his working memory. The long system response times were an interruption that made him lose his train of thought and ultimately caused lower productivity.
At one time it was thought that a relatively slow response, up to two seconds, was acceptable because the person was thinking about the next task. Research on rapid response time now indicates that this earlier theory is not borne out by the facts: productivity increases in more than direct proportion to a decrease in response time. This brief describes some of this research and the implications for increasing productivity and cutting costs that are among the chief challenges of business today.
Resources:
Jim Elliott’s Blog
Computer World Magazine, June 1984
Comments
Post a Comment