Aglet

Turn Product Language Tests Into Better Naming

Language research teaches a team which words carry an unexpected task or expectation. Save the candidate, context, participant phrasing, and decision. Then make contextual comprehension part of naming work before visual polish and internal fluency hide a label problem in context.

Keep the lesson for the next incident

  1. Capture the language case

    Keep the original term, alternatives, participant explanations, mistaken action, supporting context, and final decision together. Include a label that people liked but used incorrectly. That contrast shows why preference cannot replace task evidence when a key action is at stake.

  2. Improve naming practice

    Add own-words, task choice, audience, translation, and jargon checks to naming reviews. Test key labels in the flow before polishing the interface. Explain how the change addresses the misunderstanding found here in the earlier review.

  3. Watch for jargon return

    Set a signal such as support staff rewriting labels, users repeating an internal acronym, or different surfaces using competing terms. Assign an owner to sample new copy and revisit the glossary when the signal appears.

What to carry forward

The learning record should connect the mistaken action to the naming practice and recurrence signal. State which term or context changed. Keep language guidance tied to user tasks and audiences rather than declaring one universal vocabulary.

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