Empty states should tell people what to do next
An empty state is not decoration. It is the moment when someone arrives ready to act and finds nothing waiting for them: no messages, no saved items, no search hits, no projects yet.
Too many sites fill that moment with a cartoon and a shrug. “Nothing here yet.” “Your feed is quiet.” “Looks like you haven’t started.” Cute, and useless. The person already knows the screen is empty. What they need is the next step.
Treat the empty state as task design. Ask what the customer came to finish. Then name that task in plain words and put one primary action next to the explanation. “No invoices yet. Create your first invoice.” “No results for that search. Try a shorter phrase or browse categories.” The button should use the same words as the sentence so people do not have to translate.
Secondary actions can help, but only after the main one is obvious. Offer “Import a sample,” “Watch a 30-second setup,” or “Contact support” as quieter links. Do not present five equal buttons. Equal weight is another way of saying you have not decided what success looks like.
Empty search results deserve special care. People who typed a query already told you their intent. Repeating “0 results” without alternatives forces them to guess. Show close matches, popular tasks, or a path back to a reliable index. Silence feels like failure; guided recovery feels like competence.
Keep brand voice in check. Clever jokes about tumbleweeds entertain the design team and leave customers stuck. If you want warmth, make it helpful warmth: short sentences, concrete verbs, no jargon about “journeys” or “spaces.”
Consistency matters across the product. If the empty inbox, empty cart, and empty dashboard each invent a new metaphor, people learn nothing reusable. Use the same pattern: situation in one line, next step in the next, primary control clearly labeled.
Measure empty states the way you measure forms. Track whether people click the primary action, abandon the page, or bounce to support. A charming illustration with a low click-through rate is not delightful. It is a blocked task.
When data will appear later—pending sync, permissions, overnight batch jobs—say so. “Reports refresh every night at 2 a.m.” beats a blank chart. Uncertainty is harder to trust than a clear wait.
Empty states are content, not chrome. Write them with the same care you give homepage headlines. The people who see them are often new, uncertain, or recovering from a mistake. Help them finish something. That is customer-centric design in a blank box.
