WHY ENGLISH?
Turn a design question into realistic tasks, careful observation and findings the team can act on
A usability test plan explains what a team will test, with whom, through which tasks, under what conditions and how observations will inform a decision. English matters because the plan must avoid coaching participants, keep research questions distinct from interface steps and describe evidence precisely enough for moderators and observers to work consistently.
Digital.gov’s current usability-testing guide defines the method as observing users attempting tasks while thinking aloud. It asks teams to align on scenarios, participant recruitment, moderator and observer roles, consent, a test script, debriefs and collaborative synthesis. Its metrics guidance separates quantitative indicators such as time on task from qualitative evidence such as ratings and user comments. W3C adds an important boundary: testing with disabled people reveals barriers that conformance checks may miss, but user testing alone cannot establish standards conformance.
This article uses a fictional polytechnic scholarship-search prototype. It does not certify accessibility, produce statistically representative performance estimates or replace security, privacy and ethical review. Clear English helps a team observe what actually happens and report the scope honestly; thoughtful recruitment, accessible technology and responsible decisions must support the plan.
Article contents
Open all chapters
- 1. Name the Product Decision the Test Can Inform
- 2. Choose Formative or Summative Purpose
- 3. Write Research Questions Before Tasks
- 4. Define Participant Characteristics and Access Needs
- 5. Choose the Right Prototype Fidelity
- 6. Write Scenarios With a Real Goal
- 7. Keep Tasks Independent and Ordered Carefully
- 8. Define Behavioural and Verbal Evidence
- 9. Select Measures That Fit the Decision
- 10. Prepare Consent, Privacy and Data Handling
- 11. Write the Moderator Script and Neutral Prompts
- 12. Define Observer Behaviour and the Issues Log
- 13. Pilot the Technology, Tasks and Timing
- 14. Facilitate Without Teaching the Interface
- 15. Debrief and Synthesize Across Sessions
- 16. Report Scope, Accessibility and Next Decision
ORIENTATION
What this guide covers
Current fact check
Checked on 8 November 2026, Digital.gov’s official guidance described usability testing as observing users attempting tasks while thinking aloud and recommended planning scenarios, participants, roles, consent, scripts, sessions, debriefs and synthesis. W3C said evaluation with disabled users should complement, not replace, standards conformance evaluation.
What this guide does not cover
This article covers a moderated formative usability test plan for one digital service or prototype. It does not own user research interview guides, accessibility conformance audits, A/B tests, software QA test cases, survey design, analytics plans or final product acceptance.
Worked example
Every chapter returns to a fictional polytechnic prototype that helps students compare scholarship eligibility, documents and deadlines before deciding which official opportunity pages to open. It is fictional, low-stakes and educational; it does not report a real school, clinical decision or guaranteed outcome.
Did You Know? For a usability test plan, precise wording helps different people reproduce the same reader journey while keeping limits visible.
Warm up with eduKate’s guides to explaining scientific evidence and asking better questions in class.
CHAPTER 1 OF 16
1. Name the Product Decision the Test Can Inform
Why this move matters
State which design choice may change and what the team does not expect the session to prove.
Did You Know? A precise decision gives observations somewhere to land.
Define the decision before the session
State which design choice may change and what the team does not expect the session to prove. State what design decision the test can inform, which user goal matters and what evidence would support change. A plan prevents the team from collecting observations without knowing how they will be used.
Write tasks as realistic goals
In the worked service, The test can inform filters and deadline wording, not whether every student qualifies for a scholarship. Give participants a situation and desired outcome without naming the interface control or route the team wants them to discover.
Observe, measure and debrief carefully
Record behaviour, errors, recovery, comments and relevant measures separately. Let the participant think aloud, keep observers quiet during the session and compare notes immediately afterwards.
Report scope and accessibility honestly
Usability evidence supports judgement rather than automatically choosing a design. Include participant characteristics, assistive technology, task conditions and unresolved barriers. User testing complements standards evaluation; it does not certify universal accessibility.
Practical reader check
- Point to the exact source or method sentence supporting the claim.
- Name the person, setting, date, input and decision rule that could change its meaning.
- Label the remaining uncertainty reported, inferred, contested or unknown.
Student, parent and career transfer
Make one evidence card for “Name the Product Decision the Test Can Inform”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports UX research, content design, service design, product management, software development, accessibility and student technology projects without promising a grade, admission, funding decision or job.
CHAPTER 2 OF 16
2. Choose Formative or Summative Purpose
Why this move matters
Decide whether the study explores problems for iteration or measures performance against defined criteria.
Did You Know? Purpose changes tasks, measures, sample and conclusions.
Define the decision before the session
Decide whether the study explores problems for iteration or measures performance against defined criteria. State what design decision the test can inform, which user goal matters and what evidence would support change. A plan prevents the team from collecting observations without knowing how they will be used.
Write tasks as realistic goals
In the worked service, The early prototype uses formative testing to locate confusing eligibility and deadline paths. Give participants a situation and desired outcome without naming the interface control or route the team wants them to discover.
Observe, measure and debrief carefully
Record behaviour, errors, recovery, comments and relevant measures separately. Let the participant think aloud, keep observers quiet during the session and compare notes immediately afterwards.
Report scope and accessibility honestly
A small formative session should not be dressed as a benchmark study. Include participant characteristics, assistive technology, task conditions and unresolved barriers. User testing complements standards evaluation; it does not certify universal accessibility.
Practical reader check
- Point to the exact source or method sentence supporting the claim.
- Name the person, setting, date, input and decision rule that could change its meaning.
- Label the remaining uncertainty reported, inferred, contested or unknown.
Student, parent and career transfer
Make one evidence card for “Choose Formative or Summative Purpose”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports UX research, content design, service design, product management, software development, accessibility and student technology projects without promising a grade, admission, funding decision or job.
CHAPTER 3 OF 16
3. Write Research Questions Before Tasks
Why this move matters
Express what the team needs to learn without naming the expected interface behaviour.
Did You Know? Tasks become less leading when the question is settled first.
Define the decision before the session
Express what the team needs to learn without naming the expected interface behaviour. State what design decision the test can inform, which user goal matters and what evidence would support change. A plan prevents the team from collecting observations without knowing how they will be used.
Write tasks as realistic goals
In the worked service, Can students distinguish eligibility information from application instructions? Give participants a situation and desired outcome without naming the interface control or route the team wants them to discover.
Observe, measure and debrief carefully
Record behaviour, errors, recovery, comments and relevant measures separately. Let the participant think aloud, keep observers quiet during the session and compare notes immediately afterwards.
Report scope and accessibility honestly
A research question may need several tasks or evidence types. Include participant characteristics, assistive technology, task conditions and unresolved barriers. User testing complements standards evaluation; it does not certify universal accessibility.
Practical reader check
- Point to the exact source or method sentence supporting the claim.
- Name the person, setting, date, input and decision rule that could change its meaning.
- Label the remaining uncertainty reported, inferred, contested or unknown.
Student, parent and career transfer
Make one evidence card for “Write Research Questions Before Tasks”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports UX research, content design, service design, product management, software development, accessibility and student technology projects without promising a grade, admission, funding decision or job.
CHAPTER 4 OF 16
4. Define Participant Characteristics and Access Needs
Why this move matters
Recruit people connected to the service context and plan assistive technology, language and support with them.
Did You Know? Recruitment criteria belong to the product question, not convenience alone.
Define the decision before the session
Recruit people connected to the service context and plan assistive technology, language and support with them. State what design decision the test can inform, which user goal matters and what evidence would support change. A plan prevents the team from collecting observations without knowing how they will be used.
Write tasks as realistic goals
In the worked service, Participants include current students who have searched for funding, including keyboard and screen-reader users. Give participants a situation and desired outcome without naming the interface control or route the team wants them to discover.
Observe, measure and debrief carefully
Record behaviour, errors, recovery, comments and relevant measures separately. Let the participant think aloud, keep observers quiet during the session and compare notes immediately afterwards.
Report scope and accessibility honestly
A few participants cannot represent every disability or student pathway. Include participant characteristics, assistive technology, task conditions and unresolved barriers. User testing complements standards evaluation; it does not certify universal accessibility.
Practical reader check
- Point to the exact source or method sentence supporting the claim.
- Name the person, setting, date, input and decision rule that could change its meaning.
- Label the remaining uncertainty reported, inferred, contested or unknown.
Student, parent and career transfer
Make one evidence card for “Define Participant Characteristics and Access Needs”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports UX research, content design, service design, product management, software development, accessibility and student technology projects without promising a grade, admission, funding decision or job.
CHAPTER 5 OF 16
5. Choose the Right Prototype Fidelity
Why this move matters
Use the least complete artefact that can support the research question without pretending unavailable functions work.
Did You Know? High visual polish can create confidence that the underlying journey has not earned.
Define the decision before the session
Use the least complete artefact that can support the research question without pretending unavailable functions work. State what design decision the test can inform, which user goal matters and what evidence would support change. A plan prevents the team from collecting observations without knowing how they will be used.
Write tasks as realistic goals
In the worked service, A clickable prototype supports comparison and deadline tasks but labels external application as unavailable. Give participants a situation and desired outcome without naming the interface control or route the team wants them to discover.
Observe, measure and debrief carefully
Record behaviour, errors, recovery, comments and relevant measures separately. Let the participant think aloud, keep observers quiet during the session and compare notes immediately afterwards.
Report scope and accessibility honestly
Prototype limitations can shape behaviour and must be recorded. Include participant characteristics, assistive technology, task conditions and unresolved barriers. User testing complements standards evaluation; it does not certify universal accessibility.
Practical reader check
- Point to the exact source or method sentence supporting the claim.
- Name the person, setting, date, input and decision rule that could change its meaning.
- Label the remaining uncertainty reported, inferred, contested or unknown.
Student, parent and career transfer
Make one evidence card for “Choose the Right Prototype Fidelity”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports UX research, content design, service design, product management, software development, accessibility and student technology projects without promising a grade, admission, funding decision or job.
CHAPTER 6 OF 16
6. Write Scenarios With a Real Goal
Why this move matters
Give context and motivation without revealing the interface label or expected route.
Did You Know? A task is not a set of instructions when discovery is what the team wants to observe.
Define the decision before the session
Give context and motivation without revealing the interface label or expected route. State what design decision the test can inform, which user goal matters and what evidence would support change. A plan prevents the team from collecting observations without knowing how they will be used.
Write tasks as realistic goals
In the worked service, You have found two scholarships and need to check which one requires a referee before Friday. Give participants a situation and desired outcome without naming the interface control or route the team wants them to discover.
Observe, measure and debrief carefully
Record behaviour, errors, recovery, comments and relevant measures separately. Let the participant think aloud, keep observers quiet during the session and compare notes immediately afterwards.
Report scope and accessibility honestly
A fictional scenario should still be plausible and respectful. Include participant characteristics, assistive technology, task conditions and unresolved barriers. User testing complements standards evaluation; it does not certify universal accessibility.
Practical reader check
- Point to the exact source or method sentence supporting the claim.
- Name the person, setting, date, input and decision rule that could change its meaning.
- Label the remaining uncertainty reported, inferred, contested or unknown.
Student, parent and career transfer
Make one evidence card for “Write Scenarios With a Real Goal”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports UX research, content design, service design, product management, software development, accessibility and student technology projects without promising a grade, admission, funding decision or job.
CHAPTER 7 OF 16
7. Keep Tasks Independent and Ordered Carefully
Why this move matters
Avoid allowing an early task to teach the solution to a later one and balance learning, fatigue and risk.
Did You Know? Task order can create the success it appears to measure.
Define the decision before the session
Avoid allowing an early task to teach the solution to a later one and balance learning, fatigue and risk. State what design decision the test can inform, which user goal matters and what evidence would support change. A plan prevents the team from collecting observations without knowing how they will be used.
Write tasks as realistic goals
In the worked service, The plan tests deadline finding before comparison controls reveal additional labels. Give participants a situation and desired outcome without naming the interface control or route the team wants them to discover.
Observe, measure and debrief carefully
Record behaviour, errors, recovery, comments and relevant measures separately. Let the participant think aloud, keep observers quiet during the session and compare notes immediately afterwards.
Report scope and accessibility honestly
Some natural journeys require linked tasks; document the dependence. Include participant characteristics, assistive technology, task conditions and unresolved barriers. User testing complements standards evaluation; it does not certify universal accessibility.
Practical reader check
- Point to the exact source or method sentence supporting the claim.
- Name the person, setting, date, input and decision rule that could change its meaning.
- Label the remaining uncertainty reported, inferred, contested or unknown.
Student, parent and career transfer
Make one evidence card for “Keep Tasks Independent and Ordered Carefully”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports UX research, content design, service design, product management, software development, accessibility and student technology projects without promising a grade, admission, funding decision or job.
CHAPTER 8 OF 16
8. Define Behavioural and Verbal Evidence
Why this move matters
List actions, errors, recovery, questions and comments the team will record without turning each event into a score.
Did You Know? Observation and interpretation should occupy different columns.
Define the decision before the session
List actions, errors, recovery, questions and comments the team will record without turning each event into a score. State what design decision the test can inform, which user goal matters and what evidence would support change. A plan prevents the team from collecting observations without knowing how they will be used.
Write tasks as realistic goals
In the worked service, Observers note first click, rereading, filter changes, source-page checks and participant explanation. Give participants a situation and desired outcome without naming the interface control or route the team wants them to discover.
Observe, measure and debrief carefully
Record behaviour, errors, recovery, comments and relevant measures separately. Let the participant think aloud, keep observers quiet during the session and compare notes immediately afterwards.
Report scope and accessibility honestly
Silence does not prove understanding, and speech can change task performance. Include participant characteristics, assistive technology, task conditions and unresolved barriers. User testing complements standards evaluation; it does not certify universal accessibility.
Practical reader check
- Point to the exact source or method sentence supporting the claim.
- Name the person, setting, date, input and decision rule that could change its meaning.
- Label the remaining uncertainty reported, inferred, contested or unknown.
Student, parent and career transfer
Make one evidence card for “Define Behavioural and Verbal Evidence”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports UX research, content design, service design, product management, software development, accessibility and student technology projects without promising a grade, admission, funding decision or job.
CHAPTER 9 OF 16
9. Select Measures That Fit the Decision
Why this move matters
Use completion, error, time, path or rating only when definitions and collection methods are clear.
Did You Know? A metric is useful when it answers a decision question, not because software can count it.
Define the decision before the session
Use completion, error, time, path or rating only when definitions and collection methods are clear. State what design decision the test can inform, which user goal matters and what evidence would support change. A plan prevents the team from collecting observations without knowing how they will be used.
Write tasks as realistic goals
In the worked service, The formative plan records task outcome and critical misunderstandings, with time used descriptively. Give participants a situation and desired outcome without naming the interface control or route the team wants them to discover.
Observe, measure and debrief carefully
Record behaviour, errors, recovery, comments and relevant measures separately. Let the participant think aloud, keep observers quiet during the session and compare notes immediately afterwards.
Report scope and accessibility honestly
Small samples rarely support precise population estimates. Include participant characteristics, assistive technology, task conditions and unresolved barriers. User testing complements standards evaluation; it does not certify universal accessibility.
Practical reader check
- Point to the exact source or method sentence supporting the claim.
- Name the person, setting, date, input and decision rule that could change its meaning.
- Label the remaining uncertainty reported, inferred, contested or unknown.
Student, parent and career transfer
Make one evidence card for “Select Measures That Fit the Decision”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports UX research, content design, service design, product management, software development, accessibility and student technology projects without promising a grade, admission, funding decision or job.
CHAPTER 10 OF 16
10. Prepare Consent, Privacy and Data Handling
Why this move matters
Explain recording, observation, storage, sharing, withdrawal and any sensitive scenario before the session.
Did You Know? Usability convenience does not override research dignity.
Define the decision before the session
Explain recording, observation, storage, sharing, withdrawal and any sensitive scenario before the session. State what design decision the test can inform, which user goal matters and what evidence would support change. A plan prevents the team from collecting observations without knowing how they will be used.
Write tasks as realistic goals
In the worked service, Participants choose whether screen and voice are recorded and may stop without penalty. Give participants a situation and desired outcome without naming the interface control or route the team wants them to discover.
Observe, measure and debrief carefully
Record behaviour, errors, recovery, comments and relevant measures separately. Let the participant think aloud, keep observers quiet during the session and compare notes immediately afterwards.
Report scope and accessibility honestly
Governance requirements vary by organisation and participant group. Include participant characteristics, assistive technology, task conditions and unresolved barriers. User testing complements standards evaluation; it does not certify universal accessibility.
Practical reader check
- Point to the exact source or method sentence supporting the claim.
- Name the person, setting, date, input and decision rule that could change its meaning.
- Label the remaining uncertainty reported, inferred, contested or unknown.
Student, parent and career transfer
Make one evidence card for “Prepare Consent, Privacy and Data Handling”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports UX research, content design, service design, product management, software development, accessibility and student technology projects without promising a grade, admission, funding decision or job.
CHAPTER 11 OF 16
11. Write the Moderator Script and Neutral Prompts
Why this move matters
Plan welcome, consent check, think-aloud instruction, tasks, follow-up and close in spoken language.
Did You Know? A script protects consistency while leaving room to listen.
Define the decision before the session
Plan welcome, consent check, think-aloud instruction, tasks, follow-up and close in spoken language. State what design decision the test can inform, which user goal matters and what evidence would support change. A plan prevents the team from collecting observations without knowing how they will be used.
Write tasks as realistic goals
In the worked service, The moderator asks “What are you thinking?” rather than “Did you notice the filter?” Give participants a situation and desired outcome without naming the interface control or route the team wants them to discover.
Observe, measure and debrief carefully
Record behaviour, errors, recovery, comments and relevant measures separately. Let the participant think aloud, keep observers quiet during the session and compare notes immediately afterwards.
Report scope and accessibility honestly
Moderators still need judgement when a participant is distressed or stuck. Include participant characteristics, assistive technology, task conditions and unresolved barriers. User testing complements standards evaluation; it does not certify universal accessibility.
Practical reader check
- Point to the exact source or method sentence supporting the claim.
- Name the person, setting, date, input and decision rule that could change its meaning.
- Label the remaining uncertainty reported, inferred, contested or unknown.
Student, parent and career transfer
Make one evidence card for “Write the Moderator Script and Neutral Prompts”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports UX research, content design, service design, product management, software development, accessibility and student technology projects without promising a grade, admission, funding decision or job.
CHAPTER 12 OF 16
12. Define Observer Behaviour and the Issues Log
Why this move matters
Keep observers from interrupting, decide how questions reach the moderator and record evidence consistently.
Did You Know? Quiet observers reduce the feeling of being examined.
Define the decision before the session
Keep observers from interrupting, decide how questions reach the moderator and record evidence consistently. State what design decision the test can inform, which user goal matters and what evidence would support change. A plan prevents the team from collecting observations without knowing how they will be used.
Write tasks as realistic goals
In the worked service, Observers log timestamp, task, behaviour, quote and possible issue, then debrief after the session. Give participants a situation and desired outcome without naming the interface control or route the team wants them to discover.
Observe, measure and debrief carefully
Record behaviour, errors, recovery, comments and relevant measures separately. Let the participant think aloud, keep observers quiet during the session and compare notes immediately afterwards.
Report scope and accessibility honestly
The issue label remains provisional until the team compares evidence. Include participant characteristics, assistive technology, task conditions and unresolved barriers. User testing complements standards evaluation; it does not certify universal accessibility.
Practical reader check
- Point to the exact source or method sentence supporting the claim.
- Name the person, setting, date, input and decision rule that could change its meaning.
- Label the remaining uncertainty reported, inferred, contested or unknown.
Student, parent and career transfer
Make one evidence card for “Define Observer Behaviour and the Issues Log”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports UX research, content design, service design, product management, software development, accessibility and student technology projects without promising a grade, admission, funding decision or job.
CHAPTER 13 OF 16
13. Pilot the Technology, Tasks and Timing
Why this move matters
Run the entire plan with the intended device, prototype, recording and assistive technology before participants arrive.
Did You Know? Testing the test is part of ethical preparation.
Define the decision before the session
Run the entire plan with the intended device, prototype, recording and assistive technology before participants arrive. State what design decision the test can inform, which user goal matters and what evidence would support change. A plan prevents the team from collecting observations without knowing how they will be used.
Write tasks as realistic goals
In the worked service, The pilot finds a keyboard trap in the prototype and repairs it before testing. Give participants a situation and desired outcome without naming the interface control or route the team wants them to discover.
Observe, measure and debrief carefully
Record behaviour, errors, recovery, comments and relevant measures separately. Let the participant think aloud, keep observers quiet during the session and compare notes immediately afterwards.
Report scope and accessibility honestly
A pilot cannot remove every production or participant-specific problem. Include participant characteristics, assistive technology, task conditions and unresolved barriers. User testing complements standards evaluation; it does not certify universal accessibility.
Practical reader check
- Point to the exact source or method sentence supporting the claim.
- Name the person, setting, date, input and decision rule that could change its meaning.
- Label the remaining uncertainty reported, inferred, contested or unknown.
Student, parent and career transfer
Make one evidence card for “Pilot the Technology, Tasks and Timing”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports UX research, content design, service design, product management, software development, accessibility and student technology projects without promising a grade, admission, funding decision or job.
CHAPTER 14 OF 16
14. Facilitate Without Teaching the Interface
Why this move matters
Use neutral encouragement, allow productive struggle and apply a pre-agreed rescue rule when continuing adds no value.
Did You Know? A rescue should be visible in the record because it changes the evidence.
Define the decision before the session
Use neutral encouragement, allow productive struggle and apply a pre-agreed rescue rule when continuing adds no value. State what design decision the test can inform, which user goal matters and what evidence would support change. A plan prevents the team from collecting observations without knowing how they will be used.
Write tasks as realistic goals
In the worked service, After a stopping threshold, the moderator ends the task and asks what the participant expected. Give participants a situation and desired outcome without naming the interface control or route the team wants them to discover.
Observe, measure and debrief carefully
Record behaviour, errors, recovery, comments and relevant measures separately. Let the participant think aloud, keep observers quiet during the session and compare notes immediately afterwards.
Report scope and accessibility honestly
Safety, distress and access needs can require earlier intervention. Include participant characteristics, assistive technology, task conditions and unresolved barriers. User testing complements standards evaluation; it does not certify universal accessibility.
Practical reader check
- Point to the exact source or method sentence supporting the claim.
- Name the person, setting, date, input and decision rule that could change its meaning.
- Label the remaining uncertainty reported, inferred, contested or unknown.
Student, parent and career transfer
Make one evidence card for “Facilitate Without Teaching the Interface”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports UX research, content design, service design, product management, software development, accessibility and student technology projects without promising a grade, admission, funding decision or job.
CHAPTER 15 OF 16
15. Debrief and Synthesize Across Sessions
Why this move matters
Compare evidence after each session, then group patterns, differences and conditions without turning every comment into a feature request.
Did You Know? Collaborative synthesis exposes different observer interpretations.
Define the decision before the session
Compare evidence after each session, then group patterns, differences and conditions without turning every comment into a feature request. State what design decision the test can inform, which user goal matters and what evidence would support change. A plan prevents the team from collecting observations without knowing how they will be used.
Write tasks as realistic goals
In the worked service, The team maps deadline confusion separately from eligibility-filter discoverability. Give participants a situation and desired outcome without naming the interface control or route the team wants them to discover.
Observe, measure and debrief carefully
Record behaviour, errors, recovery, comments and relevant measures separately. Let the participant think aloud, keep observers quiet during the session and compare notes immediately afterwards.
Report scope and accessibility honestly
A repeated issue can still arise from the prototype or scenario rather than the future service. Include participant characteristics, assistive technology, task conditions and unresolved barriers. User testing complements standards evaluation; it does not certify universal accessibility.
Practical reader check
- Point to the exact source or method sentence supporting the claim.
- Name the person, setting, date, input and decision rule that could change its meaning.
- Label the remaining uncertainty reported, inferred, contested or unknown.
Student, parent and career transfer
Make one evidence card for “Debrief and Synthesize Across Sessions”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports UX research, content design, service design, product management, software development, accessibility and student technology projects without promising a grade, admission, funding decision or job.
CHAPTER 16 OF 16
16. Report Scope, Accessibility and Next Decision
Why this move matters
Describe participants, tasks, technology, limitations, barriers, confidence and the design action with an owner.
Did You Know? A good finding tells the reader both what happened and where the claim stops.
Define the decision before the session
Describe participants, tasks, technology, limitations, barriers, confidence and the design action with an owner. State what design decision the test can inform, which user goal matters and what evidence would support change. A plan prevents the team from collecting observations without knowing how they will be used.
Write tasks as realistic goals
In the worked service, The report recommends rewriting deadline states and retesting with the repaired keyboard path. Give participants a situation and desired outcome without naming the interface control or route the team wants them to discover.
Observe, measure and debrief carefully
Record behaviour, errors, recovery, comments and relevant measures separately. Let the participant think aloud, keep observers quiet during the session and compare notes immediately afterwards.
Report scope and accessibility honestly
User evaluation does not certify WCAG conformance or universal usability. Include participant characteristics, assistive technology, task conditions and unresolved barriers. User testing complements standards evaluation; it does not certify universal accessibility.
Practical reader check
- Point to the exact source or method sentence supporting the claim.
- Name the person, setting, date, input and decision rule that could change its meaning.
- Label the remaining uncertainty reported, inferred, contested or unknown.
Student, parent and career transfer
Make one evidence card for “Report Scope, Accessibility and Next Decision”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports UX research, content design, service design, product management, software development, accessibility and student technology projects without promising a grade, admission, funding decision or job.
PRACTICE LAB
Plan one honest usability task
Student route
- Name one design decision.
- Write a realistic goal without interface labels.
- List the behaviours you will observe.
- Choose a stopping and rescue rule.
- Write the limit you will report.
Parent or teacher route
Ask the learner to distinguish a software bug, a confusing instruction and a participant preference. These may appear together but need different evidence.
Early-career route
Pilot the task with the intended device and accessibility settings. Repair barriers in the prototype before treating participant struggle as a design finding.
Decision rule
If the task tells the participant how to succeed, it cannot test whether the design makes that route discoverable.
USEFUL NEXT READING
Connect this narrow owner to its neighbour
Read the user-story guide for a related but different reader job. Return here when the question is specifically how to turn a design question into realistic tasks, careful observation and findings the team can act on. Use each guide for the reader task named in its heading.
For English practice across research, school and career communication, visit the Singapore English Tuition Centre learning site.
FREQUENTLY ASKED QUESTIONS
Questions students and parents often ask
How many participants are needed?
It depends on the research purpose, user diversity, risk and desired confidence; explain the sample and avoid population claims a small study cannot support.
Should tasks tell users where to click?
Not when discovery is being tested. Give a realistic goal and let the interface reveal the route.
Is time on task always useful?
No. Use it only when timing relates to the decision and the task, prototype and sample make interpretation responsible.
Should the moderator help a stuck participant?
Use a pre-agreed stopping and rescue rule, intervene for safety or dignity, and record the assistance.
Does testing with disabled users prove accessibility?
No. W3C recommends combining user involvement with standards-based conformance evaluation.
Can AI analyse recordings?
Only within consent, privacy and security rules, with human review of context, errors and scope.
PRIMARY SOURCES
Read the primary guidance for this usability test plan
Facts were checked against current primary official sources on 8 November 2026. Follow the live source for later corrections, completed updates or companion material.
- Digital.gov: usability testing
- Digital.gov: success metrics
- W3C WAI: involving users in evaluating web accessibility
- W3C Web Content Accessibility Guidelines 2.2
- MOE English Language Syllabus 2020 Secondary E/N(A)
- eduKate Student and Learner Hub
A cheerful final note
Precise English makes a usability test plan easier to use and easier to question. People can see how their evidence and values entered the work, where disagreement remains and what a responsible next step looks like.