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.
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 root-cause analysis tools so 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.
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.
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.
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.
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.
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.
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.
Kubernetes Architecture Diagram Template
Works best for:
Software Development, Diagrams
Use the Kubernetes Architecture Diagram template to manage your containerized applications better and bring your apps’ deployment, management, and scalability to the next level. This template helps you lower the downtime in production and allows you to have a more agile app production. Improve the deployment of your apps by visualizing every step of the process with the Kubernetes Architecture template. Try it out, and see if it works for you and your team.
Ansoff Matrix Template
Works best for:
Leadership, Operations, Strategic Planning
Keep growing. Keep scaling. Keep finding those new opportunities in new markets—and creative new ways to reach customers there. Sound like your approach? Then this template might be a great fit. An Ansoff Matrix (aka, a product or market expansion grid) is broken into four potential growth strategies: Market Penetration, Market Development, Product Development, and Diversification. When you go through each section with your team, you’ll get a clear view of your options going forward and the potential risks and rewards of each.
Job Map Template
Works best for:
Design, Desk Research, Mapping
Want to truly understand your consumers’ mindset? Take a look at things from their perspective — by identifying the “jobs” they need to accomplish and exploring what would make them “hire” or “fire” a product or service like yours. Ideal for UX researchers, job mapping is a staged process that gives you that POV by breaking the “jobs” down step by step, so you can ultimately offer something unique, useful, and different from your competitors. This template makes it easy to create a detailed, comprehensive job map.
Works best for:
While storyboard is typically associated with planning out scenes for a movie or TV show, it’s been widely adopted throughout the business world. A storyboard is a sequence of illustrations that are used to develop a story. You can use the Storyboarding template anytime you’d like to really put yourself in a customer or user’s position and understand how they think, feel, and act. This tactic can be especially useful when you know there’s a problem or inefficiency with an existing process. You can storyboard existing processes or workflows and plan how you would like them to look in the future.
Weekly Planner Template
Works best for:
Business Management, Project Planning
In our hectic world, it can be hard to plan out a schedule and stick to it. Whether you’re rigorous about scheduling or you struggle to keep your calendar updated, you’ll benefit from a weekly planner. A weekly planner is a schedule of your plans and activities over a week. It enables you to manage your time, track tasks, and organize your team by day. Unlike most paper planners, which are not personalizable, you can change up this weekly planner to create an agenda that fits your needs.
Kaizen Report Template
Works best for:
Agile Methodology, Operations, Documentation
What makes a great company great? They know that greatness needs to be fostered and maintained — meaning they never stop working to improve. If you’re one of those companies (or aspire to be), a kaizen report is an ideal tool. It creates a simple visual guide to continuous improvement activities on a team, departmental, and organizational level. Using a kaizen report approach, every employee in an organization audits their own processes and understands what they might have overlooked, making this a powerful tool for increasing accountability at all levels.