Measurement

Time on Task

A UX metric for understanding how long users take to complete a defined task under evaluation conditions.

Concept facts

Time on task records the elapsed time users take to complete a defined task under evaluation conditions.

Also known as
Task time, completion time, task duration.
Used in
Usability testing, benchmark studies, workflow review, transaction evaluation, and efficiency analysis.
Interpret with
Task success, error rate, user satisfaction, assistance, task complexity, and context of use.

Plain-language explanation

Time on task measures duration, not quality by itself. A shorter time can indicate efficiency, but it can also hide rushing, confusion, incorrect completion, or skipped steps.

Timing is most useful when tasks, conditions, and measurement points are consistent enough to compare responsibly.

Why it matters

Time matters in service journeys where people may be under pressure, using a mobile device, paying for data, working through a deadline, or handling high-stakes information.

Use contexts

  • Benchmarking a redesigned flow against an existing flow.
  • Reviewing long forms or portals.
  • Comparing prototype variants.
  • Understanding effort in support-heavy journeys.

Application guidance

Define when timing starts and stops. Time on task is primarily an efficiency indicator and must be interpreted alongside task success and error conditions. Interpret duration with task success, errors, assistance, and user confidence. Avoid treating speed as the only goal when accuracy, trust, accessibility, or understanding matter more.

Practical example

A hospital appointment portal allows patients to request follow-up visits after receiving a referral. In testing, most participants eventually complete the task, but they spend a long time moving between specialty names, doctor availability, and required referral documents.

The time on task shows that completion is possible but inefficient. In a health-service context, the delay may increase anxiety, missed appointments, or unnecessary phone calls to hospital staff.

Interpretive boundaries

  • Faster is not always better.
  • Time on task is sensitive to task complexity and user context.
  • Timing comparisons require consistent task definitions.
  • Time on task alone does not establish satisfaction or accessibility.

Applied at Userhub

Time on task can help Userhub evaluate whether high-effort digital journeys are becoming easier to complete without sacrificing accuracy or understanding.

See Userhub UX Lab for applied UX research and evaluation context.

Sources and references

  • ISO. (2018). Ergonomics of human-system interaction – Part 11: Usability: Definitions and concepts (ISO Standard No. 9241-11:2018). International Organization for Standardization.
  • Card, S. K., Moran, T. P., & Newell, A. (1983). The Psychology of Human-Computer Interaction. Lawrence Erlbaum Associates.
  • Hornbæk, K. (2006). Current practice in measuring usability: Challenges to usability research and applications. International Journal of Human-Computer Studies, 64(2), 79-102. https://doi.org/10.1016/j.ijhcs.2005.06.002
  • Frøkjær, E., Hertzum, M., & Hornbæk, K. (2000). Measuring usability: Are effectiveness, efficiency, and satisfaction really correlated? Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, 345-352. https://doi.org/10.1145/332040.332455

Cite this entry

APA

Userhub. (2026). Time on Task. UX Reference. https://userhub.com.bd/reference/time-on-task/