Thinking

Five Ways a Screen Can Be Empty

Design Systems·March 31, 2026·2 min read

Most design systems have one empty state component, and it’s usually the wrong one.

Open almost any design system and find the empty state. There’ll be a little illustration, a headline, a line of copy and maybe a button, and the same one gets used everywhere.

That’s how you end up telling someone who just cleared their whole inbox how to get started.

An empty screen can mean very different things, and the person looking at it feels different each time. Someone brand new has nothing yet, so they need to know what this space is for and what to do first. This is the empty state that moves business numbers, because a confusing first screen is where a lot of people leave.

Projects
Projects
Templates
Archive

No projects yet

Projects keep your work organised. Create one to get started. You can invite your team once it's set up.

Create your first project
Clear headline, one sentence of context, single primary action. The user knows exactly what to do.

Someone who just finished everything is in a great mood. Don’t ruin it with onboarding copy. Tell them they’re done and get out of the way.

Inbox

All caught up

Nothing left to review. Check back later or take a well-earned break.

No CTA, no instructions. The accomplishment is the message. Getting out of the way is the design.

If you searched and got nothing, you’re a bit frustrated and wondering if you did it wrong. You already know the product, so you need help getting unstuck, like a quick way to clear your filters.

Suppliers

No suppliers match these filters

Try removing one or more filters to broaden your search.

Clear all filters
Echoes the query so the user knows the system understood. Offers one clear recovery action.

Then there’s the screen that’s empty because something broke. Say what happened and tell them what to do next, without making it sound like their fault. “Something went wrong” on its own doesn’t tell anyone anything.

Reports

Couldn't load your reports

There was a problem connecting to the server. Your data is safe. Try refreshing or check back in a few minutes.

Try again
Honest about failure, reassuring about data safety, specific action. Not “something went wrong.”

And the one nobody designs on purpose: the content exists, but this person isn’t allowed to see it. Enterprise products are full of these, and they usually look exactly like an error or a first-use screen. Users can’t tell whether to wait or ask someone, so they file a support ticket.

Finance reports
Overview
Finance
Operations

Finance reports are restricted

Access is limited to Finance team members. Contact your admin or request access below.

Request access
Names the restriction, explains who has access, provides a path forward. Not an error, not an empty page.

So I document these as separate patterns, each with its own copy rules and its own next step. Before any empty state ships, I want to know why it’s empty and how the person feels when they see it. Then I give them one useful thing to do.

State type
User’s emotional state
Design job
First use
No content created yet
How they feel
Anticipatory, uncertain. They don't know what to do yet.
What to do
Orient and activate. What is this, why does it matter, what do I do first.
User-cleared
Task completed, inbox zero
How they feel
Accomplished. They earned this emptiness.
What to do
Celebrate and get out of the way. Not "here's how to get started."
No results
Search returned nothing
How they feel
Mild frustration. Did they do something wrong?
What to do
Disambiguate and recover. Confirm you understood, give a next step.
Error state
System failed to load
How they feel
Mildly annoyed to concerned. Did something break?
What to do
Be transparent. Say what happened and what they can do.
Permission state
Content exists, no access
How they feel
Confused. They expected to see something here.
What to do
Explain without condescension. Who has access, how to get it.

One more opinion while I’m here. The illustration is decoration. It sets the mood, and I like a good one, but the copy does the actual work. If you only have time for one, write the words.

References

  1. Nielsen Norman Group (2021). Designing Empty States in Complex Applications: 3 Guidelines. nngroup.com
  2. Carbon Design System (IBM). Empty States Pattern. carbondesignsystem.com
An empty screen still has a job to do. 🧙 An empty screen still has a job to do. 🧙 An empty screen still has a job to do. 🧙 An empty screen still has a job to do. 🧙