Design empty states that help people get started
Gives you content and layout guidance for every empty state in a feature: first use, no results, cleared, and no permission.
The prompt
Help me design the empty states for a feature in my product.
Feature: [WHAT IT IS - e.g. "project dashboard", "saved searches"]
What the full state shows: [WHAT USERS SEE ONCE THERE IS DATA]
The most valuable first action: [WHAT WE WANT A NEW USER TO DO]
User types who will see it: [e.g. new admin, invited member with view-only access]
Brand voice and illustration style: [e.g. "plain, light illustrations allowed" or "no illustrations"]
Cover each type separately, since they need different responses:
1. First use (nothing created yet)
2. No results (search or filters returned nothing)
3. User cleared it (inbox zero, all tasks done)
4. No access (permissions) or not set up by an admin
5. Error or failed load (so it is not mistaken for "empty")
For each, give: headline, one-line body, primary action (verb-first label), optional secondary action, whether to show sample data or a template, and a layout note (what replaces the table, list, or chart). Keep headlines under 8 words.
Rules: an empty state should explain value and offer one clear next step, not just say "No data". For no-results, show the active filters and a way to clear them. Avoid cute copy where the user may be frustrated. Flag if any state is really a missing feature in disguise.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Product & UX Design prompts
What to fill in
- WHAT IT IS - e.g. "project dashboard", "saved searches"
- WHAT USERS SEE ONCE THERE IS DATA
- WHAT WE WANT A NEW USER TO DO
- e.g. new admin, invited member with view-only access
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Write UX microcopy for buttons, errors, and empty statesClear, on-brand interface text for buttons, form errors, empty states, and confirmations.
- Run a UX teardown of a competitor's product flowBreaks down how competitors handle a specific user flow step by step, comparing patterns, friction, and ideas worth borrowing or avoiding.
- Check my design for dark patterns and manipulative UXReviews a flow for deceptive or coercive patterns, explains user and regulatory risk, and suggests honest alternatives that still meet the goal.
- Make the business case for a UX improvementBuilds a short, numbers-aware pitch that links a design fix to revenue, cost, or risk so leadership prioritizes it.