Aglet

Prioritize category search boundaries with clear context

Scope work matters when people cannot tell why an expected result is absent or why unrelated results appeared inside a category. Compare route copy, breadcrumb, filter behavior, and retrieval. A visible scope cue may prevent more confusion than a broad result expansion.

Decide where the work belongs

  1. Name the category decision

    Describe the product or content a person expected in the current route and what appeared instead. Compare strict category, category filter, and global paths. Keep a valid exclusion separate from a result that violates the visible breadcrumb.

  2. Compare remedies

    Set breadcrumb and label copy, scope toggle, strict filter, inclusive filter, and result grouping beside one another. Consider how a broader path affects facets and sorting. Prefer a repair that makes the current scope explicit and reversible.

  3. Choose a bounded move

    Record route family, owner, and revisit evidence. Decide whether to investigate query routing, adjust copy, or offer a broader search action. Preserve the exact URL and a working category control so the decision remains testable.

What to carry forward

Prioritize scope work where route context changes the expected result and the current interface hides that boundary. The decision should name route, result promise, and remedy. If exclusions are intentional and visible, queue a different search gap only when the evidence supports it.

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