Zero results should offer concrete actions that relax constraints

What it is

After the cause is named, the empty page still needs concrete actions that relax constraints: drop this filter chip, widen scope from this folder to the whole library, discard the narrowest term in the query—and they must be tappable now, not the advice “please broaden your criteria.” An action has to point at a named constraint and, once tapped, re-run immediately with a non-empty set or at least a different count. Abstract advice returns generation cost to the user; a concrete action does that step for them.

These actions repair an empty set that has already happened. They are not a count preview before applying a filter, and they are not a nearby spelling query; those have their own objects.

Why it happens

Constraints are a chain; emptiness is a few links pulled too tight. People cannot reverse-engineer which link to loosen from a “0,” especially when the filter was ticked on the previous page and the scope arrived from navigation, already out of focus. Making “clear: This year” and “search all documents” into controls wires diagnosis into the motor system: the next step need not be generated, only confirmed.

Actions also need to be reversible and singular. Dropping every constraint at once hides which cut saved the search, so nothing is learned for next time; dropping the one the system judges most responsible lets feedback teach. If the action still yields 0, the second empty page is abandoned faster than the first, so probe before display—at least guarantee the count will change after relaxation.

Studying it

See whether recovery after zero travels the offered cut, and whether that cut aims at the constraint that was actually too tight.

• Paradigms: a known item emptied by a filter or a scope; one condition advice only, one tappable relax actions; in query logs, whether “remove filter / widen scope / drop a term” after zero came from a control or was spontaneous. Hearst lists support for query reformulation as a search-UI capability.
• Independent variables: whether the action names a specific constraint, one-at-a-time vs clear-all, whether display is probed.
• Dependent variables: time to recover, uptake of the control rather than spontaneous relaxation, rate of still-zero after the action.
• Methodological note: if the lab draws the filter that should be loosened in high salience, uptake is inflated. On a real empty page the filter summary may be folded into a corner. Do not count “tapped a spelling approximation” as relaxing a constraint—that swaps the query, it does not loosen current constraints.

Where it stops holding

When the object is truly absent from the collection, relaxing any constraint will not conjure it; actions should stop promising “there will be results” and point elsewhere. Emptiness from permission is not helped by loosening filters; the action is request access or switch accounts, not a pretend filter fix. When the query is already shortest, no filters are on, and scope is global, there is nothing to relax, and a “broaden” control is an empty button. On a tight mobile empty page, offer the single most responsible constraint, not the whole chain spread out.

Applying it

• Give each named constraint a tappable action whose copy includes the constraint’s own name (“remove filter: This year only,” “search in all locations”).
• Probe before display: the count must change after the tap; actions that would not change it do not appear.
• Default to relaxing one constraint; offer “clear all filters” as an explicit second choice so a total wipe is not the only way to learn.
• Verify by hiding a known item behind an over-narrow filter. If the empty page has advice and no button, the action does not exist. If the button still yields 0, or deletes a query term it should not have touched, the action missed the constraint.

Related

• Within the group: G3.07.1 Zero-result states must explain why, not only report the count · G3.07.3 A zero-result page is a guide, not a dead end
• Adjacent: G3.08 Filters · G3.04 Spelling correction · T2.05 Empty-state and zero-result copy
• Search terms: constraint relaxation · zero results · query reformulation