Decide where the work belongs
Name the choice cost
Describe what people cannot compare because repeated rows occupy the page. Contrast a true duplicate with a parent product whose variants differ in price, availability, or fit. Keep one crowded query separate from a catalog-wide identity problem.
Compare remedies
Set grouping, variant display, canonical indexing, result limits, and copy changes beside one another. Consider sort and category context. Prefer a repair that preserves a meaningful variant choice and keeps the destination clear.
Choose the first slice
Set query family, category, owner, and revisit evidence. Decide whether to investigate identity, test grouping, or adjust presentation. Preserve the before-state and one ungrouped control so the queue decision can be evaluated after a change.
What to carry forward
Prioritize duplicate-result work where repeated rows obscure distinct products or force avoidable comparison effort. The decision should identify grouping scope and preserved choices. If rows are distinct variants with clear labels, leave them visible and prioritize a different result-quality issue.
Technical background: Digital.gov 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