Keep the lesson for the next incident
Record the useful signal
Keep prefix, suggestion type, source, order, accepted query, and edits. State what job the person appeared to have. This separates a relevant recent search from a popular phrase that happened to share the first characters.
Compare later prefixes
Review new and returning prefixes after the change or catalog update. Look for useful suggestions that moved away and noisy terms entering the list. Preserve one good control and one negative example so the lesson retains a boundary.
Add one quality prompt
Require future reviews to ask what each suggestion helps complete, how it can be dismissed, and which evidence supports its order. Assign ownership and a revisit date. Define the observation that would show the prompt reduced accidental query changes.
What to carry forward
The learning record should connect one noisy prefix to later evidence and a reusable suggestion-review question. Stop when another reviewer can evaluate relevance, acceptance, and dismissal on a new prefix. Keep uncertain source behavior explicit instead of turning list popularity into a universal quality rule.
Technical background: W3C 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