Less effort, clear feedback

Response-time limits

Under 0.1 seconds feels instant, under 1 second keeps the flow of thought, and over 10 seconds loses attention.

Well supportedSeveral studies or meta-analyses point the same way.

Example

When a button shows no change, people press it again.

Why it works

The shorter the delay between action and result, the more people feel in control. Long waits break the flow and invite abandonment. A 1982 IBM report found that faster responses raised user productivity more than proportionally.

On the web

Change the button the moment it is pressed. Show progress for anything over a second, and remaining time plus a way to cancel beyond ten.

When it backfires

A fast visual response followed by a slow result widens the gap with expectations. Add deliberate delay only where the labor illusion genuinely applies.

Sources

  1. Sets out the 0.1, 1, and 10 second limits based on earlier research.

    Nielsen, J. (1993). Response Times: The 3 Important Limits. Nielsen Norman Group. Open source

  2. Reports that user productivity rose more than proportionally as system response time fell.

    Doherty, W. J., & Thadani, A. J. (1982). The Economic Value of Rapid Response Time. IBM. Open source

  3. Treats 200 milliseconds or less from interaction to next paint as good.

    web.dev. Interaction to Next Paint (INP). Open source

Connect with the classics

These links are editorial readings, not research findings. Check the original meaning on each classics page.

兵聞拙速,未睹巧之久也。

Clumsy speed is known in war; clever delay has never been seen to win. Respond immediately before polishing.

Sunzi · The Art of War Waging war: the cost of duration →

Patterns that apply it

4 patterns