Aglet

Prioritize Usability Findings for Action

A long findings wall can hide the one barrier that prevents people from completing a critical task. Prioritize by consequence and evidence, not by the most expressive quote. Keep low-frequency barriers visible when they affect access or make recovery impossible.

Decide where the work belongs

  1. Describe the consequence

    For each finding, record the task outcome, extra effort, abandonment, workaround, or access barrier. Identify affected users and journey moments. Distinguish a cosmetic preference from a problem that changes whether the person can finish the task.

  2. Assess confidence and reach

    Compare recurrence across sessions with the variety of contexts represented. Note whether the same behavior appeared in assisted and independent attempts. A single severe barrier may outrank a recurring minor annoyance; record why.

  3. Choose a next action

    Select a design fix, another test, a content change, or a deliberate deferment. Assign an owner and review date. Add a trigger for revisiting findings whose confidence depends on a narrow prototype or unfamiliar task.

What to carry forward

The priority output is a usability queue with task consequence, affected context, recurrence, confidence, and next action. Lead with findings that block meaningful outcomes or access. Keep the ranking provisional when the session set cannot represent the relevant journey.

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