Fishbone Diagram Template
Visualize the potential causes of a problem, to solve it collaboratively.
About the Fishbone Diagram template
What is a Fishbone Diagram?
A Fishbone Diagram is also known as a “cause and effect diagram” or an Ishikawa Diagram (named after its inventor, Japanese quality control expert Kaoru Ishikawa). Teams use a Fishbone Diagram to visualize all of the possible causes of a problem, zero in on the underlying cause, and anticipate the consequences with an effect analysis.
4 benefits of a Fishbone Diagram
1. Focus on a cause, rather than symptoms
Using a Fishbone Diagram helps teams truly get to the heart of why something is occurring, instead of simply describing the situation and mistaking secondary causes for the root cause.
2. See all potential causes at a glance
A Fishbone Diagram displays multiple causes, ordered logically, in a visual manner. All stakeholders can explore and understand how they fit together holistically.
3. Create a prompt for brainstorming
Many teams use a Fishbone Diagram as a jumping-off point for a structured brainstorming exercise, to generate a large number of potential ideas about what the root cause could be.
4. Focus everyone around the root cause
Instead of identifying the causes of a problem independently, a Fishbone Diagram enables the team to focus on working together, analyzing, and prioritizing different possibilities until they land on the root cause.
How to create a fishbone diagram in 3 steps
1. Define the problem statement
Create a statement that explains exactly what the problem is, and how and when it occurs. This should be added to the right side of your diagram, as the fish’s “head.” Make sure your team agrees on how the problem is being defined before you dive into exploring causes.
2. Identify categories of causes
What broad categories or areas do potential causes fall into? For example, if you’re trying to diagnose a problem with your software product, you might want to look at users, software, or marketing. For a physical product, you might include people, methods, materials, machines, or the environment. Try to keep the number of categories below ten.
3. List out the causes
Once you have your categories, it’s time to list out all of the individual causes for each bucket. These become the “bones” of the fish, which you can use as a basis for diagnosing the root cause of your problem. Some groups use the Fishbone Diagram in conjunction with 5 Whys to systematically dig deeper and uncover new potential causes.
How do you make a fishbone diagram?
Start by defining the problem statement and placing it on the right hand side of the diagram. Then, identify potential causes of the problem, and categorize these causes. Finally, list out each cause as the “bones” of the fish.
How is a fishbone diagram used?
A fishbone diagram is a tool for root cause analysis that is used to brainstorm the causes of a problem. It’s used for problem-solving and preemptively diagnosing issues before they are manifested in a way that causes damage.
Action Priority Matrix
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.
Features and capabilities — they make or break a product, which is why companies spend so much time and effort focusing on them. Sound like you? Try it with an Opportunity Canvas. This streamlined one-pager gives you and your team the power to improve your product by exploring the use cases, potential setbacks, strategies, challenges, and metrics. An Opportunity Canvas is ideal if you’ve already built a product, because you don’t need to consider the operational or revenue model.
Attracting new users, compelling them to try your product, and turning them into loyal customers—it all starts with understanding them. An empathy map is a tool that leads to that understanding, by giving you space to articulate everything you know about your customers, including their needs, expectations, and decision-making drivers. That way you’ll be able to challenge your assumptions and identify the gaps in your knowledge. Our template lets you easily create an empathy map divided into four key squares—what your customers Say, Think, Do, and Feel.
Use Case Diagram
A use case diagram is a visual tool that helps you analyze the relationships between personas and use cases. Use case diagrams typically depict the expected behavior of the system: what will happen and when. A use case diagram is helpful because it allows you to design a system from the perspective of the end user. It’s a valuable tool for communicating your desired system behavior in the language of the user, by specifying all externally visible system behavior.
Random word brainstorming is a simple, creative technique using random words to generate new ideas and creative solutions to your problems. Using random word prompts allows you to step beyond traditional boundaries and address challenges from a different direction. Random word brainstorming allows your team to unlock their creativity to solve business problems, create new inventions, improve existing ideas, or just think about problems in a new way.
Customer Journey Map (Timeline)
To attract and keep loyal customers, you have to truly start to understand them—their pain point, wants, and needs. A customer journey map (CJM) helps you gain that understanding by visualizing the path your customers follow, from signing up for a service, to using your site, to buying your product. And because no two customers are exactly alike, a CJM lets you plot out multiple pathways through your product. Soon you’ll be able to anticipate those pathways and satisfy your customers at every step.