Strategy
Five Why’s
A method for getting past the first plausible explanation to the one worth fixing.
Using repeated ‘why’ questioning to identify root causes behind recurring UX and product issues.
What it is
The Five Why’s is a UX and problem-solving method used to identify the underlying cause of issues by repeatedly asking “why?” - typically five times - until the root problem is revealed.
It involves analysing user complaints, errors, or glossaryUsabilityUsability is how easy and efficient it is for users to complete tasks within a product. It focuses on clarity, simplicity, and reducing effort so users can achieve their goals without confusion or friction.Open glossary term problems to trace back from surface-level symptoms to the fundamental cause.
The focus is on understanding why a problem occurs rather than just addressing its manifestations.
Key takeaway
The goal is to eliminate recurring issues, improve processes, and enhance the overall user experience.
When to use it
Use this method when you want to get to the root of a problem.
It is most useful when:
It is less useful when:
Five Why’s is often used alongside support ticket analysis, call centre analysis, and error tracking.
How to run it
Set up properly
Define the symptom precisely, gather the evidence you have, and involve people who understand the glossaryContextContext is the set of surrounding conditions that shape how someone behaves and decides, including their goal, their environment, their time pressure, and what happened immediately before. The same action can mean different things in different contexts.Open glossary term. A vague problem statement produces a chain of vague answers.
Make it clear this is about glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term and not people. The moment the chain starts pointing at an individual, it stops finding causes and starts finding blame.
Run the method
Five Whys traces a symptom back to its root by repeatedly asking why. It is deliberately simple, and its weakness is that it follows a single chain when most failures have several.
- State the problem clearly, in terms of what happened rather than who did it.
- Ask why it happened, and record an answer supported by evidence rather than plausibility.
- Ask why again of that answer, and keep going. The first two answers are usually symptoms wearing a cause's clothes.
- Continue until you reach something that would actually prevent recurrence if changed, often around five glossaryIterationIteration is the process of repeatedly improving a product through cycles of testing, feedback, and refinement.Open glossary term, sometimes fewer or more.
- Validate the conclusion against evidence. A chain that sounds coherent and is unsupported is a story, not a diagnosis.
Be willing to follow more than one branch. Real failures rarely have a single cause, and forcing a linear chain produces a tidy answer that fixes one contributor.
Capture and make sense of it
The value comes from fixing causes rather than symptoms. After the glossarySessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term, document:
- The chain of reasoning with evidence at each step
- The glossaryRoot CauseA root cause is the underlying reason a problem exists, as distinct from the symptom it presents as. Removing it stops the problem recurring; addressing only the symptom means meeting the same issue somewhere else.Open glossary term or causes identified
- The change that would prevent recurrence, with an owner
- Points where the chain was uncertain and could branch
Use this to stop the same problem returning. A glossaryRoot CauseA root cause is the underlying reason a problem exists, as distinct from the symptom it presents as. Removing it stops the problem recurring; addressing only the symptom means meeting the same issue somewhere else.Open glossary term with nobody accountable for it will be rediscovered in six months.
Key takeaway
Use this to ensure solutions prevent issues, not just treat symptoms.
What to look for
Focus on:
Where it goes wrong
Most issues come from:
If glossaryRoot CauseA root cause is the underlying reason a problem exists, as distinct from the symptom it presents as. Removing it stops the problem recurring; addressing only the symptom means meeting the same issue somewhere else.Open glossary term aren’t addressed, problems persist.
What you get from it
Done properly, this method gives you:
Key takeaway
It helps prevent issues instead of repeatedly treating symptoms.
Get in touch
If this sounds like something you need, we can help you apply the Five Why’s method to identify root causes, prioritise fixes, and improve your UX and product experience.
No guesswork. No assumptions. Just problems solved at the source.
FAQ
Common questions
A few practical answers to the questions that usually come up around this method.
What is the Five Why’s method in UX?
It is a problem-solving method that uncovers root causes by repeatedly asking “why?” about an issue.
When should you use Five Why’s?
When recurring problems, errors, or user complaints need a root cause analysis.
What can you analyse?
Usability issues, support tickets, errors, or process inefficiencies.
Why keep asking why?
It prevents recurring issues by addressing the fundamental cause rather than symptoms.
Does Five Why’s improve UX?
Yes. It helps create solutions that truly solve user problems and improve the overall experience.
Quick take
If the same problem keeps returning, it was never the cause you fixed last time.
Related Services
Related Guides
