Aglet

Learn from search filter dead ends and recovery gaps

A dead-end lesson should preserve the sequence that trapped a person and the recovery that would have helped. Compare later combinations with the original matrix, then turn the difference into one question about facet compatibility, empty-state copy, or preserving intent.

Keep the lesson for the next incident

  1. Keep the selection path

    Record query, category, each selected filter, result totals, and the first empty transition. Note whether the combination was truly impossible or merely unavailable at that moment. This avoids turning a temporary inventory state into a taxonomy rule.

  2. Compare later intersections

    Review neighboring combinations and their empty messages after the change. Look for a different pair that still offers no recovery or a fallback that broadens too far. Preserve a valid empty example so the lesson does not equate zero with defect.

  3. Refine one review question

    Require a valid narrow control, an incompatible pair, direct-link replay, and one removal path in future filter reviews. Assign the practice and revisit date. Define what observation would show the new question prevented another dead end.

What to carry forward

The learning output connects one trapped filter sequence to a repeatable compatibility and recovery check. Stop when another reviewer can test valid, incompatible, and direct-entry cases. Carry forward uncertainty where catalog availability changes faster than the filter contract can explain.

Technical background: W3C 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