3 steps of the problem solving process

How it works

For Business

Join Mind Tools

Article • 4 min read

The Problem-Solving Process

Looking at the basic problem-solving process to help keep you on the right track.

By the Mind Tools Content Team

Problem-solving is an important part of planning and decision-making. The process has much in common with the decision-making process, and in the case of complex decisions, can form part of the process itself.

We face and solve problems every day, in a variety of guises and of differing complexity. Some, such as the resolution of a serious complaint, require a significant amount of time, thought and investigation. Others, such as a printer running out of paper, are so quickly resolved they barely register as a problem at all.

Despite the everyday occurrence of problems, many people lack confidence when it comes to solving them, and as a result may chose to stay with the status quo rather than tackle the issue. Broken down into steps, however, the problem-solving process is very simple. While there are many tools and techniques available to help us solve problems, the outline process remains the same.

The main stages of problem-solving are outlined below, though not all are required for every problem that needs to be solved.

1. Define the Problem

Clarify the problem before trying to solve it. A common mistake with problem-solving is to react to what the problem appears to be, rather than what it actually is. Write down a simple statement of the problem, and then underline the key words. Be certain there are no hidden assumptions in the key words you have underlined. One way of doing this is to use a synonym to replace the key words. For example, ‘We need to encourage higher productivity ’ might become ‘We need to promote superior output ’ which has a different meaning.

2. Analyze the Problem

Ask yourself, and others, the following questions.

• Where is the problem occurring?
• When is it occurring?
• Why is it happening?

Be careful not to jump to ‘who is causing the problem?’. When stressed and faced with a problem it is all too easy to assign blame. This, however, can cause negative feeling and does not help to solve the problem. As an example, if an employee is underperforming, the root of the problem might lie in a number of areas, such as lack of training, workplace bullying or management style. To assign immediate blame to the employee would not therefore resolve the underlying issue.

Once the answers to the where, when and why have been determined, the following questions should also be asked:

• Where can further information be found?
• Is this information correct, up-to-date and unbiased?
• What does this information mean in terms of the available options?

3. Generate Potential Solutions

When generating potential solutions it can be a good idea to have a mixture of ‘right brain’ and ‘left brain’ thinkers. In other words, some people who think laterally and some who think logically. This provides a balance in terms of generating the widest possible variety of solutions while also being realistic about what can be achieved. There are many tools and techniques which can help produce solutions, including thinking about the problem from a number of different perspectives, and brainstorming, where a team or individual write as many possibilities as they can think of to encourage lateral thinking and generate a broad range of potential solutions.

4. Select Best Solution

When selecting the best solution, consider:

• Is this a long-term solution, or a ‘quick fix’?
• Is the solution achievable in terms of available resources and time?
• Are there any risks associated with the chosen solution?
• Could the solution, in itself, lead to other problems?

This stage in particular demonstrates why problem-solving and decision-making are so closely related.

5. Take Action

In order to implement the chosen solution effectively, consider the following:

• What will the situation look like when the problem is resolved?
• What needs to be done to implement the solution? Are there systems or processes that need to be adjusted?
• What will be the success indicators?
• What are the timescales for the implementation? Does the scale of the problem/implementation require a project plan?
• Who is responsible?

Once the answers to all the above questions are written down, they can form the basis of an action plan.

6. Monitor and Review

One of the most important factors in successful problem-solving is continual observation and feedback. Use the success indicators in the action plan to monitor progress on a regular basis. Is everything as expected? Is everything on schedule? Keep an eye on priorities and timelines to prevent them from slipping.

If the indicators are not being met, or if timescales are slipping, consider what can be done. Was the plan realistic? If so, are sufficient resources being made available? Are these resources targeting the correct part of the plan? Or does the plan need to be amended? Regular review and discussion of the action plan is important so small adjustments can be made on a regular basis to help keep everything on track.

Once all the indicators have been met and the problem has been resolved, consider what steps can now be taken to prevent this type of problem recurring? It may be that the chosen solution already prevents a recurrence, however if an interim or partial solution has been chosen it is important not to lose momentum.

Problems, by their very nature, will not always fit neatly into a structured problem-solving process. This process, therefore, is designed as a framework which can be adapted to individual needs and nature.

Join Mind Tools and get access to exclusive content.

This resource is only available to Mind Tools members.

Already a member? Please Login here

Team Management

Learn the key aspects of managing a team, from building and developing your team, to working with different types of teams, and troubleshooting common problems.

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

Newest Releases

SWOT Analysis

SMART Goals

Mind Tools Store

About Mind Tools Content

Discover something new today

How to stop procrastinating.

Overcoming the Habit of Delaying Important Tasks

What Is Time Management?

Working Smarter to Enhance Productivity

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

Energizing yourself infographic.

Infographic Transcript

Infographic

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

Managing Conflict

Delegation and Empowerment

Performance Management

Leadership Skills

Developing Your Team

Talent Management

Problem Solving

Decision Making

Member Podcast

• 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
• 2023 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."

• 281.412.7766s
• [email protected]
• Learner Dashboard
• GET YOUR CAUSE MAPPING TEMPLATE

• About Cause Mapping®
• What is Root Cause Analysis?
• Cause Mapping® Method
• Cause Mapping® FAQs
• Why ThinkReliability?
• Online Workshops
• Online Short Courses
• On-Demand Training Catalog
• On-Demand Training Subscription
• Company Case Study
• Upcoming Webinars
• Webinar Archives
• Public Workshops
• Private Workshops
• Cause Mapping Certified Facilitator Program
• Our Services
• Facilitation, Consulting, and Coaching
• Root Cause Analysis Program Development
• Work Process Reliability™
• Cause Mapping® Template
• Root Cause Analysis Examples
• Video Library
• Articles and Downloads
• About ThinkReliability
• Client List
• Testimonials

Problem Solving - 3 Basic Steps

Don't complicate it.

Problems can be confusing. Your problem-solving process shouldn’t make them more confusing. With a variety of different tools available, it’s common for people in the same company to use different approaches and different terminology. This makes problem solving problematic. It shouldn’t be.

Some companies use 5Whys , some use fishbone diagrams , and some categorize incidents into generic buckets like " human error " and " procedure not followed ." Some problem-solving methods have six steps, some have eight steps and some have 14 steps. It’s easy to understand how employees get confused.

6-sigma is another widely recognized problem-solving tool. It has five steps with its own acronym, DMAIC: define, measure, analyze, improve and control. The first two steps are for defining and measuring the problem . The third step is the analysis . And the fourth and fifth steps are improve and control, and address solutions .

3 Basic Steps of Problem Solving

As the name suggests, problem solving starts with a problem and ends with solutions. The step in the middle is the analysis. The level of detail within a problem changes based on the magnitude of an issue, but the basic steps of problem solving remain the same regardless of the type of problem:

Step 1. Problem

Step 2. analysis, step 3. solutions.

But these steps are not necessarily what everyone does. Some groups jump directly to solutions after a hasty problem definition. The analysis step is regularly neglected. Individuals and organizations don’t dig into the details that are essential to understand the issue. In the Cause Mapping® method, the point of root cause analysis is to reveal what happened within an incident—to do that digging.

Step 1. Problem

A complete problem definition consists of several different questions:

• What is the problem?
• When did it happen?
• Where did it happen?
• What was the total impact to each of the organization’s overall goals?

These four questions capture what individuals see as a problem, along with the specifics about the setting of the issue (the time and place), and, importantly, the overall consequences to the organization. The traditional approach of writing a problem description as a few sentences doesn’t necessarily capture the information needed for a complete definition. Some organizations see their problem as a single effect, but that doesn’t reflect the nature of an actual issue since different negative outcomes can occur within the same incident. Specific pieces of information are captured within each of the four questions to provide a thorough definition of the problem.

The analysis step provides a clear explanation of an issue by breaking it down into parts. A simple way to organize the details of an incident is to make a timeline . Each piece of the incident in placed in chronological order. A timeline is an effective way to understand what happened and when for an issue.

Ultimately, the objective of problem solving is to turn the negative outcomes defined in step 1 into positive results. To do so, the causes that produced the unwanted outcomes must be identified. These causes provide both the explanation of the issue as well as control points for different solution options. This cause-and-effect approach is the basis of explaining and preventing a problem solving. It’s why cause-and-effect thinking is fundamental for troubleshooting, critical thinking and effective root cause analysis.

Many organizations are under-analyzing their problems because they stop at generic categories like procedure not followed, training less than adequate or management systems . This is a mistake. Learning how to dig a littler further, by asking more Why questions, can reveal significant insight about those chronic problems that people have come to accept as normal operations.

A Cause Map™ diagram provides a way for frontline personnel, technical leads and managers to communicate the details of an issue objectively, accurately and thoroughly. A cause-and-effect analysis can begin as a single, linear path that can be expanded into as much detail as needed to fully understand the issue.

Solutions are specific actions that control specific causes to produce specific outcomes. Both short-term and long-term solutions can be identified from a clear and accurate analysis. It is also important for people to understand that every cause doesn’t need to be solved. Most people believe that 15 causes require 15 solutions. That is not true. Changing just one cause along a causal path breaks that chain of events. Providing solutions on more than one causal path provides additional layers of protection to further reduce the risk of a similar issue occurring in the future.

The Basics of Problem Solving Don't Change

These three steps of problem solving can be applied consistently across an organization from frontline troubleshooters to the executives. First principles should be the foundation of a company’s problem-solving culture. Overlooking these basics erodes critical thinking. Even though the fundamentals of cause-and-effect don’t change, organizations and individuals continue to find special adjectives, algorithms and jargon appealing. Teaching too many tools and using contrived terms such as “true root causal factors” is a symptom of ignoring lean principles. Don’t do that which is unnecessary.

Your problems may be complex, but your problem-solving process should be clear and simple. A scientific approach that objectively explains what happened and why (cause and effect) is sound. It’s the basis for understanding and solving a problem – any problem. It works on the farm, in the power plant, at the manufacturing company and at an airline. It works for the cancer researcher and for the auto mechanic. It also works the same way for safety incidents, production losses and equipment failures. Cause and effect doesn’t change. Just test it.

If you’re interested in seeing one of your problems dissected as a Cause Map diagram, send us an email or call the ThinkReliability office. We’ll arrange a call to step through your issue. You can also learn more about improving the way your organization investigates and prevents problems through one of our upcoming online webinars, short courses or workshops .

Want to learn more? Watch our 28-minute video on problem-solving basics.

Share This Post With A Friend

Similar Posts

Other resources.

• Root Cause Analysis blog
• Patient Safety blog

READ BY - - - - - - - - - -

Other Resources - - - - - - - - - -

Sign Up For Our eNewsletter

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)

Join our FREE training and learn the 5 things you can do to become a top 1% facilitator

What is problem-solving and how to do it right steps, processes, exercises.

The better your problem-solving skills are, the better (and easier!) your life will be. Organized problem-solving is a killer career skill - learn all about it here.

Whether we’re trying to solve a technical problem at work, or trying to navigate around a roadblock that Google Maps doesn’t see – most people are problem-solving every single day . 

But how effective are you at tackling the challenges in your life? Do you have a bullet-proof process you follow that ensures solid outcomes, or... Do you act on a whim of inspiration (or lack thereof) to resolve your pressing problems?

Here’s the thing: the better your problem-solving skills are - the better (and easier!) your life will be (both professionally and personally). Organized problem-solving is a killer career (and life!) skill, so if you want to learn how to do it in the most efficient way possible, you’ve come to the right place.  

Read along to learn more about the steps, techniques and exercises of the problem-solving process.

• 1. Do you want a Career in UX? 
•  Learn the Principles of UX Design
• Master a UX Design Tool ‍

What is Problem-Solving?

We’re faced with the reality of having to solve problems every day, both in our private and professional lives. So why do we even need to learn about problem-solving? Aren’t we versed in it well enough already?

Well, what separates problem-solving from dealing with the usual day-to-day issues is that it’s a distinct process that allows you to go beyond the standard approaches to solving a problem and allows you to come up with more effective and efficient solutions. Or in other words, problem-solving allows you to knock out those problems with less effort. 

Just like with any other skill, there’s an efficient way to solve problems, and a non-efficient one. While it might be tempting to go for the quickest fix for your challenge without giving it much thought, it will only end up costing you more time down the road. Quick fixes are rarely (if ever!) effective and end up being massive time wasters. 

What separates problem-solving from dealing with the usual day-to-day issues is that it’s a distinct process that allows you to go beyond the standard approaches to solving a problem and allows you to come up with more effective and efficient solutions.

On the other hand, following a systemized clear process for problem-solving allows you to shortcut inefficiencies and time-wasters, turn your challenges into opportunities, and tackle problems of any scope without the usual stress and hassle. 

What is the process that you need to follow, then? We’re glad you asked...

The Five Stages of Problem-Solving

So what’s the best way to move through the problem-solving process? There’s a 5-step process that you can follow that will allow you to solve your challenges more efficiently and effectively. In short, you need to move through these 5 steps: 

• Defining a problem
• Ideating on a solution
• Committing to a course of action
• Implementing your solution
• And finally – analyzing the results. 

Let’s look at each of those stages in detail.

Step 1: Defining The Problem

The first step might sound obvious, but trust us, you don’t want to skip it! Clearly defining and framing your challenge will help you guide your efforts and make sure you’re focussing on the things that matter, instead of being distracted by a myriad of other options, problems and issues that come up. 

For once, you have to make sure you’re trying to solve the root cause, and not trying to mend the symptoms of it. For instance, if you keep losing users during your app onboarding process, you might jump to the conclusion that you need to tweak the process itself: change the copy, the screens, or the sequence of steps.

But unless you have clear evidence that confirms your hypothesis, your challenge might have an entirely different root cause, e.g. in confusing marketing communication prior to the app download. 

Clearly defining and framing your challenge will help you guide your efforts and make sure you’re focussing on the things that matter, all the while ensuring that you’re trying to solve the root cause, and not trying to mend the symptoms of it

That’s why it’s essential you take a close look at the entire problem, not just at a fraction of it.

There are several exercises that can help you get a broader, more holistic view of the problem, some of our all-time favorites include Expert Interviews, How Might We, or The Map. Check out the step-by-step instructions on how to run them (along with 5 more exercises for framing your challenge!) here. 

When in doubt, map out your challenge, and always try to tackle the bottlenecks that are more upstream - it’s likely that solving them will solve a couple of other challenges down the flow.

You also have to be mindful of how you frame the challenge: resist the urge to include a pre-defined solution into your problem statement. Priming your solutions to a predestined outcome destroys the purpose of following a step-by-step process in the first place!  

Steer clear of formulations like:

We need to change the onboarding process... or We need to improve ad copy to increase conversions. 

Instead, opt for more neutral, problem-oriented statements that don’t include a solution suggestion in them:

The drop off rate during the onboarding process is too high or Our ad conversion rates are below the norm.

Pro tip: Reframing your challenge as a ‘How Might We’ statement is a great way to spark up new ideas, opening your problem to a broader set of solutions, and is just a great way to reframe your problem into a more positive statement (without implying the possible solution!)

For example, following the onboarding drop-off rate problem we mentioned earlier, instead of framing it as a problem, you could opt for:

How Might We decrease the drop-off rate during the onboarding process? 

Find out more about the best exercises for problem framing here!

Now that you have a clear idea of what you’re trying to solve, it’s move on to the next phase of the problem-solving process.

Learn more about facilitation and workshopping in our FREE FACILITATION COMMUNITY

Step 2: ideating a solution.

Get ready to roll up your sleeves and challenge the status quo! This step of the problem-solving process is all about thinking outside of the box, challenging old assumptions, and thinking laterally. 

This stage is the one that tends to cause the most overwhelm in teams because it requires just the right balance of creativity and critical thinking, which tends to cause a lot of friction.

Our best advice?

Let go of the pressure to produce a polished, thought-through solution at this stage. You can hash out the details at a later point. Our goal right now is to come up with a direction, a prototype if you may, of where we want to move towards. 

Embrace the “quantity over quality” motto, and let your creative juices flow! Now, we’re not saying you should roll with sub-par ideas. But you shouldn’t get too fixated on feasibility and viability just yet . 

Your main goal during this step is to spark ideas, kick off your thinking process in the right direction, venture out of the familiar territories and think outside the box. 

For the ideation to be the most effective your team will have to feel safe to challenge the norm and wide-spread assumptions. So lay judgment by side, there is no space for “that’s the way it’s always been done” in this step.

For your ideation sessions to be as efficient as possible, we highly recommend to run them in a workshop setting: this helps reduce the usual drawbacks of open discussions in teams (i.e. groupthink & team politics!)

Our favorite exercises to run during this phase include Lightning Demos, Sketching, and variations of Brainstorming.  We crafted an entire article on how to run and facilitate these exercises in a separate article, so check it out of you’re going to be running an ideation session anytime soon!

Step 3: Choosing the Best Strategy & Committing

It’s time to decide which of the ideas that you generated in the last step will be the one you’ll implement. 

This step is arguably the hardest one to complete smoothly: groupthink, team politics, differences in opinions and communication styles all make it very hard to align a team on a common course of action. 

If you want to avoid the usual pitfalls of team decision-making, we recommend you steer clear of open unstructured discussion. While it’s useful in some scenarios, it’s a poor choice for when you need to make a decision, because it tends to reward the loudest people in the room, rather than give way to the best ideas. 

It’s crucial you not only commit to a course of action but get full buy-in from the team. If your team members don’t understand the reasons for a decision, or are not fully onboard, the implementation of your decision will be half-hearted, and that’s definitely not what you want! 

To achieve that, opt for anonymized, multi-layered voting, and include guided exercises like Storyboarding to prioritize your ideas. 

We’ve gathered the list of our top-rated decision-making exercises, along with step-by-step instructions on how to run them in this article!

As a bonus tip, we recommend you involve a facilitator throughout the entire process. They will help align the team, and guide them through prioritizing and de-prioritizing solutions, as well as defining the next steps. 

Pro tip : If you’re not the ultimate decision maker on the issue you’re trying to solve, make sure they’re in the room when the call is being made! Having a Decider in the room ensures that the decisions you come to will actually get executed on after, instead of getting shut down by your superiors after. 

Join our FREE community and connect with other Facilitators and Workshoppers

Step 4: implementing your solution.

Here’s a truth that might be hard to swallow: it doesn’t matter how innovative, creative, or original your idea is, if your execution is weak. 

One of our favourite illustrations of how this works in practice comes from the book “ Anything you want ” by Derek Sivers. He reveals that ideas should be treated as multipliers of execution. What this means is that a mediocre, “so-so” idea could be worth millions if executed well, while a “brilliant” idea can completely flop with bad execution. 

That’s why this step is crucial if you want to really master the problem-solving process. 

What do we mean by execution? Everything that happens after the whiteboards are wiped clean and your team starts to action the outcomes of your sessions, be it prototyping, development, or promotion. 

But don’t just take our word for it, look at the example of how execution affected Nintendo’s sales:

In the past few years, Nintendo has come up with 3 products: the Wii, the Wii U and the Switch. Check out their sales figures on the graph below - Wii is the clear-cut leader, followed by Switch, and finally Wii U lagging behind.

The Wii was unbelievably successful - it was a genuinely unique, “brilliant”-level idea and it had a “brilliant” execution (20x $10 million = $200 million). It is  one of the fastest selling game consoles of all time and it completely took over the market.

The next product was called Wii U and it was a “great” concept but the execution was absolutely terrible. So even though this product was very interesting and innovative, the end result was 15x $1,000 = $15,000. 

Finally, Nintendo took the Wii U concept and tried it again with the Switch. The idea was “so so” as it was already done before, but the execution was “brilliant”. So, 5x $10 million = $50 million! Much better.

Bottom line?  

The same idea can either make no dent in the market and damage your share price OR become a market hit and increase your share price dramatically. The only difference between the two scenarios – execution.

So shift your focus from coming up with crazy, innovative, outlandish ideas that will disrupt the market, and concentrate on really nailing down your execution instead. 

This is likely the least “workshoppy” step out of the entire problem-solving process because it requires less alignment and decision-making and more..well.. Execution!

But hey, we wouldn’t be called “Workshopper” if we didn't offer you at least one way to optimize and workshopify (yup, we’re making it a thing) your execution process. 

Cue in….prototyping. 

We’re huge fans of prototyping all big solutions (and testing them!) The main reason?

This saves us time AND money! Prototyping and testing your solutions (especially if they’re time and investment-demanding) is a great way to make sure you’re creating something that is actually needed. 

The key with prototyping the right way is to keep it simple. Don’t invest too much time, or resources into it. The goal is to gather data for your future decisions, not to create a near-to-perfect mockup of your solution.  

There are LOADS of prototyping forms and techniques, and if you’d like to learn more on the subject you should definitely check out our extensive prototyping guide.  

Step 5: Analyzing the Results

You’re nearly done, woo! Now that you have defined the right problem to tackle, brainstormed the solutions, aligned your team on the course of action, and put your plan into action it’s time to take stock of your efforts. 

Seek feedback from all involved parties, analyze the data you’ve gathered, look at the bottom line of your efforts, and  take a hard look at your problem: did it get solved? And even more than that, did the process feel smoother, easier, and more efficient than it normally is?

Running a retrospective is a great way to highlight things that went well and that you should keep for your next round of problem.solving, as well as pinpoint inefficiencies that you can eliminate.

‍ But which kind of retrospective should you run? There are loads of options, and it’s easy to feel overwhelmed by them all, so we gathered our favorite retrospective variations in this article.

And there you have it, you just completed the cycle of  problem-solving. We highly recommend you follow through with all the steps, without leaving any out. They all complement and build on each other, and it’s the combination of all 5 of them that makes the process effective. 

Now that you have the problem solving process down, you might be wondering…

Do I need any special skills in order to be able to move through that process?

And the answer is… sort of! More in this in the next section.

Problem-Solving Skills 

While your skill set will need to adapt and change based on the challenges you’ll be working on, most efficient problem-solvers have a solid foundation of these key skills:   

• Active listening. While you might be the expert in the area of your challenge, there’s not a single person on Earth that knows it all! Being open to others’ perspectives and practicing active listening will come in very handy during step 1 of the process, as you’re trying to define the scope and the exact angle of the problem you’re working on.
• Analytical approach. Your analytical skills will help you understand problems and effectively develop solutions. You will also need analytical skills during research to help distinguish between effective and ineffective solutions.
• Communication. Is there a single area of expertise that DOESN’T require strong communication skills? We honestly don’t think so! Just like with any other life area, clear communication can make or break your problem-solving process. Being able to clearly communicate why you need to solve this challenge to your team, as well as align your team on the course of action are crucial for the success of the process. 
• Decision-making. Ultimately, you will need to make a decision about how to solve problems that arise. A process without outcomes–regardless of how well thought-out and elaborate–is useless! If you want your problem-solving huddles to be effective, you have to come to grips with prioritization techniques and decision-making frameworks. 
• Facilitation. Problem-solving revolves around being able to guide a group or a team to a common decision, and facilitation skills are essential in making that happen. Knowing how to facilitate will make it easy to keep the group focussed on the challenge, shortcut circular discussions, and make sure you’re moving along to solving the problem instead of just treading waters with fruitless discussions. 

Not checking every single skill of your list just yet? Not to worry, the next section will give you practical tools on how to level up and improve your problem-solving skills.

How to Improve Your Problem-Solving Skills

Just like with any other skill, problem-solving is not an innate talent that you either have or you don’t.  There are concrete steps you can take to improve your skills. 

Here are some things that will get you closer to mastering the problem-solving process:

• Practice, Practice, Practice

Practice makes perfect, and problem-solving skills are no exception! Seek opportunities to utilize and develop these skills any time you can. 

If you don’t know where or how to start just yet, here’s a suggestion that will get you up and running in no time: run a quick problem-solving session on a challenge that has been bothering your team for a while now. 

It doesn’t need to be the big strategic decision or the issue defining the future of the company. Something easy and manageable (like optimizing office space or improving team communication) will do. 

As you start feeling more comfortable with the problem-solving techniques, you can start tackling bigger challenges. Before you know it, you’ll master the art of creative problem-solving!

• Use a tried and tested problem-solving workshop

Facilitation is one of the essential skills for problem-solving. But here’s the thing… Facilitation skills on their own won’t lead you to a solved challenge.

While being able to shortcut aimless discussions is a great skill, you have to make sure your problem-solving session has tangible outcomes. Using a tried and tested method, a workshop, is one of the easiest ways to do that. 

Our best advice is to get started with a tried and tested problem-solving workshop like the Lightning Decision Jam . The LDJ has all the right ingredients for quick, effective problem solving that leads to tangible outcomes. Give it a go!

• Learn from your peers

You may have colleagues who are skilled problem solvers. Observing how those colleagues solve problems can help you improve your own skills. 

If possible, ask one of your more experienced colleagues if you can observe their techniques. Ask them relevant questions and try to apply as many of the new found skills i your career as possible. 

• Learn & Practice the best problem-solving exercises

Having a toolbox of problem-solving exercises to pull from that can fit any type of challenge will make you a more versatile problem-solver and will make solving challenges that much easier for you! 

Once you get used to the groove of learning how to combine them into effective sessions or workshops, there’ll be no stopping you. What are some of the most effective problem-solving exercises? Glad you asked! We’ve gathered our favorite ones here, check it out! 

And there you have it, you’re now fully equipped for running creative problem-sessions with confidence and ease! Whichever method or exercise you choose, remember to keep track of your wins, and learn as much as you can from your losses! 

Anastasia Ushakova

Brand Strategist, Digital Marketer, and a Workshopper.

When Do You Need a Facilitator?

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus.

The Ultimate Facilitation Glossary: 50 Facilitation Terms You Should Know (From A-Z)

How To Improve Team Collaboration

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

Table of Contents

The problem-solving process, how to solve problems: 5 steps, train to solve problems with lean today, what is problem solving steps, techniques, & best practices explained.

Problem solving is the art of identifying problems and implementing the best possible solutions. Revisiting your problem-solving skills may be the missing piece to leveraging the performance of your business, achieving Lean success, or unlocking your professional potential. 

Ask any colleague if they’re an effective problem-solver and their likely answer will be, “Of course! I solve problems every day.” 

Problem solving is part of most job descriptions, sure. But not everyone can do it consistently. 

Problem solving is the process of defining a problem, identifying its root cause, prioritizing and selecting potential solutions, and implementing the chosen solution.

There’s no one-size-fits-all problem-solving process. Often, it’s a unique methodology that aligns your short- and long-term objectives with the resources at your disposal. Nonetheless, many paradigms center problem solving as a pathway for achieving one’s goals faster and smarter. 

One example is the Six Sigma framework , which emphasizes eliminating errors and refining the customer experience, thereby improving business outcomes. Developed originally by Motorola, the Six Sigma process identifies problems from the perspective of customer satisfaction and improving product delivery. 

Lean management, a similar method, is about streamlining company processes over time so they become “leaner” while producing better outcomes. 

Trendy business management lingo aside, both of these frameworks teach us that investing in your problem solving process for personal and professional arenas will bring better productivity.

1. Precisely Identify Problems

As obvious as it seems, identifying the problem is the first step in the problem-solving process. Pinpointing a problem at the beginning of the process will guide your research, collaboration, and solutions in the right direction. 

At this stage, your task is to identify the scope and substance of the problem. Ask yourself a series of questions: 

• What’s the problem? 
• How many subsets of issues are underneath this problem? 
• What subject areas, departments of work, or functions of business can best define this problem? 

Although some problems are naturally large in scope, precision is key. Write out the problems as statements in planning sheets . Should information or feedback during a later step alter the scope of your problem, revise the statements. 

Framing the problem at this stage will help you stay focused if distractions come up in later stages. Furthermore, how you frame a problem will aid your search for a solution. A strategy of building Lean success, for instance, will emphasize identifying and improving upon inefficient systems. 

2. Collect Information and Plan 

The second step is to collect information and plan the brainstorming process. This is another foundational step to road mapping your problem-solving process. Data, after all, is useful in identifying the scope and substance of your problems. 

Collecting information on the exact details of the problem, however, is done to narrow the brainstorming portion to help you evaluate the outcomes later. Don’t overwhelm yourself with unnecessary information — use the problem statements that you identified in step one as a north star in your research process. 

This stage should also include some planning. Ask yourself:

• What parties will ultimately decide a solution? 
• Whose voices and ideas should be heard in the brainstorming process? 
• What resources are at your disposal for implementing a solution? 

Establish a plan and timeline for steps 3-5. 

3. Brainstorm Solutions

Brainstorming solutions is the bread and butter of the problem-solving process. At this stage, focus on generating creative ideas. As long as the solution directly addresses the problem statements and achieves your goals, don’t immediately rule it out. 

Moreover, solutions are rarely a one-step answer and are more like a roadmap with a set of actions. As you brainstorm ideas, map out these solutions visually and include any relevant factors such as costs involved, action steps, and involved parties. 

With Lean success in mind, stay focused on solutions that minimize waste and improve the flow of business ecosystems. 

Become a Quality Management Professional

• 10% Growth In Jobs Of Quality Managers Profiles By 2025
• 11% Revenue Growth For Organisations Improving Quality

Certified Lean Six Sigma Green Belt

• 4 hands-on projects to perfect the skills learnt
• 4 simulation test papers for self-assessment

Lean Six Sigma Expert

• IASSC® Lean Six Sigma Green Belt and Black Belt certification
• 13 Projects, 12 Simulation exams, 18 Case Studies & 114 PDUs

Here's what learners are saying regarding our programs:

Xueting Liu

Mechanical engineer student at sargents pty. ltd. ,.

A great training and proper exercise with step-by-step guide! I'll give a rating of 10 out of 10 for this training.

Abdus Salam

I have completed the Lean Six Sigma Expert Master’s Program from Simplilearn. And after the course, I could take up new projects and perform better. My average pay rate for a research position increased by 21%.

4. Decide and Implement

The most critical stage is selecting a solution. Easier said than done. Consider the criteria that has arisen in previous steps as you decide on a solution that meets your needs. 

Once you select a course of action, implement it. 

Practicing due diligence in earlier stages of the process will ensure that your chosen course of action has been evaluated from all angles. Often, efficient implementation requires us to act correctly and successfully the first time, rather than being hurried and sloppy. Further compilations will create more problems, bringing you back to step 1. 

5. Evaluate

Exercise humility and evaluate your solution honestly. Did you achieve the results you hoped for? What would you do differently next time? 

As some experts note, formulating feedback channels into your evaluation helps solidify future success. A framework like Lean success, for example, will use certain key performance indicators (KPIs) like quality, delivery success, reducing errors, and more. Establish metrics aligned with company goals to assess your solutions.

Master skills like measurement system analysis, lean principles, hypothesis testing, process analysis and DFSS tools with our Lean Six Sigma Green Belt Training Course . Sign-up today!

Become a quality expert with Simplilearn’s Lean Six Sigma Green Belt . This Lean Six Sigma certification program will help you gain key skills to excel in digital transformation projects while improving quality and ultimate business results.

In this course, you will learn about two critical operations management methodologies – Lean practices and Six Sigma to accelerate business improvement.

Our Quality Management Courses Duration And Fees

Explore our top Quality Management Courses and take the first step towards career success

Get Free Certifications with free video courses

Quality Management

Lean Management

Project Management

Learn from industry experts with free masterclasses, digital marketing.

The Top 10 AI Tools You Need to Master Marketing in 2024

Unlock Digital Marketing Career Success Secrets for 2024 with Purdue University

Your Gateway to Game-changing Digital Marketing Careers in 2024 with Purdue University

Recommended Reads

Introduction to Machine Learning: A Beginner's Guide

Webinar Wrap-up: Mastering Problem Solving: Career Tips for Digital Transformation Jobs

An Ultimate Guide That Helps You to Develop and Improve Problem Solving in Programming

Free eBook: 21 Resources to Find the Data You Need

ITIL Problem Workaround – A Leader’s Guide to Manage Problems

Your One-Stop Solution to Understand Coin Change Problem

Get Affiliated Certifications with Live Class programs

• PMP, PMI, PMBOK, CAPM, PgMP, PfMP, ACP, PBA, RMP, SP, and OPM3 are registered marks of the Project Management Institute, Inc.

The Ultimate Problem-Solving Process Guide: 31 Steps and Resources

[email protected]

16 Min Read

Got Challenges with Your Problem-Solving Process? Are You Frustrated?

prob·lem-solv·ing noun

-the process of finding solutions to difficult or complex issues.

It sounds so simple, doesn’t it?

But in reality problem-solving is hard. It’s almost always more complex than it seems. That’s why problem-solving can be so frustrating sometimes. You can feel like you’re spinning your wheels, arguing in circles, or just failing to find answers that actually work.

And when you’ve got a group working on a problem, it can get even muddier …differences of opinions, viewpoints colored by different backgrounds, history, life experiences, you name it. We’re all looking at life and work from different angles, and that often means disagreement. Sometimes sharp disagreement.

That human element, figuring out how to take ourselves out of the equation and make solid, fact-based decisions , is precisely why there’s been so much written on problem-solving. Which creates its own set of problems.

Whose method is best? How can you possibly sift through them all? Are we to have one person complete the entire problem-solving process by themselves or rely on a larger team to find answers to our most vexing challenges in the workplace ?

Today, we’re going to make sense of it all. We’ll take a close look at nine top problem-solving methods. Then we’ll grab the best elements of all of them to give you a process that will have your team solving problems faster, with better results , and maybe with less sharp disagreement.

Ready to dive in?

9 Profitable Problem-Solving Techniques and Methods

While there are loads of methods to choose from, we are going to focus on nine of the more common ones. You can use some of these problem-solving techniques reactively to solve a known issue or proactively to find more efficient or effective ways of performing tasks. If you want to explore other methods, check out this resource here .

A helpful bit of advice here is to reassure people that you aren’t here to identify the person that caused the problem . You’re working to surface the issue, solve it and make sure it doesn’t happen again, regardless of the person working on the process. It can’t be understated how important it is to continually reassure people of this so that you get unfiltered access to information.

Without this, people will often hide things to protect themselves . After all, nobody wants to look bad, do they?

With that said, let’s get started…

Alex Osborn coined the term “Creative Problem Solving” in the 1940s with this simple four-step process:

• Clarify : Explore the vision, gather data, and formulate questions.
• Ideate : This stage should use brainstorming to generate divergent thinking and ideas rather than the random ideas normally associated with brainstorming.
• Develop : Formulate solutions as part of an overall plan.
• Implement : Put the plan into practice and communicate it to all parties.

Source: http://www.davidcooperrider.com/ai-process/

This method seeks, first and foremost, to identify the strengths in people and organizations and play to that “positive core” rather than focus our energies on improving weaknesses . It starts with an “affirmative topic,” followed by the “positive core (strengths).” Then this method delves into the following stages:

• Discovery (fact-finding)
• Dream (visioning the future)
• Design (strategic purpose)
• Destiny (continuous improvement)

This method simply suggests that we ask “Why” at least five times during our review of the problem and in search of a fix. This helps us dig deeper to find the the true reason for the problem, or the root cause. Now, this doesn’t mean we just keeping asking the same question five times. Once we get an answer to our first “why”, we ask why to that answer until we get to five “whys”.

Using the “five whys” is part of the “Analyze” phase of Six Sigma but can be used with or without the full Six Sigma process.

Review this simple Wikipedia example of the 5 Whys in action:

The vehicle will not start. (the problem)

• Why? – The battery is dead. (First why)
• Why? – The alternator is not functioning. (Second why)
• Why? – The alternator belt has broken. (Third why)
• Why? – The alternator belt was well beyond its useful service life and not replaced. (Fourth why)
• Why? – The vehicle was not maintained according to the recommended service schedule. (Fifth why, a root cause)

While many people have at least heard of Lean or Six Sigma, do we know what it is? Like many problem-solving processes, it has five main steps to follow.

• Define : Clearly laying out the problem and soliciting feedback from those who are customers of the process is necessary to starting off on the right foot.
• Measure : Quantifying the current state of the problem is a key to measuring how well the fix performed once it was implemented.
• Analyze : Finding out the root cause of the problem (see number 5 “Root Cause Analysis” below) is one of the hardest and least explored steps of Six Sigma.
• Improve : Crafting, executing, and testing the solution for measureable improvement is key. What doesn’t get implemented and measured really won’t make a difference.
• Control : Sustaining the fix through a monitoring plan will ensure things continue to stay on track rather than being a short-lived solution.

Compared to other methods, you’ll more often find this technique in a reactive problem-solving mode, but it is helpful nonetheless. Put simply, it requires a persistent approach to finding the highest-level cause , since most reasons you’ll uncover for a problem don’t tell the whole story.

Most of the time, there are many factors that contributed to an issue. The main reason is often shrouded in either intentional or unintentional secrecy. T aking the time to drill down to the root of the issue is key to truly solving the problem.

Named for W. Edwards Deming and Walter A. Shewhart, this model follows a four-step process:

• Plan : Establish goals and objectives at the outset to gain agreement . It’s best to start on a small scale in order to test results and get a quick win.
• Do : This step is all about the implementation and execution of the solution .
• Check : Study and compare actual to expected results. Chart this data to identify trends.
• Act/Adjust : If the check phase showed different results, then adjust accordingly . If worse than expected, then try another fix. If the same or better than expected, then use that as the new baseline for future improvements.

While this is named “8D” for eight disciplines, there are actually nine , because the first is listed as step zero. Each of the disciplines represents a phase of this process. Its aim is to implement a quick fix in the short term while working on a more permanent solution with no recurring issues.

• Prepare and Plan : Collecting initial information from the team and preparing your approach to the process is a necessary first step.
• Form a Team : Select a cross-functional team of people, one leader to run meetings and the process, and one champion/sponsor who will be the final decision-maker.
• Describe the Problem : Using inductive and deductive reasoning approaches , lay out the precise issue to be corrected.
• Interim Containment Action : Determine if an interim solution needs to be implemented or if it can wait until the final fix is firmed up. If necessary, the interim action is usually removed once the permanent solution is ready for implementation.
• Root Cause Analysis and Escape Point : Finding the root of the issue and where in the process it could’ve been found but was not will help identify where and why the issue happened.
• Permanent Corrective Action : Incorporating key criteria into the solution, including requirements and wants, will help ensure buy-in from the team and your champion.
• Implement and Validate the Permanent Corrective Action : Measuring results from the fix implemented validates it or sends the team back to the drawing board to identity a more robust solution.
• Prevent Recurrence : Updating work procedure documents and regular communication about the changes are important to keep old habits in check.
• Closure and Team Celebration : Taking time to praise the team for their efforts in resolving the problem acknowledges the part each person played and offers a way to move forward.

The US Army has been solving problems for more than a couple of centuries , so why not take a look at the problem-solving process they’ve refined over many years? They recommend this five step process:

• Identify the Problem : Take time to understand the situation and define a scope and limitations before moving forward.
• Gather Information : Uncover facts, assumptions, and opinions about the problem, and challenge them to get to the truth.
• Five screening items should be questioned. Is it feasible, acceptable, distinguishable, and complete?
• Evaluation criteria should have these 5 elements: short title, definition, unit of measure, benchmark, and formula.
• Generate, Analyze, and Compare Possible Solutions : Most fixes are analyzed, but do you compare yours to one another as a final vetting method?
• Choose a Solution and Implement : Put the fix into practice and follow up to ensure it is being followed consistently and having the desired effect.

Tim Hurson introduced this model in 2007 with his book, Think Better. It consists of the following six actions.

• Ask “What is going on?” : Define the impact of the problem and the aim of its solution.
• Ask “What is success?” : Spell out the expected outcome, what should not be in fix, values to be considered, and how things will be evaluated.
• Ask “What is the question?” : Tailor questions to the problem type. Valuable resources can be wasted asking questions that aren’t truly relevant to the issue.
• Generate answers : Prioritize answers that are the most relevant to solutions, without excluding any suggestion to present to the decision-makers.
• Forge the solution : Refine the raw list of prioritized fixes, looking for ways to combine them for a more powerful solution or eliminate fixes that don’t fit the evaluation criteria.
• Align resources: Identify resources, team, and stakeholders needed to implement and maintain the solution.

Steal This Thorough 8-Step Problem-Solving Process

Now that we’ve reviewed a number of problem-solving methods, we’ve compiled the various steps into a straightforward, yet in-depth, s tep-by-step process to use the best of all methods.

Dig Deep: Identify, Define, and Clarify the Issue

“Elementary, my dear Watson,” you might say.

This is true, but we often forget the fundamentals before trying to solve a problem. So take some time to gain understanding of critical stakeholder’s viewpoints to clarify the problem and cement consensus behind what the issue really is.

Sometimes it feels like you’re on the same page, but minor misunderstandings mean you’re not really in full agreement.. It’s better to take the time to drill down on an issue before you get too far into solving a problem that may not be the exact problem . Which leads us to…

Dig Deeper: Root Cause Analysis

This part of the process involves identifying these three items :

• What happened?
• Why did it happen?
• What process do we need to employ to significantly reduce the chances of it happening again ?

You’ll usually need to sort through a series of situations to find the primary cause. So be careful not to stop at the first cause you uncover . Dig further into the situation to expose the root of the issue. We don’t want to install a solution that only fixes a surface-level issue and not the root. T here are typically three types of causes :

• Physical: Perhaps a part failed due to poor design or manufacturing.
• Human error: A person either did something wrong or didn’t do what needed to be done.
• Organizational: This one is mostly about a system, process, or policy that contributed to the error .

When searching for the root cause, it is important to ensure people that you aren’t there to assign blame to a person but rather identify the problem so a fix can prevent future issues.

Produce a Variety of Solution Options

So far, you’ve approached the problem as a data scientist, searching for clues to the real issue. Now, it’s important to keep your eyes and ears open, in case you run across a fix suggested by one of those involved in the process failure. Because they are closest to the problem, they will often have an idea of how to fix things. In other cases, they may be too close, and unable to see how the process could change.

The bottom line is to solicit solution ideas from a variety of sources , both close to and far away from the process you’re trying to improve.

You just never know where the top fix might come from!

Fully Evaluate and Select Planned Fix(es)

Evaluating solutions to a defined problem can be tricky since each one will have cost, political, or other factors associated with it. Running each fix through a filter of cost and impact is a vital step toward identifying a solid solution and hopefully settling on the one with the highest impact and low or acceptable cost.

Categorizing each solution in one of these four categories can help teams sift through them:

• High Cost/Low Impact: Implement these last, if at all, since t hey are expensive and won’t move the needle much .
• Low Cost/Low Impact: These are cheap, but you won’t get much impact.
• High Cost/High Impact: These can be used but should be second to the next category.
• Low Cost/High Impact: Getting a solid “bang for your buck” is what these fixes are all about. Start with these first .

Document the Final Solution and What Success Looks Like

Formalize a document that all interested parties (front-line staff, supervisors, leadership, etc.) agree to follow. This will go a long way towards making sure everyone fully understands what the new process looks like, as well as what success will look like .

While it might seem tedious, try to be overly descriptive in the explanation of the solution and how success will be achieved. This is usually necessary to gain full buy-in and commitment to continually following the solution. We often assume certain things that others may not know unless we are more explicit with our communications.

Successfully Sell and Execute the Fix

Arriving at this stage in the process only to forget to consistently apply the solution would be a waste of time, yet many organizations fall down in the execution phase . Part of making sure that doesn’t happen is to communicate the fix and ask for questions multiple times until all parties have a solid grasp on what is now required of them.

One often-overlooked element of this is the politics involved in gaining approval for your solution. Knowing and anticipating objections of those in senior or key leadership positions is central to gaining buy-in before fix implementation.

Rinse and Repeat: Evaluate, Monitor, and Follow Up

Next, doing check-ins with the new process will ensure that the solution is working (or identity if further reforms are necessary) . You’ll also see if the measure of predefined success has been attained (or is making progress in that regard).

Without regularly monitoring the fix, you can only gauge the success or failure of the solution by speculation and hearsay. And without hard data to review, most people will tell their own version of the story.

Collaborative Contingencies, Iteration, and Course Correction

Going into any problem-solving process, we should take note that we will not be done once the solution is implemented (or even if it seems to be working better at the moment). Any part of any process will always be subject to the need for future iterations and course corrections . To think otherwise would be either foolish or naive.

There might need to be slight, moderate, or wholesale changes to the solution previously implemented as new information is gained, new technologies are discovered, etc.

14 Fruitful Resources and Exercises for Your Problem-Solving Journey

Want to test your problem-solving skills?

Take a look at these twenty case study scenario exercises to see how well you can come up with solutions to these problems.

Still have a desire to discover more about solving problems? Check out these 14 articles and books…

The Lean Six Sigma Pocket Toolbook: A Quick Reference Guide to Nearly 100 Tools for Improving Quality and Speed

This book is like a Bible for Lean Six Sigma , all in a pocket-sized package.

The American Society for Quality has a short article on how it’s important to focus on the problem before searching for a solution. Wondering if you are solving the right problems? Check out this Harvard Business Review article. Looking for a fun and easy problem-solving book that was written by a McKinsey consultant? Take a look!

If you want a deeper dive into the seven steps of Creative Problem Solving , see this article. Appreciative Inquiry has been proven effective in organizations ranging from Roadway Express and British Airways to the United Nations and the United States Navy. Review this book to join the positive revolution. The Seattle Police Department has put together nine case studies that you can practice solving . While they are about police work, they have practical application in the sleuthing of work-related problems. Need a resource to delve further into Root Cause Analysis? Look no further than this book for answers to your most vexing questions .

This solid case study illustrates the complexities of solving problems in business. Learn all about the “8Ds” with this concise primer. Need to reduce groupthink in your organization’s problem-solving process ? Check out this article from the Harvard Business Review.

Tim Hurson details his own Productive Thinking Model at great length in this book from the author. This simple five-step process will help you break down the problem, analyze it, prioritize solutions, and sell them internally.

Critical Thinking : A Beginner’s Guide To Critical Thinking, Better Decision Making, And Problem Solving!

Looking for assistance with your problem-solving process.

There’s a lot to take in here, but following some of these methods are sure to improve your problem-solving process. However, if you really want to take problem-solving to the next level, InitiativeOne can come alongside your team to help you solve problems much faster than you ever have before.

There are several parts to this leadership transformation process provided by InitiativeOne, including a personal profile assessment, cognitive learning, group sessions with real-world challenges, personal discovery, and a toolkit to empower leaders to perform at their best.

There are really only two things stopping good teams from being great. One is how they make decisions and two is how they solve problems. Contact us today to grow your team’s leadership performance by making decisions and solving problems more swiftly than ever before!

Originally published at www.initiative-one.com

• Spring 2024
• Spring 2023
• Spring 2022
• Spring 2021
• Spring 2020
• Summer 2019
• Spring 2019
• Summer 2018
• Spring 2018
• Spring 2017
• Spring 2016
• Staff and Contact
• Julia Robinson Math Festival
• Teachers’ Circle
• The Three Stages of the Problem-Solving Cycle

Essentially every problem-solving heuristic in mathematics goes back to George Polya’s How to Solve It ; my approach is no exception. However, this cyclic description might help to keep the process cognitively present.

A few months ago, I produced a video describing this the three stages of the problem-solving cycle: Understand, Strategize, and Implement. That is, we must first understand the problem, then we think of strategies that might help solve the problem, and finally we implement those strategies and see where they lead us. During two decades of observing myself and others in the teaching and learning process, I’ve noticed that the most neglected phase is often the first one—understanding the problem.

The Three Stages Explained

• What am I looking for?
• What is the unknown?
• Do I understand every word and concept in the problem?
• Am I familiar with the units in which measurements are given?
• Is there information that seems missing?
• Is there information that seems superfluous?
• Is the source of information bona fide? (Think about those instances when a friend gives you a puzzle to solve and you suspect there’s something wrong with the way the puzzle is posed.)
• Logical reasoning
• Pattern recognition
• Working backwards
• Adopting a different point of view
• Considering extreme cases
• Solving a simpler analogous problem
• Organizing data
• Making a visual representation
• Accounting for all possibilities
• Intelligent guessing and testing

I have produced videos explaining each one of these strategies individually using problems we have solved at the Chapel Hill Math Circle.

• Implementing : We now implement our strategy or set of strategies. As we progress, we check our reasoning and computations (if any). Many novice problem-solvers make the mistake of “doing something” before understanding (or at least thinking they understand) the problem. For instance, if you ask them “What are you looking for?”, they might not be able to answer. Certainly, it is possible to have an incorrect understanding of the problem, but that is different from not even realizing that we have to understand the problem before we attempt to solve it!

As we implement our strategies, we might not be able to solve the problem, but we might refine our understanding of the problem. As we refine our understanding of the problem, we can refine our strategy. As we refine our strategy and implement a new approach, we get closer to solving the problem, and so on. Of course, even after several iterations of this cycle spanning across hours, days, or even years, one may still not be able to solve a particular problem. That’s part of the enchanting beauty of mathematics.

I invite you to observe your own thinking—and that of your students—as you move along the problem-solving cycle!

[1] Problem-Solving Strategies in Mathematics , Posamentier and Krulik, 2015.

About the author: You may contact Hector Rosario at [email protected].

Share this:

1 response to the three stages of the problem-solving cycle.

Pingback: When (Not) to Give a Hint | Chapel Hill Math Circle

Leave a comment Cancel reply

• Search for:

Recent Posts

• When (Not) to Give a Hint
• Making “Maths” Make Sense
• Problem-Solving Pedagogy

Recent Comments

• September 2016
• Uncategorized
• Entries feed
• Comments feed
• WordPress.com

• Already have a WordPress.com account? Log in now.
• Subscribe Subscribed
• Copy shortlink
• Report this content
• View post in Reader
• Manage subscriptions
• Collapse this bar

The Five-Step Problem-Solving Process

Sometimes when you’re faced with a complex problem, it’s best to pause and take a step back. A break from…

Sometimes when you’re faced with a complex problem, it’s best to pause and take a step back. A break from routine will help you think creatively and objectively. Doing too much at the same time increases the chances of burnout.

Solving problems is easier when you align your thoughts with your actions. If you’re in multiple places at once mentally, you’re more likely to get overwhelmed under pressure. So, a problem-solving process follows specific steps to make it approachable and straightforward. This includes breaking down complex problems, understanding what you want to achieve, and allocating responsibilities to different people to ease some of the pressure.

The problem-solving process will help you measure your progress against factors like budget, timelines and deliverables. The point is to get the key stakeholders on the same page about the ‘what’, ‘why’ and ‘how’ of the process. ( Xanax ) Let’s discuss the five-step problem-solving process that you can adopt.

Problems at a workplace need not necessarily be situations that have a negative impact, such as a product failure or a change in government policy. Making a decision to alter the way your team works may also be a problem. Launching new products, technological upgrades, customer feedback collection exercises—all of these are also “problems” that need to be “solved”.

Here are the steps of a problem-solving process:

1. Defining the Problem

The first step in the process is often overlooked. To define the problem is to understand what it is that you’re solving for. This is also where you outline and write down your purpose—what you want to achieve and why. Making sure you know what the problem is can make it easier to follow up with the remaining steps. This will also help you identify which part of the problem needs more attention than others.

2. Analyzing the Problem

Analyze why the problem occurred and go deeper to understand the existing situation.  If it’s a product that has malfunctioned, assess factors like raw material, assembly line, and people involved to identify the problem areas. This will help you figure out if the problem will persist or recur. You can measure the solution against existing factors to assess its future viability.

3. Weighing the Options

Once you’ve figured out what the problem is and why it occurred, you can move on to generating multiple options as solutions. You can combine your existing knowledge with research and data to come up with viable and effective solutions. Thinking objectively and getting inputs from those involved in the process will broaden your perspective of the problem. You’ll be able to come up with better options if you’re open to ideas other than your own.

4. Implementing The Best Solution

Implementation will depend on the type of data at hand and other variables. Consider the big picture when you’re selecting the best option. Look at factors like how the solution will impact your budget, how soon you can implement it, and whether it can withstand setbacks or failures. If you need to make any tweaks or upgrades, make them happen in this stage.

5. Monitoring Progress

The problem-solving process doesn’t end at implementation. It requires constant monitoring to watch out for recurrences and relapses. It’s possible that something doesn’t work out as expected on implementation. To ensure the process functions smoothly, you can make changes as soon as you catch a miscalculation. Always stay on top of things by monitoring how far you’ve come and how much farther you have to go.

You can learn to solve any problem—big or small—with experience and patience. Adopt an impartial and analytical approach that has room for multiple perspectives. In the workplace, you’re often faced with situations like an unexpected system failure or a key employee quitting in the middle of a crucial project.

Problem-solving skills will help you face these situations head-on. Harappa Education’s Structuring Problems course will show you how to classify and categorize problems to discover effective solutions. Equipping yourself with the right knowledge will help you navigate work-related problems in a calm and competent manner.

Explore topics such as  Problem Solving , the  PICK Chart ,  How to Solve Problems  & the  Barriers to Problem Solving  from our Harappa Diaries blog section and develop your skills.

• school Campus Bookshelves
• menu_book Bookshelves
• perm_media Learning Objects
• login Login
• how_to_reg Request Instructor Account
• hub Instructor Commons
• Download Page (PDF)
• Download Full Book (PDF)
• Periodic Table
• Physics Constants
• Scientific Calculator
• Reference & Cite
• Tools expand_more
• Readability

selected template will load here

This action is not available.

3.3: Creative Problem-Solving Process

• Last updated
• Save as PDF
• Page ID 62756

LEARNING OBJECTIVES

By the end of this section, you will be able to:

• Describe the five steps in the creative problem-solving process
• Identify and describe common creative problem-solving tools

Creativity can be an important trait of an entrepreneur. In that discussion, we learned about creativity’s role in innovation . Here, we will look in more depth at creativity’s role in problem-solving . Let’s first formally define creativity as the development of original ideas to solve an issue. The intent of being an entrepreneur is to break away from practical norms and use imagination to embrace quick and effective solutions to an existing problem, usually outside the corporate environment.

The Steps of the Creative Problem-Solving Process

Training oneself to think like an entrepreneur means learning the steps to evaluating a challenge: clarify, ideate, develop, implement, and evaluate (Figure 3.3.1).

Step 1: Clarify

To clarify is the critical step of recognizing the existence of a gap between the current state and a desired state. This can also be thought of as having need awareness , which occurs when the entrepreneur notes a gap between societal or customer needs and actual circumstances. Clarifying the problem by speaking with clients and developing a detailed description of the problem brings the specifics of a problem to light. Failure to identify the specifics of a problem leaves the entrepreneur with the impossible task of solving a ghost problem, a problem that is fully unknown or unseen. To establish and maintain credibility, an entrepreneur must clarify the problem by focusing on solving the problem itself, rather than solving a symptom of the problem.

For example, a farm could have polluted water, but it would not be enough to solve the problem only on that farm. Clarifying would involve identifying the source of the pollution to adequately tackle the problem. After gaining an understanding of a problem, the entrepreneur should begin to formulate plans for eliminating the gap. A fishbone diagram, as shown in Figure 3.3.2, is a tool that can be used to identify the causes of such a problem.

In the case of our water pollution example, a fishbone diagram exploring the issue might reveal the items shown in Figure 3.3.3.

Step 2: Ideate

To ideate is the step of the creative problem-solving process that involves generating and detailing ideas by the entrepreneur. After collecting all information relevant to the problem, the entrepreneur lists as many causes of the problem as possible. This is the step in which the largest variety of ideas are put forth. Each idea must be evaluated for feasibility and cost as a solution to the problem. If a farm does not have clean water, for example, the entrepreneur must list causes of toxic water and eliminate as many of those causes as possible. The entrepreneur must then move forward investigating solutions to bring the water back to a safe state. If, say, nearby livestock are polluting the water, the livestock should be isolated from the water source.

Step 3: Develop

To develop is the step in which the entrepreneur takes the list of ideas generated and tests each solution for feasibility. The entrepreneur must consider the cost of each idea and the obstacles to implementation. In the preceding example, adding a chemical to the water may not be a feasible solution to the farmer. Not every farmer wants additional chloride or fluoride added to the water due to the effect on both humans and livestock. These tradeoffs should be addressed in the feasibility assessment. The farmer might prefer a filtration system, but the cost of that solution might not be practicable. The entrepreneur should identify and assess alternative solutions to find one that is most cost-effective and feasible to the customer.

Step 4: Implement

To implement is the step in which the solution to the problem is tested and evaluated. The entrepreneur walks through the planned implementation with the client and tests each part of the solution, if a service, or thoroughly tests a developed good. The entrepreneur implements the solution and goes through a structured system of follow-up to ensure the solution remains effective and viable. In the water example, the solution would be reducing runoff from toxic insecticides by adding prairie strips, buffers of grass, and vegetation along banks of streams.

Step 5: Evaluate

To evaluate is the step in which the final solution is assessed. This is a very important step that entrepreneurs often overlook. Any fallacy in the implementation of the product or service is reassessed, and new solutions are implemented. A continual testing process may be needed to find the final solution. The prairie strips, buffers of grass, and vegetation along banks of streams chosen in the farming water example should then be analyzed and tested to ensure the chosen solution changed the content of the water.

ARE YOU READY?

Implementing Creative Problem Solving

Removing waste is a problem, and it can also present an entrepreneurial opportunity. Try to examine ways in which waste products that you usually pay to have hauled away can now generate revenue. Whether it’s recycling aluminum cans or cardboard, or garbage that could be used to feed animals, your task is to come up with solutions to this entrepreneurial-oriented problem.

• Try following the first step of the creative problem-solving process and clearly identify the problem.
• Next, gather data and formulate the challenge.
• Then, explore ideas and come up with solutions.
• Develop a plan of action.
• Finally, note how you would evaluate the effectiveness of your solution.

Using Creativity to Solve Problems

Entrepreneurs are faced with solving many problems as they develop their ideas for filling gaps, whether those opportunities involve establishing a new company or starting a new enterprise within an existing company. Some of these problems include staffing, hiring and managing employees, handling legal compliance, funding, marketing, and paying taxes. Beyond the mundane activities listed, the entrepreneur, or the team that the entrepreneur puts in place, is indispensable in maintaining the ongoing creativity behind the product line or service offered. Innovation and creativity in the business are necessary to expand the product line or develop a groundbreaking service.

It is not necessary for the entrepreneur to feel isolated when it comes to finding creative solutions to a problem. There are societies, tools, and new methods available to spur the creativity of the entrepreneur that will further support the success and expansion of a new enterprise. 14 Learning and using entrepreneurial methods to solve problems alleviates the stress many startup owners feel. The entrepreneur’s creativity will increase using collaborative methodologies. Some entrepreneurial collaborative methodologies include crowdsourcing, brainstorming, storyboarding, conducting quick online surveys to test ideas and concepts, and team creativity activities.

Crowdsourcing

Professor Daren Brabham at the University of Southern California has written books on crowdsourcing and touts its potential in for-profit and not-for-profit business sectors. He defines it simply as “an online, distributed problem-solving and production model.” 15 Crowdsourcing involves teams of amateurs and nonexperts working together to form a solution to a problem. 16 The idea, as cbsnews.com’s Jennifer Alsever has put it, is to “tap into the collective intelligence of the public at large to complete business-related tasks that a company would normally either perform itself or outsource to a third-party provider. Yet free labor is only a narrow part of crowdsourcing's appeal. More importantly, it enables managers to expand the size of their talent pool while also gaining deeper insight into what customers really want. The challenge is to take a cautionary approach to the ‘wisdom of the crowd,’ which can lead to a ‘herd’ mentality.” 17

LINK TO LEARNING

Read this article that discusses what crowdsourcing is, how to use it, and its benefits for more information.

This new business prototype, similar to outsourcing, features an enterprise posting a problem online and asking for volunteers to consider the problem and propose solutions. Volunteers earn a reward, such as prize money, promotional materials like a T-shirt, royalties on creative outlets like photos or designs, and in some cases, compensation for their labor. Before proposing the solution, volunteers learn that the solutions become the intellectual property of the startup posting the problem. The solution is then mass-produced for profit by the startup that posted the problem. 18 The process evolves into the crowdsourcing process after the enterprise mass produces and profits from the labor of the volunteers and the team. Entrepreneurs should consider that untapped masses have solutions for many issues for which agendas do not yet exist. Crowdsourcing can exploit those agendas and add to the tools used to stimulate personal creativity. This type of innovation is planned and strategically implemented for profit.

For example, Bombardier held a crowdsourced innovation contest to solicit input on the future of train interiors, including seat design and coach class interior. A corporate jury judged the submissions, with the top ten receiving computers or cash prizes. Companies are often constrained, however, by internal rules limiting open source or external idea sourcing, as they could be accused of “stealing” an idea. While crowdsourcing outside of software can be problematic, some products such as MakerBot’s 3D printers, 3DR’s drones, and Jibo’s Social Robot have used developer kits and “makers” to help build a community and stimulate innovation from the outside.

WORK IT OUT

A Crowdsourced Potato Chip

In an effort to increase sales among millennials, PepsiCo turned to crowdsourcing to get new flavor ideas for their Lay’s potato chips (called Walker’s in the UK). Their 2012 campaign, “Do Us a Flavor,” was so successful that they received over 14 million submissions. The winner was Cheesy Garlic Bread, which increased their potato chip sales by 8 percent during the first three months after the launch.

• What are some other products that would work well for a crowdsourced campaign contest?
• What items wouldn’t work well?

Amazon’s Mechanical Turk is an online crowdsourcing platform that allows individuals to post tasks for workers to complete. In many instances, these tasks are compensated, but the payment can be less than one dollar per item completed. Mechanical Turk is one of the largest and most well-known crowdsourcing platforms, but there are a number of other more niche ones as well that would apply to smaller markets. In the case of innovation contests and outsourced tasks from corporations, those tasks may be hosted internally by the corporation.

Brainstorming

Brainstorming is the generation of ideas in an environment free of judgment or dissension with the goal of creating solutions. Brainstorming is meant to stimulate participants into thinking about problem-solving in a new way. Using a multifunctional group, meaning participants come from different departments and with different skill sets, gives entrepreneurs and support teams a genuine chance to suggest and actualize ideas. The group works together to refine and prototype potential solutions to a problem.

Brainstorming is a highly researched and often practiced technique for the development of innovative solutions. One of the more successful proponents of brainstorming is the United Nations Children’s Fund (UNICEF). UNICEF faces unique problems of solving resource problems for mothers and children in underdeveloped nations. See how UNICEF practices brainstorming to solve problems including child survival, gender inclusion, refugee crises, education, and others.

The setting for a brainstorming session should remain as informal and relaxed as possible. The group needs to avoid standard solutions. All ideas are welcome and listed and considered with no censorship and with no regard to administrative restrictions. All team members have an equal voice. The focus of brainstorming is on quantity of ideas rather than on the ideal solution provided in every suggestion. A classic entrepreneurial brainstorming activity, as popularized by business software developer Strategyzer, is known as the “silly cow” exercise. Teams come up with ideas for new business models pertaining to a cow, with the results often outrageous, ranging from sponsored cows to stroking cows for therapeutic release. Participants are asked to identify some aspect of a cow and develop three business models around that concept in a short time period, typically two minutes or fewer. The activity is designed to get creative juices flowing.

Watch this video from ABC’s Nightline that shows how IDEO designed a new shopping cart for an example of a design process that involves brainstorming.

Storyboarding

Storyboarding is the process of presenting an idea in a step-by-step graphic format, as Figure 3.3.4 shows. This tool is useful when the entrepreneur is attempting to visualize a solution to a problem. The steps to the solution of a problem are sketched and hung in graphic format. Once the original graphic is placed, images of steps working toward a solution are added, subtracted, and rearranged on a continual basis, until the ultimate solution emerges in the ultimate graphic format. For many years, entrepreneurs have used this process to create a pre-visual for various media sequences.

Team Creativity

Team creativity is the process whereby an entrepreneur works with a team to create an unexpected solution for an issue or challenge. Teams progress through the same creative problem-solving process described already: clarify, ideate, develop, implement, and evaluate. The main advantage of team creativity is the collaboration and support members receive from one another. Great teams trust in other team members, have diverse members with diverse points of view, are cohesive, and have chemistry.

Team members should work in a stress-free and relaxing environment. Reinforcement and expansion of ideas in the team environment motivates the team to continually expand horizons toward problem solution. A small idea in a team may spark the imagination of a team member to an original idea. Mark Zuckerberg, co-founder of Facebook, once said, “The most important thing for you as an entrepreneur trying to build something is, you need to build a really good team. And that’s what I spend all my time on.” 19

ENTREPRENEUR IN ACTION

Taaluma Totes 20

Young entrepreneurs Jack DuFour and Alley Heffern began to notice the beautiful fabrics that came from the different countries they visited. The entrepreneurs thought about what could be done with the fabrics to create employment opportunities both in the country from which the fabric originated and in their home base of Virginia. They decided to test producing totes from the fabrics they found and formed Taaluma Totes (Figure 3.3.5). DuFour and Heffern also wanted to promote the production of these fabrics and help underserved populations in countries where the fabric originated maintain a living or follow a dream.

The team continued to test the process and gathered original fabrics, which they sent to Virginia to create totes. They trained individuals with disabilities in Virginia to manufacture the totes, thus serving populations in the United States. The entrepreneurs then decided to take 20 percent of their profits and make microloans to farmers and small business owners in the countries where the fabric originated to create jobs there. Microloans are small loans, below $50,000, which certain lenders offer to enterprising startups. These startups, for various reasons (they are in poor nations, at the poverty level), can’t afford a traditional loan from a major bank. The lenders offer business support to the borrower, which in turn helps the borrower repay the microloan. The microloans from Taaluma are repaid when the borrower is able. Repayments are used to buy more fabric, completing Taaluma’s desire to serve dual populations. If the process proved unsuccessful, the co-owners would revise the process to meet the plan’s requirements.

DuFour and Heffern now have fabrics from dozens of countries from Thailand to Ecuador. The totes are specialized with features to meet individual needs. The product line is innovated regularly and Taaluma Totes serves a dual purpose of employing persons with disabilities in Virginia and creating employment for underserved populations in other countries.

• 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.

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…

Master the 7-Step Problem-Solving Process for Better Decision-Making

Discover the powerful 7-Step Problem-Solving Process to make better decisions and achieve better outcomes. Master the art of problem-solving in this comprehensive guide. Download the Free PowerPoint and PDF Template.

StrategyPunk

Introduction

Mastering the art of problem-solving is crucial for making better decisions. Whether you're a student, a business owner, or an employee, problem-solving skills can help you tackle complex issues and find practical solutions. The 7-Step Problem-Solving Process is a proven method that can help you approach problems systematically and efficiently.

The 7-Step Problem-Solving Process involves steps that guide you through the problem-solving process. The first step is to define the problem, followed by disaggregating the problem into smaller, more manageable parts. Next, you prioritize the features and create a work plan to address each. Then, you analyze each piece, synthesize the information, and communicate your findings to others.

By following this process, you can avoid jumping to conclusions, overlooking important details, or making hasty decisions. Instead, you can approach problems with a clear and structured mindset, which can help you make better decisions and achieve better outcomes.

In this article, we'll explore each step of the 7-Step Problem-Solving Process in detail so you can start mastering this valuable skill. You can download the process's free PowerPoint and PDF templates at the end of the blog post .

Step 1: Define the Problem

The first step in the problem-solving process is to define the problem. This step is crucial because finding a solution is only accessible if the problem is clearly defined. The problem must be specific, measurable, and achievable.

One way to define the problem is to ask the right questions. Questions like "What is the problem?" and "What are the causes of the problem?" can help. Gathering data and information about the issue to assist in the definition process is also essential.

Another critical aspect of defining the problem is identifying the stakeholders. Who is affected by it? Who has a stake in finding a solution? Identifying the stakeholders can help ensure that the problem is defined in a way that considers the needs and concerns of all those affected by it.

Once the problem is defined, it is essential to communicate the definition to all stakeholders. This helps to ensure that everyone is on the same page and that there is a shared understanding of the problem.

Step 2: Disaggregate

After defining the problem, the next step in the 7-step problem-solving process is to disaggregate the problem into smaller, more manageable parts. Disaggregation helps break down the problem into smaller pieces that can be analyzed individually. This step is crucial in understanding the root cause of the problem and identifying the most effective solutions.

Disaggregation can be achieved by breaking down the problem into sub-problems, identifying the contributing factors, and analyzing the relationships between these factors. This step helps identify the most critical factors that must be addressed to solve the problem.

A tree or fishbone diagram is one effective way to disaggregate a problem. These diagrams help identify the different factors contributing to the problem and how they are related. Another way is to use a table to list the other factors contributing to the situation and their corresponding impact on the issue.

Disaggregation helps in breaking down complex problems into smaller, more manageable parts. It helps understand the relationships between different factors contributing to the problem and identify the most critical factors that must be addressed. By disaggregating the problem, decision-makers can focus on the most vital areas, leading to more effective solutions.

Step 3: Prioritize

After defining the problem and disaggregating it into smaller parts, the next step in the 7-step problem-solving process is prioritizing the issues that need addressing. Prioritizing helps to focus on the most pressing issues and allocate resources more effectively.

There are several ways to prioritize issues, including:

• Urgency: Prioritize issues based on their urgency. Problems that require immediate attention should be addressed first.
• Impact: Prioritize issues based on their impact on the organization or stakeholders. Problems with a high impact should be given priority.
• Resources: Prioritize issues based on the resources required to address them. Problems that require fewer resources should be dealt with first.

Considering their concerns and needs, it is important to involve stakeholders in the prioritization process. This can be done through surveys, focus groups, or other forms of engagement.

Once the issues have been prioritized, developing a plan of action to address them is essential. This involves identifying the resources required, setting timelines, and assigning responsibilities.

Prioritizing issues is a critical step in problem-solving. By focusing on the most pressing problems, organizations can allocate resources more effectively and make better decisions.

Step 4: Workplan

After defining the problem, disaggregating, and prioritizing the issues, the next step in the 7-step problem-solving process is to develop a work plan. This step involves creating a roadmap that outlines the steps needed to solve the problem.

The work plan should include a list of tasks, deadlines, and responsibilities for each team member involved in the problem-solving process. Assigning tasks based on each team member's strengths and expertise ensures the work is completed efficiently and effectively.

Creating a work plan can help keep the team on track and ensure everyone is working towards the same goal. It can also help to identify potential roadblocks or challenges that may arise during the problem-solving process and develop contingency plans to address them.

Several tools and techniques can be used to develop a work plan, including Gantt charts, flowcharts, and mind maps. These tools can help to visualize the steps needed to solve the problem and identify dependencies between tasks.

Developing a work plan is a critical step in the problem-solving process. It provides a clear roadmap for solving the problem and ensures everyone involved is aligned and working towards the same goal.

Step 5: Analysis

Once the problem has been defined and disaggregated, the next step is to analyze the information gathered. This step involves examining the data, identifying patterns, and determining the root cause of the problem.

Several methods can be used during the analysis phase, including:

• Root cause analysis
• Pareto analysis
• SWOT analysis

Root cause analysis is a popular method used to identify the underlying cause of a problem. This method involves asking a series of "why" questions to get to the root cause of the issue.

Pareto analysis is another method that can be used during the analysis phase. This method involves identifying the 20% of causes responsible for 80% of the problems. By focusing on these critical causes, organizations can make significant improvements.

Finally, SWOT analysis is a valuable tool for analyzing the internal and external factors that may impact the problem. This method involves identifying the strengths, weaknesses, opportunities, and threats related to the issue.

Overall, the analysis phase is critical for identifying the root cause of the problem and developing practical solutions. Organizations can gain a deeper understanding of the issue and make informed decisions by using a combination of methods.

Step 6: Synthesize

Once the analysis phase is complete, it is time to synthesize the information gathered to arrive at a solution. During this step, the focus is on identifying the most viable solution that addresses the problem. This involves examining and combining the analysis results for a clear and concise conclusion.

One way to synthesize the information is to use a decision matrix. This involves creating a table that lists the potential solutions and the essential criteria for making a decision. Each answer is then rated against each standard, and the scores are tallied to arrive at a final decision.

Another approach to synthesizing the information is to use a mind map. This involves creating a visual representation of the problem and the potential solutions. The mind map can identify the relationships between the different pieces of information and help prioritize the solutions.

During the synthesis phase, remaining open-minded and considering all potential solutions is vital. To ensure everyone's perspectives are considered, it is also essential to involve all stakeholders in the decision-making process.

Step 7: Communicate

After synthesizing the information, the next step is communicating the findings to the relevant stakeholders. This is a crucial step because it helps to ensure that everyone is on the same page and that the decision-making process is transparent.

One effective way to communicate the findings is through a well-organized report. The report should include the problem statement, the analysis, the synthesis, and the recommended solution. It should be clear, concise, and easy to understand.

In addition to the report, a presentation explaining the findings is essential. The presentation should be tailored to the audience and highlight the report's key points. Visual aids such as tables, graphs, and charts can make the presentation more engaging.

During the presentation, it is essential to be open to feedback and questions from the audience. This helps ensure everyone agrees with the recommended solution and addresses concerns or objections.

Effective communication is vital to ensuring the decision-making process is successful. Stakeholders can make informed decisions and work towards a common goal by communicating the findings clearly and concisely.

The 7-step problem-solving process is a powerful tool for helping individuals and organizations make better decisions. By following these steps, individuals can identify the root cause of a problem, prioritize potential solutions, and develop a clear plan of action. This process can be applied to various scenarios, from personal challenges to complex business problems.

Through disaggregation, individuals can break down complex problems into smaller, more manageable parts. By prioritizing potential solutions, individuals can focus their efforts on the most impactful actions. The work step allows individuals to develop a clear action plan, while the analysis step provides a framework for evaluating possible solutions.

The synthesis step combines all the information gathered to develop a comprehensive solution. Finally, the communication step allows individuals to share their answers with others and gather feedback.

By mastering the 7-step problem-solving process, individuals can become more effective decision-makers and problem-solvers. This process can help individuals and organizations save time and resources while improving outcomes. With practice, individuals can develop the skills to apply this process to a wide range of scenarios and make better decisions in all areas of life.

7-Step Problem-Solving Process PPT Template

Free powerpoint and pdf template, executive summary: the 7-step problem-solving process.

The 7-Step Problem-Solving Process is a robust and systematic method to help individuals and organizations make better decisions by tackling complex issues and finding practical solutions. This process comprises defining the problem, disaggregating it into smaller parts, prioritizing the issues, creating a work plan, analyzing the data, synthesizing the information, and communicating the findings.

By following these steps, individuals can identify the root cause of a problem, break it down into manageable components, and prioritize the most impactful actions. The work plan, analysis, and synthesis steps provide a framework for developing comprehensive solutions, while the communication step ensures transparency and stakeholder engagement.

Mastering this process can improve decision-making and problem-solving capabilities, save time and resources, and improve outcomes in personal and professional contexts.

Please buy me a coffee.

I'd appreciate your support if my templates have saved you time or helped you start a project. Buy Me a Coffee is a simple way to show your appreciation and help me continue creating high-quality templates that meet your needs.

7-Step Problem-Solving Process PDF Template

7-step problem-solving process powerpoint template.

Xpeng SWOT Analysis: Free PPT Template and In-Depth Insights (free file)

Unlock key insights into Xpeng with our free SWOT analysis PPT template. Dive deep into its business dynamics at no cost.

Strategic Insights 2024: A SWOT Analysis of Nestle (Plus Free PPT)

Explore Nestle's strategic outlook with our SWOT analysis for 2024. This PowerPoint template highlights key areas for growth and challenges.

2024 Business Disruption: Navigating Growth Through Shaping Strategy

Discover the importance of being a shaper in 2023's business ecosystem. Shaping strategy, attracting a critical mass of participants, and finding the right strategic path to create value.

Samsung PESTLE Analysis: Unveiling the Driving Forces (Free PPT)

Download our comprehensive guide: Samsung PESTLE Analysis (Free PPT). Discover the strategic insights & driving forces shaping Samsung's future.

• Miles Anthony Smith
• Sep 12, 2022
• 12 min read

The Ultimate Problem-Solving Process Guide: 31 Steps and Resources

Updated: Jan 24, 2023

GOT CHALLENGES WITH YOUR PROBLEM-SOLVING PROCESS? ARE YOU FRUSTRATED?

prob·lem-solv·ing noun -the process of finding solutions to difficult or complex issues. It sounds so simple, doesn’t it? But in reality problem-solving is hard. It's almost always more complex than it seems. That's why problem-solving can be so frustrating sometimes. You can feel like you’re spinning your wheels, arguing in circles, or just failing to find answers that actually work. And when you've got a group working on a problem, it can get even muddier …differences of opinions, viewpoints colored by different backgrounds, history, life experiences, you name it. We’re all looking at life and work from different angles, and that often means disagreement. Sometimes sharp disagreement. That human element, figuring out how to take ourselves out of the equation and make solid, fact-based decisions , is precisely why there’s been so much written on problem-solving. Which creates its own set of problems. Whose method is best? How can you possibly sift through them all? Are we to have one person complete the entire problem-solving process by themselves or rely on a larger team to find answers to our most vexing challenges in the workplace ? Today, we’re going to make sense of it all. We’ll take a close look at nine top problem-solving methods. Then we’ll grab the best elements of all of them to give you a process that will have your team solving problems faster, with better results , and maybe with less sharp disagreement. Ready to dive in? Let’s go!

9 PROFITABLE PROBLEM-SOLVING TECHNIQUES AND METHODS

While there are loads of methods to choose from, we are going to focus on nine of the more common ones. You can use some of these problem-solving techniques reactively to solve a known issue or proactively to find more efficient or effective ways of performing tasks. If you want to explore other methods, check out this resource here . A helpful bit of advice here is to reassure people that you aren’t here to identify the person that caused the problem . You’re working to surface the issue, solve it and make sure it doesn’t happen again, regardless of the person working on the process. It can’t be understated how important it is to continually reassure people of this so that you get unfiltered access to information. Without this, people will often hide things to protect themselves . After all, nobody wants to look bad, do they? With that said, let’s get started...

1. CREATIVE PROBLEM SOLVING (CPS)

Alex Osborn coined the term “Creative Problem Solving” in the 1940s with this simple four-step process:

Clarify : Explore the vision, gather data, and formulate questions.

Ideate : This stage should use brainstorming to generate divergent thinking and ideas rather than the random ideas normally associated with brainstorming.

Develop : Formulate solutions as part of an overall plan.

Implement : Put the plan into practice and communicate it to all parties.

2. APPRECIATIVE INQUIRY

Source: http://www.davidcooperrider.com/ai-process/ This method seeks, first and foremost, to identify the strengths in people and organizations and play to that “positive core” rather than focus our energies on improving weaknesses . It starts with an “affirmative topic,” followed by the “positive core (strengths).” Then this method delves into the following stages:

Discovery (fact-finding)

Dream (visioning the future)

Design (strategic purpose)

Destiny (continuous improvement)

3. “FIVE WHYS” METHOD

This method simply suggests that we ask “Why” at least five times during our review of the problem and in search of a fix. This helps us dig deeper to find the the true reason for the problem, or the root cause. Now, this doesn’t mean we just keeping asking the same question five times. Once we get an answer to our first “why”, we ask why to that answer until we get to five “whys”.

Using the “five whys” is part of the “Analyze” phase of Six Sigma but can be used with or without the full Six Sigma process.

Review this simple Wikipedia example of the 5 Whys in action:

The vehicle will not start. (the problem)

Why? - The battery is dead. (First why)

Why? - The alternator is not functioning. (Second why)

Why? - The alternator belt has broken. (Third why)

Why? - The alternator belt was well beyond its useful service life and not replaced. (Fourth why)

Why? - The vehicle was not maintained according to the recommended service schedule. (Fifth why, a root cause)

4. LEAN SIX SIGMA (DMAIC METHOD)

While many people have at least heard of Lean or Six Sigma, do we know what it is? Like many problem-solving processes, it has five main steps to follow.

Define : Clearly laying out the problem and soliciting feedback from those who are customers of the process is necessary to starting off on the right foot.

Measure : Quantifying the current state of the problem is a key to measuring how well the fix performed once it was implemented.

Analyze : Finding out the root cause of the problem (see number 5 “Root Cause Analysis” below) is one of the hardest and least explored steps of Six Sigma.

Improve : Crafting, executing, and testing the solution for measureable improvement is key. What doesn’t get implemented and measured really won’t make a difference.

Control : Sustaining the fix through a monitoring plan will ensure things continue to stay on track rather than being a short-lived solution.

5. ROOT CAUSE ANALYSIS

Compared to other methods, you’ll more often find this technique in a reactive problem-solving mode, but it is helpful nonetheless. Put simply, it requires a persistent approach to finding the highest-level cause, since most reasons you’ll uncover for a problem don’t tell the whole story.

Most of the time, there are many factors that contributed to an issue. The main reason is often shrouded in either intentional or unintentional secrecy. Taking the time to drill down to the root of the issue is key to truly solving the problem.

6. DEMING-SHEWHART CYCLE: PLAN-DO-CHECK-ACT (PDCA)

Named for W. Edwards Deming and Walter A. Shewhart, this model follows a four-step process:

Plan: Establish goals and objectives at the outset to gain agreement. It’s best to start on a small scale in order to test results and get a quick win.

Do: This step is all about the implementation and execution of the solution.

Check: Study and compare actual to expected results. Chart this data to identify trends.

Act/Adjust: If the check phase showed different results, then adjust accordingly. If worse than expected, then try another fix. If the same or better than expected, then use that as the new baseline for future improvements.

7. 8D PROBLEM-SOLVING

While this is named “8D” for eight disciplines, there are actually nine , because the first is listed as step zero. Each of the disciplines represents a phase of this process. Its aim is to implement a quick fix in the short term while working on a more permanent solution with no recurring issues.

Prepare and Plan : Collecting initial information from the team and preparing your approach to the process is a necessary first step.

Form a Team : Select a cross-functional team of people, one leader to run meetings and the process, and one champion/sponsor who will be the final decision-maker.

Describe the Problem : Using inductive and deductive reasoning approaches, lay out the precise issue to be corrected.

Interim Containment Action : Determine if an interim solution needs to be implemented or if it can wait until the final fix is firmed up. If necessary, the interim action is usually removed once the permanent solution is ready for implementation.

Root Cause Analysis and Escape Point : Finding the root of the issue and where in the process it could’ve been found but was not will help identify where and why the issue happened.

Permanent Corrective Action : Incorporating key criteria into the solution, including requirements and wants, will help ensure buy-in from the team and your champion.

Implement and Validate the Permanent Corrective Action : Measuring results from the fix implemented validates it or sends the team back to the drawing board to identity a more robust solution.

Prevent Recurrence : Updating work procedure documents and regular communication about the changes are important to keep old habits in check.

Closure and Team Celebration : Taking time to praise the team for their efforts in resolving the problem acknowledges the part each person played and offers a way to move forward.

8. ARMY PROBLEM SOLVING PROCESS

The US Army has been solving problems for more than a couple of centuries , so why not take a look at the problem-solving process they’ve refined over many years? They recommend this five step process:

Identify the Problem : Take time to understand the situation and define a scope and limitations before moving forward.

Gather Information : Uncover facts, assumptions, and opinions about the problem, and challenge them to get to the truth.

Develop Screening and Evaluation Criteria :

Five screening items should be questioned. Is it feasible, acceptable, distinguishable, and complete?

Evaluation criteria should have these 5 elements: short title, definition, unit of measure, benchmark, and formula.

Generate, Analyze, and Compare Possible Solutions : Most fixes are analyzed, but do you compare yours to one another as a final vetting method?

Choose a Solution and Implement : Put the fix into practice and follow up to ensure it is being followed consistently and having the desired effect.

9. HURSON'S PRODUCTIVE THINKING MODEL

Tim Hurson introduced this model in 2007 with his book, Think Better. It consists of the following six actions.

Ask "What is going on?" : Define the impact of the problem and the aim of its solution.

Ask "What is success?" : Spell out the expected outcome, what should not be in fix, values to be considered, and how things will be evaluated.

Ask "What is the question?" : Tailor questions to the problem type. Valuable resources can be wasted asking questions that aren’t truly relevant to the issue.

Generate answers : Prioritize answers that are the most relevant to solutions, without excluding any suggestion to present to the decision-makers.

Forge the solution : Refine the raw list of prioritized fixes, looking for ways to combine them for a more powerful solution or eliminate fixes that don’t fit the evaluation criteria.

Align resources: Identify resources, team, and stakeholders needed to implement and maintain the solution.

STEAL THIS THOROUGH 8-STEP PROBLEM-SOLVING PROCESS

Now that we’ve reviewed a number of problem-solving methods, we’ve compiled the various steps into a straightforward, yet in-depth, s tep-by-step process to use the best of all methods.

1. DIG DEEP: IDENTIFY, DEFINE, AND CLARIFY THE ISSUE

“Elementary, my dear Watson,” you might say.

This is true, but we often forget the fundamentals before trying to solve a problem. So take some time to gain understanding of critical stakeholder’s viewpoints to clarify the problem and cement consensus behind what the issue really is.

Sometimes it feels like you’re on the same page, but minor misunderstandings mean you’re not really in full agreement.. It’s better to take the time to drill down on an issue before you get too far into solving a problem that may not be the exact problem . Which leads us to…

2. DIG DEEPER: ROOT CAUSE ANALYSIS

This part of the process involves identifying these three items :

What happened?

Why did it happen?

What process do we need to employ to significantly reduce the chances of it happening again ?

You’ll usually need to sort through a series of situations to find the primary cause. So be careful not to stop at the first cause you uncover . Dig further into the situation to expose the root of the issue. We don’t want to install a solution that only fixes a surface-level issue and not the root. T here are typically three types of causes :

Physical: Perhaps a part failed due to poor design or manufacturing.

Human error: A person either did something wrong or didn’t do what needed to be done.

Organizational: This one is mostly about a system, process, or policy that contributed to the error .

When searching for the root cause, it is important to ensure people that you aren’t there to assign blame to a person but rather identify the problem so a fix can prevent future issues.

3. PRODUCE A VARIETY OF SOLUTION OPTIONS

So far, you’ve approached the problem as a data scientist, searching for clues to the real issue. Now, it’s important to keep your eyes and ears open, in case you run across a fix suggested by one of those involved in the process failure. Because they are closest to the problem, they will often have an idea of how to fix things. In other cases, they may be too close, and unable to see how the process could change.

The bottom line is to solicit solution ideas from a variety of sources , both close to and far away from the process you’re trying to improve.

You just never know where the top fix might come from!

4. FULLY EVALUATE AND SELECT PLANNED FIX(ES)

Evaluating solutions to a defined problem can be tricky since each one will have cost, political, or other factors associated with it. Running each fix through a filter of cost and impact is a vital step toward identifying a solid solution and hopefully settling on the one with the highest impact and low or acceptable cost.

Categorizing each solution in one of these four categoriescan help teams sift through them:

High Cost/Low Impact: Implement these last, if at all, since t hey are expensive and won’t move the needle much .

Low Cost/Low Impact: These are cheap, but you won’t get much impact.

High Cost/High Impact: These can be used but should be second to the next category.

Low Cost/High Impact: Getting a solid “bang for your buck” is what these fixes are all about. Start with these first .

5. DOCUMENT THE FINAL SOLUTION AND WHAT SUCCESS LOOKS LIKE

Formalize a document that all interested parties (front-line staff, supervisors, leadership, etc.) agree to follow. This will go a long way towards making sure everyone fully understands what the new process looks like, as well as what success will look like .

While it might seem tedious, try to be overly descriptive in the explanation of the solution and how success will be achieved. This is usually necessary to gain full buy-in and commitment to continually following the solution. We often assume certain things that others may not know unless we are more explicit with our communications.

6. SUCCESSFULLY SELL AND EXECUTE THE FIX

Arriving at this stage in the process only to forget to consistently apply the solution would be a waste of time, yet many organizations fall down in the execution phase . Part of making sure that doesn’t happen is to communicate the fix and ask for questions multiple times until all parties have a solid grasp on what is now required of them.

One often-overlooked element of this is the politics involved in gaining approval for your solution. Knowing and anticipating objections of those in senior or key leadership positions is central to gaining buy-in before fix implementation.

7. RINSE AND REPEAT: EVALUATE, MONITOR, AND FOLLOW UP

Next, doing check-ins with the new process will ensure that the solution is working (or identity if further reforms are necessary) . You’ll also see if the measure of predefined success has been attained (or is making progress in that regard).

Without regularly monitoring the fix, you can only gauge the success or failure of the solution by speculation and hearsay. And without hard data to review, most people will tell their own version of the story.

8. COLLABORATIVE CONTINGENCIES, ITERATION, AND COURSE CORRECTION

Going into any problem-solving process, we should take note that we will not be done once the solution is implemented (or even if it seems to be working better at the moment). Any part of any process will always be subject to the need for future iterations and course corrections . To think otherwise would be either foolish or naive.

There might need to be slight, moderate, or wholesale changes to the solution previously implemented as new information is gained, new technologies are discovered, etc.

14 FRUITFUL RESOURCES AND EXERCISES FOR YOUR PROBLEM-SOLVING JOURNEY

Want to test your problem-solving skills?

Take a look at these twenty case study scenario exercises to see how well you can come up with solutions to these problems.

Still have a desire to discover more about solving problems?

Check out these 14 articles and books...

1. THE LEAN SIX SIGMA POCKET TOOLBOOK: A QUICK REFERENCE GUIDE TO NEARLY 100 TOOLS FOR IMPROVING QUALITY AND SPEED

This book is like a Bible for Lean Six Sigma , all in a pocket-sized package.

2. SOME SAGE PROBLEM SOLVING ADVICE

The American Society for Quality has a short article on how it’s important to focus on the problem before searching for a solution.

3. THE SECRET TO BETTER PROBLEM SOLVING: HARVARD BUSINESS REVIEW

Wondering if you are solving the right problems? Check out this Harvard Business Review article.

4. PROBLEM SOLVING 101 : A SIMPLE BOOK FOR SMART PEOPLE

Looking for a fun and easy problem-solving book that was written by a McKinsey consultant? Take a look!

5. THE BASICS OF CREATIVE PROBLEM SOLVING – CPS

If you want a deeper dive into the seven steps of Creative Problem Solving , see this article.

6. APPRECIATIVE INQUIRY : A POSITIVE REVOLUTION IN CHANGE

Appreciative Inquiry has been proven effective in organizations ranging from Roadway Express and British Airways to the United Nations and the United States Navy. Review this book to join the positive revolution.

7. PROBLEM SOLVING: NINE CASE STUDIES AND LESSONS LEARNED

The Seattle Police Department has put together nine case studies that you can practice solving . While they are about police work, they have practical application in the sleuthing of work-related problems.

8. ROOT CAUSE ANALYSIS : THE CORE OF PROBLEM SOLVING AND CORRECTIVE ACTION

Need a resource to delve further into Root Cause Analysis? Look no further than this book for answers to your most vexing questions .

9. SOLVING BUSINESS PROBLEMS : THE CASE OF POOR FRANK

This solid case study illustrates the complexities of solving problems in business.

10. THE 8-DISCIPLINES PROBLEM SOLVING METHODOLOGY

Learn all about the “8Ds” with this concise primer.

11. THE PROBLEM-SOLVING PROCESS THAT PREVENTS GROUPTHINK HBR

Need to reduce groupthink in your organization’s problem-solving process ? Check out this article from the Harvard Business Review.

12. THINK BETTER : AN INNOVATOR'S GUIDE TO PRODUCTIVE THINKING

Tim Hurson details his own Productive Thinking Model at great length in this book from the author.

13. 5 STEPS TO SOLVING THE PROBLEMS WITH YOUR PROBLEM SOLVING INC MAGAZINE

This simple five-step process will help you break down the problem, analyze it, prioritize solutions, and sell them internally.

14. CRITICAL THINKING : A BEGINNER'S GUIDE TO CRITICAL THINKING, BETTER DECISION MAKING, AND PROBLEM SOLVING!

LOOKING FOR ASSISTANCE WITH YOUR PROBLEM-SOLVING PROCESS?

There's a lot to take in here, but following some of these methods are sure to improve your problem-solving process. However, if you really want to take problem-solving to the next level, InitiativeOne can come alongside your team to help you solve problems much faster than you ever have before.

There are several parts to this leadership transformation process provided by InitiativeOne, including a personal profile assessment, cognitive learning, group sessions with real-world challenges, personal discovery, and a toolkit to empower leaders to perform at their best.

There are really only two things stopping good teams from being great. One is how they make decisions and two is how they solve problems. Contact us today to grow your team’s leadership performance by making decisions and solving problems more swiftly than ever before!

• Featured Post

Recent Posts

Does Your Leadership Deserve Two Thumbs Up?

3 Ways to Harness the Power of Inspiration

Leadership Self-Check

3 Steps to Successfully Solve Any Problem

At its core, problem-solving is simply the process of identifying and addressing a challenge or obstacle that stands in the way of achieving a goal. While many different strategies and techniques can be used to solve problems effectively, three key steps are essential for any successful problem-solving process: gathering information, developing possible solutions, and evaluating potential solutions.

Whether you are facing a workplace challenge, tackling a personal problem, or working to overcome a difficult obstacle, the key to success is assessing the situation thoroughly, gathering all of the necessary information, and carefully evaluate your options.

This may involve brainstorming potential solutions with colleagues or seeking input from experts, as well as carefully considering the possible outcomes of each option. Ultimately, the key is to be persistent and remain focused on finding a solution that works for you. With the right mindset and approach, any problem can be successfully solved.

Are you tired of wasting time on problems that you can't solve? This guide will systematically show you how to solve any problem in just three steps.

Whether you are facing a work challenge, tackling a personal problem, or struggling to overcome an obstacle, the key to success has the right mindset and approach to problem-solving. At its core, problem-solving involves:

Identifying the challenge or obstacle that stands in your way.

Gathering information to understand the situation entirely.

Considering all of your possible solutions before deciding on the best course of action.

To solve a problem, you need to be able to gather enough and the right kind of information.

To successfully solve a problem, you must have accurate information about that problem. This involves being able to gather the right kind of data, as well as having the knowledge and skills needed to interpret it effectively. One essential part of problem-solving is analyzing the problem, which requires you to break it down into smaller components to understand its root causes better.

Once you have gathered enough data and understand the problem, you can begin considering possible solutions and selecting the best ones based on your available resources. Ultimately, analyzing a problem and gathering relevant information is crucial for achieving effective problem-solving results.

Developing possible solutions is an essential step in the problem-solving process steps.

Once you clearly understand the problem, your next step is to start thinking creatively about possible solutions. This may involve brainstorming ideas with colleagues or seeking input from experts, as well as considering potential outcomes for each option and weighing the pros and cons of each solution before making a final decision.

In many cases, trying out different solutions to see what works best can also be helpful. Then, with persistence, focus, and creativity, you can develop practical solutions that will allow you to overcome any challenge or obstacle that stands in your way.

Evaluating potential solutions is key to ensuring that you choose the right approach to solve your problem.

Before making a final decision about the best course of action, it is essential to evaluate your potential solutions and consider the possible outcomes carefully. This may involve conducting research, consulting with subject matter experts, or running tests to determine which solution will most effectively address your challenge or obstacle. It is also essential to consider any risks associated with each option and how feasible it will be to implement the chosen solution based on your available resources.

With a clear understanding of the problem, the right mindset and approach for problem-solving, and a willingness to explore different options, you can successfully overcome any challenge or obstacle that stands in your way. In addition, adopting these essential problem-solving skills will enable you to achieve your goals and live a more fulfilling and successful life at work or in your personal life.

Don't let problems hold you back any longer. With this simple three-step process, you will be able to quickly and effectively solve any problem that comes your way. The first step is gathering enough information about the issue at hand. Once you have a good understanding of what the problem is, you can begin developing possible solutions.

After narrowing down your options, it's essential to evaluate each potential solution to ensure that you choose the best option for solving your problem. Join our course on problem-solving today and learn how to overcome any obstacle life throws your way.

What's your favorite problem-solving technique?

My favorite problem-solving technique is breaking down the problem into smaller parts and then attacking each piece individually. This involves understanding the problem, devising a plan of action, implementing the program, and checking to ensure the solution solves the problem.

This technique works well because it helps you focus on one task at a time and prevents you from getting overwhelmed by the size or complexity of the problem. It also allows you to test different solutions and see which works best. And finally, it helps you ensure that your solution solves the problem.

Do you prefer to work on problems alone or with others?

I prefer to work on problems with others. I think it's essential to have different perspectives when solving problems. Everyone has strengths and weaknesses, so it's helpful to have as many different viewpoints as possible when trying to solve a problem. Plus, working with others can be a lot of fun!

Have you ever had a problem that you couldn't solve? If so, how did you go about finding a solution?

I have had a problem that I couldn't solve. If so, how did you go about it?

First, I would try to narrow the problem as much as possible. Then, I would research the problem and try to find any potential solutions. After that, I would test those potential solutions to see if they worked.

If none of the possible solutions worked, I would start from scratch and develop a new plan of action. Finally, I would execute that plan of action and hope for the best.

Is there a problem-solving method that you're particularly interested in but haven't had the opportunity to try yet?

I'm interested in the problem-solving process itself. The problem-solving process entails breaking a problem into smaller and smaller manageable parts. Then, once the smaller pieces are understood, the solution to the original problem can be found.

This approach is often called "Divide and Conquer." And it's a very effective way of solving problems. The key is to break the problem into manageable chunks and take one step at a time.

Of course, if you try to solve the entire problem simultaneously, you will likely become overwhelmed and frustrated. But taking it one step at a time can slowly but surely work toward a solution.

Do you think there's always a solution to every problem, or are some problems unsolvable?

There is never a simple solution to every problem. Many problems don't have a definitive answer. What is important is how we approach problem-solving.

The first step in any problem-solving process is to identify the problem. This cannot be easy because sometimes we are so close to a situation that we can't see it objectively. However, once the issue is identified, we can look for potential solutions.

Not all solutions are viable, and some may even worsen; therefore, it is a problem. It's essential to evaluate all potential solutions and choose the best one. Sometimes this means trying multiple solutions until one works.

Are there any tricks or tactics to help you solve problems more efficiently?

There's no one-size-fits-all answer to this question, as the best way to solve problems will vary depending on the situation. However, a general process that can be useful for solving many types of issues is illustrated in the diagram below.

The first step is to identify and understand the problem. This may involve identifying the problem's root cause and understanding all the relevant facts and figures. Once you have a good understanding of the problem, you can then begin brainstorming possible solutions. After you have a few potential solutions, evaluating them carefully and selecting the best one is essential. 

What are the three main steps of problem-solving?

Solving Problems Step-by-Step The initial phase in problem-solving involves Identifying and Understanding the Problem. This crucial starting point requires to clearly defining the issue. This step necessitates a thorough analysis of what the actual problem is, its contextual elements, and its potential implications. Following the identification is the Developing Possible Solutions stage. You need to brainstorm various strategies to handle the identified problem in this second step. The emphasis here is on generating a wide array of potential solutions. These strategies must be carefully assessed and selected in order to come up with the most effective solution. After you have identified potential solutions, the final step is Implementing the Chosen Solution. This phase requires action. A decision needs to be made on which solution or combination of solutions will be executed. After that, you must follow through by initiating efforts that will lead to the resolution of the problem. In conclusion, the three main steps of problem-solving include Identifying and Understanding the Problem, Developing Possible Solutions, and Implementing the Chosen Solution. These steps equip individuals with the necessary methodologies to navigate through any issue in a systematic and logical manner.

How does future problem-solving differ from traditional problem-solving approaches?

Proactive Approach of Future Problem-Solving Traditional problem-solving methods mainly focus on resolving issues as they arise. This involves identifying a problem, determining its cause, examining potential strategies, implementing a solution, and assessing its effectiveness. They are more reactive in nature, tackling problems that have already occurred. On the contrary, future problem-solving is more about anticipation. Instead of waiting for problems to occur, it assumes probable issues to arise in the future. It then engages in creating strategies to prevent those problems or mitigate their impact. This proactive approach of preemptively addressing potential problems is a key characteristic of future problem-solving. Use of Foresight in Future Problem-Solving In addition to anticipating problems, future problem-solving often uses foresight techniques, such as forecasting or scenario planning. These methods enable a better understanding of potential future environments and how current decisions might impact them. Hence, future problem-solving is not only about solving problems but also about crafting the future. Systems Thinking in Future Problem-Solving Another aspect that sets future problem-solving apart is the use of systems thinking. Instead of looking at problems in isolation, it sees them as part of a larger system. This approach helps in grasping the big picture and understanding the complex interdependence between various elements. In conclusion, future problem-solving surpasses traditional problem-solving just from being reactive to proactive. It is not only about dealing with present realities but also preparing for prospective issues. It leverages foresight tools and systems thinking to understand and shape the future, making it a more comprehensive and strategic approach to problem-solving.

In the context of future problem-solving, how does one identify potential long-term consequences of a solution?

Identification of Potential Long-Term Consequences In foreseeing the long-term outcomes of a solution, certain strategies can be observed. First and foremost, one must understand the problem comprehensively. By doing so, they position themselves to anticipate the impacts of the solution better. Analyzing Current Trends Analyzing trends associated with the problem helps to predict potential challenges. It involves looking at current patterns within the system and using them to envisage probable impacts. Implementing Scenario Planning Scenario planning avails one with multiple hypothetical situations, giving an array of potential outcomes. It allows decision-makers to examine a diverse range of scenarios and anticipate possible effects. Modeling and Simulation Additionally, the use of modeling and simulation is essential. These tactics offer a visual representation of the likely consequences, making it easier to discern long-term effects. Integration of Diverse Perspectives Involving a diverse group of stakeholders is also helpful. They provide unique insights into potential outcomes, assisting one to perceive the long-term consequences from a more holistic approach. Use of Decision-Making Tools and Techniques Further, one can employ various decision-making tools and techniques. Techniques such as Risk Analysis, SWOT Analysis, and Decision Trees help in predicting long-term consequences, highlighting potential risks and benefits. Continuous Review and Evaluation Finally, a continuous review and evaluation process allows for early identification of the long-term implications. Regular assessments help in detecting unforeseen consequences, aiding in corrective measures. True tailoring of future problem-solving demands imaginative and strategic thinking. Taking steps to identify long-term consequences, as discussed above, is central in developing sustainable solutions. Utilizing these strategies promotes robust, adaptable problem-solving, instrumental in navigating the ever-evolving complexities of the future.

She describes himself as someone who loves to write about digital marketing, social media and public relations. His personal development special interest lies in self-improvement through reading books on the subject of human behavior; she also has an eye for how these topics apply outside just business or career settings too!

Definition of Problem-Solving With Examples

How To Become a Great Problem Solver?

Need a New Problem-Solving Strategy? Try These!

10 Things You Need to Know About Problem Solving

Problem Solving: Tips, Tricks, and Tactics

How To Improve Your Problem-Solving Skills

Which Common Problems Can Be Solved With NLP Techniques?

Problem Solving - Solve any problem in less than 3 minutes

Problem Solving Method Of Teaching

A Problem Solving Method: Brainstorming

What are Problem Solving Skills?

How To Develop Problem Solving Skills?

How to Fix Any Problem: The 3 Step Approach

Solving problems isn't about the what, it's about the how..

Posted April 8, 2015

Your son is struggling with fractions, actually close to tears while doing his homework. Your car has been making some awful rumbly sound that has you worried. Your boyfriend is angry with you—he felt you were curt and cold to his mother when you met her last weekend.

Life and problems, we all know the drill. At 8, it’s math. At 20, it’s your beat up old car. At 30, the boyfriend with his nose out of joint. And multiple times a day there's everything else in between. The content is always a moving target—fractions, boyfriend, car—but by having a solid problem-solving process in place, moving through the content becomes a lot easier. We're back to the difference between the what of our lives and the how, and the how is what counts. As the parent, you want to help your son master fractions, but even more, you want him to learn how to not become overwhelmed and discouraged by teaching him how to approach and manage the problems in his life, whatever they may be. And a lot of us adults have the same struggles.

Here’s a simple roadmap for solving everyday problems along with the places it’s easy to get stuck. We’re talking mundane stuff here. We’re not talking about sorting how the next equation for string theory, or how best to arrange your living room furniture—sure that’s partly about problem solving but more about intuition and innate creativity . And even though we're focusing on the everyday, that doesn't mean that they can't feel overwhelming or that they are not difficult or complex. But that said, the basic problem-solving approach doesn't change. Here goes:

1. Define the problem as concretely / specifically as possible. This is about narrowing your—what is it that needs to get fixed? This creates problem partialization—taking big junks of overwhelming misery and breaking them down into smaller, more manageable bites. It also makes it easier to do the next two steps.

The Trap: Too vague and general. "Can’t do factions math" is not a solvable problem. Neither is your "car seems to be breaking down," your boyfriend is "upset," or that you were "curt." Ditto for being lonely , unfulfilled, unhappy, life sucks, or the couples I see who say they can’t communicate. Yes, you may feel that way, but that is the summary statement to a more specific concrete problem. You need to drill down. Be specific. At what point does the trail of fraction concepts for your son break down? Why this problem and not the one before? Rumbly sound—where does it change when you speed up, etc.? Curt—tell me what thought I did or sounded like that gave you that impression. Can’t communicate—you’re talking so you can communicate. Tell me what is exactly happening when you feel like you are not.

The other trap is that your overwhelming feelings have ramped up so far—your son is on the verge of tears—that it makes the drilling down and defining difficult to start. The problem is no longer the factions but anxiety that needs to be fixed. So you hug him or suggest he take a break and go play outside for awhile, or as an adult you do deep breathing, meditation , exercise, drink chamomile tea, or vent to a friend. Once you're back under your threshold, you move forward.

2. Decide what you can do. As the parent, you can walk through the problem with your child or if it is over your head, you can hire a tutor or call the teacher. As the child, you ask the teacher or the smartest kid in the class for help. The car—if you have mechanic skills, you can check it out yourself. If not, take it to a garage. If you don’t have money to fix it, take the bus 'till you can save up the money or see if your dad can lend you the money. Talk to your boyfriend. Apologize for unintentionally hurting his and his mother’s feelings. Offer to talk to her. Find out what specifically bothered him so much. If, as a couple, you feel you don’t communicate, be proactive and initiate conversations about where you both get stuck in conversations and see where they lead.

You get the idea.

The Trap: Rather than focusing on what can and cannot do, you instead, particularly in relationship problems, tie your solution to what you want someone else to do. Rather than having that conversation with your boyfriend you obsess about his need to simply grow up and not be so sensitive and critical. Rather sitting down with your son and walking step-by-step through the math problems, you get mentally hung up on wishing he would try harder and not just whine.

Hitching your problem-solving wagon to someone else changing is a convoluted path to a solution. Sure, you can snap back at your boyfriend for his immaturity or your son about his whining, but it distracts both of you from solving the immediate problem and often only creates another problem. Keep it simple. Your problem, embrace it.

The other trap is that rather than deciding what you can do, you decide to do nothing, to push the problem to the back burner, hope it will go away somehow, miraculously get better. Sometimes deliberately deciding to wait-and-see has merits, especially if you and/or the other is stressed —this is about lowering the anxiety first. Circle back to the fractions tomorrow, realize that you or your boyfriend are under a lot of stress at work and a heavy conversation right now will only make matters worse, and the car noise hasn't gotten worse and you have too much on your plate to this week to tackle it. This is rational decision-making . But simply pushing it way way back is about denial and magical thinking and emotional rather than rational mind. Don't do this.

3. Take action. Once you've zeroed in on the problem, consider action steps. It's time to take action. Do something! Acting and moving forward will help lower your anxiety and help stop it from staring you in the face or perpetually circling around your brain as chronic worry. So get an estimate for the car repair, talk to the teacher, find a YouTube video on fractions, write a note to your boyfriend. The action empowers you.

The Trap: The big trap here is thinking that you think you need to find the right solution that guarantees success before you can act. Unless you do—you believe—you'll wind up making a big mistake. This is the Ready, Aim, Fire approach to problems where you spend a lot of time sitting on the couch or endless hours on the Internet doing research, or forever talking to friends trying to figure out the perfect course before doing anything.

The other more practical approach is based on Ready, Fire, Aim. Do something and then see what happens next, and adjust. This is how a lot of big problems are eventually solved—think Edison and his trying out 1,000 of filaments for his light bulb before finding the best one—the trial and error, the creating the feedback loop that helps you discover what does and doesn't work.

So you try the conversation or leave the note with your boyfriend and see what happens next. You call the teacher, or walk through the factions with your son and see if he can with your support connect the dots. You look for a hole in the exhaust system, get a second estimate on the car while also approaching your dad for a loan and looking up bus routes. Whatever you do, don't endlessly mull, brood, and obsess. Perfectionism gets in the way of problem-solving because it can freeze decisive action needed to break through to a solution.

That’s it. All this moving through is a matter of practice and attitude, sometimes support, and like most things, it gets easier with repetition. So give this a try.

You can’t make a mistake.

Feel free to follow me on Twitter

Bob Taibbi, L.C.S.W., has 49 years of clinical experience. He is the author of 13 books and over 300 articles and provides training nationally and internationally.

• Find a Therapist
• Find a Treatment Center
• Find a Psychiatrist
• Find a Support Group
• Find Teletherapy
• United States
• Brooklyn, NY
• Chicago, IL
• Houston, TX
• Los Angeles, CA
• New York, NY
• Portland, OR
• San Diego, CA
• San Francisco, CA
• Seattle, WA
• Washington, DC
• Asperger's
• Bipolar Disorder
• Chronic Pain
• Eating Disorders
• Passive Aggression
• Personality
• Goal Setting
• Positive Psychology
• Stopping Smoking
• Low Sexual Desire
• Relationships
• Child Development
• Therapy Center NEW
• Diagnosis Dictionary
• Types of Therapy

Understanding what emotional intelligence looks like and the steps needed to improve it could light a path to a more emotionally adept world.

• Coronavirus Disease 2019
• Affective Forecasting
• Neuroscience

University Human Resources

8-step problem solving process, organizational effectiveness.

121 University Services Building, Suite 50 Iowa City , IA 52242-1911 United States

Step 1: Define the Problem

• What is the problem?
• How did you discover the problem?
• When did the problem start and how long has this problem been going on?
• Is there enough data available to contain the problem and prevent it from getting passed to the next process step? If yes, contain the problem.

Step 2: Clarify the Problem

• What data is available or needed to help clarify, or fully understand the problem?
• Is it a top priority to resolve the problem at this point in time?
• Are additional resources required to clarify the problem? If yes, elevate the problem to your leader to help locate the right resources and form a team. 
•  Consider a Lean Event (Do-it, Burst, RPI, Project).
• ∙Ensure the problem is contained and does not get passed to the next process step.

Step 3: Define the Goals

• What is your end goal or desired future state?
• What will you accomplish if you fix this problem?
• What is the desired timeline for solving this problem?

Step 4: Identify Root Cause of the Problem

• Identify possible causes of the problem.
• Prioritize possible root causes of the problem.
• What information or data is there to validate the root cause?

Step 5: Develop Action Plan

• Generate a list of actions required to address the root cause and prevent problem from getting to others.
• Assign an owner and timeline to each action.
• Status actions to ensure completion.

Step 6: Execute Action Plan

• Implement action plan to address the root cause.
• Verify actions are completed.

Step 7: Evaluate the Results

• Monitor and Collect Data.
• Did you meet your goals defined in step 3? If not, repeat the 8-Step Process. 
• Were there any unforeseen consequences?
• If problem is resolved, remove activities that were added previously to contain the problem.

Step 8: Continuously Improve

• Look for additional opportunities to implement solution.
• Ensure problem will not come back and communicate lessons learned.
• If needed, repeat the 8-Step Problem Solving Process to drive further improvements.

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

Share Podcast

Do You Understand the Problem You’re Trying to Solve?

To solve tough problems at work, first ask these questions.

• Apple Podcasts
• Google Podcasts

Problem solving skills are invaluable in any job. But all too often, we jump to find solutions to a problem without taking time to really understand the dilemma we face, according to Thomas Wedell-Wedellsborg , an expert in innovation and the author of the book, What’s Your Problem?: To Solve Your Toughest Problems, Change the Problems You Solve .

In this episode, you’ll learn how to reframe tough problems by asking questions that reveal all the factors and assumptions that contribute to the situation. You’ll also learn why searching for just one root cause can be misleading.

Key episode topics include: leadership, decision making and problem solving, power and influence, business management.

HBR On Leadership curates the best case studies and conversations with the world’s top business and management experts, to help you unlock the best in those around you. New episodes every week.

• Listen to the original HBR IdeaCast episode: The Secret to Better Problem Solving (2016)
• Find more episodes of HBR IdeaCast
• Discover 100 years of Harvard Business Review articles, case studies, podcasts, and more at HBR.org .

HANNAH BATES: Welcome to HBR on Leadership , case studies and conversations with the world’s top business and management experts, hand-selected to help you unlock the best in those around you.

Problem solving skills are invaluable in any job. But even the most experienced among us can fall into the trap of solving the wrong problem.

Thomas Wedell-Wedellsborg says that all too often, we jump to find solutions to a problem – without taking time to really understand what we’re facing.

He’s an expert in innovation, and he’s the author of the book, What’s Your Problem?: To Solve Your Toughest Problems, Change the Problems You Solve .

  In this episode, you’ll learn how to reframe tough problems, by asking questions that reveal all the factors and assumptions that contribute to the situation. You’ll also learn why searching for one root cause can be misleading. And you’ll learn how to use experimentation and rapid prototyping as problem-solving tools.

This episode originally aired on HBR IdeaCast in December 2016. Here it is.

SARAH GREEN CARMICHAEL: Welcome to the HBR IdeaCast from Harvard Business Review. I’m Sarah Green Carmichael.

Problem solving is popular. People put it on their resumes. Managers believe they excel at it. Companies count it as a key proficiency. We solve customers’ problems.

The problem is we often solve the wrong problems. Albert Einstein and Peter Drucker alike have discussed the difficulty of effective diagnosis. There are great frameworks for getting teams to attack true problems, but they’re often hard to do daily and on the fly. That’s where our guest comes in.

Thomas Wedell-Wedellsborg is a consultant who helps companies and managers reframe their problems so they can come up with an effective solution faster. He asks the question “Are You Solving The Right Problems?” in the January-February 2017 issue of Harvard Business Review. Thomas, thank you so much for coming on the HBR IdeaCast .

THOMAS WEDELL-WEDELLSBORG: Thanks for inviting me.

SARAH GREEN CARMICHAEL: So, I thought maybe we could start by talking about the problem of talking about problem reframing. What is that exactly?

THOMAS WEDELL-WEDELLSBORG: Basically, when people face a problem, they tend to jump into solution mode to rapidly, and very often that means that they don’t really understand, necessarily, the problem they’re trying to solve. And so, reframing is really a– at heart, it’s a method that helps you avoid that by taking a second to go in and ask two questions, basically saying, first of all, wait. What is the problem we’re trying to solve? And then crucially asking, is there a different way to think about what the problem actually is?

SARAH GREEN CARMICHAEL: So, I feel like so often when this comes up in meetings, you know, someone says that, and maybe they throw out the Einstein quote about you spend an hour of problem solving, you spend 55 minutes to find the problem. And then everyone else in the room kind of gets irritated. So, maybe just give us an example of maybe how this would work in practice in a way that would not, sort of, set people’s teeth on edge, like oh, here Sarah goes again, reframing the whole problem instead of just solving it.

THOMAS WEDELL-WEDELLSBORG: I mean, you’re bringing up something that’s, I think is crucial, which is to create legitimacy for the method. So, one of the reasons why I put out the article is to give people a tool to say actually, this thing is still important, and we need to do it. But I think the really critical thing in order to make this work in a meeting is actually to learn how to do it fast, because if you have the idea that you need to spend 30 minutes in a meeting delving deeply into the problem, I mean, that’s going to be uphill for most problems. So, the critical thing here is really to try to make it a practice you can implement very, very rapidly.

There’s an example that I would suggest memorizing. This is the example that I use to explain very rapidly what it is. And it’s basically, I call it the slow elevator problem. You imagine that you are the owner of an office building, and that your tenants are complaining that the elevator’s slow.

Now, if you take that problem framing for granted, you’re going to start thinking creatively around how do we make the elevator faster. Do we install a new motor? Do we have to buy a new lift somewhere?

The thing is, though, if you ask people who actually work with facilities management, well, they’re going to have a different solution for you, which is put up a mirror next to the elevator. That’s what happens is, of course, that people go oh, I’m busy. I’m busy. I’m– oh, a mirror. Oh, that’s beautiful.

And then they forget time. What’s interesting about that example is that the idea with a mirror is actually a solution to a different problem than the one you first proposed. And so, the whole idea here is once you get good at using reframing, you can quickly identify other aspects of the problem that might be much better to try to solve than the original one you found. It’s not necessarily that the first one is wrong. It’s just that there might be better problems out there to attack that we can, means we can do things much faster, cheaper, or better.

SARAH GREEN CARMICHAEL: So, in that example, I can understand how A, it’s probably expensive to make the elevator faster, so it’s much cheaper just to put up a mirror. And B, maybe the real problem people are actually feeling, even though they’re not articulating it right, is like, I hate waiting for the elevator. But if you let them sort of fix their hair or check their teeth, they’re suddenly distracted and don’t notice.

But if you have, this is sort of a pedestrian example, but say you have a roommate or a spouse who doesn’t clean up the kitchen. Facing that problem and not having your elegant solution already there to highlight the contrast between the perceived problem and the real problem, how would you take a problem like that and attack it using this method so that you can see what some of the other options might be?

THOMAS WEDELL-WEDELLSBORG: Right. So, I mean, let’s say it’s you who have that problem. I would go in and say, first of all, what would you say the problem is? Like, if you were to describe your view of the problem, what would that be?

SARAH GREEN CARMICHAEL: I hate cleaning the kitchen, and I want someone else to clean it up.

THOMAS WEDELL-WEDELLSBORG: OK. So, my first observation, you know, that somebody else might not necessarily be your spouse. So, already there, there’s an inbuilt assumption in your question around oh, it has to be my husband who does the cleaning. So, it might actually be worth, already there to say, is that really the only problem you have? That you hate cleaning the kitchen, and you want to avoid it? Or might there be something around, as well, getting a better relationship in terms of how you solve problems in general or establishing a better way to handle small problems when dealing with your spouse?

SARAH GREEN CARMICHAEL: Or maybe, now that I’m thinking that, maybe the problem is that you just can’t find the stuff in the kitchen when you need to find it.

THOMAS WEDELL-WEDELLSBORG: Right, and so that’s an example of a reframing, that actually why is it a problem that the kitchen is not clean? Is it only because you hate the act of cleaning, or does it actually mean that it just takes you a lot longer and gets a lot messier to actually use the kitchen, which is a different problem. The way you describe this problem now, is there anything that’s missing from that description?

SARAH GREEN CARMICHAEL: That is a really good question.

THOMAS WEDELL-WEDELLSBORG: Other, basically asking other factors that we are not talking about right now, and I say those because people tend to, when given a problem, they tend to delve deeper into the detail. What often is missing is actually an element outside of the initial description of the problem that might be really relevant to what’s going on. Like, why does the kitchen get messy in the first place? Is it something about the way you use it or your cooking habits? Is it because the neighbor’s kids, kind of, use it all the time?

There might, very often, there might be issues that you’re not really thinking about when you first describe the problem that actually has a big effect on it.

SARAH GREEN CARMICHAEL: I think at this point it would be helpful to maybe get another business example, and I’m wondering if you could tell us the story of the dog adoption problem.

THOMAS WEDELL-WEDELLSBORG: Yeah. This is a big problem in the US. If you work in the shelter industry, basically because dogs are so popular, more than 3 million dogs every year enter a shelter, and currently only about half of those actually find a new home and get adopted. And so, this is a problem that has persisted. It’s been, like, a structural problem for decades in this space. In the last three years, where people found new ways to address it.

So a woman called Lori Weise who runs a rescue organization in South LA, and she actually went in and challenged the very idea of what we were trying to do. She said, no, no. The problem we’re trying to solve is not about how to get more people to adopt dogs. It is about keeping the dogs with their first family so they never enter the shelter system in the first place.

In 2013, she started what’s called a Shelter Intervention Program that basically works like this. If a family comes and wants to hand over their dog, these are called owner surrenders. It’s about 30% of all dogs that come into a shelter. All they would do is go up and ask, if you could, would you like to keep your animal? And if they said yes, they would try to fix whatever helped them fix the problem, but that made them turn over this.

And sometimes that might be that they moved into a new building. The landlord required a deposit, and they simply didn’t have the money to put down a deposit. Or the dog might need a $10 rabies shot, but they didn’t know how to get access to a vet.

And so, by instigating that program, just in the first year, she took her, basically the amount of dollars they spent per animal they helped went from something like $85 down to around $60. Just an immediate impact, and her program now is being rolled out, is being supported by the ASPCA, which is one of the big animal welfare stations, and it’s being rolled out to various other places.

And I think what really struck me with that example was this was not dependent on having the internet. This was not, oh, we needed to have everybody mobile before we could come up with this. This, conceivably, we could have done 20 years ago. Only, it only happened when somebody, like in this case Lori, went in and actually rethought what the problem they were trying to solve was in the first place.

SARAH GREEN CARMICHAEL: So, what I also think is so interesting about that example is that when you talk about it, it doesn’t sound like the kind of thing that would have been thought of through other kinds of problem solving methods. There wasn’t necessarily an After Action Review or a 5 Whys exercise or a Six Sigma type intervention. I don’t want to throw those other methods under the bus, but how can you get such powerful results with such a very simple way of thinking about something?

THOMAS WEDELL-WEDELLSBORG: That was something that struck me as well. This, in a way, reframing and the idea of the problem diagnosis is important is something we’ve known for a long, long time. And we’ve actually have built some tools to help out. If you worked with us professionally, you are familiar with, like, Six Sigma, TRIZ, and so on. You mentioned 5 Whys. A root cause analysis is another one that a lot of people are familiar with.

Those are our good tools, and they’re definitely better than nothing. But what I notice when I work with the companies applying those was those tools tend to make you dig deeper into the first understanding of the problem we have. If it’s the elevator example, people start asking, well, is that the cable strength, or is the capacity of the elevator? That they kind of get caught by the details.

That, in a way, is a bad way to work on problems because it really assumes that there’s like a, you can almost hear it, a root cause. That you have to dig down and find the one true problem, and everything else was just symptoms. That’s a bad way to think about problems because problems tend to be multicausal.

There tend to be lots of causes or levers you can potentially press to address a problem. And if you think there’s only one, if that’s the right problem, that’s actually a dangerous way. And so I think that’s why, that this is a method I’ve worked with over the last five years, trying to basically refine how to make people better at this, and the key tends to be this thing about shifting out and saying, is there a totally different way of thinking about the problem versus getting too caught up in the mechanistic details of what happens.

SARAH GREEN CARMICHAEL: What about experimentation? Because that’s another method that’s become really popular with the rise of Lean Startup and lots of other innovation methodologies. Why wouldn’t it have worked to, say, experiment with many different types of fixing the dog adoption problem, and then just pick the one that works the best?

THOMAS WEDELL-WEDELLSBORG: You could say in the dog space, that’s what’s been going on. I mean, there is, in this industry and a lot of, it’s largely volunteer driven. People have experimented, and they found different ways of trying to cope. And that has definitely made the problem better. So, I wouldn’t say that experimentation is bad, quite the contrary. Rapid prototyping, quickly putting something out into the world and learning from it, that’s a fantastic way to learn more and to move forward.

My point is, though, that I feel we’ve come to rely too much on that. There’s like, if you look at the start up space, the wisdom is now just to put something quickly into the market, and then if it doesn’t work, pivot and just do more stuff. What reframing really is, I think of it as the cognitive counterpoint to prototyping. So, this is really a way of seeing very quickly, like not just working on the solution, but also working on our understanding of the problem and trying to see is there a different way to think about that.

If you only stick with experimentation, again, you tend to sometimes stay too much in the same space trying minute variations of something instead of taking a step back and saying, wait a minute. What is this telling us about what the real issue is?

SARAH GREEN CARMICHAEL: So, to go back to something that we touched on earlier, when we were talking about the completely hypothetical example of a spouse who does not clean the kitchen–

THOMAS WEDELL-WEDELLSBORG: Completely, completely hypothetical.

SARAH GREEN CARMICHAEL: Yes. For the record, my husband is a great kitchen cleaner.

You started asking me some questions that I could see immediately were helping me rethink that problem. Is that kind of the key, just having a checklist of questions to ask yourself? How do you really start to put this into practice?

THOMAS WEDELL-WEDELLSBORG: I think there are two steps in that. The first one is just to make yourself better at the method. Yes, you should kind of work with a checklist. In the article, I kind of outlined seven practices that you can use to do this.

But importantly, I would say you have to consider that as, basically, a set of training wheels. I think there’s a big, big danger in getting caught in a checklist. This is something I work with.

My co-author Paddy Miller, it’s one of his insights. That if you start giving people a checklist for things like this, they start following it. And that’s actually a problem, because what you really want them to do is start challenging their thinking.

So the way to handle this is to get some practice using it. Do use the checklist initially, but then try to step away from it and try to see if you can organically make– it’s almost a habit of mind. When you run into a colleague in the hallway and she has a problem and you have five minutes, like, delving in and just starting asking some of those questions and using your intuition to say, wait, how is she talking about this problem? And is there a question or two I can ask her about the problem that can help her rethink it?

SARAH GREEN CARMICHAEL: Well, that is also just a very different approach, because I think in that situation, most of us can’t go 30 seconds without jumping in and offering solutions.

THOMAS WEDELL-WEDELLSBORG: Very true. The drive toward solutions is very strong. And to be clear, I mean, there’s nothing wrong with that if the solutions work. So, many problems are just solved by oh, you know, oh, here’s the way to do that. Great.

But this is really a powerful method for those problems where either it’s something we’ve been banging our heads against tons of times without making progress, or when you need to come up with a really creative solution. When you’re facing a competitor with a much bigger budget, and you know, if you solve the same problem later, you’re not going to win. So, that basic idea of taking that approach to problems can often help you move forward in a different way than just like, oh, I have a solution.

I would say there’s also, there’s some interesting psychological stuff going on, right? Where you may have tried this, but if somebody tries to serve up a solution to a problem I have, I’m often resistant towards them. Kind if like, no, no, no, no, no, no. That solution is not going to work in my world. Whereas if you get them to discuss and analyze what the problem really is, you might actually dig something up.

Let’s go back to the kitchen example. One powerful question is just to say, what’s your own part in creating this problem? It’s very often, like, people, they describe problems as if it’s something that’s inflicted upon them from the external world, and they are innocent bystanders in that.

SARAH GREEN CARMICHAEL: Right, or crazy customers with unreasonable demands.

THOMAS WEDELL-WEDELLSBORG: Exactly, right. I don’t think I’ve ever met an agency or consultancy that didn’t, like, gossip about their customers. Oh, my god, they’re horrible. That, you know, classic thing, why don’t they want to take more risk? Well, risk is bad.

It’s their business that’s on the line, not the consultancy’s, right? So, absolutely, that’s one of the things when you step into a different mindset and kind of, wait. Oh yeah, maybe I actually am part of creating this problem in a sense, as well. That tends to open some new doors for you to move forward, in a way, with stuff that you may have been struggling with for years.

SARAH GREEN CARMICHAEL: So, we’ve surfaced a couple of questions that are useful. I’m curious to know, what are some of the other questions that you find yourself asking in these situations, given that you have made this sort of mental habit that you do? What are the questions that people seem to find really useful?

THOMAS WEDELL-WEDELLSBORG: One easy one is just to ask if there are any positive exceptions to the problem. So, was there day where your kitchen was actually spotlessly clean? And then asking, what was different about that day? Like, what happened there that didn’t happen the other days? That can very often point people towards a factor that they hadn’t considered previously.

SARAH GREEN CARMICHAEL: We got take-out.

THOMAS WEDELL-WEDELLSBORG: S,o that is your solution. Take-out from [INAUDIBLE]. That might have other problems.

Another good question, and this is a little bit more high level. It’s actually more making an observation about labeling how that person thinks about the problem. And what I mean with that is, we have problem categories in our head. So, if I say, let’s say that you describe a problem to me and say, well, we have a really great product and are, it’s much better than our previous product, but people aren’t buying it. I think we need to put more marketing dollars into this.

Now you can go in and say, that’s interesting. This sounds like you’re thinking of this as a communications problem. Is there a different way of thinking about that? Because you can almost tell how, when the second you say communications, there are some ideas about how do you solve a communications problem. Typically with more communication.

And what you might do is go in and suggest, well, have you considered that it might be, say, an incentive problem? Are there incentives on behalf of the purchasing manager at your clients that are obstructing you? Might there be incentive issues with your own sales force that makes them want to sell the old product instead of the new one?

So literally, just identifying what type of problem does this person think about, and is there different potential way of thinking about it? Might it be an emotional problem, a timing problem, an expectations management problem? Thinking about what label of what type of problem that person is kind of thinking as it of.

SARAH GREEN CARMICHAEL: That’s really interesting, too, because I think so many of us get requests for advice that we’re really not qualified to give. So, maybe the next time that happens, instead of muddying my way through, I will just ask some of those questions that we talked about instead.

THOMAS WEDELL-WEDELLSBORG: That sounds like a good idea.

SARAH GREEN CARMICHAEL: So, Thomas, this has really helped me reframe the way I think about a couple of problems in my own life, and I’m just wondering. I know you do this professionally, but is there a problem in your life that thinking this way has helped you solve?

THOMAS WEDELL-WEDELLSBORG: I’ve, of course, I’ve been swallowing my own medicine on this, too, and I think I have, well, maybe two different examples, and in one case somebody else did the reframing for me. But in one case, when I was younger, I often kind of struggled a little bit. I mean, this is my teenage years, kind of hanging out with my parents. I thought they were pretty annoying people. That’s not really fair, because they’re quite wonderful, but that’s what life is when you’re a teenager.

And one of the things that struck me, suddenly, and this was kind of the positive exception was, there was actually an evening where we really had a good time, and there wasn’t a conflict. And the core thing was, I wasn’t just seeing them in their old house where I grew up. It was, actually, we were at a restaurant. And it suddenly struck me that so much of the sometimes, kind of, a little bit, you love them but they’re annoying kind of dynamic, is tied to the place, is tied to the setting you are in.

And of course, if– you know, I live abroad now, if I visit my parents and I stay in my old bedroom, you know, my mother comes in and wants to wake me up in the morning. Stuff like that, right? And it just struck me so, so clearly that it’s– when I change this setting, if I go out and have dinner with them at a different place, that the dynamic, just that dynamic disappears.

SARAH GREEN CARMICHAEL: Well, Thomas, this has been really, really helpful. Thank you for talking with me today.

THOMAS WEDELL-WEDELLSBORG: Thank you, Sarah.  

HANNAH BATES: That was Thomas Wedell-Wedellsborg in conversation with Sarah Green Carmichael on the HBR IdeaCast. He’s an expert in problem solving and innovation, and he’s the author of the book, What’s Your Problem?: To Solve Your Toughest Problems, Change the Problems You Solve .

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

We’re a production of Harvard Business Review. If you want more podcasts, articles, case studies, books, and videos like this, find it all at HBR dot org.

This episode was produced by Anne Saini, and me, Hannah Bates. Ian Fox is our editor. Music by Coma Media. Special thanks to Maureen Hoch, Adi Ignatius, Karen Player, Ramsey Khabbaz, Nicole Smith, Anne Bartholomew, and you – our listener.

See you next week.

• Subscribe On:

Latest in this series

This article is about leadership.

• Decision making and problem solving
• Power and influence
• Business management

Partner Center