Empty State Audit

An empty state audit is a seven question checklist that tests whether every blank screen in your product actually works. It asks if the screen explains where the user is, offers one primary action, keeps consistent voice, makes the next step one click, feels alive, stays specific to its archetype, and could sell the product by itself.

Teams rarely audit their empty states. They ship whatever the designer with spare time produced and move on. That is the mistake. The audit forces the hard questions before the product reaches users. Skip it and you will wonder why retention curves look like cliffs.

The common confusion is believing a quick visual review replaces the audit. It does not. You must read the copy out loud next to populated screens. You must test if the next step truly takes one keystroke. You must ask whether this screen alone could sell the product. Anything less is self deception.

Run the audit on Linear's empty inbox. It passes every question. Context is clear. One primary action. Voice matches the brand. Hierarchy is tight. The screen feels alive. It is specific to its archetype. A new user seeing only that screen would understand the value. Most products fail at least three questions on their first run screen alone.

Stripe Atlas, Vercel, Notion, and Slack all pass the audit on their strongest empty states. They explain why the screen is empty. They offer one obvious next move. They avoid illustrations that replace thought. They keep motion subtle but present. Their empty states activate instead of apologize.

Run an empty state audit before you ship any major feature or at the end of every quarter. Do not run one if your team is not willing to redesign screens that fail. The tradeoff is comfort versus clarity. The audit will expose painful gaps. Ignoring those gaps protects ego and destroys retention.

Answer every question with a clear yes or the screen is not done. Does it tell the user where they are and why it is empty. Is there exactly one primary action made obvious by contrast. Does the voice match the rest of the product when read aloud. Is the next step achievable in one keystroke. Does the screen feel alive instead of abandoned. Is it specific to its archetype instead of generic. If the user only saw this screen would it sell the product.

Most products fail this audit on day one. The ones that pass activate users without trying.

Audit every empty state before you ship the next feature or accept that your retention problems are self inflicted.