The Underrated Craft of Empty States
An empty state is a first impression, a teacher, and a nudge. Why most teams get it wrong and a checklist for getting it right.
Three jobs an empty state must do
An empty state is the first thing a user sees in a new feature. It is also the first thing they see when they have cleared everything out. It is both a welcome mat and a completion screen. Most teams treat it as an afterthought — a placeholder that says "No items yet" — and miss the opportunity entirely.
A good empty state does three jobs. It explains what this space will contain. It tells the user what they can do next. And it does both without sounding like a manual. The best empty states read like a helpful colleague leaning over your shoulder, not a system message.
The checklist
Does the empty state explain what will appear here? If the user cannot predict what this space will look like when it is full, they do not understand the feature. Use concrete examples, not abstractions. "Your published articles will appear here" is better than "Your content will appear here."
Does it offer a clear next action? The user should not have to guess what to do. A button with a clear verb — "Write your first article," "Import your contacts," "Connect your first account" — is almost always better than a passive description.
Does it avoid blame? Never make the user feel like they did something wrong by not having data yet. "You have no projects" is accusatory. "Start your first project" is an invitation. The difference is tone, and tone matters.
