Aglet

Prioritize search snippet context with a useful result choice

Snippet work deserves priority when people cannot tell which result supports their task and must open several destinations to find out. Compare missing context with simple wrapping or label fixes. A narrow content-type rule may be safer than changing every result excerpt.

Decide where the work belongs

  1. Name the choice blocked

    Describe what context a person needs to select the result and what the current snippet hides. Compare a missing title qualifier, matched sentence, date, or category. Keep a row that is merely long separate from one that is misleading.

  2. Compare remedies

    Set field selection, excerpt window, highlighting, title copy, content-type template, and destination labels beside one another. Consider mobile truncation and localization. Prefer a repair that restores decision context without stuffing every available field into the row.

  3. Choose the next slice

    Set query family, content type, owner, and revisit evidence. Decide whether to investigate result data, tune rendering, or improve copy. Preserve the original ranked sample and a clear control so the change can be evaluated against usefulness.

What to carry forward

Prioritize snippet work where missing context causes wrong choices or repeated backtracking. The queue decision should name content scope and remedy. If users already have enough context but the row is visually dense, prioritize hierarchy and truncation instead of relevance changes.

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