Empty States
The psychology of first-use moments and how designed empty states can drive user activation.
Plain English
An empty state is the first impression for a new user after sign-up. A blank screen with "No data" feels abandoned. A designed empty state that explains what belongs here, shows what it will look like when filled, and provides a clear next action feels like a product that wants to help. The psychological principle: users need to see the potential of the space before they will invest in filling it.
Research background
Empty states trigger the 'completion loop' psychology — users are motivated to fill gaps and complete sets. Design exploits this with: (1) Illustrated states that visualise the desired end state. (2) Checklists that make progress visible and satisfying. (3) Sample data (with clear labelling as sample) that shows the product's value before user data exists. (4) Social proof in the empty state ('1,000 users added their first project today'). First-run experiences should be designed as a separate product moment, not an afterthought.
UI examples
✓ Applying the principle
An empty Kanban board that shows example cards in muted/ghost style with a "Here's what a filled board looks like" caption — visualises the end state before the user starts.
✗ Violating it
A blank screen after sign-up with no guidance, no empty state design, and no obvious next step — high abandonment rate.
AI Prompt
Paste into Claude, Cursor, Bolt, or v0.
Design first-run empty states: illustrated graphic of the desired outcome, 1-line explanation of what belongs here, 1-line description of the benefit, and a primary CTA ('Create your first project'). Consider ghost/sample data to show potential.