Empty Is a Moment of Intent
If a dashboard has no data, the user is not "not ready." They are asking what this product is for. A blank table with a gray illustration answers nothing. A sentence, a sample, and one action answers almost everything.
Good empty states do three jobs: explain the value, show what good looks like, and provide the next step.
Patterns That Work
- A single primary action, not five
- Example content the user can keep or dismiss
- Honest constraints ("You need billing access to connect a store")
- A way out that does not feel like failure
Patterns That Fail
Humor that ages badly. Illustrations with no instruction. Copy that blames the user for not having data yet. Hidden CTAs below a fold of whitespace.
How We Review Them
In every design critique we ask: if this were the only screen a new customer saw, would they know what to do in the next thirty seconds? If not, the empty state is unfinished, even if the populated state looks beautiful.
Frequently Asked Questions
What Jobs Should an Empty State Do?
Explain the value, show what good looks like, and provide one clear next step. A blank table with a gray illustration answers nothing.
Which Empty-State Patterns Fail?
Aging humor, illustrations without instruction, blamey copy, and CTAs buried under whitespace.
How Should Teams Review Empty States?
Ask whether a new customer would know what to do in the next thirty seconds if this were the only screen they saw.
Ship the Empty Path
Design the empty path with the same rigor as the populated one. Prototype the first-run screen early, test the thirty-second rule, and refuse to call a feature done until the zero-data state teaches the workflow instead of apologizing for it with decoration.