When empty states is worth the effort

It comes up on almost every project, usually later than it should. Empty states is not free, and pretending otherwise leads to bad decisions.

Design decisions are the ones clients feel most confident arguing about, which makes it worth separating taste from evidence early. The practical test is whether someone new to the project could tell, in a minute, that it had been handled.

When it is worth it

The first screen a new user sees is usually empty. The teams that handle this well are rarely the ones with the biggest budgets. Anything you cannot measure here, you are deciding by taste, which is fine as long as everyone knows it.

When it is not

If nothing downstream depends on it and nobody is complaining, it can wait. The reasoning matters more than the rule, because the rule has exceptions.

How to decide

Blank space with no guidance reads as broken. The cost of getting this wrong is rarely visible on the day it happens. It is worth deciding this deliberately rather than inheriting whatever the last person set up.

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
• Blank space with no guidance reads as broken — and you know whether that is true here
• There is a way to tell whether the last change to this helped

If any of that sounds like a description of your current setup, it is fixable.