Aglet

Verify product search intent boundaries across representative paths

Verification should show that the search surface honors the job implied by its entry context while still offering a clear recovery when intent changes. Test product, support, and navigation examples, then check that labels and result grouping do not promise a scope the query cannot provide.

Check whether the outcome improved

  1. Test the expected job

    Run representative catalog and support queries from their intended entry points. Confirm the result type, first useful action, and breadcrumb or scope cue match the job. Record a pass only when a person can explain why the leading result belongs.

  2. Try a changing-intent path

    Begin with a product phrase, then introduce an instruction or account term. Check whether the person can recover through a visible scope choice or useful result group. Make sure the recovery does not erase the original query unexpectedly.

  3. Review the claim

    Compare the tested paths with the proposed closure language. List query families, devices, and indexes not covered. Keep a mixed-intent example open when its behavior is still ambiguous instead of counting a convenient click as proof.

What to carry forward

Verification passes when the selected search job is clear, mixed-intent queries have an understandable recovery, and the closure text matches tested scope. If a result type remains unexplained, record the path as partial and name the next query family rather than claiming global relevance.

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