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

steps to the problem solving process

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

steps to the problem solving process

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

loading

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.

steps to the problem solving process

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.

steps to the problem solving process

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

steps to the problem solving process

Introducing Mind Tools for Business

Mind Tools for Business is a comprehensive library of award-winning performance and management support resources.

Whether you want to increase engagement, upskill teams, or complement your existing workplace programs – this is content designed to achieve impactful results.

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

Most Popular

Newest Releases

Article av8xg61

5 Ways to Build Great Work Relationships

Article ayve4tq

How to Manage Company Growing Pains Using the Greiner Curve Infographic

Mind Tools Store

About Mind Tools Content

Discover something new today

Make change happen with kotter's 8-step change model infographic.

Infographic Transcript

Infographic

Time Management Tips Infographic

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 succeed with continuous improvement: a primer for becoming the best in the world.

Joakim Ahlstrom

Book Insights

Business Operations and Process Management

Strategy Tools

Customer Service

Business Ethics and Values

Handling Information and Data

Project Management

Knowledge Management

Self-Development and Goal Setting

Time Management

Presentation Skills

Learning Skills

Career Skills

Communication Skills

Negotiation, Persuasion and Influence

Working With Others

Difficult Conversations

Creativity Tools

Self-Management

Work-Life Balance

Stress Management and Wellbeing

Coaching and Mentoring

Change Management

Team Management

Managing Conflict

Delegation and Empowerment

Performance Management

Leadership Skills

Developing Your Team

Talent Management

Problem Solving

Decision Making

Status.net

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)

StrategyPunk

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

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

StrategyPunk

StrategyPunk

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

Introduction

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

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

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

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

steps to the problem solving process

Step 1: Define the Problem

The first step in the problem-solving process is to define the problem. This step is crucial because if the problem is not clearly defined, finding a solution won't be easy. The problem must be defined in a specific, measurable, and achievable way.

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

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

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

Step 2: Disaggregate

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

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

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

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

Step 3: Prioritize

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

There are several ways to prioritize issues, including:

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

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

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

Prioritizing issues is a critical step in the problem-solving process. Organizations can allocate resources more effectively and make better decisions by focusing on the most pressing issues.

Step 4: Workplan

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

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

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

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

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

Step 5: Analysis

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

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

  • Root cause analysis
  • Pareto analysis
  • SWOT analysis

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

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

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

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

Step 6: Synthesize

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

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

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

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

Step 7: Communicate

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

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

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

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

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

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

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

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

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

7-Step Problem-Solving Process 

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

steps to the problem solving process

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

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

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

Please buy me a coffee.

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

Buy Me A Coffee

7-Step Problem-Solving Process PDF Template

7-step problem-solving process powerpoint template.

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

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

Strategic Insights 2024: AMD's SWOT Analysis. Free PowerPoint Template reveals key business strategies for AMD. Download now!

ABB SWOT Analysis: Free PPT Template and Insights 2024

ABB SWOT Analysis: Free PPT Template and Insights 2024

Unlock strategic planning success with our Free ABB SWOT Analysis PPT Template 2024. Get comprehensive insights on ABB's business dynamics for a competitive edge.

Retrenchment Strategy Simplified and Explained (Free PDF template)

Retrenchment Strategy Simplified and Explained (Free PDF template)

Unlock the secrets of Retrenchment Strategy with our comprehensive guide. Simplified & Explained, this Free PDF template offers key insights & strategies for effective downsizing. Download now to navigate challenges with confidence.

Fastly SWOT Analysis: Free PPT and In-Depth Insights 2024

Fastly SWOT Analysis: Free PPT and In-Depth Insights 2024

2024 SWOT Analysis of Fastly with free, detailed PPT guide and insights.

What are the 7 Steps to Problem-Solving? & Its Examples

What are the 7 Steps to Problem-Solving & Its Examples (2)-compressed

7 Steps to Problem-Solving

7 Steps to Problem-Solving is a systematic process that involves analyzing a situation, generating possible solutions, and implementing the best course of action. While different problem-solving models exist, a common approach often involves the following seven steps:

Define the Problem:

  • Clearly articulate and understand the nature of the problem. Define the issue, its scope, and its impact on individuals or the organization.

Gather Information:

  • Collect relevant data and information related to the problem. This may involve research, observation, interviews, or any other method to gain a comprehensive understanding.

Generate Possible Solutions:

  • Brainstorm and generate a variety of potential solutions to the problem. Encourage creativity and consider different perspectives during this phase.

Evaluate Options:

  • Assess the strengths and weaknesses of each potential solution. Consider the feasibility, potential risks, and the likely outcomes associated with each option.

Make a Decision:

  • Based on the evaluation, choose the most suitable solution. This decision should align with the goals and values of the individual or organization facing the problem.

Implement the Solution:

  • Put the chosen solution into action. Develop an implementation plan, allocate resources, and carry out the necessary steps to address the problem effectively.

Evaluate the Results:

  • Assess the outcomes of the implemented solution. Did it solve the problem as intended? What can be learned from the process? Use this information to refine future problem-solving efforts.

It’s important to note that these steps are not always linear and may involve iteration. Problem-solving is often an ongoing process, and feedback from the implementation and evaluation stages may lead to adjustments in the chosen solution or the identification of new issues that need to be addressed.

Problem-Solving Example in Education

  • Certainly: Let’s consider a problem-solving example in the context of education.
  • Problem: Declining Student Engagement in Mathematics Classes

Background:

A high school has noticed a decline in student engagement and performance in mathematics classes over the past few years. Students seem disinterested, and there is a noticeable decrease in test scores. The traditional teaching methods are not effectively capturing students’ attention, and there’s a need for innovative solutions to rekindle interest in mathematics.

Steps in Problem-Solving

Identify the problem:.

  • Clearly define the issue: declining student engagement and performance in mathematics classes.
  • Gather data on student performance, attendance, and feedback from teachers and students.

Root Cause Analysis

  • Conduct surveys, interviews, and classroom observations to identify the root causes of disengagement.
  • Identify potential factors such as teaching methods, curriculum relevance, or lack of real-world applications.

Brainstorm Solutions

  • Organize a team of educators, administrators, and even students to brainstorm creative solutions.
  • Consider integrating technology, real-world applications, project-based learning, or other interactive teaching methods.

Evaluate and Prioritize Solutions

  • Evaluate each solution based on feasibility, cost, and potential impact.
  • Prioritize solutions that are likely to address the root causes and have a positive impact on student engagement.

Implement the Chosen Solution

  • Develop an action plan for implementing the chosen solution.
  • Provide training and resources for teachers to adapt to new teaching methods or technologies.

Monitor and Evaluate

  • Continuously monitor the implementation of the solution.
  • Collect feedback from teachers and students to assess the effectiveness of the changes.

Adjust as Needed

  • Be willing to make adjustments based on ongoing feedback and data analysis.
  • Fine-tune the solution to address any unforeseen challenges or issues.

Example Solution

  • Introduce a project-based learning approach in mathematics classes, where students work on real-world problems that require mathematical skills.
  • Incorporate technology, such as educational apps or interactive simulations, to make learning more engaging.
  • Provide professional development for teachers to enhance their skills in implementing these new teaching methods.

Expected Outcomes:

  • Increased student engagement and interest in mathematics.
  • Improvement in test scores and overall academic performance.
  • Positive feedback from both teachers and students.

Final Words

This problem-solving approach in education involves a systematic process of identifying, analyzing, and addressing issues to enhance the learning experience for students.

Leave a Reply Cancel reply

Teach educator.

"Teach Educator" is a dynamic and innovative platform designed to empower educators with the tools and resources they need to excel in their teaching journey. This comprehensive solution goes beyond traditional methods, offering a collaborative space where educators can access cutting-edge teaching techniques, share best practices, and engage in professional development.

Privacy Policy

Live Cricket Score

Recent Post

Formula and Definition of Current Ratio - Latest 2024 (2)-compressed

Formula and Definition of Current Ratio (CR) – Latest 2024

February 24, 2024

Generally Accepted Accounting Principles (GAAP) - Latest (2)-compressed

Generally Accepted Accounting Principles (GAAP) – Latest

What Is CAPM (the Capital Asset Pricing Model) Latest-compressed

What Is CAPM (the Capital Asset Pricing Model)? Latest

Copyright © 2024 Teach Educator

Privacy policy

Discover more from Teach Educator

Subscribe now to keep reading and get access to the full archive.

Type your email…

Continue reading

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

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.

Want better strategies? Become a bulletproof problem solver

Strategy to beat the odds

firo13_frth

Five routes to more innovative problem solving

25 Year Anniversary_logo.png

  • 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

Appreciative Inquiry 4D Cycle

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)

Define, Measure, Analyze, Design, Verify

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

Man Drawing 8 Circles in a Circle

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

Thinking Man

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

Little Girl Reaching For Strawberries On The Counter

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

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)

"Time To Evaluate" Written on a Notepad with Pink Glasses & Pen

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

Execution Etched In to a Gear

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

Man Looking Up at a Success Roadmap

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

Resources | People Working Together At A Large Table With Laptops, Tablets & Paperwork Everywhere

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

Hands Holding Up a Comment Bubble That Says "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

A Drawn Lightbulb Where The Lightbulb is a Crumbled Piece Of Yellow Paper

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

Business Team Looking At Multi-Colored Sticky Notes On A Wall

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

Woman Thinking Against A Yellow Wall

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

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

Additional menu

MindManager Blog

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.

steps to the problem solving process

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

  • Career Advice
  • Five Steps To Create a...

Five Steps To Create a Problem-Solving Process (Plus Tips!)

8 min read · Updated on August 31, 2023

Marsha Hebert

Conquering workplace challenges fuses strategy and art

Sometimes, it can seem that obstacles are as prevalent as opportunities. When you're good at solving problems, though, you have the power to navigate issues with relative ease. In fact, problem solving is more than a skill - it's a tool that you can use to fuel career growth and success. 

As an effective problem solver, you use innovative thinking, demonstrate leadership, and build resilience and confidence. Often, the people you work with come to trust that you're the person to go to when there's a challenge. This could be just the stepping stone you need to move into a leadership role . 

Of course, problems range in complexity depending on your industry. But by having a five-step problem-solving process in place, you can enhance both efficiency and effectiveness. In this article, we'll explore tips to help you master the skill, strategy, and art of problem solving.

Identify, analyze, resolve, execute, evaluate

What's the definition of problem solving? It's quite simple. You have to come up with solutions to challenges or issues. 

The first step to fixing any problem is recognizing that there is one. Then the trick is to engage with each step of the problem-solving process to incorporate analytical thinking , adaptability, and collaboration skills to build a framework for addressing challenges and driving positive outcomes. 

Step 1: Identify

Identifying the problem may be simple, or it could be a detailed cognitive process that breaks the issue into manageable components. Either way, what you do during the identify step of the problem-solving process sets the stage for the next steps in problem solving. 

Step 2: Analyze

Consider underlying factors and devise strategies. Here's where the art part of your problem-solving strategy becomes important. As you gather details about the problem, employ critical thinking to uncover the root causes and potential implications. 

Step 3: Resolve

Once you have a thorough understanding of the issue, it's time to get creative. Develop some reasonable solutions that are aligned with the capabilities of your team and the mission, vision, and values of your company. Your problem-solving method could involve any one of the following - or even a combination of several:

Encourage your team to learn new technologies

Reallocate some resources

Restructure organizational elements

Draft new operating procedures

Implement brainstorming sessions

Develop metrics 

Step 4: Execute

After you've outlined the solutions and decided which ones you think will resolve the problem, it's time to put them into place. The execution phase is the bridge between theory and practice. 

Translate the solutions into actionable steps that produce tangible results

Clearly communicate the actionable steps to the relevant stakeholders - your team, colleagues, or managers

Delegate tasks based on team member acumen

Empower those you delegate tasks to by fostering a sense of ownership

Track the progress of your solutions

Overcome challenges, including unforeseen obstacles and stakeholder resistance

Step 5: Evaluate

Just because you think you solved the problem doesn't mean you actually did. It's critical to double-check your work and make sure there are no hiccups. Here's a list of 10 evaluative questions you can work through, to ensure that your problem-solving solutions were impactful:

Did the solutions effectively address the root cause of the problem?

Do you see the desired results? 

What impact can you see on your team or the company?

Has there been a noticeable enhancement in efficiency, productivity, or overall performance?

Have any unintended consequences or new challenges arisen as a result of the implemented solution?

Can the solution be sustained in the long term, or is it a short-term fix?

Have stakeholders, such as team members or customers, reported positive experiences or feedback?

Have the predefined performance metrics and goals been achieved or exceeded?

Are there any new aspects of the problem that emerged after implementing the solution?

Which aspects of the solution would you retain and which would you modify?

When you reflect on the outcome of your problem solving strategies, you not only validate the effectiveness of your approach but you can also find insights for continuous improvement and refinement for future endeavors. 

Problem solving isn't just for leaders

Sometimes, it seems that only managers and senior executives can engage in effective workplace problem solving. That's simply not the case. It doesn't matter if you're a fresher who's just graduated college or someone with decades of experience, you can employ problem-solving techniques and become a master problem solver. 

You've likely heard of hard skills and soft skills ; you may have even seen problem solving lumped in with other soft skills. There are three essential soft skills you'll need to be good at to solve workplace problems:

Analytical thinking

Adaptability, collaboration.

Let's start with a foundational problem-solving skill. Analytical thinking is something you'll use in every step of your five-step problem-solving process, from identifying the problem to coming up with and executing solutions and measuring the success of those solutions. Being able to analyze trends, anticipate shifts, and make informed decisions along the problem-solving path, you'll be assured of success. 

A real-world example: Sally is a new graduate and has secured her first job. After a few days at work, she wants to start making a name for herself by identifying a dip in sales. She dissects the customer engagement data and finds there has been a shift in consumer preferences. She knows that a new targeted marketing strategy could re-engage customers and bring sales back up. 

Toss aside any notions that the plans you set into place to solve a problem are set in stone. They're not! Being able to make course corrections to change outcomes is at the heart of being adaptable . This soft skill becomes more and more important every day because of how quickly things change in business. Technology advances, economic fluctuations come into play, and unforeseen global events can wreak havoc on the best-laid problem-solving solutions. Think about how adaptable people had to be a few years ago when Covid shut the world down – there were tons of never-before-faced problems that ultimately got solved. 

A real-world example : John has been employed in the technology sector for a little over 20 years. He's achieved the coveted role of CTO and found himself overseeing a team that had to transition into remote work. Because he's kept up with emerging technologies and the latest trends, he sets up processes that allow his team to enjoy a seamless shift with minimal impact on productivity.

When you have a problem-solving project in front of you, you'll often have to get people involved to help you to execute the solutions you come up with. Effective communication , organizational synergy, and a harmonious fusion of experiences can lend fresh insights to problem solving. 

A real-world example: Marcus is involved in a complex project involving supply chain optimization. He works with geographically-dispersed stakeholders of all levels and has become an expert at pooling together specialized knowledge to create holistic solutions. 

How do great problem-solving skills affect your career goals?

Challenges in life and at work are inevitable; by aligning your problem-solving skills with your career goals, not only will you be able to overcome immediate challenges, but you'll also cultivate a powerful tool for your job search toolkit. When you're good at solving problems and can show that you're good at it through accomplishment statements on your resume, your career trajectory will likely be positively impacted. In fact, there are several success stories that prove the journey to excellence is marked by innovative problem solving. Here are just a few:

Elon Musk: Musk's SpaceX faced immense challenges in developing reusable rockets. His innovative, problem-solving approach led to breakthrough solutions, revolutionizing space travel.

Indra Nooyi: As the former CEO of PepsiCo, Nooyi tackled the declining demand for sugary beverages by diversifying the product portfolio and focusing on healthier options, showcasing adaptability and strategic problem solving.

Nelson Mandela: Mandela's ability to collaborate across racial divides and negotiate solutions was instrumental in ending apartheid in South Africa.

Grace Hopper: A computer science pioneer, Hopper's analytical thinking led to the development of the first compiler, revolutionizing programming.

An invaluable asset

As you progress in your career, your skill in resolving a problem will set you apart from the rest of the job-seeking crowd as an invaluable asset. Whether you're identifying opportunities for growth, addressing operational inefficiencies, or strategizing through crises, the ability to solve problems creatively and effectively can become one of the key drivers for the advancement of your career. Essentially, strong problem-solving skills empower you to overcome challenges, seize opportunities, and carve a path of consistent achievement in your professional journey.

TopResume can help you to showcase exceptional problem-solving skills on your resume. Why not submit yours for a free resume review today, to make sure that you're giving this skill the prominence it deserves?

Recommended reading:

How to List Problem Solving Skills on a Resume

Divergent Thinking: Should You Include This Skill on Your Resume?

Higher Order Thinking Explained

Related Articles:

Don't “Snowplow” Your Kids' Job Search — Set Them Up for Success Instead

What Kind of Job Candidate Are You?

Why December is the Best Time of Year to Look for a Job

See how your resume stacks up.

Career Advice Newsletter

Our experts gather the best career & resume tips weekly. Delivered weekly, always free.

Thanks! Career advice is on its way.

Share this article:

Let's stay in touch.

Subscribe today to get job tips and career advice that will come in handy.

Your information is secure. Please read our privacy policy for more information.

Table of Contents

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

What Is Problem Solving? Steps, Techniques, and Best Practices Explained

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

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

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

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

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

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

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

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

1. Precisely Identify Problems

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

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

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

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

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

2. Collect Information and Plan 

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

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

This stage should also include some planning. Ask yourself:

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

Establish a plan and timeline for steps 3-5. 

3. Brainstorm Solutions

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

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

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

Become a Project Management Professional

  • 6% Growth In Jobs Of Project Management Profiles By 2024
  • 22 Million Jobs Estimated For Project Management Professionals By 2027

PMP® Certification Training

Post graduate program in project management.

  • Receive Post Graduate Program Certificate and Alumni Association Membership from UMass Amherst
  • 8X higher live interaction in live online classes by industry experts

Here's what learners are saying regarding our programs:

Katrina Tanchoco

Katrina Tanchoco

Shell - manila ,.

The interactive sessions make a huge difference as I'm able to ask for further clarifications. The training sessions are more engaging than the self-paced modules, it's easier now that i first decided to take up the online classroom training, and then followed it up with the self-paced learning (online and readings).

Nathan C

PHC Business Manager , Midlands and Lancashire Commissioning Support Unit

I wanted to transition into the Project Management field and wanted the right opportunity to do so. Thus, I took that leap forward and enrolled in this course. My learning experience was fantastic. It suited my learning style.

4. Decide and Implement

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

Once you select a course of action, implement it. 

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

5. Evaluate

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

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

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

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

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

Our Quality Management Courses Duration And Fees

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

Get Free Certifications with free video courses

Agile Scrum Master

Agile and Scrum

Agile Scrum Master

PMP Basics

Project Management

Learn from industry experts with free masterclasses.

How to Successfully Ace the PMP Exam on Your First Attempt in 2024

Career Masterclass: How to Successfully Ace the PMP Exam on Your First Attempt in 2024

Career Fast-track

Panel Discussion: The Startup Career Strategy - The Highs and Lows

Recommended Reads

Introduction to Machine Learning: A Beginner's Guide

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

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

Free eBook: 21 Resources to Find the Data You Need

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

Your One-Stop Solution to Understand Coin Change Problem

Get Affiliated Certifications with Live Class programs

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

University Human Resources

8-step problem solving process, organizational effectiveness.

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

Step 1: Define the Problem

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

Step 2: Clarify the Problem

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

Step 3: Define the Goals

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

Step 4: Identify Root Cause of the Problem

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

Step 5: Develop Action Plan

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

Step 6: Execute Action Plan

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

Step 7: Evaluate the Results

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

Step 8: Continuously Improve

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

steps to the problem solving process

The Five-Step Problem-Solving Process

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

The Five Step Problem Solving Process

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

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

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

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

Here are the steps of a problem-solving process:

1. Defining the Problem

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

2. Analyzing the Problem

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

3. Weighing the Options

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

4. Implementing The Best Solution

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

5. Monitoring Progress

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

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

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

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

Thriversitybannersidenav

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

email@milesanthonysmith.com

[email protected]

16 Min Read

steps to the problem solving process

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.

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)

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)

Lean Six Sigma

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.

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.

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.

steps to the problem solving process

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

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

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)

Evaluate and Select Planned Fix

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

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

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

Resources for Problem-Solving

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.

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

Creative Problem Solving

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 .

solving problems in business

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.

think better

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

  • Business strategy |
  • Problem management: 8 steps to better p ...

Problem management: 8 steps to better problem solving

Alicia Raeburn contributor headshot

Problem management is an 8 step framework most commonly used by IT teams. You can use problem management to solve for repeating major incidents. By organizing and structuring your problem solving, you can more effectively get to the root cause of high-impact problems—and devise a solution. Solving the root cause prevents recurrence and creates a repeatable solution to use on similar errors in the future.

In an IT department, errors and mishaps are part of the job. You can't always control these problems, but you can control how you respond to them with problem management. Problem management helps you solve larger problems and reduce the risk that they’ll happen again by identifying all connected problems, solving them, and planning for the future.

What is problem management?

Problem management is an 8 step framework most commonly used by IT teams. Your team can use problem management to solve for repeating major incidents. By organizing and structuring your problem solving, you can more effectively get to the root cause of high-impact problems—and devise a solution. Problem management is a process—used mostly by IT teams—to identify, react, and respond to issues. It’s not for every problem, but it’s a useful response when multiple major incidents occur that cause large work interruptions. Unlike problem solving, problem management goes beyond the initial incident to discover and dissect the root causes, preventing future incidents with permanent solutions.

The goals of problem management are to:

Prevent problems before they start.

Solve for repetitive errors.

Lessen each incident’s impact. 

Problem management vs. incident management 

Example: Someone leaves their unprotected laptop in a coffee shop, causing a security breach. The security team can use incident management to solve for this one, isolated event. In this case, the team could manually shut down the accounts connected to that laptop. If this continues to happen, IT would use problem management to solve the root of this issue—perhaps installing more security features on each company laptop so that if employees lose them, no one else can access the information.

Problem management vs. problem solving

While similar in name, problem management differs slightly from problem-solving. Problem management focuses on every aspect of the incident—identifying the root cause of the problem, solving it, and prevention. Problem solving is, as the name implies, focused solely on the solution step. 

Example: You’re launching a new password management system when it crashes—again. You don’t know if anything leaked, but you know it could contain confidential information. Plus, it’s happened before. You start the problem management process to ensure it doesn’t happen again. In that process, you’ll use problem solving as a step to fix the issue. In this case, perhaps securing confidential information before you try to launch a new software.

Problem management vs. change management 

Change management targets large transitions within your workplace, good and bad. These inevitable changes aren’t always negative, so you can’t always apply problem management as a solution. That’s where change management comes in—a framework that helps you adjust to any new scenario.

Example: Your company is transitioning to a new cloud platform. The transition happens incident-free—meaning you won’t need problem management—but you can ease the transition by implementing some change management best practices. Preparing and training team members in the new software is a good place to start.

Problem management vs. project management

Project management is the framework for larger collections of work. It’s the overarching method for how you work on any project, hit goals, and get results. You can use project management to help you with problem management, but they are not the same thing. Problem management and project management work together to solve issues as part of your problem management process.

Example: During problem management, you uncover a backend security issue that needs to be addressed—employees are using storage software with outdated security measures. To solve this, you create a project and outline the tasks from start to finish. In this case, you might need to alert senior executives, get approval to remove the software, and alert employees. You create a project schedule with a defined timeline and assign the tasks to relevant teams. In this process, you identified a desired outcome—remove the unsafe software—and solved it. That’s project management.

The 8 steps of problem management

It’s easy to get upset when problems occur. In fact, it’s totally normal. But an emotional response is not always the best response when faced with new incidents. Having a reliable system—such as problem management—removes the temptation to respond emotionally. Proactive project management gives your team a framework for problem solving. It’s an iterative process —the more you use it, the more likely you are to have fewer problems, faster response times, and better outputs. 

1. Identify the problem

During problem identification, you’re looking at the present—what’s happening right now? Here, you’ll define what the incident is and its scale. Is this a small, quick-fix, or a full overhaul? Consider using problem framing to define, prioritize, and understand the obstacles involved with these more complex problems. 

2. Diagnose the cause

Use problem analysis or root cause analysis to strategically look at the cause of a problem. Follow the trail of issues all the way back to its beginnings.

To diagnose the underlying cause, you’ll want to answer:

What factors or conditions led to the incident?

Do you see related incidents? Could those be coming from the same source?

Did someone miss a step? Are processes responsible for this problem?

3. Organize and prioritize

Now it’s time to build out your framework. Use an IT project plan to organize information in a space where everyone can make and see updates in real time. The easiest way to do this is with a project management tool where you can input ‌tasks, assign deadlines, and add dependencies to ensure nothing gets missed. To better organize your process, define:

What needs to be done? 

Who’s responsible for each aspect? If no one is, can we assign someone? 

When does each piece need to be completed?

What is the final number of incidents related to this problem?

Are any of these tasks dependent on another one? Do you need to set up dependencies ?

What are your highest priorities? How do they affect our larger business goals ? 

How should you plan for this in the future?

4. Create a workaround

If the incident has stopped work or altered it, you might need to create a workaround. This is not always necessary, but temporary workarounds can keep work on track and avoid backlog while you go through the problem management steps. When these workarounds are especially effective, you can make them permanent processes.

5. Update your known error database

Every time an incident occurs, create a known error record and add it to your known error database (KEDB). Recording incidents helps you catch recurrences and logs the solution, so you know how to solve similar errors in the future. 

[product ui] Incident log example (lists)

6. Pause for change management (if necessary)

Larger, high-impact problems might require change management. For example, if you realize the problem’s root cause is a lack of staff, you might dedicate team members to help. You can use change management to help them transition their responsibilities, see how these new roles fit in with the entire team, and determine how they will collaborate moving forward.

7. Solve the problem

This is the fun part—you get to resolve problems. At this stage, you should know exactly what you’re dealing with and the steps you need to take. But remember—with problem management, it’s not enough to solve the current problem. You’ll want to take any steps to prevent this from happening again in the future. That could mean hiring a new role to cover gaps in workflows , investing in new softwares and tools, or training staff on best practices to prevent these types of incidents.

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

8. Reflect on the process

The problem management process has the added benefit of recording the process in its entirety, so you can review it in the future. Once you’ve solved the problem, take the time to review each step and reflect on the lessons learned during this process. Make note of who was involved, what you needed, and any opportunities to improve your response to the next incident. After you go through the problem management process a few times and understand the basic steps, stakeholders, workload, and resources you need, create a template to make the kickoff process easier in the future.

5 benefits of problem management

Problem management helps you discover every piece of the problem—from the current scenario down to its root cause. Not only does this have an immediate positive impact on the current issue at hand, it also promotes collaboration and helps to build a better product overall. 

Here are five other ways ‌problem management can benefit your team:

Avoids repeat incidents. When you manage the entire incident from start to finish, you will address the foundational problems that caused it. This leads to fewer repeat incidents.

Boosts cross-functional collaboration. Problem management is a collaborative process. One incident might require collaboration from IT, the security team, and legal. Depending on the level of the problem, it might trickle all the way back down to the product or service team, where core changes need to be made.

Creates a better user experience. It’s simple—the fewer incidents you have, the better your customer’s experience will be. Reducing incidents means fewer delays, downtime, and frustrations for your users, and a higher rate of customer satisfaction.

Improves response time. As you develop a flow and framework with a project management process, you’ll be better equipped to handle future incidents—even if they’re different scenarios.

Organizes problem solving. Problem management provides a structured, thoughtful approach to solving problems. This reduces impulsive responses and helps you keep a better problem record of incidents and solutions.

Problem management leads to better, faster solutions

IT teams will always have to deal with incidents, but they don’t have to be bogged down by them. That’s because problem management works. Whether you employ a full problem management team or choose to apply these practices to your current IT infrastructure, problem management—especially when combined with a project management tool—saves you time and effort down the road.

With IT project plans, we’ve made it easier than ever to track your problem management work in a shared tool. Try our free IT project template to see your work come together, effortlessly.

Related resources

steps to the problem solving process

Business impact analysis: 4 steps to prepare for anything

steps to the problem solving process

The beginner’s guide to business process management (BPM)

steps to the problem solving process

Project portfolio management 101

steps to the problem solving process

Marketing campaign management: 7 steps for success

Humor That Works

The 5 Steps of Problem Solving

5-steps-of-problem-solving-humor-that-works-3

Problem solving is a critical skill for success in business – in fact it’s often what you are hired and paid to do. This article explains the five problem solving steps and provides strategies on how to execute each one.

Defining Problem Solving

Before we talk about the stages of problem solving, it’s important to have a definition of what it is. Let’s look at the two roots of problem solving — problems and solutions.

Problem – a state of desire for reaching a definite goal from a present condition [1] Solution – the management of a problem in a way that successfully meets the goals set for treating it

[1] Problem solving on Wikipedia

One important call-out is the importance of having a goal. As defined above, the solution may not completely solve problem, but it does meet the goals you establish for treating it–you may not be able to completely resolve the problem (end world hunger), but you can have a goal to help it (reduce the number of starving children by 10%).

The Five Steps of Problem Solving

With that understanding of problem solving, let’s talk about the steps that can get you there. The five problem solving steps are shown in the chart below:

problem solving steps

However this chart as is a little misleading. Not all problems follow these steps linearly, especially for very challenging problems. Instead, you’ll likely move back and forth between the steps as you continue to work on the problem, as shown below:

problem solving steps iterative

Let’s explore of these steps in more detail, understanding what it is and the inputs and outputs of each phase.

1. Define the Problem

aka What are you trying to solve? In addition to getting clear on what the problem is, defining the problem also establishes a goal for what you want to achieve.

Input:  something is wrong or something could be improved. Output: a clear definition of the opportunity and a goal for fixing it.

2. Brainstorm Ideas

aka What are some ways to solve the problem? The goal is to create a list of possible solutions to choose from. The harder the problem, the more solutions you may need.

Input: a goal; research of the problem and possible solutions; imagination. Output: pick-list of possible solutions that would achieve the stated goal.

3. Decide on a Solution

aka What are you going to do? The ideal solution is effective (it will meet the goal), efficient (is affordable), and has the fewest side effects (limited consequences from implementation).

Input:  pick-list of possible solutions; decision-making criteria. Output: decision of what solution you will implement.

4. Implement the Solution

aka What are you doing? The implementation of a solution requires planning and execution. It’s often iterative, where the focus should be on short implementation cycles with testing and feedback, not trying to get it “perfect” the first time.

Input:  decision; planning; hard work. Output:  resolution to the problem.

5. Review the Results

aka What did you do? To know you successfully solved the problem, it’s important to review what worked, what didn’t and what impact the solution had. It also helps you improve long-term problem solving skills and keeps you from re-inventing the wheel.

Input:  resolutions; results of the implementation. Output: insights; case-studies; bullets on your resume.

Improving Problem Solving Skills

Once you understand the five steps of problem solving, you can build your skill level in each one. Often we’re naturally good at a couple of the phases and not as naturally good at others. Some people are great at generating ideas but struggle implementing them. Other people have great execution skills but can’t make decisions on which solutions to use. Knowing the different problem solving steps allows you to work on your weak areas, or team-up with someone who’s strengths complement yours.

Want to improve your problem solving skills? Want to perfect the art of problem solving?  Check out our training programs or try these 20 problem solving activities to improve creativity .

THIS FREE 129 SECOND QUIZ WILL SHOW YOU

what is your humor persona?

Humor is a skill that can be learned. And when used correctly, it is a superpower that can be your greatest asset for building a happier, healthier and more productive life.  See for yourself...

you might also be interested in...

humor awards banner

Nominations open for 2021 Corporate Humor Awards

Nominations are still open for the 2021 Corporate Humor Awards! Nominate an individual or organization that is helping to keep […]

tedx-tamu-andrew-tarvin

The Skill of Humor TEDx talk – Develop your Humor Skills

We are excited to announce that Drew’s second TEDx talk on The Skill of Humor is now available online. This […]

Create Your Own Humor Awards!

Want to host your own version of the Corporate Humor Awards? Check out this free download from Humor That Works: […]

22 thoughts on “The 5 Steps of Problem Solving”

steps to the problem solving process

very helpful and informative training

steps to the problem solving process

Thank you for the information

steps to the problem solving process

YOU ARE AFOOL

steps to the problem solving process

I’m writing my 7th edition of Effective Security Management. I would like to use your circular graphic illustration in a new chapter on problem solving. You’re welcome to phone me at — with attribution.

steps to the problem solving process

Sure thing, shoot us an email at [email protected] .

steps to the problem solving process

i love your presentation. It’s very clear. I think I would use it in teaching my class problem solving procedures. Thank you

steps to the problem solving process

It is well defined steps, thank you.

steps to the problem solving process

these step can you email them to me so I can print them out these steps are very helpful

steps to the problem solving process

I like the content of this article, it is really helpful. I would like to know much on how PAID process (i.e. Problem statement, Analyze the problem, Identify likely causes, and Define the actual causes) works in Problem Solving.

steps to the problem solving process

very useful information on problem solving process.Thank you for the update.

Pingback: Let’s Look at Work Is Working with the Environment | #EnviroSociety

steps to the problem solving process

It makes sense that a business would want to have an effective problem solving strategy. Things could get bad if they can’t find solutions! I think one of the most important things about problem solving is communication.

steps to the problem solving process

Well in our school teacher teach us –

1) problem ldentification 2) structuring the problem 3) looking for possible solutions 4) lmplementation 5) monitoring or seeking feedback 6) decision making

Pleace write about it …

steps to the problem solving process

I teach Professional communication (Speech) and I find the 5 steps to problem solving as described here the best method. Your teacher actually uses 4 steps. The Feedback and decision making are follow up to the actual implementation and solving of the problem.

steps to the problem solving process

i know the steps of doing some guideline for problem solving

steps to the problem solving process

steps are very useful to solve my problem

steps to the problem solving process

The steps given are very effective. Thank you for the wonderful presentation of the cycle/steps/procedure and their connections.

steps to the problem solving process

I like the steps for problem solving

steps to the problem solving process

It is very useful for solving difficult problem i would reccomend it to a friend

steps to the problem solving process

this is very interesting because once u have learned you will always differentiate the right from the wrong.

steps to the problem solving process

I like the contents of the problem solving steps. informative.

Leave a Comment Cancel Reply

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

Humor Persona - Main B2C

I make an effort to appreciate the humor of everyday life....

This question helps us further the advancement of humor research to make it more equitable.

Humor Persona - Template B2B

5 Steps to Make your Problem-Solving Process Easier

No matter what kind of job you have, the chances of a problem arising at some point is almost inevitable. If the problem isn’t taken care of immediately with proper action, it could potentially get worse. No one wants to be in a hostile work environment, so it’s crucial to be aware of how to properly solve an issue.

What is Problem Solving?

Before we can even begin to explain what problem-solving is, we need to define what a problem is. A problem is any type of disturbance from normality that is hindering progress. A problem can be time-consuming and energy wasting. They can be as little as a disagreement, to as big as a miscommunication that costs millions of dollars to fix.

One problem-solving technique is determining whether it prevents you from reaching your goal. No matter the issue’s size, it can be solved by identifying it, gathering possible solutions, choosing the best possible one, and implementing it. That’s commonly known as the problem-solving process. If a company neglects any problems in the workplace, they could potentially get worse and cause significant problems.

Problem-solving can be the difference between a business succeeding or failing. According to Forbes.com , some common barriers that will prevent companies from being successful problem-solvers include the inability to see a problem, lack of respect, and failure to include all parts involved with the problem, among others.

Problem-solvers need some specific skills, like being able to do research and make both rational and emotionally intelligent decisions. Risk management is another skill that’s imperative to making a successful decision. Your team should all be able to work together in the problem-solving process.

In fact, in 2013, the Association of American Colleges and Universities released a report claiming that 93 percent of employers agree, “a candidate’s demonstrated capacity to think critically, communicate clearly, and solve complex problems is more important than their undergraduate major.”

Here are a few more problem-solving skills:

  • Team building
  • Effective communication
  • Active listening
  • Brainstorming

There are many benefits to problem-solving in an organization. For one thing, it creates a hostility-free environment that encourages everyone to speak their mind when a problem occurs. Resolving problems together as a team can foster team building. Problem-solving can also empower a workforce and make its members more confident. If an entire organization can problem-solve efficiently, they can spend their time more wisely.

5 Steps to Better Problem-Solving

Step 1: identify the problem.

As obvious as it may sound, the first step in the problem-solving process is to identify the root of the issue. However, the problem isn’t always easily identifiable and might require some extra analysis to get the source. One way you can identify a problem is by using Toyota’s “Five Whys” technique . In the event of a problem, ask yourself the five whys:

By asking yourself these questions, you’ll discover where the problem is coming from. If that isn’t enough, here are three steps you can take to better identify a problem:

Explore the situation : Expand on the problem to try to get to the bottom of it. If an individual is the problem’s source, try putting yourself in their shoes.

Draft a problem statement : Reduce the problem into the simplest of terms and put it down on paper. This can help you gather and organize your thoughts.

Try to answer the question : “Why is this current situation a problem?” Once you’ve boiled it down to one source, you’ll be able to better assess the situation.

Let’s use a coffee shop as an example. Say the coffee shop has slowly been losing business in the last quarter, despite being very successful in the past few months. The owner wants to better understand why they’re suddenly losing business.

First, they explore the situation and look at all the possible reasons for why this is happening. They look at their employees, their daily routines, and training procedures. They also observe the local competition and the regional factors, like the fact that they’re located in a college town.

After looking at every single possible reason, the owner figures out what’s causing the problem and writes it down: It’s the summer and most of their student clientele are away for the summer. Finally, the owner answers the question, “Why is this current situation a problem?” Then after further evaluation, they realize the problem is a limited market and that they must expand to get more business.

Step 2: Generate Potential Solutions

The next step is to create a list of possible solutions. Start by brainstorming some potential answers, either individually or in a group setting. The latter is recommended, because when you have more input, you get more perspectives that can lead to unique solutions.

Here are some other methods to create solutions:

Means-End Analysis : An artificial intelligence analysis that finds the best possible way of attaining a goal.

Plan Do Study Act Model : Also known as the PDSA Model. This is the shorthand version of the problem-solving method, where you start with planning, test the theory, study the results, and act based upon observations . This process is done several times.

Root Cause Analysis : This method is used to get to the root of the problem. Its four steps are to identify the problem, establish a timeline, distinguish between root causes and other factors, and create a cause graph.

Lean Prioritization Method : This method is created within a two-by-two matrix, with the X and Y-axis ranging from low to high. The X-axis is labeled as “effort”, while the Y-axis is labeled “value.” Inside the matrix, label the four squares with:

  • And time sinks

Evaluate the problems and situations and put them in the appropriate categories to figure out where to focus your attention.

Step 3: Choose One Solution

Once a list of possible solutions has been made, it’s time to put your decision-making skills to the test. To find the best solution for the problem, analyze every possible resolution and decide which is best for your situation.

Before making a decision, consider the potential solution’s efficacy, practicality, timeliness, resources, and cost. Narrow your choices down with the process of elimination and with a risk manager’s input. Like brainstorming, choosing a solution doesn’t have to be done alone.

Step 4: Implement the Solution You’ve Chosen

Now that you’ve chosen a solution, it’s time to implement it throughout the necessary departments, areas, or people. On average, it takes about 66 days for a new habit to become automatic, according to a study published in the European Journal of Social Psychology. In other words, change doesn’t happen overnight. To make a new change to any business, planning, patience, and persistence are all required.

Planning : Timing is everything. When a company implements a new strategy, they often take a lot of time to implement the new idea. Decide on clear goals, address any issues or possible obstacles, and create a plan. It’s also critical to practice proper communication skills across the entire organization so that everyone knows what’s expected.

Patience : Change is scary and not everyone is going to accept it, that’s why it’s important to stay patient throughout this process. Try implementing the plan little by little so that employees aren’t overwhelmed. Encourage each other and make sure everyone understands the intention behind this change, and that everyone is participating in making it possible.

Persistence : Continuous application and monitoring of these changes are crucial. Make sure all of your employees are practicing the changes every week so they become the norm.

Step 5: Evaluate Results

The final part of the problem-solving process is to analyze the results. This can be done after a couple of weeks, months, or years, depending on what you’re trying to achieve. It’s important to remember why this problem started in the first place and how it affected the company. Ask yourself any of the following questions to better evaluate results:

  • Are any of our processes being interrupted by the previous problem?
  • Have any new problems arisen since we started this process?
  • Is there a possibility the issue can return?
  • Is everyone aware of the original problem, the solution created, and why it was created?
  • Do you need to change any policy, procedure, or personnel to avoid this from happening again?

Sometimes, it’s necessary to start the process completely over. To make the problem-solving process easier, it’s best to simplify the solution as much as possible. Try to focus on the solution rather than the problem. Be positive, open-minded, and willing to make the change. With enough practice, any problem can be solved.

Problems will always occur no matter what situation you’re in, so it’s important to know how to conquer them before they get out of hand. Do you want to learn more about the process of problem-solving and how you can apply it to fix your company’s issues?

You can learn about different strategies that will help alleviate any workplace problems in KnowledgeCity’s course on Problem Solving in 5 Easy Steps . Use this information to take control of any problems that crop up at work.

steps to the problem solving process

  • About the author
  • Latest posts

steps to the problem solving process

Thanks for this terrific article! I am a mentor to undergraduate students and I was researching problem solving philosophies, methodologies, and techniques. This was a perfect resource! I like the way that you provided practical examples and also provided various methodologies and systems for problem solving. I think that’s always good to provide people options as certain methodologies may be best geared for certain disciplines, industries, or situations.

I took special note of these key quotes:

“because the more input, the better, simply because different perspectives can lead to different solutions.”

“It’s important to remember why this problem started in the first place and how it was affecting the company.”

Thanks again for making this great information publicly available.

Clifford Thornton

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

Join 80,000+ Fellow HR Professionals. Get expert recruiting and training tips straight to your inbox, and become a better HR manager.

COMMENTS

  1. What is Problem Solving? Steps, Process & Techniques

    Helpful problem-solving techniques include using flowcharts to identify the expected steps of a process and cause-and-effect diagrams to define and analyze root causes. The sections below help explain key problem-solving steps.

  2. The Problem-Solving Process

    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.

  3. The Problem-Solving Process

    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.

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

    The problem-solving process typically includes the following steps: Identify the issue: Recognize the problem that needs to be solved. Analyze the situation: Examine the issue in depth, gather all relevant information, and consider any limitations or constraints that may be present.

  5. Master the 7-Step Problem-Solving Process for Better ...

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

  6. What are the 7 Steps to Problem-Solving? & Its Examples

    7 Steps to Problem-Solving. 7 Steps to Problem-Solving is a systematic process that involves analyzing a situation, generating possible solutions, and implementing the best course of action.While different problem-solving models exist, a common approach often involves the following seven steps:

  7. How to master the seven-step problem-solving process

    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.

  8. The Ultimate Problem-Solving Process Guide: 31 Steps & Resources

    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.

  9. The 5 steps of the solving problem process

    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.

  10. Five Steps To Create a Problem-Solving Process (Plus Tips!)

    Step 1: Identify. Identifying the problem may be simple, or it could be a detailed cognitive process that breaks the issue into manageable components. Either way, what you do during the identify step of the problem-solving process sets the stage for the next steps in problem solving.

  11. What Is Problem Solving? Steps, Techniques, and Best ...

    1. Precisely Identify Problems As obvious as it seems, identifying the problem is the first step in the problem-solving process. Pinpointing a problem at the beginning of the process will guide your research, collaboration, and solutions in the right direction. At this stage, your task is to identify the scope and substance of the problem.

  12. 8-Step Problem Solving Process

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

  13. 5 Steps (And 4 Techniques) for Effective Problem Solving

    1. Define the Problem You must define and understand the problem before you start, whether you're solving it independently or as a group. If you don't have a single view of what the problem is, you could be fixing something that doesn't need fixing, or you'll fix the wrong problem.

  14. PDF Step Problem Solving Process

    Step One: Define the Problem Step One is about diagnosing the problem - the context, background and symptoms of the issue. Once the group has a clear grasp of what the problem is, they investigate the wider symptoms to discover the implications of the problem, who it affects, and how urgent/important it is to resolve the symptoms.

  15. The Eight-Step Process for Solving Problems: A Complete Guide

    The 8-step problem-solving process is a powerful tool for tackling complex problems and driving organizational success. By following each step in a systematic and structured manner, you can define ...

  16. 5 Step Problem Solving Process

    Here are the steps of a problem-solving process: 1. Defining the Problem The first step in the process is often overlooked. To define the problem is to understand what it is that you're solving for. This is also where you outline and write down your purpose—what you want to achieve and why.

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

    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.

  18. Problem management: 8 steps to better problem solving

    Problem management is an 8 step framework most commonly used by IT teams. Your team can use problem management to solve for repeating major incidents. By organizing and structuring your problem solving, you can more effectively get to the root cause of high-impact problems—and devise a solution. Problem management is a process—used mostly ...

  19. How To Put Problem-Solving Skills To Work in 6 Steps

    Here are the basic steps involved in problem-solving: 1. Define the problem The first step is to analyze the situation carefully to learn more about the problem. A single situation may solve multiple problems. Identify each problem and determine its cause. Try to anticipate the behavior and response of those affected by the problem.

  20. The 10-Step Problem-Solving Process to Solve Any Problem

    Problems are a fact of life and being effective at problem-solving can help you grow and find success in life. http://bit.ly/3XcDi9xLearn how to implement S...

  21. The easy 4 step problem-solving process (+ examples)

    Step 1: What's the problem? Step 2: What do you need to know? Step 3: What do you already know? Step 4: What's the relationship between the two? A recap of the 4 steps of the simple problem-solving process Every problem may be different, but effective problem solving asks the same four questions and follows the same method. What's the problem?

  22. The 5 Steps of Problem Solving

    The implementation of a solution requires planning and execution. It's often iterative, where the focus should be on short implementation cycles with testing and feedback, not trying to get it "perfect" the first time. Input: decision; planning; hard work. Output: resolution to the problem. 5.

  23. 5 Steps to Make your Problem-Solving Process Easier

    Step 1: Identify the Problem. As obvious as it may sound, the first step in the problem-solving process is to identify the root of the issue. However, the problem isn't always easily identifiable and might require some extra analysis to get the source. One way you can identify a problem is by using Toyota's "Five Whys" technique.

  24. How to Document the Problem-Solving Process with Clients

    The first step for documenting the problem-solving process is to clearly define the problem that you are trying to solve. This involves gathering relevant information from your client, such as ...

  25. Dr Punam Krishan on Instagram: "One of the worst jobs of being a doctor

    drpunamkrishan on February 21, 2024: "One of the worst jobs of being a doctor is breaking bad news to a patient. After nearly 20 years ..."