Website Usability Test Form Template

Research purpose: Use this form to record one usability task's outcome, difficulty, observed hesitation, and participant explanation without mixing observation with interpretation.

Record task success, friction, confidence, and a specific observation.

Download the field schema

Preview the task observation

Task and outcome establish what happened. Difficulty and open notes capture separate participant and observer evidence.

Session and task outcome

Participant code Required
Task RequiredFind informationComplete a formChange a setting
Task outcome RequiredCompletedCompleted with helpNot completed
Task difficulty Required

Observation and participant view

Where did you hesitate?
What would you change?
Record test session

Recording a hesitant completion

Documenting a checkout navigation test. A facilitator can record whether the participant completed the named task, note where hesitation occurred, and preserve the participant's suggested change. Results can then be grouped by task and issue severity without inventing population-wide success claims.

Keep outcome, rating, and observation distinct

Task and outcome establish what happened. Difficulty and open notes capture separate participant and observer evidence.

  • Participant codeLinks observations without collecting an unnecessary name.
  • TaskIdentifies the exact activity the participant attempted.
  • Task outcomeRecords completion, assisted completion, or non-completion using defined criteria.
  • Task difficultyCaptures the participant's own assessment separately from observed outcome.
  • Where did you hesitate?Locates friction points in the participant's experience.
  • What would you change?Records a concrete suggestion without treating it as the researcher's conclusion.

The evidence this record separates

This template records task outcome, difficulty, hesitation, and participant feedback for one named task on a defined website version. It separates observed behavior from participant comments and later researcher interpretation.

Use the form question writing guide to keep observation prompts neutral and separate task outcome from opinion.

Use this for one defined usability task

Use this for structured observation after a participant attempts one named task on a defined version.

Set task codes and observation rules

  • Use a participant code instead of unnecessary identity.
  • Define what completed with help means.
  • Record the page or build version tested.

From sessions to supported themes

Researchers can compare task outcomes while retaining the concrete hesitation that explains where the interface failed.

Record the outcome

Record task outcome before discussing opinions.

Separate evidence types

Separate observed behavior, participant comment, and researcher interpretation.

Group supported issues

Group issues by task and severity with supporting evidence.

Usability test questions

Answers about the choices, limits, and handoff shown on this page.

What should a usability test form record?

Record the participant code, task, defined outcome, perceived difficulty, observed hesitation, and participant feedback.

Should usability testing collect participant names?

Use a participant code when identity is not needed for the research purpose. Keep any separate contact record under its own access and retention controls.

Create a usable research record

Define the task and success rule before testing, then keep observation, participant comment, and researcher interpretation separate.

Compare form workflows