The playbook
Website User Testing: Review Process
A useful website user testing review ends with a supported decision for each item examined. Define the evidence required before opening the report: task, observation, impact, proposed change. These fields give reviewers a shared basis for agreeing what is working, what needs attention, and who should act.
Put the task in context
Ask someone to find a service, determine whether it fits, and submit an inquiry without pointing at the intended controls. Observe the route they choose and where they hesitate. Ask what they expected after the task rather than coaching them during it.
Set the review boundary
Choose the records or journeys that matter to the current question. Include a normal case, a recently changed case, and an exception where available. This is a diagnostic sample, not a claim that every item has been checked. Record how the sample was selected and what would justify expanding it.
Use explicit review criteria
| Criterion | Review question |
|---|---|
| Choose realistic tasks without revealing the answer | Is the supporting task current and traceable? |
| Watch where participants hesitate fail or misinterpret | Does observation support the decision being made? |
| Prioritize repeated obstacles over personal design preferences | Can the next owner verify proposed change? |
Inspect the evidence before assigning a result
For each item, compare the intended behavior with the observed behavior. Pay particular attention to asking only whether participants like the design. If it appears, record where it occurs and which assumption it contradicts. Distinguish a verified defect from an unanswered question and from a preference about how the work should look.
Where the evidence supports the known correction, observe task performance and ask what caused confusion. Give that action to an accountable owner with a description of the expected result. If you cannot yet identify the cause, assign a diagnostic action rather than prescribing a speculative repair.
Record a decision that can be acted on
| Decision | When to use it |
|---|---|
| Keep | The current state serves the intended task and the evidence is adequate. |
| Revise | A specific gap is confirmed and the proposed action addresses it. |
| Investigate | Important information is missing or conflicting. |
| Retire or combine | The item has no distinct useful purpose in the current scope. |
Verify corrections and expand selectively
Recheck the affected page or interaction record after the owner completes the action. Then inspect other items sharing the relevant cause. A shared template, process rule, or data source may justify expanding the review. Similar wording or appearance alone is a weaker reason.
Turn the review into a decision summary
Summarize the affected scope, confirmed findings, actions, and open questions. Connect the findings to task success in observed sessions using the same definition as the baseline. A good summary lets the responsible person decide what happens next without reading every working note.
Treat visual changes and functional changes separately in the change log. A clearer label may improve comprehension, but a broken submission destination still prevents completion. Confirm both understanding and successful delivery.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now