Decide where the work belongs
Name the narrowing task
Describe which product decision the missing value would support and where people currently stop. Compare a missing high-level choice with a long tail value that few queries need. Keep evidence about category, locale, and inventory context attached.
Compare remediation sizes
Set source cleanup, index configuration, facet visibility, and copy changes beside one another. Consider whether exposing a value with weak data will create false confidence. A scoped facet can be better than a complete list that users cannot trust.
Place the work
Choose one bounded next move with owner and revisit trigger. State the value set in scope and what would justify expansion. Preserve the coverage map so later prioritization can distinguish a source gap from a UI gap.
What to carry forward
Prioritize facet coverage where a missing value blocks a meaningful product choice and the underlying data supports a safe fix. The queue decision should state scope and tradeoff. If the catalog evidence is unreliable, prioritize data clarification before adding another control.
Technical background: Adobe 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