Choose website language
5 Whys5 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

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 

 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
Example Mapping ThumbnailExample Mapping Thumbnail
Preview

Example Mapping Template

To update your product in valuable ways—to recognize problem areas, add features, and make needed improvements—you have to walk in your users’ shoes. Example mapping (or user story mapping) can give you that perspective by helping cross-functional teams identify how users behave in different situations. These user stories are ideal for helping organizations form a development plan for Sprint planning or define the minimum amount of features needed to be valuable to customers.

Example Mapping Template
ux-research-thumb-web (1)ux-research-thumb-web (1)
Preview

UX Research Plan Template

A research plan communicates the fundamental information that stakeholders need to understand about a user experience research project: who, what, why, and when. The plan ensures everyone is aligned and knows what they must do to make the UX research project a success. Use the research plan to communicate background information about your project; objectives; research methods; the scope of the project, and profiles of the participants. By using a UX research plan, you can achieve stakeholder buy-in, stay on track, and set yourself up for success.

UX Research Plan Template
Jobs to be Done ThumbnailJobs to be Done Thumbnail
Preview

Jobs to be Done template

It’s all about a job done right — customers “hire” a product or service to do a “job,” and if it's not done right, the customer will find someone to do it better. Built on that simple premise, the Jobs To Be Done (JTBD) framework helps entrepreneurs, start-ups, and business managers define who their customer is and see unmet needs in the market. A standard job story lets you see things from your customers’ perspective by telling their story with a “When I…I Want To…So That I …” story structure.

Jobs to be Done template
Example Mapping ThumbnailExample Mapping Thumbnail
Preview

Example Mapping Template

To update your product in valuable ways—to recognize problem areas, add features, and make needed improvements—you have to walk in your users’ shoes. Example mapping (or user story mapping) can give you that perspective by helping cross-functional teams identify how users behave in different situations. These user stories are ideal for helping organizations form a development plan for Sprint planning or define the minimum amount of features needed to be valuable to customers.

Example Mapping Template
perceptual-map-thumb-webperceptual-map-thumb-web
Preview

Perceptual Map Template

To shape your messaging, tailor your marketing, improve your product, and build your brand, you have to know your customers’ perceptions — what they think of you and your competitors. You can gain those insights by exploring a perceptual map. This simple, powerful tool creates a visual representation of how customers rank your price, performance, safety, and reliability. Put this template to work and you’ll be able to size up your competition, see gaps in the market, and understand changes in customer behavior and purchasing decisions.

Perceptual Map Template
dmaic-analysis-thumb-webdmaic-analysis-thumb-web
Preview

DMAIC Analysis Template

Processes might not seem like the funnest thing to dive into and examine, but wow can it pay off—a more efficient process can lead to serious cost savings and a better product. That’s what DMAIC analysis does. Developed as part of the Six Sigma initiative, DMAIC is a data-driven quality strategy for streamlining processes and resolving issues. The technique is broken into five fundamental steps that are followed in order: Define, Measure, Analyze, Improve, and Control.

DMAIC Analysis Template