A user can spend no time clicking while reading carefully, waiting for a response, using speech input or deciding what to do. Event silence therefore cannot stand in for wasted time.
The original event log lasts100 seconds:40 seconds observable interaction,28 service waiting,24 reading or thinking and8 facilitator clarification. The four non-overlapping intervals reconcile to the whole clock.
GOV.UK, NIST and W3C sources ground usability timing, effectiveness, interaction-event coverage and the need to allow different users enough time.
The method preserves start and stop rules, overlap, assistance, accessibility support, task outcome and missing or censored attempts.
This specialist guide belongs to the User Experience root. It also connects to The Gold Standard of Education | Learning That Transfers into Life and the How X Works hub. The worked cases are original teaching examples; their numbers are stipulated so that the reasoning can be checked.
eduKateSG · User Experience
Find your next learning step
Elapsed time follows the whole task clock; active interaction time counts only intervals defined as observable input. Reading, thinking, system waiting, facilitator talk and interruptions need their own labels rather than being called idle.
ROUTE 1 · CHAPTERS 1–5
Define the quantities
Fix the objects, units, bases and first worked distinction.
ROUTE 2 · CHAPTERS 6–10
Trace the mechanism
Follow the mechanism and complete the central worked example.
ROUTE 3 · CHAPTERS 11–15
Control the comparison
Preserve settings, sampling, model choice and rival explanations.
ROUTE 4 · CHAPTERS 16–20
Audit the evidence
Carry uncertainty, receipts, reporting rules and decision boundaries.
ROUTE 5 · CHAPTERS 21–24
Transfer and continue
Repair shortcuts, change context and follow verified reading routes.
Chapter contents
Define the quantities · Chapters 1–5
2. Define observable interaction time
3. Define system waiting separately
Trace the mechanism · Chapters 6–10
6. Complete the central time ledger
7. Avoid calling residual time idle
Control the comparison · Chapters 11–15
11. Choose the denominator for completion time
12. Separate task time from page performance
13. Account for event-log gaps
Audit the evidence · Chapters 16–20
16. Keep moderator assistance in the outcome record
17. Compare builds with matched rules
18. Work the changed-build example
Transfer and continue · Chapters 21–24
21. Repair the less time is always better shortcut
22. Build the complete timing receipt
Begin with the quantities the observation or calculation actually supplies. Elapsed task time begins and ends at stated task events; it can include interaction, reading, waiting, conversation and pauses.
Work the original teaching case in a visible order. The fictional task starts at 0 seconds and completes at 100 seconds.
Check the result through evidence another reader can inspect. Record the start and stop rule before testing.
Test transfer by changing one consequential condition while holding the question fixed. Start the clock at first page load instead of after instructions and compare.
Keep the limit explicit. A time metric without event rules cannot be reproduced.
The evidence receipt for “Define the task clock” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
Separate the objects before deciding whether two numbers disagree. Active interaction time is the sum of intervals classified as observable input under a stated coding rule.
Work the original teaching case in a visible order. Keyboard, pointer and touch activity spans 0–18 and 70–92 seconds, totalling 40 seconds.
Check the result through evidence another reader can inspect. Retain the event log and interval-merging rule.
Test transfer by changing one consequential condition while holding the question fixed. Count scrolling as active in one justified variant.
Keep the limit explicit. No input event does not mean no cognitive work.
The evidence receipt for “Define observable interaction time” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
Name the mechanism and the reporting basis before interpreting the result. Service waiting covers intervals where a response needed for progress is outstanding under the study protocol.
Work the original teaching case in a visible order. The system wait runs from 18 to 46 seconds, totalling 28 seconds.
Check the result through evidence another reader can inspect. Mark request and response events and check overlapping operations.
Test transfer by changing one consequential condition while holding the question fixed. Reduce that wait to 8 seconds in a changed build.
Keep the limit explicit. Network or server telemetry may not capture every perceived wait.
The evidence receipt for “Define system waiting separately” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
Keep observation, transformation and decision in different ledger columns. Time without input can include comprehension, planning, memory search or visual inspection.
Work the original teaching case in a visible order. From 46 to 70 seconds the participant reads and thinks for 24 seconds in the observation notes.
Check the result through evidence another reader can inspect. Use video, screen and facilitator notes cautiously.
Test transfer by changing one consequential condition while holding the question fixed. Present a shorter paragraph and observe a new interval.
Keep the limit explicit. An observer cannot directly read a participant’s mental state.
The evidence receipt for “Keep reading and thinking visible” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
Use the short answer only after the unit, denominator and scope are fixed. Moderator speech can consume elapsed time and may be neutral, clarifying, accessibility-related or task-revealing.
Work the original teaching case in a visible order. Eight seconds of closing clarification occur from 92 to 100 seconds.
Check the result through evidence another reader can inspect. Timestamp the words and code their function separately from participant input.
Test transfer by changing one consequential condition while holding the question fixed. Remove the clarification in the changed run.
Keep the limit explicit. Do not infer the causal effect of a hint from one chronology.
The evidence receipt for “Distinguish facilitator talk” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
Begin with the quantities the observation or calculation actually supplies. Elapsed time is 100 seconds; active interaction is 40; explicit service wait is 28; the remaining 32 covers reading, thinking and facilitator time.
Work the original teaching case in a visible order. The components 40+28+24+8 reconcile to 100 seconds.
Check the result through evidence another reader can inspect. Require non-overlapping intervals or state how overlaps are handled.
Test transfer by changing one consequential condition while holding the question fixed. If service wait drops by 20 seconds with all else fixed, elapsed becomes 80.
Keep the limit explicit. The decomposition is descriptive and does not rank the participant.
The evidence receipt for “Complete the central time ledger” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
Separate the objects before deciding whether two numbers disagree. Residual intervals may contain essential interpretation, decision-making, accessibility-tool use or off-screen work.
Work the original teaching case in a visible order. The 24-second no-input interval precedes a correct next action.
Check the result through evidence another reader can inspect. Review evidence before assigning a category.
Test transfer by changing one consequential condition while holding the question fixed. Ask the participant to describe the interval after completion.
Keep the limit explicit. Retrospective explanation can be incomplete or influenced by later events.
The evidence receipt for “Avoid calling residual time idle” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
Name the mechanism and the reporting basis before interpreting the result. Totals alone cannot show whether waiting blocked progress or happened while another useful action was possible.
Work the original teaching case in a visible order. A 28-second request begins only after the user submits required data.
Check the result through evidence another reader can inspect. Plot intervals on one timeline.
Test transfer by changing one consequential condition while holding the question fixed. Allow the user to work on another section during the request.
Keep the limit explicit. The same wait total can have a different experience when work overlaps.
The evidence receipt for “Preserve chronology” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
Keep observation, transformation and decision in different ledger columns. Parallel reading, animation and network requests require a rule so component times do not falsely sum beyond elapsed time.
Work the original teaching case in a visible order. Ten seconds of reading overlap a background request.
Check the result through evidence another reader can inspect. Report wall-clock union and category-specific totals separately.
Test transfer by changing one consequential condition while holding the question fixed. Make the request blocking, removing overlap.
Keep the limit explicit. Category totals may legitimately exceed elapsed time if overlap is permitted and disclosed.
The evidence receipt for “Handle overlapping activity” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
Use the short answer only after the unit, denominator and scope are fixed. A group summary should preserve skew, failures, censoring and task differences rather than rely on one average.
Work the original teaching case in a visible order. Five elapsed times are 60,70,80,90 and180 seconds; median is80 and mean96.
Check the result through evidence another reader can inspect. Show the small sample and individual spread.
Test transfer by changing one consequential condition while holding the question fixed. Add a 300-second cap and mark censoring.
Keep the limit explicit. A lower median does not establish a better experience for every participant.
The evidence receipt for “Use medians and distributions carefully” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
CHAPTER 11 OF 24 · Control the comparison
11. Choose the denominator for completion time
Begin with the quantities the observation or calculation actually supplies. Time among successful attempts answers a different question from time across all starts with a timeout rule.
Work the original teaching case in a visible order. Seven of ten complete; the success-time median excludes three non-completions.
Check the result through evidence another reader can inspect. Report completion rate beside time.
Test transfer by changing one consequential condition while holding the question fixed. Treat timeouts as the cap only in a labelled analysis.
Keep the limit explicit. Dropping failures can make a difficult flow appear fast.
The evidence receipt for “Choose the denominator for completion time” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
CHAPTER 12 OF 24 · Control the comparison
12. Separate task time from page performance
Separate the objects before deciding whether two numbers disagree. Browser performance metrics describe technical milestones or event latency, not the whole user task.
Work the original teaching case in a visible order. An event lasts 120 ms while the full task takes 100 seconds.
Check the result through evidence another reader can inspect. Keep telemetry names and clocks distinct.
Test transfer by changing one consequential condition while holding the question fixed. Improve event latency without changing confusing instructions.
Keep the limit explicit. Fast events do not prove usable task completion.
The evidence receipt for “Separate task time from page performance” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
Name the mechanism and the reporting basis before interpreting the result. Keyboard and pointer logs omit reading, speech, assistive technology and actions outside the instrumented surface.
Work the original teaching case in a visible order. The event stream captures 40 seconds while observation accounts for the rest.
Check the result through evidence another reader can inspect. Document instrumentation coverage.
Test transfer by changing one consequential condition while holding the question fixed. Add screen-reader speech timestamps with participant consent.
Keep the limit explicit. More telemetry can burden privacy and still miss intent.
The evidence receipt for “Account for event-log gaps” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
CHAPTER 14 OF 24 · Control the comparison
14. Treat accessibility support as designed service
Keep observation, transformation and decision in different ledger columns. Planned support or assistive technology may be part of the intended path rather than contamination.
Work the original teaching case in a visible order. A participant uses speech input for 25 seconds under the normal service design.
Check the result through evidence another reader can inspect. Record the support type without equating duration with deficit.
Test transfer by changing one consequential condition while holding the question fixed. Compare the same task after a labeling repair.
Keep the limit explicit. Cross-user speed rankings can be unfair and misleading.
The evidence receipt for “Treat accessibility support as designed service” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
CHAPTER 15 OF 24 · Control the comparison
15. Separate interruptions from task difficulty
Use the short answer only after the unit, denominator and scope are fixed. An external interruption lengthens elapsed time but may say little about the interface.
Work the original teaching case in a visible order. A phone call pauses the task from 40 to 70 seconds.
Check the result through evidence another reader can inspect. Mark pause rules and provide summaries with and without excluded interruption.
Test transfer by changing one consequential condition while holding the question fixed. Move testing to a controlled room.
Keep the limit explicit. Excluding every interruption can erase realistic context.
The evidence receipt for “Separate interruptions from task difficulty” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
CHAPTER 16 OF 24 · Audit the evidence
16. Keep moderator assistance in the outcome record
Begin with the quantities the observation or calculation actually supplies. A task-revealing hint can change both completion category and elapsed time.
Work the original teaching case in a visible order. The participant completes at 100 seconds after a hint at 75 seconds.
Check the result through evidence another reader can inspect. Report unaided completion and post-assistance completion separately.
Test transfer by changing one consequential condition while holding the question fixed. Give only neutral encouragement in another session.
Keep the limit explicit. The difference is not a causal estimate without an appropriate design.
The evidence receipt for “Keep moderator assistance in the outcome record” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
Separate the objects before deciding whether two numbers disagree. Time changes are interpretable only when task wording, start/stop, participants, device and classification stay comparable or differences are modelled.
Work the original teaching case in a visible order. Build A median elapsed is100 seconds; Build B is90 under the same coding rules.
Check the result through evidence another reader can inspect. Audit allocation and environment.
Test transfer by changing one consequential condition while holding the question fixed. Use a new participant mix and observe the loss of comparability.
Keep the limit explicit. A ten-second difference may reflect sampling variation.
The evidence receipt for “Compare builds with matched rules” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
Name the mechanism and the reporting basis before interpreting the result. The new build cuts service wait from28 to8 seconds but active interaction rises from40 to50 and elapsed becomes90.
Work the original teaching case in a visible order. Technical waiting improves by20 seconds; total elapsed improves by10 because interaction adds10.
Check the result through evidence another reader can inspect. Reconcile components before declaring the mechanism.
Test transfer by changing one consequential condition while holding the question fixed. Also shorten reading by5 seconds to predict85 elapsed.
Keep the limit explicit. A faster total does not reveal whether extra interaction is clearer or more burdensome.
The evidence receipt for “Work the changed-build example” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
Keep observation, transformation and decision in different ledger columns. Small usability studies reveal mechanisms well but do not support precise population timing claims without a suitable design.
Work the original teaching case in a visible order. Four participants show elapsed changes of -20,-5,+10 and-15 seconds.
Check the result through evidence another reader can inspect. Display individual paths and task outcomes.
Test transfer by changing one consequential condition while holding the question fixed. Recruit a broader confirmatory sample if a population estimate is needed.
Keep the limit explicit. Statistical precision cannot fix a mismatched task definition.
The evidence receipt for “Carry uncertainty and sample size” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
Use the short answer only after the unit, denominator and scope are fixed. Raw interaction logs, recordings and assistive-technology traces can contain sensitive content.
Work the original teaching case in a visible order. The teaching receipt stores interval labels rather than typed text.
Check the result through evidence another reader can inspect. Apply consent, minimisation, access control and retention rules.
Test transfer by changing one consequential condition while holding the question fixed. Remove unnecessary keystroke content while retaining timestamps.
Keep the limit explicit. De-identification may be imperfect when sequences are distinctive.
The evidence receipt for “Protect privacy in timing evidence” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
CHAPTER 21 OF 24 · Transfer and continue
21. Repair the less time is always better shortcut
Begin with the quantities the observation or calculation actually supplies. Deliberate reading or verification can raise time while reducing errors or uncertainty.
Work the original teaching case in a visible order. A confirmation screen adds12 seconds and prevents an irreversible mistake in the fictional test.
Check the result through evidence another reader can inspect. Measure success, error recovery and confidence alongside time.
Test transfer by changing one consequential condition while holding the question fixed. Make the action reversible and reconsider the confirmation.
Keep the limit explicit. The desirable balance depends on task consequences.
The evidence receipt for “Repair the less time is always better shortcut” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
Separate the objects before deciding whether two numbers disagree. The receipt names task, participant conditions, device, clock source, start/stop, event classes, overlap rule, assistance and outcome.
Work the original teaching case in a visible order. The 100-second example can be reconstructed from four intervals.
Check the result through evidence another reader can inspect. Have another analyst recode a sample.
Test transfer by changing one consequential condition while holding the question fixed. Change one classification and report sensitivity.
Keep the limit explicit. Agreement on codes does not prove the study generalises.
The evidence receipt for “Build the complete timing receipt” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
Name the mechanism and the reporting basis before interpreting the result. A service can contain multiple pages, waits and offline steps, so page time is only one segment.
Work the original teaching case in a visible order. A ten-minute journey contains two minutes of form entry, five of service wait and three of review.
Check the result through evidence another reader can inspect. Use one journey timeline and preserve handoffs.
Test transfer by changing one consequential condition while holding the question fixed. Move identity verification offline.
Keep the limit explicit. The relevant boundary depends on the user’s real goal.
The evidence receipt for “Transfer to a service journey” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
Keep observation, transformation and decision in different ledger columns. Elapsed-versus-active time complements articles on assistance chronology and counterbalancing.
Work the original teaching case in a visible order. Follow the hint article when completion changes after help and the counterbalancing article when task order changes learning.
Check the result through evidence another reader can inspect. Keep each reader job with its substantive owner.
Test transfer by changing one consequential condition while holding the question fixed. Move from descriptive timing to a designed comparative study.
Keep the limit explicit. This article owns time decomposition and its limits.
The evidence receipt for “Continue through verified UX routes” records the source observation, the transformation, the changed-context prediction and the claim boundary on separate lines. For User Experience, the receipt retains the event chronology and denominator so a technical wait, cognitive interval and moderator action cannot collapse into one unexplained total.
Continue through the verified reading route
Unaided completion and recovery after a hint
Unaided completion and recovery after a hint. Use this when the outcome changes after moderator assistance.
Counterbalancing and task learning
Counterbalancing and task learning. Use this when repeated tasks create order and carryover effects.
The User Experience subject guide
The User Experience subject guide. Return here for the broader effectiveness, efficiency and satisfaction framework.
Frequently asked questions
Is no-input time idle time?
No. It can contain reading, thinking, speech, assistive-technology activity or waiting.
Can active interaction exceed elapsed time?
Category totals can exceed elapsed time only when overlapping intervals are allowed and clearly disclosed.
Should failed tasks be dropped from timing summaries?
Report completion alongside time and state how timeouts or censored attempts are handled.
Does a faster task prove a better experience?
No. Check success, errors, recovery, accessibility and task consequences as well.
Authoritative sources and further reading
GOV.UK usability benchmarking. Official guidance on measuring completion and time within a defined benchmark.
NIST Usability Testing. Official usability context grounded in effectiveness, efficiency and satisfaction.
W3C Event Timing API. Technical specification showing the scope of captured interaction-event timing.
W3C Understanding Enough Time. Accessibility guidance explaining why people need sufficient time for interaction and response.
Return to the User Experience subject guide, The Gold Standard of Education, or the How X Works hub.