problem solving tools examples

Skip to main content
Skip to primary sidebar
Skip to footer

Additional menu

Nine essential problem solving tools: The ultimate guide to finding a solution

October 26, 2023 by MindManager Blog

Problem solving may unfold differently depending on the industry, or even the department you work in. However, most agree that before you can fix any issue, you need to be clear on what it is, why it’s happening, and what your ideal long-term solution will achieve.

Understanding both the nature and the cause of a problem is the only way to figure out which actions will help you resolve it.

Given that most problem-solving processes are part inspiration and part perspiration, you’ll be more successful if you can reach for a problem solving tool that facilitates collaboration, encourages creative thinking, and makes it easier to implement the fix you devise.

The problem solving tools include three unique categories: problem solving diagrams, problem solving mind maps, and problem solving software solutions.

They include:

Fishbone diagrams
Strategy maps
Mental maps
Concept maps
Layered process audit software
Charting software
MindManager

In this article, we’ve put together a roundup of versatile problem solving tools and software to help you and your team map out and repair workplace issues as efficiently as possible.

Let’s get started!

Problem solving diagrams

Mapping your way out of a problem is the simplest way to see where you are, and where you need to end up.

Not only do visual problem maps let you plot the most efficient route from Point A (dysfunctional situation) to Point B (flawless process), problem mapping diagrams make it easier to see:

The root cause of a dilemma.
The steps, resources, and personnel associated with each possible solution.
The least time-consuming, most cost-effective options.

A visual problem solving process help to solidify understanding. Furthermore, it’s a great way for you and your team to transform abstract ideas into a practical, reconstructive plan.

Here are three examples of common problem mapping diagrams you can try with your team:

1. Fishbone diagrams

Fishbone diagrams are a common problem solving tool so-named because, once complete, they resemble the skeleton of a fish.

With the possible root causes of an issue (the ribs) branching off from either side of a spine line attached to the head (the problem), dynamic fishbone diagrams let you:

Lay out a related set of possible reasons for an existing problem
Investigate each possibility by breaking it out into sub-causes
See how contributing factors relate to one another

Fishbone diagrams are also known as cause and effect or Ishikawa diagrams.

2. Flowcharts

A flowchart is an easy-to-understand diagram with a variety of applications. But you can use it to outline and examine how the steps of a flawed process connect.

Made up of a few simple symbols linked with arrows indicating workflow direction, flowcharts clearly illustrate what happens at each stage of a process – and how each event impacts other events and decisions.

3. Strategy maps

Frequently used as a strategic planning tool, strategy maps also work well as problem mapping diagrams. Based on a hierarchal system, thoughts and ideas can be arranged on a single page to flesh out a potential resolution.

Once you’ve got a few tactics you feel are worth exploring as possible ways to overcome a challenge, a strategy map will help you establish the best route to your problem-solving goal.

Problem solving mind maps

Problem solving mind maps are especially valuable in visualization. Because they facilitate the brainstorming process that plays a key role in both root cause analysis and the identification of potential solutions, they help make problems more solvable.

Mind maps are diagrams that represent your thinking. Since many people struggle taking or working with hand-written or typed notes, mind maps were designed to let you lay out and structure your thoughts visually so you can play with ideas, concepts, and solutions the same way your brain does.

By starting with a single notion that branches out into greater detail, problem solving mind maps make it easy to:

Explain unfamiliar problems or processes in less time
Share and elaborate on novel ideas
Achieve better group comprehension that can lead to more effective solutions

Mind maps are a valuable problem solving tool because they’re geared toward bringing out the flexible thinking that creative solutions require. Here are three types of problem solving mind maps you can use to facilitate the brainstorming process.

4. Mental maps

A mental map helps you get your thoughts about what might be causing a workplace issue out of your head and onto a shared digital space.

Because mental maps mirror the way our brains take in and analyze new information, using them to describe your theories visually will help you and your team work through and test those thought models.

5. Idea maps

Idea maps let you take advantage of a wide assortment of colors and images to lay down and organize your scattered thought process. Idea maps are ideal brainstorming tools because they allow you to present and explore ideas about the best way to solve a problem collaboratively, and with a shared sense of enthusiasm for outside-the-box thinking.

6. Concept maps

Concept maps are one of the best ways to shape your thoughts around a potential solution because they let you create interlinked, visual representations of intricate concepts.

By laying out your suggested problem-solving process digitally – and using lines to form and define relationship connections – your group will be able to see how each piece of the solution puzzle connects with another.

Problem solving software solutions

Problem solving software is the best way to take advantage of multiple problem solving tools in one platform. While some software programs are geared toward specific industries or processes – like manufacturing or customer relationship management, for example – others, like MindManager , are purpose-built to work across multiple trades, departments, and teams.

Here are three problem-solving software examples.

7. Layered process audit software

Layered process audits (LPAs) help companies oversee production processes and keep an eye on the cost and quality of the goods they create. Dedicated LPA software makes problem solving easier for manufacturers because it helps them see where costly leaks are occurring and allows all levels of management to get involved in repairing those leaks.

8. Charting software

Charting software comes in all shapes and sizes to fit a variety of business sectors. Pareto charts, for example, combine bar charts with line graphs so companies can compare different problems or contributing factors to determine their frequency, cost, and significance. Charting software is often used in marketing, where a variety of bar charts and X-Y axis diagrams make it possible to display and examine competitor profiles, customer segmentation, and sales trends.

9. MindManager

No matter where you work, or what your problem-solving role looks like, MindManager is a problem solving software that will make your team more productive in figuring out why a process, plan, or project isn’t working the way it should.

Once you know why an obstruction, shortfall, or difficulty exists, you can use MindManager’s wide range of brainstorming and problem mapping diagrams to:

Find the most promising way to correct the situation
Activate your chosen solution, and
Conduct regular checks to make sure your repair work is sustainable

MindManager is the ultimate problem solving software.

Not only is it versatile enough to use as your go-to system for puzzling out all types of workplace problems, MindManager’s built-in forecasting tools, timeline charts, and warning indicators let you plan, implement, and monitor your solutions.

By allowing your group to work together more effectively to break down problems, uncover solutions, and rebuild processes and workflows, MindManager’s versatile collection of problem solving tools will help make everyone on your team a more efficient problem solver.

Download a free trial today to get started!

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

35 problem-solving techniques and methods for solving complex problems

Design your next session with SessionLab

Join the 150,000+ facilitators  using SessionLab.

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!

Design your next workshop with SessionLab

Join the 150,000 facilitators using SessionLab

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.

12 Decision-making techniques to improve team outcomes

9 Signs you’re micromanaging & how to change it

Revitalize your team with 20 key employee engagement drivers

Recognizing and tackling microaggressions at the workplace

16 Game-changing ways to build trust in a team

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

How to master the seven-step problem-solving process

In this episode of the McKinsey Podcast , Simon London speaks with Charles Conn, CEO of venture-capital firm Oxford Sciences Innovation, and McKinsey senior partner Hugo Sarrazin about the complexities of different problem-solving strategies.

Podcast transcript

Simon London: Hello, and welcome to this episode of the McKinsey Podcast , with me, Simon London. What’s the number-one skill you need to succeed professionally? Salesmanship, perhaps? Or a facility with statistics? Or maybe the ability to communicate crisply and clearly? Many would argue that at the very top of the list comes problem solving: that is, the ability to think through and come up with an optimal course of action to address any complex challenge—in business, in public policy, or indeed in life.

Looked at this way, it’s no surprise that McKinsey takes problem solving very seriously, testing for it during the recruiting process and then honing it, in McKinsey consultants, through immersion in a structured seven-step method. To discuss the art of problem solving, I sat down in California with McKinsey senior partner Hugo Sarrazin and also with Charles Conn. Charles is a former McKinsey partner, entrepreneur, executive, and coauthor of the book Bulletproof Problem Solving: The One Skill That Changes Everything [John Wiley & Sons, 2018].

Charles and Hugo, welcome to the podcast. Thank you for being here.

Hugo Sarrazin: Our pleasure.

Charles Conn: It’s terrific to be here.

Simon London: Problem solving is a really interesting piece of terminology. It could mean so many different things. I have a son who’s a teenage climber. They talk about solving problems. Climbing is problem solving. Charles, when you talk about problem solving, what are you talking about?

Charles Conn: For me, problem solving is the answer to the question “What should I do?” It’s interesting when there’s uncertainty and complexity, and when it’s meaningful because there are consequences. Your son’s climbing is a perfect example. There are consequences, and it’s complicated, and there’s uncertainty—can he make that grab? I think we can apply that same frame almost at any level. You can think about questions like “What town would I like to live in?” or “Should I put solar panels on my roof?”

You might think that’s a funny thing to apply problem solving to, but in my mind it’s not fundamentally different from business problem solving, which answers the question “What should my strategy be?” Or problem solving at the policy level: “How do we combat climate change?” “Should I support the local school bond?” I think these are all part and parcel of the same type of question, “What should I do?”

I’m a big fan of structured problem solving. By following steps, we can more clearly understand what problem it is we’re solving, what are the components of the problem that we’re solving, which components are the most important ones for us to pay attention to, which analytic techniques we should apply to those, and how we can synthesize what we’ve learned back into a compelling story. That’s all it is, at its heart.

I think sometimes when people think about seven steps, they assume that there’s a rigidity to this. That’s not it at all. It’s actually to give you the scope for creativity, which often doesn’t exist when your problem solving is muddled.

Simon London: You were just talking about the seven-step process. That’s what’s written down in the book, but it’s a very McKinsey process as well. Without getting too deep into the weeds, let’s go through the steps, one by one. You were just talking about problem definition as being a particularly important thing to get right first. That’s the first step. Hugo, tell us about that.

Hugo Sarrazin: It is surprising how often people jump past this step and make a bunch of assumptions. The most powerful thing is to step back and ask the basic questions—“What are we trying to solve? What are the constraints that exist? What are the dependencies?” Let’s make those explicit and really push the thinking and defining. At McKinsey, we spend an enormous amount of time in writing that little statement, and the statement, if you’re a logic purist, is great. You debate. “Is it an ‘or’? Is it an ‘and’? What’s the action verb?” Because all these specific words help you get to the heart of what matters.

Want to subscribe to The McKinsey Podcast ?

Simon London: So this is a concise problem statement.

Hugo Sarrazin: Yeah. It’s not like “Can we grow in Japan?” That’s interesting, but it is “What, specifically, are we trying to uncover in the growth of a product in Japan? Or a segment in Japan? Or a channel in Japan?” When you spend an enormous amount of time, in the first meeting of the different stakeholders, debating this and having different people put forward what they think the problem definition is, you realize that people have completely different views of why they’re here. That, to me, is the most important step.

Charles Conn: I would agree with that. For me, the problem context is critical. When we understand “What are the forces acting upon your decision maker? How quickly is the answer needed? With what precision is the answer needed? Are there areas that are off limits or areas where we would particularly like to find our solution? Is the decision maker open to exploring other areas?” then you not only become more efficient, and move toward what we call the critical path in problem solving, but you also make it so much more likely that you’re not going to waste your time or your decision maker’s time.

How often do especially bright young people run off with half of the idea about what the problem is and start collecting data and start building models—only to discover that they’ve really gone off half-cocked.

Hugo Sarrazin: Yeah.

Charles Conn: And in the wrong direction.

Simon London: OK. So step one—and there is a real art and a structure to it—is define the problem. Step two, Charles?

Charles Conn: My favorite step is step two, which is to use logic trees to disaggregate the problem. Every problem we’re solving has some complexity and some uncertainty in it. The only way that we can really get our team working on the problem is to take the problem apart into logical pieces.

What we find, of course, is that the way to disaggregate the problem often gives you an insight into the answer to the problem quite quickly. I love to do two or three different cuts at it, each one giving a bit of a different insight into what might be going wrong. By doing sensible disaggregations, using logic trees, we can figure out which parts of the problem we should be looking at, and we can assign those different parts to team members.

Simon London: What’s a good example of a logic tree on a sort of ratable problem?

Charles Conn: Maybe the easiest one is the classic profit tree. Almost in every business that I would take a look at, I would start with a profit or return-on-assets tree. In its simplest form, you have the components of revenue, which are price and quantity, and the components of cost, which are cost and quantity. Each of those can be broken out. Cost can be broken into variable cost and fixed cost. The components of price can be broken into what your pricing scheme is. That simple tree often provides insight into what’s going on in a business or what the difference is between that business and the competitors.

If we add the leg, which is “What’s the asset base or investment element?”—so profit divided by assets—then we can ask the question “Is the business using its investments sensibly?” whether that’s in stores or in manufacturing or in transportation assets. I hope we can see just how simple this is, even though we’re describing it in words.

When I went to work with Gordon Moore at the Moore Foundation, the problem that he asked us to look at was “How can we save Pacific salmon?” Now, that sounds like an impossible question, but it was amenable to precisely the same type of disaggregation and allowed us to organize what became a 15-year effort to improve the likelihood of good outcomes for Pacific salmon.

Simon London: Now, is there a danger that your logic tree can be impossibly large? This, I think, brings us onto the third step in the process, which is that you have to prioritize.

Charles Conn: Absolutely. The third step, which we also emphasize, along with good problem definition, is rigorous prioritization—we ask the questions “How important is this lever or this branch of the tree in the overall outcome that we seek to achieve? How much can I move that lever?” Obviously, we try and focus our efforts on ones that have a big impact on the problem and the ones that we have the ability to change. With salmon, ocean conditions turned out to be a big lever, but not one that we could adjust. We focused our attention on fish habitats and fish-harvesting practices, which were big levers that we could affect.

People spend a lot of time arguing about branches that are either not important or that none of us can change. We see it in the public square. When we deal with questions at the policy level—“Should you support the death penalty?” “How do we affect climate change?” “How can we uncover the causes and address homelessness?”—it’s even more important that we’re focusing on levers that are big and movable.

Would you like to learn more about our Strategy & Corporate Finance Practice ?

Simon London: Let’s move swiftly on to step four. You’ve defined your problem, you disaggregate it, you prioritize where you want to analyze—what you want to really look at hard. Then you got to the work plan. Now, what does that mean in practice?

Hugo Sarrazin: Depending on what you’ve prioritized, there are many things you could do. It could be breaking the work among the team members so that people have a clear piece of the work to do. It could be defining the specific analyses that need to get done and executed, and being clear on time lines. There’s always a level-one answer, there’s a level-two answer, there’s a level-three answer. Without being too flippant, I can solve any problem during a good dinner with wine. It won’t have a whole lot of backing.

Simon London: Not going to have a lot of depth to it.

Hugo Sarrazin: No, but it may be useful as a starting point. If the stakes are not that high, that could be OK. If it’s really high stakes, you may need level three and have the whole model validated in three different ways. You need to find a work plan that reflects the level of precision, the time frame you have, and the stakeholders you need to bring along in the exercise.

Charles Conn: I love the way you’ve described that, because, again, some people think of problem solving as a linear thing, but of course what’s critical is that it’s iterative. As you say, you can solve the problem in one day or even one hour.

Charles Conn: We encourage our teams everywhere to do that. We call it the one-day answer or the one-hour answer. In work planning, we’re always iterating. Every time you see a 50-page work plan that stretches out to three months, you know it’s wrong. It will be outmoded very quickly by that learning process that you described. Iterative problem solving is a critical part of this. Sometimes, people think work planning sounds dull, but it isn’t. It’s how we know what’s expected of us and when we need to deliver it and how we’re progressing toward the answer. It’s also the place where we can deal with biases. Bias is a feature of every human decision-making process. If we design our team interactions intelligently, we can avoid the worst sort of biases.

Simon London: Here we’re talking about cognitive biases primarily, right? It’s not that I’m biased against you because of your accent or something. These are the cognitive biases that behavioral sciences have shown we all carry around, things like anchoring, overoptimism—these kinds of things.

Both: Yeah.

Charles Conn: Availability bias is the one that I’m always alert to. You think you’ve seen the problem before, and therefore what’s available is your previous conception of it—and we have to be most careful about that. In any human setting, we also have to be careful about biases that are based on hierarchies, sometimes called sunflower bias. I’m sure, Hugo, with your teams, you make sure that the youngest team members speak first. Not the oldest team members, because it’s easy for people to look at who’s senior and alter their own creative approaches.

Hugo Sarrazin: It’s helpful, at that moment—if someone is asserting a point of view—to ask the question “This was true in what context?” You’re trying to apply something that worked in one context to a different one. That can be deadly if the context has changed, and that’s why organizations struggle to change. You promote all these people because they did something that worked well in the past, and then there’s a disruption in the industry, and they keep doing what got them promoted even though the context has changed.

Simon London: Right. Right.

Hugo Sarrazin: So it’s the same thing in problem solving.

Charles Conn: And it’s why diversity in our teams is so important. It’s one of the best things about the world that we’re in now. We’re likely to have people from different socioeconomic, ethnic, and national backgrounds, each of whom sees problems from a slightly different perspective. It is therefore much more likely that the team will uncover a truly creative and clever approach to problem solving.

Simon London: Let’s move on to step five. You’ve done your work plan. Now you’ve actually got to do the analysis. The thing that strikes me here is that the range of tools that we have at our disposal now, of course, is just huge, particularly with advances in computation, advanced analytics. There’s so many things that you can apply here. Just talk about the analysis stage. How do you pick the right tools?

Charles Conn: For me, the most important thing is that we start with simple heuristics and explanatory statistics before we go off and use the big-gun tools. We need to understand the shape and scope of our problem before we start applying these massive and complex analytical approaches.

Simon London: Would you agree with that?

Hugo Sarrazin: I agree. I think there are so many wonderful heuristics. You need to start there before you go deep into the modeling exercise. There’s an interesting dynamic that’s happening, though. In some cases, for some types of problems, it is even better to set yourself up to maximize your learning. Your problem-solving methodology is test and learn, test and learn, test and learn, and iterate. That is a heuristic in itself, the A/B testing that is used in many parts of the world. So that’s a problem-solving methodology. It’s nothing different. It just uses technology and feedback loops in a fast way. The other one is exploratory data analysis. When you’re dealing with a large-scale problem, and there’s so much data, I can get to the heuristics that Charles was talking about through very clever visualization of data.

You test with your data. You need to set up an environment to do so, but don’t get caught up in neural-network modeling immediately. You’re testing, you’re checking—“Is the data right? Is it sound? Does it make sense?”—before you launch too far.

Simon London: You do hear these ideas—that if you have a big enough data set and enough algorithms, they’re going to find things that you just wouldn’t have spotted, find solutions that maybe you wouldn’t have thought of. Does machine learning sort of revolutionize the problem-solving process? Or are these actually just other tools in the toolbox for structured problem solving?

Charles Conn: It can be revolutionary. There are some areas in which the pattern recognition of large data sets and good algorithms can help us see things that we otherwise couldn’t see. But I do think it’s terribly important we don’t think that this particular technique is a substitute for superb problem solving, starting with good problem definition. Many people use machine learning without understanding algorithms that themselves can have biases built into them. Just as 20 years ago, when we were doing statistical analysis, we knew that we needed good model definition, we still need a good understanding of our algorithms and really good problem definition before we launch off into big data sets and unknown algorithms.

Simon London: Step six. You’ve done your analysis.

Charles Conn: I take six and seven together, and this is the place where young problem solvers often make a mistake. They’ve got their analysis, and they assume that’s the answer, and of course it isn’t the answer. The ability to synthesize the pieces that came out of the analysis and begin to weave those into a story that helps people answer the question “What should I do?” This is back to where we started. If we can’t synthesize, and we can’t tell a story, then our decision maker can’t find the answer to “What should I do?”

Simon London: But, again, these final steps are about motivating people to action, right?

Charles Conn: Yeah.

Simon London: I am slightly torn about the nomenclature of problem solving because it’s on paper, right? Until you motivate people to action, you actually haven’t solved anything.

Charles Conn: I love this question because I think decision-making theory, without a bias to action, is a waste of time. Everything in how I approach this is to help people take action that makes the world better.

Simon London: Hence, these are absolutely critical steps. If you don’t do this well, you’ve just got a bunch of analysis.

Charles Conn: We end up in exactly the same place where we started, which is people speaking across each other, past each other in the public square, rather than actually working together, shoulder to shoulder, to crack these important problems.

Simon London: In the real world, we have a lot of uncertainty—arguably, increasing uncertainty. How do good problem solvers deal with that?

Hugo Sarrazin: At every step of the process. In the problem definition, when you’re defining the context, you need to understand those sources of uncertainty and whether they’re important or not important. It becomes important in the definition of the tree.

You need to think carefully about the branches of the tree that are more certain and less certain as you define them. They don’t have equal weight just because they’ve got equal space on the page. Then, when you’re prioritizing, your prioritization approach may put more emphasis on things that have low probability but huge impact—or, vice versa, may put a lot of priority on things that are very likely and, hopefully, have a reasonable impact. You can introduce that along the way. When you come back to the synthesis, you just need to be nuanced about what you’re understanding, the likelihood.

Often, people lack humility in the way they make their recommendations: “This is the answer.” They’re very precise, and I think we would all be well-served to say, “This is a likely answer under the following sets of conditions” and then make the level of uncertainty clearer, if that is appropriate. It doesn’t mean you’re always in the gray zone; it doesn’t mean you don’t have a point of view. It just means that you can be explicit about the certainty of your answer when you make that recommendation.

Simon London: So it sounds like there is an underlying principle: “Acknowledge and embrace the uncertainty. Don’t pretend that it isn’t there. Be very clear about what the uncertainties are up front, and then build that into every step of the process.”

Hugo Sarrazin: Every step of the process.

Simon London: Yeah. We have just walked through a particular structured methodology for problem solving. But, of course, this is not the only structured methodology for problem solving. One that is also very well-known is design thinking, which comes at things very differently. So, Hugo, I know you have worked with a lot of designers. Just give us a very quick summary. Design thinking—what is it, and how does it relate?

Hugo Sarrazin: It starts with an incredible amount of empathy for the user and uses that to define the problem. It does pause and go out in the wild and spend an enormous amount of time seeing how people interact with objects, seeing the experience they’re getting, seeing the pain points or joy—and uses that to infer and define the problem.

Simon London: Problem definition, but out in the world.

Hugo Sarrazin: With an enormous amount of empathy. There’s a huge emphasis on empathy. Traditional, more classic problem solving is you define the problem based on an understanding of the situation. This one almost presupposes that we don’t know the problem until we go see it. The second thing is you need to come up with multiple scenarios or answers or ideas or concepts, and there’s a lot of divergent thinking initially. That’s slightly different, versus the prioritization, but not for long. Eventually, you need to kind of say, “OK, I’m going to converge again.” Then you go and you bring things back to the customer and get feedback and iterate. Then you rinse and repeat, rinse and repeat. There’s a lot of tactile building, along the way, of prototypes and things like that. It’s very iterative.

Simon London: So, Charles, are these complements or are these alternatives?

Charles Conn: I think they’re entirely complementary, and I think Hugo’s description is perfect. When we do problem definition well in classic problem solving, we are demonstrating the kind of empathy, at the very beginning of our problem, that design thinking asks us to approach. When we ideate—and that’s very similar to the disaggregation, prioritization, and work-planning steps—we do precisely the same thing, and often we use contrasting teams, so that we do have divergent thinking. The best teams allow divergent thinking to bump them off whatever their initial biases in problem solving are. For me, design thinking gives us a constant reminder of creativity, empathy, and the tactile nature of problem solving, but it’s absolutely complementary, not alternative.

Simon London: I think, in a world of cross-functional teams, an interesting question is do people with design-thinking backgrounds really work well together with classical problem solvers? How do you make that chemistry happen?

Hugo Sarrazin: Yeah, it is not easy when people have spent an enormous amount of time seeped in design thinking or user-centric design, whichever word you want to use. If the person who’s applying classic problem-solving methodology is very rigid and mechanical in the way they’re doing it, there could be an enormous amount of tension. If there’s not clarity in the role and not clarity in the process, I think having the two together can be, sometimes, problematic.

The second thing that happens often is that the artifacts the two methodologies try to gravitate toward can be different. Classic problem solving often gravitates toward a model; design thinking migrates toward a prototype. Rather than writing a big deck with all my supporting evidence, they’ll bring an example, a thing, and that feels different. Then you spend your time differently to achieve those two end products, so that’s another source of friction.

Now, I still think it can be an incredibly powerful thing to have the two—if there are the right people with the right mind-set, if there is a team that is explicit about the roles, if we’re clear about the kind of outcomes we are attempting to bring forward. There’s an enormous amount of collaborativeness and respect.

Simon London: But they have to respect each other’s methodology and be prepared to flex, maybe, a little bit, in how this process is going to work.

Hugo Sarrazin: Absolutely.

Simon London: The other area where, it strikes me, there could be a little bit of a different sort of friction is this whole concept of the day-one answer, which is what we were just talking about in classical problem solving. Now, you know that this is probably not going to be your final answer, but that’s how you begin to structure the problem. Whereas I would imagine your design thinkers—no, they’re going off to do their ethnographic research and get out into the field, potentially for a long time, before they come back with at least an initial hypothesis.

Want better strategies? Become a bulletproof problem solver

Hugo Sarrazin: That is a great callout, and that’s another difference. Designers typically will like to soak into the situation and avoid converging too quickly. There’s optionality and exploring different options. There’s a strong belief that keeps the solution space wide enough that you can come up with more radical ideas. If there’s a large design team or many designers on the team, and you come on Friday and say, “What’s our week-one answer?” they’re going to struggle. They’re not going to be comfortable, naturally, to give that answer. It doesn’t mean they don’t have an answer; it’s just not where they are in their thinking process.

Simon London: I think we are, sadly, out of time for today. But Charles and Hugo, thank you so much.

Charles Conn: It was a pleasure to be here, Simon.

Hugo Sarrazin: It was a pleasure. Thank you.

Simon London: And thanks, as always, to you, our listeners, for tuning into this episode of the McKinsey Podcast . If you want to learn more about problem solving, you can find the book, Bulletproof Problem Solving: The One Skill That Changes Everything , online or order it through your local bookstore. To learn more about McKinsey, you can of course find us at McKinsey.com.

Charles Conn is CEO of Oxford Sciences Innovation and an alumnus of McKinsey’s Sydney office. Hugo Sarrazin is a senior partner in the Silicon Valley office, where Simon London, a member of McKinsey Publishing, is also based.

Explore a career with us

Strategy to beat the odds

Five routes to more innovative problem solving

The Ultimate Guide to Problem Solving Tools

Ossian Muscad
March 10, 2022
No Comments

Last Updated on February 29, 2024 by Ossian Muscad

Every business, regardless of its industry, encounters the inevitable challenge of problem-solving. This critical aspect of business operations is often multifaceted, whether it’s in the process of anticipating potential obstacles, addressing immediate issues at hand, or refining systems for improved efficiency. The intricate and often time-intensive nature of solving these problems demands not only a systematic approach but also the right set of tools to navigate the complexities effectively.

Problem-solving tools are, therefore, not just useful but essential for any business professional. This guide delves into the intricacies of these tools, equipping you with the necessary understanding and skills to employ them within your organizational context. From the nuances of selecting the appropriate tool for a specific challenge to the strategic implementation for maximum impact, we offer a comprehensive exploration into the world of problem-solving tools designed to streamline and enhance your decision-making processes.

What are Problem Solving Tools?

Problem-solving tools are structured methodologies or frameworks designed to aid individuals and organizations in navigating the complexities of various challenges. They offer a systematic way to deconstruct and comprehend issues, thereby empowering you to tackle each component with clarity and strategic insight. These tools serve as a kind of compass in the intricate maze of decision-making, providing a step-by-step guide to dissect problems and identify their underlying causes.

By enabling focused brainstorming, these methodologies help in the generation and assessment of potential resolutions, ensuring that the execution of solutions is not only strategic but also monitored for effectiveness. Diverse in their application, problem-solving tools adapt to a range of scenarios, each with its distinct intricacies and nuances. They encourage a proactive approach to conflict resolution, fostering a mindset geared towards continual improvement and preemptive action.

Utilizing visual aids like charts or diagrams, these tools can chart the most efficient path from a problem-ridden present to a solution-oriented future, mapping out the journey from dysfunction to functional success in a clear and accessible manner.

Common Problem Solving Tools and Diagrams

A visual problem-solving process will help reinforce your understanding of the issue and is an excellent way for you and your team to convert abstract ideas into an actual, reconstructive plan. With that said, here are six examples of common problem-mapping diagrams that you can try:

Fishbone Diagram

The Fishbone Diagram , also known as the Cause-and-effect Diagram or the Ishikawa diagram , is a powerful problem-solving tool that visually maps out the potential causes of an issue. Its distinctive shape resembles the skeleton of a fish, where the “head” represents the problem and the “bones” branching out from the “spine” symbolize different categories of root causes.

Each of these categories, such as Methods, Equipment, People, and Materials, is probed to identify possible contributing factors to the problem at hand. The simplicity and effectiveness of the Ishikawa diagram lie in its ability to facilitate comprehensive brainstorming sessions based on the principle of cause and effect.

With its widespread popularity, teams across industries value this type of diagram for its ease of use and its competence in stimulating the identification and analysis of various potential causes for a problem. Fishbone diagrams are versatile tools that can be applied in numerous situations. Here’s a comprehensive list detailing common uses:

Root Cause Analysis in Manufacturing : Identifying the root causes of defects or product quality issues, often drilling down to factors in the production process.
Service Industry Problem-Solving : Pinpointing causes of customer complaints or service bottlenecks, leading to more effective service delivery.
Healthcare Error Analysis : Analyzing medical errors or healthcare process inefficiencies, aiming to improve patient care and safety.
Product Development : Exploring potential issues in new product design and development phases, ensuring all possible flaws are addressed.
Business Process Improvement : Examining processes within a business to identify inefficiencies or recurrent problems, which can then be systematically eliminated.
Marketing Analysis : Understanding complex challenges within marketing campaigns, such as low engagement rates or poor customer feedback.
Human Resources Issues : Addressing issues relating to staff, such as absenteeism, low morale, or high turnover, with an aim to enhance employee satisfaction and retention.

Flowcharts are among the most prevalent and straightforward problem-solving tools utilized across various industries due to their visual representation of processes or systems. They consist of shapes and arrows that designate sequential steps, illustrating the flow from one stage to another. This visual mapping allows individuals and teams to follow a problem from initiation to resolution, providing a bird’s-eye view of the entire process.

The primary advantage of employing a flowchart lies in its capacity to lay out each step in a predictable manner, thereby enabling the observer to identify bottlenecks, redundancies, or inefficiencies within any step. By using flowcharts, you can dissect complex processes into manageable parts, ensuring a more precise understanding of how each component interacts with others.

This comprehensive perspective not only aids in pinpointing where the issues arise but also enhances the potential for optimizing different segments of the workflow to achieve a more efficient, streamlined process. Flowcharts are a universal tool used to break down complex processes and illustrate step-by-step sequences. Common uses for flowcharts that span across various disciplines include, but are not limited to:

Process Documentation : For capturing and communicating the steps involved in a process within an organization, ensuring consistency and clarity.
Troubleshooting Guides : A diagnostic tool to guide users through a series of decisions to resolve a problem or understand a complex scenario.
Operational Improvement : To identify inefficiencies or bottlenecks in operational processes and pinpoint areas for improvement or simplification.
Educational Tool : Utilized in teaching to explain complex topics in a visual, step-by-step manner that is easier for students to follow and understand.
Decision Making : Aids individuals and businesses by mapping out the possible routes and outcomes of a decision, making the decision-making process clearer and more informed.
Quality Management : Helps in ensuring compliance with quality standards by outlining the process flow and establishing critical control points.
System Design : In systems engineering, it represents the interactions and flow between various system components or subsystems.
Project Management : Project managers often use flowcharts to plan and monitor the stages of a project, ensuring that each phase transitions smoothly into the next.

Strategy Maps

Strategy Maps are a frequently used tool for strategic planning within companies, but they also hold significant value in problem-solving tasks. The essence of a strategy map is to illustrate the connections among various aspects of the organization, such as objectives, measures, initiatives, and activities. These diagrams provide a visual representation of how each component supports the overarching goals and serve as a guide to understanding which areas require attention in order to solve a problem. There are three main types of strategy maps:

Cause-and-effect maps : Demonstrating the relationships between different strategic objectives. Each objective is linked by arrows that show how one influences another, creating a network of cause-and-effect connections.
Objective Maps : Focused on detailing the primary objectives of the organization and outlining the necessary measures and initiatives to achieve each one.
Balanced Scorecard Maps : They correspond to the Balanced Scorecard framework and display the organization’s strategy balanced across four perspectives: Financial, Customer, Internal Processes, and Learning & Growth.

While each type of map has its specific applications and nuances, the underlying premise remains constant: to provide a comprehensive view of the strategic interdependencies within an organization. In doing so, strategy maps facilitate the identification of areas where resources can be optimized or where shifts in strategy may resolve existing problems.

Strategy Maps enable leaders and teams to align their efforts toward a common goal and to comprehend how changes in one segment of the business can ripple through and impact the organization as a whole. Strategy Maps are incredibly versatile and can be applied to a number of uses within an organization to enhance strategic understanding and alignment. Below is a detailed list of the common uses of Strategy Maps:

Vision and Strategy Communication : Strategy Maps articulate an organization’s vision and strategy across various levels, ensuring all employees understand how their roles contribute to the broader objectives.
Aligning Initiatives : They align projects and initiatives with strategic objectives, ensuring that each effort is coherent with the overall direction of the company.
Performance Analysis : These maps facilitate performance measurement against strategic goals, allowing companies to track progress and make informed adjustments.
Business Unit Synchronization : They offer a holistic view that aids in synchronizing efforts across different business units or departments, fostering an integrated approach to achieving strategic goals.
Strategic Discussion and Decision Making : Strategy Maps stimulate discussion among executives and managers, providing a framework for strategic decision-making and problem-solving.
Identifying and Closing Gaps : They help identify gaps in strategy execution and provide a structured way of developing initiatives to close those gaps.
Facilitating Strategy Review and Planning Sessions : Strategy Maps are used during strategy review meetings and planning sessions to reflect on strategic performance and plan for future periods.

The 5 Whys is a problem-solving method developed by Sakichi Toyoda and later used within Toyota Motor Corporation during its manufacturing process improvements. It is a simple yet effective technique used to uncover the root cause of a problem by asking “Why?” a minimum of five times or until the underlying issue is identified.

The process involves a team collaboratively pinpointing an issue and then questioning the cause of that issue iteratively. This exercise forces deeper inquiry beyond surface-level symptoms, leading to the discovery of the fundamental problem at hand. By addressing the root cause, organizations can implement substantive, long-term solutions rather than temporary fixes.

The 5 Whys technique is versatile and can be applied in various industries and scenarios, making it a staple in the toolbox of lean manufacturing, quality management, and process improvement. The 5 Whys technique has a multitude of applications across different fields and industries due to its simplicity and effectiveness in root cause analysis. Here is a comprehensive list detailing seven common uses of the 5 Whys:

Problem-Solving in Manufacturing : Applied to identify the root cause of defects or production issues, contributing to improved product quality and process optimization.
Safety Incident Analysis : Used to dissect the series of events leading to a safety incident, allowing organizations to implement measures that prevent future occurrences.
Healthcare Error Reduction : Helps in understanding the underlying causes of errors in medical procedures or patient care, aiming to enhance patient safety and care quality.
IT Troubleshooting : Assists in diagnosing the core issues in IT service disruptions or system failures, ensuring more reliable and efficient technological infrastructures.
Business Process Improvement : Employs the technique to delve into inefficiencies or bottlenecks in business operations, resulting in streamlined processes and reduced operational costs.
Customer Experience Enhancement : Identifies the fundamental reasons behind customer complaints or dissatisfaction, leading to better service and elevated customer satisfaction levels.
Environmental Sustainability : Applied to analyze the root causes of environmental impact within an operation, informing strategies for more sustainable business practices.

Pareto Charts

Pareto charts are statistical tools named after the Italian economist Vilfredo Pareto, who is best known for the Pareto Principle. This principle, also known as the 80/20 rule, posits that for many events, roughly 80% of the effects come from 20% of the causes. A Pareto Chart conveys this concept through a visual graph that combines both bar and line graphs.

The bars represent individual values in descending order from left to right and are typically related to frequency or cost. Next to these, a line graph indicates the cumulative total, enabling users to easily identify which factors contribute the most to the problem they are examining. Pareto Charts are especially useful in quality control and process improvement because they help stakeholders prioritize issues or defects in a process.

By concentrating efforts on the most significant problems, organizations can significantly improve their overall performance, often with considerably less effort than by treating all problems equally. Pareto Charts are widely recognized for their ability to visually represent and prioritize problems to focus improvement efforts. Here are seven common uses of Pareto Charts across various disciplines:

Quality Control in Manufacturing : Helps identify the most frequent defects or errors in the manufacturing process, allowing prioritization and allocation of resources to tackle the issues that will have the greatest impact on quality improvement.
Customer Feedback Analysis : By categorizing and ranking customer complaints or feedback, businesses can focus on resolving the problems that affect the largest number of customers or those that have the most severe impact on customer satisfaction.
Inventory Management : The use of Pareto Charts can highlight the small proportion of items that often constitute the bulk of an inventory’s value, enabling better stock optimization and cost savings.
Sales Analysis : Assists companies in determining their most profitable products or services, as well as their most valuable customers, thus guiding more effective sales and marketing strategies.
Health and Safety : Identifies the most common causes of accidents or health incidents in the workplace, leading to targeted interventions that can improve worker safety and reduce the risk of future incidents.
Operational Bottlenecks : Pinpoints the few critical bottlenecks in operational processes that cause the majority of delays or inefficiencies, allowing for focused process improvement efforts.
Financial Analysis : Enables businesses to target the most significant cost drivers or the areas where spending is greatest, promoting more strategic financial management and cost reduction measures.

Decision Trees

A decision tree is a flowchart-like structure that is used as a decision support tool, representing a series of decisions and their possible consequences, including chance event outcomes, resource costs, and utility. It’s a visual representation that maps out multiple decision paths and evaluates them based on various scenarios, which can be immensely beneficial in making informed choices in complex situations.

Decision trees feature branches that depict decision nodes and leaf nodes representing outcomes, allowing individuals or organizations to review all possible solutions and identify the best course of action before committing. This analytical tool is widely used across business, engineering, law, and medical fields due to its straightforward graphical approach, which promotes clarity in the decision-making process.

Decision Trees are versatile tools, and their application can be found in diverse areas. By exploring different scenarios and their potential outcomes, you can uncover hidden insights and make more informed decisions. Here are some common uses of Decision Trees:

Strategic Business Decisions : Enables businesses to visually map out various strategic choices and assess potential outcomes and risks, leading to well-informed decisions.
Project Management : Assists managers in anticipating potential project challenges and outcomes, allowing for proactive mitigation strategies and better allocation of resources.
Finance and Investment : Used by investors to evaluate different investment opportunities and scenarios, aiding in the risk assessment and decision-making process.
Operations Research : Helps determine optimal operational decisions based on various conditional and probabilistic scenarios, improves efficiency, and reduces costs.
Marketing Analysis : Allows marketers to understand customer behavior and segment markets, facilitating targeted marketing campaigns and customer relationship management.
Medical Diagnosis and Treatment Planning : Helps healthcare providers in assessing the probability of diseases based on symptoms and deciding on the best treatment plans.
Machine Learning and Data Mining : Provides algorithms that assist in classification and regression tasks, making predictions based on data patterns.

Objective Map

An objective map is a strategic tool utilized by companies to visualize their objectives and the connections between them. This graphical illustration aids in clarifying how various goals relate to one another and often reveals how addressing one objective can influence the achievement of others.

By mapping out objectives in a clear and structured way, an objective map enables team members and stakeholders to gain insight into the hierarchy and interdependencies of their collective goals. It’s particularly valuable when trying to solve complex problems within an organization, as it helps to pinpoint which objectives need to be prioritized and tackled in order to address and resolve specific challenges effectively.

This visual mapping can become a critical step in strategic planning, ensuring that efforts are directed toward the most impactful areas. Objective Maps are crucial in a multitude of organizational processes. Here are seven common uses:

Strategic Planning : Assists organizations in identifying their primary goals and exploring secondary objectives that support them. By understanding the impact and relationship between different aims, companies can better allocate resources to critical areas.
Performance Management : Helps translate organizational goals into employee performance metrics, ensuring individual objectives are aligned with the company’s vision and mission.
Process Improvement : Provides a framework to identify processes that are directly tied to strategic goals, which can be optimized for better efficiency and results.
Product Development : Clarifies the objectives surrounding a product’s features, market fit, and customer needs, making it a valuable tool in prioritizing development milestones.
Change Management : Aids in visualizing the objectives tied to organizational change, helping stakeholders see the bigger picture and the key goals that change initiatives support.
Resource Allocation : By clarifying which objectives are most critical, Objective Maps guide decision-makers in allocating budget, personnel, and other resources more effectively.
Risk Management : Facilitates the identification of goals that could be impacted by potential risks, allowing for a proactive approach to mitigating threats to the organization’s objectives.

Balanced Scorecard Map

A Balanced Scorecard Map is a strategic planning and management tool that provides a visual representation of an organization’s performance measures and objectives across different perspectives. It brings together financial, customer, internal, and growth-related goals in a coherent manner, articulating how the organization creates value.

By identifying key performance indicators (KPIs) and targets within these areas, the map serves as a guide to translate a company’s vision into actionable goals. It allows managers and teams to understand at a glance how various objectives tie into overall corporate strategy and how they contribute to resolving organizational issues.

With its clear, graphical design, a Balanced Scorecard Map can highlight specific areas that require attention to drive improvement and achieve strategic balance. Balanced Scorecard Maps are used widely across various industries to enhance strategic alignment and improve organizational performance. Here is a comprehensive list detailing their common uses:

Strategic Alignment & Execution : Aligns the day-to-day work that everyone is doing with strategy, making sure that projects, initiatives, and daily activities all move in the same direction as the organization’s strategic objectives.
Performance Measurement : Goes beyond financial metrics to include valuable KPIs concerning customers, internal processes, and learning and growth, thus providing a more ‘balanced’ view of organizational performance.
Communication of Strategy : Acts as a vehicle to communicate the organization’s strategy internally and externally clearly and concisely, ensuring that everyone understands the strategic priorities and how their roles impact them.
Linking Rewards to Performance Metrics : Ties performance management to KPIs and strategic goals, which can inform compensation and reward systems that motivate employees to support and achieve these goals.
Strategic Feedback & Learning : Provides a structured feedback system for monitoring, analyzing, and reviewing strategic performance and results, promoting continuous improvement and strategic learning within the organization.
Prioritization of Projects & Investments : Helps prioritize projects and investments based on how they align with and impact strategic objectives, ensuring that resources are allocated to the most strategically relevant initiatives.
Organizational Development & Change Management : Facilitates organizational growth and adaptation by linking change management initiatives to long-term strategic objectives, helping manage transformation and development in a strategic context.

No matter what type of problem you’re facing, there’s a diagram that can help you solve it. Therefore, by understanding the different types of diagrams and how to use them, you’ll need to prepare for any issue that comes your way.

How to Choose the Ideal Problem-Solving Tool?

Choosing the ideal problem-solving tool largely depends on the nature of the problem and its complexity. Here are some steps you can follow to select the most suitable tool:

Define the Problem: Before you choose a tool, you need to understand the problem clearly. What is the issue you’re trying to solve? What are its effects?
Identify the Nature of the Problem: Is the problem simple, complicated, or complex? Simple problems have predictable solutions, while complicated ones may require expert knowledge or detailed analysis. Complex problems involve many interconnected parts and are best approached by understanding those connections and their effects.
Consider the Level of Analysis Required: Some problems can be solved with a simple root cause analysis . In contrast, others may require more in-depth analysis, such as a SWOT or PESTEL analysis.
Identify the Resources Available: Some tools require specific resources or software. Ensure you have access to these resources before choosing a tool.
Consider Your Team’s Familiarity with the Tool: If your team is already familiar with a particular tool, it might be advantageous to use it. If not, you’ll need to consider whether there will be a learning curve and if sufficient time and resources are available for training.
Evaluate the Tool: Once you have chosen a tool, use it to solve the problem. Then, evaluate the effectiveness of the tool. Did it help solve the problem? Was it easy to use? Did it save time and resources?

The goal is not just to solve the problem but to learn from the process. This learning can be applied to future problem-solving efforts, continuously improving your approach.

Frequently Asked Questions (FAQs)

Q1: what differentiates a simple problem from a complex one in problem-solving.

Simple problems usually have a clear and predictable solution, whereas complex problems have many interconnected components that change dynamically and may require holistic and flexible approaches to solve. By understanding the nature of the problem, you can choose a suitable tool for effective problem-solving.

Q2: How frequently should I review and update the problem-solving tools used in my organization?

Review and update your problem-solving tools as needed when there is a significant change in the organization’s objectives or market conditions or when feedback or results indicate an improvement is warranted. Make sure your tools are aligned with your current strategy and goals to ensure their effectiveness.

Q3: Can one problem-solving tool be used for all types of problems?

Not typically. Problem-solving tools are varied and designed to address specific types of issues. It’s crucial to match the right tool to the problem to ensure an effective solution. At the same time, some tools may be adaptable and useful for multiple types of problems.

Q4: What should I do if a selected problem-solving tool does not yield the expected results?

If the tool isn’t working, it’s essential to re-evaluate the situation, possibly redefining the problem or choosing a different tool that may be better suited to the circumstances. That way, you can find a solution that is more likely to yield the expected results. If necessary, seek guidance or assistance from experts in the field to help identify a suitable tool and approach.

Q5: Is collaboration always beneficial when using problem-solving tools?

Collaborative problem-solving can foster diverse ideas and lead to innovative solutions. However, the situation and type of problem should guide the necessity and extent of collaboration. By understanding these factors, you can choose the most effective problem-solving approach and tool for your organization’s needs.

Q6: How important is it to be trained in multiple problem-solving tools?

Proficiency in various tools allows for flexibility and adaptability in tackling different problems. Continuous learning and training in multiple methodologies can significantly improve problem-solving effectiveness. Making sure your team is well-versed in various tools can also increase their confidence and competence in addressing complex issues. So, it’s beneficial to invest in training and development programs that expose individuals to a variety of problem-solving approaches and tools.

Streamline Problem-Solving Processes with DATAMYTE

DATAMYTE is a quality management platform with low-code capabilities. Our Digital Clipboard , in particular, is a low-code workflow automation software that features a workflow, checklist, and smart form builder. This tool lets you build and deploy custom solutions for problem-solving, quality control, data collection, and analysis without any programming knowledge.

DATAMYTE also lets you conduct layered process audits, a high-frequency evaluation of critical process steps, focusing on areas with the highest failure risk or non-compliance. Conducting LPA with DATAMYTE lets you effectively identify and correct potential defects before they become major quality issues.

With DATAMYTE , you have an all-in-one solution for efficient and effective problem-solving, quality management, and continuous improvement. Book a demo now to learn more.

The art of problem-solving necessitates a careful evaluation of the problem, consideration of the tools and resources available, and a sound understanding of your organization’s capabilities. Whether the problem at hand is simple, complicated, or complex, the key lies in matching the right problem-solving tool to the task.

Regular review and adaptation of tools, coupled with a readiness to embrace training and collaboration, bolsters the problem-solving process. Through an iterative and informed approach to problem-solving, it is possible to enhance decision-making, drive continuous improvement, and achieve strategic organizational goals.

How to Simplify Layered Process Audits
Top 7 Best Calibration Management Software in 2024

Implementation
Case-Studies
White Papers
Knowledge Base

Experts in the Connected Factory

1-800-455-4359
(763) 553-0455 ext. 1
[email protected]

How it works

For Business

Join Mind Tools

Article • 11 min read

Getting to the Root of a Problem Quickly

By the Mind Tools Content Team

5 Whys Root-Cause Analysis

Have you ever had a problem that refused to go away? No matter what you did, sooner or later it would return, perhaps in another form.

Stubborn or recurrent problems are often symptoms of deeper issues. "Quick fixes" may seem convenient, but they often solve only the surface issues and waste resources that could otherwise be used to tackle the real cause.

In this article and in the video, below, we look at the 5 Whys technique (sometimes known as 5Y). This is a simple but powerful tool for cutting quickly through the outward symptoms of a problem to reveal its underlying causes – so that you can deal with it once and for all.

Origins of the 5 Whys Technique

Sakichi Toyoda, the Japanese industrialist, inventor, and founder of Toyota Industries, developed the 5 Whys technique in the 1930s. It became popular in the 1970s, and Toyota still uses it to solve problems today.

Toyota has a "go and see" philosophy. This means that its decision making is based on an in-depth understanding of what's actually happening on the shop floor , rather than on what someone in a boardroom thinks might be happening.

The 5 Whys technique is true to this tradition, and it is most effective when the answers come from people who have hands-on experience of the process or problem in question.

The method is remarkably simple: when a problem occurs, you drill down to its root cause by asking "Why?" five times. Then, when a counter-measure becomes apparent, you follow it through to prevent the issue from recurring.

The 5 Whys uses "counter-measures," rather than "solutions." A counter-measure is an action or set of actions that seeks to prevent the problem from arising again, while a solution may just seek to deal with the symptom. As such, counter-measures are more robust, and will more likely prevent the problem from recurring.

When to Use a 5 Whys Analysis

You can use 5 Whys for troubleshooting, quality improvement, and problem solving, but it is most effective when used to resolve simple or moderately difficult problems.

It may not be suitable if you need to tackle a complex or critical problem. This is because 5 Whys can lead you to pursue a single track, or a limited number of tracks, of inquiry when, in fact, there could be multiple causes. In cases like these, a wider-ranging method such as Cause and Effect Analysis or Failure Mode and Effects Analysis may b e more effective.

This simple 5 Whys technique, however, can often direct you quickly to the root cause of a problem. So, whenever a system or process isn't working properly, give it a try before you embark on a more in-depth approach – and certainly before you attempt to develop a solution.

The tool's simplicity gives it great flexibility, too, and 5 Whys combines well with other methods and techniques, such as Root Cause Analysis . It is often associated with Lean Manufacturing , where it is used to identify and eliminate wasteful practices. It is also used in the analysis phase of the Six Sigma quality improvement methodology.

How to Use the 5 Whys

The model follows a very simple seven-step process: [1]

1. Assemble a Team

Gather together people who are familiar with the specifics of the problem, and with the process that you're trying to fix. Include someone to act as a facilitator , who can keep the team focused on identifying effective counter-measures.

2. Define the Problem

If you can, observe the problem in action. Discuss it with your team and write a brief, clear problem statement that you all agree on. For example, "Team A isn't meeting its response time targets" or "Software release B resulted in too many rollback failures."

Then, write your statement on a whiteboard or sticky note, leaving enough space around it to add your answers to the repeated question, "Why?"

3. Ask the First "Why?"

Ask your team why the problem is occurring. (For example, "Why isn't Team A meeting its response time targets?")

Asking "Why?" sounds simple, but answering it requires serious thought. Search for answers that are grounded in fact: they must be accounts of things that have actually happened, not guesses at what might have happened.

This prevents 5 Whys from becoming just a process of deductive reasoning, which can generate a large number of possible causes and, sometimes, create more confusion as you chase down hypothetical problems.

Your team members may come up with one obvious reason why, or several plausible ones. Record their answers as succinct phrases, rather than as single words or lengthy statements, and write them below (or beside) your problem statement. For example, saying "volume of calls is too high" is better than a vague "overloaded."

4. Ask "Why?" Four More Times

For each of the answers that you generated in Step 3, ask four further "whys" in succession. Each time, frame the question in response to the answer you've just recorded.

What Is a 5 Whys Template?

The diagram, below, shows an example of 5 Whys in action, following a single lane of inquiry.

Figure 1: 5 Whys Example (Single Lane)

The 5 Whys method also allows you to follow multiple lanes of inquiry. An example of this is shown in Figure 2, below.

In our example, asking "Why was the delivery late?" produces a second answer (Reason 2). Asking "Why?" for that answer reveals a single reason (Reason 1), which you can address with a counter-measure.

Similarly, asking "Why did the job take longer than expected?" has a second answer (Reason 2), and asking "Why?" at this point reveals a single reason (Reason 1). Another "Why?" here identifies two possibilities (Reasons 1 and 2) before a possible counter-measure becomes evident.

There is also a second reason for "Why we ran out of printer ink" (Reason 2), and a single answer for the next "Why?" (Reason 1), which can then be addressed with a counter-measure.

Figure 2: 5 Whys Example (Multiple Lanes)

Step 5. Know When to Stop

You'll know that you've revealed the root cause of the problem when asking "why" produces no more useful responses, and you can go no further. An appropriate counter-measure or process change should then become evident. (As we said earlier, if you're not sure that you've uncovered the real root cause, consider using a more in-depth problem-solving technique like Cause and Effect Analysis , Root-Cause Analysis , or FMEA .)

If you identified more than one reason in Step 3, repeat this process for each of the different branches of your analysis until you reach a root cause for each one.

6. Address the Root Cause(s)

Now that you've identified at least one root cause, you need to discuss and agree on the counter-measures that will prevent the problem from recurring.

7. Monitor Your Measures

Keep a close watch on how effectively your counter-measures eliminate or minimize the initial problem. You may need to amend them, or replace them entirely. If this happens, it's a good idea to repeat the 5 Whys process to ensure that you've identified the correct root cause.

Appreciation

A similar question-based approach known as "appreciation" can help you to uncover factors in a situation that you might otherwise miss.

It was originally developed by the military to assist commanders in gaining a comprehensive understanding of any fact, problem or situation. But you can also apply it in the workplace.

Starting with a fact, you first ask the question, "So what?" – in other words, what are the implications of that fact? Why is this fact important?

You then continue asking that question until you've drawn all possible conclusions from it.

The major difference between this and the 5 Whys technique is that appreciation is often used to get the most information out of a simple fact or statement, while 5 Whys is designed to drill down to the root of a problem.

Tips for Using the 5 Whys Technique

Try to move quickly from one question to the next. That way, you'll have the full picture before you jump to any conclusions.
The "5" in 5 Whys is really just a " rule of thumb ." In some cases, you may need to ask "Why?" a few more times before you get to the root of the problem. In other cases, you may reach this point before you ask your fifth "Why?" If you do, make sure that you haven't stopped too soon, and that you're not simply accepting "knee-jerk" responses.
Know when to stop! The important point is to stop asking "Why?" when you stop producing useful responses.

Frequently Asked Questions About 5 Whys

1. what is the 5 whys technique.

The 5 Whys Technique is a problem-solving method involving repeatedly asking "why?" It's a way of quickly getting to the root cause of a situation.

2. Who Invented 5 Whys?

The 5 Whys technique was invented in the 1930s by Sakichi Toyoda, the Japanese industrialist, inventor, and founder of Toyota Industries.

5 Whys Infographic

See our infographic on the 5 Whys and use it to get to the root of your problems!

Bear in mind that appreciation can restrict you to one line of thinking. For instance, once you've answered your first "So what?" question, you might follow a single line of inquiry to its conclusion. To avoid this, repeat the appreciation process several times over to make sure that you've covered all bases.

The 5 Whys strategy is a simple, effective tool for uncovering the root of a problem. You can use it in troubleshooting, problem-solving, and quality-improvement initiatives.

Start with a problem and ask why it is occurring. Make sure that your answer is grounded in fact, and then ask the question again. Continue the process until you reach the root cause of the problem, and you can identify a counter-measure that will prevent it from recurring.

Bear in mind that this questioning process is best suited to simple or moderately difficult problems. Complex problems may benefit from a more detailed approach, although using 5 Whys will still give you useful insights.

[1] Pojasek, R. (2000). 'Asking "Why?" Five Times,' Environmental Quality Management , Volume 10, Issue 1, 79–84. Available here . [Accessed July 1, 2022.]

You've accessed 1 of your 2 free resources.

Get unlimited access

Discover more content

Root cause analysis.

Tracing a Problem to Its Origins

Using Root Cause Analysis

Find the Root of Your Problems

Add comment

Comments (0)

Be the first to comment!

Get 20% off your first year of Mind Tools

Our on-demand e-learning resources let you learn at your own pace, fitting seamlessly into your busy workday. Join today and save with our limited time offer!

Sign-up to our newsletter

Subscribing to the Mind Tools newsletter will keep you up-to-date with our latest updates and newest resources.

Subscribe now

Business Skills

Personal Development

Leadership and Management

Member Extras

Discover something new today

Pain points podcast - what is ai.

Exploring Artificial Intelligence

Pain Points Podcast - How Do I Get Organized?

It's Time to Get Yourself Sorted!

How Emotionally Intelligent Are You?

Boosting Your People Skills

Self-Assessment

What's Your Leadership Style?

Learn About the Strengths and Weaknesses of the Way You Like to Lead

Recommended for you

Professionalism.

Meeting the Standards That Matter

Business Operations and Process Management

Strategy Tools

Customer Service

Business Ethics and Values

Handling Information and Data

Project Management

Knowledge Management

Self-Development and Goal Setting

Time Management

Presentation Skills

Learning Skills

Career Skills

Communication Skills

Negotiation, Persuasion and Influence

Working With Others

Difficult Conversations

Creativity Tools

Self-Management

Work-Life Balance

Stress Management and Wellbeing

Coaching and Mentoring

Change Management

Team Management

Managing Conflict

Delegation and Empowerment

Performance Management

Leadership Skills

Developing Your Team

Talent Management

Problem Solving

Decision Making

Member Podcast

SUGGESTED TOPICS
The Magazine
Newsletters
Managing Yourself
Managing Teams
Work-life Balance
The Big Idea
Data & Visuals
Reading Lists
Case Selections
HBR Learning
Topic Feeds
Account Settings
Email Preferences

How to Solve Problems

Laura Amico

To bring the best ideas forward, teams must build psychological safety.

Teams today aren’t just asked to execute tasks: They’re called upon to solve problems. You’d think that many brains working together would mean better solutions, but the reality is that too often problem-solving teams fall victim to inefficiency, conflict, and cautious conclusions. The two charts below will help your team think about how to collaborate better and come up with the best solutions for the thorniest challenges.

Laura Amico is a former senior editor at Harvard Business Review.

Partner Center

A Step-by-Step Guide to A3 Problem Solving Methodology
Learn Lean Sigma
Problem Solving

Problem-solving is an important component of any business or organization. It entails identifying, analyzing, and resolving problems in order to improve processes, drive results, and foster a culture of continuous improvement. A3 Problem solving is one of the most effective problem-solving methodologies.

A3 Problem solving is a structured and systematic approach to problem-solving that originated with the lean manufacturing methodology. It visualizes the problem-solving process using a one-page document known as an A3 report. The A3 report provides an overview of the problem, data analysis, root causes, solutions, and results in a clear and concise manner.

A3 Problem Solving has numerous advantages, including improved communication, better decision-making, increased efficiency, and reduced waste. It is a powerful tool for businesses of all sizes and industries, and it is especially useful for solving complex and multi-faceted problems.

In this blog post, we will walk you through the A3 Problem Solving methodology step by step. Whether you are new to A3 Problem Solving or simply want to improve your skills, this guide will help you understand and apply the process in your workplace.

What is a3 problem solving.

A3 Problem Solving is a structured and systematic approach to problem-solving that makes use of a one-page document called an A3 report to visually represent the process. The A3 report provides an overview of the problem, data analysis, root causes, solutions, and results in a clear and concise manner. The method was created within the framework of the Lean manufacturing methodology and is based on the principles of continuous improvement and visual management.

Looking for a A3 Problem solving template? Click here

Origin and History of A3 Problem Solving

A3 Problem Solving was developed by Toyota Motor Corporation and was first used in the manufacture of automobiles. The term “A3” refers to the size of the paper used to create the report, which is an ISO standard known as “A3”. The goal of the A3 report is to provide a visual representation of the problem-solving process that all members of the organisation can easily understand and share. A3 Problem Solving has been adopted by organisations in a variety of industries over the years, and it has become a widely used and recognised method for problem-solving.

Key Principles of A3 Problem Solving

The following are the key principles of A3 Problem Solving:

Define the problem clearly and concisely
Gather and analyze data to gain a deep understanding of the problem
Identify the root causes of the problem
Develop and implement effective solutions
Evaluate results and continuously improve

These principles serve as the foundation of the A3 Problem Solving methodology and are intended to assist organisations in continuously improving and achieving their objectives. Organizations can effectively solve problems, identify areas for improvement, and drive results by adhering to these principles.

Step 1: Define the Problem

Importance of clearly defining the problem.

The first step in the A3 Problem Solving process is critical because it lays the groundwork for the remaining steps. To define the problem clearly and accurately, you must first understand the problem and identify the underlying root cause. This step is critical because if the problem is not correctly defined, the rest of the process will be based on incorrect information, and the solution developed may not address the issue effectively.

The significance of defining the problem clearly cannot be overstated. It aids in the collection and analysis of relevant data, which is critical for developing effective solutions. When the problem is clearly defined, the data gathered is more relevant and targeted, resulting in a more comprehensive understanding of the issue. This will enable the development of solutions that are more likely to be effective because they are founded on a thorough and accurate understanding of the problem.

However, if the problem is not clearly defined, the data gathered may be irrelevant or incorrect, resulting in incorrect conclusions and ineffective solutions. Furthermore, the process of collecting and analysing data can become time-consuming and inefficient, resulting in resource waste. Furthermore, if the problem is not accurately defined, the solutions developed may fail to address the root cause of the problem, resulting in ongoing issues and a lack of improvement.

Techniques for Defining the Problem

The first step in the A3 Problem Solving process is to clearly and accurately define the problem. This is an important step because a clearly defined problem will help to ensure that the appropriate data is collected and solutions are developed. If the problem is not clearly defined, incorrect data may be collected, solutions that do not address the root cause of the problem, and time and resources may be wasted.

A problem can be defined using a variety of techniques, including brainstorming , root cause analysis , process mapping , and Ishikawa diagrams . Each of these techniques has its own advantages and disadvantages and can be used in a variety of situations depending on the nature of the problem.

Best Practice for Defining the Problem

In addition to brainstorming, root cause analysis, process mapping, and Ishikawa diagram s, best practices should be followed when defining a problem in A3 Problem Solving. Among these best practices are:

Define the issue in a specific and quantifiable way: It is critical to be specific and concise when defining the problem, as well as to quantify the problem in terms of its impact. This will help to ensure that all stakeholders understand the problem and that data collection is focused on the right areas.
Focus on the problem’s root cause: The A3 Problem Solving methodology is intended to assist organisations in identifying and addressing the root cause of a problem, rather than just the symptoms. Organizations can ensure that their solutions are effective and long-lasting by focusing on the root cause of the problem.
Ascertain that all stakeholders agree on the problem’s definition: All stakeholders must agree on the definition of the problem for the A3 Problem Solving process to be effective. This ensures that everyone is working towards the same goal and that the solutions developed are relevant and appropriate.
Consider the problem’s impact on the organisation and its stakeholders: It is critical to consider the impact of the problem on the organisation and its stakeholders when defining it. This will assist in ensuring that the appropriate data is gathered and that the solutions developed are relevant and appropriate.

Organizations can ensure that their problem is defined in a way that allows for effective data collection, analysis, and solution development by following these best practices. This will aid in the development of appropriate solutions and the effective resolution of the problem, resulting in improvements in the organization’s processes and outcomes.

Step 2: Gather Data

Gathering data in a3 problem solving.

Data collection is an important step in the A3 Problem Solving process because it allows organisations to gain a thorough understanding of the problem they are attempting to solve. This step entails gathering pertinent information about the problem, such as data on its origin, impact, and any related factors. This information is then used to help identify root causes and develop effective solutions.

One of the most important advantages of data collection in A3 Problem Solving is that it allows organisations to identify patterns and trends in data, which can be useful in determining the root cause of the problem. This information can then be used to create effective solutions that address the problem’s root cause rather than just its symptoms.

In A3 Problem Solving, data collection is a collaborative effort involving all stakeholders, including those directly impacted by the problem and those with relevant expertise or experience. Stakeholders can ensure that all relevant information is collected and that the data is accurate and complete by working together.

Overall, data collection is an important step in the A3 Problem Solving process because it serves as the foundation for effective problem-solving. Organizations can gain a deep understanding of the problem they are attempting to solve and develop effective solutions that address its root cause by collecting and analysing relevant data.

Data Collection Methods

In A3 Problem Solving, several data collection methods are available, including:

Observations
Process diagrams

The best data collection method will be determined by the problem being solved and the type of data required. To gain a complete understanding of the problem, it is critical to use multiple data collection methods.

Tools for Data Analysis and Visualization

Once the data has been collected, it must be analysed and visualised in order to gain insights into the problem. This process can be aided by the following tools:

Excel Spreadsheets
Flow diagrams
Pareto diagrams
Scatter Plots
Control diagrams

These tools can assist in organising data and making it easier to understand. They can also be used to generate visual representations of data, such as graphs and charts, to communicate the findings to others.

Finally, the data collection and analysis step is an important part of the A3 Problem Solving process. Organizations can gain a better understanding of the problem and develop effective solutions by collecting and analysing relevant data.

Step 3: Identify Root Causes

Identifying the root causes of the problem is the third step in the A3 Problem Solving process. This step is critical because it assists organisations in understanding the root causes of a problem rather than just its symptoms. Once the underlying cause of the problem is identified, it can be addressed more effectively, leading to more long-term solutions.

Overview of the Root Cause Analysis Process

The process of determining the underlying causes of a problem is known as root cause analysis. This process can assist organisations in determining why a problem is occurring and what can be done to prevent it from recurring in the future. The goal of root cause analysis is to identify the underlying cause of a problem rather than just its symptoms, allowing it to be addressed more effectively.

To understand Root cause analysis in more detail check out RCA in our Lean Six Sigma Yellow Belt Course Root Cause Analysis section

Techniques for Identifying Root Causes

There are several techniques for determining the root causes of a problem, including:

Brainstorming
Ishikawa diagrams (also known as fishbone diagrams)
Root Cause Tree Analysis

These methods can be used to investigate the issue in-depth and identify potential root causes. Organizations can gain a deeper understanding of the problem and identify the underlying causes that must be addressed by using these techniques.

Best Practices for Conducting Root Cause Analysis

It is critical to follow these best practices when conducting root cause analysis in A3 Problem Solving:

Make certain that all stakeholders participate in the root cause analysis process.
Concentrate on determining the root cause of the problem rather than just its symptoms.
Take into account all potential root causes, not just the most obvious ones.
To identify root causes, use a systematic approach, such as the 5 Whys or root cause tree analysis.

Organizations can ensure that root cause analysis is carried out effectively and that the root cause of the problem is identified by adhering to these best practises. This will aid in the development of appropriate solutions and the effective resolution of the problem.

Step 4: Develop Solutions

Developing solutions is the fourth step in the A3 Problem Solving process. This entails generating ideas and options for dealing with the problem, followed by selecting the best solution. The goal is to develop a solution that addresses the root cause of the problem and prevents it from recurring.

Solution Development in A3 Problem Solving

A3 solution development Problem solving is an iterative process in which options are generated and evaluated. The data gathered in the previous steps, as well as the insights and understanding gained from the root cause analysis, guide this process. The solution should be based on a thorough understanding of the problem and address the underlying cause.

Techniques for Developing Solutions

There are several techniques that can be used to develop solutions in A3 Problem Solving, including:

Brainwriting
Solution matrix
Multi voting
Force field analysis

These techniques can help to generate a range of options and to select the best solution.

Best Practice for Developing Solutions

It is critical to follow the following best practices when developing solutions in A3 Problem Solving:

Participate in the solution development process with all stakeholders.
Make certain that the solution addresses the underlying cause of the problem.
Make certain that the solution is feasible and achievable.
Consider the solution’s impact on the organisation and its stakeholders.

Organizations can ensure that the solutions they develop are effective and sustainable by adhering to these best practises. This will help to ensure that the problem is addressed effectively and that it does not reoccur.

Step 5: Implement Solutions

The final and most important step in the A3 Problem Solving methodology is solution implementation. This is the stage at which the identified and developed solutions are put into action to address the problem. This step’s goal is to ensure that the solutions are effective, efficient, and long-lasting.

The implementation Process

The implementation process entails putting the solutions developed in the previous step into action. This could include changes to processes, procedures, and systems, as well as employee training and education. To ensure that the solutions are effective, the implementation process should be well-planned and meticulously executed.

Techniques for Implementing Solutions

A3 Problem Solving solutions can be implemented using a variety of techniques, including:

Piloting the solution on a small scale before broadening its application
Participating in the implementation process with all relevant stakeholders
ensuring that the solution is in line with the goals and objectives of the organisation
Monitoring the solution to determine its effectiveness and make any necessary changes

Best Practice for Implementing Solutions

It is critical to follow these best practices when implementing solutions in A3 Problem Solving:

Make certain that all relevant stakeholders are involved and supportive of the solution. Have a clear implementation plan that outlines the steps, timeline, and resources required. Continuously monitor and evaluate the solution to determine its efficacy and make any necessary changes. Encourage all stakeholders to communicate and collaborate openly. Organizations can ensure that solutions are effectively implemented and problems are effectively addressed by adhering to these best practices. The ultimate goal is to find a long-term solution to the problem and improve the organization’s overall performance.

In conclusion, A3 Problem Solving is a comprehensive and structured methodology for problem-solving that can be applied in various industries and organisations. The A3 Problem Solving process’s five steps – Define the Problem, Gather Data, Identify Root Causes, Develop Solutions, and Implement Solutions – provide a road map for effectively addressing problems and making long-term improvements.

Organizations can improve their problem-solving skills and achieve better results by following the key principles, techniques, and best practices outlined in this guide. As a result, both the organisation and its stakeholders will benefit from increased efficiency, effectiveness, and satisfaction. So, whether you’re an experienced problem solver or just getting started, consider incorporating the A3 Problem Solving methodology into your work and start reaping the benefits right away.

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.

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…

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)

Problem Solving: Practical Tools and Techniques

Experiential Education

When solving problems, dig at the roots instead of just hacking at the leaves. Anthony J. D'Angelo

What will you learn?

An introduction to problem solving
The different stages of problem solving
Tools and techniques for defining problems, finding causes, and coming up with solutions
How to do an action plan

Introduction

Effective problem solving often requires you to collect, process, analyse and evaluate information to find a solution/s. Along with other transferable skills like communication, planning and organisation, teamwork, critical thinking, digital literacy, and active inquiry (for example), it is essential in work and life more generally.

There are a few different stages in the problem solving process, which makes it a little more complicated than it probably sounds. For example, you first have to define the problem, then collect more information about it and do some research and investigations into causes. After that, you need to process the material to understand it, and then analyse and evaluate it (whilst generating possible solutions along the way). The final solution/s and action plan then come from there.

Stages in the Problem Solving Process

There are various stages to problem solving. We have described those that we see as key in the process, starting with recognising the problem to begin with and defining and labelling it; through to solving it, evaluating it and planning for contingencies. In connection with this, we have introduced certain problem solving tools and techniques that can be used at each stage. This is because some methods work better at different stages than others. The methods are presented in more detail in the section following this one, titled ‘Tools of the Trade’.

So, what are the key stages in the problem solving process?

Problem Recognition – determining what the problem is
Labelling the problem
Conducting a problem-cause analysis
Optional solutions
Making a decision based on the best options you have generated
Developing an action plan to solve the problem
Evaluating and monitoring your solution to the problem
Contingency planning and resource examination

Problem Recognition

This first stage is where you identify the symptoms. You look for facts and analyse data, as well as explore history and human factors such as attitudes, values and reactions (soft data). Symptom identification can be achieved through collecting all kinds of data, including through interviews and focus groups, brainstorming and mind mapping. More on these methods can be found later in this module.

Define and label the Problem (and determine causes)It is important to have a clear definition of the problem otherwise the solutions generated will not work. This is because the solutions you come up with will not necessarily address the actual problem (i.e. ‘the real problem’ or ‘key stone’). For example, if you define the problem as being poor performance by employees, when in fact it is a lack of training or high expectations, the solutions generated to address the problem are unlikely to be effective.

In this stage, it is good to write down some problem statements. Begin by noting the problem and why it is important to solve. Consider the benefits to solving the problem (e.g. costs, consumer satisfaction, employee wellbeing, time, product quality).

Work out stakeholders (both internal and external) and who all the members of the team are. In regards to the problem, think through - who, what, where, when, how and why.

Find the root cause of the problem (do not be caught on symptoms otherwise you won’t find the real issue).

The tools we recommend to help you define the problem and determine the cause (including the root cause) are:

The 5W’s (and the 5 WHY’s)

SWOT Analysis

Mind mapping, brainstorming.

The Fishbone Diagram (or Cause and Effect Diagram)

Affinity Mapping

To explore some of these further, see below under ‘Tools of the Trade’.

Generate Ideas and Solutions

After defining the problem and finding the root cause, you need to generate ideas and solutions. This usually happens through brainstorming and mind mapping. These are good techniques for generating ideas quickly (and just getting it all down).

These methods help to generate thought not only around problem statements, definitions or causes (in stage one) but about potential solutions, impacts, and much more. These techniques are more concerned with ‘quantity’ in terms of getting as many ideas as possible, rather than ‘quality’. You can also do a force-field analysis in this stage or positive and negative analysis.

Students interested in watch in a lecture on critical thinking and problem solving in the context of agriculture can watch the following video:

Critical thinking and Problem solving | 19:08 mins

To explore brainstorming and mind mapping, please see below under ‘Tools of the Trade’.

Decide on the Best Solution

Once you have generated optimal solutions, you then need to make some decisions about what to choose. There are many decision-making tools that can be used. Some of these include:

Brainstorming.
Elimination – In business a process of elimination and selection of the best solution.
Weighting of consequences – you can select as solution and then weigh up all the consequences or outcomes from that solution.
Prioritising - You may have several solutions with good outcomes but you wish to select the best.

Take Action

Once you arrived at your solution to your problem, an action plan should be developed. Elements to include in your action plan could be a series of questions. There are no hard and fast rules on what to include in your action plan. However, it must be highly effective in solving the problem or problems. It must be well thought through, achievable and highly relevant to your business.

Some elements to include in your plan may be:

What is to be done?
How is it to be done?
Who is responsible?
When will it be done by?

This section of the module provides some detail on problem solving tools – and when to use them. Not all possible tools are described but we have tried to include those that are often used in business/enterprise.

The 5W’s and the 5 WHY’s

The 5W’s approach is most useful when defining the problem and then later on when identifying if more data or analysis is required.

In most cases, you can define a problem by noting:

SWOT analysis is a strategic planning tool that is used to generate information on which rigorous, logical, defendable decision can be based. As the diagram highlights, SWOT stands for Strengths, Weaknesses, Opportunities and Threats.

To complete a SWOT Analysis for your business/company/enterprise or workplace, start with asking the following questions:

What advantages (e.g. location, resources, facilities, etc.) does your enterprise have?
What do you do better than anyone else?
What make your enterprise unique? (Think about costs, resources, facilities or geographical locations etc. you identified above.)
In addition, view your strengths by placing yourself in your competitor’s shoes?

Weaknesses:

What would you need to do to improve in your enterprise?
What would you avoid doing in your enterprise or what to improve in your enterprises position?
View your weaknesses, by placing yourself in your competitor’s shoes? What are your weaknesses?
What aspects of your enterprise is costing you sales?

Opportunities:

What are the best opportunities for your enterprise to improve?
What are the future trends emerging in your industry, and how aware of these are you?
These may be new technology and changes in markets internationally or nationally.
Consumers consumption patterns may be changing based on perceived healthy, clean, safe, environmentally produced practices.
Governments (international and domestic) may change policies related to your enterprise activities.
Social patterns, population profiles, lifestyle changes and demographics etc. may change.
Operating environments (Social, Economic, Environmental) in which your enterprise operates may be changing.
What impediments, obstacles and barriers does your enterprise face in its operating environment?
Are your competitors changing their practices and their mode of operation?
Are the food safety, quality standards, or specifications under which your enterprise operates (work place health and safety, labour force costs and tax requirement etc.), or the products changing due to consumer demands or government policies locally, state wide, nationally and internationally?
Is globalisation, communications and changes technology threatening your enterprises position to remain sustainable, viable and grow?
Management of your enterprise (Human Resources, Material Resources, Financial Resources etc.)?
What is your true economic situation (cash flows, capital investment, bad debts etc/)?
What is your social standing and position in the industry?
What is your environmental situation (pollution, chemical usage, fertiliser, irrigation etc.) and your industry position?
What factors can seriously threaten your enterprise and threaten your operating practices?

To explore SWOT Analysis further (and to find blank templates to use) please follow this link to a module on SWOT Analysis

Mind mapping is an effective means to brainstorm and collect your thoughts. A mind map is a diagram that visually organises information and involves writing down a central theme/concept and thinking of new and related ideas which radiate out from the centre.

By focussing on key ideas written down in your own words and looking for connections between them, you can map knowledge in a way that will help you better understand and retain information.

To see an example from the contemporary issues and sustainability unit, look below. You will see a mind map by Dr Nissen of economic, environmental and social issues that enterprises may face (and various strategies and plans that can be used to sustainably manage these issues). The map shows you a way of viewing how to undertake the process. It is best to produce a mind map that is suited to your own agricultural enterprise.

Find more on Mind Mapping here including examples.

Brainstorming is a popular group problem-solving technique.

A desktop search of definitions of brainstorming revealed that it is typically referred to as a technique for:

Group thinking sessions (where all ideas are collected)
Stimulating creative thinking
Spontaneous participation
Group problem-solving (around a specific question or challenge)
Generating new ideas or creative solutions (drawing on lateral thinking/thinking outside the box)
Ensuring all ideas are captured and nothing is criticised or critiqued until the later analysis stage

If you are interested in exploring the method of brainstorming beyond this brief description, please follow this link to a short module on Brainstorming .

The Fishbone

A fishbone analysis is often useful for trying to organise information generated from a root cause analysis, brainstorming or mind mapping exercise. You input this information into a fishbone diagram i.e. a picture of a fish where you write the main problem in the head, then record causes in the spines. The best way to do this is to write the problem as a statement or question and then add to the backbones of the fish with potential causes. The picture below provides an example of what a fishbone diagram looks like.

For other examples and access to fishbone templates, please click here .

GoLeanSixSigma also have a great Excel tool for fishbone diagrams:

After you have undertaken the initial research on a topic, affinity mapping is a useful strategy to visualise and categorise this information. It is an effective and dynamic way of recording the qualitative and quantitative data you have collected such as on-site observations and interviews. The first step to affinity mapping involves documenting your findings on separate sticky notes, followed by grouping them according to topics (e.g. trends, challenges, themes) and then categorising them with headings. Be prepared to move your sticky notes around; affinity mapping is a dynamic process.

Pokars, S. 1989. Systematic Problem Solving and Decision Making. The Viability Group, Inc. USA.

Porter, M. E. 1979 How competitive forces shape strategy, Harvard Business Review, vol. 59, no. 2, pp. 137-145.

Porter, M. E. 2008. The five forces that shape strategy. Harvard Business Review, vol. 88, pp. 78-93

< https://globaldigitalcitizen.org/critical-thinking-skills-cheatsheet-infographic >.

Created with Shorthand, the visual storytelling platform

Our Mission

3 Simple Strategies to Improve Students’ Problem-Solving Skills

These strategies are designed to make sure students have a good understanding of problems before attempting to solve them.

Research provides a striking revelation about problem solvers. The best problem solvers approach problems much differently than novices. For instance, one meta-study showed that when experts evaluate graphs , they tend to spend less time on tasks and answer choices and more time on evaluating the axes’ labels and the relationships of variables within the graphs. In other words, they spend more time up front making sense of the data before moving to addressing the task.

While slower in solving problems, experts use this additional up-front time to more efficiently and effectively solve the problem. In one study, researchers found that experts were much better at “information extraction” or pulling the information they needed to solve the problem later in the problem than novices. This was due to the fact that they started a problem-solving process by evaluating specific assumptions within problems, asking predictive questions, and then comparing and contrasting their predictions with results. For example, expert problem solvers look at the problem context and ask a number of questions:

What do we know about the context of the problem?
What assumptions are underlying the problem? What’s the story here?
What qualitative and quantitative information is pertinent?
What might the problem context be telling us? What questions arise from the information we are reading or reviewing?
What are important trends and patterns?

As such, expert problem solvers don’t jump to the presented problem or rush to solutions. They invest the time necessary to make sense of the problem.

Now, think about your own students: Do they immediately jump to the question, or do they take time to understand the problem context? Do they identify the relevant variables, look for patterns, and then focus on the specific tasks?

If your students are struggling to develop the habit of sense-making in a problem- solving context, this is a perfect time to incorporate a few short and sharp strategies to support them.

3 Ways to Improve Student Problem-Solving

1. Slow reveal graphs: The brilliant strategy crafted by K–8 math specialist Jenna Laib and her colleagues provides teachers with an opportunity to gradually display complex graphical information and build students’ questioning, sense-making, and evaluating predictions.

For instance, in one third-grade class, students are given a bar graph without any labels or identifying information except for bars emerging from a horizontal line on the bottom of the slide. Over time, students learn about the categories on the x -axis (types of animals) and the quantities specified on the y -axis (number of baby teeth).

The graphs and the topics range in complexity from studying the standard deviation of temperatures in Antarctica to the use of scatterplots to compare working hours across OECD (Organization for Economic Cooperation and Development) countries. The website offers a number of graphs on Google Slides and suggests questions that teachers may ask students. Furthermore, this site allows teachers to search by type of graph (e.g., scatterplot) or topic (e.g., social justice).

2. Three reads: The three-reads strategy tasks students with evaluating a word problem in three different ways . First, students encounter a problem without having access to the question—for instance, “There are 20 kangaroos on the grassland. Three hop away.” Students are expected to discuss the context of the problem without emphasizing the quantities. For instance, a student may say, “We know that there are a total amount of kangaroos, and the total shrinks because some kangaroos hop away.”

Next, students discuss the important quantities and what questions may be generated. Finally, students receive and address the actual problem. Here they can both evaluate how close their predicted questions were from the actual questions and solve the actual problem.

To get started, consider using the numberless word problems on educator Brian Bushart’s site . For those teaching high school, consider using your own textbook word problems for this activity. Simply create three slides to present to students that include context (e.g., on the first slide state, “A salesman sold twice as much pears in the afternoon as in the morning”). The second slide would include quantities (e.g., “He sold 360 kilograms of pears”), and the third slide would include the actual question (e.g., “How many kilograms did he sell in the morning and how many in the afternoon?”). One additional suggestion for teams to consider is to have students solve the questions they generated before revealing the actual question.

3. Three-Act Tasks: Originally created by Dan Meyer, three-act tasks follow the three acts of a story . The first act is typically called the “setup,” followed by the “confrontation” and then the “resolution.”

This storyline process can be used in mathematics in which students encounter a contextual problem (e.g., a pool is being filled with soda). Here students work to identify the important aspects of the problem. During the second act, students build knowledge and skill to solve the problem (e.g., they learn how to calculate the volume of particular spaces). Finally, students solve the problem and evaluate their answers (e.g., how close were their calculations to the actual specifications of the pool and the amount of liquid that filled it).

Often, teachers add a fourth act (i.e., “the sequel”), in which students encounter a similar problem but in a different context (e.g., they have to estimate the volume of a lava lamp). There are also a number of elementary examples that have been developed by math teachers including GFletchy , which offers pre-kindergarten to middle school activities including counting squares , peas in a pod , and shark bait .

Students need to learn how to slow down and think through a problem context. The aforementioned strategies are quick ways teachers can begin to support students in developing the habits needed to effectively and efficiently tackle complex problem-solving.

IMAGES

Problem-Solving Strategies: Definition and 5 Techniques to Try
Developing Problem-Solving Skills for Kids
Digital Tools To Teach Problem Solving
10 Problem Solving Skills Examples: How To Improve
Digital Tools To Teach Problem Solving
What is A3 Problem Solving tool ?

VIDEO

How to Deal with Deception from Jordan Peterson #success
Problem Solving Techniques
Problem Solving Method & Checklist: Sample Problem
Multi voting|8M Tools|Problem solving tools|8 Management Tools|8M Tools
Authoring tools l
Problem solving tools

COMMENTS

9 essential problem solving tools: the ultimate guide
Problem solving software is the best way to take advantage of multiple problem solving tools in one platform. While some software programs are geared toward specific industries or processes - like manufacturing or customer relationship management, for example - others, like MindManager , are purpose-built to work across multiple trades ...
35 problem-solving techniques and methods for solving complex problems
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.
10 Problem-solving strategies to turn challenges on their head
2. Break the problem down. Identifying the problem allows you to see which steps need to be taken to solve it. First, break the problem down into achievable blocks. Then, use strategic planning to set a time frame in which to solve the problem and establish a timeline for the completion of each stage. 3.
What is Problem Solving? Steps, Process & Techniques
Finding a suitable solution for issues can be accomplished by following the basic four-step problem-solving process and methodology outlined below. Step. Characteristics. 1. Define the problem. Differentiate fact from opinion. Specify underlying causes. Consult each faction involved for information. State the problem specifically.
Effective Problem-Solving Tools: Definition and Examples
Problem-solving tools refer to strategies that can help determine the cause of a problem and identify the best solutions available. The first step in addressing an issue at work is to outline your objectives. Once you establish the cause, you can isolate variables that can help contribute to a potential solution.
14 Effective Problem-Solving Strategies
14 types of problem-solving strategies. Here are some examples of problem-solving strategies you can practice using to see which works best for you in different situations: 1. Define the problem. Taking the time to define a potential challenge can help you identify certain elements to create a plan to resolve them.
Practical Problem Solving Tools for Factory and Office
For example, the PDCA planning phase covers the first three steps in DMAIC and the first five steps in A3 and 8D. Of all those processes, there are two that stick out, that all others are based on - PDCA and 8D - they are therefore considered the "mother" and "father" of practical problem solving tools used today.
36 Problem-solving techniques, methods and tools
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.
What Is Problem Solving?
The first step in solving a problem is understanding what that problem actually is. You need to be sure that you're dealing with the real problem - not its symptoms. For example, if performance in your department is substandard, you might think that the problem lies with the individuals submitting work. However, if you look a bit deeper, the ...
How to master the seven-step problem-solving process
When we do problem definition well in classic problem solving, we are demonstrating the kind of empathy, at the very beginning of our problem, that design thinking asks us to approach. When we ideate—and that's very similar to the disaggregation, prioritization, and work-planning steps—we do precisely the same thing, and often we use ...
Problem-Solving Strategies: Definition and 5 Techniques to Try
In insight problem-solving, the cognitive processes that help you solve a problem happen outside your conscious awareness. 4. Working backward. Working backward is a problem-solving approach often ...
The Ultimate Guide to Problem Solving Tools
Common Problem Solving Tools and Diagrams. A visual problem-solving process will help reinforce your understanding of the issue and is an excellent way for you and your team to convert abstract ideas into an actual, reconstructive plan. With that said, here are six examples of common problem-mapping diagrams that you can try: Fishbone Diagram
5 Whys
The 5 Whys strategy is a simple, effective tool for uncovering the root of a problem. You can use it in troubleshooting, problem-solving, and quality-improvement initiatives. Start with a problem and ask why it is occurring. Make sure that your answer is grounded in fact, and then ask the question again.
How to Solve Problems
How to Solve Problems. To bring the best ideas forward, teams must build psychological safety. Teams today aren't just asked to execute tasks: They're called upon to solve problems. You'd ...
9 Essential Problem Solving Tools: The Ultimate Guide
Problem solving software is the best way to take advantage of multiple problem solving tools in one platform. While some software programs are geared toward specific industries or processes - like manufacturing or customer relationship management, for example - others, like MindManager , are purpose-built to work across multiple trades ...
7 Powerful Problem-Solving Root Cause Analysis Tools
Manufacturers have a variety of problem-solving tools at hand. However, they need to know when to use which tool in a manner that is appropriate for the situation. In this article, we discuss 7 tools including: ... It will cover where else in your quality management system root cause analysis can be used and will give examples of some of the ...
A Step-by-Step Guide to A3 Problem Solving Methodology
The following are the key principles of A3 Problem Solving: Define the problem clearly and concisely. Gather and analyze data to gain a deep understanding of the problem. Identify the root causes of the problem. Develop and implement effective solutions.
What is Problem Solving? (Steps, Techniques, Examples)
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 ...
Experiential Education: Problem Solving Tools and Techniques
The tools we recommend to help you define the problem and determine the cause (including the root cause) are: The 5W's (and the 5 WHY's) SWOT Analysis. Mind Mapping. Brainstorming. The Fishbone Diagram (or Cause and Effect Diagram) Affinity Mapping. To explore some of these further, see below under 'Tools of the Trade'.
50 Problem-Solving and Critical Thinking Examples
These skills enable individuals to analyze complex situations, make informed decisions, and find innovative solutions. Here, we present 25 examples of problem-solving and critical thinking. problem-solving scenarios to help you cultivate and enhance these skills. Ethical dilemma: A company faces a situation where a client asks for a product ...
Workplace Problem-Solving Examples: Real Scenarios, Practical Solutions
Problem-solving in the workplace is a complex and multifaceted skill that requires a combination of analytical thinking, creativity, and effective communication. It goes beyond simply identifying problems and extends to finding innovative solutions that address the root causes. Essential Problem-Solving Skills for the Workplace
What is 8D? Eight Disciplines Problem Solving Process
The eight disciplines (8D) model is a problem solving approach typically employed by quality engineers or other professionals, and is most commonly used by the automotive industry but has also been successfully applied in healthcare, retail, finance, government, and manufacturing. The purpose of the 8D methodology is to identify, correct, and ...
26 Good Examples of Problem Solving (Interview Answers)
Examples of Problem Solving Scenarios in the Workplace. Correcting a mistake at work, whether it was made by you or someone else. Overcoming a delay at work through problem solving and communication. Resolving an issue with a difficult or upset customer. Overcoming issues related to a limited budget, and still delivering good work through the ...
Mastering the Tower of Hanoi: A Comprehensive Guide with Examples
It helps students understand how a problem can be broken down into smaller subproblems and how recursive calls work (Gunion et al., 2009). Problem Solving: Solving the Tower of Hanoi puzzle requires logical thinking, planning, and strategic problem-solving skills. It encourages students to think algorithmically and develop step-by-step ...
3 Ways to Improve Student Problem-Solving
While slower in solving problems, experts use this additional up-front time to more efficiently and effectively solve the problem. In one study, researchers found that experts were much better at "information extraction" or pulling the information they needed to solve the problem later in the problem than novices. This was due to the fact that they started a problem-solving process by ...