Empty state brief
Design empty states that accurately explain what happened and offer the safest relevant next action.
Product features · 30 min · Starter · 10 questions
Empty-state diagnosis
Which distinct conditions can produce an empty surface?
Can the product reliably distinguish each empty condition from the available data?
What may be disclosed when content exists but the current user cannot view it?
What should appear while content is importing?
What should appear while content is indexing?
What should appear while content depends on another person?
Content and next action
Which single next action is safest and most relevant for each empty condition?
Would one realistic example clarify what comes next?
What must the empty-state message explain?
How will the team know the empty state helps rather than traps users?
How to use this brief
Use this brief as a bank of questions for the conversation. Choose what is relevant, mark covered questions as you go, and skip anything that has already been answered.
Use this brief when...
Use when you need to design empty states that accurately explain what happened and offer the safest relevant next action.
Best used as: Live call · Async intake
- Category
- Product features
- Discussion time
- 30 minutes
- Depth
- Starter
- Last updated
- Jul 21, 2026
- Scope
- Design briefs
- Best used as
- Live callAsync intake
- Design roles
- Product designerUX/UI designer
- Audience
- Product designersUX and UI designersProduct managersFreelancers and consultants
- Platforms
- WebMobile
- Company type
- StartupB2BB2C
- Product stage
- Early-stageGrowthMature product
- Tags
- product-featuresempty-stateproduct-and-experiencefirst-useno-resultsmissing-access