JOURNAL / PRODUCT DESIGN

An empty screen should say which kind of empty it is

First use, no results, cleared and unavailable look alike but need different words and next steps. Start by naming the cause.

· 5 MIN READ · Blanche Agency
Engraving-style illustration of an open, empty wooden drawer with four blank paper tags tied to its brass handle.
Original AI-created conceptual illustration; exact Blanche logo composed separately. · Blanche Agency · aiBLANCHE / 2026

INTRODUCTION

“Nothing here yet” is one of the most reused sentences in software. It appears on a new account with no projects, on a search that matched nothing, on an inbox someone has just cleared and on a dashboard whose data failed to load. Those are four different situations. The person looking at each of them needs a different explanation and a different next step.

So the useful decision is not which illustration to put in the middle of a blank screen. It is which kind of empty you are designing, because that determines what the screen should say and what it should offer.

Four reasons a view can be empty

IBM’s Carbon Design System empty states pattern (last updated in August 2026) is a useful map. It describes empty states that occur during first use, as the result of a user action, and when data exists but cannot be shown. Pull those apart and you get four practical causes.

First use: nothing has been created yet. The screen should say what will appear here and offer the one action that creates it. No results: a search or filter excluded everything. The screen should repeat what was asked and suggest changing it. Cleared: the person finished something, such as an inbox or a task list. The screen can confirm that state and often needs no action at all. Unavailable: the data exists but could not be loaded, or the person lacks permission. The screen should say why and what would change it.

Each cause has a different owner. First use belongs to onboarding, no results to search and filters, cleared to the core workflow, and unavailable to engineering and access control. When a single “empty” component serves all four, nobody owns the message and it drifts towards the vaguest sentence that fits everywhere.

Why the generic version causes harm

A generic empty state does more than miss a chance to be helpful. It can actively mislead. If a permissions failure shows “You have no reports yet”, an administrator may create duplicate reports that already exist. If a failed request shows the same calm message as a cleared inbox, someone may believe their work is done when it was never loaded.

Carbon’s guidance on error-related empty states is specific: explain why there is no data, and either what the person can do or the circumstances under which data would appear, in plain language. Its table covers permission issues, system problems and missing configuration. That is a product decision, not a copy-polish task, because the interface has to know which cause it is in before it can say anything honest.

There is an accessibility side as well. Carbon recommends that the empty state replace the element it stands in for, so a screen reader does not read an empty table’s headers before reaching the message. And WCAG 2.2 success criterion 4.1.3 gives “No results returned” as an example of a status message that assistive technology should be able to announce without moving focus. A no-results screen that only sighted users notice is incomplete.

The counterargument: do not over-design emptiness

A fair objection is that empty states are transitional. Most of a product’s life is spent with data on screen, and four bespoke variants per view can look like effort spent on the least-visited pixels. Some teams also worry that a cheerful first-use screen with a big button delays people who already know what they want.

The objection holds for decoration, not for diagnosis. You do not need four illustrations. Carbon itself suggests text-only empty states where space is limited or many widgets may be empty at once. What you do need is for the system to pass the cause to the interface, so the sentence can be true. That is usually a small change: an error code or a filter count reaching the view, instead of an empty array.

A worked example: one list, four messages

Picture a hypothetical project-management tool with a “Client reviews” list. With a single component, every case shows “No reviews yet” and an “Add review” button.

Split by cause, the same list says different things. On first use: “Reviews you request from clients will appear here,” with one button to request a review. With no results: “No reviews match ‘overdue’ and ‘Studio Lena’,” with a link to clear the filters, announced as a status message. When cleared: “All reviews are answered,” with no button, because nothing is required. When unavailable: “Reviews could not be loaded. Your other work is saved,” with a retry, or “You need project access to see reviews,” with who to ask.

None of those needs artwork. Each one prevents a specific wrong move: requesting a duplicate review, believing the client has replied, or creating work that already exists. It also connects to how a product handles returning to unfinished work: an empty view is often the first thing someone sees when they come back.

Start with an inventory, not a component

Before designing anything, list every view in your product that can be empty. Next to each, write which of the four causes can occur there and what the person should do in each case. Some views will only ever have one cause; others will need all four.

Then make sure the data layer can tell them apart. If the API returns the same empty list for “no permission” and “no items”, no amount of copywriting will fix the screen. Fix that first, then write one honest sentence per cause. A blank screen is part of the product too; it should know why it is blank.

Sources checked on 15 November 2026: the Carbon Design System empty states pattern and WCAG 2.2 Understanding 4.1.3 Status messages. The project-management example is hypothetical and does not describe a Blanche client.

KEEP THINKING

Keep reading.

More ideas on building better brands and digital products.

Product design

A placeholder is not a label

Product design

Design the return to unfinished work

View all articles