Designing Empty States That Teach, Not Apologize

Most empty states are apologies. "Nothing here yet." "No results found." They describe the absence of something instead of pointing at the action that fills it.

Three questions every empty state should answer

What is this space for, why is it empty right now, and what’s the one action that changes that. If your copy answers all three in under fifteen words, you’re close.

We rewrote every empty state across our dashboard using this frame and saw first-action completion jump noticeably in the following sprint — not because the product changed, but because the screen finally told people what to do.