Design teams we learn from
Five Whys is the set of cues that tell people what they can do next and why it makes sense. When it's strong, users move fast and feel confident.
Definition
Plain-English definition
Five Whys is the set of cues that tell people what they can do next and why it makes sense. When it's strong, users move fast and feel confident.
Why it matters
It shapes trust. When the interface keeps its promises, people keep moving.
Real-world example
A primary button that looks disabled but still works, or a menu icon with no label.
Full explanation
Here's a quick gut check for Five Whys: could a first-time user explain what to do without help? If not, the design is asking them to learn the system instead of helping them finish the task. That's a bad trade. Good Five Whys makes the next step obvious and the outcome feel earned.
Example: a checkout button that looks disabled but still works. That breaks trust fast. Or an icon-only toolbar with no labels. Experts might get it; beginners won't. Small decisions like these define the real experience, not the marketing copy.
Start by mapping the steps, then strip out anything that doesn't help the task. Use real user language, not internal jargon. Keep the important action loud and everything else calm. Test early with rough prototypes; you'll learn faster and waste less time polishing the wrong thing.
Example: a checkout button that looks disabled but still works. That breaks trust fast. Or an icon-only toolbar with no labels. Experts might get it; beginners won't. Small decisions like these define the real experience, not the marketing copy.
Start by mapping the steps, then strip out anything that doesn't help the task. Use real user language, not internal jargon. Keep the important action loud and everything else calm. Test early with rough prototypes; you'll learn faster and waste less time polishing the wrong thing.
Here's a quick gut check for Five Whys: could a first-time user explain what to do without help? If not, the design is asking them to learn the system instead of helping them finish the task. That's a bad trade. Good Five Whys makes the next step obvious and the outcome feel earned.
Start by mapping the steps, then strip out anything that doesn't help the task. Use real user language, not internal jargon. Keep the important action loud and everything else calm. Test early with rough prototypes; you'll learn faster and waste less time polishing the wrong thing.
Five Whys is one of those UX words that sounds abstract until you see it in the wild. It's the relationship between what a user expects and what the interface actually does. If the interface keeps its promises, users trust it. If it surprises them in the wrong way, they stop exploring. Trust is the currency here.
Feeling overwhelmed?
Start with the mega-guide. It gives you the 80% of UX you’ll use 80% of the time.
Read it here: User Experience Basics →