Aglet

Triage zero-query discovery before adding search suggestions

A blank search field can be an intentional starting point or a screen that leaves people without a clue. Triage the zero-query state before adding popular or recent terms. Compare who is searching, what scope is available, and whether each discovery option helps begin a real task.

Establish what is happening

  1. Capture the first state

    Record entry point, account context, scope label, field focus, visible examples, and available actions before typing. Include new, returning, signed-in, and anonymous paths where they differ. Do not assume recent searches are available or appropriate for every person.

  2. Compare discovery promises

    Classify each prompt as recent search, popular category, example query, navigation shortcut, or no-op. Check whether the option has a clear destination and respects context. A decorative list is not discovery if it cannot start a useful search.

  3. Set a safe blank-state boundary

    State what appears, when it appears, and the fallback when history or popularity is unavailable. Preserve a truly blank path if that is intentional. Stop when a person can tell how to begin without being steered by unsupported demand assumptions.

What to carry forward

The triage output is a zero-query behavior brief with entry context, discovery options, privacy-safe fallback, and first action. Stop when the blank state has a truthful purpose. If usefulness or history availability is unknown, keep the surface minimal and route the evidence question.

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