By the end of this lesson you can
- Recognise common causes of confusing interactions.
- Diagnose confusion using evidence rather than opinion.
- Fix confusing interactions with targeted changes.
The idea
Interactions become confusing for a handful of recurring reasons:
- Hidden controls: actions only available by hover, long press or swipe.
- Ambiguous labels: "Submit", "OK", or icons without text.
- Unexpected results: an action does something different from what people predict.
- Modes: the same action does different things depending on a state people do not notice (such as edit mode).
- Missing feedback: nothing seems to happen.
- Inconsistency: similar things behave differently in different places.
- Irreversible actions without warning or undo.
Diagnosing
Look for evidence: repeated clicks (rage clicks), back-and-forth navigation, support tickets, session recordings, failed tasks in testing. Ask "what did the person expect?" and compare it with what happened.
Fixing
Fix the cause, not the symptom. Adding a tooltip to a confusing icon is a weaker fix than adding a text label. Adding a tutorial for a confusing flow is weaker than simplifying the flow.
Why it matters in real projects
Confusion costs time, causes errors and erodes trust. Being able to diagnose and fix confusing interactions systematically is a core interaction design skill and a common interview topic. It also helps you push back on "just add a tooltip" fixes.
A realistic example
A photo app's delete action is a swipe left. Session recordings show many people swiping left to see the next photo, deleting images by accident. Support tickets about missing photos rise.
The team diagnoses the conflict with the common "swipe to browse" mental model. They change swipe to browse, move delete to a visible bin icon with a label, and add an "Undo" toast plus a "Recently deleted" folder. Accidental deletion tickets drop sharply.
Step by step
Collect evidence
Gather support tickets, analytics and test notes.
Identify the moment
Pinpoint where confusion happens.
Compare expectation and reality
Write what people expected and what happened.
Name the cause
Match it to one of the common causes.
Fix the cause
Design a fix that removes the confusion rather than explaining it.
Verify
Test the fix and watch the evidence change.
Common mistakes
Mistake Adding tooltips or tutorials to patch confusion.
Instead Fix the underlying interaction.
Mistake Relying on opinions.
Instead Gather behavioural evidence.
Mistake Irreversible actions without undo.
Instead Add confirmation or undo.
Check your understanding
Choose an answer, then check it. There is an explanation either way.
Practice exercise
Exercise · about 45 min
Confusion diagnosis
Find and fix a confusing interaction in a product you use.
Steps
- Identify a confusing moment and collect evidence.
- Write expectation versus reality.
- Name the cause.
- Design and justify a fix.
Deliverable
A one-page diagnosis and redesign.
Self-assessment
Tick each item when it is true of your exercise. Be honest; this is for you.
4 items
Summary
- Confusion has common causes.
- Diagnose with evidence and expectation versus reality.
- Fix causes, not symptoms.
- Verify fixes with testing.
Further reading
Third-party sources, chosen for reliability. They open in a new tab.
- Modes in user interfaces (opens in a new tab)Nielsen Norman Group
- Icon usability (opens in a new tab)Nielsen Norman Group
Your notes
Marking complete updates your course and roadmap progress.