# Status Reports: Tell Users What the System Is Doing

> Learn when to show status, how long people will wait, and which progress signal to pick.

**In short:** A status report tells users what the system is doing. Show it during waits, pick a progress signal that fits how long people will wait, and confirm what happened.

From "UI/UX basics", a free course by Venkat R. Murty: https://designervenkat.online/learn/ui-ux/status-reports

## What You Will Learn

A status report tells the user what the system is doing right now. Designers call this showing system status. When people can see status, they know whether their action worked and what to do next. In this lesson you will learn when to show status, which signal to pick, and how to keep a long wait from feeling endless.

- **Status:** The current state of a system, such as loading, saved, or failed.
- **Feedback:** A sign the system gives back after a user acts, such as a message, a colour change, or a sound.
- **Response time:** The gap between a user's action and the system's reply.
- **Progress indicator:** A visual sign that work is going on. It can be a bar, a spinner, or a message.
- **Spinner:** A small icon that turns round and round. It shows work is happening, but not how far along it is.
- **Percent-done bar:** A bar that fills from empty to full as the work moves toward 100 percent.
- **Heuristic:** A rule of thumb that helps designers check whether a screen is easy to use.

## Why does status matter?

Jakob Nielsen wrote a well-known list of ten usability heuristics. The first one is visibility of system status. It asks designers to keep people informed through feedback that arrives in a reasonable time.

- **What just happened?:** Confirm that the system got the action and what it did with it.
- **Where am I?:** Show the current place in a process, such as a step number or a highlighted menu item.
- **What is happening?:** Show that work is in progress, so people do not have to guess.
- **What will happen next?:** Tell people the next step, or roughly how long they must wait.

When these answers are missing, people feel unsure, lose trust, and make mistakes.

## What are the three response time limits?

Nielsen's research gives three limits for response time. They describe how a delay feels to a person, not only how many milliseconds have passed.

- **About 0.1 second:** The system feels instant. People feel they are directly moving things on the screen. No special sign is needed beyond the result itself.
- **About 1 second:** People notice the pause, but their train of thought stays intact.
- **About 10 seconds:** This is roughly the longest time people keep their attention on a task. After that, they start thinking about other things.

> **Tip:** Feedback matters most when the delay can vary a lot. If people cannot predict the wait, they need a sign that work is still going.

## How do you choose the right indicator?

Pick your signal by asking how long the wait is and whether you can measure the work. Follow these steps in order.

1. **Check for a very short wait:** If the result appears in about 0.1 second, show the result and nothing more.
2. **Use a spinner when progress cannot be measured:** A spinner is a last resort, used only when you cannot show progress in absolute terms, such as naming each item processed.
3. **Use a percent-done bar when you can measure:** If you know how much work is left, fill a bar from 0 to 100 percent. Percent-done indicators are recommended for operations over about 10 seconds.
4. **Plan for waits over 10 seconds:** Show percent done or time left.

Use the indicator that matches the wait. Do not use a heavy progress bar for a task that ends almost at once.

### Why do static signs fall short?

A static sign shows that something exists, but it does not show movement or progress. NN/G discusses indicators that show the system is working without showing what it is doing, and presents them as a last resort. A spinner at least shows that the system is alive.

NN/G says progress indicators reduce uncertainty and make waiting more tolerable. A bar that fills toward done helps people choose whether to wait or to leave.

## How do you confirm what happened?

After a user acts, a short message confirms the result. Place the message where the user is already looking, not in a log that they must open.

> **Tip:** Show failures as clearly as successes. Say what went wrong and what the user can do next.

## How do you plan for long waits?

Some jobs take minutes, such as processing a large data set. For these, show how much work is done and how much remains. NN/G recommends giving this information for any wait longer than 10 seconds. Where it fits, let the job run in the background, so people can keep working.

### How do you help people come back?

Show a clear done state, and make it easy to see what changed while they were away.

## Try a Text Progress Bar

This short program draws a percent-done bar in plain text. It uses only the standard library. Each step fills a little more of the bar.

```python
def progress_bar(done, total, width=10):
    filled = done * width // total
    percent = done * 100 // total
    return "[" + "#" * filled + "-" * (width - filled) + "] " + str(percent) + "%"

for step in range(0, 11, 5):
    print(progress_bar(step, 10))
```

Output:

```text
[----------] 0%
[#####-----] 50%
[##########] 100%
```

Each line shows the filled part of the bar and the percent done. The bar is ten characters wide, so each step of one unit fills ten percent of it.

## Check Your Understanding

**Quick check:** A file upload takes about 25 seconds, and the file size is known. Which indicator fits best?

A. No indicator, because users rarely look at the screen
B. A percent-done bar, with a clear way to stop the upload
C. A spinner with no words, shown until the upload ends

**Answer:** B. Waits over 10 seconds need percent-done feedback and a clear way to interrupt the job. A known size lets you measure progress.

## Key Takeaways

Tell users what is happening, and do it quickly. Match the signal to the length of the wait. Use a percent-done bar when you can measure progress, and a spinner when you cannot. Confirm results and failures in plain words, close to where the user is looking.

## Sources

- [NN/G: Response Time Limits: The 3 Important Limits (Jakob Nielsen)](https://www.nngroup.com/articles/response-times-3-important-limits/)
- [NN/G: Progress Indicators Make a Slow System Less Insufferable](https://www.nngroup.com/articles/progress-indicators/)
- [NN/G: Designing for Long Waits and Interruptions in Complex Application Design](https://www.nngroup.com/articles/designing-for-waits-and-interruptions/)
- [The Decision Lab: Nielsen's Heuristics](https://thedecisionlab.com/reference-guide/design/nielsens-heuristics)
- [Human Standards: Nielsen's 10 Usability Heuristics](https://www.humanstandards.org/interaction-patterns/nielsen-heuristics/)
- [uxcel: 10 Usability Heuristics by Jakob Nielsen](https://uxcel.com/lessons/usability-heuristics-270)
- [Adobe Commerce Pattern Library: Progress indicator](https://developer.adobe.com/commerce/admin-developer/pattern-library/feedback-to-user/progress-indicator)
- [UX Tigers: Progress Indicators Ease the Wait](https://www.uxtigers.com/post/progress-indicators)
