5 Whys

5 Whys Template

Analyze and understand the root of a problem or issue with the 5 Whys Template. Create the conditions for creative solutions.

About the 5 Whys Template

The 5 Whys Template is a simple brainstorming tool that helps to identify the root causes of a problem. Starting with an initial problem, you ask “Why” until you narrow in on one key issue that you can focus your efforts and attention on.

What are the 5 Whys?

The 5 Whys is a technique for getting to the root of a problem. Fundamentally, the approach is simple: you ask why a given problem happened, and then you ask four more times. But it is also much more than that. Toyota pioneered the 5 Whys technique as a critical component of its problem-solving training. By repeating the question five times, it becomes easier to get at the heart of the problem and discover a solution.

Keep reading to know more about the 5 Whys Template.

Why use the 5 Whys approach?

The 5 Whys framework allows you to have a focused discussion so you don't get distracted by other topics. You simply start with a problem statement, examine why that problem exists, then continue moving through each problem until you identify a core issue that you can act upon. Keep in mind that it might not always take five rounds — just go through the activity until you arrive at a satisfactory conclusion.

The 5 Whys Template and the Fishbone Diagram

There are many problem-solving techniques, and you should be able to explore all your options when running a session with your team.

While the 5 Whys Template allows you to hone in on one aspect of your problem statement, the Fishbone Diagram offers you another alternative as it tries to look for the potential causes of a given problem.

Both problem-solving techniques are widely recognized across many industries. When choosing which methodology to use, ask yourself: Do you want to get to the root cause of a single issue? Or do you want to explore all possible alternatives that led to your current situation?

How do you use the Miro 5 Whys Template?

The 5 Whys Template in Miro is built to show you the necessary steps to apply this methodology.

First, write the problem statement you want to analyze in the first rectangle of the template, on the top left. This will be your focus throughout the whole process.

Start asking “why”. Subsequently, dig deeper by asking “because” questions until you get to the root of the issue. Record these question/answer statements in each block to keep track and refer back to later as you test your hypothesis.

Follow this path until you reach a satisfying conclusion.

To make your session more collaborative, you can involve team members sharing the 5 Whys Template you are using and @mentioning them in comments.

Use sticky notes to call out issues that are particularly important or require follow-up. You may also want to color-code the sticky notes depending on the urgency or severity of the problem or whose role it will be to take the next step.

5 Whys Template Example

Let's say you're trying to ship an app that your team has been working on. You were prepared to ship on time, but you ended up delivering the app 2 days overdue.

Here's how you might use the 5 Whys to uncover the reason that happened and how you can avoid delays in the future.

Step 1:

Start with the broadest possible question, then try to answer it.

Example: Why was the app late? It was late because there was a production delay.

Step 2:

Based on this answer, you can narrow the question slightly.

Example: Why was there a production delay? There was a production delay because the engineering team had to deploy a last-minute patch, which the product team did not know about until launch day.

Step 3:

Narrow the question even further, and then answer it.

Example: Why didn't the product team know about the patch? The product team didn't know about the patch because engineering didn't communicate it to them.

Step 4:

Keep narrowing and answering the question.

Example: Why didn't the engineering team communicate to the product team? The engineering team didn't communicate with the product team because they did not know how to communicate that information.

Step 5:

Ask the question one last time to zero in on your solution.

Example: Why didn't the engineering team know how to communicate with the product team? The engineering team didn't know how to communicate to the product team because the product team has no clear point of contact or processes for communication.

FAQ about the 5 Whys Template

What are the 5 Whys questions?

The 5 Whys technique helps you to get to the root of a given problem by asking why this problem happened. The ‘why questions’ may look like this: ‘why does this keep happening’ or ‘why are we having this problem.’ Try to ask the why question at least five times before reaching a conclusion, and of course, if you want to go further, just repeat the 5 Whys exercise.

How do you document 5 Whys?

You can document your 5 Whys session using our ready-made template, or you can open a new board in Miro and draw your own 5 Whys Template from scratch. After you finish your session, share the link with your team and ask for feedback, so you can either iterate or add new ideas.

5 Whys Template

Get started with this template right now.

Related Templates
UML Communication Diagram
Preview

UML Communication Diagram Template

Works best for:

Software Development, Mapping, Diagrams

Most modern programs consist of many moving parts working to a precise set of instructions. With a communication diagram, you can visualize exactly how those parts work together, giving you a clearer understanding of your program as a whole. What’s more, the diagram leaves spaces for expanding the network of relationships as your product grows and evolves. A communication diagram is a vital tool in any software designer’s arsenal.

UML Communication Diagram Template
SCAMPER Thumbnail
Preview

SCAMPER Model

Works best for:

Ideation, Operations, Brainstorming

Is your team in a rut? Have you had a lingering problem that can’t seem to be solved? First introduced in 1972, SCAMPER. is a brainstorming method developed by Bob Eberle, an author of creativity books for young people. This clever, easy-to-use method helps teams overcome creative roadblocks. SCAMPER walks you through seven questions that are meant to encourage your team to approach a problem through seven unique filters. By asking your team to think through a problem using this framework, you’ll unlock fresh, innovative ways to understand the problem you’re trying to solve.

SCAMPER Model
feature-canvas-thumb-web
Preview

Feature Canvas Template

Works best for:

Design, Desk Research, Product Management

When you’re working on a new feature that solves a problem for your users, it’s easy to dive right in and start looking for solutions. However, it’s important to understand the initial user problem first. Use the Feature Canvas template to do a deep-dive into the user’s problems, the context in which they will use your feature, and the value proposition you will deliver to your users. The template enables you to spend more time exploring the problem to anticipate any potential blind spots before jumping into solutions mode.

Feature Canvas Template
Service Blueprint Thumbnail
Preview

Service Blueprint Template

Works best for:

Desk Research, Operations, Market Research

First introduced by G. Lynn Shostack in 1984, service blueprints allow you to visualize the steps that go into a service process from the customer’s perspective. Service blueprints are useful tools for understanding and designing a service experience – and finding ways to improve it. Service blueprint diagrams make it simpler for teams to design new processes or improve existing ones. To create a service blueprint, map out each process and actor that contributes to the customer experience, from in-house contributors to third-party vendors.

Service Blueprint Template
kano-model-thumb-web
Preview

Kano Model Template

Works best for:

Desk Research, Product Management, Prioritization

When it comes down to it, a product’s success is determined by the features it offers and the satisfaction it gives to customers. So which features matter most? The Kano model will help you decide. It’s a simple, powerful method for helping you prioritize all your features — by comparing how much satisfaction a feature will deliver to what it will cost to implement. This template lets you easily create a standard Kano model, with two axes (satisfaction and functionality) creating a quadrant with four values: attractive, performance, indifferent, and must-be.

Kano Model Template
Action-Priority-Matrix-thumb-web
Preview

Action Priority Matrix Template

Works best for:

Mapping

You and your teammates probably have more ideas than resources, which can make it difficult to prioritize tasks. Use an Action Priority Matrix to help choose the order in which you will work on your tasks, allowing you to save time and money and avoid getting bogged down in unnecessary work. An Action Priority Matrix is a simple diagram that allows you to score tasks based on their impact and the effort needed to complete them. You use your scores to plot each task in one of four quadrants: quick wins, major projects, fill-ins, and thankless tasks.

Action Priority Matrix Template