Before you invest in empty states

Most teams know this matters. Fewer have decided who owns it. Before you spend anything on empty states, it is worth confirming a few things are already true.

Design decisions are the ones clients feel most confident arguing about, which makes it worth separating taste from evidence early. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.

Prerequisites

• You can describe the outcome you want in one sentence
• Someone owns it after the work is done
• The first screen a new user sees is usually empty
• You have a way to tell whether it worked

Where it usually goes wrong

An empty state should teach the next action. The reasoning matters more than the rule, because the rule has exceptions. If two people in the business would answer this differently, that gap is the actual problem.

Blank space with no guidance reads as broken. This is the sort of thing that compounds, quietly, in both directions. Write the reasoning down alongside the decision, because the reasoning is what changes first.

In practice

The measurable part of design is whether people can find what they came for and act on it without hesitating. Three things worth confirming about empty states before you move on:

• Someone can say what the current setup is without going to look
• An empty state should teach the next action — and you know whether that is true here
• There is a way to tell whether the last change to this helped

If you are not sure where your systems currently stand on this, it takes us about an hour to find out.