Run a lightweight observed task session
Observe a realistic task, identify concrete failures, and choose a change to test next.
- Preparation
- Preparation, sessions, and a review round
- Steps
- 7
- Difficulty
- Moderate
- Task
- Observe a realistic user task
Requires: Choose a prototype that can answer the research question. Confirm consent, recording, accessibility, and data-handling arrangements.
Uses: Google Sheets
Back to the Task: Observe a realistic user taskBefore you start
Prepare
- Choose a prototype that can answer the research question.
- Confirm consent, recording, accessibility, and data-handling arrangements.
Steps
Work through the method
Use the listed inputs and tools. Check the evidence when you need to verify a step.
Define the realistic task
Write a scenario with a goal, starting state, and observable completion condition.
Step details and sources
Why it matters: The task needs a clear relationship to the research question.
- Input
- The key user job and prototype state.
- Output
- A task scenario and completion condition.
Tools in this stepGoogle SheetsEvidence for this step
GOV.UK guidance links a prototype to a research question and asks participants to attempt realistic tasks.
GOV.UK: How to carry out usability testingParticipant guidance is contextual and should not become a fixed rule.
Recruit likely users
Screen for people who would plausibly attempt this task in the relevant context.
Step details and sources
Why it matters: Selection affects what the team can infer from the session.
- Input
- The task scenario and participant criteria.
- Output
- Consented participants with relevant experience.
Tools in this stepGoogle SheetsEvidence for this step
GOV.UK guidance recommends recruiting actual or likely users and selecting a route that fits the research need.
GOV.UK Service Manual: Choosing the best approaches to find participants; Inviting existing usersConsent, procurement, and inclusion duties vary by context.Google Design describes quick prototype conversations and warns about selection and disclosure effects.
Google Design: Test prototypes with quick conversationsThis is vendor-authored practice guidance.
Prepare the prototype and fallback
Set the prototype to the required starting state and prepare a safe response for broken paths.
Step details and sources
Why it matters: A predictable setup keeps prototype failures distinct from facilitation problems.
- Input
- The prototype and task scenario.
- Output
- A tested session setup.
Tools in this stepGoogle SheetsEvidence for this step
GOV.UK guidance links a prototype to a research question and asks participants to attempt realistic tasks.
GOV.UK: How to carry out usability testingParticipant guidance is contextual and should not become a fixed rule.
Observe without coaching
Give the task, let the participant act, and record any facilitator intervention separately.
Step details and sources
Why it matters: Coaching can change the behaviour under study.
- Input
- The participant, task, and prototype.
- Output
- A chronological observation record.
Tools in this stepGoogle SheetsEvidence for this step
GOV.UK guidance links a prototype to a research question and asks participants to attempt realistic tasks.
GOV.UK: How to carry out usability testingParticipant guidance is contextual and should not become a fixed rule.Google Design describes quick prototype conversations and warns about selection and disclosure effects.
Google Design: Test prototypes with quick conversationsThis is vendor-authored practice guidance.
Ask after the attempt
Ask what the participant expected at hesitation, error, abandonment, and completion points.
Step details and sources
Why it matters: The follow-up connects observed behaviour with the participant’s account.
- Input
- The observation record.
- Output
- Source-linked comments for key moments.
Tools in this stepGoogle SheetsEvidence for this step
Google Design describes quick prototype conversations and warns about selection and disclosure effects.
Google Design: Test prototypes with quick conversationsThis is vendor-authored practice guidance.
Group common errors carefully
Group similar observed failures and retain the participant codes and contrary cases.
Step details and sources
Why it matters: A repeated pattern must remain traceable to individual sessions.
- Input
- De-identified observation records.
- Output
- An evidence-linked problem list.
Tools in this stepGoogle SheetsEvidence for this step
GOV.UK guidance separates extracted observations, sorted themes, findings, and resulting actions.
GOV.UK Service Manual: Extract observations; Sort observations; Determine findings; Decide actionsThe sequence may need adaptation for a solo founder.
Choose a change to retest
Select one change tied to a supported problem and define the same task for the next round.
Step details and sources
Why it matters: The session should end with an inspectable change and another test.
- Input
- The problem list and prototype constraints.
- Output
- A change hypothesis and retest task.
Tools in this stepGoogle SheetsEvidence for this step
GOV.UK guidance links a prototype to a research question and asks participants to attempt realistic tasks.
GOV.UK: How to carry out usability testingParticipant guidance is contextual and should not become a fixed rule.
Success checks
Check the result
- The task has an observable completion condition.
- Facilitator interventions remain visible in the record.
- Each proposed change links to observed behaviour.
Failure modes
What could go wrong
- Revise the task when participants fail because the scenario lacks required context.
- Report accessibility or prototype failures separately from product findings.
- Recruit a different group when selection limits block the intended inference.
Tools
Choose tools
Google Sheets
A shared spreadsheet for source-linked research, decisions, and operating records that people can inspect and correct.
Check fit, limits and pricingSources
Check the sources
Check what each source supports and where the advice has limits.
- Hacker News: Ask HN: Do you find it challenging to talk to your users?First-hand community discussion · Published 28 April 2022
- GOV.UK Service Manual: Finding participants for user researchGovernment service guidance · Publication date unavailable
- GOV.UK: Usability testing: qualitative studiesGovernment guidance · Publication date unavailable
- Google Design: Global UX Research TipsVendor-authored practice guidance · Publication date unavailable
- GOV.UK Service Manual: Analyse a research sessionGovernment service guidance · Publication date unavailable
- Google Workspace: Share files from Google DriveOfficial help documentation · Publication date unavailable