5 Whys Template
Clearly analyze and understand the root of a problem or issue.
About the 5 Whys template
What are the 5 Whys?
The 5 Whys is a technique for getting at 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.
How do you use the Miro 5 Whys template?
You can involve team members by asking them questions in chat or @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 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 were two days late. 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. 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. 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. 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. Why didn’t the engineering team communicate to the product team? The engineering team didn’t communicate to 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. Why didn’t the engineering team know how to communicate to 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.
Want to keep your company secure and performing soundly? You have to first know how you’ll be affected by outside elements and factors — especially those that are political, economic, social, technological, legal and environmental in nature. A PESTLE Analysis helps you identify them and prepare for them. With this easy-to-use template, you can conduct a PESTLE Analysis, then use the results to shape your strategic planning, budget allocation, marketing, product updates, and organizational change initiatives.
Pros and Cons List
A pros and cons list is a simple but powerful decision-making tool used to help understand both sides of an argument. Pros are listed as arguments in favor of making a particular decision or action. Cons are listed arguments against it. By creating a list that details both sides of the argument, it becomes easier to visualize the potential impact of your decision. To make your pros and cons list even more objective, it can help to weight each pro and con against the others. You can then present your decision with confidence, making a strong argument for why it’s the right one.
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.
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.
AWS Architecture Diagram
The AWS Architecture Diagram is a visual representation of the AWS framework, and it also translates the best practices when using Amazon Web Services architecture. You can now have an overview of your AWS architecture with Miro’s AWS Architecture Diagram Template, track your cloud solutions easily, and optimize processes like never before.
A user persona is a tool for representing and summarizing a target audience for your product or service that you have researched or observed. Whether you’re in content marketing, product marketing, design, or sales, you operate with a target in mind. Maybe it’s your customer or prospect. Maybe it’s someone who will benefit from your product or service. Usually, it’s a whole collection of personalities and needs that intersect in interesting ways. By distilling your knowledge about a user, you create a model for the person you hope to target: this is a persona.