what are the steps involved in problem solving process

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

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

What Is Problem Solving?

Definition and importance.

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

Problem-Solving Steps

The problem-solving process typically includes the following steps:

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

Defining the Problem

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

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

Generating Solutions

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

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

Evaluating and Selecting Solutions

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

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

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

Implementing and Monitoring the Solution

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

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

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

Problem-Solving Techniques

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

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

Brainstorming

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

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

When brainstorming, remember to:

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

Root Cause Analysis

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

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

SWOT Analysis

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

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

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

Mind Mapping

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

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

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

Examples of Problem Solving in Various Contexts

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

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

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

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

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

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

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

• 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

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

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

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

Navigating scale: a framework for leading product teams through growth

5 decision-making models to streamline collaboration and reach success

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

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