Identify why nothing is shown
A list can be empty because no information exists, a filter excludes it, a task has not started, or the product could not retrieve a result. These states imply different next steps. A generic “Nothing here” message can conceal the distinction.
Begin by mapping the possible reasons for the display. The product team needs to define which state can be established and which must remain uncertain before the content can explain it accurately.
Offer an action that fits the situation
A first-use screen may help the person begin a task. An empty search result may explain the applied criteria. A failed retrieval may provide a way to retry or return later. The action should respond to the actual state rather than repeat a standard button everywhere.
If a proposed action can change information, explain the relevant consequence. A recovery path should not require the person to risk creating a duplicate or losing context.
Preserve useful context
An error message should not make the person reconstruct the task from the beginning when relevant context can remain visible. The original goal, selected item, or entered criteria may help them choose an appropriate next step.
Research should examine the transition into the state as well as the message itself. A technically accurate sentence can still be confusing when it appears without the information needed to interpret it.
Observe the next decision
Ask what the person thinks happened and what they would do next. Their response can distinguish an unclear explanation from a missing product capability. Review a genuine absence, a filtered result, and an unresolved retrieval as different scenarios.
The findings should connect each state to the observed belief and action. A revised message may resolve the problem, or the product may need an additional state distinction before a truthful explanation is possible.