What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
An empty state should explain why expected content is missing and, when useful, show what to do next. First identify the cause: the area has not been set up, a search returned no matches, the user completed a task, or the system failed. Each situation needs different feedback; a generic blank screen—or a premature “no results” message—can leave people unsure what happened.
Start by identifying why the space is empty
“Empty state” describes several different situations, not one reusable screen. Before writing copy, determine what caused the absence, whether processing has finished, and whether the user needs to act. SAP Fiori groups empty states into no-data, user-action, and error situations; Morningstar likewise distinguishes cases following a user action from cases where the user needs to act.
As an Amazon Associate I earn from qualifying purchases.
| Cause | Has processing finished? | Does the user need to act? | Useful response |
|---|---|---|---|
| First use or not configured | Usually, yes: there is no content yet. | Often, if the user can create or set up the content. | Explain what belongs here and provide a direct route to begin. |
| Search or filter has no matches | Yes, once the search or filter has completed. | Usually, if changing the query or criteria could help. | Name the searched content and suggest an available adjustment. |
| Task completed | Yes. | Not necessarily; the task may be finished. | Confirm completion without adding unnecessary instructions. |
| Error or access problem | The requested content could not be shown. | Possibly; explain a corrective step when one is available. | State the problem in human-readable terms and identify a useful recovery path. |
The table is a starting point, not a fixed component specification. The appropriate presentation depends on the situation and the surrounding page layout.
What should an empty state say when there are no results?
Make the message specific to what the user expected to find. “No results” may be accurate, but naming the searched content gives people a clearer account of what came up empty. If the interface supports a sensible change—such as broadening the search or removing a filter—offer that as the next step. Do not recommend actions the interface does not provide.
For example, a search screen could say, “No matching invoices. Try a broader date range or clear a filter.” Use only the part that fits the actual search controls. If results might be missing because an object was removed or is no longer available, avoid implying that the search itself is necessarily wrong.
Give first-time users a way to get started
When a feature has not been used or configured, say what will appear in the area and how to add the first item, if the user has permission to do so. A useful message might read: “Your saved reports will appear here. Create a report to get started.” Link the primary action directly to the relevant creation or setup flow rather than making users search for it elsewhere.
Nielsen Norman Group recommends using empty states to communicate system status, help users discover features, and provide direct pathways to tasks. That makes this moment a practical place for a concise explanation or cue—not a reason to add a lengthy tutorial.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesKeep loading separate from a completed search
An empty result is only accurate after the system has finished checking. While a request is still running, show progress or another truthful status instead. Nielsen Norman Group describes the problem of displaying “No records” before records have finished loading, and advises using progress indicators when a process is running.
Rank #3
Only change to a no-results message once the search or data request has completed and returned no content. If the request fails instead, show an error state rather than presenting the failure as a successful search with zero matches.
Confirm completion without inventing another task
When content is absent because the user successfully finished an action, the empty area can simply confirm the outcome. For example: “All reminders are complete.” Add another action only if there is a meaningful next step. Extra instructions or a create button can make a completed task feel unfinished.
Explain errors and access problems plainly
If the system cannot show content, tell users that it could not load or that they do not have access, as appropriate. Pair the explanation with a corrective action when one is available—for example, retrying after a temporary failure or requesting access through the product’s established process. Do not disguise an error as “No results,” which suggests the search succeeded.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Nielsen Norman Group’s error-message guidance calls for human-readable messages and cautions against communicating an error only through color or animation. The message should remain understandable without relying on a visual cue alone.
Best Value
Choose the message and action for the context
Keep the main point quick to find: what is missing, why it is missing when that is known, and what the user can do next when action would help. eBay’s guidance emphasizes a clear primary message and warns against empty states that offer no resolution or too many possible actions. A single relevant action is often clearer than a cluster of competing buttons.
- Known cause: Explain it directly, such as “No matching files” or “You haven’t added a project yet.”
- Useful action available: Offer the most relevant next step, such as adjusting criteria or creating the first item.
- No action needed: Confirm the outcome and let the user move on.
- Cause not yet known: Do not guess. Show an accurate status while checking, or explain the failure if the system cannot complete the request.
The guidance from Nielsen Norman Group, SAP Fiori, Morningstar, and eBay is design advice, not a universal rule or a quantified claim about how much an empty state improves outcomes. Treat the exact wording and layout as dependent on the interface and situation.
Quick Recap
Sources
- Nielsen Norman Group: “Designing Empty States in Complex Applications: 3 Guidelines”, Kate Kaplan, September 19, 2021.
- SAP Fiori Design Web: “Empty States”.
- Morningstar Design System: “Empty States”.
- eBay Playbook: “Empty states”.
- Nielsen Norman Group: “Error-Message Guidelines”, published 2023.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
