Field note

The cost of a blank dashboard

An empty product is not a neutral starting point. It asks the user to supply structure, confidence, and momentum before the system has earned anything.

August 16, 2026

Blank dashboards are common because they are easy to ship. They also place an invisible amount of work on the person who arrives first.

An empty screen says: decide what belongs here, understand how the system thinks, and create the first meaningful state without any proof that the effort will pay off.

Empty is a state

The absence of data is still information. It may mean a project is new, an integration has not happened, a task is waiting for a decision, or the product does not yet know enough to help.

Treating all of those situations as the same empty table makes the product feel indifferent. The first useful question is not “how can we fill the screen?” It is “what should this person understand and do next?”

The first-run job

Every product has a first-run job. Sometimes it is to help someone create a project. Sometimes it is to choose a source, write a brief, connect a system, or understand the limits of the tool.

The interface should make that job tangible. Give it a name, a short path, and enough context to show why it matters. Avoid theatrical sample data that makes the product look busy but disappears when the person starts real work.

Show ground truth

Useful empty states distinguish between what the user needs to do and what the system already knows. They make progress visible even before there is much content: a saved brief, a connected source, a completed setup step, a status that can be checked.

This is especially important in AI products. The system may be capable of generating something impressive immediately, but the person still needs to know what is durable, what is editable, and what will be there on their second visit.

A good first state gives the user a reason to begin. It does not make them invent the product's purpose on its behalf.