The empty state is the best place to show capability

What it is

For the few seconds the result well is still empty, attention is not held by any artifact, and the caret is already asking what to do next. An empty-state capability showcase claims that the window in which capability gets seen opens on this not-yet-committed surface — not after the first miss, and not at a help entry on the product’s edge. What material to use (examples, labels, a short clip) is a separate choice. This entry pins the place.

An empty state is not “no content, so dump campaigns.” It is the only stretch when the user has not yet staked a first sentence, and will still look at a map.

Why it happens

Attention follows unfinished action. An empty result well is a gap, and people fill it with the nearest thing that looks like an answer. Capability material placed then shares a visual field with the gap. Once the first generation occupies the well, the gap closes and attention moves to judging the artifact; later tips become interruption and get dismissed. Help-center copy and a settings page titled “what it can do” are not on this action chain at all — you first have to admit you do not know, then leave the current task to read, by which time discovery has already ended.

There is also once-per-session recurrence. Empty states return in each new thread or document, so the place brings its own repeat exposure without requiring anyone to remember that they once opened an article.

Studying it

Park the same capability material in four places: a true empty state (result well blank), a banner after the first miss, a persistent sidebar, the first item in a help menu. Compare not material quality but “seen at least once” and “first legal request after seeing.” Independent variables: timing, skippability, whether the well goes empty again inside the session. Dependent variables: exposure rate, latency from exposure to uptake, skip rate, whether help is opened later.

A lab that forces a five-second dwell on the empty state will overstate the place. Cleaner: people arrive with their own files, and the empty state appears only when they open the generate entry.

Where it stops holding

Returning threads carry history; the well is not empty; the place vanishes. Embedded entries (a floating bar on selected text) often have no empty state, and capability display has to live in short labels on the bar. On mobile, the keyboard can push empty-state material out of view: the place is nominally right and actually invisible. Frequent users form a “just type” habit, and empty-state material becomes noise that needs to collapse. This entry does not argue that examples beat documentation as display material — only where the window opens.

Applying it

• The first time the generate panel opens and the result well is still empty, lay capability material in the well, not as one grey placeholder line inside the input.
• When the user starts typing, the material yields. Do not fight the draft. Bring it back when the result is cleared or a new thread opens.
• Offer a clear “skip, I know what to ask,” so the showcase is not a modal that must be dismissed.
• Check: screen recordings of new users, first five seconds after opening the entry. Does gaze land on the material, and is the material still in view after keyboard or panel expansion? If they are typing in those five seconds and the material never entered the field of view, the place was chosen and the layout did not use it.

Related

• Same group: L2.02.1 Examples are the most effective display of capability · L2.02.3 Help documentation cannot carry that job
• Nearby: L2.01 Openness of Natural-Language Commands and Its Cost · L2.09 Discoverability of What I Can Say · L6.03 Cold Start
• Search terms: empty-state capability showcase · zero-data state · first-run discoverability