Playbook
5 Why's
Dive deep into the root cause of the problem you are trying to solve rather than focusing on the apparent, surface-level problem that presents itself.
Requirements
- Estimated time needed: 30 minutes
- Team: Facilitator, Note-taker, Stakeholders
Why should we do this exercise?
This exercises helps us to identify the root cause of the problem we are trying to solve, rather than the apparent surface-level problem. Solving the root cause should be the goal of any Sprint or new product as it creates a better product with fewer wasted resources so it is absolutely crucial to know what your root problem is.
Check out the example below to see exactly what we mean.
Instructions
- Write down a specific problem.
- Ask the team to individually write down why that is happening.
- Form a new problem from the answers the team gave.
- Repeat steps 2 and 3 four more times or as much as necessary.
- Analyse the results and form relationships between answers.
Tips
- This can be a difficult process to follow if you have spent a lot of time trying to solve a surface level problem. Try to keep an open mind and be willing to look at the problem on a deeper level.
Example
The vehicle will not start. (the problem)
- Why? — The battery is dead (first why)
- Why? — The alternator is not functioning (second why)
- Why? — The alternator belt has broken (third why)
- Why? — The alternator belt was well beyond its useful service life and not replaced (fourth why)
- Why? — The vehicle was not maintained according to the recommended service schedule (fifth why, a root cause)