Aglet

Triage filter combinations that create search dead ends

A zero-result view can be a legitimate narrow choice or a dead end caused by incompatible filters. Triage the distinction before changing facets. Reproduce the selections, inspect available alternatives, and identify whether inventory, scope, or an interaction rule makes the combination impossible.

Establish what is happening

  1. Map the selected filters

    Record the query, category, facets, order of selection, result total, and visible recovery controls. Compare each filter alone with the combination. Keep a true zero-result query separate from a filtered zero so the empty state has a meaningful cause.

  2. Find the recovery path

    Check whether the interface offers a useful removal, alternative value, broader scope, or explanation. Test back and reset behavior. Mark a missing recovery as a design gap, but do not claim the combination itself is invalid without evidence.

  3. Set the dead-end boundary

    Classify the state as valid empty, incompatible selection, stale facet, or unknown. List which filters and contexts are in scope. Preserve the shortest sequence that reaches the dead end so investigation can compare the user’s path rather than only the final URL.

What to carry forward

The triage output names the filter intersection, its cause or uncertainty, and the next recovery a person can take. Stop when valid empty and incompatible states are distinguishable. If the catalog or index cannot explain the result, preserve the query and route it for evidence.

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