Usability Task Runner
Set a task objective and observable success criterion before a session. Assign a pseudonymous participant code, start and stop each attempt, then explicitly record the observed outcome and issue point. The report calculates task and session completion success rates and elapsed wall-clock time. Corrections append a reason and revised observation while preserving the first record. This tool does not infer whether a participant truly succeeded.
Key features
- Task objective and success-criterion snapshots attached to each attempt
- Pseudonymous sessions and explicit start/stop wall-clock timestamps
- Observed success, failure or abandonment with notes and required failure point
- Append-only correction records preserving the original outcome and notes
- Per-task and per-session success, elapsed-time and failure-point summaries
- Strict versioned JSON restoration and formula-safe CSV report
How to use
- Load the two-participant example or start a blank study and enter a study title.
- Add tasks with an objective and a measurable success criterion. Create a session using a pseudonymous participant code.
- Choose a session and task, start the attempt, then stop it and explicitly record success, failure or abandonment, notes and a failure point where needed.
- Review task and session success rates, elapsed time and issue clusters. Open an attempt to inspect any original and corrected observations.
- If an observation was wrong, select the completed attempt, enter a reason and revised values, then append a correction. Download JSON for continuation or CSV for review.
Use cases
- Observe whether people find a product and add it to a cart
- Compare task success and elapsed time across anonymized sessions
- Locate repeated navigation or form failure points
- Correct an observer's mistaken outcome without erasing the first entry
Frequently asked questions
Does this tool decide whether a participant succeeded?
No. The researcher writes a success criterion before the attempt and explicitly selects the observed outcome at stop time. Success rate is successful completed attempts divided by all completed attempts, including failures and abandonments. Active attempts are excluded.
What does elapsed time measure?
It is the difference between recorded UTC start and stop wall-clock timestamps. It includes tab-hidden time and pauses because the tool has no pause action. Average time uses completed attempts only. Timing is not a measurement of attention or precise user activity.
What happens when I edit a task after running it?
New attempts use the revised task definition. Every existing attempt keeps the task title, objective and success criterion captured when it started, so its interpretation does not silently change.
Can I correct an outcome or time?
Yes. Select a stopped attempt, enter a reason and revised UTC timestamps, outcome, observation or failure point. A correction is appended to the attempt and the original remains visible. The latest correction drives summary metrics. This is an editable local record, not a tamper-proof audit trail.
Are participant identities collected or uploaded?
The field accepts a short pseudonymous code such as P03, not a name. The browser cannot guarantee that you did not enter an identifying code or sensitive notes. No study data is sent to a server or saved automatically; exported files are under your control.
What can be imported?
Only this tool's version 1 project JSON with valid tasks, sessions, attempts and correction history can restore a study. Duplicate JSON keys, bad references and malformed timestamps are rejected without replacing the current study. CSV is a report, not an import format.
Privacy
Study tasks, participant codes, observations and notes remain in this browser tab. There is no remote collection or automatic save. Avoid identifying details; download JSON before leaving and handle exported files securely.
Comments & questions