How to audit empty states

Action play: Go through your product and look at every empty state (no data, no results, first-time screens). Ask: "Does this screen help the user take the next step?"

• Example: When a user has not designated any items as favorites or has not opened any files yet, containers meant to display lists of favorite or recently viewed items will be empty.
• Example: When an application supports alerts, but a user has not yet configured any alerts, there may be an empty pane or dialogue where those alerts will eventually appear.
• Example: When an application is composed of various workspaces or dashboards, but a user has not added content to those areas, those pages or screens will be empty.
• Example: Search results lists when nothing is found, as well as other cases where a command creates empty output.

Why: Empty states are often forgotten, but they shape first impressions and can turn confusion into momentum.