diagram of problem solving

Problem-Solving Flowchart: A Visual Method to Find Perfect Solutions

Lucid Content

Reading time: about 7 min

“People ask me questions Lost in confusion Well, I tell them there's no problem Only solutions” —John Lennon, “Watching the Wheels”

Despite John Lennon’s lyrics, nobody is free from problems, and that’s especially true in business. Chances are that you encounter some kind of problem at work nearly every day, and maybe you’ve had to “put out a fire” before lunchtime once or twice in your career.

But perhaps what Lennon’s saying is that, no matter what comes our way, we can find solutions. How do you approach problems? Do you have a process in place to ensure that you and your co-workers come to the right solution?

In this article, we will give you some tips on how to find solutions visually through a problem-solving flowchart and other methods.

What is visual problem-solving?

If you are a literal thinker, you may think that visual problem-solving is something that your ophthalmologist does when your vision is blurry. For the rest of us, visual problem-solving involves executing the following steps in a visual way:

• Define the problem.
• Brainstorm solutions.
• Pick a solution.
• Implement solutions.
• Review the results.

How to make your problem-solving process more visual

Words pack a lot of power and are very important to how we communicate on a daily basis. Using words alone, you can brainstorm, organize data, identify problems, and come up with possible solutions. The way you write your ideas may make sense to you, but it may not be as easy for other team members to follow.

When you use flowcharts, diagrams, mind maps, and other visuals, the information is easier to digest. Your eyes dart around the page quickly gathering information, more fully engaging your brain to find patterns and make sense of the data.

Identify the problem with mind maps

So you know there is a problem that needs to be solved. Do you know what that problem is? Is there only one problem? Is the problem sum total of a bunch of smaller problems?

You need to ask these kinds of questions to be sure that you are working on the root of the issue. You don’t want to spend too much time and energy solving the wrong problem.

To help you identify the problem, use a mind map. Mind maps can help you visually brainstorm and collect ideas without a strict organization or structure. A mind map more closely aligns with the way a lot of our brains work—participants can bounce from one thought to the next defining the relationships as they go.

Mind mapping to solve a problem includes, but is not limited to, these relatively easy steps:

• In the center of the page, add your main idea or concept (in this case, the problem).
• Branch out from the center with possible root causes of the issue. Connect each cause to the central idea.
• Branch out from each of the subtopics with examples or additional details about the possible cause. As you add more information, make sure you are keeping the most important ideas closer to the main idea in the center.
• Use Collaborative AI to generate or expand on your ideas, so your mind map is as complete as possible.

Alternatively, you could use mind maps to brainstorm solutions once you discover the root cause. Try our free mind map template  or add the mind map shape library to quickly start your own mind map.

Create a problem-solving flowchart

A mind map is generally a good tool for non-linear thinkers. However, if you are a linear thinker—a person who thinks in terms of step-by-step progression making a flowchart may work better for your problem-solving strategy. A flowchart is a graphical representation of a workflow or process with various shapes connected by arrows representing each step.

Whether you are trying to solve a simple or complex problem, the steps you take to solve that problem with a flowchart are easy and straightforward. Using boxes and other shapes to represent steps, you connect the shapes with arrows that will take you down different paths until you find the logical solution at the end.

Flowcharts or decision trees are best used to solve problems or answer questions that are likely to come up multiple times. For example, Yoder Lumber , a family-owned hardwood manufacturer, built decision trees in Lucidchart to demonstrate what employees should do in the case of an injury.

To start your problem-solving flowchart, follow these steps:

• Draw a starting shape to state your problem.
• Draw a decision shape where you can ask questions that will give you yes-or-no answers.
• Based on the yes-or-no answers, draw arrows connecting the possible paths you can take to work through the steps and individual processes.
• Continue following paths and asking questions until you reach a logical solution to the stated problem.
• Try the solution. If it works, you’re done. If it doesn’t work, review the flowchart to analyze what may have gone wrong and rework the flowchart until you find the solution that works.

If your problem involves a process or workflow , you can also use flowcharts to visualize the current state of your process to find the bottleneck or problem that’s costing your company time and money.

Lucidchart has a large library of flowchart templates to help you analyze, design, and document problem-solving processes or any other type of procedure you can think of.

Draw a cause-and-effect diagram

A cause-and-effect diagram is used to analyze the relationship between an event or problem and the reason it happened. There is not always just one underlying cause of a problem, so this visual method can help you think through different potential causes and pinpoint the actual cause of a stated problem.

Cause-and-effect diagrams, created by Kaoru Ishikawa, are also known as Ishikawa diagrams, fishbone diagrams , or herringbone diagrams (because they resemble a fishbone when completed). By organizing causes and effects into smaller categories, these diagrams can be used to examine why things went wrong or might go wrong.

To perform a cause-and-effect analysis, follow these steps.

1. Start with a problem statement.

The problem statement is usually placed in a box or another shape at the far right of your page. Draw a horizontal line, called a “spine” or “backbone,” along the center of the page pointing to your problem statement.

2. Add the categories that represent possible causes.

For example, the category “Materials” may contain causes such as “poor quality,” “too expensive,” and “low inventory.” Draw angled lines (or “bones”) that branch out from the spine to these categories.

3. Add causes to each category.

Draw as many branches as you need to brainstorm the causes that belong in each category.

Like all visuals and diagrams, a cause-and-effect diagram can be as simple or as complex as you need it to be to help you analyze operations and other factors to identify causes related to undesired effects.

Collaborate with Lucidchart

You may have superior problem-solving skills, but that does not mean that you have to solve problems alone. The visual strategies above can help you engage the rest of your team. The more involved the team is in the creation of your visual problem-solving narrative, the more willing they will be to take ownership of the process and the more invested they will be in its outcome.

In Lucidchart, you can simply share the documents with the team members you want to be involved in the problem-solving process. It doesn’t matter where these people are located because Lucidchart documents can be accessed at any time from anywhere in the world.

Whatever method you decide to use to solve problems, work with Lucidchart to create the documents you need. Sign up for a free account today and start diagramming in minutes.

About Lucidchart

Lucidchart, a cloud-based intelligent diagramming application, is a core component of Lucid Software's Visual Collaboration Suite. This intuitive, cloud-based solution empowers teams to collaborate in real-time to build flowcharts, mockups, UML diagrams, customer journey maps, and more. Lucidchart propels teams forward to build the future faster. Lucid is proud to serve top businesses around the world, including customers such as Google, GE, and NBC Universal, and 99% of the Fortune 500. Lucid partners with industry leaders, including Google, Atlassian, and Microsoft. Since its founding, Lucid has received numerous awards for its products, business, and workplace culture. For more information, visit lucidchart.com.

Related articles

Sometimes you're faced with challenges that traditional problem solving can't fix. Creative problem solving encourages you to find new, creative ways of thinking that can help you overcome the issue at hand more quickly.

Dialogue mapping is a facilitation technique used to visualize critical thinking as a group. Learn how you and your team can start dialogue mapping today to solve problems and bridge gaps in knowledge and understanding (plus get a free template!).

Bring your bright ideas to life.

or continue with

What is Problem Solving? (Steps, Techniques, Examples)

By Status.net Editorial Team on May 7, 2023 — 5 minutes to read

What Is Problem Solving?

Definition and importance.

Problem solving is the process of finding solutions to obstacles or challenges you encounter in your life or work. It is a crucial skill that allows you to tackle complex situations, adapt to changes, and overcome difficulties with ease. Mastering this ability will contribute to both your personal and professional growth, leading to more successful outcomes and better decision-making.

Problem-Solving Steps

The problem-solving process typically includes the following steps:

• Identify the issue : Recognize the problem that needs to be solved.
• Analyze the situation : Examine the issue in depth, gather all relevant information, and consider any limitations or constraints that may be present.
• Generate potential solutions : Brainstorm a list of possible solutions to the issue, without immediately judging or evaluating them.
• Evaluate options : Weigh the pros and cons of each potential solution, considering factors such as feasibility, effectiveness, and potential risks.
• Select the best solution : Choose the option that best addresses the problem and aligns with your objectives.
• Implement the solution : Put the selected solution into action and monitor the results to ensure it resolves the issue.
• Review and learn : Reflect on the problem-solving process, identify any improvements or adjustments that can be made, and apply these learnings to future situations.

Defining the Problem

To start tackling a problem, first, identify and understand it. Analyzing the issue thoroughly helps to clarify its scope and nature. Ask questions to gather information and consider the problem from various angles. Some strategies to define the problem include:

• Brainstorming with others
• Asking the 5 Ws and 1 H (Who, What, When, Where, Why, and How)
• Analyzing cause and effect
• Creating a problem statement

Generating Solutions

Once the problem is clearly understood, brainstorm possible solutions. Think creatively and keep an open mind, as well as considering lessons from past experiences. Consider:

• Creating a list of potential ideas to solve the problem
• Grouping and categorizing similar solutions
• Prioritizing potential solutions based on feasibility, cost, and resources required
• Involving others to share diverse opinions and inputs

Evaluating and Selecting Solutions

Evaluate each potential solution, weighing its pros and cons. To facilitate decision-making, use techniques such as:

• SWOT analysis (Strengths, Weaknesses, Opportunities, Threats)
• Decision-making matrices
• Pros and cons lists
• Risk assessments

After evaluating, choose the most suitable solution based on effectiveness, cost, and time constraints.

Implementing and Monitoring the Solution

Implement the chosen solution and monitor its progress. Key actions include:

• Communicating the solution to relevant parties
• Setting timelines and milestones
• Assigning tasks and responsibilities
• Monitoring the solution and making adjustments as necessary
• Evaluating the effectiveness of the solution after implementation

Utilize feedback from stakeholders and consider potential improvements. Remember that problem-solving is an ongoing process that can always be refined and enhanced.

Problem-Solving Techniques

During each step, you may find it helpful to utilize various problem-solving techniques, such as:

• Brainstorming : A free-flowing, open-minded session where ideas are generated and listed without judgment, to encourage creativity and innovative thinking.
• Root cause analysis : A method that explores the underlying causes of a problem to find the most effective solution rather than addressing superficial symptoms.
• SWOT analysis : A tool used to evaluate the strengths, weaknesses, opportunities, and threats related to a problem or decision, providing a comprehensive view of the situation.
• Mind mapping : A visual technique that uses diagrams to organize and connect ideas, helping to identify patterns, relationships, and possible solutions.

Brainstorming

When facing a problem, start by conducting a brainstorming session. Gather your team and encourage an open discussion where everyone contributes ideas, no matter how outlandish they may seem. This helps you:

• Generate a diverse range of solutions
• Encourage all team members to participate
• Foster creative thinking

When brainstorming, remember to:

• Reserve judgment until the session is over
• Encourage wild ideas
• Combine and improve upon ideas

Root Cause Analysis

For effective problem-solving, identifying the root cause of the issue at hand is crucial. Try these methods:

• 5 Whys : Ask “why” five times to get to the underlying cause.
• Fishbone Diagram : Create a diagram representing the problem and break it down into categories of potential causes.
• Pareto Analysis : Determine the few most significant causes underlying the majority of problems.

SWOT Analysis

SWOT analysis helps you examine the Strengths, Weaknesses, Opportunities, and Threats related to your problem. To perform a SWOT analysis:

• List your problem’s strengths, such as relevant resources or strong partnerships.
• Identify its weaknesses, such as knowledge gaps or limited resources.
• Explore opportunities, like trends or new technologies, that could help solve the problem.
• Recognize potential threats, like competition or regulatory barriers.

SWOT analysis aids in understanding the internal and external factors affecting the problem, which can help guide your solution.

Mind Mapping

A mind map is a visual representation of your problem and potential solutions. It enables you to organize information in a structured and intuitive manner. To create a mind map:

• Write the problem in the center of a blank page.
• Draw branches from the central problem to related sub-problems or contributing factors.
• Add more branches to represent potential solutions or further ideas.

Mind mapping allows you to visually see connections between ideas and promotes creativity in problem-solving.

Examples of Problem Solving in Various Contexts

In the business world, you might encounter problems related to finances, operations, or communication. Applying problem-solving skills in these situations could look like:

• Identifying areas of improvement in your company’s financial performance and implementing cost-saving measures
• Resolving internal conflicts among team members by listening and understanding different perspectives, then proposing and negotiating solutions
• Streamlining a process for better productivity by removing redundancies, automating tasks, or re-allocating resources

In educational contexts, problem-solving can be seen in various aspects, such as:

• Addressing a gap in students’ understanding by employing diverse teaching methods to cater to different learning styles
• Developing a strategy for successful time management to balance academic responsibilities and extracurricular activities
• Seeking resources and support to provide equal opportunities for learners with special needs or disabilities

Everyday life is full of challenges that require problem-solving skills. Some examples include:

• Overcoming a personal obstacle, such as improving your fitness level, by establishing achievable goals, measuring progress, and adjusting your approach accordingly
• Navigating a new environment or city by researching your surroundings, asking for directions, or using technology like GPS to guide you
• Dealing with a sudden change, like a change in your work schedule, by assessing the situation, identifying potential impacts, and adapting your plans to accommodate the change.
• How to Resolve Employee Conflict at Work [Steps, Tips, Examples]
• How to Write Inspiring Core Values? 5 Steps with Examples
• 30 Employee Feedback Examples (Positive & Negative)

• Bipolar Disorder
• Therapy Center
• When To See a Therapist
• Types of Therapy
• Best Online Therapy
• Best Couples Therapy
• Best Family Therapy
• Managing Stress
• Sleep and Dreaming
• Understanding Emotions
• Self-Improvement
• Healthy Relationships
• Student Resources
• Personality Types
• Guided Meditations
• Verywell Mind Insights
• 2024 Verywell Mind 25
• Mental Health in the Classroom
• Editorial Process
• Meet Our Review Board
• Crisis Support

Overview of the Problem-Solving Mental Process

Kendra Cherry, MS, is a psychosocial rehabilitation specialist, psychology educator, and author of the "Everything Psychology Book."

Rachel Goldman, PhD FTOS, is a licensed psychologist, clinical assistant professor, speaker, wellness expert specializing in eating behaviors, stress management, and health behavior change.

• Identify the Problem
• Define the Problem
• Form a Strategy
• Organize Information
• Allocate Resources
• Monitor Progress
• Evaluate the Results

Frequently Asked Questions

Problem-solving is a mental process that involves discovering, analyzing, and solving problems. The ultimate goal of problem-solving is to overcome obstacles and find a solution that best resolves the issue.

The best strategy for solving a problem depends largely on the unique situation. In some cases, people are better off learning everything they can about the issue and then using factual knowledge to come up with a solution. In other instances, creativity and insight are the best options.

It is not necessary to follow problem-solving steps sequentially, It is common to skip steps or even go back through steps multiple times until the desired solution is reached.

In order to correctly solve a problem, it is often important to follow a series of steps. Researchers sometimes refer to this as the problem-solving cycle. While this cycle is portrayed sequentially, people rarely follow a rigid series of steps to find a solution.

The following steps include developing strategies and organizing knowledge.

1. Identifying the Problem

While it may seem like an obvious step, identifying the problem is not always as simple as it sounds. In some cases, people might mistakenly identify the wrong source of a problem, which will make attempts to solve it inefficient or even useless.

Some strategies that you might use to figure out the source of a problem include :

• Asking questions about the problem
• Breaking the problem down into smaller pieces
• Looking at the problem from different perspectives
• Conducting research to figure out what relationships exist between different variables

2. Defining the Problem

After the problem has been identified, it is important to fully define the problem so that it can be solved. You can define a problem by operationally defining each aspect of the problem and setting goals for what aspects of the problem you will address

At this point, you should focus on figuring out which aspects of the problems are facts and which are opinions. State the problem clearly and identify the scope of the solution.

3. Forming a Strategy

After the problem has been identified, it is time to start brainstorming potential solutions. This step usually involves generating as many ideas as possible without judging their quality. Once several possibilities have been generated, they can be evaluated and narrowed down.

The next step is to develop a strategy to solve the problem. The approach used will vary depending upon the situation and the individual's unique preferences. Common problem-solving strategies include heuristics and algorithms.

• Heuristics are mental shortcuts that are often based on solutions that have worked in the past. They can work well if the problem is similar to something you have encountered before and are often the best choice if you need a fast solution.
• Algorithms are step-by-step strategies that are guaranteed to produce a correct result. While this approach is great for accuracy, it can also consume time and resources.

Heuristics are often best used when time is of the essence, while algorithms are a better choice when a decision needs to be as accurate as possible.

4. Organizing Information

Before coming up with a solution, you need to first organize the available information. What do you know about the problem? What do you not know? The more information that is available the better prepared you will be to come up with an accurate solution.

When approaching a problem, it is important to make sure that you have all the data you need. Making a decision without adequate information can lead to biased or inaccurate results.

5. Allocating Resources

Of course, we don't always have unlimited money, time, and other resources to solve a problem. Before you begin to solve a problem, you need to determine how high priority it is.

If it is an important problem, it is probably worth allocating more resources to solving it. If, however, it is a fairly unimportant problem, then you do not want to spend too much of your available resources on coming up with a solution.

At this stage, it is important to consider all of the factors that might affect the problem at hand. This includes looking at the available resources, deadlines that need to be met, and any possible risks involved in each solution. After careful evaluation, a decision can be made about which solution to pursue.

6. Monitoring Progress

After selecting a problem-solving strategy, it is time to put the plan into action and see if it works. This step might involve trying out different solutions to see which one is the most effective.

It is also important to monitor the situation after implementing a solution to ensure that the problem has been solved and that no new problems have arisen as a result of the proposed solution.

Effective problem-solvers tend to monitor their progress as they work towards a solution. If they are not making good progress toward reaching their goal, they will reevaluate their approach or look for new strategies .

7. Evaluating the Results

After a solution has been reached, it is important to evaluate the results to determine if it is the best possible solution to the problem. This evaluation might be immediate, such as checking the results of a math problem to ensure the answer is correct, or it can be delayed, such as evaluating the success of a therapy program after several months of treatment.

Once a problem has been solved, it is important to take some time to reflect on the process that was used and evaluate the results. This will help you to improve your problem-solving skills and become more efficient at solving future problems.

A Word From Verywell​

It is important to remember that there are many different problem-solving processes with different steps, and this is just one example. Problem-solving in real-world situations requires a great deal of resourcefulness, flexibility, resilience, and continuous interaction with the environment.

Get Advice From The Verywell Mind Podcast

Hosted by therapist Amy Morin, LCSW, this episode of The Verywell Mind Podcast shares how you can stop dwelling in a negative mindset.

Follow Now : Apple Podcasts / Spotify / Google Podcasts

You can become a better problem solving by:

• Practicing brainstorming and coming up with multiple potential solutions to problems
• Being open-minded and considering all possible options before making a decision
• Breaking down problems into smaller, more manageable pieces
• Asking for help when needed
• Researching different problem-solving techniques and trying out new ones
• Learning from mistakes and using them as opportunities to grow

It's important to communicate openly and honestly with your partner about what's going on. Try to see things from their perspective as well as your own. Work together to find a resolution that works for both of you. Be willing to compromise and accept that there may not be a perfect solution.

Take breaks if things are getting too heated, and come back to the problem when you feel calm and collected. Don't try to fix every problem on your own—consider asking a therapist or counselor for help and insight.

If you've tried everything and there doesn't seem to be a way to fix the problem, you may have to learn to accept it. This can be difficult, but try to focus on the positive aspects of your life and remember that every situation is temporary. Don't dwell on what's going wrong—instead, think about what's going right. Find support by talking to friends or family. Seek professional help if you're having trouble coping.

Davidson JE, Sternberg RJ, editors.  The Psychology of Problem Solving .  Cambridge University Press; 2003. doi:10.1017/CBO9780511615771

Sarathy V. Real world problem-solving .  Front Hum Neurosci . 2018;12:261. Published 2018 Jun 26. doi:10.3389/fnhum.2018.00261

By Kendra Cherry, MSEd Kendra Cherry, MS, is a psychosocial rehabilitation specialist, psychology educator, and author of the "Everything Psychology Book."

35 problem-solving techniques and methods for solving complex problems

Design your next session with SessionLab

Join the 150,000+ facilitators 
using SessionLab.

Recommended Articles

A step-by-step guide to planning a workshop, how to create an unforgettable training session in 8 simple steps, 47 useful online tools for workshop planning and meeting facilitation.

All teams and organizations encounter challenges as they grow. There are problems that might occur for teams when it comes to miscommunication or resolving business-critical issues . You may face challenges around growth , design , user engagement, and even team culture and happiness. In short, problem-solving techniques should be part of every team’s skillset.

Problem-solving methods are primarily designed to help a group or team through a process of first identifying problems and challenges , ideating possible solutions , and then evaluating the most suitable .

Finding effective solutions to complex problems isn’t easy, but by using the right process and techniques, you can help your team be more efficient in the process.

So how do you develop strategies that are engaging, and empower your team to solve problems effectively?

In this blog post, we share a series of problem-solving tools you can use in your next workshop or team meeting. You’ll also find some tips for facilitating the process and how to enable others to solve complex problems.

Let’s get started! 

How do you identify problems?

How do you identify the right solution.

• Tips for more effective problem-solving

Complete problem-solving methods

• Problem-solving techniques to identify and analyze problems
• Problem-solving techniques for developing solutions

Problem-solving warm-up activities

Closing activities for a problem-solving process.

Before you can move towards finding the right solution for a given problem, you first need to identify and define the problem you wish to solve. 

Here, you want to clearly articulate what the problem is and allow your group to do the same. Remember that everyone in a group is likely to have differing perspectives and alignment is necessary in order to help the group move forward. 

Identifying a problem accurately also requires that all members of a group are able to contribute their views in an open and safe manner. It can be scary for people to stand up and contribute, especially if the problems or challenges are emotive or personal in nature. Be sure to try and create a psychologically safe space for these kinds of discussions.

Remember that problem analysis and further discussion are also important. Not taking the time to fully analyze and discuss a challenge can result in the development of solutions that are not fit for purpose or do not address the underlying issue.

Successfully identifying and then analyzing a problem means facilitating a group through activities designed to help them clearly and honestly articulate their thoughts and produce usable insight.

With this data, you might then produce a problem statement that clearly describes the problem you wish to be addressed and also state the goal of any process you undertake to tackle this issue.  

Finding solutions is the end goal of any process. Complex organizational challenges can only be solved with an appropriate solution but discovering them requires using the right problem-solving tool.

After you’ve explored a problem and discussed ideas, you need to help a team discuss and choose the right solution. Consensus tools and methods such as those below help a group explore possible solutions before then voting for the best. They’re a great way to tap into the collective intelligence of the group for great results!

Remember that the process is often iterative. Great problem solvers often roadtest a viable solution in a measured way to see what works too. While you might not get the right solution on your first try, the methods below help teams land on the most likely to succeed solution while also holding space for improvement.

Every effective problem solving process begins with an agenda . A well-structured workshop is one of the best methods for successfully guiding a group from exploring a problem to implementing a solution.

In SessionLab, it’s easy to go from an idea to a complete agenda . Start by dragging and dropping your core problem solving activities into place . Add timings, breaks and necessary materials before sharing your agenda with your colleagues.

The resulting agenda will be your guide to an effective and productive problem solving session that will also help you stay organized on the day!

Tips for more effective problem solving

Problem-solving activities are only one part of the puzzle. While a great method can help unlock your team’s ability to solve problems, without a thoughtful approach and strong facilitation the solutions may not be fit for purpose.

Let’s take a look at some problem-solving tips you can apply to any process to help it be a success!

Clearly define the problem

Jumping straight to solutions can be tempting, though without first clearly articulating a problem, the solution might not be the right one. Many of the problem-solving activities below include sections where the problem is explored and clearly defined before moving on.

This is a vital part of the problem-solving process and taking the time to fully define an issue can save time and effort later. A clear definition helps identify irrelevant information and it also ensures that your team sets off on the right track.

Don’t jump to conclusions

It’s easy for groups to exhibit cognitive bias or have preconceived ideas about both problems and potential solutions. Be sure to back up any problem statements or potential solutions with facts, research, and adequate forethought.

The best techniques ask participants to be methodical and challenge preconceived notions. Make sure you give the group enough time and space to collect relevant information and consider the problem in a new way. By approaching the process with a clear, rational mindset, you’ll often find that better solutions are more forthcoming.  

Try different approaches  

Problems come in all shapes and sizes and so too should the methods you use to solve them. If you find that one approach isn’t yielding results and your team isn’t finding different solutions, try mixing it up. You’ll be surprised at how using a new creative activity can unblock your team and generate great solutions.

Don’t take it personally 

Depending on the nature of your team or organizational problems, it’s easy for conversations to get heated. While it’s good for participants to be engaged in the discussions, ensure that emotions don’t run too high and that blame isn’t thrown around while finding solutions.

You’re all in it together, and even if your team or area is seeing problems, that isn’t necessarily a disparagement of you personally. Using facilitation skills to manage group dynamics is one effective method of helping conversations be more constructive.

Get the right people in the room

Your problem-solving method is often only as effective as the group using it. Getting the right people on the job and managing the number of people present is important too!

If the group is too small, you may not get enough different perspectives to effectively solve a problem. If the group is too large, you can go round and round during the ideation stages.

Creating the right group makeup is also important in ensuring you have the necessary expertise and skillset to both identify and follow up on potential solutions. Carefully consider who to include at each stage to help ensure your problem-solving method is followed and positioned for success.

Document everything

The best solutions can take refinement, iteration, and reflection to come out. Get into a habit of documenting your process in order to keep all the learnings from the session and to allow ideas to mature and develop. Many of the methods below involve the creation of documents or shared resources. Be sure to keep and share these so everyone can benefit from the work done!

Bring a facilitator 

Facilitation is all about making group processes easier. With a subject as potentially emotive and important as problem-solving, having an impartial third party in the form of a facilitator can make all the difference in finding great solutions and keeping the process moving. Consider bringing a facilitator to your problem-solving session to get better results and generate meaningful solutions!

Develop your problem-solving skills

It takes time and practice to be an effective problem solver. While some roles or participants might more naturally gravitate towards problem-solving, it can take development and planning to help everyone create better solutions.

You might develop a training program, run a problem-solving workshop or simply ask your team to practice using the techniques below. Check out our post on problem-solving skills to see how you and your group can develop the right mental process and be more resilient to issues too!

Design a great agenda

Workshops are a great format for solving problems. With the right approach, you can focus a group and help them find the solutions to their own problems. But designing a process can be time-consuming and finding the right activities can be difficult.

Check out our workshop planning guide to level-up your agenda design and start running more effective workshops. Need inspiration? Check out templates designed by expert facilitators to help you kickstart your process!

In this section, we’ll look at in-depth problem-solving methods that provide a complete end-to-end process for developing effective solutions. These will help guide your team from the discovery and definition of a problem through to delivering the right solution.

If you’re looking for an all-encompassing method or problem-solving model, these processes are a great place to start. They’ll ask your team to challenge preconceived ideas and adopt a mindset for solving problems more effectively.

• Six Thinking Hats
• Lightning Decision Jam
• Problem Definition Process
• Discovery & Action Dialogue

Design Sprint 2.0

• Open Space Technology

1. Six Thinking Hats

Individual approaches to solving a problem can be very different based on what team or role an individual holds. It can be easy for existing biases or perspectives to find their way into the mix, or for internal politics to direct a conversation.

Six Thinking Hats is a classic method for identifying the problems that need to be solved and enables your team to consider them from different angles, whether that is by focusing on facts and data, creative solutions, or by considering why a particular solution might not work.

Like all problem-solving frameworks, Six Thinking Hats is effective at helping teams remove roadblocks from a conversation or discussion and come to terms with all the aspects necessary to solve complex problems.

2. Lightning Decision Jam

Featured courtesy of Jonathan Courtney of AJ&Smart Berlin, Lightning Decision Jam is one of those strategies that should be in every facilitation toolbox. Exploring problems and finding solutions is often creative in nature, though as with any creative process, there is the potential to lose focus and get lost.

Unstructured discussions might get you there in the end, but it’s much more effective to use a method that creates a clear process and team focus.

In Lightning Decision Jam, participants are invited to begin by writing challenges, concerns, or mistakes on post-its without discussing them before then being invited by the moderator to present them to the group.

From there, the team vote on which problems to solve and are guided through steps that will allow them to reframe those problems, create solutions and then decide what to execute on. 

By deciding the problems that need to be solved as a team before moving on, this group process is great for ensuring the whole team is aligned and can take ownership over the next stages. 

Lightning Decision Jam (LDJ)   #action   #decision making   #problem solving   #issue analysis   #innovation   #design   #remote-friendly   The problem with anything that requires creative thinking is that it’s easy to get lost—lose focus and fall into the trap of having useless, open-ended, unstructured discussions. Here’s the most effective solution I’ve found: Replace all open, unstructured discussion with a clear process. What to use this exercise for: Anything which requires a group of people to make decisions, solve problems or discuss challenges. It’s always good to frame an LDJ session with a broad topic, here are some examples: The conversion flow of our checkout Our internal design process How we organise events Keeping up with our competition Improving sales flow

3. Problem Definition Process

While problems can be complex, the problem-solving methods you use to identify and solve those problems can often be simple in design. 

By taking the time to truly identify and define a problem before asking the group to reframe the challenge as an opportunity, this method is a great way to enable change.

Begin by identifying a focus question and exploring the ways in which it manifests before splitting into five teams who will each consider the problem using a different method: escape, reversal, exaggeration, distortion or wishful. Teams develop a problem objective and create ideas in line with their method before then feeding them back to the group.

This method is great for enabling in-depth discussions while also creating space for finding creative solutions too!

Problem Definition   #problem solving   #idea generation   #creativity   #online   #remote-friendly   A problem solving technique to define a problem, challenge or opportunity and to generate ideas.

4. The 5 Whys 

Sometimes, a group needs to go further with their strategies and analyze the root cause at the heart of organizational issues. An RCA or root cause analysis is the process of identifying what is at the heart of business problems or recurring challenges. 

The 5 Whys is a simple and effective method of helping a group go find the root cause of any problem or challenge and conduct analysis that will deliver results. 

By beginning with the creation of a problem statement and going through five stages to refine it, The 5 Whys provides everything you need to truly discover the cause of an issue.

The 5 Whys   #hyperisland   #innovation   This simple and powerful method is useful for getting to the core of a problem or challenge. As the title suggests, the group defines a problems, then asks the question “why” five times, often using the resulting explanation as a starting point for creative problem solving.

5. World Cafe

World Cafe is a simple but powerful facilitation technique to help bigger groups to focus their energy and attention on solving complex problems.

World Cafe enables this approach by creating a relaxed atmosphere where participants are able to self-organize and explore topics relevant and important to them which are themed around a central problem-solving purpose. Create the right atmosphere by modeling your space after a cafe and after guiding the group through the method, let them take the lead!

Making problem-solving a part of your organization’s culture in the long term can be a difficult undertaking. More approachable formats like World Cafe can be especially effective in bringing people unfamiliar with workshops into the fold. 

World Cafe   #hyperisland   #innovation   #issue analysis   World Café is a simple yet powerful method, originated by Juanita Brown, for enabling meaningful conversations driven completely by participants and the topics that are relevant and important to them. Facilitators create a cafe-style space and provide simple guidelines. Participants then self-organize and explore a set of relevant topics or questions for conversation.

6. Discovery & Action Dialogue (DAD)

One of the best approaches is to create a safe space for a group to share and discover practices and behaviors that can help them find their own solutions.

With DAD, you can help a group choose which problems they wish to solve and which approaches they will take to do so. It’s great at helping remove resistance to change and can help get buy-in at every level too!

This process of enabling frontline ownership is great in ensuring follow-through and is one of the methods you will want in your toolbox as a facilitator.

Discovery & Action Dialogue (DAD)   #idea generation   #liberating structures   #action   #issue analysis   #remote-friendly   DADs make it easy for a group or community to discover practices and behaviors that enable some individuals (without access to special resources and facing the same constraints) to find better solutions than their peers to common problems. These are called positive deviant (PD) behaviors and practices. DADs make it possible for people in the group, unit, or community to discover by themselves these PD practices. DADs also create favorable conditions for stimulating participants’ creativity in spaces where they can feel safe to invent new and more effective practices. Resistance to change evaporates as participants are unleashed to choose freely which practices they will adopt or try and which problems they will tackle. DADs make it possible to achieve frontline ownership of solutions.

7. Design Sprint 2.0

Want to see how a team can solve big problems and move forward with prototyping and testing solutions in a few days? The Design Sprint 2.0 template from Jake Knapp, author of Sprint, is a complete agenda for a with proven results.

Developing the right agenda can involve difficult but necessary planning. Ensuring all the correct steps are followed can also be stressful or time-consuming depending on your level of experience.

Use this complete 4-day workshop template if you are finding there is no obvious solution to your challenge and want to focus your team around a specific problem that might require a shortcut to launching a minimum viable product or waiting for the organization-wide implementation of a solution.

8. Open space technology

Open space technology- developed by Harrison Owen – creates a space where large groups are invited to take ownership of their problem solving and lead individual sessions. Open space technology is a great format when you have a great deal of expertise and insight in the room and want to allow for different takes and approaches on a particular theme or problem you need to be solved.

Start by bringing your participants together to align around a central theme and focus their efforts. Explain the ground rules to help guide the problem-solving process and then invite members to identify any issue connecting to the central theme that they are interested in and are prepared to take responsibility for.

Once participants have decided on their approach to the core theme, they write their issue on a piece of paper, announce it to the group, pick a session time and place, and post the paper on the wall. As the wall fills up with sessions, the group is then invited to join the sessions that interest them the most and which they can contribute to, then you’re ready to begin!

Everyone joins the problem-solving group they’ve signed up to, record the discussion and if appropriate, findings can then be shared with the rest of the group afterward.

Open Space Technology   #action plan   #idea generation   #problem solving   #issue analysis   #large group   #online   #remote-friendly   Open Space is a methodology for large groups to create their agenda discerning important topics for discussion, suitable for conferences, community gatherings and whole system facilitation

Techniques to identify and analyze problems

Using a problem-solving method to help a team identify and analyze a problem can be a quick and effective addition to any workshop or meeting.

While further actions are always necessary, you can generate momentum and alignment easily, and these activities are a great place to get started.

We’ve put together this list of techniques to help you and your team with problem identification, analysis, and discussion that sets the foundation for developing effective solutions.

Let’s take a look!

• The Creativity Dice
• Fishbone Analysis
• Problem Tree
• SWOT Analysis
• Agreement-Certainty Matrix
• The Journalistic Six
• LEGO Challenge
• What, So What, Now What?
• Journalists

Individual and group perspectives are incredibly important, but what happens if people are set in their minds and need a change of perspective in order to approach a problem more effectively?

Flip It is a method we love because it is both simple to understand and run, and allows groups to understand how their perspectives and biases are formed. 

Participants in Flip It are first invited to consider concerns, issues, or problems from a perspective of fear and write them on a flip chart. Then, the group is asked to consider those same issues from a perspective of hope and flip their understanding.  

No problem and solution is free from existing bias and by changing perspectives with Flip It, you can then develop a problem solving model quickly and effectively.

Flip It!   #gamestorming   #problem solving   #action   Often, a change in a problem or situation comes simply from a change in our perspectives. Flip It! is a quick game designed to show players that perspectives are made, not born.

10. The Creativity Dice

One of the most useful problem solving skills you can teach your team is of approaching challenges with creativity, flexibility, and openness. Games like The Creativity Dice allow teams to overcome the potential hurdle of too much linear thinking and approach the process with a sense of fun and speed. 

In The Creativity Dice, participants are organized around a topic and roll a dice to determine what they will work on for a period of 3 minutes at a time. They might roll a 3 and work on investigating factual information on the chosen topic. They might roll a 1 and work on identifying the specific goals, standards, or criteria for the session.

Encouraging rapid work and iteration while asking participants to be flexible are great skills to cultivate. Having a stage for idea incubation in this game is also important. Moments of pause can help ensure the ideas that are put forward are the most suitable. 

The Creativity Dice   #creativity   #problem solving   #thiagi   #issue analysis   Too much linear thinking is hazardous to creative problem solving. To be creative, you should approach the problem (or the opportunity) from different points of view. You should leave a thought hanging in mid-air and move to another. This skipping around prevents premature closure and lets your brain incubate one line of thought while you consciously pursue another.

11. Fishbone Analysis

Organizational or team challenges are rarely simple, and it’s important to remember that one problem can be an indication of something that goes deeper and may require further consideration to be solved.

Fishbone Analysis helps groups to dig deeper and understand the origins of a problem. It’s a great example of a root cause analysis method that is simple for everyone on a team to get their head around. 

Participants in this activity are asked to annotate a diagram of a fish, first adding the problem or issue to be worked on at the head of a fish before then brainstorming the root causes of the problem and adding them as bones on the fish. 

Using abstractions such as a diagram of a fish can really help a team break out of their regular thinking and develop a creative approach.

Fishbone Analysis   #problem solving   ##root cause analysis   #decision making   #online facilitation   A process to help identify and understand the origins of problems, issues or observations.

12. Problem Tree 

Encouraging visual thinking can be an essential part of many strategies. By simply reframing and clarifying problems, a group can move towards developing a problem solving model that works for them. 

In Problem Tree, groups are asked to first brainstorm a list of problems – these can be design problems, team problems or larger business problems – and then organize them into a hierarchy. The hierarchy could be from most important to least important or abstract to practical, though the key thing with problem solving games that involve this aspect is that your group has some way of managing and sorting all the issues that are raised.

Once you have a list of problems that need to be solved and have organized them accordingly, you’re then well-positioned for the next problem solving steps.

Problem tree   #define intentions   #create   #design   #issue analysis   A problem tree is a tool to clarify the hierarchy of problems addressed by the team within a design project; it represents high level problems or related sublevel problems.

13. SWOT Analysis

Chances are you’ve heard of the SWOT Analysis before. This problem-solving method focuses on identifying strengths, weaknesses, opportunities, and threats is a tried and tested method for both individuals and teams.

Start by creating a desired end state or outcome and bare this in mind – any process solving model is made more effective by knowing what you are moving towards. Create a quadrant made up of the four categories of a SWOT analysis and ask participants to generate ideas based on each of those quadrants.

Once you have those ideas assembled in their quadrants, cluster them together based on their affinity with other ideas. These clusters are then used to facilitate group conversations and move things forward. 

SWOT analysis   #gamestorming   #problem solving   #action   #meeting facilitation   The SWOT Analysis is a long-standing technique of looking at what we have, with respect to the desired end state, as well as what we could improve on. It gives us an opportunity to gauge approaching opportunities and dangers, and assess the seriousness of the conditions that affect our future. When we understand those conditions, we can influence what comes next.

14. Agreement-Certainty Matrix

Not every problem-solving approach is right for every challenge, and deciding on the right method for the challenge at hand is a key part of being an effective team.

The Agreement Certainty matrix helps teams align on the nature of the challenges facing them. By sorting problems from simple to chaotic, your team can understand what methods are suitable for each problem and what they can do to ensure effective results. 

If you are already using Liberating Structures techniques as part of your problem-solving strategy, the Agreement-Certainty Matrix can be an invaluable addition to your process. We’ve found it particularly if you are having issues with recurring problems in your organization and want to go deeper in understanding the root cause. 

Agreement-Certainty Matrix   #issue analysis   #liberating structures   #problem solving   You can help individuals or groups avoid the frequent mistake of trying to solve a problem with methods that are not adapted to the nature of their challenge. The combination of two questions makes it possible to easily sort challenges into four categories: simple, complicated, complex , and chaotic .  A problem is simple when it can be solved reliably with practices that are easy to duplicate.  It is complicated when experts are required to devise a sophisticated solution that will yield the desired results predictably.  A problem is complex when there are several valid ways to proceed but outcomes are not predictable in detail.  Chaotic is when the context is too turbulent to identify a path forward.  A loose analogy may be used to describe these differences: simple is like following a recipe, complicated like sending a rocket to the moon, complex like raising a child, and chaotic is like the game “Pin the Tail on the Donkey.”  The Liberating Structures Matching Matrix in Chapter 5 can be used as the first step to clarify the nature of a challenge and avoid the mismatches between problems and solutions that are frequently at the root of chronic, recurring problems.

Organizing and charting a team’s progress can be important in ensuring its success. SQUID (Sequential Question and Insight Diagram) is a great model that allows a team to effectively switch between giving questions and answers and develop the skills they need to stay on track throughout the process. 

Begin with two different colored sticky notes – one for questions and one for answers – and with your central topic (the head of the squid) on the board. Ask the group to first come up with a series of questions connected to their best guess of how to approach the topic. Ask the group to come up with answers to those questions, fix them to the board and connect them with a line. After some discussion, go back to question mode by responding to the generated answers or other points on the board.

It’s rewarding to see a diagram grow throughout the exercise, and a completed SQUID can provide a visual resource for future effort and as an example for other teams.

SQUID   #gamestorming   #project planning   #issue analysis   #problem solving   When exploring an information space, it’s important for a group to know where they are at any given time. By using SQUID, a group charts out the territory as they go and can navigate accordingly. SQUID stands for Sequential Question and Insight Diagram.

16. Speed Boat

To continue with our nautical theme, Speed Boat is a short and sweet activity that can help a team quickly identify what employees, clients or service users might have a problem with and analyze what might be standing in the way of achieving a solution.

Methods that allow for a group to make observations, have insights and obtain those eureka moments quickly are invaluable when trying to solve complex problems.

In Speed Boat, the approach is to first consider what anchors and challenges might be holding an organization (or boat) back. Bonus points if you are able to identify any sharks in the water and develop ideas that can also deal with competitors!   

Speed Boat   #gamestorming   #problem solving   #action   Speedboat is a short and sweet way to identify what your employees or clients don’t like about your product/service or what’s standing in the way of a desired goal.

17. The Journalistic Six

Some of the most effective ways of solving problems is by encouraging teams to be more inclusive and diverse in their thinking.

Based on the six key questions journalism students are taught to answer in articles and news stories, The Journalistic Six helps create teams to see the whole picture. By using who, what, when, where, why, and how to facilitate the conversation and encourage creative thinking, your team can make sure that the problem identification and problem analysis stages of the are covered exhaustively and thoughtfully. Reporter’s notebook and dictaphone optional.

The Journalistic Six – Who What When Where Why How   #idea generation   #issue analysis   #problem solving   #online   #creative thinking   #remote-friendly   A questioning method for generating, explaining, investigating ideas.

18. LEGO Challenge

Now for an activity that is a little out of the (toy) box. LEGO Serious Play is a facilitation methodology that can be used to improve creative thinking and problem-solving skills. 

The LEGO Challenge includes giving each member of the team an assignment that is hidden from the rest of the group while they create a structure without speaking.

What the LEGO challenge brings to the table is a fun working example of working with stakeholders who might not be on the same page to solve problems. Also, it’s LEGO! Who doesn’t love LEGO! 

LEGO Challenge   #hyperisland   #team   A team-building activity in which groups must work together to build a structure out of LEGO, but each individual has a secret “assignment” which makes the collaborative process more challenging. It emphasizes group communication, leadership dynamics, conflict, cooperation, patience and problem solving strategy.

19. What, So What, Now What?

If not carefully managed, the problem identification and problem analysis stages of the problem-solving process can actually create more problems and misunderstandings.

The What, So What, Now What? problem-solving activity is designed to help collect insights and move forward while also eliminating the possibility of disagreement when it comes to identifying, clarifying, and analyzing organizational or work problems. 

Facilitation is all about bringing groups together so that might work on a shared goal and the best problem-solving strategies ensure that teams are aligned in purpose, if not initially in opinion or insight.

Throughout the three steps of this game, you give everyone on a team to reflect on a problem by asking what happened, why it is important, and what actions should then be taken. 

This can be a great activity for bringing our individual perceptions about a problem or challenge and contextualizing it in a larger group setting. This is one of the most important problem-solving skills you can bring to your organization.

W³ – What, So What, Now What?   #issue analysis   #innovation   #liberating structures   You can help groups reflect on a shared experience in a way that builds understanding and spurs coordinated action while avoiding unproductive conflict. It is possible for every voice to be heard while simultaneously sifting for insights and shaping new direction. Progressing in stages makes this practical—from collecting facts about What Happened to making sense of these facts with So What and finally to what actions logically follow with Now What . The shared progression eliminates most of the misunderstandings that otherwise fuel disagreements about what to do. Voila!

20. Journalists  

Problem analysis can be one of the most important and decisive stages of all problem-solving tools. Sometimes, a team can become bogged down in the details and are unable to move forward.

Journalists is an activity that can avoid a group from getting stuck in the problem identification or problem analysis stages of the process.

In Journalists, the group is invited to draft the front page of a fictional newspaper and figure out what stories deserve to be on the cover and what headlines those stories will have. By reframing how your problems and challenges are approached, you can help a team move productively through the process and be better prepared for the steps to follow.

Journalists   #vision   #big picture   #issue analysis   #remote-friendly   This is an exercise to use when the group gets stuck in details and struggles to see the big picture. Also good for defining a vision.

Problem-solving techniques for developing solutions 

The success of any problem-solving process can be measured by the solutions it produces. After you’ve defined the issue, explored existing ideas, and ideated, it’s time to narrow down to the correct solution.

Use these problem-solving techniques when you want to help your team find consensus, compare possible solutions, and move towards taking action on a particular problem.

• Improved Solutions
• Four-Step Sketch
• 15% Solutions
• How-Now-Wow matrix
• Impact Effort Matrix

21. Mindspin  

Brainstorming is part of the bread and butter of the problem-solving process and all problem-solving strategies benefit from getting ideas out and challenging a team to generate solutions quickly. 

With Mindspin, participants are encouraged not only to generate ideas but to do so under time constraints and by slamming down cards and passing them on. By doing multiple rounds, your team can begin with a free generation of possible solutions before moving on to developing those solutions and encouraging further ideation. 

This is one of our favorite problem-solving activities and can be great for keeping the energy up throughout the workshop. Remember the importance of helping people become engaged in the process – energizing problem-solving techniques like Mindspin can help ensure your team stays engaged and happy, even when the problems they’re coming together to solve are complex. 

MindSpin   #teampedia   #idea generation   #problem solving   #action   A fast and loud method to enhance brainstorming within a team. Since this activity has more than round ideas that are repetitive can be ruled out leaving more creative and innovative answers to the challenge.

22. Improved Solutions

After a team has successfully identified a problem and come up with a few solutions, it can be tempting to call the work of the problem-solving process complete. That said, the first solution is not necessarily the best, and by including a further review and reflection activity into your problem-solving model, you can ensure your group reaches the best possible result. 

One of a number of problem-solving games from Thiagi Group, Improved Solutions helps you go the extra mile and develop suggested solutions with close consideration and peer review. By supporting the discussion of several problems at once and by shifting team roles throughout, this problem-solving technique is a dynamic way of finding the best solution. 

Improved Solutions   #creativity   #thiagi   #problem solving   #action   #team   You can improve any solution by objectively reviewing its strengths and weaknesses and making suitable adjustments. In this creativity framegame, you improve the solutions to several problems. To maintain objective detachment, you deal with a different problem during each of six rounds and assume different roles (problem owner, consultant, basher, booster, enhancer, and evaluator) during each round. At the conclusion of the activity, each player ends up with two solutions to her problem.

23. Four Step Sketch

Creative thinking and visual ideation does not need to be confined to the opening stages of your problem-solving strategies. Exercises that include sketching and prototyping on paper can be effective at the solution finding and development stage of the process, and can be great for keeping a team engaged. 

By going from simple notes to a crazy 8s round that involves rapidly sketching 8 variations on their ideas before then producing a final solution sketch, the group is able to iterate quickly and visually. Problem-solving techniques like Four-Step Sketch are great if you have a group of different thinkers and want to change things up from a more textual or discussion-based approach.

Four-Step Sketch   #design sprint   #innovation   #idea generation   #remote-friendly   The four-step sketch is an exercise that helps people to create well-formed concepts through a structured process that includes: Review key information Start design work on paper,  Consider multiple variations , Create a detailed solution . This exercise is preceded by a set of other activities allowing the group to clarify the challenge they want to solve. See how the Four Step Sketch exercise fits into a Design Sprint

24. 15% Solutions

Some problems are simpler than others and with the right problem-solving activities, you can empower people to take immediate actions that can help create organizational change. 

Part of the liberating structures toolkit, 15% solutions is a problem-solving technique that focuses on finding and implementing solutions quickly. A process of iterating and making small changes quickly can help generate momentum and an appetite for solving complex problems.

Problem-solving strategies can live and die on whether people are onboard. Getting some quick wins is a great way of getting people behind the process.   

It can be extremely empowering for a team to realize that problem-solving techniques can be deployed quickly and easily and delineate between things they can positively impact and those things they cannot change. 

15% Solutions   #action   #liberating structures   #remote-friendly   You can reveal the actions, however small, that everyone can do immediately. At a minimum, these will create momentum, and that may make a BIG difference.  15% Solutions show that there is no reason to wait around, feel powerless, or fearful. They help people pick it up a level. They get individuals and the group to focus on what is within their discretion instead of what they cannot change.  With a very simple question, you can flip the conversation to what can be done and find solutions to big problems that are often distributed widely in places not known in advance. Shifting a few grains of sand may trigger a landslide and change the whole landscape.

25. How-Now-Wow Matrix

The problem-solving process is often creative, as complex problems usually require a change of thinking and creative response in order to find the best solutions. While it’s common for the first stages to encourage creative thinking, groups can often gravitate to familiar solutions when it comes to the end of the process. 

When selecting solutions, you don’t want to lose your creative energy! The How-Now-Wow Matrix from Gamestorming is a great problem-solving activity that enables a group to stay creative and think out of the box when it comes to selecting the right solution for a given problem.

Problem-solving techniques that encourage creative thinking and the ideation and selection of new solutions can be the most effective in organisational change. Give the How-Now-Wow Matrix a go, and not just for how pleasant it is to say out loud. 

How-Now-Wow Matrix   #gamestorming   #idea generation   #remote-friendly   When people want to develop new ideas, they most often think out of the box in the brainstorming or divergent phase. However, when it comes to convergence, people often end up picking ideas that are most familiar to them. This is called a ‘creative paradox’ or a ‘creadox’. The How-Now-Wow matrix is an idea selection tool that breaks the creadox by forcing people to weigh each idea on 2 parameters.

26. Impact and Effort Matrix

All problem-solving techniques hope to not only find solutions to a given problem or challenge but to find the best solution. When it comes to finding a solution, groups are invited to put on their decision-making hats and really think about how a proposed idea would work in practice. 

The Impact and Effort Matrix is one of the problem-solving techniques that fall into this camp, empowering participants to first generate ideas and then categorize them into a 2×2 matrix based on impact and effort.

Activities that invite critical thinking while remaining simple are invaluable. Use the Impact and Effort Matrix to move from ideation and towards evaluating potential solutions before then committing to them. 

Impact and Effort Matrix   #gamestorming   #decision making   #action   #remote-friendly   In this decision-making exercise, possible actions are mapped based on two factors: effort required to implement and potential impact. Categorizing ideas along these lines is a useful technique in decision making, as it obliges contributors to balance and evaluate suggested actions before committing to them.

27. Dotmocracy

If you’ve followed each of the problem-solving steps with your group successfully, you should move towards the end of your process with heaps of possible solutions developed with a specific problem in mind. But how do you help a group go from ideation to putting a solution into action? 

Dotmocracy – or Dot Voting -is a tried and tested method of helping a team in the problem-solving process make decisions and put actions in place with a degree of oversight and consensus. 

One of the problem-solving techniques that should be in every facilitator’s toolbox, Dot Voting is fast and effective and can help identify the most popular and best solutions and help bring a group to a decision effectively. 

Dotmocracy   #action   #decision making   #group prioritization   #hyperisland   #remote-friendly   Dotmocracy is a simple method for group prioritization or decision-making. It is not an activity on its own, but a method to use in processes where prioritization or decision-making is the aim. The method supports a group to quickly see which options are most popular or relevant. The options or ideas are written on post-its and stuck up on a wall for the whole group to see. Each person votes for the options they think are the strongest, and that information is used to inform a decision.

All facilitators know that warm-ups and icebreakers are useful for any workshop or group process. Problem-solving workshops are no different.

Use these problem-solving techniques to warm up a group and prepare them for the rest of the process. Activating your group by tapping into some of the top problem-solving skills can be one of the best ways to see great outcomes from your session.

• Check-in/Check-out
• Doodling Together
• Show and Tell
• Constellations
• Draw a Tree

28. Check-in / Check-out

Solid processes are planned from beginning to end, and the best facilitators know that setting the tone and establishing a safe, open environment can be integral to a successful problem-solving process.

Check-in / Check-out is a great way to begin and/or bookend a problem-solving workshop. Checking in to a session emphasizes that everyone will be seen, heard, and expected to contribute. 

If you are running a series of meetings, setting a consistent pattern of checking in and checking out can really help your team get into a groove. We recommend this opening-closing activity for small to medium-sized groups though it can work with large groups if they’re disciplined!

Check-in / Check-out   #team   #opening   #closing   #hyperisland   #remote-friendly   Either checking-in or checking-out is a simple way for a team to open or close a process, symbolically and in a collaborative way. Checking-in/out invites each member in a group to be present, seen and heard, and to express a reflection or a feeling. Checking-in emphasizes presence, focus and group commitment; checking-out emphasizes reflection and symbolic closure.

29. Doodling Together  

Thinking creatively and not being afraid to make suggestions are important problem-solving skills for any group or team, and warming up by encouraging these behaviors is a great way to start. 

Doodling Together is one of our favorite creative ice breaker games – it’s quick, effective, and fun and can make all following problem-solving steps easier by encouraging a group to collaborate visually. By passing cards and adding additional items as they go, the workshop group gets into a groove of co-creation and idea development that is crucial to finding solutions to problems. 

Doodling Together   #collaboration   #creativity   #teamwork   #fun   #team   #visual methods   #energiser   #icebreaker   #remote-friendly   Create wild, weird and often funny postcards together & establish a group’s creative confidence.

30. Show and Tell

You might remember some version of Show and Tell from being a kid in school and it’s a great problem-solving activity to kick off a session.

Asking participants to prepare a little something before a workshop by bringing an object for show and tell can help them warm up before the session has even begun! Games that include a physical object can also help encourage early engagement before moving onto more big-picture thinking.

By asking your participants to tell stories about why they chose to bring a particular item to the group, you can help teams see things from new perspectives and see both differences and similarities in the way they approach a topic. Great groundwork for approaching a problem-solving process as a team! 

Show and Tell   #gamestorming   #action   #opening   #meeting facilitation   Show and Tell taps into the power of metaphors to reveal players’ underlying assumptions and associations around a topic The aim of the game is to get a deeper understanding of stakeholders’ perspectives on anything—a new project, an organizational restructuring, a shift in the company’s vision or team dynamic.

31. Constellations

Who doesn’t love stars? Constellations is a great warm-up activity for any workshop as it gets people up off their feet, energized, and ready to engage in new ways with established topics. It’s also great for showing existing beliefs, biases, and patterns that can come into play as part of your session.

Using warm-up games that help build trust and connection while also allowing for non-verbal responses can be great for easing people into the problem-solving process and encouraging engagement from everyone in the group. Constellations is great in large spaces that allow for movement and is definitely a practical exercise to allow the group to see patterns that are otherwise invisible. 

Constellations   #trust   #connection   #opening   #coaching   #patterns   #system   Individuals express their response to a statement or idea by standing closer or further from a central object. Used with teams to reveal system, hidden patterns, perspectives.

32. Draw a Tree

Problem-solving games that help raise group awareness through a central, unifying metaphor can be effective ways to warm-up a group in any problem-solving model.

Draw a Tree is a simple warm-up activity you can use in any group and which can provide a quick jolt of energy. Start by asking your participants to draw a tree in just 45 seconds – they can choose whether it will be abstract or realistic. 

Once the timer is up, ask the group how many people included the roots of the tree and use this as a means to discuss how we can ignore important parts of any system simply because they are not visible.

All problem-solving strategies are made more effective by thinking of problems critically and by exposing things that may not normally come to light. Warm-up games like Draw a Tree are great in that they quickly demonstrate some key problem-solving skills in an accessible and effective way.

Draw a Tree   #thiagi   #opening   #perspectives   #remote-friendly   With this game you can raise awarness about being more mindful, and aware of the environment we live in.

Each step of the problem-solving workshop benefits from an intelligent deployment of activities, games, and techniques. Bringing your session to an effective close helps ensure that solutions are followed through on and that you also celebrate what has been achieved.

Here are some problem-solving activities you can use to effectively close a workshop or meeting and ensure the great work you’ve done can continue afterward.

• One Breath Feedback
• Who What When Matrix
• Response Cards

How do I conclude a problem-solving process?

All good things must come to an end. With the bulk of the work done, it can be tempting to conclude your workshop swiftly and without a moment to debrief and align. This can be problematic in that it doesn’t allow your team to fully process the results or reflect on the process.

At the end of an effective session, your team will have gone through a process that, while productive, can be exhausting. It’s important to give your group a moment to take a breath, ensure that they are clear on future actions, and provide short feedback before leaving the space. 

The primary purpose of any problem-solving method is to generate solutions and then implement them. Be sure to take the opportunity to ensure everyone is aligned and ready to effectively implement the solutions you produced in the workshop.

Remember that every process can be improved and by giving a short moment to collect feedback in the session, you can further refine your problem-solving methods and see further success in the future too.

33. One Breath Feedback

Maintaining attention and focus during the closing stages of a problem-solving workshop can be tricky and so being concise when giving feedback can be important. It’s easy to incur “death by feedback” should some team members go on for too long sharing their perspectives in a quick feedback round. 

One Breath Feedback is a great closing activity for workshops. You give everyone an opportunity to provide feedback on what they’ve done but only in the space of a single breath. This keeps feedback short and to the point and means that everyone is encouraged to provide the most important piece of feedback to them. 

One breath feedback   #closing   #feedback   #action   This is a feedback round in just one breath that excels in maintaining attention: each participants is able to speak during just one breath … for most people that’s around 20 to 25 seconds … unless of course you’ve been a deep sea diver in which case you’ll be able to do it for longer.

34. Who What When Matrix 

Matrices feature as part of many effective problem-solving strategies and with good reason. They are easily recognizable, simple to use, and generate results.

The Who What When Matrix is a great tool to use when closing your problem-solving session by attributing a who, what and when to the actions and solutions you have decided upon. The resulting matrix is a simple, easy-to-follow way of ensuring your team can move forward. 

Great solutions can’t be enacted without action and ownership. Your problem-solving process should include a stage for allocating tasks to individuals or teams and creating a realistic timeframe for those solutions to be implemented or checked out. Use this method to keep the solution implementation process clear and simple for all involved. 

Who/What/When Matrix   #gamestorming   #action   #project planning   With Who/What/When matrix, you can connect people with clear actions they have defined and have committed to.

35. Response cards

Group discussion can comprise the bulk of most problem-solving activities and by the end of the process, you might find that your team is talked out! 

Providing a means for your team to give feedback with short written notes can ensure everyone is head and can contribute without the need to stand up and talk. Depending on the needs of the group, giving an alternative can help ensure everyone can contribute to your problem-solving model in the way that makes the most sense for them.

Response Cards is a great way to close a workshop if you are looking for a gentle warm-down and want to get some swift discussion around some of the feedback that is raised. 

Response Cards   #debriefing   #closing   #structured sharing   #questions and answers   #thiagi   #action   It can be hard to involve everyone during a closing of a session. Some might stay in the background or get unheard because of louder participants. However, with the use of Response Cards, everyone will be involved in providing feedback or clarify questions at the end of a session.

Save time and effort discovering the right solutions

A structured problem solving process is a surefire way of solving tough problems, discovering creative solutions and driving organizational change. But how can you design for successful outcomes?

With SessionLab, it’s easy to design engaging workshops that deliver results. Drag, drop and reorder blocks  to build your agenda. When you make changes or update your agenda, your session  timing   adjusts automatically , saving you time on manual adjustments.

Collaborating with stakeholders or clients? Share your agenda with a single click and collaborate in real-time. No more sending documents back and forth over email.

Explore  how to use SessionLab  to design effective problem solving workshops or  watch this five minute video  to see the planner in action!

Over to you

The problem-solving process can often be as complicated and multifaceted as the problems they are set-up to solve. With the right problem-solving techniques and a mix of creative exercises designed to guide discussion and generate purposeful ideas, we hope we’ve given you the tools to find the best solutions as simply and easily as possible.

Is there a problem-solving technique that you are missing here? Do you have a favorite activity or method you use when facilitating? Let us know in the comments below, we’d love to hear from you! 

thank you very much for these excellent techniques

Certainly wonderful article, very detailed. Shared!

Your list of techniques for problem solving can be helpfully extended by adding TRIZ to the list of techniques. TRIZ has 40 problem solving techniques derived from methods inventros and patent holders used to get new patents. About 10-12 are general approaches. many organization sponsor classes in TRIZ that are used to solve business problems or general organiztational problems. You can take a look at TRIZ and dwonload a free internet booklet to see if you feel it shound be included per your selection process.

Leave a Comment Cancel reply

Your email address will not be published. Required fields are marked *

Going from a mere idea to a workshop that delivers results for your clients can feel like a daunting task. In this piece, we will shine a light on all the work behind the scenes and help you learn how to plan a workshop from start to finish. On a good day, facilitation can feel like effortless magic, but that is mostly the result of backstage work, foresight, and a lot of careful planning. Read on to learn a step-by-step approach to breaking the process of planning a workshop into small, manageable chunks.  The flow starts with the first meeting with a client to define the purposes of a workshop.…

How does learning work? A clever 9-year-old once told me: “I know I am learning something new when I am surprised.” The science of adult learning tells us that, in order to learn new skills (which, unsurprisingly, is harder for adults to do than kids) grown-ups need to first get into a specific headspace.  In a business, this approach is often employed in a training session where employees learn new skills or work on professional development. But how do you ensure your training is effective? In this guide, we'll explore how to create an effective training session plan and run engaging training sessions. As team leader, project manager, or consultant,…

Effective online tools are a necessity for smooth and engaging virtual workshops and meetings. But how do you choose the right ones? Do you sometimes feel that the good old pen and paper or MS Office toolkit and email leaves you struggling to stay on top of managing and delivering your workshop? Fortunately, there are plenty of online tools to make your life easier when you need to facilitate a meeting and lead workshops. In this post, we’ll share our favorite online tools you can use to make your job as a facilitator easier. In fact, there are plenty of free online workshop tools and meeting facilitation software you can…

Design your next workshop with SessionLab

Join the 150,000 facilitators using SessionLab

Sign up for free

• Skip to main content
• Skip to primary sidebar
• Skip to footer

Additional menu

Fishbone diagrams: How to use them for problem-solving

October 5, 2023 by MindManager Blog

When something goes wrong, it’s essential to understand the root cause in order to prevent it from occurring again.

However, life and business are both complex, making it difficult to identify at times the underlying causes which created the situation you’re facing now. That’s where and when a fishbone diagram can help!

In this article, we’ll dive into everything you need to know about fishbone diagrams and how to use them for problem-solving.

What is a fishbone diagram?

Fishbone diagrams (also called Ishikawa diagrams and cause-and-effect diagrams) are visualizations used to identify and illustrate the causes for a specific event. Potential causes are often brainstormed and then categorized in order to identify a problem’s root cause.

The diagram gets its name due to the branches radiating out from the main issue in a way that resembles a side view of a fish skeleton. However, the process can be applied to most mind map layouts.

Here’s a fishbone diagram example:

When to use fishbone diagrams

Fishbone diagrams help focus you and your team’s energy on the root cause of a problem instead of merely addressing and wasting time on the symptoms.

Here are a few common applications of Fishbone diagrams:

Manufacturing: Discover the root cause of a manufacturing issue by brainstorming and ranking the likelihood and impact of all the areas that influence the production process.

How to create a fishbone diagram in MindManager in 5 steps

Fishbone diagrams are quick to make in MindManager and the examples above are included as templates to make it even easier.

MindManager’s ease of capturing ideas during brainstorming makes it the ideal tool to capture and organize potential causes. The visual format allows you to see all the causes simultaneously, draw relationships between causes, and identify if the root cause is found multiple times within the diagram.

Here’s how to create a fishbone diagram:

• In MindManager, go to the File menu, select New and then click into the Problem-Solving folder. There you’ll find three templates for Fishbones, the manufacturing, service, and product analyses. Select a template.
• Enter the issue in the central topic.
• Next, either brainstorm potential causes and add them as floating topics initially and categorize them after the brainstorming session. Or, use each category as a guide for a mini-brainstorm session and enter the potential causes directly in the appropriate branch.
• Add more details to your causes as new subtopics or notes with the cause itself.
• Once all the potential causes have been identified, you can take the diagram a step further and rank each cause. One way to do this would be to use the Priority marker to rank the cause between 1 and 9. You can later filter the diagram and view specific priorities and hide the less important ones that will distract the focus of the team.

Key MindManager features for fishbone diagrams

There is no one single ‘right’ way to create, categorize, or rank items within a fishbone diagram.

With that said, here’s a list of ways to apply some of MindManager’s features to transform an ordinary diagram into a powerful application to visualize and empower your work.

• Use color (fonts, topic fill color) to categorize different causes.
• Change the font characteristics to emphasize different causes (e.g. bold, larger fonts, different font types, etc.).
• Use topic images to add greater context and enhance the visualizations.
• Write topic notes for more in-depth details related to each cause.
• Apply icons and tags to categorize causes.
• Hyperlink or add attachments to provide more details.
• Draw relationship lines between different connected causes throughout the diagram.
• Assign resources to any causes that you have identified. This may clarify who is responsible or accountable for that cause.
• Collapse branches for a quick overview or drill down into all the details.
• View the diagram through multiple lenses. For instance, you are not confined to the layout of the Fishbone diagram. Switch views to see the diagram as an outline, or dive in the Schedule, Icon or Tag views to see your content in groupings based on your assigned categories or due dates.
• Filter content to either show or hide topics that you have annotated with tags or icon markers. For instance, filter on all the top priority potential causes that need additional investigation.
• Share your diagram by either publishing it onto the web (and sharing a link) where anyone can open and view the Fishbone diagram interactively in their browser or export the diagram into a variety of different formats (e.g. Microsoft Word, HTML5, Microsoft Project, etc.).

Download MindManager today to get started on your fishbone diagram!

Ready to take the next step?

MindManager helps boost collaboration and productivity among remote and hybrid teams to achieve better results, faster.

Why choose MindManager?

MindManager® helps individuals, teams, and enterprises bring greater clarity and structure to plans, projects, and processes. It provides visual productivity tools and mind mapping software to help take you and your organization to where you want to be.

Explore MindManager

36 Problem-solving techniques, methods and tools

When it comes to solving problems, getting ideas is the easy part. 

But businesses often forget the other four stages of the problem-solving process that will allow them to find the best solution.

Instead of jumping straight to idea generation, your problem-solving framework should look like this:

• Identify the problem
• Reveal why it has occurred
• Brainstorm ideas
• Select the best solution

See how idea generation doesn’t appear until stage 3?!

In this extensive resource, we provide techniques, methodologies and tools to guide you through every stage of the problem-solving process.

Once you’ve finished reading, you’ll possess an extensive problem-solving arsenal that will enable you to overcome your biggest workplace challenges.

11 Problem-solving techniques for clarity and confidence

Before we dive into more comprehensive methodologies for solving problems, there are a few basic techniques you should know. 

The following techniques will set you up for a successful problem-solving session with your team, allowing you to take on your biggest challenges with clarity and confidence. ‍

1. Take a moment, take a breath

When a problem or challenge arises, it’s normal to act too quickly or rely on solutions that have worked well in the past. This is known as entrenched thinking.

But acting impulsively, without prior consideration or planning, can cause you to misunderstand the issue and overlook possible solutions to the problem.

Therefore, the first thing you should always do when you encounter a problem is: breathe in and out.

Take a step back and make a clear plan of action before you act. This will help you to take rational steps towards solving a problem. ‍

2. Ask questions to understand the full extent of the issue

Another common mistake people make when attempting to solve a problem is taking action before fully understanding the problem.

Before committing to a theory, ask enough questions to unearth the true root of the issue. 

Later in this article, we cover The 5 Why’s problem-solving methodology which you can use to easily identify the root of your problem. Give this a go at your next meeting and see how your initial understanding of a problem can often be wrong. ‍

3. Consider alternative perspectives

A common problem-solving issue is that of myopia—a narrow-minded view or perception of the problem. Myopia can occur when you’re too involved with the problem or your team isn’t diverse enough.

To give yourself the best chance of resolving a problem, gain insight from a wide range of sources. Collaborate with key stakeholders, customers and on-the-ground employees to learn how the problem affects them and whether they have found workarounds or solutions.

To paint the broadest picture, don’t limit your problem-solving team to a specific archetype. Try to include everyone, from the chief executive to the office janitor.

If you’re working with a small team, try the Flip It! problem-solving methodology to view the issue from a fresh angle. ‍

4. Make your office space conducive to problem-solving

The environment in which your host your brainstorming sessions should maximise creativity . When your team members trust each other and feel relaxed, they’re more likely to come up with innovative ideas and solutions to a problem.

Here are a few ways to get your employees’ creative juices flowing:

• Play team-building games that maximise trust and build interpersonal relationships
• Improve your team’s problem-solving skills with games that encourage critical thinking
• Redesign the office with comfortable furniture and collaborative spaces
• Boost job satisfaction by creating a positive work-life balance
• Improve collaborative skills and learn to resolve conflicts

World Café is a problem-solving method that creates a casual environment conducive to creative thinking. 

Keep reading to learn more about how World Café can help your team solve complex organisational problems. ‍

5. Use problem-solving methodologies to guide the process

Because problem-solving is a creative process, it can be hard to keep it on track. As more ideas get banded around, conflicts can arise that derail the session.

That’s why problem-solving methodologies are so helpful. They offer you proven problem-solving frameworks to guide your group sessions and keep them on track.

The Six Thinking Hats problem-solving method is a popular technique that guides the process and helps your team analyse a problem from all angles.

We’re going to take a look at our favourite problem-solving methodologies in the next section of this article, XY Tried and tested problem-solving methodologies. ‍

6. Use analogies to solve complex problems

Sometimes, solving a different problem can help you uncover solutions to another problem! 

By stripping back a complex issue and framing it as a simplified analogy , you approach a problem from a different angle, enabling you to come up with alternative ideas.

After solving practice problems, your team might be more aptly equipped to solve real-world issues.

However, coming up with an analogy that reflects your issue can be difficult, so don’t worry if this technique doesn’t work for you.

The Speed Boat diagram is a visual tool that helps your employees view existing challenges as anchors holding back a boat which represents your end goals. By assigning a “weight” to each anchor, your team can prioritise which issues to tackle first. ‍

7. Establish clear constraints

Constraints make a big problem more approachable. 

Before you tackle a problem, establish clear boundaries and codes of conduct for the session. This allows your team to focus on the current issue without becoming distracted or veering off on a tangent.

In an article published in the Harvard Business Review, authors Oguz A. Acar, Murat Tarakci, and Daan van Knippenberg wrote, “Constraints … provide focus and a creative challenge that motivates people to search for and connect information from different sources to generate novel ideas for new products, services, or business processes.” (Why Constraints Are Good for Innovation, 2019)

Lightning Decision Jam is a prime example of how constraints can assist the creative process. Here, your team are given strict time constraints and isn’t permitted to discuss ideas until the end. ‍

8. Dislodge preconceived ideas

Humans are creatures of habit. 

We defer to strategies that have produced positive results in the past. This is typically beneficial because recalling our previous successes means we don’t need to constantly re-learn similar tasks.

But when it comes to problem-solving, this way of thinking can trip us up. We become fixated on a solution that worked in the past, but when this fails we’re dismayed and left wondering what to do next.

To resolve problems effectively, your employees need to escape the precincts of their imaginations. This helps to eliminate functional fixedness—the belief that an item serves only its predefined function.

Alternative Application is an icebreaker game that encourages employees to think outside the box by coming up with different uses for everyday objects. Try this at your next meeting or team-building event and watch your team tap into their creativity. ‍

9. Level the playing field

Having a diverse group of employees at your brainstorming sessions is a good idea, but there’s one problem: the extroverted members of your team will be more vocal than the introverts.

To ensure you’re gaining insight from every member of your team, you need to give your quieter employees equal opportunities to contribute by eliminating personality biases.

Read more: What icebreaker games and questions work best for introverts?

The obvious solution, then, is to “silence” the louder participants (it’s not as sinister as it sounds, promise)—all you have to do is ban your team from debating suggestions during the ideation process. 

The Lightning Decision Jam methodology gives your employees equal opportunities to contribute because much of the problem-solving process is carried out in silence. ‍

10. Take a break from the problem

Have you ever noticed how the best ideas seem to come when you’re not actively working on a problem? You may have spent hours slumped over your desk hashing out a solution, only for the “eureka!” moment to come when you’re walking your dog or taking a shower.

In James Webb Young’s book, A Technique for Producing Ideas , phase three of the process is “stepping away from the problem.” Young proclaims that after putting in the hard work, the information needs to ferment in the mind before any plausible ideas come to you.

So next time you’re in a meeting with your team trying to solve a problem, don’t panic if you don’t uncover groundbreaking ideas there and then. Allow everybody to mull over what they’ve learned, then reconvene at a later date.

The Creativity Dice methodology is a quick-fire brainstorming game that allows your team to incubate ideas while concentrating on another. ‍

11. Limit feedback sessions

The way your team delivers feedback at the end of a successful brainstorming session is critical. Left unsupervised, excessive feedback can undo all of your hard work.

Therefore, it’s wise to put a cap on the amount of feedback your team can provide. One great way of doing this is by using the One Breath Feedback technique.

By limiting your employees to one breath, they’re taught to be concise with their final comments. 

16 Tried and tested problem-solving methodologies

Problem-solving methodologies keep your brainstorming session on track and encourage your team to consider all angles of the issue.

Countless methods have wiggled their way into the world of business, each one with a unique strategy and end goal.

Here are 12 of our favourite problem-solving methodologies that will help you find the best-fit solution to your troubles. ‍

12. Six Thinking Hats

Six Thinking Hats is a methodical problem-solving framework that helps your group consider all possible problems, causes, solutions and repercussions by assigning a different coloured hat to each stage of the problem-solving process.

The roles of each hat are as follows:

• Blue Hat (Control): This hat controls the session and dictates the order in which the hats will be worn. When wearing the Blue Hat, your group will observe possible solutions, draw conclusions and define a plan of action.
• Green Hat (Idea Generation): The Green Hat signifies creativity. At this stage of the methodology, your team will focus their efforts on generating ideas, imagining solutions and considering alternatives.
• Red Hat (Intuition and Feelings): It’s time for your employees to communicate their feelings. Here, your team listen to their guts and convey their emotional impulses without justification. 
• Yellow Hat (Benefits and Values): What are the merits of each idea that has been put forward thus far? What positive impacts could they have?
• Black or Grey Hat (Caution): What are the potential risks or shortcomings of each idea? What negative impacts could result from implicating each idea?
• White Hat (Information and Data): While wearing The White Hat, your team must determine what information is needed and from where it can be obtained.

For Six Thinking Hats to work effectively, ensure your team acts within the confines of each role. 

While wearing The Yellow Hat, for example, your team should only discuss the positives . Any negative implications should be left for the Black or Grey hat.

Note: Feel free to alter the hat colours to align with your cultural context. ‍

13. Lightning Decision Jam (LDJ)

Lightning Decision Jam is a nine-stage problem-solving process designed to uncover a variety of perspectives while keeping the session on track.

The process starts by defining a general topic like the internal design process, interdepartmental communication, the sales funnel, etc.

Then, armed with pens and post-it notes, your team will work through the nine stages in the following order:

• Write problems (7 minutes)
• Present problems (4 minutes/person)
• Select problems (6 minutes)
• Reframe the problems (6 minutes)
• Offer solutions (7 minutes)
• Vote on solutions (10 minutes)
• Prioritise solutions (30 seconds)
• Decide what to execute (10 minutes)
• Create task lists (5 minutes)

The philosophy behind LDJ is that of constraint. By limiting discussion, employees can focus on compiling ideas and coming to democratic decisions that benefit the company without being distracted or going off on a tangent. ‍

14. The 5 Why’s

Root Cause Analysis (RCA) is the process of unearthing a problem and finding the underlying cause. To help you through this process, you can use The 5 Why’s methodology.

The idea is to ask why you’re experiencing a problem, reframe the problem based on the answer, and then ask “ why?” again. If you do this five times , you should come pretty close to the root of your original challenge.

While this might not be a comprehensive end-to-end methodology, it certainly helps you to pin down your core challenges. ‍

15. World Café

If you’ve had enough of uninspiring corporate boardrooms, World Café is the solution. 

This problem-solving strategy facilitates casual conversations around given topics, enabling players to speak more openly about their grievances without the pressure of a large group.

Here’s how to do it:

• Create a cosy cafe-style setting (try to have at least five or six chairs per table).
• As a group, decide on a core problem and mark this as the session topic.
• Divide your group into smaller teams by arranging five or six players at a table.
• Assign each group a question that pertains to the session topic, or decide on one question for all groups to discuss at once.
• Give the groups about 20 minutes to casually talk over each question.
• Repeat this with about three or four different questions, making sure to write down key insights from each group.
• Share the insights with the whole group.

World Café is a useful way of uncovering hidden causes and pitfalls by having multiple simultaneous conversations about a given topic. ‍

16. Discovery and Action Dialogue (DAD)

Discovery and Actions Dialogues are a collaborative method for employees to share and adopt personal behaviours in response to a problem. 

This crowdsourcing approach provides insight into how a problem affects individuals throughout your company and whether some are better equipped than others.

A DAD session is guided by a facilitator who asks seven open-ended questions in succession. Each person is given equal time to participate while a recorder takes down notes and valuable insights. 

This is a particularly effective method for uncovering preexisting ideas, behaviours and solutions from the people who face problems daily. ‍

17. Design Sprint 2.0

The Design Sprint 2.0 model by Jake Knapp helps your team to focus on finding, developing measuring a solution within four days . Because theorising is all well and good, but sometimes you can learn more by getting an idea off the ground and observing how it plays out in the real world.

Here’s the basic problem-solving framework:

• Day 1: Map out or sketch possible solutions
• Day 2: Choose the best solutions and storyboard your strategy going forward
• Day 3: Create a living, breathing prototype
• Day 4: Test and record how it performs in the real world

This technique is great for testing the viability of new products or expanding and fixing the features of an existing product. ‍

18. Open Space Technology

Open Space Technology is a method for large groups to create a problem-solving agenda around a central theme. It works best when your group is comprised of subject-matter experts and experienced individuals with a sufficient stake in the problem.

Open Space Technology works like this:

• Establish a core theme for your team to centralise their efforts.
• Ask the participants to consider their approach and write it on a post-it note.
• Everybody writes a time and place for discussion on their note and sticks it to the wall.
• The group is then invited to join the sessions that most interest them.
• Everybody joins and contributes to their chosen sessions
• Any significant insights and outcomes are recorded and presented to the group.

This methodology grants autonomy to your team and encourages them to take ownership of the problem-solving process. ‍

19. Round-Robin Brainstorming Technique

While not an end-to-end problem-solving methodology, the Round-Robin Brainstorming Technique is an effective way of squeezing every last ounce of creativity from your ideation sessions.

Here’s how it works:

• Decide on a problem that needs to be solved
• Sitting in a circle, give each employee a chance to offer an idea
• Have somebody write down each idea as they come up
• Participants can pass if they don’t have anything to contribute
• The brainstorming session ends once everybody has passed

Once you’ve compiled a long list of ideas, it’s up to you how you move forward. You could, for example, borrow techniques from other methodologies, such as the “vote on solutions” phase of the Lightning Decision Jam. ‍

20. Failure Modes and Effects Analysis (FMEA)

Failure Modes and Effects Analysis is a method for preventing and mitigating problems within your business processes.

This technique starts by examining the process in question and asking, “What could go wrong?” From here, your team starts to brainstorm a list of potential failures.

Then, going through the list one by one, ask your participants, “Why would this failure happen?” 

Once you’ve answered this question for each list item, ask yourselves, “What would the consequences be of this failure?”

This proactive method focuses on prevention rather than treatment. Instead of waiting for a problem to occur and reacting, you’re actively searching for future shortcomings. ‍

21. Flip It!

The Flip It! Methodology teaches your team to view their concerns in a different light and frame them instead as catalysts for positive change.

The game works like this:

• Select a topic your employees are likely to be concerned about, like market demand for your product or friction between departments.
• Give each participant a pile of sticky notes and ask them to write down all their fears about the topic.
• Take the fears and stick them to an area of the wall marked “fears.”
• Then, encourage your team to look at these fears and ask them to reframe them as “hope” by writing new statements on different sticky notes.
• Take these “hope” statements and stick them to an area of the wall marked “hope.”
• Discuss the statements, then ask them to vote on the areas they feel they can start to take action on. They can do this by drawing a dot on the corner of the sticky note.
• Move the notes with the most votes to a new area of the wall marked “traction.”
• Discuss the most popular statements as a group and brainstorm actionable items related to each.
• Write down the actions that need to be made and discuss them again as a group.

This brainstorming approach teaches your employees the danger of engrained thinking and helps them to reframe their fears as opportunities. ‍

22. The Creativity Dice

The Creativity Dice teaches your team to incubate ideas as they focus on different aspects of a problem. As we mentioned earlier in the article, giving ideas time to mature can be a highly effective problem-solving strategy. Here’s how the game works:

Choose a topic to focus on, It can be as specific or open-ended as you like. Write this down as a word or sentence. Roll the die, start a timer of three minutes and start writing down ideas within the confines of what that number resembles. The roles of each number are as follows:

• Specification: Write down goals you want to achieve.
• Investigation: Write down existing factual information you know about the topic.
• Ideation: Write down creative or practical ideas related to the topic.
• Incubation: Do something else unrelated to the problem.
• Iteration: Look at what you’ve already written and come up with related ideas (roll again if you didn’t write anything yet). ‍
• Integration: Look at everything you have written and try to create something cohesive from your ideas like a potential new product or actionable next step.

Once you’ve finished the activity, review your findings and decide what you want to take with you. ‍

23. SWOT Analysis

The SWOT Analysis is a long-standing method for analysing the current state of your business and considering how this affects the desired end state.

The basic idea is this:

• Before the meeting, come up with a “Desired end state” and draw a picture that represents this on a flipchart or whiteboard.
• Divide a large piece of paper into quadrants marked “Strengths”, “Weaknesses”, “Opportunities” and “Threats.”
• Starting with “Strengths”, work through the quadrants, coming up with ideas that relate to the desired end state.
• Ask your team to vote for the statements or ideas of each category that they feel are most relevant to the desired end state.
• As a group, discuss the implications that these statements have on the desired end state. Spark debate by asking thought-provoking and open-ended questions.

The SWOT Analysis is an intuitive method for understanding which parts of your business could be affecting your long-term goals. ‍

24. The Journalistic Six

When learning to cover every aspect of a story, journalists are taught to ask themselves six essential questions:  

Now, this approach has been adopted by organisations to help understand every angle of a problem. All you need is a clear focus question, then you can start working through the six questions with your team until you have a 360-degree view of what has, can and needs to be done. ‍

25. Gamestorming

Gamestorming is a one-stop creative-thinking framework that uses various games to help your team come up with innovative ideas.

Originally published as a book 10 years ago, Gamestorming contained a selection of creative games used by Silicon Valley’s top-performing businesses to develop groundbreaking products and services.

This collection of resources, plucked from the minds of founders and CEOs like Jeff Bezos and Steve Jobs, allows you to tap into the potentially genius ideas lying dormant in the minds of your employees. ‍

26. Four-Step Sketch

The Four-Step Sketch is a visual brainstorming that provides an alternative to traditional discussion-based ideation techniques .

This methodology requires prior discussion to clarify the purpose of the activity. Imagine you’re on a startup retreat , for example, and your team is taking part in a design sprint or hackathon.

Once you’ve brainstormed a list of ideas with your team, participants can look at the suggestions and take down any relevant notes. They then take these notes and turn them into rough sketches that resemble the idea.

Then, as a warm-up, give each participant eight minutes to produce eight alternative sketches (eight minutes per sketch) of the idea. These ideas are not to be shared with the group.

Finally, participants create new sketches based on their favourite ideas and share them with the group. The group can then vote on the ideas they think offer the best solution. ‍

27. 15% Solutions

15% Solutions is a problem-solving strategy for motivating and inspiring your employees. By encouraging your team to gain small victories, you pave the way for bigger changes.

First, ask your participants to think about things they can personally do within the confines of their role.

Then, arrange your team into small groups of three to four and give them time to share their ideas and consult with each other.

This simple problem-solving process removes negativity and powerlessness and teaches your team to take responsibility for change. 

9 Problem-solving tools for gathering and selecting ideas

Problem-solving tools support your meeting with easy-to-use graphs, visualisations and techniques.  

By implementing a problem-solving tool, you break the cycle of mundane verbal discussion, enabling you to maintain engagement throughout the session. ‍

28. Fishbone Diagram

The Fishbone Diagram (otherwise known as the Ishikawa Diagram or Cause and Effect Diagram), is a tool for identifying the leading causes of a problem. You can then consolidate these causes into a comprehensive “Problem Statement.”

The term “Fishbone Diagram” is derived from the diagram’s structure. The problem itself forms the tail, possible causes radiate from the sides to form the fish skeleton while the final “Problem Statement” appears as the “head” of the fish.

Example: A fast-food chain is investigating the declining quality of their food. As the team brainstorms potential causes, they come up with reasons like “poorly trained personnel”, “lack of quality control”, and “incorrect quantity of spices.” Together with other causes, the group summarises that these problems lead to “bad burgers.” They write this as the Problem Statement and set about eliminating the main contributing factors. ‍

29. The Problem Tree

A Problem Tree is a useful tool for assessing the importance or relevance of challenges concerning the core topic. If you’re launching a new product, for example, gather your team and brainstorm the current issues, roadblocks and bottlenecks that are hindering the process.

Then, work together to decide which of these are most pressing. Place the most relevant issues closer to the core topic and less relevant issues farther away. ‍

30. SQUID Diagram

The Squid Diagram is an easy-to-use tool that charts the progress of ideas and business developments as they unfold. Your SQUID Diagram can remain on a wall for your team to add to over time.

• Write down a core theme on a sticky note such as “customer service” or “Innovation”—this will be the “head” of your SQUID.
• Hand two sets of different coloured sticky notes to your participants and choose one colour to represent “questions” and the other to represent “answers.”
• Ask your team to write down questions pertaining to the success of the main topic. In the case of “Innovation,” your team might write things like “How can we improve collaboration between key stakeholders?”
• Then, using the other coloured sticky notes, ask your team to write down possible answers to these questions. In the example above, this might be “Invest in open innovation software.”
• Over time, you’ll develop a spawling SQUID Diagram that reflects the creative problem-solving process. ‍

31. The Speed Boat

The Speed Boat Diagram is a visual metaphor used to help your team identify and solve problems in the way of your goals.

Here’s how it works: 

• Draw a picture of a boat and name it after the core objective.
• With your team, brainstorm things that are slowing progress and draw each one as an anchor beneath the boat.
• Discuss possible solutions to each problem on the diagram.

This is an easy-to-use tool that sparks creative solutions. If you like, your team can assign a “weight” to each anchor which determines the impact each problem has on the end goal. ‍

32. The LEGO Challenge

LEGO is an excellent creative-thinking and problem-solving tool used regularly by event facilitators to help teams overcome challenges. 

In our article 5 and 10-minute Team-Building Activities , we introduce Sneak a Peek —a collaborative team-building game that develops communication and leadership skills. ‍

33. The Three W’s: What? So What? Now What?

Teams aren’t always aligned when it comes to their understanding of a problem. While the problem remains the same for everyone, they might have differing opinions as to how it occurred at the implications it had.

Asking “ What? So What? Now What?” Helps you to understand different perspectives around a problem.

It goes like this:

• Alone or in small groups, ask your employees to consider and write What happened. This should take between five and 10 minutes.
• Then ask So What? What occurred because of this? Why was what happened important? What might happen if this issue is left unresolved?
• Finally, ask your team Now What? What might be a solution to the problem? What actions do you need to take to avoid this happening again?

This approach helps your team understand how problems affect individuals in different ways and uncovers a variety of ways to overcome them. ‍

34. Now-How-Wow Matrix

Gathering ideas is easy—but selecting the best ones? That’s a different story. 

If you’ve got a bunch of ideas, try the Now-How-Wow Matrix to help you identify which ones you should implement now and which ones should wait until later.

Simply draw a two-axis graph with “implementation difficulty” on the Y axis and “idea originality” on the X axis. Divide this graph into quadrants and write “Now!” in the bottom left panel, “Wow!” in the bottom right panel, and “How?” in the top right panel. You can leave the top left panel blank.

Then, take your ideas and plot them on the graph depending on their implementation difficulty and level of originality.

By the end, you’ll have a clearer picture of which ideas to ignore, which ones to implement now, and which ones to add to the pipeline for the future. ‍

35. Impact-Effort Matrix

The Impact-Effort Matrix is a variation of the Now-How-Wow Matrix where the Y axis is marked “Impact” and the X axis is marked “Effort.”

Then, divide the graph into quadrants and plot your ideas. 

• Top left section = Excellent, implement immediately
• Top right section = Risky, but worth a try
• Bottom left section = Low risk, but potentially ineffective
• Bottom right section = Bad idea, ignore

The Impact-Effort Matrix is a simple way for your team to weigh the benefits of an idea against the amount of investment required. ‍

36. Dot Voting

Once you’ve gathered a substantial list of ideas from your employees, you need to sort the good from the bad. 

Dot voting is a simple tool used by problem-solving facilitators as a fast and effective way for large groups to vote on their favourite ideas . You’ll have seen this method used in problem-solving methods like Flip It! and Lightning Decision Jam .

• Participants write their ideas on sticky notes and stick them to the wall or a flipchart.
• When asked, participants draw a small dot on the corner of the idea they like the most.
• Participants can be given as many votes as necessary.
• When voting ends, arrange the notes from “most popular” to “least popular.”

This provides an easy-to-use visual representation of the best and worst ideas put forward by your team.

Give your problems the attention they deserve at an offsite retreat

While working from home or at the office, your team is often too caught up in daily tasks to take on complex problems. 

By escaping the office and uniting at an offsite location, you can craft a purposeful agenda of team-building activities and problem-solving sessions. This special time away from the office can prove invaluable when it comes to keeping your business on track.

If you have problems that need fixing (who doesn’t?), reach out to Surf Office and let us put together a fully-customised offsite retreat for you.

free course

How to plan your first company retreat

Retreat Budget Spreadsheet

Are you organising a company retreat and want to make sure you have all the costs under the control?

Get a copy of our free Budget Calculator spreadsheet.

25 Employee engagement ideas for remote employees

How to establish powerful employee connections

15 Truly impactful feedback methods for your team

Improve remote team communication with these 11 tips

From awareness to action: 35 Practical DEI tips

Organize your next company retreat with surf office, 💌 join 17,000+ managers receiving insights on building company culture that people love., stay in touch, work with us.

How to build a fishbone diagram and get the most out of it

No business operates without problems along the way. But to solve them in time, you’ll need to be able to determine the cause quickly. That’s where using a fishbone diagram comes in.

A fishbone diagram , also known as the Ishikawa diagram or cause-and-effect diagram, is a tool you can use to visualize all of a problem’s potential causes, allowing you to discover the root causes and identify the best possible solution.

We put this guide together to show you how to make a fishbone diagram based on a fictional problem we’ll be investigating: why a software company’s customer churn is so high.

Let’s get started.

Step 1 – Define the problem

The first step to solving any problem – and the key to learning how to make a fishbone diagram – is correctly defining it. A clearly defined problem makes it easier to identify causes. It also encourages us to determine whether there’s even a problem to begin with.

In this case, the problem we’ve identified is that 40% of users cancel their subscriptions after the first month — which keeps us from reaching our goal of keeping cancellations below 20%. Now that we’ve identified our main problem, we can go ahead and add that to the fishbone diagram.

Problem definition tips:

• If you’re using the fishbone diagram to design a process or increase productivity, it’s just as important to correctly define your output. Your goals should be objective and achievable.
• Place the problem (the fish head) on one side of the diagram, and build the rest of the diagram (the fish bones) out to its left or right. The idea is that the “fish bones” indicate the impact of the causes.
• Place the causes with the biggest impact closer to the fish head and the causes with the smaller impact further away.

Step 2 – Decide on key categories of causes

Next, decide what areas of the problem are key to determining the actual cause. Going back to our example of investigating a high churn rate, here are three areas worth looking into:

• Subscription system

Once you start considering potential causes, you might find that most of them fall within one of these three categories. But you can always add more categories if needed. For example, If you think marketing impacted your retention figures, you could add that as a fourth area.

You can have as many areas as you need to. But to keep things simple, we recommend limiting yourself to no more than 10 — especially since we’re only learning how to make a fishbone diagram with this example.

Step 3 – Determine the actual causes of the problem

Now that you’ve defined the key areas to look into, let’s go through each one to determine all the individual influences that can affect our output. Look at each category and list every possible cause you can think of.

Looking at the subscription system, some possible causes include:

• We aren’t offering enough payment options
• The payment and registration systems are difficult to navigate
• Credit cards expire, voiding renewal
• The system doesn’t send out reminders for renewals.

When considering the user, potential causes include:

• Users don’t understand the full benefit of the software
• Users don’t know how to use all the functions
• Users experience delays when contacting support
• Users don’t use the software continuously, only requiring it for a few days at a time
• Users forget about the product.

When it comes to the software itself, potential causes may be:

• The software is unstable and crashes regularly
• The software is difficult to use
• Software installation requires multiple plugins to function well
• Key functionality requires additional subscriptions
• The software is insecure.

These are just a few potential causes. You should fill your fishbone diagram with as many different causes as you can come up with. Note that not every area of your diagram needs to have causes. Some might even have more causes than others.

Regardless, you now have a starting point to determine root causes. To keep going, investigate each cause to establish its actual effect on your output.

Tips to determine the actual cause:

• Run a brainstorming session or lay out a process map to generate better causes for your fishbone diagram
• Invite other team members in the process to make sure you’ve identified all the potential causes
• Some causes may have multiple sub-causes. Expand your fishbone diagram as needed to encompass all possible causes.

Step 4 – Using tools to plan the way forward

Remember, a fishbone diagram helps identify a problem’s causes. It doesn’t lead to solutions on its own. In fact, part of learning how to make a fishbone diagram is knowing what other tools you can use to identify causes more effectively.

Here are a few more tools to help you take your fishbone diagram to the next level:

Process Map

A process map is a flowchart of a specific system, showing all its inputs and outputs. It works best in areas like the manufacturing industry, where each product has a clearly defined process with multiple steps.

Process mapping involves looking at each step of the process one by one and listing all the potential influences. In an actual manufacturing environment, this may include being present on the production line and viewing the system, taking notes as you go through the process.

A process map is very effective at making sure you consider all the steps and influences involved in a system. In other words, it helps you clearly identify potential causes and add them to your fishbone diagram.

Brainstorming

Brainstorming is a fairly common tool in modern businesses. Instead of considering all the factors of a fishbone diagram by yourself, include others in the process. When working alone, it’s easy to overlook certain areas and completely miss others.

That’s why it’s worth making sure your  brainstorming session  takes the shape of a clearly-defined meeting. Have someone lead the session, taking note of any ideas team members offer up and leaving room for discussion. The goal is to end the brainstorming session with a list of causes to add to your fishbone diagram.

Once you’ve filled out your fishbone diagram, make sure everyone’s on the same page about how to follow up — whether it’s about delegating tasks or setting clear deadlines.

Tips for planning next steps:

• Not sure what causes to investigate? Collaborate with your team members on developing a cause-and-effect matrix. This way, you’ll get to rank causes by priority based on your team’s experience.
• Want to address a problem’s root cause and not just its symptom? Use our 5 Whys Template to take a closer look.
• How to make a fishbone diagram in a remote team

A fishbone diagram is more effective when multiple people get involved in creating it. But if your team works in remote and hybrid settings, you’ll need a tool designed to facilitate seamless collaboration.

Miro’s visual workspace is built for collaboration, making it easy to make a fishbone diagram together in real time — even if you aren’t in the same room. Seamlessly build diagrams using our intuitive, automated diagramming tools and our drag-and-drop, infinite canvas.

Not sure how to make a fishbone diagram from scratch? Save time using our free Fishbone Diagram Template . It’s fully customizable, allowing your team to add as much detail as you want and adjust its look and feel.

Tips for collaborating on a fishbone diagram in Miro:

• Invite your team to edit your board with you in real-time
• Invite stakeholders to view and comment on your Miro board for instant feedback
• Differentiate ideas by color-coding them
• Use frames to present your fishbone diagram and easily export it as a PDF or image
• Use sticky notes to add important context when building your fishbone diagram

Above all, avoid trying to build your fishbone diagram too quickly. Take the time to understand all the contributing factors, and make sure that anything you add to the fishbone diagram adds value.

• When to use a fishbone diagram?

Though fishbone diagrams were originally meant for problem-solving, they’re far more versatile — helping you break down any process or system into its contributing factors.

Here are a few use cases where knowing how to make a fishbone diagram comes in handy:

• To analyze a problem statement
• To brainstorm the causes of the problem (root cause analysis)
• To analyze a new design
• Process improvement
• Quality improvement

When in doubt, talk to your team to clarify the problem you’re investigating and how a fishbone diagram would help.

Miro is your team's visual platform to connect, collaborate, and create — together.

Join millions of users that collaborate from all over the planet using Miro.

• Step 1 – Define the problem
• Step 2 – Decide on key categories of causes
• Step 3 – Determine the actual causes of the problem
• Step 4 – Using tools to plan the way forward

Keep reading

Agile beyond software development: how to empower non-tech teams.

Don’t let ideas die post-retro: 5 ways to make retrospectives more actionable

Removing the hassle of brainstorm documentation with Miro + Naer

• Memberships

Kepner Tregoe Method of Problem Solving

Kepner Tregoe Method of Problem Solving: this article explains the Kepner Tregoe Method , also known as the KT-method , developed by Charles Kepner and Benjamin Tregoe in a practical way. Next to what this is, this article also highlights rational processes, the importance of cause and that this method is effective. After reading, you’ll have a basic understanding of this problem solving process. Enjoy reading!

What is the Kepner Tregoe Method?

Problems occur in any given organization. Often there is pressure of time to solve the problems and it is debatable what the right way of solving these problems is.

The Kepner Tregoe method or KT-method is a problem analysis model in which the “problem” is disconnected from the “decision” . An English synonym for this problem solving method is Problem Solving and Decision Making (PSDM).

Traditional thinking pattern

The founders Charles Kepner and Benjamin Tregoe developed a rational working method in the 1960s in which they researched and identified the troubleshooting skills of people.

Throughout the centuries mankind has learned to deal with complexity and to (directly) anticipate on this. As a consequence, the traditional thinking pattern became a part of human nature.

When solving problems people search for the answer to the following four questions:

• What happened?
• Why did it happen?
• How should we act?
• What will be the (future) result?

Kepner Tregoe method: rational processes

To break through this traditional pattern Charles Kepner and Benjamin Tregoe came up with four rational processes in which four fundamental questions are reflected:

1. Situation analysis

This clarifies the problem situation (what happened).

1.1 Problem analysis

Here the actual cause of the problem and the relationship between cause and result are searched for (why did it happen).

1.2 Decision analysis

Based on the decision making criteria, choices are made to arrive at potential problem resolutions (how should we act).

1.3 Potential Problem analysis

Figure 1 – Kepner Tregoe Method Analysis

Distinction

According to the KT-method, different tasks involve different problems, which in turn need different approaches. A situation analysis will clarify the distinctions in all these processes and as a result it will be possible to search for suitable solutions. This situation analysis provides an insight into necessity, priority and urgency of the various tasks.

When it has become clear which tasks are to be prioritized (action list) preparations can be made for potential problems. By using a good problem analysis in advance, a process will be created to prevent future problems or in emergencies, to limit the damage.

The strengths of this method does not stop there. Apart from the fact that problems are specified in terms such as “what, where, when and how big”, the Kepner Tregoe Method focuses on anything that cannot be the cause of the problem.

Certain causes are therefore excluded. Based on a “this is” and “this is not” analysis a clear overview of possible causes can be created and this makes the troubleshooting process consistent.

The Kepner Tregoe Method is efficient

The KT-method deploys an efficient troubleshooting process. Through research Charles Kepner and Benjamin Tregoe discovered that the registration of a problem is not a uniform process. In spite of the available information, people usually process information badly, misinterpret this or overlook important matters.

In addition, Charles Kepner and Benjamin Tregoe examined the discrepancies between successful and less successful troubleshooting.

They discovered that a predetermined logical method facilitates the search for the causes of a problem. In their “Best practice in troubleshooting” , they describe this methodology, which forms the basis for this method.

The Kepner Tregoe Method is Effective

This method is universal and is still used today in many organizations to track down problems and identify potential causes. Apart from the fact that the Kepner Tregoe Method leads to an explanation of problems, it also helps improve mutual understanding within an organization.

It’s Your Turn

What do you think? Is the Kepner Tregoe Method applicable in today’s modern organizations? Do you recognize the practical explanation or do you have more suggestions? What are your success factors for the good Kepner Tregoe Method set up?

Share your experience and knowledge in the comments box below.

More information

• Lussier, R. N.  (2005). Management fundamentals: concepts. applications, skill development . Cengage Learning .
• Payne, S. L. & Marty, C.S. (1966). The Rational Manager: A Systematic Approach to Problem Solving and Decision Making . Journal of Marketing. Vol. 30 Issue 1, p97.
• Kepner, C. H. & Tregoe, B. B. (1965). The Rational Manager . McGraw-Hill.

How to cite this article: Mulder, P. (2012). Kepner Tregoe Method . Retrieved [insert date] from Toolshero: https://www.toolshero.com/problem-solving/kepner-tregoe-method/

Original publication date: 06/30/2012 | Last update: 12/09/2023

Add a link to this page on your website: <a href=”https://www.toolshero.com/problem-solving/kepner-tregoe-method/”>Toolshero: Kepner Tregoe Method</a>

Did you find this article interesting?

Your rating is more than welcome or share this article via Social media!

Average rating 3.7 / 5. Vote count: 30

No votes so far! Be the first to rate this post.

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Patty Mulder

Patty Mulder is an Dutch expert on Management Skills, Personal Effectiveness and Business Communication. She is also a Content writer, Business Coach and Company Trainer and lives in the Netherlands (Europe). Note: all her articles are written in Dutch and we translated her articles to English!

Related ARTICLES

Soft Systems Methodology (SSM) by Peter Checkland

Convergent Thinking: the Definition and Theory

CATWOE Analysis: theory and example

Means End Analysis: the basics and example

Systems Thinking: Theory and Definition

5 Whys Root Cause Analysis (Toyoda)

Also interesting.

Crowdsourcing: the meaning, definition and some examples

Systematic Inventive Thinking (SIT)

Linear Thinking by Edward De Bono explained

4 responses to “kepner tregoe method of problem solving”.

I am stunned to read that the Kepner Tregoe Method “…… IS STILL used today in many organizations to track down problems and identify potential causes…..”. I have used it all the time along my career as a manager of organizations, with extreme success. As a tool for identifying problems, as a tool for taking better decisions. So, please, I would appreciate to know what kind of system is being used now instead of an approach like K-T, to have provoked your comment about the existence of an alternative way of thinking.

Other than KT, I also use the Analytic Hierarchy Process (AHP) Like KT, it forces discipline and analysis and it helps to explain why decisions are made with understandable background and data. Many of the old Total Quality Management tools are also useful for solving problems and making good management decisions. Nominal Group Technique, Pareto Charts, and weighted multivoting are all quite useful. ITIL is the new way of thinking, but it can be rather dry and robotic unless it is underpinned with good decision tools.

Thank you for your comment and sharing your experience Pete.

Seems that I naturally deal with problems this way without knowing a name for it. In fact, it seems obvious to me that this approach should be taken anyway.

Leave a Reply Cancel reply

You must be logged in to post a comment.

BOOST YOUR SKILLS

Toolshero supports people worldwide ( 10+ million visitors from 100+ countries ) to empower themselves through an easily accessible and high-quality learning platform for personal and professional development.

By making access to scientific knowledge simple and affordable, self-development becomes attainable for everyone, including you! Join our learning platform and boost your skills with Toolshero.

POPULAR TOPICS

• Change Management
• Marketing Theories
• Problem Solving Theories
• Psychology Theories

ABOUT TOOLSHERO

• Free Toolshero e-book
• Memberships & Pricing

Venn Diagram Examples, Problems and Solutions

On this page:

• What is Venn diagram? Definition and meaning.
• Venn diagram formula with an explanation.
• Examples of 2 and 3 sets Venn diagrams: practice problems with solutions, questions, and answers.
• Simple 4 circles Venn diagram with word problems.
• Compare and contrast Venn diagram example.

Let’s define it:

A Venn Diagram is an illustration that shows logical relationships between two or more sets (grouping items). Venn diagram uses circles (both overlapping and nonoverlapping) or other shapes.

Commonly, Venn diagrams show how given items are similar and different.

Despite Venn diagram with 2 or 3 circles are the most common type, there are also many diagrams with a larger number of circles (5,6,7,8,10…). Theoretically, they can have unlimited circles.

Venn Diagram General Formula

n(A ∪ B) = n(A) + n(B) – n(A ∩ B)

Don’t worry, there is no need to remember this formula, once you grasp the meaning. Let’s see the explanation with an example.

This is a very simple Venn diagram example that shows the relationship between two overlapping sets X, Y.

X – the number of items that belong to set A Y – the number of items that belong to set B Z – the number of items that belong to set A and B both

From the above Venn diagram, it is quite clear that

n(A) = x + z n(B) = y + z n(A ∩ B) = z n(A ∪ B) = x +y+ z.

Now, let’s move forward and think about Venn Diagrams with 3 circles.

Following the same logic, we can write the formula for 3 circles Venn diagram :

n(A ∪ B ∪ C) = n(A) + n(B) + n(C) – n(A ∩ B) – n(B ∩ C) – n(C ∩ A) + n(A ∩ B ∩ C)

Venn Diagram Examples (Problems with Solutions)

As we already know how the Venn diagram works, we are going to give some practical examples (problems with solutions) from the real life.

2 Circle Venn Diagram Examples (word problems):

Suppose that in a town, 800 people are selected by random types of sampling methods . 280 go to work by car only, 220 go to work by bicycle only and 140 use both ways – sometimes go with a car and sometimes with a bicycle.

Here are some important questions we will find the answers:

• How many people go to work by car only?
• How many people go to work by bicycle only?
• How many people go by neither car nor bicycle?
• How many people use at least one of both transportation types?
• How many people use only one of car or bicycle?

The following Venn diagram represents the data above:

Now, we are going to answer our questions:

• Number of people who go to work by car only = 280
• Number of people who go to work by bicycle only = 220
• Number of people who go by neither car nor bicycle = 160
• Number of people who use at least one of both transportation types = n(only car) + n(only bicycle) + n(both car and bicycle) = 280 + 220 + 140 = 640
• Number of people who use only one of car or bicycle = 280 + 220 = 500

Note: The number of people who go by neither car nor bicycle (160) is illustrated outside of the circles. It is a common practice the number of items that belong to none of the studied sets, to be illustrated outside of the diagram circles.

We will deep further with a more complicated triple Venn diagram example.

3 Circle Venn Diagram Examples:

For the purposes of a marketing research , a survey of 1000 women is conducted in a town. The results show that 52 % liked watching comedies, 45% liked watching fantasy movies and 60% liked watching romantic movies. In addition, 25% liked watching comedy and fantasy both, 28% liked watching romantic and fantasy both and 30% liked watching comedy and romantic movies both. 6% liked watching none of these movie genres.

Here are our questions we should find the answer:

• How many women like watching all the three movie genres?
• Find the number of women who like watching only one of the three genres.
• Find the number of women who like watching at least two of the given genres.

Let’s represent the data above in a more digestible way using the Venn diagram formula elements:

• n(C) = percentage of women who like watching comedy = 52%
• n(F ) = percentage of women who like watching fantasy = 45%
• n(R) = percentage of women who like watching romantic movies= 60%
• n(C∩F) = 25%; n(F∩R) = 28%; n(C∩R) = 30%
• Since 6% like watching none of the given genres so, n (C ∪ F ∪ R) = 94%.

Now, we are going to apply the Venn diagram formula for 3 circles. 

94% = 52% + 45% + 60% – 25% – 28% – 30% + n (C ∩ F ∩ R)

Solving this simple math equation, lead us to:

n (C ∩ F ∩ R)  = 20%

It is a great time to make our Venn diagram related to the above situation (problem):

See, the Venn diagram makes our situation much more clear!

From the Venn diagram example, we can answer our questions with ease.

• The number of women who like watching all the three genres = 20% of 1000 = 200.
• Number of women who like watching only one of the three genres = (17% + 12% + 22%) of 1000 = 510
• The number of women who like watching at least two of the given genres = (number of women who like watching only two of the genres) +(number of women who like watching all the three genres) = (10 + 5 + 8 + 20)% i.e. 43% of 1000 = 430.

As we mentioned above 2 and 3 circle diagrams are much more common for problem-solving in many areas such as business, statistics, data science and etc. However, 4 circle Venn diagram also has its place.

4 Circles Venn Diagram Example:

A set of students were asked to tell which sports they played in school.

The options are: Football, Hockey, Basketball, and Netball.

Here is the list of the results:

The next step is to draw a Venn diagram to show the data sets we have.

It is very clear who plays which sports. As you see the diagram also include the student who does not play any sports (Dorothy) by putting her name outside of the 4 circles.

From the above Venn diagram examples, it is obvious that this graphical tool can help you a lot in representing a variety of data sets. Venn diagram also is among the most popular types of graphs for identifying similarities and differences .

Compare and Contrast Venn Diagram Example:

The following compare and contrast example of Venn diagram compares the features of birds and bats:

Tools for creating Venn diagrams

It is quite easy to create Venn diagrams, especially when you have the right tool. Nowadays, one of the most popular way to create them is with the help of paid or free graphing software tools such as:

You can use Microsoft products such as:

Some free mind mapping tools are also a good solution. Finally, you can simply use a sheet of paper or a whiteboard.

Conclusion:

A Venn diagram is a simple but powerful way to represent the relationships between datasets. It makes understanding math, different types of data analysis , set theory and business information easier and more fun for you.

Besides of using Venn diagram examples for problem-solving and comparing, you can use them to present passion, talent, feelings, funny moments and etc.

Be it data science or real-world situations, Venn diagrams are a great weapon in your hand to deal with almost any kind of information.

If you need more chart examples, our posts fishbone diagram examples and what does scatter plot show might be of help.

About The Author

Silvia Valcheva

Silvia Valcheva is a digital marketer with over a decade of experience creating content for the tech industry. She has a strong passion for writing about emerging software and technologies such as big data, AI (Artificial Intelligence), IoT (Internet of Things), process automation, etc.

Well explained I hope more on this one

WELL STRUCTURED CONTENT AND ENLIGHTNING AS WELL

Leave a Reply Cancel Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed .

• How to Use Ishikawa Diagrams to Solve Business Problems

• Learn Lean Sigma
• Root Cause Analysis

Do you want to solve business problems in an efficient manner? If this is the case, you should think about using Ishikawa Diagrams. Ishikawa Diagrams, also known as fishbone diagrams or cause-and-effect diagrams, are a visual tool that can help identify the root causes of a problem. As a result, they are an ideal solution for businesses looking to improve their processes and reduce errors.

We’ll look at how Ishikawa Diagrams can be used to solve business problems in this post. We’ll look at the anatomy of an Ishikawa Diagram and show you how to make one step by step. We’ll also look at real-world examples of business problems solved with Ishikawa Diagrams and the benefits gained by doing so. Finally, we’ll go over best practises for using Ishikawa Diagrams and how to avoid common pitfalls.

Whether you’re new to Ishikawa Diagrams or want to improve your problem-solving skills, this post will walk you through how to use this powerful tool to solve business problems.

Table of Contents

What is an ishikawa diagram.

Because of its appearance, the Ishikawa Diagram is also known as the fishbone diagram after its creator, Kaoru Ishikawa. The diagram is organised with a central spine and several branches that resemble fish bones. Each branch represents a possible cause category that contributes to the problem under consideration.

Because it is a versatile and widely used tool in problem solving and process improvement, an Ishikawa diagram is known by many different names. Here are some brief explanations for the various names:

Fishbone diagram: This name comes from the visual appearance of the diagram, which looks like a fish skeleton with the problem or effect at the head and the causes branching out like the bones of the fish.

Cause-and-effect diagram: This name reflects the diagram’s purpose, which is to aid in the identification of the root causes of a problem by mapping out the various factors that contribute to it. The diagram depicts the relationships between the causes and the effects, making it easier to determine where to focus improvement efforts.

Herringbone diagram: This is another name for the diagram’s appearance. The diagram’s branches resemble the bones of a herring, a type of fish.

While the names may be used interchangeably, they all refer to the same basic problem-solving and process-improvement tool.

An Ishikawa Diagram has six main branches, which are as follows:

• Personnel – This branch includes all human-related factors that may have an impact on the problem under consideration, such as training, communication, and teamwork.
• Process – This branch includes all of the steps and procedures involved in the process or activity, as well as the equipment, materials, and workflow.
• Machines – This branch includes all the physical equipment and machinery used in the process, including tools, machines, and technology.
• Materials – The raw materials and other inputs used in the process, such as supplies, ingredients, and components, are the focus of this branch.
• Environment – This branch includes all environmental factors that may affect the process, such as temperature, humidity, lighting, and noise.
• Measurement – This branch includes all metrics and measurements used to evaluate the process, such as quality standards, performance indicators, and statistical analysis.

Each of these branches is used to identify potential causes that may be contributing to the problem under investigation. For example, if a decrease in product quality is the issue, the Ishikawa Diagram can be used to identify the various factors that could be causing this problem, such as a lack of employee training, faulty equipment, or low-quality materials. The branches are used to identify as many potential causes as possible, which can then be further evaluated to determine the underlying cause of the problem.

The Ishikawa Diagram assists teams in gaining a better understanding of the problem being analysed and developing targeted solutions to address the root cause by identifying potential causes and organising them in a clear and concise manner.

How to Create an Ishikawa Diagram

Creating an Ishikawa Diagram is a simple process that begins with identifying the problem and breaking it down into its component parts. Here’s a step-by-step tutorial for making an Ishikawa Diagram:

• Step 1: Identify the problem and write it in a box at the top of the diagram.
• Step 2: To represent the main spine of the fishbone diagram, draw a horizontal arrow pointing to the problem box.
• Step 3: Draw a diagonal arrow for each of the diagram’s six main branches (People, Process, Equipment, Materials, Environment, and Measurement). Label each arrow with the name of the corresponding branch.
• Step 4: Determine the possible causes of the problem and document them on the appropriate branch. Create as many causes as you can and add them to the diagram.
• Step 5: If necessary, divide each cause into smaller sub-causes. Include these sub-causes in your diagram as well.
• Step 6: Determine the root cause of the problem by evaluating potential causes and sub-causes. The root cause is the underlying issue that is causing the problem being investigated.
• Step 7: Create and implement solutions to the root cause.

In addition to drawing an Ishikawa Diagram by hand, several software tools are available to help you create and collaborate on these diagrams. Among the most popular software tools are:

SmartDraw : This programme provides a variety of templates and tools for creating professional-looking Ishikawa Diagrams.

Lucidchart : This cloud-based software enables teams to work together in real-time to create Ishikawa Diagrams.

Creately : For creating Ishikawa Diagrams, this tool provides a variety of templates and customization options.

Creating Ishikawa Diagrams with software tools can save time and streamline the process of collaborating with team members. These tools also make it simple to share and export the diagram in a variety of formats, making it easier to include in presentations and reports.

Using Ishikawa Diagrams in Problem-Solving

Ishikawa Diagrams are a powerful problem-solving tool that can be used in root cause analysis. Teams can analyse the causes and develop solutions to address the root cause by identifying the various factors that contribute to a problem.

The process of determining the underlying cause of a problem rather than just addressing its symptoms is known as root cause analysis. This approach assists teams in developing more effective and long-term problem solutions.

To use an Ishikawa Diagram in root cause analysis, teams must first identify the problem and draw a fishbone diagram. The diagram’s six main branches (Personnel, Process, Machine, Materials, Environment, and Measurement) are used to identify potential problem causes. Teams can analyse the root cause by brainstorming and organizing these causes on the diagram.

Teams can use the “five whys” technique in addition to an Ishikawa Diagram to identify the root cause of a problem. The five whys technique is a method of drilling down into the root cause of a problem by asking “why” five times. The goal is for the team to keep asking “why” until they find the underlying root cause of the problem.

For example, if the issue is a product delivery delay, the five whys technique could be used as follows:

• Why was the product delivery delayed? – Because the shipment was sent to the wrong address.
• Why was it sent to the wrong address? – Because the shipping label was incorrect.
• Why was the label incorrect? – Because the person who prepared it didn’t check the address.
• Why didn’t they check the address? – Because they were in a rush to finish the task.
• Why were they in a rush? – Because they were given too many tasks to complete in a short amount of time.

In this example, the root cause of the product delivery delay is that the worker was assigned too many tasks to complete in a short period of time. By identifying the root cause, the team can develop solutions to the problem, such as allocating more time for tasks or more effectively delegating responsibilities.

To Summarize here is an overview of how Ishikawa Diagrams are used in root cause analysis follows:

Step 1: Brainstorm potential causes for each branch and write them on the diagram’s appropriate branch.

Step 2: Examine each possible cause to see if it is the root cause or a symptom of the problem.

Step 3: Use 5 Whys Analysis to ask “why” five times for each potential root cause identified to determine the underlying cause of the problem. Check out our 5 Whys Analysis Template to support this

Step 4: Once the root cause has been identified, develop and implement solutions to address it.

Here is an example of how a complete Ishikawa Diagram may look with potential problems identified on it.

To summarise, Ishikawa Diagrams are an effective problem-solving tool that can be combined with the five whys technique to identify the root cause of a problem. Teams can develop more effective and long-term solutions to improve their processes and operations by analysing potential causes and asking “why” to drill down into the underlying issue.

Examples of Business Problems Solved with Ishikawa Diagrams

Ishikawa Diagrams, also known as fishbone diagrams, have been used to solve a wide range of business problems. Here are some real-world examples of business problems solved with Ishikawa Diagrams:

Quality control issues in a manufacturing plant

A manufacturing plant was experiencing quality control issues with their products. The problem was identified using an Ishikawa Diagram, which helped the team to identify the potential causes of the problem. The diagram revealed that the issues were caused by a lack of training among the employees, poor machine maintenance, and inadequate raw materials. By addressing these issues, the plant was able to improve the quality of its products and reduce waste.

A call centre has a high employee turnover rate.

A call center’s ability to provide quality customer service was being hampered by high employee turnover. An Ishikawa Diagram was used to identify the problem, which assisted the team in determining the potential causes of the high turnover rate. According to the diagram, the problems were caused by low employee morale, insufficient training, and a lack of career development opportunities. The call centre was able to improve employee satisfaction and retention rates by addressing these issues.

Inventory management in a retail store is inefficient.

A retail store’s inventory management process was inefficient, resulting in excess inventory and stockouts. An Ishikawa Diagram was used to identify the problem, which assisted the team in determining the potential causes of the inefficiencies. According to the diagram, the problems were caused by inaccurate demand forecasting, insufficient inventory tracking, and poor communication among the store’s departments. The store was able to improve its inventory management process, reduce excess inventory, and prevent stockouts by addressing these issues.

The Ishikawa Diagram was used as a problem-solving tool in each of these examples to identify potential causes of the problem. The diagram enabled the teams to brainstorm and organise the various factors that could be contributing to the problem, allowing them to drill down to the root cause. The teams were able to implement more effective and long-term solutions to improve their processes and operations by addressing the root cause.

The advantages of using Ishikawa Diagrams in these scenarios include improved quality control, reduced waste, increased employee retention and satisfaction, and increased inventory management efficiency. The diagram enabled the teams to take a structured approach to problem-solving, allowing them to identify the root cause of the problem and develop more effective solutions.

Best Practice for Ishikawa Diagrams

Ishikawa Diagrams are a powerful problem-solving tool, but they must be used correctly to produce the desired results. Some best practises for using Ishikawa Diagrams in problem-solving processes are as follows:

• Clearly define the problem: Before you create an Ishikawa Diagram, you must first define the problem you are attempting to solve. This will aid your concentration and ensure that your diagram is relevant and effective.
• Involve a diverse team: Ishikawa Diagrams work best when used in a group setting. To ensure a well-rounded perspective, try to include a diverse group of people from various departments or areas of expertise.
• Brainstorm potential causes: Encourage team members to brainstorm all potential causes of the problem when creating the diagram. This will assist you in identifying all potential root causes and ensuring that your solutions are all-inclusive.
• Use clear and concise language: When labelling the branches of the diagram, use clear and concise language to ensure that everyone understands the meaning. Avoid using jargon or abbreviations that may be confusing to some team members.
• Prioritize potential causes: After identifying all potential causes, prioritise them based on their likelihood of contributing to the problem. This will allow you to concentrate your efforts on the most pressing root causes.
• Verify the root cause: Before implementing any solutions, test your hypothesis to determine the root cause of the problem. This will help you ensure that you are treating the underlying cause of the problem rather than just the symptoms.

Avoiding Common Mistakes When Using Ishikawa Diagrams

While Ishikawa Diagrams can be a useful problem-solving tool, there are some common errors that teams can make when creating and using them. Here are some errors to avoid:

• Jumping to conclusions: It is critical to avoid jumping to conclusions before identifying and evaluating all potential causes. Rushing to solutions without fully comprehending the underlying cause of the problem can result in ineffective and costly solutions.
• Excessive diagram complexity: Keep the diagram simple and focused on the problem at hand. Overcomplicating the diagram with too many branches or irrelevant information can make determining the true root cause of the problem difficult.
• Ignoring other sources of information: While Ishikawa Diagrams are a powerful tool, they should not be used as the sole source of information in problem-solving processes. Other data sources to consider include customer feedback, process data, and employee input.

Teams can effectively use Ishikawa Diagrams to identify and address the root causes of business problems by adhering to these best practises and avoiding common pitfalls.

Finally, Ishikawa Diagrams are a useful tool for solving business problems and determining the root causes of problems. Teams can effectively use Ishikawa Diagrams to find comprehensive solutions by following best practices such as clearly defining the problem, involving a diverse team, brainstorming potential causes, and prioritising root causes.

It’s critical to remember that Ishikawa diagrams should be used in conjunction with other sources of information to ensure a well-rounded approach to problem-solving. Teams can effectively leverage the power of Ishikawa diagrams in their problem-solving processes by avoiding common mistakes such as overcomplicating the diagram and jumping to conclusions.

Finally, using Ishikawa Diagrams to solve business problems can result in better processes, higher customer satisfaction, and a more efficient organisation. Teams can achieve greater success and propel their businesses forward by mastering this powerful tool.

• Ilie, G. and Ciocoiu, C.N., 2010. Application of fishbone diagram to determine the risk of an event with multiple causes .  Management research and practice ,  2 (1), pp.1-20.
• Radziwill, N., 2017. Creating ishikawa (fishbone) diagrams with R.   Software Quality Professional ,  20 (1), pp.47-48.

Daniel Croft

Daniel Croft is a seasoned continuous improvement manager with a Black Belt in Lean Six Sigma. With over 10 years of real-world application experience across diverse sectors, Daniel has a passion for optimizing processes and fostering a culture of efficiency. He's not just a practitioner but also an avid learner, constantly seeking to expand his knowledge. Outside of his professional life, Daniel has a keen Investing, statistics and knowledge-sharing, which led him to create the website learnleansigma.com, a platform dedicated to Lean Six Sigma and process improvement insights.

Getting Started with Lean Six Sigma: A Guide to Launching Your First Project

Understanding Problem Definition

Free lean six sigma templates.

Improve your Lean Six Sigma projects with our free templates. They're designed to make implementation and management easier, helping you achieve better results.

5S Floor Marking Best Practices

In lean manufacturing, the 5S System is a foundational tool, involving the steps: Sort, Set…

How to Measure the ROI of Continuous Improvement Initiatives

When it comes to business, knowing the value you’re getting for your money is crucial,…

8D Problem-Solving: Common Mistakes to Avoid

In today’s competitive business landscape, effective problem-solving is the cornerstone of organizational success. The 8D…

The Evolution of 8D Problem-Solving: From Basics to Excellence

In a world where efficiency and effectiveness are more than just buzzwords, the need for…

8D: Tools and Techniques

Are you grappling with recurring problems in your organization and searching for a structured way…

How to Select the Right Lean Six Sigma Projects: A Comprehensive Guide

Going on a Lean Six Sigma journey is an invigorating experience filled with opportunities for…

We use essential cookies to make Venngage work. By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.

Manage Cookies

Cookies and similar technologies collect certain information about how you’re using our website. Some of them are essential, and without them you wouldn’t be able to use Venngage. But others are optional, and you get to choose whether we use them or not.

Strictly Necessary Cookies

These cookies are always on, as they’re essential for making Venngage work, and making it safe. Without these cookies, services you’ve asked for can’t be provided.

Show cookie providers

• Google Login

Functionality Cookies

These cookies help us provide enhanced functionality and personalisation, and remember your settings. They may be set by us or by third party providers.

Performance Cookies

These cookies help us analyze how many people are using Venngage, where they come from and how they're using it. If you opt out of these cookies, we can’t get feedback to make Venngage better for you and all our users.

• Google Analytics

Targeting Cookies

These cookies are set by our advertising partners to track your activity and show you relevant Venngage ads on other sites as you browse the internet.

• Google Tag Manager
• Infographics
• Daily Infographics
• Popular Templates
• Accessibility
• Graphic Design
• Graphs and Charts
• Data Visualization
• Human Resources
• Beginner Guides

Blog Beginner Guides 15+ Fishbone Diagram Examples for Brainstorming Problem Causes

15+ Fishbone Diagram Examples for Brainstorming Problem Causes

Written by: Danesh Ramuthi Oct 13, 2023

The fishbone diagram, often referred to as the Ishikawa diagram or cause and effect diagram, is a powerful visualization tool that elucidates the intricate web of contributing factors behind a specific problem or issue. Characterized by its unique bone structure, it places the problem statement at the fish’s head, branching out to the various causes categorized into major segments.

The primary purpose of a fishbone diagram is to break down complex problems into understandable components, enabling team members to efficiently brainstorm and analyze causal relationships, making it indispensable in areas like quality management and root cause analysis.

Whether you’re aiming to delve deep into the causes of climate change or dissect the factors behind a the fishbone diagram provides a clear visual representation, highlighting the cause and effect relationship and underscoring the value of systematic problem solving.

For those eager to harness the potential of this great tool, Venngage offers a robust diagram maker . With customizable fishbone diagram templates , it empowers users to craft their diagrams effortlessly. These templates are meticulously designed to help you place ideas in the appropriate category, ensuring a comprehensive and organized cause and effect analysis.

Click to jump ahead:

Root cause fishbone diagram example

Cause and effect fishbone diagram example, ishikawa fishbone diagram example, medical fishbone diagram example, climate fishbone diagram example, project management fishbone diagram example, simple fishbone diagram example, how to use a fishbone diagram.

A root cause fishbone diagram, at its core, is a tool specifically tailored to identify, analyze and represent the underlying causes or root causes of a problem. Imagine a scenario where a manufacturing process has a recurring defect. 

In such a scenario, the problem statement or defect would be placed at the fish’s head. As one begins the fishbone analysis, the spine of the fish represents the main flow of the process, with smaller bones branching out. Each of these bones corresponds to a contributing factor or potential cause of the defect.

Utilizing the fishbone diagram for root cause analysis involves gathering team members for a brainstorming session. Here, the group would identify various major categories like “Machinery”, “Manpower”, “Materials”, “Methods”, etc. 

Under each of these categories, multiple factors are explored. For instance, under “Machinery”, potential causes could include outdated equipment, calibration errors or frequent breakdowns. The aim is to determine the root cause, or in some cases, multiple root causes, responsible for the defect. 

The visual representation afforded by the diagram aids in systematically breaking down the problem, ensuring no stone is left unturned.

One of the advantages of using a root cause fishbone diagram is its ability to pinpoint areas that might otherwise be overlooked. It offers a structured approach, helping teams avoid short-term fixes and instead address the deeper, underlying issues. However, it’s crucial to be aware of its disadvantages too. 

The success of the diagram heavily relies on the expertise and insights of the team members. If not all possible causes are considered, the analysis may be incomplete, leading to erroneous conclusions.

The cause and effect fishbone diagram is primarily used to map out the various causes contributing to a specific effect or outcome. For instance, consider a problem statement like “Decreased Sales in Quarter 3”. 

Placed at the head of the fish, this statement becomes the focal point of the analysis. The spine extends outwards, branching into multiple categories that could be influencing this decline.

Starting with a brainstorming session, team members can identify major categories such as “Marketing”, “Product Quality”, “External Factors”, and “Customer Service”. Under “Marketing”, for example, potential causes could be insufficient advertising, poor social media engagement, or ineffective promotional campaigns. 

The aim is to capture all the possible causes contributing to the decline in sales. Through the fishbone diagram’s structured format, teams can effectively map out the causal relationships, understanding how various factors interplay and lead to the overarching problem.

Using the cause and effect fishbone diagram offers a comprehensive overview, helping businesses or teams strategize effectively. They can prioritize areas that need urgent attention and develop strategies for improvement. 

However, like all tools, it has its disadvantages. It requires thoroughness and can become convoluted if too many minor issues are included. Thus, it’s essential to keep the diagram focused on significant, impactful causes to maintain its efficacy as a problem-solving tool.

The Ishikawa fishbone diagram or just fishbone diagram, named after its creator Kaoru Ishikawa, is a powerful visualization tool designed to map out causal relationships concerning a particular problem or issue. Its unique design, reminiscent of a fish’s skeletal structure, places the primary problem or effect at the fish’s head.

From this focal point, the “spine” of the fish extends, leading to branching “bones.” Each branch represents a category or a group of potential contributing factors that lead to the main problem. Often used in root cause analysis and quality management, the Ishikawa diagram breaks down complex issues by categorizing them into major areas such as “People”, “Processes”, “Environment” and more.

This structure allows for an organized exploration of potential causes, ensuring that various perspectives and elements related to the problem are considered.

By facilitating systematic identification and categorization of causes, the Ishikawa fishbone diagram becomes an essential tool in problem-solving and decision-making processes.

In the medical realm, the fishbone diagram finds a specialized application, offering clinicians a structured format to diagnose and understand patient conditions.

Given the critical nature of healthcare, pinpointing the root causes of medical symptoms or conditions becomes paramount. A medical fishbone diagram aids in this by visualizing potential causes related to a specific medical problem or symptom. Categories in a medical context might include “Laboratory Results”, “Patient History”, “Physical Examination Findings” and “Environmental Factors”.

Under each category, various factors or sub-causes can be listed. For instance, “Laboratory Results” could delve into specifics like electrolyte imbalances or abnormal blood cell counts.

The diagram’s visual representation ensures that healthcare professionals can comprehensively analyze patient conditions, considering multiple facets before determining a diagnosis or treatment plan. This systematic approach fosters enhanced patient care and promotes more accurate diagnostic processes.

Designed for meticulous cause and effect analysis, this fishbone diagram delves into the complex problems associated with climate change. Its visual representation, characteristic of the fish’s skeletal structure, places the overarching problem statement — for instance, “Global Warming” — at the fish’s head. From here, multiple categories branch out, representing major aspects such as “Anthropogenic Activities”, “Natural Causes” and “Economic Factors”. 

Each of these major categories further branches out to depict the specific factors contributing to the primary problem. 

The strength of the climate fishbone diagram lies in its ability to present a comprehensive overview, ensuring that all potential causes, whether they relate to deforestation, industrial emissions, or natural volcanic activities, are captured and analyzed. 

It serves as a visualization tool that aids researchers and decision-makers in crafting informed and effective strategies to combat climate-induced challenges.

In project management, where precision and systematic problem solving are paramount, the fishbone diagram finds significant utility. Project delays, cost overruns and unmet objectives often have multifaceted root causes. 

The project management fishbone diagram, an adaptation of the Ishikawa diagram, serves to identify, categorize and analyze these causes. 

Each category delineates into specific contributing factors, ensuring a thorough exploration of all potential issues. The visual format of the diagram aids team members during brainstorming sessions, facilitating the identification of challenges within the project lifecycle. 

By offering a clear visual representation of the cause and effect relationships inherent in project challenges, the project management fishbone diagram stands as an invaluable tool, helping teams to preemptively address issues, optimize processes and enhance overall project execution.

Related: How to Write a Comprehensive Project Management Plan [+ Examples]

For problems that may not be as intricate but still require structured analysis, a simple fishbone diagram becomes the tool of choice. Stripped of excessive categories and branches, the simple fishbone diagram focuses on presenting the main causes of a problem in a straightforward manner. 

Despite its simplicity, the core structure remains consistent: the primary issue or problem statement occupies the fish’s head, while a few major categories branch out from the central spine. This diagram’s strength lies in its accessibility; without delving into overly detailed branches, it offers a clear, concise visualization of the root causes and contributing factors. 

It’s particularly beneficial for quick brainstorming sessions or when introducing the concept of cause and effect analysis to those unfamiliar with the fishbone methodology. 

The simple fishbone diagram, while not exhaustive, provides a foundational framework, promoting structured thought and problem-solving in various contexts.

A fishbone diagram , also known as an Ishikawa or cause and effect diagram, provides a visual representation of potential causes leading to a particular problem or effect. 

It is a structured brainstorming tool that helps teams identify, explore and visually display the many potential causes related to a specific problem.

• Begin your fishbone diagram with the problem statement or the main effect you’re trying to understand. This is written on the right side and represents the fish’s head.
• Draw a horizontal line extending from the problem statement towards the left. This is the fish’s spine and serves as a foundation for the potential causes.
• Identify the major categories of causes. Common categories include “People”, “Processes”, “Equipment”, “Materials” and others, depending on the context. These are the primary bones branching off the central spine.
• Draw diagonal lines or “fishbones” branching off the spine for each major category.
• Under each major category, brainstorm and list down the potential contributing factors or sub-causes. These represent the smaller bones branching out from the primary bones.
• Connect these sub-causes to the respective major category lines using smaller diagonal lines.
• For causes that may have sub-components or more detailed breakdowns, further branch out from the main cause.
• Make sure to clearly label each cause and sub-cause for clarity.
• After the brainstorming session, analyze the diagram to determine the most likely root causes of the problem.
• Once complete, your fishbone diagram should offer a comprehensive visual overview of all the potential causes leading to the main problem. This structure enables teams to better understand the problem, prioritize potential causes and develop effective solutions or interventions.

Related: 10+ Types of Diagrams and How to Choose the Right One

We explored over 15 examples of fishbone diagrams to help you effectively brainstorm the causes of problems. 

This tool, with its visually intuitive structure, serves as a game-changer in analyzing root causes across various fields, from business challenges to technological snags. 

This article doesn’t just present examples but also educates readers on how to harness the power of the fishbone diagram to its fullest. 

For anyone inspired to create their own or seeking specialized templates, Venngage stands out as a go-to resource.

Explore Venngage’s diagram maker and discover an array of pre-designed fishbone diagram templates to kickstart your brainstorming sessions.

Discover popular designs

Infographic maker

Brochure maker

White paper online

Newsletter creator

Flyer maker

Timeline maker

Letterhead maker

Mind map maker

Ebook maker