Empty states: what to get right first

The gap between knowing this and actually doing it is where most teams lose ground. If you only fix one thing about empty states this quarter, make it the first item below.

Design decisions are the ones clients feel most confident arguing about, which makes it worth separating taste from evidence early. Budget a little time for it every quarter and it never becomes a project of its own.

Start here

The first screen a new user sees is usually empty. Getting it slightly wrong is survivable. Ignoring it entirely is not. Write the reasoning down alongside the decision, because the reasoning is what changes first.

Then this

An empty state should teach the next action. Getting it slightly wrong is survivable. Ignoring it entirely is not. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

Eventually

Blank space with no guidance reads as broken. It is worth being explicit about, because assumptions differ quietly. The version that survives contact with a real deadline is the simple one.

The short version

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.