Aglet

Prioritize zero-query discovery with a clear first action

A blank search state competes with other discovery work according to how much it delays a person’s first useful query and how safely guidance can be offered. Compare examples, categories, recent terms, and no prompt. A modest scope cue may be safer than a personalized suggestion system.

Decide where the work belongs

  1. Name the first-task friction

    Describe what a new or returning person cannot infer from the blank state. Compare a visible example, category link, recent term, and focus cue. Keep a person who already knows the query separate from someone who needs orientation.

  2. Compare guidance sizes

    Set static examples, scope explanation, recent history, popular categories, and a blank field beside one another. Consider privacy and relevance. Prefer a cue that supports the next action without implying that one term or category is universally important.

  3. Choose the queue move

    Select copy, scope labeling, example content, history handling, or no change. Name the context and revisit evidence. Preserve a low-guidance control so the decision can be compared against an intentionally blank search rather than memory.

What to carry forward

Prioritize zero-query work where people cannot identify the search scope or first action and a small cue can help without inventing popularity. The decision should name context, guidance, privacy boundary, and owner. If the blank state is already understandable, queue higher-impact result issues instead.

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