Aglet

Prioritize a product search synonym gap with evidence

A vocabulary gap competes with other search work according to the journeys it blocks and the safety of the proposed mapping. Compare representative failed searches with the cost of a broad synonym. A narrow, high-confidence correction may belong ahead of a larger vocabulary project.

Decide where the work belongs

  1. Describe the blocked task

    Name the product or category people were trying to find and how the alternate term led them away. Compare zero results, irrelevant results, and successful reformulation. Keep query counts as context only when their denominator and sampling are known.

  2. Compare scope and risk

    Set a category-specific alias, locale-specific alias, correction hint, and global synonym beside one another. Consider false positives, variant confusion, and reversibility. A candidate that helps one family but harms adjacent families needs a narrower queue item.

  3. Set the next move

    Choose investigation, a limited experiment, a content correction, or a deferred vocabulary review. Assign an owner and review trigger, such as a new category or a contradictory result example. Preserve the rejected alternatives in the decision record.

What to carry forward

Queue the synonym work according to blocked outcome, confidence, and false-positive risk. The useful decision identifies a bounded term pair and experiment size. If evidence does not distinguish equivalent language from a neighboring concept, prioritize clarification instead of a broad rule.

Technical background: GOV.UK developer documentation.

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