Support Conscious Action: Help People Choose on Purpose
Learn why people slip or make mistakes, and how clear design, smart confirmations and honest choices help people act on purpose.
In short
Supporting conscious action means helping people avoid slips and mistakes with clear design, smart confirmations and honest choices.
4 min readFree
What you will learn
Good design helps people do what they mean to do. This lesson is about supporting conscious action. You will learn why people slip or make mistakes, when to ask for confirmation, and how to avoid tricks that push people around.
Key words
- Conscious action
- A step a person takes on purpose, knowing what it will do.
- Slip
- A wrong action taken while aiming for a sensible goal, often while on autopilot.
- Mistake
- A wrong goal chosen because the person's picture of how the screen works is wrong.
- Mental model
- The picture in someone's head of how a system works.
- Signifier
- A visual cue that shows how an element can be used, such as a shadow that makes a button look pressable.
- Confirmation dialog
- A pop-up that asks the user to confirm before a command runs.
- Undo
- A way to reverse the last action.
- Dark pattern
- A misleading design that pushes people toward choices they did not mean to make.
Why do people make errors?
The Nielsen Norman Group, a UX research firm, follows Don Norman's split of user errors into two groups: slips and mistakes. Each type needs a different fix.
What are slips?
A slip happens when someone is on autopilot and takes a wrong action on the way to a sensible goal. Slips often happen when two choices look alike or sit too close together. Simple tools help. Designers can add safeguards and validation that catch wrong actions before they cause harm.
What are mistakes?
A mistake happens when a person's mental model does not match how the interface really works. The person then picks a goal that does not suit the situation. To prevent mistakes, learn what users expect before you build. Interviews and simple usability tests can show where your picture and the user's picture differ.
Make the right action easy to see
People act on what they can see. These three ideas help.
Use familiar conventions
People expect common parts to look and behave the way they always have. Keep standard patterns unless you have a strong reason not to.
Show signifiers
A button with a slight shadow looks pressable. An empty field with a light inner shadow looks typeable. These cues tell people what they can do.
Preview results
Show what will happen before the person commits. A preview lets people check their choice while they can still change it.
When should you ask before big moves?
A confirmation dialog gives the user a second chance before a command runs. It helps only when people read it. If it appears too often, people click Yes without thinking, and the protection is lost.
When a question helps
- 1
Find the serious actions
Ask only before actions with serious results, such as losing work or spending money. Be extra careful with actions that cannot be undone.
- 2
Keep routine actions quiet
Do not ask about every normal step. Repeated questions teach people to ignore them.
- 3
Name the effect
Say exactly what will happen, such as the file name. A vague question like Are you sure? gives people nothing to check.
- 4
Label buttons with outcomes
Use buttons such as Delete file and Keep file instead of Yes and No, so each choice states its result.
Tip
Ask yourself: if this question appeared every hour, would people still read it? If not, ask less often or make it more specific.
How do you give a way back?
A question is a backup, not the main safety net. Nielsen Norman Group says designers should try their best to offer undo, because undo helps people recover from big problems and lowers anxiety.
Never trick the user
Some designs are built to mislead. A dark pattern, also called a deceptive pattern, tricks people into choices they did not intend. The term was popularised by UX researcher Harry Brignull, who collected examples. Dark patterns often serve the business at the user's expense, so they directly undermine conscious action.
Common tricks to avoid
Confirmshaming
Guilt-filled wording, such as a decline button that says No, I do not want to save money, makes people feel bad for saying no.
Hidden costs
Fees that appear only at the final step make people pay for things they did not plan to buy.
Tip
Show your wording to a friend. If they would feel tricked, fix the design before you ship.
See it in code
This short program shows the core idea. The file is removed only when the user has confirmed.
def delete_file(files, name, confirmed):
if not confirmed:
return files
return [f for f in files if f != name]
files = ["notes.txt", "photo.jpg"]
print(delete_file(files, "photo.jpg", False))
print(delete_file(files, "photo.jpg", True))
Output
['notes.txt', 'photo.jpg'] ['notes.txt']
Quick check
Quick check
A form asks Are you sure? before every single save. What is the main problem?
Sources
- Nielsen Norman Group: Preventing User Errors: Avoiding Conscious Mistakes (Page Laubheimer, 2015)
- Nielsen Norman Group: Confirmation Dialogs Can Prevent User Errors, If Not Overused (Jakob Nielsen, 2018)
- Nielsen Norman Group: What the Erroneous Hawaiian Missile Alert Can Teach Us About Error Prevention (Kim Flaherty, 2018)
- The Decision Lab: Dark Patterns
- The Decision Lab: Nielsen's Heuristics
- Sue Behavioural Design: What is a dark pattern? Deceptive UX explained
- Usercentrics: Avoid Dark Patterns: Privacy Compliance Best Practices
Last updated on 17 November 2026
Related lessons
Learn with me
Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.