Aglet

Investigate Which Product Label Users Understand

Naming investigation should observe what people do with a label, not collect abstract votes. Present alternatives in the task where the word matters, ask participants to explain their choice, and compare interpretations across audiences. Keep a liked label that leads to the wrong action as a failure case.

Build a useful investigation brief

  1. Test the first interpretation

    Show the label with realistic surrounding content and ask the participant what it means or what they would do next. Record their own words before explaining the intended meaning. Note hesitation, search, and nearby labels that changed interpretation.

  2. Compare candidates and audiences

    Run the same task with new, experienced, support, and translated contexts where relevant. Record correct choice, explanation, confidence, and mistaken path. Do not treat expert vocabulary as the only valid language when the product serves newcomers.

  3. Check the consequence

    Change one term or supporting phrase and repeat the task. Test whether comprehension improves without creating a different expectation. Preserve ambiguous cases and state whether the problem is label, context, hierarchy, or missing content.

What to carry forward

The investigation brief should show labels in context, uncoached interpretations, task choices, audience differences, and the changed candidate. End with a bounded language recommendation or follow-up. Do not choose a term from stated preference alone.

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