Skip to content

Empty-State Prompt

Interface artifact — instantiates Latent Affordance Surfacing

Turns a blank container — an empty inbox, list, or workspace — into a cue that names what could go there and offers the first step to put it there.

An empty container is the moment a system is most likely to lie about what is possible: a blank pane reads as "nothing here / dead end," when what it should say is "here is what goes here, and here is how to add the first one." Empty-State Prompt is the artifact that occupies that emptiness on purpose — replacing default blankness with a cue that names the primary affordance and a first action that begins the flow in place. Its defining property is when and where it lives: it owns the entire surface precisely when there is nothing else competing for the user's attention. That makes emptiness — usually a design afterthought — the highest-attention, lowest-noise moment to teach the core action and hand the user straight into it.

Example

A new user opens a note-taking app and lands on an empty "Notebooks" view. Left as a default, it would be a blank pane — a silent dead end. The empty-state prompt fills it instead: a small illustration, the line "No notebooks yet," one sentence on what a notebook is for, a prominent "Create your first notebook" button, and a quieter secondary path, "or import from…". The blank space that conveyed "nothing here" now conveys "here is the affordance, and here is your first move."

The capability to create notebooks was always present in a menu somewhere; what the empty view added was a reason and a route at the exact moment the user had neither. Tapping the button drops them straight into creation rather than back out to hunt for the feature — the cue and the first action are one continuous path, so discovery and doing don't split apart.[1]

How it works

  • Detect the zero-state. Recognize when a container is genuinely empty — first run, or emptied — and treat that as a surfacing opportunity rather than a blank default.
  • Name the affordance in the negative space. Replace blankness with a legible cue: what belongs here, and why, in a glance's worth of words and image.
  • Offer one primary first action (and maybe a quiet second). Provide a button that begins the core flow in place, keeping discovery and the first step on a single unbroken path.

The artifact is distinguished by owning the surface when it is empty: it earns undivided attention not by being loud but by arriving when nothing else is there.

Tuning parameters

  • Guidance depth — a single clear call to action versus a mini-tutorial. More guidance teaches more but reintroduces the clutter the empty moment was free of.
  • Primary vs. secondary actions — how many paths to offer before the first choice. One is decisive; several risk paralysis at the very first step.
  • Tone and illustration — encouraging and warm versus terse and functional. Tone sets whether the blank slate feels inviting or like unfinished chrome.
  • Seed data — pure blank versus pre-filled sample or template content. Seeding shows the payoff but can blur "is this mine or an example?"
  • Re-empty behavior — first-run only, or shown again whenever the container empties. Re-triggering keeps the teaching available; always-on can nag an expert who cleared the list on purpose.

When it helps, and when it misleads

Its strength is capturing the single highest-attention, lowest-competition moment in the whole experience: with nothing else on screen, one clear cue and one first action can carry a brand-new user into the core loop with almost no friction. It is the cheapest place to reduce first-run abandonment.

Its failure modes come from over-loading that quiet moment. An empty state stuffed with tips, upsells, and multiple calls to action becomes its own wall of text and forfeits the clarity that made it valuable — and cramming marketing where the user's first action belongs is the classic misuse, spending the user's attention on a pitch instead of their goal. Seeding fake sample data can confuse ownership. And a prompt can mask rather than fix: if the real problem is that the container is hard to fill, a cheerful empty state decorates the friction instead of removing it. The discipline is one clear primary action, kept as the user's step rather than a sales moment, with any teaching subordinate to it.

How it implements the components

Empty-State Prompt realizes the negative-space side of the archetype — surfacing the primary affordance in the moment a container is empty:

  • negative_space_or_empty_state_cue — its core: it converts blank, "nothing here" space into a legible cue for what belongs there and why.
  • action_path_continuity — the primary button begins the core flow in place, so discovery and the first action stay on one unbroken path.

The in-flow transient hint, empirical placement testing, and entitlement disclosure — affordance_signifier_design as a just-in-time cue, surface_placement_and_timing_rule, rights_and_consequence_disclosure — belong to Contextual Hint or Tooltip, Call-to-Action Placement Test, and Eligibility or Rights Notice; this artifact surfaces the affordance only in the empty-container case.

Notes

The empty-state prompt is ambient and re-triggerable — it reappears whenever the container is empty — where a Guided Walkthrough or Onboarding Step is a one-time sequenced tour. That difference is a reason to prefer the empty state for durable teaching of the core action: it resurfaces exactly when the moment recurs, instead of firing once and never again when the user might most need it.

References

[1] Don Norman's Gulf of Execution names the gap between a user's goal and knowing which action achieves it. An empty state bridges that gulf at the earliest possible point — the user has arrived with an intent but no notion of the first move, and the prompt supplies both the affordance and the step across. ↩