# Help Users Think About Their Action

> People plan each action, then check the result. Learn how to make both steps clear, with feedback, plain labels and a safe way back.

**In short:** People plan each action and then check the result, so help them with feedback, plain labels and a safe way back.

From "UI/UX basics", a free course by Venkat R. Murty: https://designervenkat.online/learn/ui-ux/help-user-think-about-their-action

## What you will learn

Every time someone uses a product, they try to do something. They tap a button, pick a date or flip a switch. Good design helps that person plan the move and then understand what happened. In this lesson you will learn how people think through an action, where they get stuck, and what you can change to help.

- **Action:** Something a person does with a product, such as tapping a button.
- **Goal:** The result the person wants, such as sending a message.
- **Mental model:** A person's own idea of how a thing works and what will happen when they act.
- **Feedback:** A sign from the product that shows what happened after an action.
- **Gulf of execution:** The gap between what a person wants to do and what the product lets them do easily.
- **Gulf of evaluation:** The gap between what the product shows and how easily a person can understand its state.
- **Undo:** A control that reverses the last action.

## How do people think through an action?

Don Norman, who wrote the book The Design of Everyday Things, describes people as moving through a loop. They plan what to do, do it, and then check the result. A simple version has four steps. Each step is a chance for the design to help or hurt.

1. **Set a goal:** The person decides what they want. A clear page title tells them they are in the right place.
2. **Plan the move:** They look for the control that gets them there. Plain labels and familiar places make this quick.
3. **Do the move:** They tap, type or drag. The control should respond to exactly what they did.
4. **Check the result:** They look for a sign that it worked. If no sign appears, they start to doubt themselves and may try again.

## What are the two gaps?

The loop has two gaps where people often get stuck. Nielsen Norman Group calls them the gulf of execution and the gulf of evaluation. Both gaps are normal. Good design keeps them small.

### Gap one: knowing what to do

The gulf of execution is the distance between what a person wants and the steps the product asks for. If a task asks for many steps that do not seem linked to the goal, the gap is wide. A short path with clear labels narrows it.

### Gap two: knowing what happened

The gulf of evaluation is the effort it takes to read the product's current state. In one case that Nielsen Norman Group describes, a person could clearly see a Bluetooth switch but misread what it meant. They spent over an hour trying to connect a headset that was not the problem. Seeing something does not always mean understanding it.

## Why show what the system is doing?

Visibility of system status is the first of Jakob Nielsen's usability rules. It asks products to keep people informed about what is going on, with feedback that arrives in a reasonable time. Nielsen's rules are rules of thumb, not laws, so check them with real people.

- **Quick response:** A button should change soon after a tap, for example with a colour shift or a checkmark.
- **Honest labels:** A switch label should show the state it is in now, not only what a tap will do next.
- **Progress:** For a slow task, a progress bar shows the work is still running, so people do not tap again.

> **Tip:** Put the status where people are already looking. A message hidden in a log they must open helps nobody.

## How do you give users a way back?

People make mistakes and change their minds. Nielsen Norman Group says users should be able to fix a mistake or go back a step quickly. When they cannot, they feel trapped and report being less satisfied. A clear exit also helps people explore and learn your product.

### Undo, cancel and back

Common exits include Back, Cancel, Close and Undo. Back returns to the last screen. Cancel quits a multi-step task. Close shuts a new view. Undo reverses a change, and redo brings it back. Each one should be easy to find.

> **Tip:** If people have to hunt for undo, many will never find it. Show it right after the action.

## Why confirm only what cannot be undone?

A confirmation box asks 'Are you sure?' before an action runs. People often click through these without reading, so a box alone gives little real control. When an action can be reversed, undo is usually the better choice. Save the confirmation box for actions that cannot be reversed, such as permanent deletion. Too many boxes teach people to click without thinking.

## Try it: a tiny undo history

This short program keeps a record of each change, so the last change can be reversed. It uses only Python's standard library.

```python
history = []
state = 'off'

def toggle():
    global state
    history.append(state)
    state = 'on' if state == 'off' else 'off'
    print('Now:', state)

def undo():
    global state
    state = history.pop()
    print('Undo to:', state)

toggle()
toggle()
undo()

```

Output:

```text
Now: on
Now: off
Undo to: on

```

Each change saves the old state before it changes anything. Undo puts the saved state back. This is the same idea behind the undo buttons people use every day.

## Quick check

**Quick check:** A user taps Save, and nothing on the screen changes. What is the most likely problem?

A. The user cannot tell whether the save worked
B. The button is too big
C. The colour scheme is too dark
D. The user forgot their goal

**Answer:** A. Without feedback, people cannot tell if the action worked, so they may tap again or give up.

## Checklist for your own design

- **Status:** Can people tell what state things are in, and did their last action work?
- **Exits:** Can people go back, cancel or undo without losing their work?
- **Confirmations:** Do you ask for confirmation only when an action cannot be undone?

## Sources

- [Visibility of System Status (Usability Heuristic #1), Nielsen Norman Group](https://www.nngroup.com/articles/visibility-system-status/)
- [User Control and Freedom (Usability Heuristic #3), Nielsen Norman Group](https://www.nngroup.com/articles/user-control-and-freedom/)
- [The Two UX Gulfs: Evaluation and Execution, Nielsen Norman Group](https://www.nngroup.com/articles/two-ux-gulfs-evaluation-execution/)
- [The Design of Everyday Things, Don Norman (book PDF)](https://ia902800.us.archive.org/3/items/thedesignofeverydaythingsbydonnorman/The%20Design%20of%20Everyday%20Things%20by%20Don%20Norman.pdf)
- [User Control and Freedom (Nielsen Heuristic 3), Falcon](https://falcon.so/resources/principles/user-control-and-freedom)
- [Nielsen's 10 Heuristics explained with practical examples, Otther](https://otther.co/blog/nielsen-heuristics)
