management problem solving tools

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!

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

Design your next workshop with SessionLab

Join the 150,000 facilitators using SessionLab

Learn Creative Problem Solving Techniques to Stimulate Innovation in Your Organization

By Kate Eby | October 20, 2017 (updated August 27, 2021)

Share on Facebook
Share on LinkedIn

Link copied

In today’s competitive business landscape, organizations need processes in place to make strong, well-informed, and innovative decisions. Problem solving - in particular creative problem solving (CPS) - is a key skill in learning how to accurately identify problems and their causes, generate potential solutions, and evaluate all the possibilities to arrive at a strong corrective course of action. Every team in any organization, regardless of department or industry, needs to be effective, creative, and quick when solving problems.

In this article, we’ll discuss traditional and creative problem solving, and define the steps, best practices, and common barriers associated. After that, we’ll provide helpful methods and tools to identify the cause(s) of problematic situations, so you can get to the root of the issue and start to generate solutions. Then, we offer nearly 20 creative problem solving techniques to implement at your organization, or even in your personal life. Along the way, experts weigh in on the importance of problem solving, and offer tips and tricks.

What Is Problem Solving and Decision Making?

Problem solving is the process of working through every aspect of an issue or challenge to reach a solution. Decision making is choosing one of multiple proposed solutions — therefore, this process also includes defining and evaluating all potential options. Decision making is often one step of the problem solving process, but the two concepts are distinct.

Collective problem solving is problem solving that includes many different parties and bridges the knowledge of different groups. Collective problem solving is common in business problem solving because workplace decisions typically affect more than one person.

Problem solving, especially in business, is a complicated science. Not only are business conflicts multifaceted, but they often involve different personalities, levels of authority, and group dynamics. In recent years, however, there has been a rise in psychology-driven problem solving techniques, especially for the workplace. In fact, the psychology of how people solve problems is now studied formally in academic disciplines such as psychology and cognitive science.

Joe Carella is the Assistant Dean for Executive Education at the University of Arizona . Joe has over 20 years of experience in helping executives and corporations in managing change and developing successful business strategies. His doctoral research and executive education engagements have seen him focus on corporate strategy, decision making and business performance with a variety of corporate clients including Hershey’s, Chevron, Fender Musical Instruments Corporation, Intel, DP World, Essilor, BBVA Compass Bank.

He explains some of the basic psychology behind problem solving: “When our brain is engaged in the process of solving problems, it is engaged in a series of steps where it processes and organizes the information it receives while developing new knowledge it uses in future steps. Creativity is embedded in this process by incorporating diverse inputs and/or new ways of organizing the information received.”

Laura MacLeod is a Professor of Social Group Work at City University of New York, and the creator of From The Inside Out Project® , a program that coaches managers in team leadership for a variety of workplaces. She has a background in social work and over two decades of experience as a union worker, and currently leads talks on conflict resolution, problem solving, and listening skills at conferences across the country.

MacLeod thinks of problem solving as an integral practice of successful organizations. “Problem solving is a collaborative process — all voices are heard and connected, and resolution is reached by the group,” she says. “Problems and conflicts occur in all groups and teams in the workplace, but if leaders involve everyone in working through, they will foster cohesion, engagement, and buy in. Everybody wins.”

10 tips that will make you more productive.

Uncover the top three factors that are killing your productivity and 10 tips to help you overcome them.

Download the free e-book to overcome my productivity killers

Project Management Guide

Your one-stop shop for everything project management

Ready to get more out of your project management efforts? Visit our comprehensive project management guide for tips, best practices, and free resources to manage your work more effectively.

View the guide

What Is the First Step in Solving a Problem?

Although problem solving techniques vary procedurally, experts agree that the first step in solving a problem is defining the problem. Without a clear articulation of the problem at stake, it is impossible to analyze all the key factors and actors, generate possible solutions, and then evaluate them to pick the best option.

Dr. Elliott Jaffa is a behavioral and management psychologist with over 25 years of problem solving training and management experience. “Start with defining the problem you want to solve,” he says, “And then define where you want to be, what you want to come away with.” He emphasizes these are the first steps in creating an actionable, clear solution.

Bryan Mattimore is Co-Founder of Growth Engine, an 18-year old innovation agency based in Norwalk, CT. Bryan has facilitated over 1,000 ideation sessions and managed over 200 successful innovation projects leading to over $3 billion in new sales. His newest book is 21 Days to a Big Idea . When asked about the first critical component to successful problem solving, Mattimore says, “Defining the challenge correctly, or ‘solving the right problem’ … The three creative techniques we use to help our clients ‘identify the right problem to be solved’ are questioning assumptions, 20 questions, and problem redefinition. A good example of this was a new product challenge from a client to help them ‘invent a new iron. We got them to redefine the challenge as first: a) inventing new anti-wrinkle devices, and then b) inventing new garment care devices.”

What Are Problem Solving Skills?

To understand the necessary skills in problem solving, you should first understand the types of thinking often associated with strong decision making. Most problem solving techniques look for a balance between the following binaries:

Convergent vs. Divergent Thinking: Convergent thinking is bringing together disparate information or ideas to determine a single best answer or solution. This thinking style values logic, speed, and accuracy, and leaves no chance for ambiguity. Divergent thinking is focused on generating new ideas to identify and evaluate multiple possible solutions, often uniting ideas in unexpected combinations. Divergent thinking is characterized by creativity, complexity, curiosity, flexibility, originality, and risk-taking.
Pragmatics vs. Semantics: Pragmatics refer to the logic of the problem at hand, and semantics is how you interpret the problem to solve it. Both are important to yield the best possible solution.
Mathematical vs. Personal Problem Solving: Mathematical problem solving involves logic (usually leading to a single correct answer), and is useful for problems that involve numbers or require an objective, clear-cut solution. However, many workplace problems also require personal problem solving, which includes interpersonal, collaborative, and emotional intuition and skills.

The following basic methods are fundamental problem solving concepts. Implement them to help balance the above thinking models.

Reproductive Thinking: Reproductive thinking uses past experience to solve a problem. However, be careful not to rely too heavily on past solutions, and to evaluate current problems individually, with their own factors and parameters.
Idea Generation: The process of generating many possible courses of action to identify a solution. This is most commonly a team exercise because putting everyone’s ideas on the table will yield the greatest number of potential solutions.

However, many of the most critical problem solving skills are “soft” skills: personal and interpersonal understanding, intuitiveness, and strong listening.

Mattimore expands on this idea: “The seven key skills to be an effective creative problem solver that I detail in my book Idea Stormers: How to Lead and Inspire Creative Breakthroughs are: 1) curiosity 2) openness 3) a willingness to embrace ambiguity 4) the ability to identify and transfer principles across categories and disciplines 5) the desire to search for integrity in ideas, 6) the ability to trust and exercise “knowingness” and 7) the ability to envision new worlds (think Dr. Seuss, Star Wars, Hunger Games, Harry Potter, etc.).”

“As an individual contributor to problem solving it is important to exercise our curiosity, questioning, and visioning abilities,” advises Carella. “As a facilitator it is essential to allow for diverse ideas to emerge, be able to synthesize and ‘translate’ other people’s thinking, and build an extensive network of available resources.”

MacLeod says the following interpersonal skills are necessary to effectively facilitate group problem solving: “The abilities to invite participation (hear all voices, encourage silent members), not take sides, manage dynamics between the monopolizer, the scapegoat, and the bully, and deal with conflict (not avoiding it or shutting down).”

Furthermore, Jaffa explains that the skills of a strong problem solver aren’t measurable. The best way to become a creative problem solver, he says, is to do regular creative exercises that keep you sharp and force you to think outside the box. Carella echoes this sentiment: “Neuroscience tells us that creativity comes from creating novel neural paths. Allow a few minutes each day to exercise your brain with novel techniques and brain ‘tricks’ – read something new, drive to work via a different route, count backwards, smell a new fragrance, etc.”

What Is Creative Problem Solving? History, Evolution, and Core Principles

Creative problem solving (CPS) is a method of problem solving in which you approach a problem or challenge in an imaginative, innovative way. The goal of CPS is to come up with innovative solutions, make a decision, and take action quickly. Sidney Parnes and Alex Osborn are credited with developing the creative problem solving process in the 1950s. The concept was further studied and developed at SUNY Buffalo State and the Creative Education Foundation.

The core principles of CPS include the following:

Balance divergent and convergent thinking
Ask problems as questions
Defer or suspend judgement
Focus on “Yes, and…” rather than “No, but…”

According to Carella, “Creative problem solving is the mental process used for generating innovative and imaginative ideas as a solution to a problem or a challenge. Creative problem solving techniques can be pursued by individuals or groups.”

When asked to define CPS, Jaffa explains that it is, by nature, difficult to create boundaries for. “Creative problem solving is not cut and dry,” he says, “If you ask 100 different people the definition of creative problem solving, you’ll get 100 different responses - it’s a non-entity.”

Business presents a unique need for creative problem solving. Especially in today’s competitive landscape, organizations need to iterate quickly, innovate with intention, and constantly be at the cutting-edge of creativity and new ideas to succeed. Developing CPS skills among your workforce not only enables you to make faster, stronger in-the-moment decisions, but also inspires a culture of collaborative work and knowledge sharing. When people work together to generate multiple novel ideas and evaluate solutions, they are also more likely to arrive at an effective decision, which will improve business processes and reduce waste over time. In fact, CPS is so important that some companies now list creative problem solving skills as a job criteria.

MacLeod reiterates the vitality of creative problem solving in the workplace. “Problem solving is crucial for all groups and teams,” she says. “Leaders need to know how to guide the process, hear all voices and involve all members - it’s not easy.”

“This mental process [of CPS] is especially helpful in work environments where individuals and teams continuously struggle with new problems and challenges posed by their continuously changing environment,” adds Carella.

Problem Solving Best Practices

By nature, creative problem solving does not have a clear-cut set of do’s and don’ts. Rather, creating a culture of strong creative problem solvers requires flexibility, adaptation, and interpersonal skills. However, there are a several best practices that you should incorporate:

Use a Systematic Approach: Regardless of the technique you use, choose a systematic method that satisfies your workplace conditions and constraints (time, resources, budget, etc.). Although you want to preserve creativity and openness to new ideas, maintaining a structured approach to the process will help you stay organized and focused.
View Problems as Opportunities: Rather than focusing on the negatives or giving up when you encounter barriers, treat problems as opportunities to enact positive change on the situation. In fact, some experts even recommend defining problems as opportunities, to remain proactive and positive.
Change Perspective: Remember that there are multiple ways to solve any problem. If you feel stuck, changing perspective can help generate fresh ideas. A perspective change might entail seeking advice of a mentor or expert, understanding the context of a situation, or taking a break and returning to the problem later. “A sterile or familiar environment can stifle new thinking and new perspectives,” says Carella. “Make sure you get out to draw inspiration from spaces and people out of your usual reach.”
Break Down Silos: To invite the greatest possible number of perspectives to any problem, encourage teams to work cross-departmentally. This not only combines diverse expertise, but also creates a more trusting and collaborative environment, which is essential to effective CPS. According to Carella, “Big challenges are always best tackled by a group of people rather than left to a single individual. Make sure you create a space where the team can concentrate and convene.”
Employ Strong Leadership or a Facilitator: Some companies choose to hire an external facilitator that teaches problem solving techniques, best practices, and practicums to stimulate creative problem solving. But, internal managers and staff can also oversee these activities. Regardless of whether the facilitator is internal or external, choose a strong leader who will value others’ ideas and make space for creative solutions. Mattimore has specific advice regarding the role of a facilitator: “When facilitating, get the group to name a promising idea (it will crystalize the idea and make it more memorable), and facilitate deeper rather than broader. Push for not only ideas, but how an idea might specifically work, some of its possible benefits, who and when would be interested in an idea, etc. This fleshing-out process with a group will generate fewer ideas, but at the end of the day will yield more useful concepts that might be profitably pursued.” Additionally, Carella says that “Executives and managers don’t necessarily have to be creative problem solvers, but need to make sure that their teams are equipped with the right tools and resources to make this happen. Also they need to be able to foster an environment where failing fast is accepted and celebrated.”
Evaluate Your Current Processes: This practice can help you unlock bottlenecks, and also identify gaps in your data and information management, both of which are common roots of business problems.

MacLeod offers the following additional advice, “Always get the facts. Don’t jump too quickly to a solution – working through [problems] takes time and patience.”

Mattimore also stresses that how you introduce creative problem solving is important. “Do not start by introducing a new company-wide innovation process,” he says. “Instead, encourage smaller teams to pursue specific creative projects, and then build a process from the ground up by emulating these smaller teams’ successful approaches. We say: ‘You don’t innovate by changing the culture, you change the culture by innovating.’”

Barriers to Effective Problem Solving

Learning how to effectively solve problems is difficult and takes time and continual adaptation. There are several common barriers to successful CPS, including:

Confirmation Bias: The tendency to only search for or interpret information that confirms a person’s existing ideas. People misinterpret or disregard data that doesn’t align with their beliefs.
Mental Set: People’s inclination to solve problems using the same tactics they have used to solve problems in the past. While this can sometimes be a useful strategy (see Analogical Thinking in a later section), it often limits inventiveness and creativity.
Functional Fixedness: This is another form of narrow thinking, where people become “stuck” thinking in a certain way and are unable to be flexible or change perspective.
Unnecessary Constraints: When people are overwhelmed with a problem, they can invent and impose additional limits on solution avenues. To avoid doing this, maintain a structured, level-headed approach to evaluating causes, effects, and potential solutions.
Groupthink: Be wary of the tendency for group members to agree with each other — this might be out of conflict avoidance, path of least resistance, or fear of speaking up. While this agreeableness might make meetings run smoothly, it can actually stunt creativity and idea generation, therefore limiting the success of your chosen solution.
Irrelevant Information: The tendency to pile on multiple problems and factors that may not even be related to the challenge at hand. This can cloud the team’s ability to find direct, targeted solutions.
Paradigm Blindness: This is found in people who are unwilling to adapt or change their worldview, outlook on a particular problem, or typical way of processing information. This can erode the effectiveness of problem solving techniques because they are not aware of the narrowness of their thinking, and therefore cannot think or act outside of their comfort zone.

According to Jaffa, the primary barrier of effective problem solving is rigidity. “The most common things people say are, ‘We’ve never done it before,’ or ‘We’ve always done it this way.’” While these feelings are natural, Jaffa explains that this rigid thinking actually precludes teams from identifying creative, inventive solutions that result in the greatest benefit.

“The biggest barrier to creative problem solving is a lack of awareness – and commitment to – training employees in state-of-the-art creative problem-solving techniques,” Mattimore explains. “We teach our clients how to use ideation techniques (as many as two-dozen different creative thinking techniques) to help them generate more and better ideas. Ideation techniques use specific and customized stimuli, or ‘thought triggers’ to inspire new thinking and new ideas.”

MacLeod adds that ineffective or rushed leadership is another common culprit. “We're always in a rush to fix quickly,” she says. “Sometimes leaders just solve problems themselves, making unilateral decisions to save time. But the investment is well worth it — leaders will have less on their plates if they can teach and eventually trust the team to resolve. Teams feel empowered and engagement and investment increases.”

Strategies for Problem Cause Identification

As discussed, most experts agree that the first and most crucial step in problem solving is defining the problem. Once you’ve done this, however, it may not be appropriate to move straight to the solution phase. Rather, it is often helpful to identify the cause(s) of the problem: This will better inform your solution planning and execution, and help ensure that you don’t fall victim to the same challenges in the future.

Below are some of the most common strategies for identifying the cause of a problem:

Root Cause Analysis: This method helps identify the most critical cause of a problem. A factor is considered a root cause if removing it prevents the problem from recurring. Performing a root cause analysis is a 12 step process that includes: define the problem, gather data on the factors contributing to the problem, group the factors based on shared characteristics, and create a cause-and-effect timeline to determine the root cause. After that, you identify and evaluate corrective actions to eliminate the root cause.

‌ Download Fishbone Diagram Template - Excel

Download 5 Whys Template Excel | Word | PDF

Problem Solving Techniques and Strategies

In this section, we’ll explain several traditional and creative problem solving methods that you can use to identify challenges, create actionable goals, and resolve problems as they arise. Although there is often procedural and objective crossover among techniques, they are grouped by theme so you can identify which method works best for your organization.

Divergent Creative Problem Solving Techniques

Brainstorming: One of the most common methods of divergent thinking, brainstorming works best in an open group setting where everyone is encouraged to share their creative ideas. The goal is to generate as many ideas as possible – you analyze, critique, and evaluate the ideas only after the brainstorming session is complete. To learn more specific brainstorming techniques, read this article .

Mind Mapping: This is a visual thinking tool where you graphically depict concepts and their relation to one another. You can use mind mapping to structure the information you have, analyze and synthesize it, and generate solutions and new ideas from there. The goal of a mind map is to simplify complicated problems so you can more clearly identify solutions.

Appreciative Inquiry (AI): The basic assumption of AI is that “an organization is a mystery to be embraced.” Using this principle, AI takes a positive, inquisitive approach to identifying the problem, analyzing the causes, and presenting possible solutions. The five principles of AI emphasize dialogue, deliberate language and outlook, and social bonding.

Lateral Thinking: This is an indirect problem solving approach centered on the momentum of idea generation. As opposed to critical thinking, where people value ideas based on their truth and the absence of errors, lateral thinking values the “movement value” of new ideas: This means that you reward team members for producing a large volume of new ideas rapidly. With this approach, you’ll generate many new ideas before approving or rejecting any.

Problem Solving Techniques to Change Perspective

Constructive Controversy: This is a structured approach to group decision making to preserve critical thinking and disagreement while maintaining order. After defining the problem and presenting multiple courses of action, the group divides into small advocacy teams who research, analyze, and refute a particular option. Once each advocacy team has presented its best-case scenario, the group has a discussion (advocacy teams still defend their presented idea). Arguing and playing devil’s advocate is encouraged to reach an understanding of the pros and cons of each option. Next, advocacy teams abandon their cause and evaluate the options openly until they reach a consensus. All team members formally commit to the decision, regardless of whether they advocated for it at the beginning. You can learn more about the goals and steps in constructive controversy here .

Carella is a fan of this approach. “Create constructive controversy by having two teams argue the pros and cons of a certain idea,” he says. “It forces unconscious biases to surface and gives space for new ideas to formulate.”

Abstraction: In this method, you apply the problem to a fictional model of the current situation. Mapping an issue to an abstract situation can shed extraneous or irrelevant factors, and reveal places where you are overlooking obvious solutions or becoming bogged down by circumstances.

Analogical Thinking: Also called analogical reasoning , this method relies on an analogy: using information from one problem to solve another problem (these separate problems are called domains). It can be difficult for teams to create analogies among unrelated problems, but it is a strong technique to help you identify repeated issues, zoom out and change perspective, and prevent the problems from occurring in the future. .

CATWOE: This framework ensures that you evaluate the perspectives of those whom your decision will impact. The factors and questions to consider include (which combine to make the acronym CATWOE):

Customers: Who is on the receiving end of your decisions? What problem do they currently have, and how will they react to your proposed solution?
Actors: Who is acting to bring your solution to fruition? How will they respond and be affected by your decision?
Transformation Process: What processes will you employ to transform your current situation and meet your goals? What are the inputs and outputs?
World View: What is the larger context of your proposed solution? What is the larger, big-picture problem you are addressing?
Owner: Who actually owns the process? How might they influence your proposed solution (positively or negatively), and how can you influence them to help you?
Environmental Constraints: What are the limits (environmental, resource- and budget-wise, ethical, legal, etc.) on your ideas? How will you revise or work around these constraints?

Complex Problem Solving

Soft Systems Methodology (SSM): For extremely complex problems, SSM can help you identify how factors interact, and determine the best course of action. SSM was borne out of organizational process modeling and general systems theory, which hold that everything is part of a greater, interconnected system: This idea works well for “hard” problems (where logic and a single correct answer are prioritized), and less so for “soft” problems (i.e., human problems where factors such as personality, emotions, and hierarchy come into play). Therefore, SSM defines a seven step process for problem solving:

Begin with the problem or problematic situation
Express the problem or situation and build a rich picture of the themes of the problem
Identify the root causes of the problem (most commonly with CATWOE)
Build conceptual models of human activity surrounding the problem or situation
Compare models with real-world happenings
Identify changes to the situation that are both feasible and desirable
Take action to implement changes and improve the problematic situation

SSM can be used for any complex soft problem, and is also a useful tool in change management .

Failure Mode and Effects Analysis (FMEA): This method helps teams anticipate potential problems and take steps to mitigate them. Use FMEA when you are designing (redesigning) a complex function, process, product, or service. First, identify the failure modes, which are the possible ways that a project could fail. Then, perform an effects analysis to understand the consequences of each of the potential downfalls. This exercise is useful for internalizing the severity of each potential failure and its effects so you can make adjustments or safeties in your plan.

‌ Download FMEA Template

Problem Solving Based on Data or Logic (Heuristic Methods)

TRIZ: A Russian-developed problem solving technique that values logic, analysis, and forecasting over intuition or soft reasoning. TRIZ (translated to “theory of inventive problem solving” or TIPS in English) is a systematic approach to defining and identifying an inventive solution to difficult problems. The method offers several strategies for arriving at an inventive solution, including a contradictions matrix to assess trade-offs among solutions, a Su-Field analysis which uses formulas to describe a system by its structure, and ARIZ (algorithm of inventive problem solving) which uses algorithms to find inventive solutions.

Inductive Reasoning: A logical method that uses evidence to conclude that a certain answer is probable (this is opposed to deductive reasoning, where the answer is assumed to be true). Inductive reasoning uses a limited number of observations to make useful, logical conclusions (for example, the Scientific Method is an extreme example of inductive reasoning). However, this method doesn’t always map well to human problems in the workplace — in these instances, managers should employ intuitive inductive reasoning , which allows for more automatic, implicit conclusions so that work can progress. This, of course, retains the principle that these intuitive conclusions are not necessarily the one and only correct answer.

Process-Oriented Problem Solving Methods

Plan Do Check Act (PDCA): This is an iterative management technique used to ensure continual improvement of products or processes. First, teams plan (establish objectives to meet desired end results), then do (implement the plan, new processes, or produce the output), then check (compare expected with actual results), and finally act (define how the organization will act in the future, based on the performance and knowledge gained in the previous three steps).

Means-End Analysis (MEA): The MEA strategy is to reduce the difference between the current (problematic) state and the goal state. To do so, teams compile information on the multiple factors that contribute to the disparity between the current and goal states. Then they try to change or eliminate the factors one by one, beginning with the factor responsible for the greatest difference in current and goal state. By systematically tackling the multiple factors that cause disparity between the problem and desired outcome, teams can better focus energy and control each step of the process.

Hurson’s Productive Thinking Model: This technique was developed by Tim Hurson, and is detailed in his 2007 book Think Better: An Innovator’s Guide to Productive Thinking . The model outlines six steps that are meant to give structure while maintaining creativity and critical thinking: 1) Ask “What is going on?” 2) Ask “What is success?” 3) Ask “What is the question?” 4) Generate answers 5) Forge the solution 6) Align resources.

Control Influence Accept (CIA): The basic premise of CIA is that how you respond to problems determines how successful you will be in overcoming them. Therefore, this model is both a problem solving technique and stress-management tool that ensures you aren’t responding to problems in a reactive and unproductive way. The steps in CIA include:

Control: Identify the aspects of the problem that are within your control.
Influence: Identify the aspects of the problem that you cannot control, but that you can influence.
Accept: Identify the aspects of the problem that you can neither control nor influence, and react based on this composite information.

GROW Model: This is a straightforward problem solving method for goal setting that clearly defines your goals and current situation, and then asks you to define the potential solutions and be realistic about your chosen course of action. The steps break down as follows:

Goal: What do you want?
Reality: Where are you now?
Options: What could you do?
Will: What will you do?

OODA Loop: This acronym stands for observe, orient, decide, and act. This approach is a decision-making cycle that values agility and flexibility over raw human force. It is framed as a loop because of the understanding that any team will continually encounter problems or opponents to success and have to overcome them.

There are also many un-named creative problem solving techniques that follow a sequenced series of steps. While the exact steps vary slightly, they all follow a similar trajectory and aim to accomplish similar goals of problem, cause, and goal identification, idea generation, and active solution implementation.

MacLeod offers her own problem solving procedure, which echoes the above steps:

“1. Recognize the Problem: State what you see. Sometimes the problem is covert. 2. Identify: Get the facts — What exactly happened? What is the issue? 3. and 4. Explore and Connect: Dig deeper and encourage group members to relate their similar experiences. Now you're getting more into the feelings and background [of the situation], not just the facts. 5. Possible Solutions: Consider and brainstorm ideas for resolution. 6. Implement: Choose a solution and try it out — this could be role play and/or a discussion of how the solution would be put in place. 7. Evaluate: Revisit to see if the solution was successful or not.”

Many of these problem solving techniques can be used in concert with one another, or multiple can be appropriate for any given problem. It’s less about facilitating a perfect CPS session, and more about encouraging team members to continually think outside the box and push beyond personal boundaries that inhibit their innovative thinking. So, try out several methods, find those that resonate best with your team, and continue adopting new techniques and adapting your processes along the way.

Improve Problem Solving with Work Management in Smartsheet

Empower your people to go above and beyond with a flexible platform designed to match the needs of your team — and adapt as those needs change.

The Smartsheet platform makes it easy to plan, capture, manage, and report on work from anywhere, helping your team be more effective and get more done. Report on key metrics and get real-time visibility into work as it happens with roll-up reports, dashboards, and automated workflows built to keep your team connected and informed.

When teams have clarity into the work getting done, there’s no telling how much more they can accomplish in the same amount of time. Try Smartsheet for free, today.

Discover why over 90% of Fortune 100 companies trust Smartsheet to get work done.

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

More From Forbes

How to solve a problem like a leader.

Share to Facebook
Share to Twitter
Share to Linkedin

Often leaders will think they are driving a problem-solving culture by insistent, or even just encouraging, team members to utilize the tools and templates of problem-solving.

However, most organizations then respond with either sterile and uninspired efforts or at worse, malicious compliance. Shaping the culture of good problem-solving behaviors will naturally encourage people to pick up those same tools with the right intent.

After nearly three decades of coaching at every level, from entry-level employees to experienced CEOs of multi-billion-dollar corporations, author and advisor Jamie Flinchbaugh has worked with over 300 companies worldwide in Lean transformation, including Intel, Harley-Davidson, Crayola, BMW, and Amazon. In his new book, People Solve Problems: The Power of Every Person, Every Day, Every Problem , Flinchbaugh shifts the conversation and argues that organizations focus too much on problem-solving tools and templates and miss other critical elements that make a more significant difference: getting the right behaviors and building the right capabilities.

Problem-solving is not usually completed in a straight line, with fixed questions and predetermined ... [+] answers, say experts

Problem-solving is not usually completed in a straight line, with fixed questions and predetermined answers. Instead, it requires learning, agility, curiosity, and intuition. “This is certainly the case as problems are not puzzles. Whereas a puzzle may have a correct answer, a problem is often unbounded, requiring firstly, the need to understand its scope before exploring solutions, more accurately, different solutions”, says Lebene Soga of Henley Business School. While each problem may not be unique, each requires its own line of inquiry. And each situation solver cannot just follow a script but must leverage their strengths and overcome their weaknesses. “The formulaic approaches to problem-solving may be useful elsewhere but not when we are confronted with wicked problems.”

Attempting to solve or “solutionize” wicked problems requires an understanding of complexity, risks, and more importantly, people,” Soga adds. This is where the right coaching becomes necessary as you do not want leaders rushing to solve problems which often leads to more significant problems. The flexibility and personal engagement that coaching enables to make it the most powerful leverage point for improving problem-solving.

Best Travel Insurance Companies

Best covid-19 travel insurance plans.

In a similar vein, the head of the management discipline at the University of Newcastle Australia, Ashish Malik, reflecting on his two decades of research on the global information technology industry, noted, “the essence of leadership is to take decisions on a range of problems—which may vary on a continuum from simple to complex, for some there are known solutions, while for others there is no known solution or a script ready. Therefore, decision-making is a courageous exercise, and for the first-time leaders, it is a watershed moment.” Leaders often employ many systematic and less planned tools and techniques to solve complex problems, such as using evidence-based and metricized approaches to solving known and unknown issues. In his research, Malik, Sinha, and Blumenfeld found that the use of Six Sigma or Lean Six Sigma methodologies was very prevalent in offshore outsourcing call centers , BPOs , and IT Industry in India as a useful tool for approaching complex tasks operational and leadership problems.

Problem-solving is not a recipe with known inputs, established steps, and a predictable outcome. Curiosity allows us to enter problem-solving as a learning process because we must close our knowledge gaps before closing our performance gaps. Intuition is helpful because when trekking through uncharted territory, as most problem solving is done, it requires making essential adjustments such as when to go slower, when to start over, and even where to start. Analytical and data-driven methods are critical but insufficient when navigating such a journey as problem-solving.

In summary, excellent and practical tools help us perform better in most domains, and problem-solving is no exception, however, much like many of those exact domains, the skill, capability, and talent that we bring to the task far outweigh those tools in their impact on performance.

Disclosure: One source mentioned in this article, Lebene Soga, is employed by the same University as this article’s author, though both reside on different campuses

Editorial Standards
Reprints & Permissions

Product overview
All features
App integrations

CAPABILITIES

project icon Project management
Project views
Custom fields
Status updates
goal icon Goals and reporting
Reporting dashboards
workflow icon Workflows and automation
portfolio icon Resource management
Time tracking
my-task icon Admin and security
Admin console
asana-intelligence icon Asana Intelligence
list icon Personal
premium icon Starter
briefcase icon Advanced
Goal management
Organizational planning
Campaign management
Creative production
Content calendars
Marketing strategic planning
Resource planning
Project intake
Product launches
Employee onboarding
View all uses arrow-right icon
Project plans
Team goals & objectives
Team continuity
Meeting agenda
View all templates arrow-right icon
Work management resources Discover best practices, watch webinars, get insights
What's new Learn about the latest and greatest from Asana
Customer stories See how the world's best organizations drive work innovation with Asana
Help Center Get lots of tips, tricks, and advice to get the most from Asana
Asana Academy Sign up for interactive courses and webinars to learn Asana
Developers Learn more about building apps on the Asana platform
Community programs Connect with and learn from Asana customers around the world
Events Find out about upcoming events near you
Partners Learn more about our partner programs
Support Need help? Contact the Asana support team
Asana for nonprofits Get more information on our nonprofit discount program, and apply.

Turn your team into skilled problem solvers with these problem-solving strategies

Picture this, you're handling your daily tasks at work and your boss calls you in and says, "We have a problem."

Unfortunately, we don't live in a world in which problems are instantly resolved with the snap of our fingers. Knowing how to effectively solve problems is an important professional skill to hone. If you have a problem that needs to be solved, what is the right process to use to ensure you get the most effective solution?

In this article we'll break down the problem-solving process and how you can find the most effective solutions for complex problems.

What is problem solving?

Problem solving is the process of finding a resolution for a specific issue or conflict. There are many possible solutions for solving a problem, which is why it's important to go through a problem-solving process to find the best solution. You could use a flathead screwdriver to unscrew a Phillips head screw, but there is a better tool for the situation. Utilizing common problem-solving techniques helps you find the best solution to fit the needs of the specific situation, much like using the right tools.

Decision-making tools for agile businesses

In this ebook, learn how to equip employees to make better decisions—so your business can pivot, adapt, and tackle challenges more effectively than your competition.

Make good choices, fast: How decision-making processes can help businesses stay agile ebook banner image

4 steps to better problem solving

While it might be tempting to dive into a problem head first, take the time to move step by step. Here’s how you can effectively break down the problem-solving process with your team:

1. Identify the problem that needs to be solved

One of the easiest ways to identify a problem is to ask questions. A good place to start is to ask journalistic questions, like:

Who : Who is involved with this problem? Who caused the problem? Who is most affected by this issue?

What: What is happening? What is the extent of the issue? What does this problem prevent from moving forward?

Where: Where did this problem take place? Does this problem affect anything else in the immediate area?

When: When did this problem happen? When does this problem take effect? Is this an urgent issue that needs to be solved within a certain timeframe?

Why: Why is it happening? Why does it impact workflows?

How: How did this problem occur? How is it affecting workflows and team members from being productive?

Asking journalistic questions can help you define a strong problem statement so you can highlight the current situation objectively, and create a plan around that situation.

Here’s an example of how a design team uses journalistic questions to identify their problem:

Overarching problem: Design requests are being missed

Who: Design team, digital marketing team, web development team

What: Design requests are forgotten, lost, or being created ad hoc.

Where: Email requests, design request spreadsheet

When: Missed requests on January 20th, January 31st, February 4th, February 6th

How : Email request was lost in inbox and the intake spreadsheet was not updated correctly. The digital marketing team had to delay launching ads for a few days while design requests were bottlenecked. Designers had to work extra hours to ensure all requests were completed.

In this example, there are many different aspects of this problem that can be solved. Using journalistic questions can help you identify different issues and who you should involve in the process.

2. Brainstorm multiple solutions

If at all possible, bring in a facilitator who doesn't have a major stake in the solution. Bringing an individual who has little-to-no stake in the matter can help keep your team on track and encourage good problem-solving skills.

Here are a few brainstorming techniques to encourage creative thinking:

Brainstorm alone before hand: Before you come together as a group, provide some context to your team on what exactly the issue is that you're brainstorming. This will give time for you and your teammates to have some ideas ready by the time you meet.

Say yes to everything (at first): When you first start brainstorming, don't say no to any ideas just yet—try to get as many ideas down as possible. Having as many ideas as possible ensures that you’ll get a variety of solutions. Save the trimming for the next step of the strategy.

Talk to team members one-on-one: Some people may be less comfortable sharing their ideas in a group setting. Discuss the issue with team members individually and encourage them to share their opinions without restrictions—you might find some more detailed insights than originally anticipated.

Break out of your routine: If you're used to brainstorming in a conference room or over Zoom calls, do something a little different! Take your brainstorming meeting to a coffee shop or have your Zoom call while you're taking a walk. Getting out of your routine can force your brain out of its usual rut and increase critical thinking.

3. Define the solution

After you brainstorm with team members to get their unique perspectives on a scenario, it's time to look at the different strategies and decide which option is the best solution for the problem at hand. When defining the solution, consider these main two questions: What is the desired outcome of this solution and who stands to benefit from this solution?

Set a deadline for when this decision needs to be made and update stakeholders accordingly. Sometimes there's too many people who need to make a decision. Use your best judgement based on the limitations provided to do great things fast.

4. Implement the solution

To implement your solution, start by working with the individuals who are as closest to the problem. This can help those most affected by the problem get unblocked. Then move farther out to those who are less affected, and so on and so forth. Some solutions are simple enough that you don’t need to work through multiple teams.

After you prioritize implementation with the right teams, assign out the ongoing work that needs to be completed by the rest of the team. This can prevent people from becoming overburdened during the implementation plan . Once your solution is in place, schedule check-ins to see how the solution is working and course-correct if necessary.

Implement common problem-solving strategies

There are a few ways to go about identifying problems (and solutions). Here are some strategies you can try, as well as common ways to apply them:

Trial and error

Trial and error problem solving doesn't usually require a whole team of people to solve. To use trial and error problem solving, identify the cause of the problem, and then rapidly test possible solutions to see if anything changes.

This problem-solving method is often used in tech support teams through troubleshooting.

The 5 whys problem-solving method helps get to the root cause of an issue. You start by asking once, “Why did this issue happen?” After answering the first why, ask again, “Why did that happen?” You'll do this five times until you can attribute the problem to a root cause.

This technique can help you dig in and find the human error that caused something to go wrong. More importantly, it also helps you and your team develop an actionable plan so that you can prevent the issue from happening again.

Here’s an example:

Problem: The email marketing campaign was accidentally sent to the wrong audience.

“Why did this happen?” Because the audience name was not updated in our email platform.

“Why were the audience names not changed?” Because the audience segment was not renamed after editing.

“Why was the audience segment not renamed?” Because everybody has an individual way of creating an audience segment.

“Why does everybody have an individual way of creating an audience segment?” Because there is no standardized process for creating audience segments.

“Why is there no standardized process for creating audience segments?” Because the team hasn't decided on a way to standardize the process as the team introduced new members.

In this example, we can see a few areas that could be optimized to prevent this mistake from happening again. When working through these questions, make sure that everyone who was involved in the situation is present so that you can co-create next steps to avoid the same problem.

A SWOT analysis

A SWOT analysis can help you highlight the strengths and weaknesses of a specific solution. SWOT stands for:

Strength: Why is this specific solution a good fit for this problem?

Weaknesses: What are the weak points of this solution? Is there anything that you can do to strengthen those weaknesses?

Opportunities: What other benefits could arise from implementing this solution?

Threats: Is there anything about this decision that can detrimentally impact your team?

As you identify specific solutions, you can highlight the different strengths, weaknesses, opportunities, and threats of each solution.

This particular problem-solving strategy is good to use when you're narrowing down the answers and need to compare and contrast the differences between different solutions.

Even more successful problem solving

After you’ve worked through a tough problem, don't forget to celebrate how far you've come. Not only is this important for your team of problem solvers to see their work in action, but this can also help you become a more efficient, effective , and flexible team. The more problems you tackle together, the more you’ll achieve.

Looking for a tool to help solve problems on your team? Track project implementation with a work management tool like Asana .

Related resources

How to find alignment on AI

How to scale your creative and content production with Asana

Smooth product launches are simpler than you think

Fix these common onboarding challenges to boost productivity

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.

Methods and techniques on how to set team goals

25 Employee engagement ideas for remote employees

How to establish powerful employee connections

15 Truly impactful feedback methods for your team

Improve remote team communication with these 11 tips

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

Explore Lean Thinking and Practice / Problem-Solving

Problem-Solving

Explore the process that’s foundational to assuring every individual becomes engaged by arming them with methods they can use to overcome obstacles and improve their work process.

Overcoming obstacles to achieve or elevate a standard

In a lean management system, everyone is engaged in ongoing problem-solving that is guided by two characteristics:

Everything described or claimed should be based on verifiable facts, not assumptions and interpretations. 
Problem-solving is never-ending; that is, it begins rather than ends when an improvement plan is implemented. The implementation process is a learning opportunity to discover how to make progress toward the target condition.

Lean thinkers & practitioners understand that the problem-solving process is impeded if you make the common mistake of mechanically reaching for a familiar or favorite problem-solving methodology or, worse, jump quickly to a solution. 

Leaders and teams avoid this trap by recognizing that most business problems fall into four categories, each requiring different thought processes, improvement methods, and management cadences.

The Four Types of Problems

Type 1: Troubleshooting: reactive problem-solving that hinges upon rapidly returning abnormal conditions to known standards. It provides some immediate relief but does not address the root cause.

Type 2: Gap from Standard: structured problem-solving that focuses on defining the problem, setting goals, analyzing the root cause, and establishing countermeasures, checks, standards, and follow-up activities. The aim is to prevent the problem from recurring by eliminating its underlying causes.

Type 3: Target Condition: continuous improvement ( kaizen ) that goes beyond existing standards of performance. It may utilize existing methods in new, creative ways to deliver superior value or performance toward a new target state of improvement.

Type 4: Open-ended: innovative problem-solving based on creativity, synthesis, and recognition of opportunity. It establishes new norms that often entail unexpected products, processes, systems, or value for the customer well beyond current levels. 

By helping everyone in the organization to understand the importance of taking ownership of seeing and solving all types of problems, lean thinking & practice:

Engenders a sense of empowerment and autonomy in all workers, which in turn promotes engagement in and ownership of the work process
Enables organizations to overcome obstacles at their source, so they do not become more significant problems upstream

Ultimately, building a problem-solving culture creates a competitive advantage that is difficult for competitors to match.

Relevant Posts

Problem Solving

Why the A3 Process Involves More than Filling in Boxes

Article by Tracey Richardson

Big Problems? Start Small

Article by Josh Howell

Article graphic image with repeating icons

What’s your problem

Article, Video by John Shook

Relevant Products

Four Types of Problems

by Art Smalley

Managing to Learn: Using the A3 management process

by John Shook

Getting Home

by Liz McCartney and Zack Rosenburg

Steady Work

by Karen Gaudet

Relevant Events

August 05, 2024 | Coach-Led Online Course and Oakland University in Rochester, Michigan

Managing to Learn

November 05, 2024 | Morgantown, PA

Building a Lean Operating and Management System

November 12, 2024 | Coach-Led Online Course

Improvement Kata/Coaching Kata

Be the first to learn of new learning opportunities and the latest practical, actionable information. subscribe to an lei newsletter., join us on social, privacy overview.

Business & Money
Biography & History

Buy new: .savingPriceOverride { color:#CC0C39!important; font-weight: 300!important; } .reinventMobileHeaderPrice { font-weight: 400; } #apex_offerDisplay_mobile_feature_div .reinventPriceSavingsPercentageMargin, #apex_offerDisplay_mobile_feature_div .reinventPricePriceToPayMargin { margin-right: 4px; } -35% $22.74 $ 22 . 74 $3.99 delivery June 6 - 13 Ships from: indoobestsellers Sold by: indoobestsellers

Save with used - good .savingpriceoverride { color:#cc0c39important; font-weight: 300important; } .reinventmobileheaderprice { font-weight: 400; } #apex_offerdisplay_mobile_feature_div .reinventpricesavingspercentagemargin, #apex_offerdisplay_mobile_feature_div .reinventpricepricetopaymargin { margin-right: 4px; } $13.00 $ 13 . 00 free delivery june 9 - 18 on orders shipped by amazon over $35 ships from: amazon sold by: favr store, return this item for free.

Free returns are available for the shipping address you chose. You can return the item for any reason in new and unused condition: no shipping charges

Go to your orders and start the return
Select the return method

Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required .

Read instantly on your browser with Kindle for Web.

Using your mobile phone camera - scan the code below and download the Kindle app.

Follow the authors

Image Unavailable

To view this video download Flash Player

The McKinsey Mind: Understanding and Implementing the Problem-Solving Tools and Management Techniques of the World's Top Strategic Consulting Firm Hardcover – October 17, 2001

Purchase options and add-ons.

The groundbreaking follow-up to the international bestsellera hands-on guide to putting McKinsey techniques to work in your organization

McKinsey & Company is the most respected and most secretive consulting firm in the world, and business readers just can't seem to get enough of all things McKinsey. Now, hot on the heels of his acclaimed international bestseller The McKinsey Way , Ethan Rasiel brings readers a powerful new guide to putting McKinsey concepts and skills into action The McKinsey Mind . While the first book used case studies and anecdotes from former and current McKinseyites to describe how "the firm" solves the thorniest business problems of their A-list clients, The McKinsey Mind goes a giant step further. It explains, step-by-step, how to use McKinsey tools, techniques and strategies to solve an array of core business problems and to make any business venture more successful.

Designed to work as a stand-alone guide or together with The McKinsey Way , The McKinsey Mind follows the same critically acclaimed style and format as its predecessor. In this book authors Rasiel and Friga expand upon the lessons found in The McKinsey Way with real-world examples, parables, and easy-to-do exercises designed to get readers up and running.

Print length 272 pages
Language English
Publisher McGraw Hill
Publication date October 17, 2001
Dimensions 6.3 x 1.1 x 9.3 inches
ISBN-10 0071374299
ISBN-13 978-0071374293
See all details

Frequently bought together

The McKinsey Mind: Understanding and Implementing the Problem-Solving Tools and Management Techniques of the World's Top Stra

Similar items that may ship from close to you

The McKinsey Edge: Success Principles from the World’s Most Powerful Consulting Firm

Editorial Reviews

From the back cover.

The First Step-by-Step Manual for Achieving McKinsey-Style Solutions--and Success

International bestseller The McKinsey Way provided a through-the-keyhole look at McKinsey & Co., history's most prestigious consulting firm. Now, the follow-up implementation manual, The McKinsey Mind , reveals the hands-on secrets behind the powerhouse firm's success--and discusses how executives from any field or industry can use those tactics to be more proactive and successful in their day-to-day decision-making.

Structured around interviews and frontline anecdotes from former McKinsey consultants--as well as the authors, themselves McKinsey alumni-- The McKinsey Mind explores how McKinsey tools and techniques can be applied to virtually any business problem in any setting. Immensely valuable in today's crisis-a-minute workplace, it discusses:

Techniques for framing problems and designing analyses
Methods for interpreting results and presenting solutions

The ability to think in a rigorous, structured manner--a McKinsey manner--is not a birthright. It can, however, be a learned behavior. Let The McKinsey Mind show you how to approach and solve problems with the skill of a McKinsey consultant and obtain the positive results that have been delivered to McKinsey clients for over a century.

McKinsey & Co. is renowned throughout the world for its ability to arrive at sharp, insightful analyses of its clients' situations then provide solutions that are as ingenious as they are effective. McKinsey succeeds almost as well as shielding its revolutionary methods from competitors' scrutiny.

Now, The McKinsey Mind pulls back the curtain to reveal the ways in which McKinsey consultants consistently deliver their magic and how those methods can be used to achieve exceptional results in companies from 10 employees to 10,000. Packed with insights and brainstorming exercises for establishing the McKinsey mind-set, this book is an in-depth guidebook for applying McKinsey methods in any industry and organizational environment.

Taking a step-by-step approach, The McKinsey Mind looks at the McKinsey mystique from every angle. Owners, executives, consultants, and team leaders can look to this comprehensive treatment for ways to:

Follow McKinsey's MECE (mutually exclusive, collectively exhaustive) line of attack
Frame business problems to make them susceptible to rigorous fact-based analysis
Use the same fact-based analysis--in conjunction with gut instinct--to make strategic decisions
Conduct meaningful interviews and effectively summarize the content of those interviews
Analyze the data to find out the "so what"
Clearly communicate fact-based solutions to all pertinent decision makers

Because organizational problems rarely exist in a vacuum, The McKinsey Mind discusses these approaches and more to help you arrive at usable and sensible solutions. It goes straight to the source--former McKinsey consultants now in leadership positions in organizations throughout the world--to give you today's only implementation-based, solution-driven look at the celebrated McKinsey problem-solving method.

" The McKinsey Mind provides a fascinating peek at the tools, practices, and philosophies that have helped this much-admired firm develop generations of bright young MBAs into trusted corporate advisors. But the book's practical, down-to-earth advice is not just for consultants. The disciplined way in which McKinsey consultants frame issues, analyze problems, and present solutions offers valuable lessons for any practicing or aspiring manager." --Christopher A. Bartlett, Daewoo Professor of Business Administration, Harvard Business School

"McKinsey and Co. rescues the biggest companies from disaster by addressing every problem with its own mixture of logic-driven, hypothesis-tested analysis. The McKinsey Mind helps everyone learn how to think with the same discipline and devotion to creating business success. According to the maxim, giving a man a fish may feed him for a day, but teaching him to fish will feed him for a lifetime. Paying McKinsey to solve your problem may help you for a day, but learning how they do it should help you for a lifetime." --Peter Wayner, Author of Free For All: How Linux and the Free Software Movement Undercut The High-Tech Titans

"The McKinsey Mind unlocks the techniques of the world's preeminent consulting firm and presents them in a format that is easy to understand and even easier to implement." --Dan Nagy, Associate Dean, The Fuqua School of Business, Duke University

About the Author

Ethan M. Rasiel was a consultant in McKinsey & Co.'s New York office. His clients included major companies in finance, telecommunications, computing, and consumer goods sectors. Prior to joining McKinsey, Rasiel, who earned an MBA from the Wharton School at the University of Pennsylvania, was an equity fund manager at Mercury Asset Management in London, as well as an investment banker.

Paul N. Friga worked for McKinsey & Co. in the Pittsburgh office after receiving his MBA from the Kenan-Flagler Business School at the University of North Carolina. He has conducted consulting projects relating to international expansion, acquisition and strategic planning, education, water, and other industries. He has also consulted for Price Waterhouse. He is currently pursuing his Ph.D. in Strategy at Kenan-Flagler and is Acting Director of the North Carolina Knowledge Management Center.

Product details

Publisher ‏ : ‎ McGraw Hill; First Edition (October 17, 2001)
Language ‏ : ‎ English
Hardcover ‏ : ‎ 272 pages
ISBN-10 ‏ : ‎ 0071374299
ISBN-13 ‏ : ‎ 978-0071374293
Item Weight ‏ : ‎ 2.31 pounds
Dimensions ‏ : ‎ 6.3 x 1.1 x 9.3 inches
#40 in Consulting
#310 in Decision-Making & Problem Solving
#943 in Business Management (Books)

Videos for this product

Click to play video

The Biggest Lesson from this Book

Omar M Khateeb

About the authors

Paul n. friga.

Discover more of the author’s books, see similar authors, read author blogs and more

Ethan M. Rasiel

Customer reviews.

Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.

To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.

Sort reviews by Top reviews Most recent Top reviews

Top reviews from the United States

There was a problem filtering reviews right now. please try again later..

Top reviews from other countries

Amazon Newsletter
About Amazon
Accessibility
Sustainability
Press Center
Investor Relations
Amazon Devices
Amazon Science
Sell on Amazon
Sell apps on Amazon
Supply to Amazon
Protect & Build Your Brand
Become an Affiliate
Become a Delivery Driver
Start a Package Delivery Business
Advertise Your Products
Self-Publish with Us
Become an Amazon Hub Partner
› See More Ways to Make Money
Amazon Visa
Amazon Store Card
Amazon Secured Card
Amazon Business Card
Shop with Points
Credit Card Marketplace
Reload Your Balance
Amazon Currency Converter
Your Account
Your Orders
Shipping Rates & Policies
Amazon Prime
Returns & Replacements
Manage Your Content and Devices
Recalls and Product Safety Alerts
Conditions of Use
Privacy Notice
Consumer Health Data Privacy Disclosure
Your Ads Privacy Choices

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

Share Podcast

A Better Framework for Solving Tough Problems

Start with trust and end with speed.

Apple Podcasts

When it comes to solving complicated problems, the default for many organizational leaders is to take their time to work through the issues at hand. Unfortunately, that often leads to patchwork solutions or problems not truly getting resolved.

But Anne Morriss offers a different framework. In this episode, she outlines a five-step process for solving any problem and explains why starting with trust and ending with speed is so important for effective change leadership. As she says, “Let’s get into dialogue with the people who are also impacted by the problem before we start running down the path of solving it.”

Morriss is an entrepreneur and leadership coach. She’s also the coauthor of the book, Move Fast and Fix Things: The Trusted Leader’s Guide to Solving Hard Problems .

Key episode topics include: strategy, decision making and problem solving, strategy execution, managing people, collaboration and teams, trustworthiness, organizational culture, change leadership, problem solving, leadership.

HBR On Strategy curates the best case studies and conversations with the world’s top business and management experts, to help you unlock new ways of doing business. New episodes every week.

Listen to the full HBR IdeaCast episode: How to Solve Tough Problems Better and Faster (2023)
Find more episodes of HBR IdeaCast
Discover 100 years of Harvard Business Review articles, case studies, podcasts, and more at HBR.org .

HANNAH BATES: Welcome to HBR On Strategy , case studies and conversations with the world’s top business and management experts, hand-selected to help you unlock new ways of doing business.

When it comes to solving complicated problems, many leaders only focus on the most apparent issues. Unfortunately that often leads to patchwork or partial solutions. But Anne Morriss offers a different framework that aims to truly tackle big problems by first leaning into trust and then focusing on speed.

Morriss is an entrepreneur and leadership coach. She’s also the co-author of the book, Move Fast and Fix Things: The Trusted Leader’s Guide to Solving Hard Problems . In this episode, she outlines a five-step process for solving any problem. Some, she says, can be solved in a week, while others take much longer. She also explains why starting with trust and ending with speed is so important for effective change leadership.

This episode originally aired on HBR IdeaCast in October 2023. Here it is.

CURT NICKISCH: Welcome to the HBR IdeaCast from Harvard Business Review. I’m Curt Nickisch.

Problems can be intimidating. Sure, some problems are fun to dig into. You roll up your sleeves, you just take care of them; but others, well, they’re complicated. Sometimes it’s hard to wrap your brain around a problem, much less fix it.

And that’s especially true for leaders in organizations where problems are often layered and complex. They sometimes demand technical, financial, or interpersonal knowledge to fix. And whether it’s avoidance on the leaders’ part or just the perception that a problem is systemic or even intractable, problems find a way to endure, to keep going, to keep being a problem that everyone tries to work around or just puts up with.

But today’s guest says that just compounds it and makes the problem harder to fix. Instead, she says, speed and momentum are key to overcoming a problem.

Anne Morriss is an entrepreneur, leadership coach and founder of the Leadership Consortium and with Harvard Business School Professor Francis Frei, she wrote the new book, Move Fast and Fix Things: The Trusted Leaders Guide to Solving Hard Problems . Anne, welcome back to the show.

ANNE MORRISS: Curt, thank you so much for having me.

CURT NICKISCH: So, to generate momentum at an organization, you say that you really need speed and trust. We’ll get into those essential ingredients some more, but why are those two essential?

ANNE MORRISS: Yeah. Well, the essential pattern that we observed was that the most effective change leaders out there were building trust and speed, and it didn’t seem to be a well-known observation. We all know the phrase, “Move fast and break things,” but the people who were really getting it right were moving fast and fixing things, and that was really our jumping off point. So when we dug into the pattern, what we observed was they were building trust first and then speed. This foundation of trust was what allowed them to fix more things and break fewer.

CURT NICKISCH: Trust sounds like a slow thing, right? If you talk about building trust, that is something that takes interactions, it takes communication, it takes experiences. Does that run counter to the speed idea?

ANNE MORRISS: Yeah. Well, this issue of trust is something we’ve been looking at for over a decade. One of the headlines in our research is it’s actually something we’re building and rebuilding and breaking all the time. And so instead of being this precious, almost farbege egg, it’s this thing that is constantly in motion and this thing that we can really impact when we’re deliberate about our choices and have some self-awareness around where it’s breaking down and how it’s breaking down.

CURT NICKISCH: You said break trust in there, which is intriguing, right? That you may have to break trust to build trust. Can you explain that a little?

ANNE MORRISS: Yeah, well, I’ll clarify. It’s not that you have to break it in order to build it. It’s just that we all do it some of the time. Most of us are trusted most of the time. Most of your listeners I imagine are trusted most of the time, but all of us have a pattern where we break trust or where we don’t build as much as could be possible.

CURT NICKISCH: I want to talk about speed, this other essential ingredient that’s so intriguing, right? Because you think about solving hard problems as something that just takes a lot of time and thinking and coordination and planning and designing. Explain what you mean by it? And also, just how we maybe approach problems wrong by taking them on too slowly?

ANNE MORRISS: Well, Curt, no one has ever said to us, “I wish I had taken longer and done less.” We hear the opposite all the time, by the way. So what we really set out to do was to create a playbook that anyone can use to take less time to do more of the things that are going to make your teams and organizations stronger.

And the way we set up the book is okay, it’s really a five step process. Speed is the last step. It’s the payoff for the hard work you’re going to do to figure out your problem, build or rebuild trust, expand the team in thoughtful and strategic ways, and then tell a real and compelling story about the change you’re leading.

Only then do you get to go fast, but that’s an essential part of the process, and we find that either people under emphasize it or speed has gotten a bad name in this world of moving fast and breaking things. And part of our mission for sure was to rehabilitate speed’s reputation because it is an essential part of the change leader’s equation. It can be the difference between good intentions and getting anything done at all.

CURT NICKISCH: You know, the fact that nobody ever tells you, “I wish we had done less and taken more time.” I think we all feel that, right? Sometimes we do something and then realize, “Oh, that wasn’t that hard and why did it take me so long to do it? And I wish I’d done this a long time ago.” Is it ever possible to solve a problem too quickly?

ANNE MORRISS: Absolutely. And we see that all the time too. What we push people to do in those scenarios is really take a look at the underlying issue because in most cases, the solution is not to take your foot off the accelerator per se and slow down. The solution is to get into the underlying problem. So if it’s burnout or a strategic disconnect between what you’re building and the marketplace you’re serving, what we find is the anxiety that people attach to speed or the frustration people attach to speed is often misplaced.

CURT NICKISCH: What is a good timeline to think about solving a problem then? Because if we by default take too long or else jump ahead and we don’t fix it right, what’s a good target time to have in your mind for how long solving a problem should take?

ANNE MORRISS: Yeah. Well, we’re playful in the book and talking about the idea that many problems can be solved in a week. We set the book up five chapters. They’re titled Monday, Tuesday, Wednesday, Thursday, Friday, and we’re definitely having fun with that. And yet, if you count the hours in a week, there are a lot of them. Many of our problems, if you were to spend a focused 40 hours of effort on a problem, you’re going to get pretty far.

But our main message is, listen, of course it’s going to depend on the nature of the problem, and you’re going to take weeks and maybe even some cases months to get to the other side. What we don’t want you to do is take years, which tends to be our default timeline for solving hard problems.

CURT NICKISCH: So you say to start with identifying the problem that’s holding you back, seems kind of obvious. But where do companies go right and wrong with this first step of just identifying the problem that’s holding you back?

ANNE MORRISS: And our goal is that all of these are going to feel obvious in retrospect. The problem is we skip over a lot of these steps and this is why we wanted to underline them. So this one is really rooted in our observation and I think the pattern of our species that we tend to be overconfident in the quality of our thoughts, particularly when it comes to diagnosing problems.

And so we want to invite you to start in a very humble and curious place, which tends not to be our default mode when we’re showing up for work. We convince ourselves that we’re being paid for our judgment. That’s exactly what gets reinforced everywhere. And so we tend to counterintuitively, given what we just talked about, we tend to move too quickly through the diagnostic phase.

CURT NICKISCH: “I know what to do, that’s why you hired me.”

ANNE MORRISS: Exactly. “I know what to do. That’s why you hired me. I’ve seen this before. I have a plan. Follow me.” We get rewarded for the expression of confidence and clarity. And so what we’re inviting people to do here is actually pause and really lean into what are the root causes of the problem you’re seeing? What are some alternative explanations? Let’s get into dialogue with the people who are also impacted by the problem before we start running down the path of solving it.

CURT NICKISCH: So what do you recommend for this step, for getting to the root of the problem? What are questions you should ask? What’s the right thought process? What do you do on Monday of the week?

ANNE MORRISS: In our experience of doing this work, people tend to undervalue the power of conversation, particularly with other people in the organization. So we will often advocate putting together a team of problem solvers, make it a temporary team, really pull in people who have a particular perspective on the problem and create the space, make it as psychologically safe as you can for people to really, as Chris Argyris so beautifully articulated, discuss the undiscussable.

And so the conditions for that are going to look different in every organization depending on the problem, but if you can get a space where smart people who have direct experience of a problem are in a room and talking honestly with each other, you can make an extraordinary amount of progress, certainly in a day.

CURT NICKISCH: Yeah, that gets back to the trust piece.

ANNE MORRISS: Definitely.

CURT NICKISCH: How do you like to start that meeting, or how do you like to talk about it? I’m just curious what somebody on that team might hear in that meeting, just to get the sense that it’s psychologically safe, you can discuss the undiscussable and you’re also focusing on the identification part. What’s key to communicate there?

ANNE MORRISS: Yeah. Well, we sometimes encourage people to do a little bit of data gathering before those conversations. So the power of a quick anonymous survey around whatever problem you’re solving, but also be really thoughtful about the questions you’re going to ask in the moment. So a little bit of preparation can go a long way and a little bit of thoughtfulness about the power dynamic. So who’s going to walk in there with license to speak and who’s going to hold back? So being thoughtful about the agenda, about the questions you’re asking about the room, about the facilitation, and then courage is a very infectious emotion.

So if you can early on create the conditions for people to show up bravely in that conversation, then the chance that you’re going to get good information and that you’re going to walk out of that room with new insight in the problem that you didn’t have when you walked in is extraordinarily high.

CURT NICKISCH: Now, in those discussions, you may have people who have different perspectives on what the problem really is. They also bear different costs of addressing the problem or solving it. You talked about the power dynamic, but there’s also an unfairness dynamic of who’s going to actually have to do the work to take care of it, and I wonder how you create a culture in that meeting where it’s the most productive?

ANNE MORRISS: For sure, the burden of work is not going to be equitably distributed around the room. But I would say, Curt, the dynamic that we see most often is that people are deeply relieved that hard problems are being addressed. So it really can create, and more often than not in our experience, it does create this beautiful flywheel of action, creativity, optimism. Often when problems haven’t been addressed, there is a fair amount of anxiety in the organization, frustration, stagnation. And so credible movement towards action and progress is often the best antidote. So even if the plan isn’t super clear yet, if it’s credible, given who’s in the room and their decision rights and mandate, if there’s real momentum coming out of that to make progress, then that tends to be deeply energizing to people.

CURT NICKISCH: I wonder if there’s an organization that you’ve worked with that you could talk about how this rolled out and how this took shape?

ANNE MORRISS: When we started working with Uber, that was wrestling with some very public issues of culture and trust with a range of stakeholders internally, the organization, also external, that work really started with a campaign of listening and really trying to understand where trust was breaking down from the perspective of these stakeholders?

So whether it was female employees or regulators or riders who had safety concerns getting into the car with a stranger. This work, it starts with an honest internal dialogue, but often the problem has threads that go external. And so bringing that same commitment to curiosity and humility and dialogue to anyone who’s impacted by the problem is the fastest way to surface what’s really going on.

CURT NICKISCH: There’s a step in this process that you lay out and that’s communicating powerfully as a leader. So we’ve heard about listening and trust building, but now you’re talking about powerful communication. How do you do this and why is it maybe this step in the process rather than the first thing you do or the last thing you do?

ANNE MORRISS: So in our process, again, it’s the days of the week. On Monday you figured out the problem. Tuesday you really got into the sandbox in figuring out what a good enough plan is for building trust. Wednesday, step three, you made it better. You created an even better plan, bringing in new perspectives. Thursday, this fourth step is the day we’re saying you got to go get buy-in. You got to bring other people along. And again, this is a step where we see people often underinvest in the power and payoff of really executing it well.

CURT NICKISCH: How does that go wrong?

ANNE MORRISS: Yeah, people don’t know the why. Human behavior and the change in human behavior really depends on a strong why. It’s not just a selfish, “What’s in it for me?” Although that’s helpful, but where are we going? I may be invested in a status quo and I need to understand, okay, if you’re going to ask me to change, if you’re going to invite me into this uncomfortable place of doing things differently, why am I here? Help me understand it and articulate the way forward and language that not only I can understand, but also that’s going to be motivating to me.

CURT NICKISCH: And who on my team was part of this process and all that kind of stuff?

ANNE MORRISS: Oh, yeah. I may have some really important questions that may be in the way of my buy-in and commitment to this plan. So certainly creating a space where those questions can be addressed is essential. But what we found is that there is an architecture of a great change story, and it starts with honoring the past, honoring the starting place. Sometimes we’re so excited about the change and animated about the change that what has happened before or what is even happening in the present tense is low on our list of priorities.

Or we want to label it bad, because that’s the way we’ve thought about the change, but really pausing and honoring what came before you and all the reasonable decisions that led up to it, I think can be really helpful to getting people emotionally where you want them to be willing to be guided by you. Going back to Uber, when Dara Khosrowshahi came in.

CURT NICKISCH: This is the new CEO.

ANNE MORRISS: The new CEO.

CURT NICKISCH: Replaced Travis Kalanick, the founder and first CEO, yeah.

ANNE MORRISS: Yeah, and had his first all-hands meeting. One of his key messages, and this is a quote, was that he was going to retain the edge that had made Uber, “A force of nature.” And in that meeting, the crowd went wild because this is also a company that had been beaten up publicly for months and months and months, and it was a really powerful choice. And his predecessor, Travis was in the room, and he also honored Travis’ incredible work and investment in bringing the company to the place where it was.

And I would use words like grace to also describe those choices, but there’s also an incredible strategic value to naming the starting place for everybody in the room because in most cases, most people in that room played a role in getting to that starting place, and you’re acknowledging that.

CURT NICKISCH: You can call it grace. Somebody else might call it diplomatic or strategic. But yeah, I guess like it or not, it’s helpful to call out and honor the complexity of the way things have been done and also the change that’s happening.

ANNE MORRISS: Yeah, and the value. Sometimes honoring the past is also owning what didn’t work or what wasn’t working for stakeholders or segments of the employee team, and we see that around culture change. Sometimes you’ve got to acknowledge that it was not an equitable environment, but whatever the worker, everyone in that room is bringing that pass with them. So again, making it discussable and using it as the jumping off place is where we advise people to start.

Then you’ve earned the right to talk about the change mandate, which we suggest using clear and compelling language about the why. “This is what happened, this is where we are, this is the good and the bad of it, and here’s the case for change.”

And then the last part, which is to describe a rigorous and optimistic way forward. It’s a simple past, present, future arc, which will be familiar to human beings. We love stories as human beings. It’s among the most powerful currency we have to make sense of the world.

CURT NICKISCH: Yeah. Chronological is a pretty powerful order.

ANNE MORRISS: Right. But again, the change leaders we see really get it right, are investing an incredible amount of time into the storytelling part of their job. Ursula Burns, the Head of Xerox is famous for the months and years she spent on the road just telling the story of Xerox’s change, its pivot into services to everyone who would listen, and that was a huge part of her success.

CURT NICKISCH: So Friday or your fifth step, you end with empowering teams and removing roadblocks. That seems obvious, but it’s critical. Can you dig into that a little bit?

ANNE MORRISS: Yeah. Friday is the fun day. Friday’s the release of energy into the system. Again, you’ve now earned the right to go fast. You have a plan, you’re pretty confident it’s going to work. You’ve told the story of change the organization, and now you get to sprint. So this is about really executing with urgency, and it’s about a lot of the tactics of speed is where we focus in the book. So the tactics of empowerment, making tough strategic trade-offs so that your priorities are clear and clearly communicated, creating mechanisms to fast-track progress. At Etsy, CEO Josh Silverman, he labeled these projects ambulances. It’s an unfortunate metaphor, but it’s super memorable. These are the products that get to speed out in front of the other ones because the stakes are high and the clock is sticking.

CURT NICKISCH: You pull over and let it go by.

ANNE MORRISS: Yeah, exactly. And so we have to agree as an organization on how to do something like that. And so we see lots of great examples both in young organizations and big complex biotech companies with lots of regulatory guardrails have still found ways to do this gracefully.

And I think we end with this idea of conflict debt, which is a term we really love. Leanne Davey, who’s a team scholar and researcher, and anyone in a tech company will recognize the idea of tech debt, which is this weight the organization drags around until they resolve it. Conflict debt is a beautiful metaphor because it is this weight that we drag around and slows us down until we decide to clean it up and fix it. The organizations that are really getting speed right have figured out either formally or informally, how to create an environment where conflict and disagreements can be gracefully resolved.

CURT NICKISCH: Well, let’s talk about this speed more, right? Because I think this is one of those places that maybe people go wrong or take too long, and then you lose the awareness of the problem, you lose that urgency. And then that also just makes it less effective, right? It’s not just about getting the problem solved as quickly as possible. It’s also just speed in some ways helps solve the problem.

ANNE MORRISS: Oh, yeah. It really is the difference between imagining the change you want to lead and really being able to bring it to life. Speed is the thing that unlocks your ability to lead change. It needs a foundation, and that’s what Monday through Thursday is all about, steps one through four, but the finish line is executing with urgency, and it’s that urgency that releases the system’s energy, that communicates your priorities, that creates the conditions for your team to make progress.

CURT NICKISCH: Moving fast is something that entrepreneurs and tech companies certainly understand, but there’s also this awareness that with big companies, the bigger the organization, the harder it is to turn the aircraft carrier around, right? Is speed relative when you get at those levels, or do you think this is something that any company should be able to apply equally?

ANNE MORRISS: We think this applies to any company. The culture really lives at the level of team. So we believe you can make a tremendous amount of progress even within your circle of control as a team leader. I want to bring some humility to this and careful of words like universal, but we do think there’s some universal truths here around the value of speed, and then some of the byproducts like keeping fantastic people. Your best people want to solve problems, they want to execute, they want to make progress and speed, and the ability to do that is going to be a variable in their own equation of whether they stay or they go somewhere else where they can have an impact.

CURT NICKISCH: Right. They want to accomplish something before they go or before they retire or finish something out. And if you’re able to just bring more things on the horizon and have it not feel like it’s going to be another two years to do something meaningful.

ANNE MORRISS: People – I mean, they want to make stuff happen and they want to be around the energy and the vitality of making things happen, which again, is also a super infectious phenomenon. One of the most important jobs of a leader, we believe, is to set the metabolic pace of their teams and organizations. And so what we really dig into on Friday is, well, what does that look like to speed something up? What are the tactics of that?

CURT NICKISCH: I wonder if that universal truth, that a body in motion stays in motion applies to organizations, right? If an organization in motion stays in motion, there is something to that.

ANNE MORRISS: Absolutely.

CURT NICKISCH: Do you have a favorite client story to share, just where you saw speed just become a bit of a flywheel or just a positive reinforcement loop for more positive change at the organization?

ANNE MORRISS: Yeah. We work with a fair number of organizations that are on fire. We do a fair amount of firefighting, but we also less dramatically do a lot of fire prevention. So we’re brought into organizations that are working well and want to get better, looking out on the horizon. That work is super gratifying, and there is always a component of, well, how do we speed this up?

What I love about that work is there’s often already a high foundation of trust, and so it’s, well, how do we maintain that foundation but move this flywheel, as you said, even faster? And it’s really energizing because often there’s a lot of pent-up energy that… There’s a lot of loyalty to the organization, but often it’s also frustration and pent-up energy. And so when that gets released, when good people get the opportunity to sprint for the first time in a little while, it’s incredibly energizing, not just for us, but for the whole organization.

CURT NICKISCH: Anne, this is great. I think finding a way to solve problems better but also faster is going to be really helpful. So thanks for coming on the show to talk about it.

ANNE MORRISS: Oh, Curt, it was such a pleasure. This is my favorite conversation. I’m delighted to have it anytime.

HANNAH BATES: That was entrepreneur, leadership coach, and author Anne Morriss – in conversation with Curt Nickisch on HBR IdeaCast.

We’ll be back next Wednesday with another hand-picked conversation about business strategy from Harvard Business Review. If you found this episode helpful, share it with your friends and colleagues, and follow our show on Apple Podcasts, Spotify, or wherever you get your podcasts. While you’re there, be sure to leave us a review.

When you’re ready for more podcasts, articles, case studies, books, and videos with the world’s top business and management experts, you’ll find it all at HBR.org.

This episode was produced by Mary Dooe, Anne Saini, and me, Hannah Bates. Ian Fox is our editor. Special thanks to Rob Eckhardt, Maureen Hoch, Erica Truxler, Ramsey Khabbaz, Nicole Smith, Anne Bartholomew, and you – our listener. See you next week.

Subscribe On:

Latest in this series

This article is about strategy.

Decision making and problem solving
Strategy execution
Leadership and managing people
Collaboration and teams
Trustworthiness
Organizational culture

Partner Center

By using this site you agree to our use of cookies. Please refer to our privacy policy for more information. Close

7 Powerful Problem-Solving Root Cause Analysis Tools

The first step to solving a problem is to define the problem precisely. It is the heart of problem-solving.

Root cause analysis is the second important element of problem-solving in quality management. The reason is if you don't know what the problem is, you can never solve the exact problem that is hurting the quality.

Sustainable Compliance for Out of Specifications (OOS) Results, Deviations, and Corrective and Preventive Actions (CAPA)

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:

The Ishikawa Fishbone Diagram (IFD)
Pareto Chart
Failure Mode and Effects Analysis (FMEA)
Scatter Diagram
Affinity Diagram
Fault Tree Analysis (FTA)

1. The Ishikawa Fishbone Diagram IFD

The model introduced by Ishikawa (also known as the fishbone diagram) is considered one of the most robust methods for conducting root cause analysis. This model uses the assessment of the 6Ms as a methodology for identifying the true or most probable root cause to determine corrective and preventive actions. The 6Ms include:

Measurement,
Mother Nature- i.e., Environment

Related Training: Fishbone Diagramming

2. Pareto Chart

The Pareto Chart is a series of bars whose heights reflect the frequency or impact of problems. On the Chart, bars are arranged in descending order of height from left to right, which means the categories represented by the tall bars on the left are relatively more frequent than those on the right.

Related Training: EFFECTIVE INVESTIGATIONS AND CORRECTIVE ACTIONS (CAPA) Establishing and resolving the root causes of deviations, problems and failures

This model uses the 5 Why by asking why 5 times to find the root cause of the problem. It generally takes five iterations of the questioning process to arrive at the root cause of the problem and that's why this model got its name as 5 Whys. But it is perfectly fine for a facilitator to ask less or more questions depending on the needs.

Related training: Accident/Incident Investigation and Root Cause Analysis

4. Failure Mode and Effects Analysis (FMEA)

FMEA is a technique used to identify process and product problems before they occur. It focuses on how and when a system will fail, not if it will fail. In this model, each failure mode is assessed for:

Severity (S)
Occurrence (O)
Detection (D)

A combination of the three scores produces a risk priority number (RPN). The RPN is then provided a ranking system to prioritize which problem must gain more attention first.

Related Training: Failure Mode Effects Analysis

5. Scatter Diagram

A scatter diagram also known as a scatter plot is a graph in which the values of two variables are plotted along two axes, the pattern of the resulting points revealing any correlation present.

To use scatter plots in root cause analysis, an independent variable or suspected cause is plotted on the x-axis and the dependent variable (the effect) is plotted on the y-axis. If the pattern reflects a clear curve or line, it means they are correlated. If required, more sophisticated correlation analyses can be continued.

Related Training: Excel Charting Basics - Produce Professional-Looking Excel Charts

6. Affinity Diagram

Also known as KJ Diagram, this model is used to represent the structure of big and complex factors that impact a problem or a situation. It divides these factors into small classifications according to their similarity to assist in identifying the major causes of the problem.

7. Fault Tree Analysis (FTA)

The Fault Tree Analysis uses Boolean logic to arrive at the cause of a problem. It begins with a defined problem and works backward to identify what factors contributed to the problem using a graphical representation called the Fault Tree. It takes a top-down approach starting with the problem and evaluating the factors that caused the problem.

Finding the root cause isn't an easy because there is not always one root cause. You may have to repeat your experiment several times to arrive at it to eliminate the encountered problem. Using a scientific approach to solving problem works. So, its important to learn the several problem-solving tools and techniques at your fingertips so you can use the ones appropriate for different situations.

ComplianceOnline Trainings on Root Cause Analysis

P&PC, SPC/6Sigma, Failure Investigation, Root Cause Analysis, PDCA, DMAIC, A3 This webinar will define what are the US FDA's expectation for Production and Process Control / Product Realization, the use of statistical tehniques, 6 sigma, SPC, for establishing, controlling , and verifying the acceptability of process capability and product characteristics, product acceptance or validation and other studies. Non-conformance, OOS, deviations Failure Investigations, and Root Cause Analysis, PDCA, DMAIC, and similar project drivers to improvement, A# and similar dash boards.

Accident/Incident Investigation and Root Cause Analysis If a major workplace injury or illness occurred, what would you do? How would you properly investigate it? What could be done to prevent it from happening again? A properly executed accident/incident investigation drives to the root causes of the workplace accident to prevent a repeat occurrence. A good accident/incident investigation process includes identifying the investigation team, establishing/reviewing written procedures, identifying root causes and tracking of all safety hazards found to completion.

Root Cause Analysis - The Heart of Corrective Action This presentation will explain the importance of root cause analysis and how it fits into an effective corrective and preventive action system. It will cover where else in your quality management system root cause analysis can be used and will give examples of some of the techniques for doing an effective root cause analysis. Attendees will learn how root cause analysis can be used in process control.

Addressing Non-Conformances using Root Cause Analysis (RCA) RCA assumes that systems and events are interrelated. An action in one area triggers an action in another, and another, and so on. By tracing back these actions, you can discover where the issue started and how it grew into the problem you're now facing.

Introduction to Root Cause Investigation for CAPA If you have reoccurring problems showing up in your quality systems, your CAPA system is not effective and you have not performed an in-depth root cause analysis to be able to detect through proper problem solving tools and quality data sources, the true root cause of your problem. Unless you can get to the true root cause of a failure, nonconformity, defect or other undesirable situation, your CAPA system will not be successful.

Root Cause Analysis and CAPA Controls for a Compliant Quality System In this CAPA webinar, learn various regulations governing Corrective and Preventive Actions (CAPA) and how organization should collect information, analyze information, identify, investigate product and quality problems, and take appropriate and effective corrective and/or preventive action to prevent their recurrence.

Root Cause Analysis for CAPA Management (Shutting Down the Alligator Farm) Emphasis will be placed on realizing system interactions and cultural environment that often lies at the root of the problem and prevents true root cause analysis. This webinar will benefit any organization that wants to improve the effectiveness of their CAPA and failure investigation processes.

Root Cause Analysis for Corrective and Preventive Action (CAPA) The Quality Systems Regulation (21 CFR 820) and the Quality Management Standard for Medical Devices (ISO 13485:2003), require medical device companies to establish and maintain procedures for implementing corrective and preventive action (CAPA) as an integral part of the quality system.

Strategies for an Effective Root Cause Analysis and CAPA Program This webinar will provide valuable assistance to all regulated companies, a CAPA program is a requirement across the Medical Device, Diagnostic, Pharmaceutical, and Biologics fields. This session will discuss the importance, requirements, and elements of a root cause-based CAPA program, as well as detailing the most effective ways to determine root cause and describing the uses of CAPA data.

Legal Disclaimer

This piece of content and any of its enclosures, attachments or appendices, references are created to provide solely for information purpose. ComplianceOnline has made all effort to provide accurate information concerning the subject matter covered. This content is created from interpretation, and understanding of relevant and applicable information and it is not all inclusive. It can be best used in conjunction with your professional judgment and discretion.

However, this piece of content and any other ancillary items disseminated in connection with same are not necessarily prepared by a person licensed to practice law in a particular jurisdiction. This piece of content is not a substitute for the advice of an attorney. If you require legal or other expert advice, you should seek the services of a competent attorney or other professional.

ComplianceOnline necessarily is not, cannot and will not be liable for any claims, damages, or regulatory legal proceedings initiated as a consequence of you using whole or any part of the content present in this document. If any action, claim for damages, or regulatory proceedings is commenced against ComplianceOnline as a consequence of your use of this document, then and in that event, you agree to indemnify ComplianceOnline for such claims, and for any attorney's fees expended by ComplianceOnline in connection with defense of same.

Problem Solving And Decision Making Tools

Problem-solving and decision-making tools and techniques can be used to help in gathering the right information to make optimal decisions and learn from those decisions, as well as in the process of making those decisions. Often, the learning steps in the decision-making process are neglected, but it should not be. It is important to evaluate and analyze both the decision made and the process used in coming to the decision to ensure learning and enable continuous improvement.

A structured approach to problem-solving and decision making includes the following steps:

 Identifying and framing the issue or problem.

 Generating or determining possible courses of action and evaluating those alternatives.

 Choosing and implementing the best solution or alternative; and

 Reviewing and reflecting on the previous steps and outcomes

Mapping Techniques Mind Mapping In this structured brainstorming technique, ideas are organized on a “map” and the connections between them are made explicit. Mind mapping starts with an issue to be addressed placed in the center of the map. Ideas on causes, solutions, and so on radiate from the central theme. Questions such as who, what, where, why, when, and how are often helpful for problem-solving.

Process Mapping A process map, or flowchart, is a graphic depiction of a process showing inputs, outputs, and steps in the process. Depending on the purpose of the map, it can be high level or detailed.

The steps for creating a process map or flowchart are:

Assemble and train the team
Determine the boundaries of the process
Brainstorm the major process tasks and subtasks
Create a formal chart
Make corrections
Determine additional data needs

Activity and Role Lane Mapping Activity and role lane mapping can be a useful exercise to include in process mapping. List the process activities and the roles involved, and ask who performs the activity now. Then, take the role out of the activity so that “nurse records vital signs” becomes “record vital signs”, this type of analysis can help with process redesign and streaming.

Service Blueprinting Service blueprinting is a special form of process mapping, it begins by mapping the process from the point of view of the customer. The typical purpose of a service blueprint is to identify points where the service might fail to satisfy the customer and then redesign or add controls to the system to reduce or eliminate the possibility of failure.

Problem Identification Tools

Root-Cause Analysis Root-Cause Analysis is a structured, step-by-step technique for problem-solving. It aims to determine and correct the ultimate causes of a problem, not just the visible symptoms, to ensure that the problem does not happen again.

Five Whys technique The five whys technique consists of asking why the condition occurred, noting the answer, and then asking why for each answer over and over until the “root” causes are identified.

Cause-and-effect-diagram The cause-and-effect diagram is one of the seven basic quality tools, it is sometimes called a fishbone diagram (because it looks like the skeleton of a fish). The problem, or outcome of interest, is the “head” of the fish. The rest of the fishbone consists of a horizontal line leading to the problem statements and several branches, or “fishbone” vertical to the main line.

The branches represent different categories of causes.

Failure Mode and Effects Analysis (FMEA) FMEA is used to identify the ways in which a process (or a piece of equipment) might potentially fail, and its goal is eliminating or reducing the severity of such a potential failure.

Theory of Constraints The TOC maintains that every organization is subject to at least one constraint that limits it from moving toward or achieving its goal. Eliminating or alleviating the constraint can enable the organization to come closer to its goal. Constraints can be physical (e.g., the capacity of a machine) or nonphysical (e.g., an organizational procedure).

Analytical Tools

Optimization Optimization, or mathematical programming, is a technique used to determine the optimal allocation of limited resources given the desired goal. For example, the resources might be people, money, or equipment. Of all possible resources’ allocation, the goal or objective is to find the allocation that maximizes or minimize some numerical quantity such as profit or cost.

Linear Programming

Decision Analysis Decision analysis is a process for examining and evaluating decisions in a structured manner. A decision tree is a graphic representation of the order of events in a decision process. It is a structured process that enables an evaluation of the risks and rewards of choosing a particular course of action. In constructing a decision tree, events are linked from left to right in the order in which they would occur. Three types of events, represented by nodes, can occur: decision or choice events (squares), chance events (circles), and outcomes (triangles)

Strategy and the Balanced Scorecard

Quality management: focus on lean-six sigma, project management.

Become a Project Manager
Certification

Problem Solving Techniques for Project Managers

Learn which problem solving techniques and strategies can help you effectively handle the challenges you face in your projects.

Problem Solving Techniques: A 5-Step Approach

Some problems are small and can be resolved quickly. Other problems are large and may require significant time and effort to solve. These larger problems are often tackled by turning them into formal projects.

"A project is a problem scheduled for solution."

- Joseph M. Juran

Problem Solving is one of the Tools & Techniques used for Managing Quality and Controlling Resources.

Modules 8 and 9 of the PM PrepCast cover Project Quality Management and Project Resource Management.

Consider this study program if you're preparing to take your CAPM or PMP Certification exam.

Disclosure: I may receive a commission if you purchase the PM PrepCast with this link.

Whether the problem you are focusing on is small or large, using a systematic approach for solving it will help you be a more effective project manager.

This approach defines five problem solving steps you can use for most problems...

Define the Problem

Determine the causes, generate ideas, select the best solution, take action.

The most important of the problem solving steps is to define the problem correctly. The way you define the problem will determine how you attempt to solve it.

For example, if you receive a complaint about one of your project team members from a client, the solutions you come up with will be different based on the way you define the problem.

If you define the problem as poor performance by the team member you will develop different solutions than if you define the problem as poor expectation setting with the client.

Once you have defined the problem, you are ready to dig deeper and start to determine what is causing it. You can use a fishbone diagram to help you perform a cause and effect analysis.

If you consider the problem as a gap between where you are now and where you want to be, the causes of the problem are the obstacles that are preventing you from closing that gap immediately.

This level of analysis is important to make sure your solutions address the actual causes of the problem instead of the symptoms of the problem. If your solution fixes a symptom instead of an actual cause, the problem is likely to reoccur since it was never truly solved.

Once the hard work of defining the problem and determining its causes has been completed, it's time to get creative and develop possible solutions to the problem.

Two great problem solving methods you can use for coming up with solutions are brainstorming and mind mapping .

After you come up with several ideas that can solve the problem, one problem solving technique you can use to decide which one is the best solution to your problem is a simple trade-off analysis .

To perform the trade-off analysis, define the critical criteria for the problem that you can use to evaluate how each solution compares to each other. The evaluation can be done using a simple matrix. The highest ranking solution will be your best solution for this problem.

Pass your PMP Exam!

The PM Exam Simulator is an online exam simulator.

Realistic exam sample questions so you can pass your CAPM or PMP Certification exam.

Disclosure: I may receive a commission if you purchase the PM Exam Simulator with this link.

Once you've determined which solution you will implement, it's time to take action. If the solution involves several actions or requires action from others, it is a good idea to create an action plan and treat it as a mini-project.

Using this simple five-step approach can increase the effectiveness of your problem solving skills .

For more problem solving strategies and techniques, subscribe to my newsletter below.

Do You Want More Project Management Tips?

Subscribe to Project Success Tips , my FREE Project Management Newsletter where I share tips and techniques that you can use to get your Project Management Career off to a great start .

As a BONUS for signing up, you'll receive access to my Subscribers Only Download Page ! This is where you can download my " Become A Project Manager Checklist " and other project management templates.

Don't wait...

Become a PM
Problem Solving Techniques

New! Comments

Home Privacy Policy About Contact

Project-Management-Skills.com

Every day, billions of people globally use their computers or mobile devices to access the Internet. Invariably, some of those users attempt to access a website that is either slow to load or prone to crashing. One reason that the website underperformed is that too many people were trying to access the site at the same time, overwhelming the servers. However, it might also be indicative of a larger concern, including DNS misconfiguration, a lasting server failure or a malicious attack from a bad actor.

Incidents are errors or complications in IT service that need remedying. Many of these incidents are temporary challenges that require a specific remedy, but those that point to underlying or more complicated issues that require more comprehensive addressing are called problems .

This explains the existence of both incident and problem management, two important processes for issue and error control, maintaining uptime, and ultimately, delivering a great service to customers and other stakeholders. Organizations increasingly depend on digital technologies to serve their customers and collaborate with partners. An organization’s technology stack can create new and exciting opportunities to grow its business. But an error in service can also create exponential disruptions and damage to its reputation and financial health.

Incident management is how organizations identify, track, and resolve incidents that might disrupt normal business processes . It is often a reactive process where an incident occurs and the organization provides an incident response as quickly as possible.

An increase in organizations pursuing digital transformation and other technology-driven operations makes incident management even more important given the dependence on technology to deliver solutions to customers.

Organizations’ IT services are increasingly made up of a complex system of applications, software, hardware and other technologies, all of which can be interdependent. Individual processes can break down, disrupting the service that they provide to customers, costing the business money and creating reputational issues. Organizations have embraced advanced development operations ( DevOps ) procedures to minimize incidents, but they need a resolution process for when they occur.

Every day, organizations encounter and need to manage minor and major incidents, all of which have the potential to disrupt normal business functions. Organizations need to pay attention to several types of incidents, including unplanned interruptions like system outages, network configuration issues, bugs, security incidents, data loss and more.

As technology stacks have increased in complexity, it becomes even more important to strategically manage the incident management process. To ensure that everyone in the organization knows what to do if they encounter an incident.

Incident management systems have evolved from blunt tools where employees recorded incidents that they observed (which might happen hours after occurring). To a robust, always-on practice with automation and self-service incident management software, enabling anyone in the organization to report an incident to the service desk.

It is important to resolve incidents immediately and prevent them from happening again. This allows organizations to uphold their service-level agreement (SLA), which may guarantee a certain amount of uptime or access to services. Failing to adhere to an SLA might put your organization at legal or reputational risk.

The incident manager is the key stakeholder of the incident management process. An incident manager is responsible for managing the response to an incident and communicating progress to key stakeholders. It is a complex IT services role that requires the employee to perform under stressful conditions while communicating with stakeholders with different roles and priorities in the business.

Problem management is intended to prevent the incident from reoccurring by addressing the root cause. It logically follows incident management, especially if that incident has occurred several times and should likely be diagnosed as a problem or known error.

Incident management without problem management only addresses symptoms and not the underlying cause (that is, the root cause), leading to a likelihood that similar incidents will occur in the future. Effective problem management identifies a permanent solution to problems, decreasing the number of incidents an organization will have to manage in the future.

A problem management team can either engage in reactive or proactive problem management, depending on what incidents they observed and what historical data they have.

There is one major difference to consider when observing incidents versus problems: short-term versus long-term goals.

Incident management is more concerned with intervening on an issue instance with the stated goal of getting that service back online without causing any additional issues. It is a short-term tool to keep the service running at that very moment.

Problem management focuses more on the long-term response, addressing any potential underlying cause as part of a larger potential issue (that is, a problem).

Organizations try to keep their IT infrastructure in good standing by using IT service management (ITSM) to govern the implementation, delivery, and management of services that meet the needs of end users. ITSM aims to minimize unscheduled downtime and ensure that every IT resource works as intended for every end user.

Issues arise regardless of how much effort organizations put into their ITSM. An organization’s ability to address and fix unforeseen issues before they turn into larger problems can be a huge competitive advantage. An IT service breaking down once is considered an incident. For example, too many people trying to access a server may cause it to crash, creating an incident that your organization needs to fix. Incident management relates to fixing that particular issue affecting your users as quickly and carefully as possible. In this case, an incident manager can contact the organization’s employees and ask them to exit programs while the organization resolves the issue.

Incident management and problem management are both governed by the Information Technology Infrastructure Library (ITIL) , a widely adopted guidance framework for implementing and documenting both management approaches. ITIL creates the structure for responding reactively to incidents as they occur. The most up-to-date release at the time of writing is ITIL 4.

It provides a library of best practices for managing IT assets and improving IT support and service levels. ITIL processes connect IT services to business operations so that they can change when business objectives change.

A key component of ITIL is the configuration management database (CMDB), which tracks and manages the interdependence of all software, IT components, documents, users and hardware that is required to deliver an IT service. ITIL also creates a distinction between incident management and problem management.

A constantly crashing server may represent a larger, systematic problem, like hardware failure or misconfiguration. The crashes may continue if the IT service team fails to uncover the root cause and map a solution to the underlying issue. In this case, the response may require an escalation to problem management, which is concerned with fixing repeated incidents.

Problem management provides a root cause analysis for the problem and a recommended solution, which identifies the required resources to prevent it from happening again.

Effective incident and problem management encompasses a structured workflow that requires real-time monitoring, automation, and dedicated workers coordinating to resolve issues as quickly as possible to avoid unnecessary downtime or business interruptions. Both forms of management feature several recurring components that organizations should know.

Incident management

Incident identification: To resolve an incident, you must first observe it. Organizations increasingly automate systems to detect and send notifications when incidents occur. But many also require a human to ensure that an incident is happening, determine whether it requires intervention and confirm the correct approach. For instance, a server crash is a common incident with digital-first organizations. When the server goes offline, an automated tool or employee may identify the incident, initiating the incident management process.
Incident reporting: This is the formal process for cataloging an incident record that a machine or human observed. It includes incident logging, the process by which an individual or system assigns a respondent to the issue, categorizes the incident and identifies the impacted business unit and the resolution date.
Incident resolution prioritization: Software and IT services are often interdependent in modern organizations, so one incident can have a knock-on effect on other services. Sometimes an incident occurs as part of a larger systematic failure, which can set off a catastrophic chain of events. For example, if multiple servers crash, the business analytics team may not be unable to access the data that they need, or the company’s knowledge workers may not be able to log in and access the software for their jobs. Or, if a company’s API fails, the organization’s customers may be unable to access the information they need to serve their end users. In both situations, the response team must assess the entire scope of the problem and prioritize which incidents to resolve to minimize the short-term and long-term effects on the business. They can prioritize based on which incident has the greatest impact on the organization.
Incident response and containment: A response team—potentially aided by automated software or systems—then engages in troubleshooting the incident to minimize business interruptions. The response team usually comprises internal IT team members, external service providers and operations staff, as needed.
Incident resolution: This is critical for IT operations to return to normal services. Potential resolutions to an IT incident include taking the incorrectly working server offline, creating a patch, establishing a workaround, or changing the hardware.
Incident documentation and communication: This is a crucial step of the incident lifecycle to help avoid future incidents. Many companies create knowledge bases for their incident reports where employees can search to help them solve an incident that may have occurred in the past. In addition, new employees can learn about what incidents the company has recently faced and the solutions that are applied, so they can more readily help with the next incident. Documentation is also critical for determining whether an issue is recurring and becoming a problem, increasing the need for problem management.

Problem management

Problem assessment: The organization now must determine whether the incident should be categorized as a problem record or if it is just an unrelated incident. The former means that it now becomes a part of problem management.
Problem logging and categorization: The IT team must now log the identified problem and track each occurrence.
Root cause analysis: The organization should study the underlying issues behind these problems and develop a roadmap to create a long-term solution. One way to accomplish this is by asking recursive “how” questions at each step of the way until one can identify the original problem.
Problem-solving: An IT team that understands the problem and its root cause can now solve the problem. It might involve a quick or protracted response depending on the severity or complexity of the problem.
Postmortem: A postmortem where relevant employees discuss the incident(s), root causes and response to the problem is a critical component of any transparent organization that is interested in maintaining uptime and providing customers excellent service. Postmortems provide everyone an opportunity to discuss how to improve without judging any employee or casting blame for any issue. The purpose of the postmortem is to find out what happened and to define actions to improve the organization. It can also provide insights into how the team can better respond to future incidents. It can identify whether an organization requires change management to revitalize and streamline its incident and problem management. The best ideas and best results come from postmortem meetings that are open and honest. Team culture should assure all members that this is a way to discover how the team can improve IT services and not a way to find someone to blame. Teams will quickly understand if this is an honest and supportive exercise or not.

Organizations often assess incident managers and the incident management process based on several key performance indicators (KPIs):

Mean time to take action: An incident requires detection, response, and repair. Organizations judge the health of their incident management service by the mean time to alert or acknowledge (MTTA) and mean time to respond and mean time to repair (MTTR) , all of which provide a clear picture of how the organization can respond to incidents.
Mean time between failures (MTBF): The time between incidents for any IT service. MTBF , which happens more frequently than expected, might signify larger problems requiring a more proactive stance.
Uptime: The time your services are available and working as intended. Too little uptime can put an organization at risk of violating its SLA with end users and otherwise losing business to competitors.
Incidents and problems reported: The number of incidents an incident manager has reported in a given time frame. Increasing incidents reported may be a sign of a larger problem.

Companies with comprehensive problem and incident management plans can quickly respond to incidents and outperform their competition. The following are some benefits:

Increased customer satisfaction and loyalty: Customers expect that the services and products they pay for will work whenever needed. More and more products are software (or connected to software, like smart devices). A server crashing at a company making smart doorbells means that people cannot enter their homes or apartments. A hotel booking website having a DNS error issue loses revenue that day and potentially loses a lifetime customer to a competitor. The impact of incidents and problems can weigh heavily on an organization. The ones that respond to incidents quicker and minimize downtime will earn the loyalty of customers who are likely to switch providers if they’re unhappy. A robust incident management strategy saves companies money by decreasing downtime and the likelihood of a customer or employee leaving, both of which are associated with hard costs.
Increased employee satisfaction: A severe IT incident affects employees as much as customers. Employees that can’t access critical business software can’t do their jobs. Their work piles up as the company tries to get things back online. They may must work overtime or during the weekend to catch up, creating stress and threatening their morale.
Meeting SLA requirements: Organizations detail customer expectations for their products and services in an SLA. The organization might be at risk for legal action if they fail to withhold the terms of service in their SLAs and potentially lose customers to competitors.

IBM® Turbonomic® integrates with your existing ITOps solutions, bridges siloed teams and data, and turns manual, reactive processes into continuous application resource optimization while safely reducing cloud consumption by 33%.

IBM Cloud Pak® for AIOps , the self-hosted option for incident management, achieves proactive incident management and automated remediation to reduce customer-facing outages by up to 50% and mean time to recovery (MTTR) by up to 50%.

Get our newsletters and topic updates that deliver the latest thought leadership and insights on emerging trends.

Read the Total Economic Impact™ of IBM Turbonomic study to learn more

LSE Authors
Subscribe to our newsletter

Ravi Sawhney

May 24th, 2024, how to enhance generative ai’s problem-solving capabilities and boost workplace productivity.

0 comments | 6 shares

Estimated reading time: 5 minutes

In 2024, enterprise software companies are betting on generative AI, in a quest to enhance productivity. OpenAI has recently released GPT-4o, which includes interpretation and generation of voice and vision. Ravi Sawhney discusses how to incorporate this technology into end-user workplace technology and introduces the concept of multi-agent workflows, an idea that allows organisations to imitate entire knowledge teams.

Back in 2021 I wrote a piece for LSE Business Review in which I demonstrated the power of OpenAI’s GPT3 in being able to interpret human language by converting it into code. At the time, the technology was in its infancy and didn’t generate the spark ChatGPT did when it was released to the public in November 2022, that moment truly ignited the generative AI (GenAI) boom. Here I provide some personal thoughts on why GenAI matters and the challenges in using it for work. I also introduce the concept of multi-agent workflows as a method to boost the potential of where we can go.

It’s all about productivity

In 2024, nearly all enterprise software companies are making bets on GenAI, which perhaps has taken away some of the limelight from existing machine learning approaches such as supervised and unsupervised learning that are still crucial parts of any complete AI framework. The premise of why organisations are doing this all ties back to what got me interested in this technology in the first place: productivity.

In its more basic form, GenAI can be thought of as the most powerful autocomplete technology we have ever seen. The ability of large language models (LLMs) to predict the next word is so good that it can step in and perform knowledge worker tasks such as classifying, editing, summarising, questions and answers as well as content creation.

Additionally, variations of this technology can operate across modalities, much like human senses, to include interpretation and generation across voice and vision. In fact, in 2024 the nomenclature is shifting from LLMs to large multimodal models (LMMs) and the recent release of GPT-4o from OpenAI is evidence of this. Whether the step-in process is advisory, with a human in-the-loop or full-blown automated decision-making, it is not hard to see how GenAI has the potential to deliver transformational boost to labour productivity across the knowledge working sector. A recent paper on this very topic estimated that, when used to drive task automation, GenAI could boost labour productivity by 3.3 percentage points annually, creating $4.4 trillion of value to global GDP.

The productivity benefits perhaps take us closer to the aspiration Keynes had when he wrote Economic Possibilities for our Grandchildren in 1930, in which he forecast that in a hundred years, thanks to technological advancements improving the standard of living, we could all be doing 15-hour work weeks. This sentiment was echoed by Nobel Prize winner in economics Sir Chirstopher Pissarides, who said ChatGPT could herald 4-day work week.

So, if the potential to meaningfully transform how we work is right in front of us and is being developed at breakneck speed, then how do we bridge the gap to make this possibility a reality?

Trust and tooling

Two typical challenges need to be considered when incorporating this technology into end-user workplace technology. The largest, arguably, is managing the trust issue. By default, LLMs do not have access to your own private information, so asking it about a very specific support issue on your own product will typically produce a confident but inaccurate response, typically referred to as “hallucinations”. Fine-tuning LLMs on your own data is one option, albeit an expensive one given the hardware requirements. A much more approachable method that has become commonplace in the community is referred to as retrieval-augmented-generation (RAG) . This is where your private data is brought into the query prompt using the power of embeddings to perform lookups from a given query. This resultant response is synthesised from this data along with the LLM’s existing knowledge, resulting in something that could be considered useful, albeit with some appropriate user guidance.

The second challenge is maths. While LLMs, with some careful prompting, could create a unique, compelling and (importantly) convincing story from scratch, it would struggle with basic to intermediate maths, depending on the foundation model you are using. Here the community has introduced the concept of tooling or sometimes referred to as agents. In this paradigm, the LLM can categorise the query being asked and, rather than trying to answer it, call the appropriate ‘tool’ for the job . For example, if being asked about the weather outside, it might call a weather API service. If being asked to perform math, it would route the query to a calculator API. And if it needs to retrieve information from a database, it might convert the request to SQL or Pandas, execute the resulting code in a sandbox environment and return the result to the user, who might be none the wiser about what is going on under the hood.

The potential of multi-agent workflows

Agent frameworks with tooling are expanding the possibilities of how LLMs can be used to solve real-world problems today. However, they still largely fall short of being able to perform complex knowledge-work tasks due to limitations such as lack of memory, planning and reasoning capabilities. Multi-agent frameworks present an opportunity to tackle some of these challenges. A good way to understand how they could work is to draw a contrast with System 1 and System 2 thinking , popularised by Daniel Kahneman.

Think of System 1 as your gut instinct: fast, automatic and intuitive. In the world of LLMs, that’s like the model’s ability to generate human-like responses based on its vast training data. In contrast, System 2 thinking is slower, more deliberate, and logical, representing the model’s capacity for structured, step-by-step problem-solving and reasoning.

To fully unleash the potential of LLMs, we need to develop techniques that leverage both System 1 and System 2 capabilities. By breaking down complex tasks into smaller, manageable steps, we can guide LLMs to perform more structured and reliable problem-solving, akin to how humans would solve challenges.

Consider a team of agents, each assigned a specific role through prompt engineering, working together to tackle a single goal. That’s essentially what agent workflows, or sometimes referred to as agentic workflows, do for LLMs. Each agent is responsible for a specific subtask, and they communicate with each other, passing information and results back and forth until the overall task is complete. By designing prompts that encourage logical reasoning, step-by-step problem-solving, and collaboration with other agents, we can create a system that mimics the deliberate and rational thinking associated with System 2.

Here is where this gets exciting: agent workflows could allow us to imitate entire knowledge teams. Imagine a virtual team of AI agents, each with its workflow’s own specialism, collaborating to solve problems and make decisions just like a human team would. This could revolutionise the way we work, allowing us to tackle more complex challenges with zero or minimal human-in-the-loop supervision. It also opens the idea of allowing us to simulate how teams will react to events in a sandbox environment, where every team member is modelled as an agent in the workflow. The conversational outputs could even be saved for retrieval latter, serving as long-term memory.

By combining the raw power of System 1 thinking with the structured reasoning of System 2, we can create AI systems that not only generate human-like responses but can also tackle more complex tasks and move towards solving problems. The future of work is here, and it’s powered by the symbiosis of human ingenuity and artificial intelligence.

Authors’ disclaimer: All views expressed are my own.
This blog post represents the views of the author(s), not the position of LSE Business Review or the London School of Economics and Political Science.
Featured image provided by Shutterstock
When you leave a comment, you’re agreeing to our Comment Policy .

About the author

Ravi Sawhney is Head of Buyside Execution at Bloomberg LP. He has wide experience in the financial markets. Ravi holds a Bsc Hons in economics from LSE.

How to ensure future brain technologies will help and not harm society

March 10th, 2017.

How can businesses measure social media influence to create value?

September 8th, 2015.

How to help AI developers understand the societal implications of their creations

January 15th, 2024.

Blockchain can help mitigate investment risk for the pharmaceutical industry

April 30th, 2018.

How it works

For Business

Join Mind Tools

Self-Assessment • 20 min read

How Good Is Your Problem Solving?

Use a systematic approach..

By the Mind Tools Content Team

Good problem solving skills are fundamentally important if you're going to be successful in your career.

But problems are something that we don't particularly like.

They're time-consuming.

They muscle their way into already packed schedules.

They force us to think about an uncertain future.

And they never seem to go away!

That's why, when faced with problems, most of us try to eliminate them as quickly as possible. But have you ever chosen the easiest or most obvious solution – and then realized that you have entirely missed a much better solution? Or have you found yourself fixing just the symptoms of a problem, only for the situation to get much worse?

To be an effective problem-solver, you need to be systematic and logical in your approach. This quiz helps you assess your current approach to problem solving. By improving this, you'll make better overall decisions. And as you increase your confidence with solving problems, you'll be less likely to rush to the first solution – which may not necessarily be the best one.

Once you've completed the quiz, we'll direct you to tools and resources that can help you make the most of your problem-solving skills.

How Good Are You at Solving Problems?

Instructions.

For each statement, click the button in the column that best describes you. Please answer questions as you actually are (rather than how you think you should be), and don't worry if some questions seem to score in the 'wrong direction'. When you are finished, please click the 'Calculate My Total' button at the bottom of the test.

Answering these questions should have helped you recognize the key steps associated with effective problem solving.

This quiz is based on Dr Min Basadur's Simplexity Thinking problem-solving model. This eight-step process follows the circular pattern shown below, within which current problems are solved and new problems are identified on an ongoing basis. This assessment has not been validated and is intended for illustrative purposes only.

Below, we outline the tools and strategies you can use for each stage of the problem-solving process. Enjoy exploring these stages!

Step 1: Find the Problem (Questions 7, 12)

Some problems are very obvious, however others are not so easily identified. As part of an effective problem-solving process, you need to look actively for problems – even when things seem to be running fine. Proactive problem solving helps you avoid emergencies and allows you to be calm and in control when issues arise.

These techniques can help you do this:

PEST Analysis helps you pick up changes to your environment that you should be paying attention to. Make sure too that you're watching changes in customer needs and market dynamics, and that you're monitoring trends that are relevant to your industry.

Risk Analysis helps you identify significant business risks.

Failure Modes and Effects Analysis helps you identify possible points of failure in your business process, so that you can fix these before problems arise.

After Action Reviews help you scan recent performance to identify things that can be done better in the future.

Where you have several problems to solve, our articles on Prioritization and Pareto Analysis help you think about which ones you should focus on first.

Step 2: Find the Facts (Questions 10, 14)

After identifying a potential problem, you need information. What factors contribute to the problem? Who is involved with it? What solutions have been tried before? What do others think about the problem?

If you move forward to find a solution too quickly, you risk relying on imperfect information that's based on assumptions and limited perspectives, so make sure that you research the problem thoroughly.

Step 3: Define the Problem (Questions 3, 9)

Now that you understand the problem, define it clearly and completely. Writing a clear problem definition forces you to establish specific boundaries for the problem. This keeps the scope from growing too large, and it helps you stay focused on the main issues.

A great tool to use at this stage is CATWOE . With this process, you analyze potential problems by looking at them from six perspectives, those of its Customers; Actors (people within the organization); the Transformation, or business process; the World-view, or top-down view of what's going on; the Owner; and the wider organizational Environment. By looking at a situation from these perspectives, you can open your mind and come to a much sharper and more comprehensive definition of the problem.

Cause and Effect Analysis is another good tool to use here, as it helps you think about the many different factors that can contribute to a problem. This helps you separate the symptoms of a problem from its fundamental causes.

Step 4: Find Ideas (Questions 4, 13)

With a clear problem definition, start generating ideas for a solution. The key here is to be flexible in the way you approach a problem. You want to be able to see it from as many perspectives as possible. Looking for patterns or common elements in different parts of the problem can sometimes help. You can also use metaphors and analogies to help analyze the problem, discover similarities to other issues, and think of solutions based on those similarities.

Traditional brainstorming and reverse brainstorming are very useful here. By taking the time to generate a range of creative solutions to the problem, you'll significantly increase the likelihood that you'll find the best possible solution, not just a semi-adequate one. Where appropriate, involve people with different viewpoints to expand the volume of ideas generated.

Tip: Don't evaluate your ideas until step 5. If you do, this will limit your creativity at too early a stage.

Step 5: Select and Evaluate (Questions 6, 15)

After finding ideas, you'll have many options that must be evaluated. It's tempting at this stage to charge in and start discarding ideas immediately. However, if you do this without first determining the criteria for a good solution, you risk rejecting an alternative that has real potential.

Decide what elements are needed for a realistic and practical solution, and think about the criteria you'll use to choose between potential solutions.

Paired Comparison Analysis , Decision Matrix Analysis and Risk Analysis are useful techniques here, as are many of the specialist resources available within our Decision-Making section . Enjoy exploring these!

Step 6: Plan (Questions 1, 16)

You might think that choosing a solution is the end of a problem-solving process. In fact, it's simply the start of the next phase in problem solving: implementation. This involves lots of planning and preparation. If you haven't already developed a full Risk Analysis in the evaluation phase, do so now. It's important to know what to be prepared for as you begin to roll out your proposed solution.

The type of planning that you need to do depends on the size of the implementation project that you need to set up. For small projects, all you'll often need are Action Plans that outline who will do what, when, and how. Larger projects need more sophisticated approaches – you'll find out more about these in the article What is Project Management? And for projects that affect many other people, you'll need to think about Change Management as well.

Here, it can be useful to conduct an Impact Analysis to help you identify potential resistance as well as alert you to problems you may not have anticipated. Force Field Analysis will also help you uncover the various pressures for and against your proposed solution. Once you've done the detailed planning, it can also be useful at this stage to make a final Go/No-Go Decision , making sure that it's actually worth going ahead with the selected option.

Step 7: Sell the Idea (Questions 5, 8)

As part of the planning process, you must convince other stakeholders that your solution is the best one. You'll likely meet with resistance, so before you try to “sell” your idea, make sure you've considered all the consequences.

As you begin communicating your plan, listen to what people say, and make changes as necessary. The better the overall solution meets everyone's needs, the greater its positive impact will be! For more tips on selling your idea, read our article on Creating a Value Proposition and use our Sell Your Idea Skillbook.

Step 8: Act (Questions 2, 11)

Finally, once you've convinced your key stakeholders that your proposed solution is worth running with, you can move on to the implementation stage. This is the exciting and rewarding part of problem solving, which makes the whole process seem worthwhile.

This action stage is an end, but it's also a beginning: once you've completed your implementation, it's time to move into the next cycle of problem solving by returning to the scanning stage. By doing this, you'll continue improving your organization as you move into the future.

Problem solving is an exceptionally important workplace skill.

Being a competent and confident problem solver will create many opportunities for you. By using a well-developed model like Simplexity Thinking for solving problems, you can approach the process systematically, and be comfortable that the decisions you make are solid.

Given the unpredictable nature of problems, it's very reassuring to know that, by following a structured plan, you've done everything you can to resolve the problem to the best of your ability.

This assessment has not been validated and is intended for illustrative purposes only. It is just one of many Mind Tool quizzes that can help you to evaluate your abilities in a wide range of important career skills.

If you want to reproduce this quiz, you can purchase downloadable copies in our Store .

You've accessed 1 of your 2 free resources.

Get unlimited access

Discover more content

4 logical fallacies.

Avoid Common Types of Faulty Reasoning

Problem Solving

How to solve problems using the Cause and Effect Analysis technique

Add comment

Comments (2)

Afkar Hashmi

😇 This tool is very useful for me.

over 1 year

Very impactful

Gain essential management and leadership skills

Busy schedule? No problem. Learn anytime, anywhere.

Subscribe to unlimited access to meticulously researched, evidence-based resources.

Join today and save on an annual membership!

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

How to create psychological safety at work.

Speaking up without fear

How to Guides

Pain Points Podcast - Presentations Pt 1

How do you get better at presenting?

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

Dealing with manipulative people.

Standing Your Ground

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

Decision Making

Member Podcast

IMAGES

Problem Solving Methods Steps Process Examples
5 step problem solving method
Problem Solving Infographic 10 Steps Concept Vector Image
Problem-Solving Strategies: Definition and 5 Techniques to Try
Definitive Guide to Problem Solving Techniques
example of a problem solving tool

VIDEO

Problem solving tools
Problem Solving tools -part2
Problem Solving Tools- 8D and Fishbone- Part2.1
Problem Solving Techniques
Aa013
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
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.
Problem management: 8 steps to better problem solving
Summary. Problem management is an 8 step framework most commonly used by IT teams. You can use problem management to solve for repeating major incidents. By organizing and structuring your problem solving, you can more effectively get to the root cause of high-impact problems—and devise a solution. Solving the root cause prevents recurrence ...
Definitive Guide to Problem Solving Techniques
Balance divergent and convergent thinking. Ask problems as questions. Defer or suspend judgement. Focus on "Yes, and…" rather than "No, but…". According to Carella, "Creative problem solving is the mental process used for generating innovative and imaginative ideas as a solution to a problem or a challenge.
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 ...
Problem Solving
Leadership and Management > Problem Solving. Problem Solving. 56 Resources. Problems can occur at any time, and solutions often need to be found quickly. Delve into this wide variety of tools that will help you to identify the source of a problem, brainstorm solutions and select the best option. Explore Problem Solving topics .
The McKinsey guide to problem solving
May 14, 2023 - Leaders today are confronted with more problems, of greater magnitude, than ever before. In these volatile times, it's natural to react based on what's worked best in the past. But when you're solving the toughest business challenges on an ongoing basis, it's crucial to start from a place of awareness.
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.
How to master the seven-step problem-solving process
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].
How To Solve A Problem Like A Leader
Leaders often employ many systematic and less planned tools and techniques to solve complex problems, such as using evidence-based and metricized approaches to solving known and unknown issues. In ...
Problem Solving Strategies for the Workplace [2024] • Asana
4 steps to better problem solving. While it might be tempting to dive into a problem head first, take the time to move step by step. Here's how you can effectively break down the problem-solving process with your team: 1. Identify the problem that needs to be solved. One of the easiest ways to identify a problem is to ask questions.
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.
Lean Problem Solving
The Four Types of Problems. Type 1: Troubleshooting: reactive problem-solving that hinges upon rapidly returning abnormal conditions to known standards.It provides some immediate relief but does not address the root cause. Type 2: Gap from Standard: structured problem-solving that focuses on defining the problem, setting goals, analyzing the root cause, and establishing countermeasures, checks ...
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.
PDF 4/22/2020 Problem-Solving Tools
NGT is used to generate and evaluate or rank a series of actions or solutions. It is often used after a brainstorming session to organize and evaluate the products of the brainstorming session. The problem or decision is stated by the facilitator. Ideas are generated or imported from a previous brainstorming session.
The McKinsey Mind: Understanding and Implementing the Problem-Solving
The McKinsey Mind: Understanding and Implementing the Problem-Solving Tools and Management Techniques of the World's Top Strategic Consulting Firm [Ethan Rasiel, Paul N. Friga] on Amazon.com. *FREE* shipping on qualifying offers. The McKinsey Mind: Understanding and Implementing the Problem-Solving Tools and Management Techniques of the World's Top Strategic Consulting Firm
A Better Framework for Solving Tough Problems
Start with trust and end with speed. May 22, 2024. When it comes to solving complicated problems, the default for many organizational leaders is to take their time to work through the issues at hand.
7 Powerful Problem-Solving Root Cause Analysis Tools
It is the heart of problem-solving. Root cause analysis is the second important element of problem-solving in quality management. The reason is if you don't know what the problem is, you can never solve the exact problem that is hurting the quality. Manufacturers have a variety of problem-solving tools at hand.
7 Problem-Solving Skills That Can Help You Be a More ...
Although problem-solving is a skill in its own right, a subset of seven skills can help make the process of problem-solving easier. These include analysis, communication, emotional intelligence, resilience, creativity, adaptability, and teamwork. 1. Analysis. As a manager, you'll solve each problem by assessing the situation first.
Problem Solving And Decision Making Tools
A structured approach to problem-solving and decision making includes the following steps: Identifying and framing the issue or problem. Generating or determining possible courses of action and evaluating those alternatives. Choosing and implementing the best solution or alternative; and.
Problem Solving Techniques & Strategies for Project Managers
Problem Solving is one of the Tools & Techniques used for Managing Quality and Controlling Resources. Modules 8 and 9 of the PM PrepCast cover Project Quality Management and Project Resource Management. Consider this study program if you're preparing to take your CAPM or PMP Certification exam. Disclosure: I may receive a commission if you ...
7 Basic Quality Tools: Quality Management Tools
Quality Glossary Definition: Seven tools of quality "The Old Seven." "The First Seven." "The Basic Seven." Quality pros have many names for these seven basic tools of quality, first emphasized by Kaoru Ishikawa, a professor of engineering at Tokyo University and the father of "quality circles."Start your quality journey by mastering these tools, and you'll have a name for them too: indispensable.
The Problem-Solving Process
By the Mind Tools Content Team Problem-solving is an important part of planning and decision-making. The process has much in common with the decision-making process, and in the case of complex decisions, can form part of the process itself.
Incident management vs. Problem Management
Incident management without problem management only addresses symptoms and not the underlying cause (that is, the root cause), leading to a likelihood that similar incidents will occur in the future. Effective problem management identifies a permanent solution to problems, decreasing the number of incidents an organization will have to manage ...
INQUIRE: Healthcare Project Planning Simplified
Enter the INQUIRE model, a comprehensive navigation tool designed to simplify the project planning process and empower healthcare teams to achieve tangible outcomes. Empowering Nurses with Effective Problem-Solving Strategies in Healthcare. We are committed to delivering high quality, evidence-based patient care across healthcare. Nurses are ...
How to enhance GenAI's problem-solving
How to enhance generative AI's problem-solving capabilities and boost workplace productivity. In 2024, enterprise software companies are betting on generative AI, in a quest to enhance productivity. OpenAI has recently released GPT-4o, which includes interpretation and generation of voice and vision. Ravi Sawhney discusses how to incorporate ...
How Good Is Your Problem Solving?
Problem solving is an exceptionally important workplace skill. Being a competent and confident problem solver will create many opportunities for you. By using a well-developed model like Simplexity Thinking for solving problems, you can approach the process systematically, and be comfortable that the decisions you make are solid.
Solving the problem of multi-objective optimization based on a fuzzy
In this article, an analytical analysis of solving classification tasks for loosely formalized processes is conducted. Throughout the course of this research, structures were devised for the creation of training datasets. These structures facilitate the management of the intricate task of modeling processes, particularly in scenarios where the available data exhibits a fuzzy or uncertain nature.