example of 4 step problem solving

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)

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

selected template will load here

This action is not available.

10.1: George Polya's Four Step Problem Solving Process

• Last updated
• Save as PDF
• Page ID 72365

Step 1: Understand the Problem

• Do you understand all the words?
• Can you restate the problem in your own words?
• Do you know what is given?
• Do you know what the goal is?
• Is there enough information?
• Is there extraneous information?
• Is this problem similar to another problem you have solved?

Step 2: Devise a Plan: Below are some strategies one might use to solve a problem. Can one (or more) of the following strategies be used? (A strategy is defined as an artful means to an end.)

• The Art of Effective Problem Solving: A Step-by-Step Guide
• Learn Lean Sigma
• Problem Solving

Whether we realise it or not, problem solving skills are an important part of our daily lives. From resolving a minor annoyance at home to tackling complex business challenges at work, our ability to solve problems has a significant impact on our success and happiness. However, not everyone is naturally gifted at problem-solving, and even those who are can always improve their skills. In this blog post, we will go over the art of effective problem-solving step by step.

You will learn how to define a problem, gather information, assess alternatives, and implement a solution, all while honing your critical thinking and creative problem-solving skills. Whether you’re a seasoned problem solver or just getting started, this guide will arm you with the knowledge and tools you need to face any challenge with confidence. So let’s get started!

Table of Contents

Problem solving methodologies.

Individuals and organisations can use a variety of problem-solving methodologies to address complex challenges. 8D and A3 problem solving techniques are two popular methodologies in the Lean Six Sigma framework.

Methodology of 8D (Eight Discipline) Problem Solving:

The 8D problem solving methodology is a systematic, team-based approach to problem solving. It is a method that guides a team through eight distinct steps to solve a problem in a systematic and comprehensive manner.

The 8D process consists of the following steps:

• Form a team: Assemble a group of people who have the necessary expertise to work on the problem.
• Define the issue: Clearly identify and define the problem, including the root cause and the customer impact.
• Create a temporary containment plan: Put in place a plan to lessen the impact of the problem until a permanent solution can be found.
• Identify the root cause: To identify the underlying causes of the problem, use root cause analysis techniques such as Fishbone diagrams and Pareto charts.
• Create and test long-term corrective actions: Create and test a long-term solution to eliminate the root cause of the problem.
• Implement and validate the permanent solution: Implement and validate the permanent solution’s effectiveness.
• Prevent recurrence: Put in place measures to keep the problem from recurring.
• Recognize and reward the team: Recognize and reward the team for its efforts.

Download the 8D Problem Solving Template

A3 Problem Solving Method:

The A3 problem solving technique is a visual, team-based problem-solving approach that is frequently used in Lean Six Sigma projects. The A3 report is a one-page document that clearly and concisely outlines the problem, root cause analysis, and proposed solution.

The A3 problem-solving procedure consists of the following steps:

• Determine the issue: Define the issue clearly, including its impact on the customer.
• Perform root cause analysis: Identify the underlying causes of the problem using root cause analysis techniques.
• Create and implement a solution: Create and implement a solution that addresses the problem’s root cause.
• Monitor and improve the solution: Keep an eye on the solution’s effectiveness and make any necessary changes.

Subsequently, in the Lean Six Sigma framework, the 8D and A3 problem solving methodologies are two popular approaches to problem solving. Both methodologies provide a structured, team-based problem-solving approach that guides individuals through a comprehensive and systematic process of identifying, analysing, and resolving problems in an effective and efficient manner.

Step 1 – Define the Problem

The definition of the problem is the first step in effective problem solving. This may appear to be a simple task, but it is actually quite difficult. This is because problems are frequently complex and multi-layered, making it easy to confuse symptoms with the underlying cause. To avoid this pitfall, it is critical to thoroughly understand the problem.

To begin, ask yourself some clarifying questions:

• What exactly is the issue?
• What are the problem’s symptoms or consequences?
• Who or what is impacted by the issue?
• When and where does the issue arise?

Answering these questions will assist you in determining the scope of the problem. However, simply describing the problem is not always sufficient; you must also identify the root cause. The root cause is the underlying cause of the problem and is usually the key to resolving it permanently.

Try asking “why” questions to find the root cause:

• What causes the problem?
• Why does it continue?
• Why does it have the effects that it does?

By repeatedly asking “ why ,” you’ll eventually get to the bottom of the problem. This is an important step in the problem-solving process because it ensures that you’re dealing with the root cause rather than just the symptoms.

Once you have a firm grasp on the issue, it is time to divide it into smaller, more manageable chunks. This makes tackling the problem easier and reduces the risk of becoming overwhelmed. For example, if you’re attempting to solve a complex business problem, you might divide it into smaller components like market research, product development, and sales strategies.

To summarise step 1, defining the problem is an important first step in effective problem-solving. You will be able to identify the root cause and break it down into manageable parts if you take the time to thoroughly understand the problem. This will prepare you for the next step in the problem-solving process, which is gathering information and brainstorming ideas.

Step 2 – Gather Information and Brainstorm Ideas

Gathering information and brainstorming ideas is the next step in effective problem solving. This entails researching the problem and relevant information, collaborating with others, and coming up with a variety of potential solutions. This increases your chances of finding the best solution to the problem.

Begin by researching the problem and relevant information. This could include reading articles, conducting surveys, or consulting with experts. The goal is to collect as much information as possible in order to better understand the problem and possible solutions.

Next, work with others to gather a variety of perspectives. Brainstorming with others can be an excellent way to come up with new and creative ideas. Encourage everyone to share their thoughts and ideas when working in a group, and make an effort to actively listen to what others have to say. Be open to new and unconventional ideas and resist the urge to dismiss them too quickly.

Finally, use brainstorming to generate a wide range of potential solutions. This is the place where you can let your imagination run wild. At this stage, don’t worry about the feasibility or practicality of the solutions; instead, focus on generating as many ideas as possible. Write down everything that comes to mind, no matter how ridiculous or unusual it may appear. This can be done individually or in groups.

Once you’ve compiled a list of potential solutions, it’s time to assess them and select the best one. This is the next step in the problem-solving process, which we’ll go over in greater detail in the following section.

Step 3 – Evaluate Options and Choose the Best Solution

Once you’ve compiled a list of potential solutions, it’s time to assess them and select the best one. This is the third step in effective problem solving, and it entails weighing the advantages and disadvantages of each solution, considering their feasibility and practicability, and selecting the solution that is most likely to solve the problem effectively.

To begin, weigh the advantages and disadvantages of each solution. This will assist you in determining the potential outcomes of each solution and deciding which is the best option. For example, a quick and easy solution may not be the most effective in the long run, whereas a more complex and time-consuming solution may be more effective in solving the problem in the long run.

Consider each solution’s feasibility and practicability. Consider the following:

• Can the solution be implemented within the available resources, time, and budget?
• What are the possible barriers to implementing the solution?
• Is the solution feasible in today’s political, economic, and social environment?

You’ll be able to tell which solutions are likely to succeed and which aren’t by assessing their feasibility and practicability.

Finally, choose the solution that is most likely to effectively solve the problem. This solution should be based on the criteria you’ve established, such as the advantages and disadvantages of each solution, their feasibility and practicability, and your overall goals.

It is critical to remember that there is no one-size-fits-all solution to problems. What is effective for one person or situation may not be effective for another. This is why it is critical to consider a wide range of solutions and evaluate each one based on its ability to effectively solve the problem.

Step 4 – Implement and Monitor the Solution

When you’ve decided on the best solution, it’s time to put it into action. The fourth and final step in effective problem solving is to put the solution into action, monitor its progress, and make any necessary adjustments.

To begin, implement the solution. This may entail delegating tasks, developing a strategy, and allocating resources. Ascertain that everyone involved understands their role and responsibilities in the solution’s implementation.

Next, keep an eye on the solution’s progress. This may entail scheduling regular check-ins, tracking metrics, and soliciting feedback from others. You will be able to identify any potential roadblocks and make any necessary adjustments in a timely manner if you monitor the progress of the solution.

Finally, make any necessary modifications to the solution. This could entail changing the solution, altering the plan of action, or delegating different tasks. Be willing to make changes if they will improve the solution or help it solve the problem more effectively.

It’s important to remember that problem solving is an iterative process, and there may be times when you need to start from scratch. This is especially true if the initial solution does not effectively solve the problem. In these situations, it’s critical to be adaptable and flexible and to keep trying new solutions until you find the one that works best.

To summarise, effective problem solving is a critical skill that can assist individuals and organisations in overcoming challenges and achieving their objectives. Effective problem solving consists of four key steps: defining the problem, generating potential solutions, evaluating alternatives and selecting the best solution, and implementing the solution.

You can increase your chances of success in problem solving by following these steps and considering factors such as the pros and cons of each solution, their feasibility and practicability, and making any necessary adjustments. Furthermore, keep in mind that problem solving is an iterative process, and there may be times when you need to go back to the beginning and restart. Maintain your adaptability and try new solutions until you find the one that works best for you.

• Novick, L.R. and Bassok, M., 2005.  Problem Solving . Cambridge University Press.

Daniel Croft

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

Free Lean Six Sigma Templates

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

5S Floor Marking Best Practices

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

How to Measure the ROI of Continuous Improvement Initiatives

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

8D Problem-Solving: Common Mistakes to Avoid

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

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

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

8D: Tools and Techniques

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

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

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

How it works

For Business

Join Mind Tools

Article • 4 min read

The Problem-Solving Process

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

By the Mind Tools Content Team

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

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

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

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

1. Define the Problem

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

2. Analyze the Problem

Ask yourself, and others, the following questions.

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

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

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

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

3. Generate Potential Solutions

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

4. Select Best Solution

When selecting the best solution, consider:

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

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

5. Take Action

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

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

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

6. Monitor and Review

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

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

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

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

Join Mind Tools and get access to exclusive content.

This resource is only available to Mind Tools members.

Already a member? Please Login here

Team Management

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

Sign-up to our newsletter

Subscribing to the Mind Tools newsletter will keep you up-to-date with our latest updates and newest resources.

Subscribe now

Business Skills

Personal Development

Leadership and Management

Member Extras

Most Popular

Newest Releases

SWOT Analysis

SMART Goals

Mind Tools Store

About Mind Tools Content

Discover something new today

How to stop procrastinating.

Overcoming the Habit of Delaying Important Tasks

What Is Time Management?

Working Smarter to Enhance Productivity

How Emotionally Intelligent Are You?

Boosting Your People Skills

Self-Assessment

What's Your Leadership Style?

Learn About the Strengths and Weaknesses of the Way You Like to Lead

Recommended for you

Energizing yourself infographic.

Infographic Transcript

Infographic

Business Operations and Process Management

Strategy Tools

Customer Service

Business Ethics and Values

Handling Information and Data

Project Management

Knowledge Management

Self-Development and Goal Setting

Time Management

Presentation Skills

Learning Skills

Career Skills

Communication Skills

Negotiation, Persuasion and Influence

Working With Others

Difficult Conversations

Creativity Tools

Self-Management

Work-Life Balance

Stress Management and Wellbeing

Coaching and Mentoring

Change Management

Managing Conflict

Delegation and Empowerment

Performance Management

Leadership Skills

Developing Your Team

Talent Management

Problem Solving

Decision Making

Member Podcast

• Rosters & E-Bidding

Have a Research Question?

• Research Tools
• Explore Topics
• Stay Informed
• Publications

Easy Problem Solving Using the 4-step Method

June 7, 2017  by  Jennifer Haury Category:  Guest Author ,  Management

At a recent hospital town forum, hospital leaders are outlining the changes coming when a lone, brave nurse raises her hand and says, “We just can’t take any more changes. They are layered on top of each other and each one is rolled out in a different way. We are exhausted and it’s overloading us all.”  

 “Flavor of the Month” Fatigue

Change fatigue. You hear about it in every industry, from government sectors to software design to manufacturing to healthcare and more. When policy and leadership changes and process improvement overlap it’s no surprise when people complain about “flavor of the month,” and resist it just so they can keep some routine to their days.

In a time where change is required just to keep up with the shifting environment, one way to ease fatigue is to standardize HOW we change. If we use a best practice for solving problems, we can ensure that the right people are involved and problems are solved permanently, not temporarily. Better yet, HOW we change can become the habit and routine we long for.

The 4-step Problem Solving Method

The model we’ve used with clients is based on the A3 problem-solving methodology used by many “lean” production-based companies. In addition to being simpler, our 4-step method is visual, which helps remind the user what goes into each box.

The steps are as follows

• Develop a Problem Statement
• Determine Root Causes
• Rank Root Causes in Order of Importance
• Create an Action Plan

Step 1: Develop a Problem Statement

Developing a good problem statement always seems a lot easier than it generally turns out to be.  For example, this statement: “We don’t have enough staff,” frequently shows up as a problem statement. However, it suggests the solution—“GET MORE STAFF” — and fails to address the real problem that more staff might solve, such as answering phones in a timely manner.

The trick is to develop a problem statement that does not suggest a solution.  Avoiding the following words/phrases: “lack of,” “no,” “not enough,” or “too much” is key. When I start to fall into the trap of suggesting a solution, I ask: “So what problem does that cause?” This usually helps to get to a more effective problem statement.

Once you’ve developed a problem statement, you’ll need to define your target goal, measure your actual condition, then determine the gap. If we ran a restaurant and our problem was: “Customers complaining about burnt toast during morning shift,” the target goal might be: “Toast golden brown 100% of morning shift.”

Focus on a tangible, achievable target goal then measure how often that target is occurring. If our actual condition is: “Toast golden brown 50% of the time,” then our gap is: “Burnt toast 50% of the time.” That gap is now a refined problem to take to Step 2.

Step 2:  Determine Root Causes

In Step 2, we want to understand the root causes. For example, if the gap is burnt toast 50% of the time, what are all the possible reasons why?

This is when you brainstorm. It could be an inattentive cook or a broken pop-up mechanism. Cooks could be using different methods to time the toasting process or some breads toast more quickly.  During brainstorming, you’ll want to include everyone in the process since observing these interactions might also shed light on why the problem is occurring.

Once we have an idea of why, we then use the 5-why process to arrive at a root cause.  Ask “Why?” five times or until it no longer makes sense to ask. Root causes can be tricky.  For example, if the pop up mechanism is broken you could just buy a new toaster, right? But if you asked WHY it broke, you may learn cooks are pressing down too hard on the pop up mechanism, causing it to break. In this case, the problem would just reoccur if you bought a new toaster.

When you find you are fixing reoccurring problems that indicates you haven’t solved for the root cause. Through the 5-why process, you can get to the root cause and fix the problem permanently.

Step 3: Rank Root Causes

Once you know what’s causing the problem (and there may be multiple root causes), it’s time to move to Step 3 to understand which causes, if solved for, would close your gap. Here you rank the root causes in order of importance by looking at which causes would have the greatest impact in closing the gap.

There may be times when you don’t want to go after your largest root cause (perhaps because it requires others to change what they are doing, will take longer, or is dependent on other things getting fixed, etc). Sometimes you’ll find it’s better to start with a solution that has a smaller impact but can be done quickly.

Step 4: Create an Action Plan

In Step 4 you create your action plan — who is going to do what and by when. Documenting all of this and making it visible helps to communicate the plan to others and helps hold them accountable during implementation.

This is where your countermeasures or experiments to fix the problem are detailed. Will we train our chefs on how to use a new “pop-up mechanism” free toaster? Will we dedicate one toaster for white bread and one for wheat?  

Make sure to measure your results after you’ve implemented your plan to see if your target is met. If not, that’s okay; just go through the steps again until the problem is resolved.

Final Thoughts

Using the 4-step method has been an easy way for teams to change how they solve problems. One team I was working with started challenging their “solution jumps” and found this method was a better way to avoid assumptions which led to never really solving their problems.  It was easy to use in a conference room and helped them make their thinking visual so everyone could be involved and engaged in solving the problems their team faced. 

Do you have a problem-solving method that you use at your worksite?  Let us know in the comments below. 

MRSC is a private nonprofit organization serving local governments in Washington State. Eligible government agencies in Washington State may use our free, one-on-one Ask MRSC service to get answers to legal, policy, or financial questions.

About Jennifer Haury

Jennifer Haury is the CEO of All Angles Consulting, LLC and guest authored this post for MRSC.

Jennifer has over 28 years learning in the healthcare industry (17 in leadership positions or consulting in performance improvement and organizational anthropology) and is a Lean Six Sigma Black Belt.

She is a trusted, experienced leader with a keen interest in performance improvement and organizational anthropology. Jennifer is particularly concerned with the sustainability of continuous improvement programs and the cultural values and beliefs that translate into behaviors that either get in our own way or help us succeed in transforming our work.

The views expressed in guest columns represent the opinions of the author and do not necessarily reflect those of MRSC.

Blog Archives

Weekly e-news.

Get the latest local government news, analysis, and training opportunities in Washington State with MRSC’s Weekly Insights .

Related Materials

Have You Reviewed Your Excise Tax Worksheets Lately?

Planners manage conflict every day: Here's how to get better at it

Strategic Planning

An Overview of 4-Step Problem Solving

• Resource Topics
• Professional Learning Modules
• Program Evaluation
• Fact Sheets
• Presentations LiveBinder

This online course is intended to provide users with an understanding of the broad concepts of the 4-step problem solving process. The course includes the critical elements and guiding questions within each step, features sample data sources, and provides checks for understanding throughout.

• Sign into your account.
• Select All Courses at the top of the page, find An Overview of 4-Step Problem Solving , and click “Start Course” to begin.
• From FL PS/RtI Thinkific site, click “Sign In” in the upper right-hand corner.
• Click “Create a new account” below sign-in fields.
• Fill in your name, email, and create a password. Click “Sign Up.”

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

Additional menu

The 5 steps of the solving problem process

August 17, 2023 by MindManager Blog

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

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

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

Understanding the problem solving process

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

The problem solving process typically includes:

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

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

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

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

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

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

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

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

Examples of problem solving scenarios

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

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

Scenario #1: Manufacturing

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

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

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

Your team comes up with three possible solutions.

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

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

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

Scenario #2: Service Delivery

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

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

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

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

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

Scenario #3: Marketing

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

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

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

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

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

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

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

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

Ready to take the next step?

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

Why choose MindManager?

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

Explore MindManager

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

Overview of the Problem-Solving Mental Process

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

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

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

Frequently Asked Questions

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

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

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

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

The following steps include developing strategies and organizing knowledge.

1. Identifying the Problem

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

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

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

2. Defining the Problem

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

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

3. Forming a Strategy

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

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

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

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

4. Organizing Information

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

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

5. Allocating Resources

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

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

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

6. Monitoring Progress

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

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

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

7. Evaluating the Results

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

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

A Word From Verywell​

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

Get Advice From The Verywell Mind Podcast

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

Follow Now : Apple Podcasts / Spotify / Google Podcasts

You can become a better problem solving by:

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

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

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

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

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

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

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

How to Solve Coding Problems with a Simple Four Step Method

I had fifteen minutes left, and I knew I was going to fail.

I had spent two months studying for my first technical interview.

I thought I was prepared, but as the interview came to a close, it hit me: I had no idea how to solve coding problems.

Of all the tutorials I had taken when I was learning to code, not one of them had included an approach to solving coding problems.

I had to find a method for problem-solving—my career as a developer depended on it.

I immediately began researching methods. And I found one. In fact, what I uncovered was an invaluable strategy. It was a time-tested four-step method that was somehow under the radar in the developer ecosystem.

In this article, I’ll go over this four-step problem-solving method that you can use to start confidently solving coding problems.

Solving coding problems is not only part of the developer job interview process—it’s what a developer does all day. After all, writing code is problem-solving.

A method for solving problems

This method is from the book How to Solve It by George Pólya. It originally came out in 1945 and has sold over one million copies.

His problem-solving method has been used and taught by many programmers, from computer science professors (see Udacity’s Intro to CS course taught by professor David Evans) to modern web development teachers like Colt Steele.

Let’s walk through solving a simple coding problem using the four-step problem-solving method. This allows us to see the method in action as we learn it. We'll use JavaScript as our language of choice. Here’s the problem:

Create a function that adds together two numbers and returns that value. There are four steps to the problem-solving method:

• Understand the problem.
• Devise a plan.
• Carry out the plan.

Let’s get started with step one.

Step 1: Understand the problem.

When given a coding problem in an interview, it’s tempting to rush into coding. This is hard to avoid, especially if you have a time limit.

However, try to resist this urge. Make sure you actually understand the problem before you get started with solving it.

Read through the problem. If you’re in an interview, you could read through the problem out loud if that helps you slow down.

As you read through the problem, clarify any part of it you do not understand. If you’re in an interview, you can do this by asking your interviewer questions about the problem description. If you’re on your own, think through and/or Google parts of the question you might not understand.

This first step is vital as we often don’t take the time to fully understand the problem. When you don’t fully understand the problem, you’ll have a much harder time solving it.

To help you better understand the problem, ask yourself:

What are the inputs?

What kinds of inputs will go into this problem? In this example, the inputs are the arguments that our function will take.

Just from reading the problem description so far, we know that the inputs will be numbers. But to be more specific about what the inputs will be, we can ask:

Will the inputs always be just two numbers? What should happen if our function receives as input three numbers?

Here we could ask the interviewer for clarification, or look at the problem description further.

The coding problem might have a note saying, “You should only ever expect two inputs into the function.” If so, you know how to proceed. You can get more specific, as you’ll likely realize that you need to ask more questions on what kinds of inputs you might be receiving.

Will the inputs always be numbers? What should our function do if we receive the inputs “a” and “b”? Clarify whether or not our function will always take in numbers.

Optionally, you could write down possible inputs in a code comment to get a sense of what they’ll look like:

//inputs: 2, 4

What are the outputs?

What will this function return? In this case, the output will be one number that is the result of the two number inputs. Make sure you understand what your outputs will be.

Create some examples.

Once you have a grasp of the problem and know the possible inputs and outputs, you can start working on some concrete examples.

Examples can also be used as sanity checks to test your eventual problem. Most code challenge editors that you’ll work in (whether it’s in an interview or just using a site like Codewars or HackerRank) have examples or test cases already written for you. Even so, writing out your own examples can help you cement your understanding of the problem.

Start with a simple example or two of possible inputs and outputs. Let's return to our addition function.

Let’s call our function “add.”

What’s an example input? Example input might be:

// add(2, 3)

What is the output to this? To write the example output, we can write:

// add(2, 3) ---> 5

This indicates that our function will take in an input of 2 and 3 and return 5 as its output.

Create complex examples.

By walking through more complex examples, you can take the time to look for edge cases you might need to account for.

For example, what should we do if our inputs are strings instead of numbers? What if we have as input two strings, for example, add('a', 'b')?

Your interviewer might possibly tell you to return an error message if there are any inputs that are not numbers. If so, you can add a code comment to handle this case if it helps you remember you need to do this.

Your interviewer might also tell you to assume that your inputs will always be numbers, in which case you don’t need to write any extra code to handle this particular input edge case.

If you don’t have an interviewer and you’re just solving this problem, the problem might say what happens when you enter invalid inputs.

For example, some problems will say, “If there are zero inputs, return undefined.” For cases like this, you can optionally write a comment.

// check if there are no inputs.

// If no inputs, return undefined.

For our purposes, we’ll assume that our inputs will always be numbers. But generally, it’s good to think about edge cases.

Computer science professor Evans says to write what developers call defensive code. Think about what could go wrong and how your code could defend against possible errors.  

Before we move on to step 2, let’s summarize step 1, understand the problem:

-Read through the problem.

-What are the inputs?

-What are the outputs?

Create simple examples, then create more complex ones.

2. Devise a plan for solving the problem.

Next, devise a plan for how you’ll solve the problem. As you devise a plan, write it out in pseudocode.

Pseudocode is a plain language description of the steps in an algorithm. In other words, your pseudocode is your step-by-step plan for how to solve the problem.

Write out the steps you need to take to solve the problem. For a more complicated problem, you’d have more steps. For this problem, you could write:

// Create a sum variable.

Add the first input to the second input using the addition operator .

// Store value of both inputs into sum variable.

// Return as output the sum variable. Now you have your step-by-step plan to solve the problem. For more complex problems, professor Evans notes, “Consider systematically how a human solves the problem.” That is, forget about how your code might solve the problem for a moment, and think about how you would solve it as a human. This can help you see the steps more clearly.

3. Carry out the plan (Solve the problem!)

The next step in the problem-solving strategy is to solve the problem. Using your pseudocode as your guide, write out your actual code.

Professor Evans suggests focusing on a simple, mechanical solution. The easier and simpler your solution is, the more likely you can program it correctly.

Taking our pseudocode, we could now write this:

Professor Evans adds, remember not to prematurely optimize. That is, you might be tempted to start saying, “Wait, I’m doing this and it’s going to be inefficient code!”

First, just get out your simple, mechanical solution.

What if you can’t solve the entire problem? What if there's a part of it you still don't know how to solve?

Colt Steele gives great advice here: If you can’t solve part of the problem, ignore that hard part that’s tripping you up. Instead, focus on everything else that you can start writing.

Temporarily ignore that difficult part of the problem you don’t quite understand and write out the other parts. Once this is done, come back to the harder part.

This allows you to get at least some of the problem finished. And often, you’ll realize how to tackle that harder part of the problem once you come back to it.

Step 4: Look back over what you've done.

Once your solution is working, take the time to reflect on it and figure out how to make improvements. This might be the time you refactor your solution into a more efficient one.

As you look at your work, here are some questions Colt Steele suggests you ask yourself to figure out how you can improve your solution:

• Can you derive the result differently? What other approaches are there that are viable?
• Can you understand it at a glance? Does it make sense?
• Can you use the result or method for some other problem?
• Can you improve the performance of your solution?
• Can you think of other ways to refactor?
• How have other people solved this problem?

One way we might refactor our problem to make our code more concise: removing our variable and using an implicit return:

With step 4, your problem might never feel finished. Even great developers still write code that they later look at and want to change. These are guiding questions that can help you.

If you still have time in an interview, you can go through this step and make your solution better. If you are coding on your own, take the time to go over these steps.

When I’m practicing coding on my own, I almost always look at the solutions out there that are more elegant or effective than what I’ve come up with.

Wrapping Up

In this post, we’ve gone over the four-step problem-solving strategy for solving coding problems.

Let's review them here:

• Step 1: understand the problem.
• Step 2: create a step-by-step plan for how you’ll solve it .
• Step 3: carry out the plan and write the actual code.
• Step 4: look back and possibly refactor your solution if it could be better.

Practicing this problem-solving method has immensely helped me in my technical interviews and in my job as a developer. If you don't feel confident when it comes to solving coding problems, just remember that problem-solving is a skill that anyone can get better at with time and practice.

If you enjoyed this post, join my coding club , where we tackle coding challenges together every Sunday and support each other as we learn new technologies.

If you have feedback or questions on this post, feel free to tweet me @madisonkanna ..

Read more posts .

If you read this far, thank the author to show them you care. Say Thanks

Learn to code for free. freeCodeCamp's open source curriculum has helped more than 40,000 people get jobs as developers. Get started

The Simple Guide to Problem Mapping (only 4 steps)

In this short post I’m going to show you how to create a visual model of your complex problem with a 4-step problem mapping method.

This type of modeling can be applied to any complex social problem, like homelessness, poverty or crime. Whether you’re a street activist or long-time systems change practitioner, the systems thinking method I share below can help you gain understanding about the structure and dynamics of your problem and increase your likelihood of making good decisions about solving it. 

These are the exact steps we use to start mapping in my online course about systems thinking and solving social problems .

In the post I’ll also talk about the different types of problem mapping, how mapping itself is a problem-solving process, and give an example of mapping the issue of illegal opioids.

It doesn’t matter what you call it

Let’s get this out of the way first. There’s a lot of methods for visualizing connected ideas or systems, including problem mapping, mind mapping, cognitive mapping and issue mapping. There’s also a variety of ways people refer to the results: mind maps, mental models, causal loop diagrams, solution maps, and problem solution maps.

When you’re just getting started, jargon and differences in mapping method don’t matter very much. My intent in this blog is to remove the somewhat artificial barriers that prevent people from regularly creating and using problem maps.

For now, I don’t want you to worry about any of this. Just begin with Step 1 below by putting your ideas about the problem and its causes on paper. You can easily adjusting your map later if you want it to reflect a certain mapping protocol.

Problem mapping as problem-solving process

Mapping is just one of many problem solving techniques. But, it is particularly suited to complex problems with many variables and interconnections. Whereas verbally describing a series of complex relationships is very difficult, a simple picture really can be worth a thousand words.

At the beginning, it’s important to recognize that the goal isn’t to create a perfect representation of reality. That’s not possible and it would be foolish to try. Rather, the process of creating the map is about gaining insight about problem in way that can’t be had with words or equations alone.

Along the way, you’ll make explicit many assumptions you have about the problem, as well as how they are connected. In other words, mapping allows you to simultaneously capture details about parts the problem while creating a representation of the “big picture.” This type of switching back and forth from reductive analysis to synthesis is an excellent complex problem-solving approach .

Mapping isn’t a choice

You might not think you need to formally model your problem, but the question is not whether you should model or not. Mental models are always used, even if only implicitly in our heads or baked into the assumptions we make. The choice is really about whether you want to use an implicit and vague model in your head or you want to use an explicit and detailed model.

I know you already have a rudimentary idea about your social problem and what causes it. This is your most basic mental model of the problem. The question is – how accurate is it? For most people who haven’t written it down, the model in their head is simple, perhaps a linear cause and effect model.

Complex problem mapping example: illegal opioids

As an example, let’s look at the issue of illegal opioids.

The two opioid models and policies I show bel0w are adapted from Narcotics and the Community: A System Simulation . Note that this is a simplified version for instruction purposes only and doesn’t reflect the intricacies of more recent opioid issues likes prescription opioids and fentanyl.

The logic of the model is straight-forward: with less illegal opioid supply, there will be less addiction and thus less addiction-related crime. It’s intuitive and easy to remember. Our minds are full of models like this, each fairly simple because the human brain isn’t able to hold more than a handful of variables in mind at the same time. 

While it is hard to disagree with the premise of the simple cause and effect model, mistakes can happen when we assume the effects of our actions will be similarly simple and linear. For example, one common policy recommendation to reduce opioid addiction has been to curb the supply of illegal opioids. Let’s examine the consequences of this policy with a slightly more detailed model that captures its additional complexity.

Adding variables, or nodes

Let’s add three additional variables (or nodes) not in the simple model.

The number of opioid addicts isn’t one static number (a fixed quantity, or “stock” as it’s referred to in a stock and flow diagram). Rather, the number is determined by rates of addiction and attrition (or “flows”). So let’s add “addiction rate” and “attrition rate” to the map.

Because a reduced opioid supply would make the price of illegal opioids rise, let’s add “opioid price” as well.

Causal feedback loops

In the simple cause and effect model, price isn’t considered and any reduction in the supply deterministically reduces addiction and crime. But, adding the price of opioids to the model gives us a counterintuitive feedback loop: because addicts need more money to get the same amount of opioids, reducing the supply could actually make crime worse.

On the other hand, the addition of price to the model also mediates the rate at which people become addicted (represented by addiction and attrition rate nodes). When the price is high, there are fewer new users, which is good.

The point of the more complex model is not to show that reducing the illegal supply of opioids is a good or bad policy. Like all actions aimed at social problems, it is a trade-off between benefits and costs.

Rather, my intent is to show that overly simple mental models of a problem, even when logically correct, can lead us to make decisions that lead to unintended consequences. Better models don’t necessarily help us find the right solution, but they can supply needed insight about how the problem works systemically and give a sense of how our actions may cascade through the larger system.

So, if you don’t already have an explicit model of your problem or if you’re just working from a simple linear model in your mind, here are the steps you should take to create your own.

Problem mapping in four steps

Step 1. brainstorm primary causes and concepts.

Think of a problem and spend some time brainstorming all of its causes, including any other relevant concepts. For now, concepts can be any important variables in your problem: actors, stocks (e.g. quantities) and flows (e.g. rates), or even abstract concepts (e.g. wealth, democracy, etc.). Keep these tips in mind:

• Use nouns and avoid verbs, since actions will be represented in the map with arrows.
• Try to pick things that can go up or down in quantity, strength or influence over time.
• Be as specific as possible. When possible choose metrics over abstract concepts.

You might have a long list, and some causes and concepts may be more important that others. That’s OK.

For our purposes to get started, select the top 3-5 causes. These are the issues you believe are most fundamental in causing your problem.

My example below has only three primary causes for simplicity, but yours may have more. After you get through the steps there will be plenty of time for you to add or subtract variables.

Step 2. Brainstorm second-order causes

Most people think step 2 is about brainstorming solutions. But don’t do that yet! You don’t yet understand how the problem works, so solutions at this point will likely be similarly incomplete. To start getting a fuller picture of how your problem functions as part of a larger system, brainstorm second order causes. To put it simply, what causes each of your primary causes?

You can pull second-order causes from your initial brainstorming list, or brainstorm a new list for each primary cause.

Once you do that, your model may look something like this:

Step 3. Add interrelationships between causes

We’re getting closer to a comprehensive model – just two more steps to go!

In this step you operationalize the biggest insight about complex systems: the relationships are more important than the components . Right now, you still have a fairly simple, linear model. Every node leads directly to your problem, which makes it a kind of hierarchy.

I’m fairly certain that in real life your problem exists in a more complicated web of connections. In this step you connect causes that have a relationship to any other cause, even those that don’t lead directly to the problem.

For example, one of your second-order causes may be related to another second-order cause. That may sound confusing, but your task right now is just to draw connections between any two nodes that you feel might affect each other (see red lines in model below). 

Step 4. Define causality of each relationship

The final step is to characterize each of the relationships between nodes as increasing or decreasing (for example, Cause #1a increases Cause #1, or Cause #1a decreases Cause #1).

A plus sign represents increase and a negative sign represents decrease.

Use this question to help you determine the direction of the relationship:

When this component increases, does the other component increase or decrease?

Note that sometimes nodes will have a two-way relationship. For example, in the model below an increase in Cause #1 increases Cause #2a, but an increase in Cause #2a decreases Cause #1. This is a balancing feedback loop.

The first draft of your model is complete. Who-hoo!

Three problem mapping principles

Here are a few words of guidance to keep in mind as you start modeling.

#1. Always model a problem, never a system

Problems themselves dictate the necessary boundaries that formal systems (like the education system) do not.

#2. The map is not the terrain

Your model is only an abstraction of reality and should always be regarded with a degree of skepticism and knowledge that the terrain may change.

#3. All models are wrong and incomplete

The purpose of using a model isn’t to find the solution, but to increase your understanding of the problem and explore the effects of possible interventions.

The whole process is most valuable when you remember that mapping is more of an art than science.

What to do after you’ve created a first draft

Share it with others for feedback.

There’s a few directions you can go from here. The first is to talk through your model to a trusted colleague who also has some understanding of the problem, or encourage them to create their own model following these steps.

Differing perspectives can uncover different assumptions about the problem and lead to fruitful dialogue. Your model can be updated based on feedback, or you can work with your colleague to combine models, adding and subtracting nodes and relationships as you see fit.

Convert it into a fuzzy cognitive map

The other direction is to convert your model into a fuzzy cognitive map using computer software. This is super exciting because it allows you to run simulations of potential changes you could make and see resulting changes in the system as a whole.

For example, in the earlier opioid addiction model we could run a simulation of a policy that provides free legal supply of opioids to addicts (in an effort to reduce both crime and long-term addition), and calculate system-wide changes. This helps uncover feedback loops and potential unintentional consequences.

Creating a fuzzy cognitive map only requires a few additional steps. I go through them step-by-step plus how to run what-if scenarios in my next blog posts.

Interview Questions

Comprehensive Interview Guide: 60+ Professions Explored in Detail

26 Good Examples of Problem Solving (Interview Answers)

By Biron Clark

Published: November 15, 2023

Employers like to hire people who can solve problems and work well under pressure. A job rarely goes 100% according to plan, so hiring managers will be more likely to hire you if you seem like you can handle unexpected challenges while staying calm and logical in your approach.

But how do they measure this?

They’re going to ask you interview questions about these problem solving skills, and they might also look for examples of problem solving on your resume and cover letter. So coming up, I’m going to share a list of examples of problem solving, whether you’re an experienced job seeker or recent graduate.

Then I’ll share sample interview answers to, “Give an example of a time you used logic to solve a problem?”

Problem-Solving Defined

It is the ability to identify the problem, prioritize based on gravity and urgency, analyze the root cause, gather relevant information, develop and evaluate viable solutions, decide on the most effective and logical solution, and plan and execute implementation. 

Problem-solving also involves critical thinking, communication, listening, creativity, research, data gathering, risk assessment, continuous learning, decision-making, and other soft and technical skills.

Solving problems not only prevent losses or damages but also boosts self-confidence and reputation when you successfully execute it. The spotlight shines on you when people see you handle issues with ease and savvy despite the challenges. Your ability and potential to be a future leader that can take on more significant roles and tackle bigger setbacks shine through. Problem-solving is a skill you can master by learning from others and acquiring wisdom from their and your own experiences. 

It takes a village to come up with solutions, but a good problem solver can steer the team towards the best choice and implement it to achieve the desired result.

Watch: 26 Good Examples of Problem Solving

Examples of problem solving scenarios in the workplace.

• Correcting a mistake at work, whether it was made by you or someone else
• Overcoming a delay at work through problem solving and communication
• Resolving an issue with a difficult or upset customer
• Overcoming issues related to a limited budget, and still delivering good work through the use of creative problem solving
• Overcoming a scheduling/staffing shortage in the department to still deliver excellent work
• Troubleshooting and resolving technical issues
• Handling and resolving a conflict with a coworker
• Solving any problems related to money, customer billing, accounting and bookkeeping, etc.
• Taking initiative when another team member overlooked or missed something important
• Taking initiative to meet with your superior to discuss a problem before it became potentially worse
• Solving a safety issue at work or reporting the issue to those who could solve it
• Using problem solving abilities to reduce/eliminate a company expense
• Finding a way to make the company more profitable through new service or product offerings, new pricing ideas, promotion and sale ideas, etc.
• Changing how a process, team, or task is organized to make it more efficient
• Using creative thinking to come up with a solution that the company hasn’t used before
• Performing research to collect data and information to find a new solution to a problem
• Boosting a company or team’s performance by improving some aspect of communication among employees
• Finding a new piece of data that can guide a company’s decisions or strategy better in a certain area

Problem Solving Examples for Recent Grads/Entry Level Job Seekers

• Coordinating work between team members in a class project
• Reassigning a missing team member’s work to other group members in a class project
• Adjusting your workflow on a project to accommodate a tight deadline
• Speaking to your professor to get help when you were struggling or unsure about a project
• Asking classmates, peers, or professors for help in an area of struggle
• Talking to your academic advisor to brainstorm solutions to a problem you were facing
• Researching solutions to an academic problem online, via Google or other methods
• Using problem solving and creative thinking to obtain an internship or other work opportunity during school after struggling at first

You can share all of the examples above when you’re asked questions about problem solving in your interview. As you can see, even if you have no professional work experience, it’s possible to think back to problems and unexpected challenges that you faced in your studies and discuss how you solved them.

Interview Answers to “Give an Example of an Occasion When You Used Logic to Solve a Problem”

Now, let’s look at some sample interview answers to, “Give me an example of a time you used logic to solve a problem,” since you’re likely to hear this interview question in all sorts of industries.

Example Answer 1:

At my current job, I recently solved a problem where a client was upset about our software pricing. They had misunderstood the sales representative who explained pricing originally, and when their package renewed for its second month, they called to complain about the invoice. I apologized for the confusion and then spoke to our billing team to see what type of solution we could come up with. We decided that the best course of action was to offer a long-term pricing package that would provide a discount. This not only solved the problem but got the customer to agree to a longer-term contract, which means we’ll keep their business for at least one year now, and they’re happy with the pricing. I feel I got the best possible outcome and the way I chose to solve the problem was effective.

Example Answer 2:

In my last job, I had to do quite a bit of problem solving related to our shift scheduling. We had four people quit within a week and the department was severely understaffed. I coordinated a ramp-up of our hiring efforts, I got approval from the department head to offer bonuses for overtime work, and then I found eight employees who were willing to do overtime this month. I think the key problem solving skills here were taking initiative, communicating clearly, and reacting quickly to solve this problem before it became an even bigger issue.

Example Answer 3:

In my current marketing role, my manager asked me to come up with a solution to our declining social media engagement. I assessed our current strategy and recent results, analyzed what some of our top competitors were doing, and then came up with an exact blueprint we could follow this year to emulate our best competitors but also stand out and develop a unique voice as a brand. I feel this is a good example of using logic to solve a problem because it was based on analysis and observation of competitors, rather than guessing or quickly reacting to the situation without reliable data. I always use logic and data to solve problems when possible. The project turned out to be a success and we increased our social media engagement by an average of 82% by the end of the year.

Answering Questions About Problem Solving with the STAR Method

When you answer interview questions about problem solving scenarios, or if you decide to demonstrate your problem solving skills in a cover letter (which is a good idea any time the job description mention problem solving as a necessary skill), I recommend using the STAR method to tell your story.

STAR stands for:

It’s a simple way of walking the listener or reader through the story in a way that will make sense to them. So before jumping in and talking about the problem that needed solving, make sure to describe the general situation. What job/company were you working at? When was this? Then, you can describe the task at hand and the problem that needed solving. After this, describe the course of action you chose and why. Ideally, show that you evaluated all the information you could given the time you had, and made a decision based on logic and fact.

Finally, describe a positive result you got.

Whether you’re answering interview questions about problem solving or writing a cover letter, you should only choose examples where you got a positive result and successfully solved the issue.

Example answer:

Situation : We had an irate client who was a social media influencer and had impossible delivery time demands we could not meet. She spoke negatively about us in her vlog and asked her followers to boycott our products. (Task : To develop an official statement to explain our company’s side, clarify the issue, and prevent it from getting out of hand). Action : I drafted a statement that balanced empathy, understanding, and utmost customer service with facts, logic, and fairness. It was direct, simple, succinct, and phrased to highlight our brand values while addressing the issue in a logical yet sensitive way.   We also tapped our influencer partners to subtly and indirectly share their positive experiences with our brand so we could counter the negative content being shared online.  Result : We got the results we worked for through proper communication and a positive and strategic campaign. The irate client agreed to have a dialogue with us. She apologized to us, and we reaffirmed our commitment to delivering quality service to all. We assured her that she can reach out to us anytime regarding her purchases and that we’d gladly accommodate her requests whenever possible. She also retracted her negative statements in her vlog and urged her followers to keep supporting our brand.

What Are Good Outcomes of Problem Solving?

Whenever you answer interview questions about problem solving or share examples of problem solving in a cover letter, you want to be sure you’re sharing a positive outcome.

Below are good outcomes of problem solving:

• Saving the company time or money
• Making the company money
• Pleasing/keeping a customer
• Obtaining new customers
• Solving a safety issue
• Solving a staffing/scheduling issue
• Solving a logistical issue
• Solving a company hiring issue
• Solving a technical/software issue
• Making a process more efficient and faster for the company
• Creating a new business process to make the company more profitable
• Improving the company’s brand/image/reputation
• Getting the company positive reviews from customers/clients

Every employer wants to make more money, save money, and save time. If you can assess your problem solving experience and think about how you’ve helped past employers in those three areas, then that’s a great start. That’s where I recommend you begin looking for stories of times you had to solve problems.

Tips to Improve Your Problem Solving Skills

Throughout your career, you’re going to get hired for better jobs and earn more money if you can show employers that you’re a problem solver. So to improve your problem solving skills, I recommend always analyzing a problem and situation before acting. When discussing problem solving with employers, you never want to sound like you rush or make impulsive decisions. They want to see fact-based or data-based decisions when you solve problems.

Next, to get better at solving problems, analyze the outcomes of past solutions you came up with. You can recognize what works and what doesn’t. Think about how you can get better at researching and analyzing a situation, but also how you can get better at communicating, deciding the right people in the organization to talk to and “pull in” to help you if needed, etc.

Finally, practice staying calm even in stressful situations. Take a few minutes to walk outside if needed. Step away from your phone and computer to clear your head. A work problem is rarely so urgent that you cannot take five minutes to think (with the possible exception of safety problems), and you’ll get better outcomes if you solve problems by acting logically instead of rushing to react in a panic.

You can use all of the ideas above to describe your problem solving skills when asked interview questions about the topic. If you say that you do the things above, employers will be impressed when they assess your problem solving ability.

If you practice the tips above, you’ll be ready to share detailed, impressive stories and problem solving examples that will make hiring managers want to offer you the job. Every employer appreciates a problem solver, whether solving problems is a requirement listed on the job description or not. And you never know which hiring manager or interviewer will ask you about a time you solved a problem, so you should always be ready to discuss this when applying for a job.

Related interview questions & answers:

• How do you handle stress?
• How do you handle conflict?
• Tell me about a time when you failed

About the Author

Read more articles by Biron Clark

Continue Reading

15 Most Common Pharmacist Interview Questions and Answers

15 most common paralegal interview questions and answers, top 30+ funny interview questions and answers, 60 hardest interview questions and answers, 100+ best ice breaker questions to ask candidates, top 20 situational interview questions (& sample answers), 15 most common physical therapist interview questions and answers, 15 most common project manager interview questions and answers.