problem solving analysis

The 5 Steps in Problem Analysis

One technique that is extremely useful to gain a better understanding of the problems before determining a solution is problem analysis .

Problem analysis is the process of understanding real-world problems and user’s needs and proposing solutions to meet those needs. The goal of problem analysis is to gain a better understanding of the problem being solved before developing a solution.

There are five useful steps that can be taken to gain a better understanding of the problem before developing a solution.

• Gain agreement on the problem definition
• Understand the root-causes – the problem behind the problem
• Identify the stakeholders and the users
• Define the solution boundary
• Identify the constraints to be imposed on the solution

Table of Contents

Gain agreement on the problem definition.

The first step is to gain agreement on the definition of the problem to be solved. One of the simplest ways to gain agreement is to simply write the problem down and see whether everyone agrees.

Business Problem Statement Template

A helpful and standardised format to write the problem definition is as follows:

• The problem of – Describe the problem
• Affects – Identify stakeholders affected by the problem
• The results of which – Describe the impact of this problem on stakeholders and business activity
• Benefits of – Indicate the proposed solution and list a few key benefits

Example Business Problem Statement

There are many problems statement examples that can be found in different business domains and during the discovery when the business analyst is conducting analysis. An example business problem statement is as follows:

The problem of  having to manually maintain an accurate single source of truth for finance product data across the business, affects the finance department. The results of which has the impact of not having to have duplicate data, having to do workarounds and difficulty of maintaining finance product data across the business and key channels. A successful solution would  have the benefit of providing a single source of truth for finance product data that can be used across the business and channels and provide an audit trail of changes, stewardship and maintain data standards and best practices.

Understand the Root Causes Problem Behind the Problem

You can use a variety of techniques to gain an understanding of the real problem and its real causes. One such popular technique is root cause analysis, which is a systematic way of uncovering the root or underlying cause of an identified problem or a symptom of a problem.

Root cause analysis helps prevents the development of solutions that are focussed on symptoms alone .

To help identify the root cause, or the problem behind the problem, ask the people directly involved.

The primary goal of the technique is to determine the root cause of a defect or problem by repeating the question “Why?” . Each answer forms the basis of the next question. The “five” in the name derives from an anecdotal observation on the number of iterations needed to resolve the problem .

Identify the Stakeholders and the Users

Effectively solving any complex problem typically involves satisfying the needs of a diverse group of stakeholders. Stakeholders typically have varying perspectives on the problem and various needs that must be addressed by the solution. So, involving stakeholders will help you to determine the root causes to problems.

Define the Solution Boundary

Once the problem statement is agreed to and the users and stakeholders are identified, we can turn our attention of defining a solution that can be deployed to address the problem.

Identify the Constraints  Imposed on Solution

We must consider the constraints that will be imposed on the solution. Each constraint has the potential to severely restrict our ability to deliver a solution as we envision it.

Some example solution constraints and considerations could be:-

• Economic – what financial or budgetary constraints are applicable?
• Environmental – are there environmental or regulatory constraints?
• Technical  – are we restricted in our choice of technologies?
• Political – are there internal or external political issues that affect potential solutions?

Conclusion – Problem Analysis

Try the five useful steps for problem solving when your next trying to gain a better understanding of the problem domain on your business analysis project or need to do problem analysis in software engineering.

The problem statement format can be used in businesses and across industries. 

Jerry Nicholas

Jerry continues to maintain the site to help aspiring and junior business analysts and taps into the network of experienced professionals to accelerate the professional development of all business analysts. He is a Principal Business Analyst who has over twenty years experience gained in a range of client sizes and sectors including investment banking, retail banking, retail, telecoms and public sector. Jerry has mentored and coached business analyst throughout his career. He is a member of British Computer Society (MBCS), International Institute of Business Analysis (IIBA), Business Agility Institute, Project Management Institute (PMI), Disciplined Agile Consortium and Business Architecture Guild. He has contributed and is acknowledged in the book: Choose Your WoW - A Disciplined Agile Delivery Handbook for Optimising Your Way of Working (WoW).

Recent Posts

Introduction to Train the Trainer for a Business Analyst

No matter the industry, modern professionals need to continuously improve themselves and work on up skilling and re-skilling to maintain satisfactory success within their field. This is particularly...

CliftonStrengths for a Business Analyst | Be You

Today, the job of a business analyst is probably more challenging than ever. The already intricate landscape of modern business analysis has recently gone through various shifts, mainly due to the...

35 problem-solving techniques and methods for solving complex problems

Design your next session with SessionLab

Join the 150,000+ facilitators 
using SessionLab.

Recommended Articles

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

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

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

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

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

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

Let’s get started! 

How do you identify problems?

How do you identify the right solution.

• Tips for more effective problem-solving

Complete problem-solving methods

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

Problem-solving warm-up activities

Closing activities for a problem-solving process.

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

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

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

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

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

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

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

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

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

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

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

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

Tips for more effective problem solving

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

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

Clearly define the problem

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

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

Don’t jump to conclusions

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

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

Try different approaches  

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

Don’t take it personally 

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

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

Get the right people in the room

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

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

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

Document everything

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

Bring a facilitator 

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

Develop your problem-solving skills

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

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

Design a great agenda

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

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

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

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

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

Design Sprint 2.0

• Open Space Technology

1. Six Thinking Hats

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

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

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

2. Lightning Decision Jam

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

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

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

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

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

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

3. Problem Definition Process

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

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

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

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

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

4. The 5 Whys 

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

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

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

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

5. World Cafe

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

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

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

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

6. Discovery & Action Dialogue (DAD)

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

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

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

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

7. Design Sprint 2.0

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

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

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

8. Open space technology

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

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

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

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

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

Techniques to identify and analyze problems

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

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

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

Let’s take a look!

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

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

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

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

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

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

10. The Creativity Dice

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

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

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

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

11. Fishbone Analysis

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

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

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

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

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

12. Problem Tree 

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

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

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

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

13. SWOT Analysis

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

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

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

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

14. Agreement-Certainty Matrix

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

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

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

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

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

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

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

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

16. Speed Boat

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

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

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

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

17. The Journalistic Six

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

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

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

18. LEGO Challenge

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

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

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

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

19. What, So What, Now What?

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

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

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

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

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

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

20. Journalists  

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

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

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

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

Problem-solving techniques for developing solutions 

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

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

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

21. Mindspin  

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

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

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

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

22. Improved Solutions

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

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

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

23. Four Step Sketch

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

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

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

24. 15% Solutions

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

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

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

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

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

25. How-Now-Wow Matrix

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

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

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

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

26. Impact and Effort Matrix

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

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

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

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

27. Dotmocracy

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

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

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

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

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

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

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

28. Check-in / Check-out

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

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

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

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

29. Doodling Together  

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

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

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

30. Show and Tell

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

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

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

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

31. Constellations

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

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

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

32. Draw a Tree

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

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

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

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

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

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

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

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

How do I conclude a problem-solving process?

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

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

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

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

33. One Breath Feedback

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

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

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

34. Who What When Matrix 

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

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

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

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

35. Response cards

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

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

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

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

Save time and effort discovering the right solutions

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

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

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

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

Over to you

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

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

thank you very much for these excellent techniques

Certainly wonderful article, very detailed. Shared!

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

Leave a Comment Cancel reply

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

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

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

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

Design your next workshop with SessionLab

Join the 150,000 facilitators using SessionLab

Sign up for free

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

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

What Is Problem Solving?

Definition and importance.

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

Problem-Solving Steps

The problem-solving process typically includes the following steps:

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

Defining the Problem

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

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

Generating Solutions

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

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

Evaluating and Selecting Solutions

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

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

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

Implementing and Monitoring the Solution

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

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

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

Problem-Solving Techniques

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

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

Brainstorming

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

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

When brainstorming, remember to:

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

Root Cause Analysis

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

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

SWOT Analysis

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

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

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

Mind Mapping

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

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

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

Examples of Problem Solving in Various Contexts

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

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

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

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

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

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

• A Step-by-Step Guide to A3 Problem Solving Methodology

• Learn Lean Sigma
• Problem Solving

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

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

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

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

Table of Contents

What is a3 problem solving.

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

Looking for a A3 Problem solving template? Click here

Origin and History of A3 Problem Solving

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

Key Principles of A3 Problem Solving

The following are the key principles of A3 Problem Solving:

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

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

Step 1: Define the Problem

Importance of clearly defining the problem.

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

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

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

Techniques for Defining the Problem

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

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

Best Practice for Defining the Problem

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

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

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

Step 2: Gather Data

Gathering data in a3 problem solving.

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

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

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

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

Data Collection Methods

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

• Observations
• Process diagrams

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

Tools for Data Analysis and Visualization

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

• Excel Spreadsheets
• Flow diagrams
• Pareto diagrams
• Scatter Plots
• Control diagrams

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

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

Step 3: Identify Root Causes

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

Overview of the Root Cause Analysis Process

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

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

Techniques for Identifying Root Causes

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

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

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

Best Practices for Conducting Root Cause Analysis

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

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

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

Step 4: Develop Solutions

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

Solution Development in A3 Problem Solving

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

Techniques for Developing Solutions

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

• Brainwriting
• Solution matrix
• Multi voting
• Force field analysis

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

Best Practice for Developing Solutions

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

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

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

Step 5: Implement Solutions

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

The implementation Process

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

Techniques for Implementing Solutions

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

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

Best Practice for Implementing Solutions

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

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

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

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

Daniel Croft

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

A Beginner’s Guide to Just-In-Time Manufacturing

How to Use Ishikawa Diagrams to Solve Business Problems

Free lean six sigma templates.

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

5S Floor Marking Best Practices

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

How to Measure the ROI of Continuous Improvement Initiatives

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

8D Problem-Solving: Common Mistakes to Avoid

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

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

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

8D: Tools and Techniques

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

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

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

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

Related articles.

Strategy to beat the odds

Five routes to more innovative problem solving

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

Overview of the Problem-Solving Mental Process

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

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

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

Frequently Asked Questions

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

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

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

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

The following steps include developing strategies and organizing knowledge.

1. Identifying the Problem

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

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

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

2. Defining the Problem

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

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

3. Forming a Strategy

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

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

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

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

4. Organizing Information

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

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

5. Allocating Resources

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

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

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

6. Monitoring Progress

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

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

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

7. Evaluating the Results

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

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

A Word From Verywell​

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

Get Advice From The Verywell Mind Podcast

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

Follow Now : Apple Podcasts / Spotify / Google Podcasts

You can become a better problem solving by:

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

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

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

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

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

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

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

• RCA 101 – 5-Why Analysis (Free Training)
• RCA 201 – Basic Failure Analysis
• RCA 301 – PROACT® RCA Certification
• RCA 401 – RCA Train The Trainer
• Other Trainings
• 5 Whys Root Cause Analysis Template
• RCA Template
• Chronic Failure Calculator

7 Powerful Root Cause Analysis Tools and Techniques

By Sebastian Traeger

Updated: April 21, 2024

Reading Time: 5 minutes

1. The Ishikawa Fishbone Diagram (IFD)

2. pareto chart, 4. failure mode and effects analysis (fmea), 5. proact® rca method, 6. affinity diagram, 7. fault tree analysis (fta).

With over two decades in business – spanning strategy consulting, tech startups and executive leadership – I am committed to helping your organization thrive. At Reliability, we’re on a mission to help enhance strategic decision-making and operational excellence through the power of Root Cause Analysis, and I hope this article will be helpful!  Our goal is to help you better understand these root cause analysis techniques by offering insights and practical tips based on years of experience. Whether you’re new to doing RCAs or a seasoned pro, we trust this will be useful in your journey towards working hard and working smart.

Root Cause Analysis (RCA) shines as a pivotal process that helps organizations identify the underlying reasons for problems, failures, and inefficiencies. The goal is simple: find the cause, fix it, and prevent it from happening again. But the process can be complex, and that’s where various RCA techniques come into play. 

Let’s dive into seven widely utilized RCA techniques and explore how they can empower your team’s problem-solving efforts.

Named after Japanese quality control statistician Kaoru Ishikawa, the Fishbone Diagram is a visual tool designed for group discussions. It helps teams track back to the potential root causes of a problem by sorting and relating them in a structured way. The diagram resembles a fishbone, with the problem at the head and the causes branching off the spine like bones. This visualization aids in categorizing potential causes and studying their complex interrelationships.

The Pareto Chart, rooted in the Pareto Principle, is a visual tool that helps teams identify the most significant factors in a set of data. In most situations, 80% of problems can be traced back to about 20% of causes. By arranging bar heights from tallest to shortest, teams can prioritize the most significant factors and focus their improvement efforts where they can have the most impact.

The 5 Whys method is the epitome of simplicity in getting to the bottom of a problem. By repeatedly asking ‘why’ (typically five times), you can delve beneath the surface-level symptoms of a problem to unearth the root cause. This iterative interrogation is most effective when answers are grounded in factual evidence.

When prevention is better than cure, Failure Mode and Effects Analysis (FMEA) steps in. This systematic, proactive method helps teams identify where and how a process might fail. By predicting and examining potential process breakdowns and their impacts, teams can rectify issues before they turn into failures. FMEA is a three-step process that involves identifying potential failures, analyzing their effects, and prioritizing them based on severity, occurrence, and detection ratings.

The PROACT ® RCA technique is a robust process designed to drive significant business results. Notably used to identify and analyze ‘chronic failures,’ which can otherwise be overlooked, this method is defined by its name:

PReserving Evidence and Acquiring Data: Initial evidence collection step based on the 5-P’s – Parts, Position, People, Paper, and Paradigms.

Order Your Analysis Team and Assign Resources: Assembling an unbiased team to analyze a specific failure.

Analyze the Event: Reconstructing the event using a logic tree to identify Physical, Human, and Latent Root Causes.

Communicate Findings and Recommendations: Developing and implementing solutions to prevent root cause recurrence.

Track and Measure Impact for Bottom Line Results: Tracking the success of implemented recommendations and correlating the RCA’s effectiveness with ROI.

PROACT® RCA excels in mitigating risk, optimizing cost, and boosting performance, making it a valuable addition to any RCA toolkit.

The Affinity Diagram is a powerful tool for dealing with large amounts of data. It organizes a broad range of information into groups based on their natural relationships, creating a clear, visual representation of complex situations. It’s particularly beneficial for condensing feedback from brainstorming sessions into manageable categories, fostering a better understanding of the broader picture.

Fault Tree Analysis (FTA) is a top-down, deductive failure analysis that explores the causes of faults or problems. It involves graphically mapping multiple causal chains to track back to possible root causes, using a tree-like diagram. FTA is particularly useful in high-risk industries, such as aerospace and nuclear power, where preventing failure is crucial.

Each RCA technique provides a unique approach for viewing and understanding problems, helping you pinpoint the root cause more effectively. The key is to understand when and how to use each tool, which can significantly enhance your team’s problem-solving capabilities.

Power up your RCA analysis with our EasyRCA and revolutionize your problem-solving process. Start Your Free Trial.

In conclusion, the techniques presented offer a diverse set of tools to help organizations address problems and inefficiencies effectively. From visual representations like the Ishikawa Fishbone Diagram and Pareto Chart to more proactive approaches such as the 5 Whys and Failure Mode and Effects Analysis (FMEA), each technique provides a unique perspective on identifying and mitigating root causes.

The PROACT® RCA Method stands out for its comprehensive process, particularly suited for chronic failures. Additionally, the Affinity Diagram and Fault Tree Analysis (FTA) contribute valuable insights by organizing data and exploring causal chains, respectively. Leveraging these techniques strategically enhances a team’s problem-solving capabilities, enabling them to make informed decisions and drive continuous improvement.

I hope you found these 7 techniques insightful and actionable! Stay tuned for more thought-provoking articles as we continue to share our knowledge. Success is rooted in a thorough understanding and consistent application, and we hope this article was a step in unlocking the full potential of Root Cause Analysis for your organization. Reliability runs initiatives such as an online learning center focused on the proprietary PROACT® RCA methodology and EasyRCA.com software. For additional resources, visit our Reliability Resources .

• Root Cause Analysis /

Recent Posts

Ultimate Guide to Swiss Cheese Model and Its Applications

5 Root Cause Analysis Examples That Shed Light on Complex Issues

Root Cause Analysis with 5 Whys Technique (With Examples)

What Is Fault Tree Analysis (FTA)? Definition & Examples

Root Cause Analysis Software

Our RCA software mobilizes your team to complete standardized RCA’s while giving you the enterprise-wide data you need to increase asset performance and keep your team safe.

Root Cause Analysis Training

[email protected]

Tel: 1 (800) 457-0645

Share article with friends:

Exploring the Elements: Analysis & Problem Solving

Analysis & problem solving are necessary to navigate everyday life, especially in a world of echo-chambers and #fakenews . through analysis, we seek to fully understand issues and uncover potential solutions. so keep reading for insights into how these skills can be developed…, what is analysis & problem solving and why is it important .

Analysis and Problem Solving is the ability to critically evaluate data and use judgement to work through issues. It involves spotting connections between data. And essentially, involves seeing and actioning solutions effectively.

Firstly, Analysis is about being objective. And looking for evidence to support the conclusions we reach. Ultimately to improve judgement. And good analysis helps us to keep in check important cognitive shortcuts that can often impair our judgements– our biases.

We all have biases. When left unmanaged, biases are very problematic. One common bias, the Halo Effect , leads us to amplify the positive aspects of people. For example, thinking because a person is attractive, they’ll automatically be a good person. By building an analytical mindset, we can manage our biases, make better decisions and effectively solve problems.

The goal is to problem-solve on the basis of objective evidence, not sentiment. Emotions and biases cloud our judgement. So it’s essential to probe the evidence, determine what’s fact from fiction. Good analysis helps us to do this.

When starting out

At the outset of your career, you’re likely to be given tasks or problems to solve. A good determinant of how successful you’ll be in problem solving or delivering tasks is your ability to conduct strong analysis.

Naturally, over time, the problems you’ll deal with will become increasingly complex. So, it’s good to get in the habit of conducting thorough, evidence-based analysis early on.

First, focus on identifying relevant information. Is there data, facts, evidence available to help you analyse? Be careful too, it’s easy to waste time with interesting yet ultimately irrelevant data.

During this time, you’ll be getting to grips with the role, workplace and your colleagues. So you’ll have all sorts of information to handle. This makes it even more important to focus on what really matters to the task at hand.

Ask questions for a better understanding of what you’re trying to solve. Seek others’ views and opinions. This is important for ensuring others trust and engage with you. But your priority should be on building a picture of problems, built of evidence and data.

Test assumptions to decipher and challenge the myths. In a world of fake news, critical thinking is integral to analysis and problem solving. Sometimes can be as simple as reviewing problems again after a break. Ask yourself:  what am I assuming here? What is really going? W hat might I have missed before?

Exercise lateral thinking. Think outside the box and to look at problems from different perspectives. For example, if you’re a product designer it’s effective to interact with product from the perspective of users, suppliers and distributors.

Beware of  overconfidence . Both your own and that of others. Don’t just expect your managers or seniors to be correct, examine the source of data. Also, get a handle on the different types of biases that hinder  analysis . Think about which biases you might be prone to.

Essentially, it’s about having your research hat on. So stay alert and conduct qualitative and quantitative analysis as appropriate. Try testing yourself to build your capacity for spotting trends and patterns in complex problems. Logical or abstract reasoning tests can be a great one to start with.

Analysis and Problem Solving on your way up

So as you gain more experience in dealing with analysis, you’ll become better at problem-solving. Often the more senior your role is means the more responsibility you have, thus more potential problems.

With experience, you’ll start to more routinely tune-in to the workplace. Y ou’ll be aware of issues brewing beneath the surface, like office politics. And you will analyse and navigate underlying issues like this when problem-solving.

By its very nature, you’re dealing with more data, more information, more stakeholders and more pressure. So your ability to analyse despite additional distractions is truly put to the test. However, you may now have the opportunity to delegate tasks.

And if the option of help is there – grab it with both hands! The variety of information you’re dealing with grows with increasing responsibility. It’s easy to think you can continue to effectively analyse as you once did with a more focused workload, but don’t be fooled. We all have limits. We have to prioritise our attention. Pick what and when we analyse.

As you take more of a lead on problems, help others to think critically. Point out the evidence, data or facts underpinning your judgements. And ask them to critically evaluate them too.

More and more, leaders will want to see depth in your analysis and evidence that your ideas are future-proofed. They’ll ask to see the business case for any recommendations you make. So prioritise building strong rationale in business cases and focus on testing assumptions and iterating your solutions. Build prototypes or minimal viable products (MVPs) to truly stress test your ideas or judgements.

Develop a process for problem solving. Try to implement systems to seek, analyse, formulate solutions and evaluate outcomes. Building loops like this can help create habits and make analysis more seamless.

You could use tools to appraise data quickly. Or you can work with specialists in evaluating big data. In the future we’ll be using more tools to analyse complex and diverse data. So get ahead of the curb, by building you capacity for interpreting data now.

Leading in Analysis and Problem Solving

No matter what career stage you’re at, there will be problems to solve. This is especially the case when you’re in a position of leadership. A good leader is both demonstrator and facilitator of strong analysis and problem-solving skills.

At this stage you’ll likely be responsible for the management of a team and the big picture of the organisation.  Ultimately, you’ll need to lead by example and set the tone for your team when problem-solving.

Leaders are expected to be decisive. And good decisions are made by harnessing the power of an analytical mindset to collect and decipher data and information. No knee-jerk reactions, but thoughtful and strategic responses. Here are some pointers on how you can do this:

Use patterns and trends to uncover longer term opportunities and draw potential conclusions. This could relate to commercial thinking when looking for financially beneficial opportunities.

Recognise and respond strategically to the pressures faced by your people. Engage with your team and look at how you can improve processes, wellbeing and overall productivity.

Consistently build and review your awareness of new technologies shaping the way things might be done in the future. Stay in the know and beware of the fads. It’s about choosing what is best to pursue.

Increase your awareness and use of Systems Thinking . Identify the links between different tasks and functions. Then evaluate on the basis of seeing things in a system, rather than treating issues in isolation.

Say what you think. Share your thought-process openly. Be a thought-leader, create an open space for sharing thoughts and your team will contribute. This ultimately increases potential collaboration, empowers the team and teases out team-working issues.

From analysing the situation to solving it

Whatever walk of life or occupation, your chances of success will improve along with your capacity for analysis and problem solving. Whether you’re just starting out or you’ve been around for a while, these skills are needed at every stage.

And analysis is important in our interpersonal interactions, as it is for regular tasks. There are always instances where you might need to read between the lines of what someone is saying. And to identify what’s really going on, beneath the conversation’s surface.

Additionally, the more hands-on experience we have with problems, the better we’ll be at finding solutions. So maybe we should schedule some time for ‘brain-training’ exercises like Sudoku? Although there isn’t any conclusive evidence to suggest games like Sudoku substantially improve our problem-solving abilities, the regular exposure to problems tests us and builds confidence.

So if you’re looking to build up your analysis and problem solving skills, set up a  spotlight  on the  WiseAmigo app . Doing this will help you stay on track with your development, and get inspired along the way.

And once you’ve nailed Analysis and Problem Solving, you’ll be in a better place to think strategically, commercially and manage conflict better too.

“Analysis is the art of creation through destruction.”  

― p.s. baber, cassie draws the universe..

Normal 0 false false false EN-US JA X-NONE

Development is a journey and the  WiseAmigo  app is here to help you along the way. Join the WiseAmigo community,  create a Spotlight , discover more insightful content and reflect on your assertiveness journey today.

Privacy Preference Center

Privacy preferences.

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

How to Solve Problems

• Laura Amico

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

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

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

Partner Center

How it works

For Business

Join Mind Tools

Article • 7 min read

What Is Problem Solving?

Find a solution to any problem you face..

By the Mind Tools Content Team

We all spend a lot of our time solving problems, both at work and in our personal lives.

Some problems are small, and we can quickly sort them out ourselves. But others are complex challenges that take collaboration, creativity, and a considerable amount of effort to solve.

At work, the types of problems we face depend largely on the organizations we're in and the jobs we do. A manager in a cleaning company, for example, might spend their day untangling staffing issues, resolving client complaints, and sorting out problems with equipment and supplies. An aircraft designer, on the other hand, might be grappling with a problem about aerodynamics, or trying to work out why a new safety feature isn't working. Meanwhile, a politician might be exploring solutions to racial injustice or climate change.

But whatever issues we face, there are some common ways to tackle them effectively. And we can all boost our confidence and ability to succeed by building a strong set of problem-solving skills.

Mind Tools offers a large collection of resources to help you do just that!

How Well Do You Solve Problems?

Start by taking an honest look at your existing skills. What's your current approach to solving problems, and how well is it working? Our quiz, How Good Is Your Problem Solving? lets you analyze your abilities, and signposts ways to address any areas of weakness.

Define Every Problem

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 real issue might be a general lack of training, or an unreasonable workload across the team.

Tools like 5 Whys , Appreciation and Root Cause Analysis get you asking the right questions, and help you to work through the layers of a problem to uncover what's really going on.

However, defining a problem doesn't mean deciding how to solve it straightaway. It's important to look at the issue from a variety of perspectives. If you commit yourself too early, you can end up with a short-sighted solution. The CATWOE checklist provides a powerful reminder to look at many elements that may contribute to the problem, keeping you open to a variety of possible solutions.

Understanding Complexity

As you define your problem, you'll often discover just how complicated it is. There are likely several interrelated issues involved. That's why it's important to have ways to visualize, simplify and make sense of this tangled mess!

Affinity Diagrams are great for organizing many different pieces of information into common themes, and for understanding the relationships between them.

Another popular tool is the Cause-and-Effect Diagram . To generate viable solutions, you need a solid understanding of what's causing the problem.

When your problem occurs within a business process, creating a Flow Chart , Swim Lane Diagram or a Systems Diagram will help you to see how various activities and inputs fit together. This may well highlight a missing element or bottleneck that's causing your problem.

Quite often, what seems to be a single problem turns out to be a whole series of problems. The Drill Down technique prompts you to split your problem into smaller, more manageable parts.

General Problem-Solving Tools

When you understand the problem in front of you, you’re ready to start solving it. With your definition to guide you, you can generate several possible solutions, choose the best one, then put it into action. That's the four-step approach at the heart of good problem solving.

There are various problem-solving styles to use. For example:

• Constructive Controversy is a way of widening perspectives and energizing discussions.
• Inductive Reasoning makes the most of people’s experiences and know-how, and can speed up solution finding.
• Means-End Analysis can bring extra clarity to your thinking, and kick-start the process of implementing solutions.

Specific Problem-Solving Systems

Some particularly complicated or important problems call for a more comprehensive process. Again, Mind Tools has a range of approaches to try, including:

• Simplex , which involves an eight-stage process: problem finding, fact finding, defining the problem, idea finding, selecting and evaluating, planning, selling the idea, and acting. These steps build upon the basic, four-step process described above, and they create a cycle of problem finding and solving that will continually improve your organization.
• Appreciative Inquiry , which is a uniquely positive way of solving problems by examining what's working well in the areas surrounding them.
• Soft Systems Methodology , which takes you through four stages to uncover more details about what's creating your problem, and then define actions that will improve the situation.

Further Problem-Solving Strategies

Good problem solving requires a number of other skills – all of which are covered by Mind Tools.

For example, we have a large section of resources to improve your Creativity , so that you come up with a range of possible solutions.

By strengthening your Decision Making , you'll be better at evaluating the options, selecting the best ones, then choosing how to implement them.

And our Project Management collection has valuable advice for strengthening the whole problem-solving process. The resources there will help you to make effective changes – and then keep them working long term.

Problems are an inescapable part of life, both in and out of work. So we can all benefit from having strong problem-solving skills.

It's important to understand your current approach to problem solving, and to know where and how to improve.

Define every problem you encounter – and understand its complexity, rather than trying to solve it too soon.

There's a range of general problem-solving approaches, helping you to generate possible answers, choose the best ones, and then implement your solution.

Some complicated or serious problems require more specific problem-solving systems, especially when they relate to business processes.

By boosting your creativity, decision-making and project-management skills, you’ll become even better at solving all the problems you face.

You've accessed 1 of your 2 free resources.

Get unlimited access

Discover more content

Simplex thinking.

8 Steps for Solving Complex Problems

Book Insights

Solving Tough Problems: An Open Way of Talking, Listening, and Creating New Realities

Adam Kahane (Foreword by Peter Senge)

Add comment

Comments (0)

Be the first to comment!

Get 30% off your first year of Mind Tools

Great teams begin with empowered leaders. Our tools and resources offer the support to let you flourish into leadership. Join today!

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

Most Popular

Latest Updates

Nine Ways to Get the Best From X (Twitter)

Take the Stress Out of Your Life

Mind Tools Store

About Mind Tools Content

Discover something new today

Eight classic mistakes interviewers make infographic.

Infographic Transcript

Infographic

How to Overcome Fear of Failure

Five tips to help you move forward

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

Round-robin brainstorming.

Allowing Everyone to Contribute

Business Operations and Process Management

Strategy Tools

Customer Service

Business Ethics and Values

Handling Information and Data

Project Management

Knowledge Management

Self-Development and Goal Setting

Time Management

Presentation Skills

Learning Skills

Career Skills

Communication Skills

Negotiation, Persuasion and Influence

Working With Others

Difficult Conversations

Creativity Tools

Self-Management

Work-Life Balance

Stress Management and Wellbeing

Coaching and Mentoring

Change Management

Team Management

Managing Conflict

Delegation and Empowerment

Performance Management

Leadership Skills

Developing Your Team

Talent Management

Problem Solving

Decision Making

Member Podcast

Lean Six Sigma Training Certification

• Facebook Instagram Twitter LinkedIn YouTube
• (877) 497-4462

Is/Is Not Analysis: A Powerful Problem-Solving Technique for Peak Performance

May 15th, 2024

Businesses face all kinds of hurdles slowing progress and threatening success. From grindingly slow workflows to quality glitches, these problems spread damage far if left unaddressed.

But with the right problem-solving styles, companies can pinpoint what’s causing trouble and implement fixes well.

One such method earning its stripes across industries everywhere is “Is/Is Not Analysis”.

It provides a methodical way for teams to sharply define issues while excluding what they’re not.

Doing so eliminates vagueness, prevents scope creep, and guarantees efforts target the actual problem.

Whether handling complex engineering puzzles or streamlining company processes, Is/Is Not Analysis has time and again proven hugely useful in my problem-crushing toolkit.

Key Highlights

• A thorough understanding of what the Is/Is Not Analysis is and how it fits into the broader problem-solving framework.
• The numerous benefits of using this technique, such as enhanced focus and clarity, improved team alignment, effective scope management, better communication, and robust decision-making.
• A step-by-step guide on how to conduct an “Is/Is Not Analysis”, from describing the problem to formulating a concise problem statement.
• Insights into the wide-ranging applications of this analysis across various domains.
• An example demonstrating the application of the Is/Is Not Analysis in a manufacturing context, addressing the issue of machine downtime, and highlighting the process of comparative analysis and problem statement formulation.
• Industry-specific terminology, technical insights, and best practices drawn from my extensive experience working with Lean Six Sigma methodologies.

What is an Is/Is Not Analysis?

The Is/Is Not Analysis is a powerful problem-solving technique that brings clarity and focus to complex situations.

This method is an invaluable asset in my toolkit, enabling me to tackle intricate challenges across a wide range of industries and domains.

Problem-solving technique

The Is/Is Not Analysis is a systematic approach that guides teams through the process of precisely defining the scope of a problem.

Breaking down the issue into two distinct components – what the problem “is” and what it “is not” – allows you to isolate the core elements that require attention while filtering out extraneous factors that may distract or derail your efforts.

Scope definition with Is/Is Not Analysis

One of the primary benefits of this analysis is its ability to establish clear boundaries and parameters around the problem at hand.

By explicitly stating what falls within the scope of the issue and what lies outside of it, you can prevent scope creep and ensure that your team remains focused on the most relevant aspects.

This not only streamlines the problem-solving process but also optimizes the allocation of resources, directing them toward the areas that truly matter.

Structured problem-solving approach

The Is/Is Not Analysis is a structured and systematic approach that follows a well-defined set of steps. It begins with a detailed description of the problem, followed by the identification of what the problem “is” and what it “is not”.

This process involves gathering data, analyzing information, and leveraging templates to facilitate a comprehensive understanding of the situation.

This problem-solving technique seamlessly integrates into the widely adopted DMAIC (Define, Measure, Analyze, Improve, Control) methodology, which is a cornerstone of Lean Six Sigma practices.

The Is/Is Not Analysis plays a crucial role in the “ Define ” phase, where it helps teams precisely articulate the problem they are addressing, setting the stage for subsequent phases of measurement, analysis, improvement, and control.

Is vs. Is Not Matrix

To facilitate the analysis, a commonly used tool is the “Is vs. Is Not” matrix, which is a tabular representation that contrasts the elements that fall within the scope of the problem (“Is”) with those that do not (“Is Not”).

This visual aid not only enhances understanding but also serves as a reference point throughout the problem-solving journey, ensuring that the team remains aligned and focused on the defined objectives.

Benefits of Using an Is/Is Not Analysis

The Is/Is Not Analysis can have on problem-solving endeavors.

This versatile technique offers a multitude of benefits that not only enhance the effectiveness of the problem-solving process but also foster a more collaborative and efficient team dynamic.

Focus and clarity

One of the primary advantages of the Is/Is Not Analysis is its ability to bring laser-sharp focus and clarity to even the most complex challenges.

By meticulously delineating what the problem is and what it is not, this approach eliminates ambiguity and ensures that all team members are operating with a shared understanding of the issue at hand.

This shared clarity of purpose is a powerful catalyst for efficient and targeted problem-solving efforts.

Team alignment

In my experience, one of the biggest hurdles in tackling complex problems is achieving true alignment among team members.

The Is/Is Not Analysis serves as a unifying force, fostering a collaborative environment where everyone is working towards the same clearly defined objectives.

Scope management

Effective scope management is crucial in any problem-solving endeavor, as it prevents resources from being diluted across irrelevant areas.

The Is/Is Not Analysis excels in this regard, as it establishes precise boundaries around the problem, delineating what aspects fall within the scope and what lies outside of it.

Communication enhancement

Clear and effective communication is the lifeblood of any successful problem-solving initiative. By providing a structured framework for defining the problem, the Is/Is Not Analysis enhances communication within the team and across stakeholder groups.

The visual representation of the problem’s scope, often through the use of matrices or templates, facilitates a common understanding and streamlines the dissemination of information, ensuring that everyone is working towards the same goals.

Problem definition

At the heart of the Is/Is Not Analysis lies a robust problem definition process.

By breaking down complex issues into manageable components and identifying the specific characteristics and boundaries of the problem, this technique lays a solid foundation for comprehensive problem-solving efforts.

A well-defined problem statement is a critical first step towards finding effective solutions.

Boundary setting

In addition to defining the problem’s scope, the Is/Is Not Analysis also plays a crucial role in setting boundaries for the problem-solving effort.

By explicitly stating what falls outside the scope of the issue, this technique helps teams avoid getting sidetracked by tangential or irrelevant factors, ensuring that their focus remains unwavering on the core problem at hand.

Risk identification

Another valuable benefit of the Is/Is Not Analysis is its ability to identify potential risks or areas that might otherwise be overlooked.

This proactive approach allows for the development of effective risk mitigation strategies, enhancing the overall success of the initiative.

Decision-making

Informed decision-making is a critical component of any successful problem-solving effort. The Is/Is Not Analysis supports this process by providing a clear and comprehensive picture of the situation.

By understanding what is within the scope and what lies outside of it, teams can make well-informed decisions regarding resource allocation, action prioritization, and appropriate solutions.

Continuous improvement

The Is/Is Not Analysis is not a one-time exercise but rather a continuous improvement tool. As teams gain insights and lessons learned throughout the problem-solving journey, they can refine and update their understanding of what the problem “is” and “is not”.

This iterative process allows for ongoing optimization and ensures that solutions remain relevant and effective over time.

Documentation

Finally, the Is/Is Not Analysis provides a documented record of the problem’s scope and boundaries. 

This documentation serves as a valuable reference not only for the current problem-solving initiative but also for future projects or audits.

It ensures that the rationale behind decisions and the parameters of the problem are captured, facilitating knowledge transfer and enabling continuous learning within the organization.

How to Conduct an Is/Is Not Analysis

While the specifics may vary depending on the nature of the problem and the industry, there is a well-established framework that has proven effective time and time again.

Describe the problem

The first step in any successful Is/Is Not Analysis is to provide a detailed description of the problem at hand. This involves more than simply stating what the issue is; it requires a comprehensive understanding of the symptoms, consequences, and impact of the problem.

During this stage, it is crucial to gather as much relevant data and information as possible, ensuring that the problem is thoroughly documented and free from assumptions or proposed solutions.

Identify the “Is”

With a clear understanding of the problem in place, the next step is to identify what the problem “is”.

This involves documenting the specific characteristics, actions, behaviors, or outcomes that are considered problematic.

Template-based analysis with Is/Is Not Analysis

To facilitate this process, I often recommend the use of templates or matrices that allow teams to visually organize and contrast the “Is” and “Is Not” elements.

One popular approach is the “Is vs. Is Not” matrix, which provides a tabular representation that delineates the problem’s scope.

These templates enhance understanding and serve as a reference point throughout the analysis, ensuring consistency and alignment among team members.

Identify the “Is Not”

Once the “Is” elements have been defined, it is equally important to identify what the problem “is not”.

This step involves considering what one would expect to happen in the absence of the problem, as well as determining the locations, timeframes, and conditions where the issue does not occur.

Compare and contrast

With the “Is” and “Is Not” elements clearly defined, the next step is to compare and contrast the information collected.

This comparative analysis can reveal patterns, inconsistencies, or discrepancies that may point to potential root causes or contributing factors. It is during this stage that the true value of the Is/Is Not Analysis becomes apparent, as teams can begin to pinpoint the areas that require the most attention.

Data analysis with Is/Is Not Analysis

Throughout the Is/Is Not Analysis process, data plays a crucial role in informing and guiding the team’s efforts.

Narrow down the scope

Armed with the insights gained from the comparative analysis and data analysis, teams can begin to narrow down the scope of the problem.

This may involve discarding certain aspects that are not central to the issue or focusing on areas that have the most significant impact.

The goal is to create a refined view of the problem that can be effectively addressed through targeted solutions.

Formulate the problem statement with Is/Is Not Analysis

The culmination of the Is/Is Not Analysis process is the formulation of a concise and well-defined problem statement. This statement should incorporate all relevant “Is” and “Is Not” factors while being specific, measurable, and verifiable.

A clear problem statement sets the boundaries for what will (and will not) be addressed in the subsequent problem-solving efforts, ensuring that teams remain focused and on track throughout the journey.

Applications of Is/Is Not Analysis

This versatile technique has proven its value time and again, transcending boundaries and demonstrating its applicability in numerous contexts.

Project management

The Is/Is Not Analysis is an invaluable tool in the realm of project management .

By clearly defining the scope of a project and delineating what tasks and objectives are included (and excluded), this technique ensures that resources are allocated effectively and that efforts remain focused on the most critical elements.

Whether managing large-scale initiatives or smaller-scale endeavors, the Is/Is Not Analysis provides a structured framework for aligning stakeholders, setting boundaries, and mitigating the risk of scope creep.

Business analysis

In the dynamic world of business, organizations often face complex challenges that require a deep understanding of the underlying issues.

The Is/Is Not Analysis is a powerful ally in this regard, enabling business analysts to define precisely the scope of a problem or opportunity.

Product development with Is/Is Not Analysis

Whether developing tangible products or crafting innovative services, the Is/Is Not Analysis can play a crucial role in defining requirements and setting boundaries.

Quality management

By defining what constitutes quality (and what does not), this technique provides a solid foundation for developing effective quality control processes and procedures.

Whether assessing the quality of a product, service, or process, the Is/Is Not Analysis ensures that efforts are targeted and that resources are allocated appropriately, ultimately driving continuous improvement and customer satisfaction.

Requirements gathering

Effective requirements gathering is critical to the success of any project or initiative, and the Is/Is Not Analysis is an invaluable tool in this regard.

Root cause analysis and Is/Is Not Analysis

When faced with complex problems, identifying the root cause is often the most challenging and critical step.

The Is/Is Not Analysis provides a structured approach to unraveling these intricacies, by systematically separating the core issues from peripheral factors.

Environmental impact assessment

Companies must carefully consider the potential impact of their operations and projects on the natural world.

The Is/Is Not Analysis can be a powerful tool in this regard, enabling teams to clearly define the scope of an environmental assessment and delineate what factors should be considered.

Conflict resolution

Conflicts, whether interpersonal or organizational, often stem from a lack of clear understanding and alignment.

The Is/Is Not Analysis can be a valuable asset in resolving such conflicts by providing a structured framework for defining the issues at hand and separating them from extraneous factors.

By clarifying what the conflict “is” and what it “is not”, teams can focus their efforts on addressing the core points of contention, facilitating effective communication, and paving the way for resolution.

Goal setting with Is/Is Not Analysis

Whether setting personal or organizational goals, the Is/Is Not Analysis can be a powerful tool for ensuring clarity and focus.

Defining what goals should be pursued (and what should be excluded), individuals and teams can align their efforts and allocate resources effectively.

Personal development

Beyond its applications in professional settings, the Is/Is Not Analysis can also be a valuable tool for personal growth and development.

This structured approach can help individuals prioritize their efforts, overcome obstacles, and achieve their desired outcomes more effectively.

Lean Six Sigma

This technique aligns perfectly with the core tenets of these philosophies, such as continuous improvement, waste elimination , and data-driven decision-making .

An Example of Is/Is Not Analysis for Machine Downtime

To illustrate the practical application of the “Is/Is Not Analysis”, let us consider a real-world example from the manufacturing sector.

In this scenario, a company is grappling with the issue of unexpected machine downtime, which is negatively impacting productivity and delivery times.

Problem description

The initial step in the Is/Is Not Analysis is to provide a detailed description of the problem. In this case, the issue is unscheduled machine downtime, which results in machines stopping unexpectedly and requiring maintenance.

This downtime is reported to occur specifically on Line 1, which handles a portion of the production process.

“Is” analysis

Next, the team identifies the “Is” elements of the problem. They note that the machine downtime is occurring on Line 1, particularly during the third shift (11 PM to 7 AM).

“Is Not” analysis

In contrast, the team observes that the downtime is not occurring on Lines 2 and 3, indicating that the issue may be isolated to factors unique to Line 1, such as equipment, personnel, or processes.

Comparative analysis

By comparing and contrasting the “Is” and “Is Not” elements, the team can start to pinpoint potential root causes.

For instance, the fact that the issue is specific to Product A and not Products B or C could indicate that the problem is related to the machinery’s configuration, the complexity of Product A, or the raw materials used.

Problem statement formulation

Armed with these insights, the team can formulate a concise and well-defined problem statement:

During the third shift, Line 1 experiences an increase in machine downtime, specifically when running Product A, leading to production delays.

This issue does not occur during the first or second shifts, nor does it affect Lines 2 and 3 when running Products B or C”.

Next steps: Root cause analysis

With a clear problem statement in place, the team can now proceed to a focused root cause analysis, investigating potential factors such as:

• Specific differences in the setup for Product A versus Products B and C
• Environmental and operational conditions of Line 1 during the third shift
• Training, expertise, and fatigue levels of third-shift staff compared to other shifts

Is/Is Not Analysis has proven its worth across countless industries and uses. Whether handling complex engineering puzzles, smoothing company workflows, or fueling constant upgrades, it provides an organized style framing issues while distinguishing main problems from extra factors.

As you start leveraging “Is/Is Not Analysis”, remember to embrace an organized, fact-based method. Foster teamwork and agreement between all involved. Also, stay committed to constant learning and perfecting your approach.

With determination and truly grasping this mighty technique, you too can break into new levels of problem-solving success. You’ll power transformative change within your work or personal goals.

My hope is you feel equipped to maximize every tool in your toolkit. With Is/Is Not Analysis helping sharpen your problem-solving focus, countless opportunities now come clearly into view. Take what you’ve learned and change the game!

SixSigma.us offers both Live Virtual classes as well as Online Self-Paced training. Most option includes access to the same great Master Black Belt instructors that teach our World Class in-person sessions. Sign-up today!

Virtual Classroom Training Programs Self-Paced Online Training Programs

SixSigma.us Accreditation & Affiliations

Monthly Management Tips

• Be the first one to receive the latest updates and information from 6Sigma
• Get curated resources from industry-experts
• Gain an edge with complete guides and other exclusive materials
• Become a part of one of the largest Six Sigma community
• Unlock your path to become a Six Sigma professional

" * " indicates required fields

• The Problem Analysis Triangle

While the  SARA model  is useful as a way of organizing the approach to recurring problems, it is often very difficult to figure out just exactly what the real problem is. The problem analysis triangle (sometimes referred to as the crime triangle) provides a way of thinking about recurring problems of crime and disorder. This idea assumes that crime or disorder results when (1) likely offenders and (2) suitable targets come together in (3) time and space, in the absence of capable guardians for that target. A simple version of a problem analysis triangle looks like this:

Offenders can sometimes be controlled by other people: those people are known as handlers. Targets and victims can sometimes be protected by other people as well: those people are known as guardians. And places are usually controlled by someone: those people are known as managers. Thus, effective problem-solving requires understanding how offenders and their targets/victims come together in places, and understanding how those offenders, targets/victims, and places are or are not effectively controlled. Understanding the weaknesses in the problem analysis triangle in the context of a particular problem will point the way to new interventions. A complete problem analysis triangle looks like this:

Problems can be understood and described in a variety of ways. No one way is definitive. They should be described in whichever way is most likely to lead to an improved understanding of the problem and effective interventions. Generally, incidents that the police handle cluster in four ways:

• Behavior . Certain behavior(s) is (are) common to the incidents. For example, making excessive noise, robbing people or businesses, driving under the influence, crashing vehicles, dealing drugs, stealing cars. There are many different behaviors that might constitute problems.
• Place . Certain places can be common to incidents. Incidents involving one or more problem behaviors may occur at, for example, a street corner, a house, a business, a park, a neighborhood, or a school. Some incidents occur in abstract places such as cyberspace, on the telephone, or through other information networks.
• Persons . Certain individuals or groups of people can be common to incidents. These people could be either offenders or victims. Incidents involving one or more behaviors, occurring in one or more places may be attributed to, for example, a youth gang, a lone person, a group of prostitutes, a group of chronic inebriates, or a property owner. Or incidents may be causing harm to, for example, residents of a neighborhood, senior citizens, young children, or a lone individual.
• Time . Certain times can be common to incidents. Incidents involving one or more behaviors, in one or more places, caused by or affecting one or more people may happen at, for example, traffic rush hour, bar closing time, the holiday shopping season, or during an annual festival.

There is growing evidence that, in fact, crime and disorder does cluster in these ways. It is not evenly distributed across time, place, or people. Increasingly, police and researchers are recognizing some of these clusters as:

• Repeat offenders attacking different targets at different places.
• Repeat victims repeatedly attacked by different offenders at different places.
• Repeat places (or hot spots) involving different offenders and different targets interacting at the same place.

The Problem Analysis Triangle was derived from the routine activity approach to explaining how and why crime occurs. This theory argues that when a crime occurs, three things happen at the same time and in the same space:

• a suitable target is available.
• there is the lack of a suitable guardian to prevent the crime from happening.
• a motivated offender is present.

Check out the list of readings under the  POP Center recommended readings .

• What Is Problem-Oriented Policing?
• History of Problem-Oriented Policing
• Key Elements of POP
• The SARA Model
• Situational Crime Prevention
• 25 Techniques
• Links to Other POP Friendly Sites
• About POP en Español

• Study resources
• Calendar - Graduate
• Calendar - Undergraduate
• Class schedules
• Class cancellations
• Course registration
• Important academic dates
• More academic resources
• Campus services
• IT services
• Job opportunities
• Safety & prevention
• Mental health support
• Student Service Centre (Birks)
• All campus services
• Calendar of events
• Latest news
• Media Relations
• Faculties, Schools & Colleges
• Arts and Science
• Gina Cody School of Engineering and Computer Science
• John Molson School of Business
• School of Graduate Studies
• All Schools, Colleges & Departments.
• Directories
• Future students
• Current students
• Alumni & friends
• Faculty & staff
• Arts & culture
• In the community
• Sports & wellness
• Student life
• University affairs
• Publications & reports
• Find an expert
• Our award winners
• Filming on campus

How immersion in problem solving turned Donia Chaouch into a safety-analysis entrepreneur

The next time your car’s digital system alerts you to a potential collision, think of  Donia Chaouch , MASc 15. The software engineer spent so many years analyzing and testing safety systems in cars, as well as for robotics companies, she decided to launch her own business.

As co-founder and chief technology officer of  Robosafety , the Ottawa-based Chaouch serves as chief architect of the newborn company, designing and implementing scalable and efficient system infrastructures that help develop a range safety-analysis tools. Currently in beta mode, Robosafety seeks to work with a range of sectors in need of comprehensive safety audits.

“From automotive to aviation to oil and gas to medical devices, all of these industries have to have safety as a key priority,” says Chaouch.

In the case of a car’s collision-detector system, common on most modern vehicles, the Robosafety team can first identify any potential hazards, including the system malfunctions or performance limitations leading to false alarms.

“We then conduct a thorough failure analysis and consider factors such as the hardware, software, environmental conditions, and so on,” says Chaouch. “The risk assessment follows, and we look over all of the risks associated with each of the failure-leading hazards that we identified.”

A lightbulb moment

The idea for Robosafety was born in 2021, when Chaouch was in Silicon Valley, California, working as a safety consultant for several robotics companies. She learned from parts suppliers that they were all facing the same pain points on how the whole safety process unfolded. “That kind of stayed on my mind,” she recalls, “and I asked myself ‘How can we change that?’”

Returning to Ottawa, where she had lived since graduating from Concordia, Chaouch discussed her percolating vision with close friend Mary Yazdani, founder and CEO of consulting firm  GenesisLink .

“When I shared the idea with her, she was very interested in collaborating,” Chaouch recalls. Last year, they started Robosafety — with Yazdani joining as co-founder and CEO — and began hiring engineers and working on the software.

“If you think of safety recalls for things like cars, often the issue is something that was overlooked or missed during design and analysis. Our tools can help with that challenge.”

Bringing Robosafety to life isn’t a far reach for Chaouch, whose experience in the field prepared her for this new adventure.

‘Ready for the professional world’

Raised in Sousse, Tunisia, Chaouch had always been an avid reader, whether the books were in French, Arabic or English. And, after an enlightening conversation with her father about her future, she soon discovered how attractive computer science was as a subject.

She earned a computer science/software engineering degree in Tunisia before deciding to head to Concordia for her master’s.

“So many of my friends moved to Montreal,” she recalls. “I also wanted to live in a welcoming and diverse country. Unfortunately, some of the other countries I was considering weren’t like that all.”

At Concordia, where she specialized in  electrical and computer engineering , Chaouch looks back fondly at how it prepared her for future roles in engineering. “Concordia helped me be ready for the professional world, and when I landed my first job out of school, I really didn’t feel worried at all,” she says. She now says she couldn’t have asked for better mentor than  Professor Sofiène Tahar  and being involved in his  world-renowned research group .

One of her most memorable jobs was as a software engineer for BlackBerry QNX, the operating system common in many cars. She would study test cases and experiments to ensure the operating system didn’t have any glitches.

“I was married with a five-month-old daughter at the time so working at BlackBerry was really great for me and my family,” Chaouch says.

As busy as her life has become as an entrepreneur, she admits she’s found her calling. “To have the courage to be a young woman on a non-traditional path, that’s fulfilling to me,” Chaouch says.

“It can be hard to be assertive in a male-dominated career, but the fact that I didn’t give up — even if something went wrong — that’s something I think about a lot.”

Related topics

You might also like:.

• Engineering grad at the helm of Cadillac Fairview remembers the learnings and friendships of his Concordia years
• Father’s legacy at Concordia honoured with scholarship for mechanical engineering students
• $250,000 from Embark Foundation ignites innovation at Gina Cody School of Engineering and Computer Science

© Concordia University