Decide where the work belongs
Name the context cost
Describe the task a person was doing and how a product, help, project, or account result changed it. Compare a wrong index with a correctly scoped but poorly labeled result. Keep access confusion separate from ranking confusion.
Compare scope remedies
Set separate sections, route-specific search, result-type labels, explicit broadening, and one blended list beside one another. Consider destination and permission context. Prefer a repair that preserves meaning before changing cross-index order.
Choose the first slice
Record indexes, route, owner, and revisit evidence. Decide whether to investigate routing, improve grouping, or test an explicit scope control. Preserve the mixed sample and a known in-scope result so the queue decision remains grounded.
What to carry forward
Prioritize scope work where a wrong-context result changes a meaningful decision or makes access unclear. The queue decision should name indexes and the smallest remedy. If blended results are intentional and labeled, prioritize the specific ranking or snippet gap instead.
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