steps involved for problem solving

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

Overview of the Problem-Solving Mental Process

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

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

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)

The Art of Effective Problem Solving: A Step-by-Step Guide

Author: Daniel Croft

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

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!

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.

Was this helpful?

Daniel Croft

Hi im Daniel continuous improvement manager with a Black Belt in Lean Six Sigma and over 10 years of real-world experience across a range sectors, I have a passion for optimizing processes and creating a culture of efficiency. I wanted to create Learn Lean Siigma to be a platform dedicated to Lean Six Sigma and process improvement insights and provide all the guides, tools, techniques and templates I looked for in one place as someone new to the world of Lean Six Sigma and Continuous improvement.

The Power of Mistakes: Lessons Learned from Failure

How to Use Ishikawa Diagrams to Solve Business Problems

Free lean six sigma templates.

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

Understanding Process Performance: Pp and Ppk

Understand Process Performance (Pp) and Process Performance Index (Ppk) to assess and improve manufacturing processes.…

LIFO or FIFO for Stock Management?

Choosing between LIFO and FIFO for stock management depends on factors like product nature, market…

Are There Any Official Standards for Six Sigma?

Are there any official standards for Six Sigma? While Six Sigma is a well-defined methodology…

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…

Brain Power

5 steps (and 4 techniques) for effective problem solving.

Problem solving is the process of reviewing every element of an issue so you can get to a solution or fix it. Problem solving steps cover multiple aspects of a problem that you can bring together to find a solution. Whether that’s in a group collaboratively or independently, the process remains the same, but the approach and the steps can differ.

To find a problem solving approach that works for you, your team, or your company, you have to take into consideration the environment you’re in and the personalities around you.

Knowing the characters in the room will help you decide on the best approach to try and ultimately get to the best solution.

Table of Contents

5 problem solving steps, 4 techniques to encourage problem solving, the bottom line.

No matter what the problem is, to solve it, you nearly always have to follow these problem solving steps. Missing any of these steps can cause the problem to either resurface or the solution to not be implemented correctly.

Once you know these steps, you can then get creative with the approach you take to find the solutions you need.

1. Define the Problem

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

Spend time elaborating on the problem, write it down, and discuss everything, so you’re clear on why the problem is occurring and who it is impacting.

Once you have clarity on the problem, you then need to start thinking about every possible solution . This is where you go big and broad, as you want to come up with as many alternative solutions as possible. Don’t just take the first idea; build out as many as you can through active listening, as the more you create, the more likely you’ll find a solution that has the best impact on the team.

3. Decide on a Solution

Whichever solution you pick individually or as a team, make sure you think about the impact on others if you implement this solution. Ask questions like:

• How will they react to this change?
• Will they need to change anything?
• Who do we need to inform of this change?

4. Implement the Solution

At this stage of problem solving, be prepared for feedback, and plan for this. When you roll out the solution, request feedback on the success of the change made.

5. Review, Iterate, and Improve

Making a change shouldn’t be a one time action. Spend time reviewing the results of the change to make sure it’s made the required impact and met the desired outcomes.

Make changes where needed so you can further improve the solution implemented.

Each individual or team is going to have different needs and may need a different technique to encourage each of the problem solving steps. Try one of these to stimulate the process.

1-2-4 All Approach + Voting

The 1-2-4-All is a good problem solving approach that can work no matter how large the group is. Everyone is involved, and you can generate a vast amount of ideas quickly.

Ideas and solutions are discussed and organized rapidly, and what is great about this approach is the attendees own their ideas, so when it comes to implementing the solutions, you don’t have more work to gain buy-in.

As a facilitator, you first need to present the group with a question explaining the problem or situation. For example, “What actions or ideas would you recommend to solve the company’s lack of quiet working areas?”

With the question clear for all to see, the group then spends 5 minutes to reflect on the question individually. They can jot down their thoughts and ideas on Post-Its.

Now ask the participants to find one or two other people to discuss their ideas and thoughts with. Ask the group to move around to find a partner so they can mix with new people.

Ask the pairs to spend 5 minutes discussing their shared ideas and thoughts.

Next, put the group into groups of two or three pairs to make groups of 4-6. Each group shouldn’t be larger than six as the chances of everyone being able to speak reduces.

Ask the group to discuss one interesting idea they’ve heard in previous rounds, and each group member shares one each.

The group then needs to pick their preferred solution to the problem. This doesn’t have to be voted on, just one that resonated most with the group.

Then ask for three actions that could be taken to implement this change.

Bring everyone back together as a group and ask open questions like “What is the one thing you discussed that stood out for you?” or “Is there something you now see differently following these discussions?”

By the end of the session, you’ll have multiple approaches to solve the problem, and the whole group will have contributed to the future solutions and improvements.

The Lightning Decision Jam

The Lightning Decision Jam is a great way to solve problems collaboratively and agree on one solution or experiment you want to try straight away. It encourages team decision making, but at the same time, the individual can get their ideas and feedback across. [1]

If, as a team, you have a particular area you want to improve upon, like the office environment, for example, this approach is perfect to incorporate in the problem solving steps.

The approach follows a simple loop.

Make a Note – Stick It on The Wall – Vote – Prioritize

Using sticky notes, the technique identifies major problems, encourages solutions, and opens the group up for discussion. It allows each team member to play an active role in identifying both problems and ways to solve them.

Mind Mapping

Mind mapping is a fantastic visual thinking tool that allows you to bring problems to life by building out the connections and visualizing the relationships that make up the problem.

You can use a mind map to quickly expand upon the problem and give yourself the full picture of the causes of the problem, as well as solutions [2] .

The goal of a mind map is to simplify the problem and link the causes and solutions to the problem.

To create a mind map, you must first create the central topic (level 1). In this case, that’s the problem.

Next, create the linked topics (level 2) that you place around and connect to the main central topic with a simple line.

If the central topic is “The client is always changing their mind at the last minute,” then you could have linked topics like:

• How often does this happen?
• Why are they doing this?
• What are they asking for?
• How do they ask for it?
• What impact does this have?

Adding these linking topics allows you to start building out the main causes of the problem as you can begin to see the full picture of what you need to fix. Once you’re happy that you’ve covered the breadth of the problem and its issues, you can start to ideate on how you’re going to fix it with the problem solving steps.

Now, start adding subtopics (level 3) linking to each of the level 2 topics. This is where you can start to go big on solutions and ideas to help fix the problem.

For each of the linked topics (level 2), start to think about how you can prevent them, mitigate them, or improve them. As this is just ideas on paper, write down anything that comes to mind, even if you think the client will never agree to it!

The more you write down, the more ideas you’ll have until you find one or two that could solve the main problem.

Once you run out of ideas, take a step back and highlight your favorite solutions to take forward and implement.

The 5 Why’s

The five why’s can sound a little controversial, and you shouldn’t try this without prepping the team beforehand.

Asking “why” is a great way to go deep into the root of the problem to make the individual or team really think about the cause. When a problem arises, we often have preconceived ideas about why this problem has occurred, which is usually based on our experiences or beliefs.

Start with describing the problem, and then the facilitator can ask “Why?” fives time or more until you get to the root of the problem. It’s tough at first to keep being asked why, but it’s also satisfying when you get to the root of the problem [3] .

As a facilitator, although the basic approach is to ask why, you need to be careful not to guide the participant down a single route.

To help with this, you can use a mind map with the problem at the center. Then ask a why question that will result in multiple secondary topics around the central problem. Having this visual representation of the problem helps you build out more useful why questions around it.

Once you get to the root of the problem, don’t forget to be clear in the actions to put a fix in place to resolve it.

Learn more about how to use the five why’s here .

To fix a problem, you must first be in a position where you fully understand it. There are many ways to misinterpret a problem, and the best way to understand them is through conversation with the team or individuals who are experiencing it.

Once you’re aligned, you can then begin to work on the solutions that will have the greatest impact through effective problem solving steps.

For the more significant or difficult problems to solve, it’s often advisable to break the solution up into smaller actions or improvements.

Trial these improvements in short iterations, and then continue the conversations to review and improve the solution. Implementing all of these steps will help you root out the problems and find useful solutions each time.

How to Use a Planner Effectively

How to Be a Better Planner: Avoid the Planning Fallacy

5 Best Apps to Help You Delegate Tasks Easily

Delegating Leadership Style: What Is It & When To Use It?

The Fear of Delegating Work To Others

Why Is Delegation Important in Leadership?

7 Best Tools for Prioritizing Work

How to Deal with Competing Priorities Effectively

What Is the RICE Prioritization Model And How Does It Work?

4 Exercises to Improve Your Focus

What Is Chronic Procrastination and How To Deal with It

How to Snap Out of Procrastination With ADHD

Are Depression And Procrastination Connected?

Procrastination And Laziness: Their Differences & Connections

Bedtime Procrastination: Why You Do It And How To Break It

15 Books on Procrastination To Help You Start Taking Action

Productive Procrastination: Is It Good or Bad?

The Impact of Procrastination on Productivity

How to Cope With Anxiety-Induced Procrastination

How to Break the Perfectionism-Procrastination Loop

15 Work-Life Balance Books to Help You Take Control of Life

Work Life Balance for Women: What It Means & How to Find It

6 Essential Mindsets For Continuous Career Growth

How to Discover Your Next Career Move Amid the Great Resignation

The Key to Creating a Vibrant (And Magical Life) by Lee Cockerell

9 Tips on How To Disconnect From Work And Stay Present

Work-Life Integration vs Work-Life Balance: Is One Better Than the Other?

How To Practice Self-Advocacy in the Workplace (Go-to Guide)

How to Boost Your Focus And Attention Span

What Are Distractions in a Nutshell?

What Is Procrastination And How To End It

Prioritization — Using Your Time & Energy Effectively

Delegation — Leveraging Your Time & Resources

Your Guide to Effective Planning & Scheduling

The Ultimate Guide to Achieving Goals

How to Find Lasting Motivation

Complete Guide to Getting Back Your Energy

How to Have a Good Life Balance

Explore the time flow system.

About the Time Flow System

Key Philosophy I: Fluid Progress, Like Water

Key Philosophy II: Pragmatic Priorities

Key Philosophy III: Sustainable Momentum

Key Philosophy IV: Three Goal Focus

How the Time Flow System Works

How to master the seven-step problem-solving process

In this episode of the McKinsey Podcast , Simon London speaks with Charles Conn, CEO of venture-capital firm Oxford Sciences Innovation, and McKinsey senior partner Hugo Sarrazin about the complexities of different problem-solving strategies.

Podcast transcript

Simon London: Hello, and welcome to this episode of the McKinsey Podcast , with me, Simon London. What’s the number-one skill you need to succeed professionally? Salesmanship, perhaps? Or a facility with statistics? Or maybe the ability to communicate crisply and clearly? Many would argue that at the very top of the list comes problem solving: that is, the ability to think through and come up with an optimal course of action to address any complex challenge—in business, in public policy, or indeed in life.

Looked at this way, it’s no surprise that McKinsey takes problem solving very seriously, testing for it during the recruiting process and then honing it, in McKinsey consultants, through immersion in a structured seven-step method. To discuss the art of problem solving, I sat down in California with McKinsey senior partner Hugo Sarrazin and also with Charles Conn. Charles is a former McKinsey partner, entrepreneur, executive, and coauthor of the book Bulletproof Problem Solving: The One Skill That Changes Everything [John Wiley & Sons, 2018].

Charles and Hugo, welcome to the podcast. Thank you for being here.

Hugo Sarrazin: Our pleasure.

Charles Conn: It’s terrific to be here.

Simon London: Problem solving is a really interesting piece of terminology. It could mean so many different things. I have a son who’s a teenage climber. They talk about solving problems. Climbing is problem solving. Charles, when you talk about problem solving, what are you talking about?

Charles Conn: For me, problem solving is the answer to the question “What should I do?” It’s interesting when there’s uncertainty and complexity, and when it’s meaningful because there are consequences. Your son’s climbing is a perfect example. There are consequences, and it’s complicated, and there’s uncertainty—can he make that grab? I think we can apply that same frame almost at any level. You can think about questions like “What town would I like to live in?” or “Should I put solar panels on my roof?”

You might think that’s a funny thing to apply problem solving to, but in my mind it’s not fundamentally different from business problem solving, which answers the question “What should my strategy be?” Or problem solving at the policy level: “How do we combat climate change?” “Should I support the local school bond?” I think these are all part and parcel of the same type of question, “What should I do?”

I’m a big fan of structured problem solving. By following steps, we can more clearly understand what problem it is we’re solving, what are the components of the problem that we’re solving, which components are the most important ones for us to pay attention to, which analytic techniques we should apply to those, and how we can synthesize what we’ve learned back into a compelling story. That’s all it is, at its heart.

I think sometimes when people think about seven steps, they assume that there’s a rigidity to this. That’s not it at all. It’s actually to give you the scope for creativity, which often doesn’t exist when your problem solving is muddled.

Simon London: You were just talking about the seven-step process. That’s what’s written down in the book, but it’s a very McKinsey process as well. Without getting too deep into the weeds, let’s go through the steps, one by one. You were just talking about problem definition as being a particularly important thing to get right first. That’s the first step. Hugo, tell us about that.

Hugo Sarrazin: It is surprising how often people jump past this step and make a bunch of assumptions. The most powerful thing is to step back and ask the basic questions—“What are we trying to solve? What are the constraints that exist? What are the dependencies?” Let’s make those explicit and really push the thinking and defining. At McKinsey, we spend an enormous amount of time in writing that little statement, and the statement, if you’re a logic purist, is great. You debate. “Is it an ‘or’? Is it an ‘and’? What’s the action verb?” Because all these specific words help you get to the heart of what matters.

Want to subscribe to The McKinsey Podcast ?

Simon London: So this is a concise problem statement.

Hugo Sarrazin: Yeah. It’s not like “Can we grow in Japan?” That’s interesting, but it is “What, specifically, are we trying to uncover in the growth of a product in Japan? Or a segment in Japan? Or a channel in Japan?” When you spend an enormous amount of time, in the first meeting of the different stakeholders, debating this and having different people put forward what they think the problem definition is, you realize that people have completely different views of why they’re here. That, to me, is the most important step.

Charles Conn: I would agree with that. For me, the problem context is critical. When we understand “What are the forces acting upon your decision maker? How quickly is the answer needed? With what precision is the answer needed? Are there areas that are off limits or areas where we would particularly like to find our solution? Is the decision maker open to exploring other areas?” then you not only become more efficient, and move toward what we call the critical path in problem solving, but you also make it so much more likely that you’re not going to waste your time or your decision maker’s time.

How often do especially bright young people run off with half of the idea about what the problem is and start collecting data and start building models—only to discover that they’ve really gone off half-cocked.

Hugo Sarrazin: Yeah.

Charles Conn: And in the wrong direction.

Simon London: OK. So step one—and there is a real art and a structure to it—is define the problem. Step two, Charles?

Charles Conn: My favorite step is step two, which is to use logic trees to disaggregate the problem. Every problem we’re solving has some complexity and some uncertainty in it. The only way that we can really get our team working on the problem is to take the problem apart into logical pieces.

What we find, of course, is that the way to disaggregate the problem often gives you an insight into the answer to the problem quite quickly. I love to do two or three different cuts at it, each one giving a bit of a different insight into what might be going wrong. By doing sensible disaggregations, using logic trees, we can figure out which parts of the problem we should be looking at, and we can assign those different parts to team members.

Simon London: What’s a good example of a logic tree on a sort of ratable problem?

Charles Conn: Maybe the easiest one is the classic profit tree. Almost in every business that I would take a look at, I would start with a profit or return-on-assets tree. In its simplest form, you have the components of revenue, which are price and quantity, and the components of cost, which are cost and quantity. Each of those can be broken out. Cost can be broken into variable cost and fixed cost. The components of price can be broken into what your pricing scheme is. That simple tree often provides insight into what’s going on in a business or what the difference is between that business and the competitors.

If we add the leg, which is “What’s the asset base or investment element?”—so profit divided by assets—then we can ask the question “Is the business using its investments sensibly?” whether that’s in stores or in manufacturing or in transportation assets. I hope we can see just how simple this is, even though we’re describing it in words.

When I went to work with Gordon Moore at the Moore Foundation, the problem that he asked us to look at was “How can we save Pacific salmon?” Now, that sounds like an impossible question, but it was amenable to precisely the same type of disaggregation and allowed us to organize what became a 15-year effort to improve the likelihood of good outcomes for Pacific salmon.

Simon London: Now, is there a danger that your logic tree can be impossibly large? This, I think, brings us onto the third step in the process, which is that you have to prioritize.

Charles Conn: Absolutely. The third step, which we also emphasize, along with good problem definition, is rigorous prioritization—we ask the questions “How important is this lever or this branch of the tree in the overall outcome that we seek to achieve? How much can I move that lever?” Obviously, we try and focus our efforts on ones that have a big impact on the problem and the ones that we have the ability to change. With salmon, ocean conditions turned out to be a big lever, but not one that we could adjust. We focused our attention on fish habitats and fish-harvesting practices, which were big levers that we could affect.

People spend a lot of time arguing about branches that are either not important or that none of us can change. We see it in the public square. When we deal with questions at the policy level—“Should you support the death penalty?” “How do we affect climate change?” “How can we uncover the causes and address homelessness?”—it’s even more important that we’re focusing on levers that are big and movable.

Would you like to learn more about our Strategy & Corporate Finance Practice ?

Simon London: Let’s move swiftly on to step four. You’ve defined your problem, you disaggregate it, you prioritize where you want to analyze—what you want to really look at hard. Then you got to the work plan. Now, what does that mean in practice?

Hugo Sarrazin: Depending on what you’ve prioritized, there are many things you could do. It could be breaking the work among the team members so that people have a clear piece of the work to do. It could be defining the specific analyses that need to get done and executed, and being clear on time lines. There’s always a level-one answer, there’s a level-two answer, there’s a level-three answer. Without being too flippant, I can solve any problem during a good dinner with wine. It won’t have a whole lot of backing.

Simon London: Not going to have a lot of depth to it.

Hugo Sarrazin: No, but it may be useful as a starting point. If the stakes are not that high, that could be OK. If it’s really high stakes, you may need level three and have the whole model validated in three different ways. You need to find a work plan that reflects the level of precision, the time frame you have, and the stakeholders you need to bring along in the exercise.

Charles Conn: I love the way you’ve described that, because, again, some people think of problem solving as a linear thing, but of course what’s critical is that it’s iterative. As you say, you can solve the problem in one day or even one hour.

Charles Conn: We encourage our teams everywhere to do that. We call it the one-day answer or the one-hour answer. In work planning, we’re always iterating. Every time you see a 50-page work plan that stretches out to three months, you know it’s wrong. It will be outmoded very quickly by that learning process that you described. Iterative problem solving is a critical part of this. Sometimes, people think work planning sounds dull, but it isn’t. It’s how we know what’s expected of us and when we need to deliver it and how we’re progressing toward the answer. It’s also the place where we can deal with biases. Bias is a feature of every human decision-making process. If we design our team interactions intelligently, we can avoid the worst sort of biases.

Simon London: Here we’re talking about cognitive biases primarily, right? It’s not that I’m biased against you because of your accent or something. These are the cognitive biases that behavioral sciences have shown we all carry around, things like anchoring, overoptimism—these kinds of things.

Both: Yeah.

Charles Conn: Availability bias is the one that I’m always alert to. You think you’ve seen the problem before, and therefore what’s available is your previous conception of it—and we have to be most careful about that. In any human setting, we also have to be careful about biases that are based on hierarchies, sometimes called sunflower bias. I’m sure, Hugo, with your teams, you make sure that the youngest team members speak first. Not the oldest team members, because it’s easy for people to look at who’s senior and alter their own creative approaches.

Hugo Sarrazin: It’s helpful, at that moment—if someone is asserting a point of view—to ask the question “This was true in what context?” You’re trying to apply something that worked in one context to a different one. That can be deadly if the context has changed, and that’s why organizations struggle to change. You promote all these people because they did something that worked well in the past, and then there’s a disruption in the industry, and they keep doing what got them promoted even though the context has changed.

Simon London: Right. Right.

Hugo Sarrazin: So it’s the same thing in problem solving.

Charles Conn: And it’s why diversity in our teams is so important. It’s one of the best things about the world that we’re in now. We’re likely to have people from different socioeconomic, ethnic, and national backgrounds, each of whom sees problems from a slightly different perspective. It is therefore much more likely that the team will uncover a truly creative and clever approach to problem solving.

Simon London: Let’s move on to step five. You’ve done your work plan. Now you’ve actually got to do the analysis. The thing that strikes me here is that the range of tools that we have at our disposal now, of course, is just huge, particularly with advances in computation, advanced analytics. There’s so many things that you can apply here. Just talk about the analysis stage. How do you pick the right tools?

Charles Conn: For me, the most important thing is that we start with simple heuristics and explanatory statistics before we go off and use the big-gun tools. We need to understand the shape and scope of our problem before we start applying these massive and complex analytical approaches.

Simon London: Would you agree with that?

Hugo Sarrazin: I agree. I think there are so many wonderful heuristics. You need to start there before you go deep into the modeling exercise. There’s an interesting dynamic that’s happening, though. In some cases, for some types of problems, it is even better to set yourself up to maximize your learning. Your problem-solving methodology is test and learn, test and learn, test and learn, and iterate. That is a heuristic in itself, the A/B testing that is used in many parts of the world. So that’s a problem-solving methodology. It’s nothing different. It just uses technology and feedback loops in a fast way. The other one is exploratory data analysis. When you’re dealing with a large-scale problem, and there’s so much data, I can get to the heuristics that Charles was talking about through very clever visualization of data.

You test with your data. You need to set up an environment to do so, but don’t get caught up in neural-network modeling immediately. You’re testing, you’re checking—“Is the data right? Is it sound? Does it make sense?”—before you launch too far.

Simon London: You do hear these ideas—that if you have a big enough data set and enough algorithms, they’re going to find things that you just wouldn’t have spotted, find solutions that maybe you wouldn’t have thought of. Does machine learning sort of revolutionize the problem-solving process? Or are these actually just other tools in the toolbox for structured problem solving?

Charles Conn: It can be revolutionary. There are some areas in which the pattern recognition of large data sets and good algorithms can help us see things that we otherwise couldn’t see. But I do think it’s terribly important we don’t think that this particular technique is a substitute for superb problem solving, starting with good problem definition. Many people use machine learning without understanding algorithms that themselves can have biases built into them. Just as 20 years ago, when we were doing statistical analysis, we knew that we needed good model definition, we still need a good understanding of our algorithms and really good problem definition before we launch off into big data sets and unknown algorithms.

Simon London: Step six. You’ve done your analysis.

Charles Conn: I take six and seven together, and this is the place where young problem solvers often make a mistake. They’ve got their analysis, and they assume that’s the answer, and of course it isn’t the answer. The ability to synthesize the pieces that came out of the analysis and begin to weave those into a story that helps people answer the question “What should I do?” This is back to where we started. If we can’t synthesize, and we can’t tell a story, then our decision maker can’t find the answer to “What should I do?”

Simon London: But, again, these final steps are about motivating people to action, right?

Charles Conn: Yeah.

Simon London: I am slightly torn about the nomenclature of problem solving because it’s on paper, right? Until you motivate people to action, you actually haven’t solved anything.

Charles Conn: I love this question because I think decision-making theory, without a bias to action, is a waste of time. Everything in how I approach this is to help people take action that makes the world better.

Simon London: Hence, these are absolutely critical steps. If you don’t do this well, you’ve just got a bunch of analysis.

Charles Conn: We end up in exactly the same place where we started, which is people speaking across each other, past each other in the public square, rather than actually working together, shoulder to shoulder, to crack these important problems.

Simon London: In the real world, we have a lot of uncertainty—arguably, increasing uncertainty. How do good problem solvers deal with that?

Hugo Sarrazin: At every step of the process. In the problem definition, when you’re defining the context, you need to understand those sources of uncertainty and whether they’re important or not important. It becomes important in the definition of the tree.

You need to think carefully about the branches of the tree that are more certain and less certain as you define them. They don’t have equal weight just because they’ve got equal space on the page. Then, when you’re prioritizing, your prioritization approach may put more emphasis on things that have low probability but huge impact—or, vice versa, may put a lot of priority on things that are very likely and, hopefully, have a reasonable impact. You can introduce that along the way. When you come back to the synthesis, you just need to be nuanced about what you’re understanding, the likelihood.

Often, people lack humility in the way they make their recommendations: “This is the answer.” They’re very precise, and I think we would all be well-served to say, “This is a likely answer under the following sets of conditions” and then make the level of uncertainty clearer, if that is appropriate. It doesn’t mean you’re always in the gray zone; it doesn’t mean you don’t have a point of view. It just means that you can be explicit about the certainty of your answer when you make that recommendation.

Simon London: So it sounds like there is an underlying principle: “Acknowledge and embrace the uncertainty. Don’t pretend that it isn’t there. Be very clear about what the uncertainties are up front, and then build that into every step of the process.”

Hugo Sarrazin: Every step of the process.

Simon London: Yeah. We have just walked through a particular structured methodology for problem solving. But, of course, this is not the only structured methodology for problem solving. One that is also very well-known is design thinking, which comes at things very differently. So, Hugo, I know you have worked with a lot of designers. Just give us a very quick summary. Design thinking—what is it, and how does it relate?

Hugo Sarrazin: It starts with an incredible amount of empathy for the user and uses that to define the problem. It does pause and go out in the wild and spend an enormous amount of time seeing how people interact with objects, seeing the experience they’re getting, seeing the pain points or joy—and uses that to infer and define the problem.

Simon London: Problem definition, but out in the world.

Hugo Sarrazin: With an enormous amount of empathy. There’s a huge emphasis on empathy. Traditional, more classic problem solving is you define the problem based on an understanding of the situation. This one almost presupposes that we don’t know the problem until we go see it. The second thing is you need to come up with multiple scenarios or answers or ideas or concepts, and there’s a lot of divergent thinking initially. That’s slightly different, versus the prioritization, but not for long. Eventually, you need to kind of say, “OK, I’m going to converge again.” Then you go and you bring things back to the customer and get feedback and iterate. Then you rinse and repeat, rinse and repeat. There’s a lot of tactile building, along the way, of prototypes and things like that. It’s very iterative.

Simon London: So, Charles, are these complements or are these alternatives?

Charles Conn: I think they’re entirely complementary, and I think Hugo’s description is perfect. When we do problem definition well in classic problem solving, we are demonstrating the kind of empathy, at the very beginning of our problem, that design thinking asks us to approach. When we ideate—and that’s very similar to the disaggregation, prioritization, and work-planning steps—we do precisely the same thing, and often we use contrasting teams, so that we do have divergent thinking. The best teams allow divergent thinking to bump them off whatever their initial biases in problem solving are. For me, design thinking gives us a constant reminder of creativity, empathy, and the tactile nature of problem solving, but it’s absolutely complementary, not alternative.

Simon London: I think, in a world of cross-functional teams, an interesting question is do people with design-thinking backgrounds really work well together with classical problem solvers? How do you make that chemistry happen?

Hugo Sarrazin: Yeah, it is not easy when people have spent an enormous amount of time seeped in design thinking or user-centric design, whichever word you want to use. If the person who’s applying classic problem-solving methodology is very rigid and mechanical in the way they’re doing it, there could be an enormous amount of tension. If there’s not clarity in the role and not clarity in the process, I think having the two together can be, sometimes, problematic.

The second thing that happens often is that the artifacts the two methodologies try to gravitate toward can be different. Classic problem solving often gravitates toward a model; design thinking migrates toward a prototype. Rather than writing a big deck with all my supporting evidence, they’ll bring an example, a thing, and that feels different. Then you spend your time differently to achieve those two end products, so that’s another source of friction.

Now, I still think it can be an incredibly powerful thing to have the two—if there are the right people with the right mind-set, if there is a team that is explicit about the roles, if we’re clear about the kind of outcomes we are attempting to bring forward. There’s an enormous amount of collaborativeness and respect.

Simon London: But they have to respect each other’s methodology and be prepared to flex, maybe, a little bit, in how this process is going to work.

Hugo Sarrazin: Absolutely.

Simon London: The other area where, it strikes me, there could be a little bit of a different sort of friction is this whole concept of the day-one answer, which is what we were just talking about in classical problem solving. Now, you know that this is probably not going to be your final answer, but that’s how you begin to structure the problem. Whereas I would imagine your design thinkers—no, they’re going off to do their ethnographic research and get out into the field, potentially for a long time, before they come back with at least an initial hypothesis.

Want better strategies? Become a bulletproof problem solver

Hugo Sarrazin: That is a great callout, and that’s another difference. Designers typically will like to soak into the situation and avoid converging too quickly. There’s optionality and exploring different options. There’s a strong belief that keeps the solution space wide enough that you can come up with more radical ideas. If there’s a large design team or many designers on the team, and you come on Friday and say, “What’s our week-one answer?” they’re going to struggle. They’re not going to be comfortable, naturally, to give that answer. It doesn’t mean they don’t have an answer; it’s just not where they are in their thinking process.

Simon London: I think we are, sadly, out of time for today. But Charles and Hugo, thank you so much.

Charles Conn: It was a pleasure to be here, Simon.

Hugo Sarrazin: It was a pleasure. Thank you.

Simon London: And thanks, as always, to you, our listeners, for tuning into this episode of the McKinsey Podcast . If you want to learn more about problem solving, you can find the book, Bulletproof Problem Solving: The One Skill That Changes Everything , online or order it through your local bookstore. To learn more about McKinsey, you can of course find us at McKinsey.com.

Charles Conn is CEO of Oxford Sciences Innovation and an alumnus of McKinsey’s Sydney office. Hugo Sarrazin is a senior partner in the Silicon Valley office, where Simon London, a member of McKinsey Publishing, is also based.

Explore a career with us

Related articles.

Strategy to beat the odds

Five routes to more innovative problem solving

• 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

Problem-solving: Steps, strategies, and skills

By Alyssa Zacharias

Your team hits a bump in the road with a new client: They’d like to add extra objectives to the scope without changing the schedule. The mood grows tense as everyone frets about how to rearrange their calendars. 

One team member suggests breaking down the new scope into small, more manageable parts. One by one, you divide each deliverable into new tasks and prioritize them based on the team's calendar and resources. You push back non-urgent tasks and delegate others to different teams. Slowly, all the pieces start to fit together. What seemed like an impossible challenge is now a series of connected dots. The meeting wraps up with a clear and actionable solution, and everyone gets to work. 

This hypothetical scenario might sound too good to be true, but it’s well within your reach. It’s the perfect example of how establishing problem-solving steps can set your team up for success. Let’s explore how to prepare your team for the next project’s hurdles. 

What’s problem-solving? 

Problem-solving is a strategy-driven approach that uses logical thinking, creativity, and collaboration to analyze obstacles and build actionable solutions to overcome them. Life rarely goes exactly to plan, and problem-solving skills remove barriers that stop your team from reaching objectives when things go awry. 

You and your team’s ability to embrace different approaches to solving problems marks the difference between staying ahead or behind the curve. But problem-solving isn’t a single skill. Good problem-solvers pull from a list of soft skills, such as analytical thinking, flexibility, and curiosity — which are among the top 10 most sought-after job skills .  

Bringing problem-solvers onto the team is just the start. Nurturing a supportive environment that encourages teamwork, leadership, and the ability to make mistakes is essential for innovative solutions to serious roadblocks. After all, healthy work environments encourage out-of-the-box thinking and accountability that spawn effective solutions.

Problem-solving process: 6 key steps 

Problem-solving starts with carefully dissecting an issue, evaluating all its parts, and then brainstorming an action plan to rise above the challenge. Whether you’re working independently or collaborating with a big team, following a standard procedure can make the process more productive. 

Here are six steps to solve problems and get your project back on track: 

1. Define the problem

The first step might sound obvious, but figuring out how to solve a problem starts with a clear definition. No matter how big or small the issue is, laying it out as clearly as possible guides the rest of the process, pushing your brainstorming, collaboration, and solutions down the right path. Plus, a succinct definition can help you foresee potential project management risks and build a risk register to avoid more challenging situations in the future.  

You can start by asking yourself a few basic questions to understand the depth and scope of the issue: 

Who does this problem involve? Who’s equipped with the knowledge and skills to solve this problem? 

What’s the root cause? What other problems does it cause?

Where did this problem take place?

When did the problem start? When does it need a resolution?

Why does it impact workflows? Why do you need to solve this problem now?

Once you’ve dissected the issue, write it down. Putting pen to paper forces you to think through the obstacle, and the result can serve as a reference point as you work toward the solution. 

Be careful not to leave any room for ambiguity in your problem statement by identifying the specific situation and timing. Rather than “I don’t have enough time to complete a project,” write a definition like “I need to complete an important project within three days, but I have three other tasks due on the same day, which collectively require 20 hours of work.” A detailed problem statement provides a crystal clear picture of the problem, helping you be more productive during brainstorming and implementation.

2. Brainstorm possible solutions

With your clearly defined problem in hand, it’s time to get creative. Effective brainstorming focuses on quantity rather than quality. The intention is to build diverse options without overanalyzing them — that’ll come later. 

Brainstorm as many potential solutions as possible, no matter how quirky or out-of-the-box. Aim to generate a list of 10–15 possible paths and encourage your mind to wander, moving away from obvious solutions to potentially innovative ones. 

3. Consider all your alternatives

It may be tempting to immediately discard unfamiliar ideas and embrace others within your comfort zone. But as long as an idea directly addresses your problem, give it the benefit of the doubt. 

Map out every idea, including relevant details like costs, step-by-step process, time frames, and the people involved. If the idea doesn't align with your needs or resources, toss it. Order the remaining alternatives by preference and evaluate their advantages and disadvantages. 

4. Agree on a solution

With all the information in front of you, it’s time to decide on the best course of action. Narrow down all your choices, seeking out efficiency and practicality. For complex problems and solutions, managers and colleagues experienced in crisis management can offer valuable insights. 

5. Take action

After choosing the best solution, it’s time to implement it. Track progress throughout the entire process to avoid unexpected delays and unwelcome surprises. And consider using an issue tracker to analyze unexpected bumps in the road and learn from them — just be sure to leave room in the plan to adapt to challenges when necessary. 

6. Evaluate the outcome

Analyzing the success of your solution encourages learning from failures and promotes future success. Evaluate the effectiveness of the chosen solution and decide if a different course of action may be necessary. You might ask yourself some of the following questions: 

Was the problem solved within the expected timeframe?

Were any resources overused or wasted?

What was learned during the problem-solving process? 

Were there any communication breakdowns or conflicts? 

Will a policy or organizational change help prevent this problem from occurring in the future?

You may find you need to simplify the process even further. Using your insights, focus on the solution instead of the problem. Staying flexible and open-minded will help you rise to the next challenge. 

Problem-solving example

To understand how you can apply the problem-solving steps above, let’s look at a common problem for product, IT, and development teams: apps that crash when updates are rolled out. 

To clearly define the problem, the team collects user feedback and crash reports to pinpoint specific scenarios where the app fails. They discover that crashes most often occur on devices using old versions of the operating system. With this clear problem definition, they align on where to focus their efforts. 

Together, they brainstorm several solutions, including rolling back the update, creating a solution specifically for older operating systems, or rolling out a marketing campaign to convince users to update. 

After debating all the alternatives, they decide to develop a patch. Although it’s not the most time-effective solution, it won’t alienate users by rolling back features or forcing them to update. They might also take on extra initiatives along the way, like making the app less resource-intensive to run smoothly on more devices. 

Throughout the implementation, the team monitors feedback. Crash reports decrease significantly, and positive reviews increase. After achieving the desired outcome, the team performs regular diagnostics to spot room for improvement and prevent future mishaps.

4 problem-solving strategies

Learning different strategies to identify and solve problems empowers you to stay flexible and resilient, even in the most challenging circumstances. Here are four common problem-solving strategies to try out: 

Trial and error: There’s rarely a single “right” answer to your problem. A trial-and-error approach (or A/B testing) encourages your team to experiment with solutions and identify the best one. Of course, this is only productive if you have the necessary time and resources.

Working backward: Using your imagination, visualize your problem solved. Now, work backward, retracing each step to your current place. Involve team leaders in this process and share ideas until you have a solid plan of action.

Use an old solution: You don’t always have to reinvent the wheel. Think about how you’ve solved similar issues in the past. If one of your old solutions works, use it again. 

Draw it out: Visualizing every part of a problem isn’t always easy. Using fishbone diagrams, concept maps, or flowcharts ensures you make connections and account for every last detail. Plus, a diagram will make the roadblock easier to understand when you address it with the rest of the team. But don’t tackle this work alone — the more heads you involve, the more perspectives you can draw upon. Someone else at the table will likely think of something you missed.

Problem-solving skills

Effective problem-solving means drawing upon several soft skills in your tool belt. Here are ten of the most valuable skills for overcoming obstacles:

Critical thinking

Adaptability

Collaboration

Effective communication 

Active listening

Persistence

Decision-making

Solve your next problem with Notion

Whether big or small, incorporating time-tested problem-solving steps to overcome challenges will help your team overcome future barriers to success. Try different techniques, like SWOT Analysis , to adapt to the next challenging situation swiftly and effectively. 

You can assist your problem-solving efforts with Notion templates for support task lists and reporting bugs . Plus, you can — and should — use Notion’s issue tracker to monitor the action plan you choose to put in place.

Keep reading

7 idea generation methods for out-of-the-box thinking

5 decision-making models to streamline collaboration and reach success

Discovering new workplace opportunities with systems thinking

Turn ideas into reality with an agile engineering design process

A comprehensive guide to writing problem statements

Handle roadblocks faster with a root cause analysis

Get going on web or desktop, we also have mac & windows apps to match., we also have ios & android apps to match..

Desktop app

• Product overview
• All features
• Latest feature release
• App integrations

CAPABILITIES

• project icon Project management
• Project views
• Custom fields
• Status updates
• goal icon Goals and reporting
• Reporting dashboards
• workflow icon Workflows and automation
• portfolio icon Resource management
• Capacity planning
• Time tracking
• my-task icon Admin and security
• Admin console
• asana-intelligence icon Asana AI
• list icon Personal
• premium icon Starter
• briefcase icon Advanced
• Goal management
• Organizational planning
• Campaign management
• Creative production
• Content calendars
• Marketing strategic planning
• Resource planning
• Project intake
• Product launches
• Employee onboarding
• View all uses arrow-right icon
• Project plans
• Team goals & objectives
• Team continuity
• Meeting agenda
• View all templates arrow-right icon
• Work management resources Discover best practices, watch webinars, get insights
• Customer stories See how the world's best organizations drive work innovation with Asana
• Help Center Get lots of tips, tricks, and advice to get the most from Asana
• Asana Academy Sign up for interactive courses and webinars to learn Asana
• Developers Learn more about building apps on the Asana platform
• Community programs Connect with and learn from Asana customers around the world
• Events Find out about upcoming events near you
• Partners Learn more about our partner programs
• Asana for nonprofits Get more information on our nonprofit discount program, and apply.

Featured Reads

• Collaboration |
• Turn your team into skilled problem sol ...

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

Picture this, you're handling your daily tasks at work and your boss calls you in and says, "We have a problem." 

Unfortunately, we don't live in a world in which problems are instantly resolved with the snap of our fingers. Knowing how to effectively solve problems is an important professional skill to hone. If you have a problem that needs to be solved, what is the right process to use to ensure you get the most effective solution?

In this article we'll break down the problem-solving process and how you can find the most effective solutions for complex problems.

What is problem solving? 

Problem solving is the process of finding a resolution for a specific issue or conflict. There are many possible solutions for solving a problem, which is why it's important to go through a problem-solving process to find the best solution. You could use a flathead screwdriver to unscrew a Phillips head screw, but there is a better tool for the situation. Utilizing common problem-solving techniques helps you find the best solution to fit the needs of the specific situation, much like using the right tools.

Decision-making tools for agile businesses

In this ebook, learn how to equip employees to make better decisions—so your business can pivot, adapt, and tackle challenges more effectively than your competition.

4 steps to better problem solving

While it might be tempting to dive into a problem head first, take the time to move step by step. Here’s how you can effectively break down the problem-solving process with your team:

1. Identify the problem that needs to be solved

One of the easiest ways to identify a problem is to ask questions. A good place to start is to ask journalistic questions, like:

Who : Who is involved with this problem? Who caused the problem? Who is most affected by this issue?

What: What is happening? What is the extent of the issue? What does this problem prevent from moving forward?

Where: Where did this problem take place? Does this problem affect anything else in the immediate area? 

When: When did this problem happen? When does this problem take effect? Is this an urgent issue that needs to be solved within a certain timeframe?

Why: Why is it happening? Why does it impact workflows?

How: How did this problem occur? How is it affecting workflows and team members from being productive?

Asking journalistic questions can help you define a strong problem statement so you can highlight the current situation objectively, and create a plan around that situation.

Here’s an example of how a design team uses journalistic questions to identify their problem:

Overarching problem: Design requests are being missed

Who: Design team, digital marketing team, web development team

What: Design requests are forgotten, lost, or being created ad hoc.

Where: Email requests, design request spreadsheet

When: Missed requests on January 20th, January 31st, February 4th, February 6th

How : Email request was lost in inbox and the intake spreadsheet was not updated correctly. The digital marketing team had to delay launching ads for a few days while design requests were bottlenecked. Designers had to work extra hours to ensure all requests were completed.

In this example, there are many different aspects of this problem that can be solved. Using journalistic questions can help you identify different issues and who you should involve in the process.

2. Brainstorm multiple solutions

If at all possible, bring in a facilitator who doesn't have a major stake in the solution. Bringing an individual who has little-to-no stake in the matter can help keep your team on track and encourage good problem-solving skills.

Here are a few brainstorming techniques to encourage creative thinking:

Brainstorm alone before hand: Before you come together as a group, provide some context to your team on what exactly the issue is that you're brainstorming. This will give time for you and your teammates to have some ideas ready by the time you meet.

Say yes to everything (at first): When you first start brainstorming, don't say no to any ideas just yet—try to get as many ideas down as possible. Having as many ideas as possible ensures that you’ll get a variety of solutions. Save the trimming for the next step of the strategy. 

Talk to team members one-on-one: Some people may be less comfortable sharing their ideas in a group setting. Discuss the issue with team members individually and encourage them to share their opinions without restrictions—you might find some more detailed insights than originally anticipated.

Break out of your routine: If you're used to brainstorming in a conference room or over Zoom calls, do something a little different! Take your brainstorming meeting to a coffee shop or have your Zoom call while you're taking a walk. Getting out of your routine can force your brain out of its usual rut and increase critical thinking.

3. Define the solution

After you brainstorm with team members to get their unique perspectives on a scenario, it's time to look at the different strategies and decide which option is the best solution for the problem at hand. When defining the solution, consider these main two questions: What is the desired outcome of this solution and who stands to benefit from this solution? 

Set a deadline for when this decision needs to be made and update stakeholders accordingly. Sometimes there's too many people who need to make a decision. Use your best judgement based on the limitations provided to do great things fast.

4. Implement the solution

To implement your solution, start by working with the individuals who are as closest to the problem. This can help those most affected by the problem get unblocked. Then move farther out to those who are less affected, and so on and so forth. Some solutions are simple enough that you don’t need to work through multiple teams.

After you prioritize implementation with the right teams, assign out the ongoing work that needs to be completed by the rest of the team. This can prevent people from becoming overburdened during the implementation plan . Once your solution is in place, schedule check-ins to see how the solution is working and course-correct if necessary.

Implement common problem-solving strategies

There are a few ways to go about identifying problems (and solutions). Here are some strategies you can try, as well as common ways to apply them:

Trial and error

Trial and error problem solving doesn't usually require a whole team of people to solve. To use trial and error problem solving, identify the cause of the problem, and then rapidly test possible solutions to see if anything changes. 

This problem-solving method is often used in tech support teams through troubleshooting.

The 5 whys problem-solving method helps get to the root cause of an issue. You start by asking once, “Why did this issue happen?” After answering the first why, ask again, “Why did that happen?” You'll do this five times until you can attribute the problem to a root cause. 

This technique can help you dig in and find the human error that caused something to go wrong. More importantly, it also helps you and your team develop an actionable plan so that you can prevent the issue from happening again.

Here’s an example:

Problem: The email marketing campaign was accidentally sent to the wrong audience.

“Why did this happen?” Because the audience name was not updated in our email platform.

“Why were the audience names not changed?” Because the audience segment was not renamed after editing. 

“Why was the audience segment not renamed?” Because everybody has an individual way of creating an audience segment.

“Why does everybody have an individual way of creating an audience segment?” Because there is no standardized process for creating audience segments. 

“Why is there no standardized process for creating audience segments?” Because the team hasn't decided on a way to standardize the process as the team introduced new members. 

In this example, we can see a few areas that could be optimized to prevent this mistake from happening again. When working through these questions, make sure that everyone who was involved in the situation is present so that you can co-create next steps to avoid the same problem. 

A SWOT analysis

A SWOT analysis can help you highlight the strengths and weaknesses of a specific solution. SWOT stands for:

Strength: Why is this specific solution a good fit for this problem? 

Weaknesses: What are the weak points of this solution? Is there anything that you can do to strengthen those weaknesses?

Opportunities: What other benefits could arise from implementing this solution?

Threats: Is there anything about this decision that can detrimentally impact your team?

As you identify specific solutions, you can highlight the different strengths, weaknesses, opportunities, and threats of each solution. 

This particular problem-solving strategy is good to use when you're narrowing down the answers and need to compare and contrast the differences between different solutions. 

Even more successful problem solving

After you’ve worked through a tough problem, don't forget to celebrate how far you've come. Not only is this important for your team of problem solvers to see their work in action, but this can also help you become a more efficient, effective , and flexible team. The more problems you tackle together, the more you’ll achieve. 

Looking for a tool to help solve problems on your team? Track project implementation with a work management tool like Asana .

Related resources

10 tips to improve nonverbal communication

Scaling clinical trial management software with PM solutions

How to build your critical thinking skills in 7 steps (with examples)

4 ways to establish roles and responsibilities for team success

The 5 Steps of Problem Solving

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

Defining Problem Solving

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

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

[1] Problem solving on Wikipedia

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

The Five Steps of Problem Solving

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

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

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

1. Define the Problem

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

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

2. Brainstorm Ideas

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

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

3. Decide on a Solution

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

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

4. Implement the Solution

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

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

5. Review the Results

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

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

Improving Problem Solving Skills

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

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

THIS FREE 129 SECOND QUIZ WILL SHOW YOU

what is your humor persona?

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

you might also be interested in...

What to Expect on your First Open Mic Night

So, you’re doing your first open mic! You’re excited, a little nervous (no need to be), happy and we are […]

Achieving Your Goals Through Daily Habits

Way back in December of 2011 (holy wow that was already 4 years ago), I wrote about why people fail […]

Celebrity Comics Babble Book Review

We recently read Celebrity Comics Babble A Romp Through a Red Carpet Line-up of Interviews compiled by Marry Ann Pierro […]

22 thoughts on “The 5 Steps of Problem Solving”

very helpful and informative training

Thank you for the information

YOU ARE AFOOL

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

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

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

It is well defined steps, thank you.

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

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

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

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

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

Well in our school teacher teach us –

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

Pleace write about it …

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

i know the steps of doing some guideline for problem solving

steps are very useful to solve my problem

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

I like the steps for problem solving

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

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

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

Leave a Comment Cancel Reply

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

Humor Persona - Template B2B

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

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

Humor Persona - Main B2C

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

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

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

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

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

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

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

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

What is Problem-Solving?

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

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

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

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

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

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

The Five Stages of Problem-Solving

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

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

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

Step 1: Defining The Problem

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

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

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

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

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

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

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

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

Steer clear of formulations like:

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

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

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

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

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

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

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

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

Learn more about facilitation and workshopping in our FREE FACILITATION COMMUNITY

Step 2: ideating a solution.

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

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

Our best advice?

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

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

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

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

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

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

Step 3: Choosing the Best Strategy & Committing

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

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

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

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

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

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

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

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

Join our FREE community and connect with other Facilitators and Workshoppers

Step 4: implementing your solution.

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

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

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

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

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

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

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

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

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

Bottom line?  

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

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

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

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

Cue in….prototyping. 

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

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

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

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

Step 5: Analyzing the Results

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

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

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

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

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

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

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

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

Problem-Solving Skills 

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

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

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

How to Improve Your Problem-Solving Skills

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

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

• Practice, Practice, Practice

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

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

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

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

• Use a tried and tested problem-solving workshop

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

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

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

• Learn from your peers

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

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

• Learn & Practice the best problem-solving exercises

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

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

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

Anastasia Ushakova

Brand Strategist, Digital Marketer, and a Workshopper.

When Do You Need a Facilitator?

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

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

How To Improve Team Collaboration

• Soft skills
• What is a credential?
• Why do a credential?
• How do credentials work?
• Selecting your level
• How will I be assessed?
• Benefits for professionals
• Benefits for organisations
• Benefits for postgraduates

Problem solving techniques: Steps and methods

Posted on May 29, 2019

Constant disruption has become a hallmark of the modern workforce and organisations want problem solving skills to combat this. Employers need people who can respond to change – be that evolving technology, new competitors, different models for doing business, or any of the other transformations that have taken place in recent years.

In addition, problem solving techniques encompass many of the other top skills employers seek . For example, LinkedIn’s list of the most in-demand soft skills of 2019 includes creativity, collaboration and adaptability, all of which fall under the problem-solving umbrella.

Despite its importance, many employees misunderstand what the problem solving method really involves.

What constitutes effective problem solving?

Effective problem solving doesn’t mean going away and coming up with an answer immediately. In fact, this isn’t good problem solving at all, because you’ll be running with the first solution that comes into your mind, which often isn’t the best.

Instead, you should look at problem solving more as a process with several steps involved that will help you reach the best outcome. Those steps are:

• Define the problem
• List all the possible solutions
• Evaluate the options
• Select the best solution
• Create an implementation plan
• Communicate your solution

Let’s look at each step in a little more detail.

1. Define the problem

The first step to solving a problem is defining what the problem actually is – sounds simple, right? Well no. An effective problem solver will take the thoughts of everyone involved into account, but different people might have different ideas on what the root cause of the issue really is. It’s up to you to actively listen to everyone without bringing any of your own preconceived notions to the conversation. Learning to differentiate facts from opinion is an essential part of this process.

An effective problem solver will take the opinions of everyone involved into account

The same can be said of data. Depending on what the problem is, there will be varying amounts of information available that will help you work out what’s gone wrong. There should be at least some data involved in any problem, and it’s up to you to gather as much as possible and analyse it objectively.

2. List all the possible solutions

Once you’ve identified what the real issue is, it’s time to think of solutions. Brainstorming as many solutions as possible will help you arrive at the best answer because you’ll be considering all potential options and scenarios. You should take everyone’s thoughts into account when you’re brainstorming these ideas, as well as all the insights you’ve gleaned from your data analysis. It also helps to seek input from others at this stage, as they may come up with solutions you haven’t thought of.

Depending on the type of problem, it can be useful to think of both short-term and long-term solutions, as some of your options may take a while to implement.

3. Evaluate the options

Each option will have pros and cons, and it’s important you list all of these, as well as how each solution could impact key stakeholders. Once you’ve narrowed down your options to three or four, it’s often a good idea to go to other employees for feedback just in case you’ve missed something. You should also work out how each option ties in with the broader goals of the business.

There may be a way to merge two options together in order to satisfy more people.

4. Select an option

Only now should you choose which solution you’re going to go with. What you decide should be whatever solves the problem most effectively while also taking the interests of everyone involved into account. There may be a way to merge two options together in order to satisfy more people.

5. Create an implementation plan

At this point you might be thinking it’s time to sit back and relax – problem solved, right? There are actually two more steps involved if you want your problem solving method to be truly effective. The first is to create an implementation plan. After all, if you don’t carry out your solution effectively, you’re not really solving the problem at all. 

Create an implementation plan on how you will put your solution into practice. One problem solving technique that many use here is to introduce a testing and feedback phase just to make sure the option you’ve selected really is the most viable. You’ll also want to include any changes to your solution that may occur in your implementation plan, as well as how you’ll monitor compliance and success.

6. Communicate your solution

There’s one last step to consider as part of the problem solving methodology, and that’s communicating your solution . Without this crucial part of the process, how is anyone going to know what you’ve decided? Make sure you communicate your decision to all the people who might be impacted by it. Not everyone is going to be 100 per cent happy with it, so when you communicate you must give them context. Explain exactly why you’ve made that decision and how the pros mean it’s better than any of the other options you came up with.

Prove your problem solving skills with Deakin

Employers are increasingly seeking soft skills, but unfortunately, while you can show that you’ve got a degree in a subject, it’s much harder to prove you’ve got proficiency in things like problem solving skills. But this is changing thanks to Deakin’s micro-credentials. These are university-level micro-credentials that provide an authoritative and third-party assessment of your capabilities in a range of areas, including problem solving. Reach out today for more information .

Building future workplaces

5 Simple Steps to Effective Problem Solving

The ability to solve problems is a crucial skill in the modern workplace. It can make the difference between success and failure, and it can help you navigate the complexities of a fast-paced environment. But what exactly is effective problem solving? And how can you develop the skills needed to solve problems efficiently and effectively?

Effective problem solving involves several key steps that can help you identify the root cause of a problem, develop a plan of action, and implement that plan to achieve a successful outcome . Here are five simple steps you can take to develop your problem-solving skills and tackle any challenge that comes your way in the workplace.

Introduction

Have you ever found yourself in a situation where you’re faced with a workplace problem, and you’re not sure where to start? Whether it’s a customer complaint, a team conflict, or a project delay, it’s essential to address it promptly to maintain productivity and morale. In this article, we’ll provide practical steps that can help you effectively solve problems at your workplace.

Step 1: Define the Problem

The first step in effective problem solving is to define the problem clearly. Take the time to analyze the issue and gather as much information as possible. It’s crucial to identify the cause of the problem and its impact on your team or organization. For example, if a team member is underperforming, it’s essential to understand the root cause of the issue and how it’s affecting the team’s productivity. Is it a lack of training, motivation, or resources? Are there external factors, such as personal issues or workload, that are affecting their performance?

Once you have a clear understanding of the problem, you can begin to develop a plan of action to address it. It’s important to involve all stakeholders in this process, including those who are directly affected by the problem, to ensure that you have a complete picture of the situation. Involving others in the process can also help you gain different perspectives and insights, which can be valuable in developing an effective solution.

Step 2: Brainstorm Possible Solutions

After identifying the problem, the next step is to brainstorm possible solutions. It’s important to be creative and come up with as many solutions as possible, even if they seem unrealistic or impractical. Brainstorming can be done individually or in a group setting, where team members can bounce ideas off each other. In a group setting, it’s important to create an open and safe environment where everyone feels comfortable sharing their ideas. Remember to focus on generating ideas, without evaluating or criticizing them during the brainstorming session.

Once you have a list of possible solutions, evaluate each one based on their feasibility, potential impact, and costs. It’s important to consider the pros and cons of each solution before selecting the most appropriate one. Keep in mind that the solution may not be perfect, but it should be the best one available given the resources and constraints. By considering different options, you can increase the chances of finding an effective solution that addresses the problem.

Step 3: Evaluate the Solutions

When evaluating the solutions, it’s important to keep an open mind and consider different perspectives. Seek feedback from other team members or colleagues who may have a different point of view. It’s also important to consider the long-term effects of each solution, rather than just the immediate impact. For instance, while changing the project scope may seem like a quick fix to a delayed project, it could cause further delays or even impact the project’s success in the long run.

During the evaluation process, it’s essential to prioritize solutions based on their impact on the problem and their feasibility. Consider the resources, time, and effort required to implement each solution. Some solutions may be quick fixes that can be implemented immediately, while others may require more planning and preparation. It’s important to choose a solution that addresses the problem effectively while also being feasible to implement within the given resources and timeframe.

It’s also important to remember that not all solutions may work as expected. Be prepared to modify or pivot to a different solution if the initial solution does not yield the desired results. Additionally, ensure that the chosen solution aligns with the company’s policies and values and does not violate any ethical standards.

Step 4: Implement the Solution

Implementing the chosen solution requires careful planning and execution. The team needs to work together to ensure that the solution is implemented smoothly and efficiently. The plan should include a timeline, specific tasks, and deadlines. Assigning roles and responsibilities to each team member is crucial to ensure that everyone understands their role in the implementation process.

Effective communication is also essential during the implementation phase. The team should communicate regularly to discuss progress, identify any obstacles, and adjust the plan if necessary. For example, if the team decides to implement a new customer service strategy, they should train the customer service team, provide them with the necessary tools, and communicate the new strategy to customers.

It’s also important to track the progress of the implementation to ensure that everything is on track. Regular check-ins can help identify any problems early on and provide an opportunity to address them before they become bigger issues.

Step 5: Monitor and Adjust

Monitoring and adjusting the solution is crucial in ensuring that the problem is fully resolved. It’s essential to track the progress of the solution and evaluate its effectiveness. If the solution is not working as planned, it’s important to adjust it accordingly. This step requires flexibility and open communication among team members.

For example, if the team decided to adjust the project timeline, they should monitor the progress regularly and make adjustments if necessary. They should also communicate any changes to the stakeholders involved in the project. If the new timeline is not working, the team should be open to making further adjustments, such as revising the project scope or adding more resources.

Feedback plays a vital role in this step. It’s important to gather feedback from team members and stakeholders to ensure that the solution is meeting their needs. Feedback can also help identify any potential issues that may arise and allow the team to address them promptly.

Learning from mistakes is also an important aspect of effective problem solving. Every problem presents an opportunity to learn and grow. By reflecting on the process and the outcome, team members can identify areas for improvement and apply them in future problem-solving situations.

So, there you have it – a five-step process to solve any workplace problem like a pro! Whether it’s a pesky customer complaint, a tricky team conflict, or a stubborn project delay, you can tackle it with ease.

Remember, the first step is to define the problem – analyze it, gather information, and understand the root cause. Next, brainstorm possible solutions, even if they seem unrealistic or impractical. Get creative and come up with as many solutions as possible!

After that, evaluate the solutions by identifying their pros and cons, and choose the one that’s most feasible and practical. Make sure to consider the potential risks and benefits of each solution. Then, it’s time to implement the most practical solution. Develop a plan, communicate it to everyone involved, and assign roles and responsibilities.

Last but not least, monitor the progress and adjust the solution if necessary. Keep track of the progress and be open to feedback. Remember, learning from your mistakes is the key to success!

So, the next time you face a workplace problem, take a deep breath and follow these simple steps. You’ll be able to find a solution that works for everyone and become a valuable asset to your team or organization. With effective problem solving skills, you can maintain productivity, boost morale, and achieve success!

• DISC Certification
• Emotional Intelligence Using DISC
• DISC Insights for First-Time Managers
• Team Building Using DISC
• Sales Training with DISC
• DISC for Customer Service
• Conflict Management Using DISC
• Communication Skills Using DISC
• Vision Mission Values Workshop
• Competency Mapping
• Agile Culture
• Micro Learning Labs™
• Coaching Skills For Managers
• BEI Certification Program
• Design Thinking Certification
• Synergogy Blog
• Leadership Immersion Retreat

Six Steps to Develop an Effective Problem-Solving Process

by Rawzaba Alhalabi Published on November 1, 2017

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

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

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

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

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

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

Case study 1:

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

Case study 2:

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

Yolanda Barreros Gutiérrez, B&C Consulting

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

Click here to register (coupon embedded) .

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

Leave a Reply Cancel reply

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

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

Subscribe to our newsletter

The Five-Step Problem-Solving Process

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

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

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

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

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

Here are the steps of a problem-solving process:

1. Defining the Problem

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

2. Analyzing the Problem

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

3. Weighing the Options

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

4. Implementing The Best Solution

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

5. Monitoring Progress

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

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

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

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

Psychological Steps Involved in Problem Solving

A mental process or a phenomenon dedicated towards solving problems by discovering and analyzing the problem is referred to as problem-solving. It is a process dedicated to finding not just any solution, but the best solution to resolve any problems. There is no such thing as one best way to solve every kind of problem, since there are unique problems depending upon the situation there are unique solutions too.

In psychology, problem solving doesn’t necessarily refer to solving psychological/mental issues of the brain. The process simply refers to solving every kind of problems in life in a proper manner. The idea of including the subject in psychology is because psychology deals with the overall mental process. And, tactfully using our thought process is what leads to the solution of any problems.

There are number of rigid psychological steps involved in problem solving, which is also referred as problem-solving cycle. The steps are in sequential order, and solving any problem requires following them one after another. But, we tend to avoid following this rigid set of steps, which is why it often requires us to go through the same steps over and over again until a satisfactory solution is reached.

Here are the steps involved in problem solving, approved by expert psychologists.

1. Identifying the Problem

Identifying the problem seems like the obvious first stem, but it’s not exactly as simple as it sounds. People might identify the wrong source of a problem, which will render the steps thus carried on useless.

For instance , let’s say you’re having trouble with your studies. identifying the root of your failure is your first priority. The problem here could be that you haven’t been allocating enough time for your studies, or you haven’t tried the right techniques. But, if you make an assumption that the problem here is the subject being too hard, you won’t be able to solve the problem.

2. Defining/Understanding the Problem

It’s vital to properly define the problem once it’s been identified. Only by defining the problem, further steps can be taken to solve it. While at it, you also need to take into consideration different perspectives to understand any problem; this will also help you look for solutions with different perspectives.

Now, following up with the previous example . Let’s say you have identified the problem as not being able to allocate enough time for your studies. You need to sort out the reason behind it. Have you just been procrastinating? Have you been too busy with work? You need to understand the whole problem and reasons behind it, which is the second step in problem solving.

3. Forming a Strategy

Developing a strategy is the next step to finding a solution. Each different situation will require formulating different strategies, also depending on individual’s unique preferences.

Now, you have identified and studied your problem. You can’t just simply jump into trying to solve it. You can’t just quit work and start studying. You need to draw up a strategy to manage your time properly. Allocate less time for not-so-important works, and add them to your study time. Your strategy should be well thought, so that in theory at least, you are able to manage enough time to study properly and not fail in the exams.

4. Organizing Information

Organizing the available information is another crucial step to the process. You need to consider

• What do you know about the problem?
• What do you not know about the problem?

Accuracy of the solution for your problem will depend on the amount of information available.

The hypothetical strategy you formulate isn’t the all of it either. You need to now contemplate on the information available on the subject matter. Use the aforementioned questions to find out more about the problem. Proper organization of the information will force you to revise your strategy and refine it for best results.

5. Allocating Resources

Time, money and other resources aren’t unlimited. Deciding how high the priority is to solve your problem will help you determine the resources you’ll be using in your course to find the solution. If the problem is important, you can allocate more resources to solving it. However, if the problem isn’t as important, it’s not worth the time and money you might spend on it if not for proper planning.

For instance , let’s consider a different scenario where your business deal is stuck, but it’s few thousand miles away. Now, you need to analyze the problem and the resources you can afford to expend to solve the particular problem. If the deal isn’t really in your favor, you could just try solving it over the phone, however, more important deals might require you to fly to the location in order to solve the issue.

6. Monitoring Progress

You need to document your progress as you are finding a solution. Don’t rely on your memory, no matter how good your memory is. Effective problem-solvers have been known to monitor their progress regularly. And, if they’re not making as much progress as they’re supposed to, they will reevaluate their approach or look for new strategies.

Problem solving isn’t an overnight feat. You can’t just have a body like that of Brad Pitt after a single session in the gym. It takes time and patience. Likewise, you need to work towards solving any problem every day until you finally achieve the results. Looking back at the previous example , if everything’s according to plan, you will be allocating more and more time for your studies until finally you are confident that you’re improving. One way to make sure that you’re on a right path to solving a problem is by keeping track of the progress. To solve the problem illustrated in the first example, you can take self-tests every week or two and track your progress.

7. Evaluating the Results

Your job still isn’t done even if you’ve reached a solution. You need to evaluate the solution to find out if it’s the best possible solution to the problem. The evaluation might be immediate or might take a while. For instance , answer to a math problem can be checked then and there, however solution to your yearly tax issue might not be possible to be evaluated right there.

• Take time to identify the possible sources of the problem. It’s better to spend a substantial amount of time on something right, than on something completely opposite.
• Ask yourself questions like What, Why, How to figure out the causes of the problem. Only then can you move forward on solving it.
• Carefully outline the methods to tackle the problem. There might be different solutions to a problem, record them all.
• Gather all information about the problem and the approaches. More, the merrier.
• From the outlined methods, choose the ones that are viable to approach. Try discarding the ones that have unseen consequences.
• Track your progress as you go.
• Evaluate the outcome of the progress.

What are other people reading?

Divergent Thinking

Convergent Thinking

Convergent Vs Divergent Thinking

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

By Teach Educator

Published on: February 4, 2024

7 Steps to Problem-Solving

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

Define the Problem:

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

Gather Information:

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

Generate Possible Solutions:

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

Evaluate Options:

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

Make a Decision:

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

Implement the Solution:

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

Evaluate the Results:

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

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

Problem-Solving Example in Education

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

Background:

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

Steps in Problem-Solving

Identify the problem:.

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

Root Cause Analysis

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

Brainstorm Solutions

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

Evaluate and Prioritize Solutions

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

Implement the Chosen Solution

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

Monitor and Evaluate

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

Adjust as Needed

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

Example Solution

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

Expected Outcomes:

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

Final Words

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

Related Post

What is physical fitness (latest).

Physical Fitness Physical fitness refers to a state of health and well-being that allows individuals to perform aspects of sports, occupations, and daily activities without undue fatigue. It ...

Need and Importance of Physical Education – Latest

Need and Importance of Physical Education Need and Importance of Physical Education: Physical education is crucial for several reasons, offering a wide range of benefits to individuals and ...

Aims and Objectives of Physical Education – Latest Update

Aims and Objectives of Physical Education The aims and objectives of physical education vary depending on educational institutions, curricula, and cultural contexts. However, some common goals are generally ...

What is Cognitive Development with Example? Latest

Cognitive Development with Example Cognitive development refers to the process through which individuals acquire and enhance their intellectual abilities and thinking skills as they grow and mature. This ...

Leave a Comment Cancel reply

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

Latest Post

Unemployment problems in india – latest update, the changing role of housewife – latest 2024, teach educator.

"Teach Educator aims to empower learners and educators alike through its comprehensive services. Dedicated to bridging educational gaps, it offers a range of resources designed to enhance teaching methodologies, provide updated curriculum insights, and foster professional development. With a commitment to accessibility, Teach Educator ensures that educational tools and information are readily available to all, promoting inclusivity in learning.

© Teach Educator 2021 - 2024 | All Rights Reserved

Privacy policy

• Trending Now
• Foundational Courses
• Data Science
• Practice Problem
• Machine Learning
• System Design
• DevOps Tutorial

CBSE Class 11 | Problem Solving Methodologies

Problem solving process.

The process of problem-solving is an activity which has its ingredients as the specification of the program and the served dish is a correct program. This activity comprises of four steps : 1. Understanding the problem: To solve any problem it is very crucial to understand the problem first. What is the desired output of the code and how that output can be generated? The obvious and essential need to generate the output is an input. The input may be singular or it may be a set of inputs. A proper relationship between the input and output must be drawn in order to solve the problem efficiently. The input set should be complete and sufficient enough to draw the output. It means all the necessary inputs required to compute the output should be present at the time of computation. However, it should be kept in mind that the programmer should ensure that the minimum number of inputs should be there. Any irrelevant input only increases the size of and memory overhead of the program. Thus Identifying the minimum number of inputs required for output is a crucial element for understanding the problem.

2. Devising the plan: Once a problem has been understood, a proper action plan has to be devised to solve it. This is called devising the plan. This step usually involves computing the result from the given set of inputs. It uses the relationship drawn between inputs and outputs in the previous step. The complexity of this step depends upon the complexity of the problem at hand.

3. Executing the plan: Once the plan has been defined, it should follow the trajectory of action while ensuring the plan’s integrity at various checkpoints. If any inconsistency is found in between, the plan needs to be revised.

4. Evaluation: The final result so obtained must be evaluated and verified to see if the problem has been solved satisfactorily.

Problem Solving Methodology(The solution for the problem)

The methodology to solve a problem is defined as the most efficient solution to the problem. Although, there can be multiple ways to crack a nut, but a methodology is one where the nut is cracked in the shortest time and with minimum effort. Clearly, a sledgehammer can never be used to crack a nut. Under problem-solving methodology, we will see a step by step solution for a problem. These steps closely resemble the software life cycle . A software life cycle involves several stages in a program’s life cycle. These steps can be used by any tyro programmer to solve a problem in the most efficient way ever. The several steps of this cycle are as follows :

Step by step solution for a problem (Software Life Cycle) 1. Problem Definition/Specification: A computer program is basically a machine language solution to a real-life problem. Because programs are generally made to solve the pragmatic problems of the outside world. In order to solve the problem, it is very necessary to define the problem to get its proper understanding. For example, suppose we are asked to write a code for “ Compute the average of three numbers”. In this case, a proper definition of the problem will include questions like : “What exactly does average mean?” “How to calculate the average?”

Once, questions like these are raised, it helps to formulate the solution of the problem in a better way. Once a problem has been defined, the program’s specifications are then listed. Problem specifications describe what the program for the problem must do. It should definitely include :

what is the input set of the program

What is the desired output of the program and in what form the output is desired?

2. Problem Analysis (Breaking down the solution into simple steps): This step of solving the problem follows a modular approach to crack the nut. The problem is divided into subproblems so that designing a solution to these subproblems gets easier. The solutions to all these individual parts are then merged to get the final solution of the original problem. It is like divide and merge approach.

Modular Approach for Programming :

The process of breaking a large problem into subproblems and then treating these individual parts as different functions is called modular programming. Each function behaves independent of another and there is minimal inter-functional communication. There are two methods to implement modular programming :

• Top Down Design : In this method, the original problem is divided into subparts. These subparts are further divided. The chain continues till we get the very fundamental subpart of the problem which can’t be further divided. Then we draw a solution for each of these fundamental parts.
• Bottom Up Design : In this style of programming, an application is written by using the pre-existing primitives of programming language. These primitives are then amalgamated with more complicated features, till the application is written. This style is just the reverse of the top-down design style.

3. Problem Designing: The design of a problem can be represented in either of the two forms :

The ways to execute any program are of three categories:

• Sequence Statements Here, all the instructions are executed in a sequence, that is, one after the another, till the program is executed.
• Selection Statements As it is self-clear from the name, in these type of statements the whole set of instructions is not executed. A selection has to be made. A selected number of instructions are executed based on some condition. If the condition holds true then some part of the instruction set is executed, otherwise, another part of the set is executed. Since this selection out of the instruction set has to be made, thus these type of instructions are called Selection Statements.

Identification of arithmetic and logical operations required for the solution : While writing the algorithm for a problem, the arithmetic and logical operations required for the solution are also usually identified. They help to write the code in an easier manner because the proper ordering of the arithmetic and logical symbols is necessary to determine the correct output. And when all this has been done in the algorithm writing step, it just makes the coding task a smoother one.

• Flow Chart : Flow charts are diagrammatic representation of the algorithm. It uses some symbols to illustrate the starting and ending of a program along with the flow of instructions involved in the program.

4. Coding: Once an algorithm is formed, it can’t be executed on the computer. Thus in this step, this algorithm has to be translated into the syntax of a particular programming language. This process is often termed as ‘coding’. Coding is one of the most important steps of the software life cycle. It is not only challenging to find a solution to a problem but to write optimized code for a solution is far more challenging.

Writing code for optimizing execution time and memory storage : A programmer writes code on his local computer. Now, suppose he writes a code which takes 5 hours to get executed. Now, this 5 hours of time is actually the idle time for the programmer. Not only it takes longer time, but it also uses the resources during that time. One of the most precious computing resources is memory. A large program is expected to utilize more memory. However, memory utilization is not a fault, but if a program is utilizing unnecessary time or memory, then it is a fault of coding. The optimized code can save both time and memory. For example, as has been discussed earlier, by using the minimum number of inputs to compute the output , one can save unnecessary memory utilization. All such techniques are very necessary to be deployed to write optimized code. The pragmatic world gives reverence not only to the solution of the problem but to the optimized solution. This art of writing the optimized code also called ‘competitive programming’.

5. Program Testing and Debugging: Program testing involves running each and every instruction of the code and check the validity of the output by a sample input. By testing a program one can also check if there’s an error in the program. If an error is detected, then program debugging is done. It is a process to locate the instruction which is causing an error in the program and then rectifying it. There are different types of error in a program : (i) Syntax Error Every programming language has its own set of rules and constructs which need to be followed to form a valid program in that particular language. If at any place in the entire code, this set of rule is violated, it results in a syntax error. Take an example in C Language

In the above program, the syntax error is in the first printf statement since the printf statement doesn’t end with a ‘;’. Now, until and unless this error is not rectified, the program will not get executed.

Once the error is rectified, one gets the desired output. Suppose the input is ‘good’ then the output is : Output:

(ii) Logical Error An error caused due to the implementation of a wrong logic in the program is called logical error. They are usually detected during the runtime. Take an example in C Language:

In the above code, the ‘for’ loop won’t get executed since n has been initialized with the value of 11 while ‘for’ loop can only print values smaller than or equal to 10. Such a code will result in incorrect output and thus errors like these are called logical errors. Once the error is rectified, one gets the desired output. Suppose n is initialised with the value ‘5’ then the output is : Output:

(iii) Runtime Error Any error which causes the unusual termination of the program is called runtime error. They are detected at the run time. Some common examples of runtime errors are : Example 1 :

If during the runtime, the user gives the input value for B as 0 then the program terminates abruptly resulting in a runtime error. The output thus appears is : Output:

Example 2 : If while executing a program, one attempts for opening an unexisting file, that is, a file which is not present in the hard disk, it also results in a runtime error.

6. Documentation : The program documentation involves :

• Problem Definition
• Problem Design
• Documentation of test perform
• History of program development

7. Program Maintenance: Once a program has been formed, to ensure its longevity, maintenance is a must. The maintenance of a program has its own costs associated with it, which may also exceed the development cost of the program in some cases. The maintenance of a program involves the following :

• Detection and Elimination of undetected errors in the existing program.
• Modification of current program to enhance its performance and adaptability.
• Enhancement of user interface
• Enriching the program with new capabilities.
• Updation of the documentation.

Control Structure- Conditional control and looping (finite and infinite)

There are codes which usually involve looping statements. Looping statements are statements in which instruction or a set of instructions is executed multiple times until a particular condition is satisfied. The while loop, for loop, do while loop, etc. form the basis of such looping structure. These statements are also called control structure because they determine or control the flow of instructions in a program. These looping structures are of two kinds :

In the above program, the ‘for’ loop gets executed only until the value of i is less than or equal to 10. As soon as the value of i becomes greater than 10, the while loop is terminated. Output:

In the above code, one can easily see that the value of n is not getting incremented. In such a case, the value of n will always remain 1 and hence the while loop will never get executed. Such loop is called an infinite loop. Output:

Please Login to comment...

Similar reads.

• School Programming
• SUMIF in Google Sheets with formula examples
• How to Get a Free SSL Certificate
• Best SSL Certificates Provider in India
• Elon Musk's xAI releases Grok-2 AI assistant
• Content Improvement League 2024: From Good To A Great Article

Improve your Coding Skills with Practice

What kind of Experience do you want to share?

Trust in AI is more than a moral problem

• Share on Facebook
• Share on LinkedIn

Join our daily and weekly newsletters for the latest updates and exclusive content on industry-leading AI coverage. Learn More

The economic potential of AI is uncontested, but it is largely unrealized by organizations, with an astounding 87% of AI projects failing to succeed.

Some consider this a technology problem, others a business problem, a culture problem or an industry problem — but the latest evidence reveals that it is a trust problem.

According to recent research, nearly two-thirds of C-suite executives say that trust in AI drives revenue, competitiveness and customer success.

Trust has been a complicated word to unpack when it comes to AI. Can you trust an AI system ? If so, how? We don’t trust humans immediately, and we’re even less likely to trust AI systems immediately.

But a lack of trust in AI is holding back economic potential, and many of the recommendations for building trust in AI systems have been criticized as too abstract or far-reaching to be practical.

It’s time for a new “AI Trust Equation” focused on practical application.

The AI trust equation

The Trust Equation, a concept for building trust between people, was first proposed in The Trusted Advisor by David Maister, Charles Green and Robert Galford. The equation is Trust = Credibility + Reliability + Intimacy, divided by Self-Orientation.

It is clear at first glance why this is an ideal equation for building trust between humans, but it does not translate to building trust between humans and machines.

For building trust between humans and machines , the new AI Trust Equation is Trust = Security + Ethics + Accuracy, divided by Control.

Security forms the first step in the path to trust, and it is made up of several key tenets that are well outlined elsewhere. For the exercise of building trust between humans and machines, it comes down to the question: “Will my information be secure if I share it with this AI system?”

Ethics is more complicated than security because it is a moral question rather than a technical question. Before investing in an AI system, leaders need to consider:

• How were people treated in the making of this model, such as the Kenyan workers in the making of ChatGPT? Is that something I/we feel comfortable with supporting by building our solutions with it?
• Is the model explainable? If it produces a harmful output, can I understand why? And is there anything I can do about it (see Control)?
• Are there implicit or explicit biases in the model? This is a thoroughly documented problem, such as the Gender Shades research from Joy Buolamwini and Timnit Gebru and Google’s recent attempt to eliminate bias in their models, which resulted in creating ahistorical biases .
• What is the business model for this AI system? Are those whose information and life’s work have trained the model being compensated when the model built on their work generates revenue?
• What are the stated values of the company that created this AI system, and how well do the actions of the company and its leadership track to those values? OpenAI’s recent choice to imitate Scarlett Johansson’s voice without her consent, for example, shows a significant divide between the stated values of OpenAI and Altman’s decision to ignore Scarlett Johansson’s choice to decline the use of her voice for ChatGPT.

Accuracy can be defined as how reliably the AI system provides an accurate answer to a range of questions across the flow of work. This can be simplified to: “When I ask this AI a question based on my context, how useful is its answer?” The answer is directly intertwined with 1) the sophistication of the model and 2) the data on which it’s been trained.

Control is at the heart of the conversation about trusting AI, and it ranges from the most tactical question: “Will this AI system do what I want it to do, or will it make a mistake?” to the one of the most pressing questions of our time: “Will we ever lose control over intelligent systems?” In both cases, the ability to control the actions, decisions and output of AI systems underpins the notion of trusting and implementing them.

5 steps to using the AI trust equation

•  Determine whether the system is useful: Before investing time and resources in investigating whether an AI platform is trustworthy, organizations would benefit from determining whether a platform is useful in helping them create more value.
• Investigate if the platform is secure: What happens to your data if you load it into the platform? Does any information leave your firewall? Working closely with your security team or hiring security advisors is critical to ensuring you can rely on the security of an AI system.
• Set your ethical threshold and evaluate all systems and organizations against it: If any models you invest in must be explainable, define, to absolute precision, a common, empirical definition of explainability across your organization, with upper and lower tolerable limits, and measure proposed systems against those limits. Do the same for every ethical principle your organization determines is non-negotiable when it comes to leveraging AI.
• Define your accuracy targets and don’t deviate: It can be tempting to adopt a system that doesn’t perform well because it’s a precursor to human work. But if it’s performing below an accuracy target you’ve defined as acceptable for your organization, you run the risk of low quality work output and a greater load on your people. More often than not, low accuracy is a model problem or a data problem, both of which can be addressed with the right level of investment and focus.
• Decide what degree of control your organization needs and how it’s defined: How much control you want decision-makers and operators to have over AI systems will determine whether you want a fully autonomous system, semi-autonomous, AI-powered, or if your organizational tolerance level for sharing control with AI systems is a higher bar than any current AI systems may be able to reach.

In the era of AI, it can be easy to search for best practices or quick wins, but the truth is: no one has quite figured all of this out yet, and by the time they do, it won’t be differentiating for you and your organization anymore.

So, rather than wait for the perfect solution or follow the trends set by others, take the lead. Assemble a team of champions and sponsors within your organization, tailor the AI Trust Equation to your specific needs, and start evaluating AI systems against it. The rewards of such an endeavor are not just economic but also foundational to the future of technology and its role in society.

Some technology companies see the market forces moving in this direction and are working to develop the right commitments, control and visibility into how their AI systems work — such as with Salesforce’s Einstein Trust Layer — and others are claiming that that any level of visibility would cede competitive advantage. You and your organization will need to determine what degree of trust you want to have both in the output of AI systems as well as with the organizations that build and maintain them.

AI’s potential is immense, but it will only be realized when AI systems and the people who make them can reach and maintain trust within our organizations and society. The future of AI depends on it.

Brian Evergreen is author of “Autonomous Transformation: Creating a More Human Future in the Era of Artificial Intelligence .”

DataDecisionMakers

Welcome to the VentureBeat community!

DataDecisionMakers is where experts, including the technical people doing data work, can share data-related insights and innovation.

If you want to read about cutting-edge ideas and up-to-date information, best practices, and the future of data and data tech, join us at DataDecisionMakers.

You might even consider  contributing an article  of your own!

Read More From DataDecisionMakers