Unit 4 · Lesson 16 of 20
Revise, then test the change
Connect a design change to a finding and examine its new tradeoff.
01 / Learn
Learn the method
Fictional case
Two patients in the fictional study treated a delayed check-in as a completed arrival.
Terms for this lesson
- Revision
- A design change intended to address an observed issue.
- Retest
- A new observation of the changed interaction.
- Regression
- A new difficulty introduced while improving another part of the flow.
A revision proposes a mechanism for improving an observed experience. Begin with the finding: during a delayed branch, two patients moved to waiting before the service issued a receipt. Then name a change that helps patients recognize the pending state and choose a useful next action.
Change the smallest set of elements that can address the mechanism. The team can place a clear pending heading, explain that the request is still sending, and offer a reception-help action after a defined wait. The received state can keep its own distinct heading and waiting instruction. The contrast between states helps patients form an accurate expectation.
Retest the original situation and a routine successful check-in. The delayed task shows whether patients understand the pending action. The successful task shows whether the extra distinction adds reading time or confusion during normal use. Record understanding, next action, recovery, and task time.
A revision can expose a new question. Patients may understand the pending message and still need a clearer reception route. The next round turns that observation into another focused change. Iteration keeps the service aligned with actual patient behavior.
Use the method
- Link each proposed change to a finding and expected mechanism.
- Test the original difficulty and a routine successful path.
- Record the new behavior, added effort, and next decision rule.
A revision gains strength when its intended effect and its possible cost are both observed in the next test.
- Nielsen Norman Group: Iterative Design of User Interfaces ↗Revise, observe again, and keep unresolved questions visible.
- Nielsen Norman Group: Making Usability Findings Actionable ↗Report an observed issue with context and a direction the team can use.
- GOV.UK Service Manual: Using moderated usability testing ↗Write believable, neutral tasks that answer a research question.
02 / See the reasoning
Worked example
The team changes 'Almost done' to 'Check-in is still sending' and adds 'Please stay here. Reception can help after one minute.' They keep 'The clinic has received your check-in' for the receipt state. In the retest, the moderator triggers both branches. The observer records whether patients distinguish them, where they go next, and how the extra wording affects a routine arrival.
Try a decision →03 / Decide
Guided decision
Which revision and retest best follows the delayed-state finding?
Feedback on your choice
What could change the answer: Patients who understand the pending wording and still move to waiting would make lobby directions and reception practices the next focus.
Use this feedback to examine your choice and written reasoning.
Build your case file →04 / Build the case
Your case file
Fictional case update
A patient sees the revised pending message during a busy session and chooses the reception-help route.
Evidence and constraints
- Fictional original finding: two of six patients moved to waiting during a delayed branch before a service receipt.
- Fictional proposed change: distinct pending and received headings with different next actions.
- Fictional operations detail: reception can query the appointment service directly.
Write one retest observation for this route and one service check that reception must complete to support it.
Create: A findings-to-change table with revised copy, test tasks, observations, and a next decision rule.
The revision addresses a specific observation and the retest examines both understanding and added effort.
- Each change links to a finding.
- The retest includes delayed and routine branches.
- The next decision rule follows observable patient behavior.
The revised flow now needs a feasible release and a responsible operational owner.
Unit complete
You completed test and improve.
You finished this unit's four case-file tasks. The next unit builds on the evidence and decisions you made here.
05 / Keep working