Aglet

Verify Usability Findings Before a Product Change

Verification makes a finding useful to design without overstating its reach. Reapply the task or review to the affected contexts, inspect exceptions, and compare with successful behavior. Record the evidence boundary before deciding that a change solves the problem for users.

Check whether the outcome improved

  1. Define finding acceptance

    Require a named task, observable behavior, outcome consequence, context, source sessions, and confidence note. Add a check that separates observed difficulty from a participant preference or observer guess about the cause.

  2. Review varied sessions

    Compare first-time, experienced, assisted, and access-related paths where relevant. Inspect the interaction state at the moment of difficulty. Record a successful recovery and an exception so the finding does not erase useful variation.

  3. State the design boundary

    Decide whether the finding supports a change, another test, or a narrower statement. Record what it cannot establish about all users or devices. Give the next owner a clear success condition and a date to review new evidence from this task.

What to carry forward

The verification record should show finding criteria, source sessions, task outcomes, exceptions, and decision scope. Use the finding only for the contexts tested. Retain an investigation when the observed behavior and stated explanation still disagree.

Technical background: GOV.UK user research guidance.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow