This repository has been archived by the owner on May 31, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 67
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #438 from 18F/peterrowland-patch-1
Create five-whys
- Loading branch information
Showing
1 changed file
with
60 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,60 @@ | ||
--- | ||
layout: card | ||
title: Five whys | ||
permalink: /discover/five-whys/ | ||
redirect_from: | ||
- /five-whys/ | ||
description: | ||
category: Discover | ||
what: 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. | ||
|
||
why: To identify the root cause(s) of an issue or problem. | ||
|
||
timeRequired: Less than 1 hour | ||
|
||
--- | ||
|
||
## 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.” | ||
1. *Why?* | ||
“Not enough people submitted comments.” | ||
2. *Why?* | ||
“Not enough people made it to the comment submission form.” | ||
3. *Why?* | ||
“The comment submission form was hard to find.” | ||
4. *Why?* | ||
“The link to the comment submission form was buried on the page.” | ||
5. *Why?* | ||
“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 can “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.* | ||
|
||
<!-- <section class="method--section method--section--18f-example" markdown="1" > | ||
## Example from 18F | ||
</section> --> | ||
|
||
<section class="method--section method--section--additional-resources" markdown="1"> | ||
|
||
## Additional resources | ||
|
||
- Five Whys Tree Diagrams — [Example 1](https://www.xmind.net/m/n5cq/) and [Example 2](https://www.xmind.net/m/SeKk/) | ||
- [Five Whys](https://en.wikipedia.org/wiki/Five_whys) on Wikipedia | ||
- [Root cause analysis](https://en.wikipedia.org/wiki/Five_whys) on Wikipedia | ||
|
||
</section> | ||
|
||
<section class="method--section method--section--government-considerations" markdown="1" > | ||
|
||
## Considerations for use in government | ||
|
||
No PRA implications. No information is collected from members of the public. | ||
|
||
</section> |