list the six stages of 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

How to Build a Strong Culture in a Distributed Team

Mind Tools Store

About Mind Tools Content

Discover something new today

Top tips for delegating.

Delegate work to your team members effectively with these top tips

Ten Dos and Don'ts of Change Conversations

Tips for tackling discussions about change

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

How to create brand champions.

A Seven-Step Methodology to Help Create Brand Champions in an Organization

How to Guides

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

Six Steps to Develop an Effective Problem-Solving Process

by Rawzaba Alhalabi Published on November 1, 2017

Problem-solving involves thought and understanding. Although it may appear simple, identifying a problem may be a challenging process.

“Problems are only opportunities in work clothes”, says American industrialist Henry Kaiser. According to Concise Oxford Dictionary (1995), a problem is “ doubtful or difficult matter requiring a solution” and “something hard to understand or accomplish or deal with.” Such situations are at the center of what many people do at work every day.

Whether to help a client solve a problem, support a problem-solver, or to discover new problems, problem-solving is a crucial element to the workplace ingredients. Everyone can benefit from effective problem-solving skills that would make people happier. Everyone wins. Hence, this approach is a critical element but how can you do it effectively? You need to find a solution, but not right away. People tend to put the solution at the beginning of the process but they actually needed it at the end of the process.

Here are six steps to an effective problem-solving process:

Identify the issues, understand everyone’s interests, list the possible solutions, make a decision, implement the solution.

By following the whole process, you will be able to enhance your problem-solving skills and increase your patience. Keep in mind that effective problem solving does take some time and attention. You have to always be ready to hit the brakes and slow down. A problem is like a bump road. Take it right and you’ll find yourself in good shape for the straightaway that follows. Take it too fast and you may not be in as good shape.

Case study 1:

According to Real Time Economics, there are industries that have genuinely evolved, with more roles for people with analytical and problem-solving skills. In healthcare, for example, a regulatory change requiring the digitization of health records has led to greater demand for medical records technicians. Technological change in the manufacturing industry has reduced routine factory jobs while demanding more skilled workers who can operate complex machinery.

Case study 2:

Yolanda was having a hard time dealing with difficult clients and dealing with her team at the office, so she decided to take a problem-solving course. “I was very pleased with the 2-day Problem Solving program at RSM.  It is an excellent investment for anyone involved in the strategic decision-making process—be it in their own company or as a consultant charged with supporting organizations facing strategic challenges.“

Yolanda Barreros Gutiérrez, B&C Consulting

As a response to the COVID-19 outbreak, Potential.com is offering individuals free access to our future skills library (20+ Courses) to support you during the COVID outbreak. It’s your chance to learn essential skills to help you prepare for future jobs. Register now for free using your details and coupon code: potentialreader .

Click here to register (coupon embedded) .

Having read this I believed it was extremely enlightening. I appreciate you taking the time and energy to put tis informative article together. I onc again findd myself spending a significant amount of time both reading and leavfing comments. But so what, it was still worth it!

Leave a Reply Cancel reply

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

Save my name, email, and website in this browser for the next time I comment.

Subscribe to our newsletter

• Guide: Problem Solving

Daniel Croft

Daniel Croft is an experienced continuous improvement manager with a Lean Six Sigma Black Belt and a Bachelor's degree in Business Management. With more than ten years of experience applying his skills across various industries, Daniel specializes in optimizing processes and improving efficiency. His approach combines practical experience with a deep understanding of business fundamentals to drive meaningful change.

• Last Updated: January 7, 2024
• Learn Lean Sigma

Problem-solving stands as a fundamental skill, crucial in navigating the complexities of both everyday life and professional environments. Far from merely providing quick fixes, it entails a comprehensive process involving the identification, analysis, and resolution of issues.

This multifaceted approach requires an understanding of the problem’s nature, the exploration of its various components, and the development of effective solutions. At its core, problem-solving serves as a bridge from the current situation to a desired outcome, requiring not only the recognition of an existing gap but also the precise definition and thorough analysis of the problem to find viable solutions.

Table of Contents

What is problem solving.

At its core, problem-solving is about bridging the gap between the current situation and the desired outcome. It starts with recognizing that a discrepancy exists, which requires intervention to correct or improve. The ability to identify a problem is the first step, but it’s equally crucial to define it accurately. A well-defined problem is half-solved, as the saying goes.

Analyzing the problem is the next critical step. This analysis involves breaking down the problem into smaller parts to understand its intricacies. It requires looking at the problem from various angles and considering all relevant factors – be they environmental, social, technical, or economic. This comprehensive analysis aids in developing a deeper understanding of the problem’s root causes, rather than just its symptoms.

Finally, effective problem-solving involves the implementation of the chosen solution and its subsequent evaluation. This stage tests the practicality of the solution and its effectiveness in the real world. It’s a critical phase where theoretical solutions meet practical application.

The Nature of Problems

The nature of the problem significantly influences the approach to solving it. Problems vary greatly in their complexity and structure, and understanding this is crucial for effective problem-solving.

Simple vs. Complex Problems : Simple problems are straightforward, often with clear solutions. They usually have a limited number of variables and predictable outcomes. On the other hand, complex problems are multi-faceted. They involve multiple variables, stakeholders, and potential outcomes, often requiring a more sophisticated analysis and a multi-pronged approach to solving.

Structured vs. Unstructured Problems : Structured problems are well-defined. They follow a specific pattern or set of rules, making their outcomes more predictable. These problems often have established methodologies for solving. For example, mathematical problems usually fall into this category. Unstructured problems, in contrast, are more ambiguous. They lack a clear pattern or set of rules, making their outcomes uncertain. These problems require a more exploratory approach, often involving trial and error, to identify potential solutions.

Understanding the type of problem at hand is essential, as it dictates the approach. For instance, a simple problem might require a straightforward solution, while a complex problem might need a more comprehensive, step-by-step approach. Similarly, structured problems might benefit from established methodologies, whereas unstructured problems might need more innovative and creative problem-solving techniques.

The Problem-Solving Process

The process of problem-solving is a methodical approach that involves several distinct stages. Each stage plays a crucial role in navigating from the initial recognition of a problem to its final resolution. Let’s explore each of these stages in detail.

Step 1: Identifying the Problem

Step 2: defining the problem.

Once the problem is identified, the next step is to define it clearly and precisely. This is a critical phase because a well-defined problem often suggests its solution. Defining the problem involves breaking it down into smaller, more manageable parts. It also includes understanding the scope and impact of the problem. A clear definition helps in focusing efforts and resources efficiently and serves as a guide to stay on track during the problem-solving process.

Step 3: Analyzing the Problem

Step 4: generating solutions, step 5: evaluating and selecting solutions.

After generating a list of possible solutions, the next step is to evaluate each one critically. This evaluation includes considering the feasibility, costs, benefits, and potential impact of each solution. Techniques like cost-benefit analysis, risk assessment, and scenario planning can be useful here. The aim is to select the solution that best addresses the problem in the most efficient and effective way, considering the available resources and constraints.

Step 6: Implementing the Solution

Step 7: reviewing and reflecting.

The final stage in the problem-solving process is to review the implemented solution and reflect on its effectiveness and the process as a whole. This involves assessing whether the solution met its intended goals and what could have been done differently. Reflection is a critical part of learning and improvement. It helps in understanding what worked well and what didn’t, providing valuable insights for future problem-solving efforts.

Tools and Techniques for Effective Problem Solving

Problem-solving is a multifaceted endeavor that requires a variety of tools and techniques to navigate effectively. Different stages of the problem-solving process can benefit from specific strategies, enhancing the efficiency and effectiveness of the solutions developed. Here’s a detailed look at some key tools and techniques:

Brainstorming

Swot analysis (strengths, weaknesses, opportunities, threats), root cause analysis.

This is a method used to identify the underlying causes of a problem, rather than just addressing its symptoms. One popular technique within root cause analysis is the “ 5 Whys ” method. This involves asking “why” multiple times (traditionally five) until the fundamental cause of the problem is uncovered. This technique encourages deeper thinking and can reveal connections that aren’t immediately obvious. By addressing the root cause, solutions are more likely to be effective and long-lasting.

Mind Mapping

Each of these tools and techniques can be adapted to different types of problems and situations. Effective problem solvers often use a combination of these methods, depending on the nature of the problem and the context in which it exists. By leveraging these tools, one can enhance their ability to dissect complex problems, generate creative solutions, and implement effective strategies to address challenges.

Developing Problem-Solving Skills

Developing problem-solving skills is a dynamic process that hinges on both practice and introspection. Engaging with a diverse array of problems enhances one’s ability to adapt and apply different strategies. This exposure is crucial as it allows individuals to encounter various scenarios, ranging from straightforward to complex, each requiring a unique approach. Collaborating with others in teams is especially beneficial. It broadens one’s perspective, offering insights into different ways of thinking and approaching problems. Such collaboration fosters a deeper understanding of how diverse viewpoints can contribute to more robust solutions.

Reflection is equally important in the development of problem-solving skills. Reflecting on both successes and failures provides valuable lessons. Successes reinforce effective strategies and boost confidence, while failures are rich learning opportunities that highlight areas for improvement. This reflective practice enables one to understand what worked, what didn’t, and why.

Critical thinking is a foundational skill in problem-solving. It involves analyzing information, evaluating different perspectives, and making reasoned judgments. Creativity is another vital component. It pushes the boundaries of conventional thinking and leads to innovative solutions. Effective communication also plays a crucial role, as it ensures that ideas are clearly understood and collaboratively refined.

In conclusion, problem-solving is an indispensable skill set that blends analytical thinking, creativity, and practical implementation. It’s a journey from understanding the problem to applying a solution and learning from the outcome.

Whether dealing with simple or complex issues, or structured or unstructured challenges, the essence of problem-solving lies in a methodical approach and the effective use of various tools and techniques. It’s a skill that is honed over time, through experience, reflection, and the continuous development of critical thinking, creativity, and communication abilities. In mastering problem-solving, one not only addresses immediate issues but also builds a foundation for future challenges, leading to more innovative and effective outcomes.

• Mourtos, N.J., Okamoto, N.D. and Rhee, J., 2004, February. Defining, teaching, and assessing problem solving skills . In  7th UICEE Annual Conference on Engineering Education  (pp. 1-5).
• Foshay, R. and Kirkley, J., 2003. Principles for teaching problem solving.   Technical paper ,  4 (1), pp.1-16.

Q: What are the key steps in the problem-solving process?

A : The problem-solving process involves several key steps: identifying the problem, defining it clearly, analyzing it to understand its root causes, generating a range of potential solutions, evaluating and selecting the most viable solution, implementing the chosen solution, and finally, reviewing and reflecting on the effectiveness of the solution and the process used to arrive at it.

Q: How can brainstorming be effectively used in problem-solving?

A: Brainstorming is effective in the solution generation phase of problem-solving. It involves gathering a group and encouraging the free flow of ideas without immediate criticism. The goal is to produce a large quantity of ideas, fostering creative thinking. This technique helps in uncovering unique and innovative solutions that might not surface in a more structured setting.

Q: What is SWOT Analysis and how does it aid in problem-solving?

A : SWOT Analysis is a strategic planning tool used to evaluate the Strengths, Weaknesses, Opportunities, and Threats involved in a situation. In problem-solving, it aids by providing a clear understanding of the internal and external factors that could impact the problem and potential solutions. This analysis helps in formulating strategies that leverage strengths and opportunities while mitigating weaknesses and threats.

Q: Why is it important to understand the nature of a problem before solving it?

A : Understanding the nature of a problem is crucial as it dictates the approach for solving it. Problems can be simple or complex, structured or unstructured, and each type requires a different strategy. A clear understanding of the problem’s nature helps in applying the appropriate methods and tools for effective resolution.

Q: How does reflection contribute to developing problem-solving skills?

A : Reflection is a critical component in developing problem-solving skills. It involves looking back at the problem-solving process and the implemented solution to assess what worked well and what didn’t. Reflecting on both successes and failures provides valuable insights and lessons, helping to refine and improve problem-solving strategies for future challenges. This reflective practice enhances one’s ability to approach problems more effectively over time.

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.

Other Guides

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

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

What Is Problem Solving?

Definition and importance.

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

Problem-Solving Steps

The problem-solving process typically includes the following steps:

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

Defining the Problem

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

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

Generating Solutions

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

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

Evaluating and Selecting Solutions

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

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

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

Implementing and Monitoring the Solution

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

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

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

Problem-Solving Techniques

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

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

Brainstorming

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

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

When brainstorming, remember to:

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

Root Cause Analysis

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

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

SWOT Analysis

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

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

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

Mind Mapping

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

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

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

Examples of Problem Solving in Various Contexts

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

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

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

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

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

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

• Bipolar Disorder
• Therapy Center
• When To See a Therapist
• Types of Therapy
• Best Online Therapy
• Best Couples Therapy
• Best Family Therapy
• Managing Stress
• Sleep and Dreaming
• Understanding Emotions
• Self-Improvement
• Healthy Relationships
• Student Resources
• Personality Types
• Guided Meditations
• Verywell Mind Insights
• 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."

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

• 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

• 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

Data & Visuals

Partner Center

Problem Solving Process: The Ultimate Guide to the Process of Problem Solving

What is problem solving, the process for problem solving, be smart about problem solving.

Whether you manage a team or the entire organization, you need to apply excellent problem solving techniques to keep your organization going. Problems can occur between employees, which needs quick and effective problem solving tricks to continue with your business operations. That is why you need to learn about problem solving stages. Read on to learn more about problem solving.

Problem solving is the ability to offer solutions to difficult or complex issues and devising ways to avoid repetitive occurrences in the future.

Develop a positive approach

Before you handle any issue, the first thing is to have a positive mentality towards the problem. It could be a huge problem that may cause you to panic, but try as much as possible to remain composed and confident during the problem solving process. You want to give it the best outcome without involving emotions. So, stay positive as you figure out how to deal with the issue.

Understand the problem

The next problem solving method is to define the problem you are facing. The issue could be more profound than you think, and that is why you need to be intentional about diagnosing the root cause of the problem. This is the only way to solve the issue, because you can't solve what you cannot diagnose. Know the root cause and the effect of the issue. If possible, write down everything and use the notes as a guide on how to solve the problem.

Be creative about the problem

Creativity is a vital skill that a good problem solver should possess. It helps you think outside the box and approach the issue strategically. You need to address the issue from different angles to avoid leaning on one side.

Determine whether other issues could be a stumbling block to the current problem and devise ways to address it first before you proceed.

Looking for solutions

A single problem can have tens of practical solutions. This is why you need to think deeper and analyze all the possible solutions before making the final decision. Determine the problem solving model you're going to use to solve the issue.

You can brainstorm with your colleagues and take note of the possible solutions. Let it be an open platform where everyone can air out their views and ideas about the proposed solutions. But this doesn't mean that every solution is applicable.

Determine the effective solution

Once you highlight various scenarios, determine the problem solving techniques and approaches you will use. You do not have to apply every proposed solution. It is best to analyze what you have noted and settle for the best option.

Please choose an alternative that will solve the issue at hand without complicating it further. You only need to be smart and sensible when choosing the best problem solving strategies.

Solve the problem

Now, you already have a solution to the problem, and are ready to make the final decision. Go on and execute. Be patient at this moment as you weigh both sides to see how the involved parties react to the final decision. If you experience a drawback, you can quickly counter it by applying creative tips and remain persistent until you achieve your goals.

Be ready for the outcome

One thing you need to know is that not all decisions end up well with the involved parties. The solution could fail and cause more chaos in the long run. It is imperative to prepare for such outcomes to avoid dilemmas and confusion.

Remember, even if you do not get it right at first, this will be a learning lesson and you can be sure of doing better the next time. However, to avoid such scenarios, prepare adequately to handle the outcome, whether positive or negative. 

Create a follow-up strategy

No matter the outcome, find creative problem solving steps to follow up until you're sure that the problem is entirely resolved. Do not assume that everything is okay, since this could be the beginning of new problems. You can involve your colleagues to offer support until you achieve your goals.

Today, there are more advanced ways of problem solving. Problem-solving software is a crucial tool that will help you solve your issues within a short time and without compromising quality. Check out MindManager to get all the tools you need for collaborative problem solving!

Need to Download MindManager?

Try the full version of mindmanager free for 30 days.

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

Additional menu

The 5 steps of the solving problem process

August 17, 2023 by MindManager Blog

Whether you run a business, manage a team, or work in an industry where change is the norm, it may feel like something is always going wrong. Thankfully, becoming proficient in the problem solving process can alleviate a great deal of the stress that business issues can create.

Understanding the right way to solve problems not only takes the guesswork out of how to deal with difficult, unexpected, or complex situations, it can lead to more effective long-term solutions.

In this article, we’ll walk you through the 5 steps of problem solving, and help you explore a few examples of problem solving scenarios where you can see the problem solving process in action before putting it to work.

Understanding the problem solving process

When something isn’t working, it’s important to understand what’s at the root of the problem so you can fix it and prevent it from happening again. That’s why resolving difficult or complex issues works best when you apply proven business problem solving tools and techniques – from soft skills, to software.

The problem solving process typically includes:

• Pinpointing what’s broken by gathering data and consulting with team members.
• Figuring out why it’s not working by mapping out and troubleshooting the problem.
• Deciding on the most effective way to fix it by brainstorming and then implementing a solution.

While skills like active listening, collaboration, and leadership play an important role in problem solving, tools like visual mapping software make it easier to define and share problem solving objectives, play out various solutions, and even put the best fit to work.

Before you can take your first step toward solving a problem, you need to have a clear idea of what the issue is and the outcome you want to achieve by resolving it.

For example, if your company currently manufactures 50 widgets a day, but you’ve started processing orders for 75 widgets a day, you could simply say you have a production deficit.

However, the problem solving process will prove far more valuable if you define the start and end point by clarifying that production is running short by 25 widgets a day, and you need to increase daily production by 50%.

Once you know where you’re at and where you need to end up, these five steps will take you from Point A to Point B:

• Figure out what’s causing the problem . You may need to gather knowledge and evaluate input from different documents, departments, and personnel to isolate the factors that are contributing to your problem. Knowledge visualization software like MindManager can help.
• Come up with a few viable solutions . Since hitting on exactly the right solution – right away – can be tough, brainstorming with your team and mapping out various scenarios is the best way to move forward. If your first strategy doesn’t pan out, you’ll have others on tap you can turn to.
• Choose the best option . Decision-making skills, and software that lets you lay out process relationships, priorities, and criteria, are invaluable for selecting the most promising solution. Whether it’s you or someone higher up making that choice, it should include weighing costs, time commitments, and any implementation hurdles.
• Put your chosen solution to work . Before implementing your fix of choice, you should make key personnel aware of changes that might affect their daily workflow, and set up benchmarks that will make it easy to see if your solution is working.
• Evaluate your outcome . Now comes the moment of truth: did the solution you implemented solve your problem? Do your benchmarks show you achieved the outcome you wanted? If so, congratulations! If not, you’ll need to tweak your solution to meet your problem solving goal.

In practice, you might not hit a home-run with every solution you execute. But the beauty of a repeatable process like problem solving is that you can carry out steps 4 and 5 again by drawing from the brainstorm options you documented during step 2.

Examples of problem solving scenarios

The best way to get a sense of how the problem solving process works before you try it for yourself is to work through some simple scenarios.

Here are three examples of how you can apply business problem solving techniques to common workplace challenges.

Scenario #1: Manufacturing

Building on our original manufacturing example, you determine that your company is consistently short producing 25 widgets a day and needs to increase daily production by 50%.

Since you’d like to gather data and input from both your manufacturing and sales order departments, you schedule a brainstorming session to discover the root cause of the shortage.

After examining four key production areas – machines, materials, methods, and management – you determine the cause of the problem: the material used to manufacture your widgets can only be fed into your equipment once the machinery warms up to a specific temperature for the day.

Your team comes up with three possible solutions.

• Leave your machinery running 24 hours so it’s always at temperature.
• Invest in equipment that heats up faster.
• Find an alternate material for your widgets.

After weighing the expense of the first two solutions, and conducting some online research, you decide that switching to a comparable but less expensive material that can be worked at a lower temperature is your best option.

You implement your plan, monitor your widget quality and output over the following week, and declare your solution a success when daily production increases by 100%.

Scenario #2: Service Delivery

Business training is booming and you’ve had to onboard new staff over the past month. Now you learn that several clients have expressed concern about the quality of your recent training sessions.

After speaking with both clients and staff, you discover there are actually two distinct factors contributing to your quality problem:

• The additional conference room you’ve leased to accommodate your expanding training sessions has terrible acoustics
• The AV equipment you’ve purchased to accommodate your expanding workforce is on back-order – and your new hires have been making do without

You could look for a new conference room or re-schedule upcoming training sessions until after your new equipment arrives. But your team collaboratively determines that the best way to mitigate both issues at once is by temporarily renting the high-quality sound and visual system they need.

Using benchmarks that include several weeks of feedback from session attendees, and random session spot-checks you conduct personally, you conclude the solution has worked.

Scenario #3: Marketing

You’ve invested heavily in product marketing, but still can’t meet your sales goals. Specifically, you missed your revenue target by 30% last year and would like to meet that same target this year.

After collecting and examining reams of information from your sales and accounting departments, you sit down with your marketing team to figure out what’s hindering your success in the marketplace.

Determining that your product isn’t competitively priced, you map out two viable solutions.

• Hire a third-party specialist to conduct a detailed market analysis.
• Drop the price of your product to undercut competitors.

Since you’re in a hurry for results, you decide to immediately reduce the price of your product and market it accordingly.

When revenue figures for the following quarter show sales have declined even further – and marketing surveys show potential customers are doubting the quality of your product – you revert back to your original pricing, revisit your problem solving process, and implement the market analysis solution instead.

With the valuable information you gain, you finally arrive at just the right product price for your target market and sales begin to pick up. Although you miss your revenue target again this year, you meet it by the second quarter of the following year.

Kickstart your collaborative brainstorming sessions and  try MindManager for free today !

Ready to take the next step?

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

Why choose MindManager?

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

Explore MindManager

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

Integrations

Help articles.

[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

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

Psychology Spot

All About Psychology

The 5 phases of problem solving

Problem solving is a complex psychological process through which we try to find the best way to overcome an obstacle or face a challenge. Unfortunately, this process is not always linear, but can follow tortuous paths, plunging us into a situation of psychological anguish when we believe that there is no possible solution.

On the other hand, knowing the phases of problem solving will save us a lot of headaches. Providing a coherent structure to the situation that concerns us, and having a common thread that guides us along the way, will help us to put some order in the mental chaos that problems usually generate.

To Solve a Problem, Experience Does not Always Work in Our Favor

Experience can be a plus or, on the contrary, become an impediment to solving problems. Psychologists from the universities of Hong Kong and Princeton examined how we implement problem-solving strategies by asking a group of people to solve a series of problems with matches.

Participants were presented with a series of linked squares. Each square in the matrix was made up of separate pieces, and people had to remove a certain number of matches while keeping a specified number of squares intact. The interesting thing about these types of problems is that they generally have more than one solution, different strategies can be used and these must change according to the configuration of the matrix, just as it usually happens with life problems.

These researchers found that participants went through two major stages in problem solving. At first they let themselves be carried away by the perceptual characteristics of the problem and began to explore different strategies, some successful and others not.

In a second moment they used the accumulated experience to narrow their options of strategies, focusing on those that were more successful. The problem is that the more the participants trusted their strategic knowledge, the more difficulties they had in solving problems that demanded the application of novel strategies. In practice, they suffered from a kind of functional fixation.

These series of experiments show us that to solve a problem we must keep an open mind because along the way circumstances are likely to change and we need the mental flexibility necessary to change our problem-solving strategies.

The Stages of Problem Solving We Can All Apply

1. Identify the problem

It may seem like a truism, but the truth is that identifying the real problem is not as easy as it seems, especially when it comes to a situation that affects us emotionally. In fact, when the problem is too scary or we sense that we do not have the psychological tools to solve it, we usually put into practice defense mechanisms such as displacement that allow us to erase the problematic situation from our conscious mind.

Instead, being able to identify the problem is the first step in finding a solution. Many times that means stopping looking outside for the culprits and searching within, wondering why a situation is particularly bothering or hindering us.

2. Understand the problem

Many times the problem brings with it the seed of the solution. So one of the steps in solving a problem is making sure we understand it. It is not enough to identify the problem, we need to define it. For this we need to analyze it from different perspectives.

For example, if we are trying to carry out a professional project that does not finish taking off, we have to clarify the reasons. Do we need more training? Are we in an overly competitive sector? Do we have enough resources? We need to understand the source of the problem.

Organizing the information available is another crucial step in the problem-solving process. We have to ask ourselves both, what we know about the problem and everything we do not know. Ultimately, the accuracy of the solution will largely depend on the amount of information available.

3. Assume a psychological distance

Most of the major problems in life have the potential to generate an emotional tsunami. However, many times that affective involvement obfuscates and prevents us from thinking clearly. That is why on many occasions one of the most important but least known phases for solving problems consists of moving away from what concerns us. To assume a psychological distance , we can take a few days away from the problematic environment or try to stop thinking about what worries us for a while.

During that time the unconscious mind will continue to work and is likely to generate creative and perfectly valid insights that lead to the solution of the problem. That distance to allow us to overcome the functional fixations that prevent us from thinking outside the box, giving way to a mental restructuring that will allow us to see the problem from another perspective.

4. Find solutions and develop strategies

Each problem is different, so it will require a specific solution. A solution cannot always be reached by insight, so it will be necessary to think of possible alternatives to solve the problem. Synectics , for example, is a problem-solving method that uses creativity to find original solutions.

The next step is to develop a strategy, since solutions that do not materialize in concrete steps are very difficult to implement. Therefore, we must ask ourselves how we are going to implement our solution. In this phase of problem solving it is important to be honest with ourselves and “land” that strategy taking into account our resources and real availability. It is useless to develop a great strategy if we cannot apply it later.

5. Evaluation of progress

Very few problems are solved overnight. These are generally complex situations that we must patiently “unwind” over time. Therefore, another of the phases to solve a problem consists of monitoring the results that we are achieving. This way we make sure that we are on the right track and we are not wasting energy and time uselessly.

In this last stage of problem solving it is important to be able to adapt our expectations. It is difficult for a professional project to take off in the blink of an eye, so we must focus on the small steps that indicate that the solution is paying off. To do this, it is important to sit down and reflect on the impact of the solution from time to time.

We must also bear in mind that circumstances often change, so we may need to make adjustments to our initial solution. This requires great mental flexibility to change course when we realize that the strategy is not as effective as we would like.

Fedor, A. et. Al. (2015) Problem solving stages in the five square problem.  Front. Psychol ; 6: 1050.

Louis Lee, N. Y. & Johnson-Laird, P. N. (2013) Strategic changes in problem solving.  Journal of Cognitive Psychology ; 25: 165–173. 

Gillen, G. (2009) Managing Executive Function Impairments to Optimize Function.  Cognitive and Perceptual Rehabilitation ; 245-283.

Jennifer Delgado

I am a psychologist and I spent several years writing articles for scientific journals specialized in Health and Psychology. I want to help you create great experiences. Learn more about me .

If you sleep badly, you will feel bad: How does sleep affect your mood?

17/04/2024 By Jennifer Delgado

Is relationship reconciliation worth it?

Unsung Heroes: The invaluable role of the social worker in mental health

16/04/2024 By Jennifer Delgado

Keep Learning