Reading a Fast Task Time Paired with a High Error Count
In a usability test, a participant completes a task quickly — well under the target time — but racks up several wrong turns and backtracks along the way, each one corrected fast.
Read completion rate, time-on-task, and error rate together, what does this specific pattern most likely mean?
The correct answer is "The participant got lucky recovering from confusion, not that the design works well."
This is the pattern this subject calls out explicitly: high completion, low time, high errors describes a participant who stumbled into several mistakes and happened to recover from all of them quickly — not a design that's actually clear. Time-on-task alone would make this look like a clean success; only reading it alongside the error count reveals the confusion the fast completion time was hiding.
The distractors misread the combination: a fast time doesn't override a high error rate as evidence the design "works well" — that's exactly the trap of reading time-on-task in isolation; errors are diagnostic precisely when a task is otherwise completed, not a signal to discard the time metric; and nothing about this pattern means the task was untestable — it means the design, not the test, needs a second look.
Share this question