Aglet

Turn Usability Analysis Into Better Research

Usability analysis teaches the team how it turns raw behavior into product language. Preserve the observation, interpretation, counterexample, and decision that changed. Then improve the analysis ritual so future findings retain task context and confidence instead of becoming untraceable sticky notes.

Keep the lesson for the next incident

  1. Save the analytic case

    Keep the raw note, task state, participant context, observer interpretation, final finding, and decision together. Include a session that contradicted the first reading. A counterexample shows where the finding stops applying and which context still needs a different explanation.

  2. Improve synthesis practice

    Add fields for behavior, outcome, evidence source, recurrence, confidence, and open question to the analysis template. Require a successful path before declaring a blocker. Explain how the new structure addresses the earlier overgeneralization.

  3. Watch for anecdote drift

    Set a signal such as findings without session links, severity based on quote vividness, or causes written as facts. Assign an owner to sample the next analysis and revisit the method when the signal appears in a later round.

What to carry forward

The learning record should connect the analysis mistake to the revised evidence practice and recurrence signal. State which findings were narrowed or retained. A durable method keeps the work traceable without slowing useful synthesis. for future sessions.

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