An iterative process for identifying the root cause of a problem by posing the question “Why?” at least five times to help separate symptoms from causes.
To identify the root cause(s) of an issue or problem.
How to do it
Select a particular issue or problem from your user research to investigate further. This could be the most commonly occurring problem or a problem that has been prioritized by the team. Ask why the problem occurred and write down an answer. Repeat this process another four times, building off of the previous response each time to drill down to a root cause. See example below:
Starting problem: “We didn’t meet our goal for public feedback during the open comment period.”
“Not enough people submitted comments.”
“Not enough people made it to the comment submission form.”
“The comment submission form was hard to find.”
“The link to the comment submission form was buried on the page.”
“We didn’t formulate and publish a call to action to submit comments.”
After getting to a root cause, frame or reframe your problem solving approach to address it (e.g., “how might we create a call to action for comment submission?”).
Note: You may ask “why” more or less than five times during this process. The purpose of this exercise is to help identify what is the root cause. Ask “why” as many times as needed to get to what you think the root cause is.
Considerations for use in government
No PRA implications. No information is collected from members of the public.