What the pattern needs to do
An empty state is not decorative relief. It is a transition moment. The page has to explain the missing data, describe what a successful screen will look like, and point to the next useful action.
When those three jobs get separated, the page turns into either marketing copy or a dead end.
Good empty states are specific
The strongest examples refer directly to the object the user has not created yet, the import that has not finished, or the permission they do not have. Generic reassurance wastes the most valuable moment on the page.
That is why empty states often work best when paired with one clear Button instead of multiple competing actions.
What to avoid
Do not confuse a loading problem with a true empty state. The user needs different language for "nothing exists yet" than for "we have not loaded anything yet."
Also avoid over-illustrating the screen. Decorative scenes can help with tone, but if the image becomes the loudest element, the actual next step is buried.
Adjacent patterns
This pattern often shares space with onboarding, inline creation, and Form Field guidance. The difference is that an empty state frames the absence first, then offers a route forward.