The playbook
Website User Testing: Checklist
Use this website user testing checklist before a new release, a handoff, or a scheduled review. Its purpose is to verify the decisions that affect task success in observed sessions. Check an actual page or interaction record; a box marked complete without evidence does not show that the customer journey works.
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.
Before you use the checklist
Name the exact item being checked and its purpose. Gather task, observation, impact, proposed change. If one of those details is unknown, mark it as unknown and assign a way to resolve it. An invented value makes the checklist look complete while weakening every later decision.
Working checklist
| Check | Evidence to keep | Responsible role |
|---|---|---|
| Choose realistic tasks without revealing the answer | A dated observation showing how task was verified | website lead |
| Watch where participants hesitate fail or misinterpret | A dated observation showing how observation was verified | designer or developer |
| Prioritize repeated obstacles over personal design preferences | A dated observation showing how impact was verified | site owner |
Check the failure path
- Look specifically for this failure: asking only whether participants like the design.
- Observe task performance and ask what caused confusion. Record the actual correction, not just the intention to make it.
- Repeat the affected task after the correction and check proposed change.
- Make sure the next owner can find the decision and supporting evidence.
Use three outcomes for each check
Mark an item as complete only when the expected behavior or information has been observed. Mark it as incomplete when a required condition is absent. Use not applicable when the condition genuinely does not belong to the chosen scope, and write a short reason. These states keep a review useful without forcing every process into an identical mold.
For example, if the check is “Choose realistic tasks without revealing the answer,” a meeting about the subject is not the evidence itself. Retain the relevant task and observation, the decision made from them, and the result of checking that decision. The record should allow someone who missed the meeting to understand what changed.
Decide what must be resolved first
An incomplete item that prevents observe whether representative visitors can complete important tasks deserves attention before a cosmetic improvement. Assign an owner and a next action to that issue. Keep optional refinements visible, but do not let them obscure a failure in the core process.
Close the review
Recheck corrected items and note anything still uncertain. The checklist is finished when the next owner understands what was verified and what remains open. Follow task success in observed sessions using a consistent definition so later reviews can connect execution quality with useful results.
Keep the page’s main task visible when adding helpful detail. Supporting information should reduce uncertainty at the decision point. If a section introduces a second unrelated offer, decide whether it belongs on another page.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now