7 step method for problem solving

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

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

StrategyPunk

Introduction

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

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

Step 1: Define the Problem

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

Step 2: Disaggregate

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

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

Step 3: Prioritize

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

Step 4: Workplan

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

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

Step 5: Analysis

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

Step 6: Synthesize

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

During the synthesis phase, it is vital to remain open-minded and consider all potential solutions. Involving all stakeholders in the decision-making process is essential to ensure everyone's perspectives are considered.

Step 7: Communicate

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

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

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

7-Step Problem-Solving Process PPT Template

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

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

Please buy me a coffee.

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

7-Step Problem-Solving Process PDF Template

7-step problem-solving process powerpoint template, multi-chapter growth strategy framework (free template), lidl swot analysis: free ppt template and in-depth insights.

Discover Lidl's strengths, weaknesses, opportunities, and threats with our free PowerPoint template. This in-depth SWOT analysis provides valuable insights to help you understand Lidl's market position and strategic direction.

Global Bites: PESTLE Insights into Nestlé (Free PPT)

Pestle analysis: decoding reddit's landscape (free ppt).

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

Latest educational keywords 2024 – new post.

Latest educational keywords 2024 The term “latest educational keywords 2024” refers to the most recent and emerging keywords that are expected to shape the field of education in ...

The Real Impact of Social Media – Latest Update

Real Impact of Social Media Social media has had a profound impact on various aspects of society, influencing communication, information dissemination, business, politics, and personal relationships. Here are ...

Can Facebook be used for teaching? – Latest Update

Facebook Used For Teaching Yes, Facebook Used For Teaching. Facebook can be used as a platform for teaching and education. Many educators and institutions use Facebook as a ...

How useful is Facebook for teachers?

Facebook Useful for teachers Facebook Useful for teachers: Facebook can be a useful tool for teachers in various ways, but its effectiveness depends on how educators choose to ...

Leave a Comment Cancel reply

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

Latest Post

What are the effects of facebook on students, how useful is facebook for students – latest, 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

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

The Leading Source of Insights On Business Model Strategy & Tech Business Models

7 Steps To Problem-Solving

The 7 steps to problem-solving is a disciplined and methodical approach to identifying and then addressing the root cause of problems. Instead, a more robust approach involves working through a problem using the hypothesis-driven framework of the scientific method. Each viable hypothesis is tested using a range of specific diagnostics and then recommendations are made.

Table of Contents

Understanding the 7 steps to problem-solving

The core argument of this approach is that the most obvious solutions to a problem are often not the best solutions. 

Good problem-solving in business is a skill that must be learned. Businesses that are adept at problem-solving take responsibility for their own decisions and have courage and confidence in their convictions. Ultimately, this removes doubt which can impede the growth of businesses and indeed employees alike.

Moving through the 7 steps to problem-solving

Although many versions of the 7-step approach exist, the McKinsey approach is the most widely used in business settings. Here is how decision makers can move through each of the steps systematically.

Step 1 – Define the problem

First, the scope and extent of the problem must be identified. Actions and behaviors of individuals must be the focus – instead of a focus on the individuals themselves. Whatever the case, the problem must be clearly defined and be universally accepted by all relevant parties.

Step 2 – Disaggregate the problem

In the second step, break down the problem (challenge) into smaller parts using logic trees and develop an early hypothesis. Here, economic and scientific principles can be useful in brainstorming potential solutions. Avoid cognitive biases, such as deciding that a previous solution should be used again because it worked last time.

Step 3 – Prioritize issues

Which constituent parts could be key driving factors of the problem? Prioritize each according to those which have the biggest impact on the problem. Eliminate parts that have negligible impact. This step helps businesses use their resources wisely.

Step 4 – Plan the analyses

Before testing each hypothesis, develop a work and process plan for each. Staff should be assigned to analytical tasks with unique output and completion dates. Hypothesis testing should also be reviewed at regular intervals to measure viability and adjust strategies accordingly.

Step 5 – Conduct the analyses

In step five, gather the critical data required to accept or reject each hypothesis. Data analysis methods will vary according to the nature of the project, but each business must understand the reasons for implementing specific methods. In question-based problem solving, the Five Whys or Fishbone method may be used. More complicated problems may require the use of statistical analysis . In any case, this is often the longest and most complex step of the process. 

Step 6 – Synthesise the results

Once the results have been determined, they must be synthesized in such a way that they can be tested for validity and logic. In a business context, assess the implications of the findings for a business moving forward. Does it solve the problem? 

Step 7 – Communicate

In the final step, the business must present the solutions in such a way that they link back to the original problem statement. When presenting to clients, this is vital. It shows that the business understands the problem and has a solution supported by facts or hard data. Above all, the data should be woven into a convincing story that ends with recommendations for future action.

Key takeaways

• 7 steps to problem-solving is a methodical approach to problem-solving based on the scientific method.
• Although a somewhat rigorous approach, the strategy can be learned by any business willing to devote the time and resources.
• Fundamentally, the 7 steps to problem-solving method involves formulating and then testing hypotheses. Through the process of elimination, a business can narrow its focus to the likely root cause of a problem.

Key Highlights

• Definition : The 7 Steps to Problem-Solving is a structured methodology rooted in the scientific method. It emphasizes systematic hypothesis testing and data analysis to identify and address the root cause of problems, avoiding surface-level solutions.
• Problem-Solving Skill : Effective problem-solving is a learned skill that fosters responsible decision-making, boosts confidence, and supports business growth .
• Define the Problem : Clearly outline the problem’s scope and impact, focusing on actions and behaviors rather than individuals.
• Disaggregate the Problem : Break down the problem into smaller parts using logic trees and form early hypotheses. Avoid biases from past solutions.
• Prioritize Issues : Identify key driving factors of the problem and prioritize them by impact. Eliminate parts with minimal impact to allocate resources efficiently.
• Plan the Analyses : Develop work and process plans for hypothesis testing, assigning staff and setting completion dates. Regularly review and adjust strategies.
• Conduct the Analyses : Gather critical data to accept or reject hypotheses. Use methods like Five Whys, Fishbone diagrams, or statistical analysis .
• Synthesize the Results : Combine and analyze results to determine their validity and implications for the business . Assess if the problem is solved.
• Communicate : Present solutions that link back to the original problem statement, supported by facts. Create a compelling story ending with recommendations.
• The 7 Steps to Problem-Solving is based on the scientific method.
• It requires a structured approach to formulating and testing hypotheses.
• Businesses willing to invest time and resources can learn and apply this method effectively.

Connected Decision-Making Frameworks

Cynefin Framework

SWOT Analysis

Personal SWOT Analysis

Pareto Analysis

Failure Mode And Effects Analysis

Blindspot Analysis

Comparable Company Analysis

Cost-Benefit Analysis

Agile Business Analysis

SOAR Analysis

STEEPLE Analysis

Pestel Analysis

DESTEP Analysis

Paired Comparison Analysis

Related Strategy Concepts:  Go-To-Market Strategy ,  Marketing Strategy ,  Business Models ,  Tech Business Models ,  Jobs-To-Be Done ,  Design Thinking ,  Lean Startup Canvas ,  Value Chain ,  Value Proposition Canvas ,  Balanced Scorecard ,  Business Model Canvas ,  SWOT Analysis ,  Growth Hacking ,  Bundling ,  Unbundling ,  Bootstrapping ,  Venture Capital ,  Porter’s Five Forces ,  Porter’s Generic Strategies ,  Porter’s Five Forces ,  PESTEL Analysis ,  SWOT ,  Porter’s Diamond Model ,  Ansoff ,  Technology Adoption Curve ,  TOWS ,  SOAR ,  Balanced

Read Next:  Mental Models ,  Biases ,  Bounded Rationality ,  Mandela Effect ,  Dunning-Kruger Effect ,  Lindy Effect ,  Crowding Out Effect ,  Bandwagon Effect ,  Decision-Making Matrix .

• Business Models
• Business Strategy
• Marketing Strategy
• Business Model Innovation
• Platform Business Models
• Network Effects In A Nutshell
• Digital Business Models

More Resources

About The Author

Gennaro Cuofano

Discover more from fourweekmba.

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

Type your email…

Continue reading

• AI Business Coach

Resources >

Mckinsey approach to problem solving, a guide to the 7-step mckinsey problem solving process.

McKinsey and Company is recognized for its rigorous approach to problem solving. They train their consultants on their seven-step process that anyone can learn.

This resource guides you through that process, largely informed by the McKinsey Staff Paper 66. It also includes a PowerPoint Toolkit with slide templates of each step of the process that you can download and customize for your own use.

In this guide you'll learn:

Overview of the mckinsey approach to problem solving, problem solving process, problem definition.

• Problem Statement

Stakeholder Analysis Worksheet

Structure the problem, hypothesis trees, issue trees, analyses and workplan, synthesize findings, craft recommendations, communicate, distinctiveness practices, harness the power of collaboration, sources and additional reading, request the mckinsey approach to problem solving.

Problem solving — finding the optimal solution to a given business opportunity or challenge — is the very heart of how consultants create client impact, and considered the most important skill for success at McKinsey.

The characteristic “McKinsey method” of problem solving is a structured, inductive approach that can be used to solve any problem. Using this standardized process saves us from reinventing the problem-solving wheel, and allows for greater focus on distinctiveness in the solution. Every new McKinsey associate must learn this method on his or her first day with the firm.

There are four fundamental disciplines of the McKinsey method:

1. Problem definition

A thorough understanding and crisp definition of the problem.

2. The problem-solving process

Structuring the problem, prioritizing the issues, planning analyses, conducting analyses, synthesizing findings, and developing recommendations.

3. Distinctiveness practices

Constructing alternative perspectives; identifying relationships; distilling the essence of an issue, analysis, or recommendation; and staying ahead of others in the problem-solving process.

4. Collaboratio n

Actively seeking out client, customer, and supplier perspectives, as well as internal and external expert insight and knowledge.

Once the problem has been defined, the problem-solving process proceeds with a series of steps:

• Structure the problem
• Prioritize the issues
• Plan analyses
• Conduct analyses
• Synthesize findings
• Develop recommendations

Not all problems require strict adherence to the process. Some steps may be truncated, such as when specific knowledge or analogies from other industries make it possible to construct hypotheses and associated workplans earlier than their formal place in the process. Nonetheless, it remains important to be capable of executing every step in the basic process.

When confronted with a new and complex problem, this process establishes a path to defining and disaggregating the problem in a way that will allow the team to move to a solution. The process also ensures nothing is missed and concentrates efforts on the highest-impact areas. Adhering to the process gives the client clear steps to follow, building confidence, credibility, and long-term capability.

The most important step in your entire project is to first carefully define the problem. The problem definition will serve the guide all of the team’s work, so it is critical to ensure that all key stakeholders agree that it is the right problem to be solving.

The problem definition will serve the guide all of the team’s work, so it is critical to ensure that all key stakeholders agree that it is the right problem to be solving.

There are often dozens of issues that a team could focus on, and it is often not obvious how to define the problem.

In any real-life situation, there are many possible problem statements. Your choice of problem statement will serve to constrain the range of possible solutions.

Constraints can be a good thing (e.g., limit solutions to actions within the available budget.) And constraints can be a bad thing (e.g., eliminating the possibility of creative ideas.) So choose wisely.

The problem statement may ignore many issues to focus on the priority that should be addressed. The problem statement should be phrased as a question, such that the answer will be the solution.

Example scenario – A family on Friday evening :

A mother, a father, and their two teenage children have all arrived home on a Friday at 6 p.m. The family has not prepared dinner for Friday evening. The daughter has lacrosse practice on Saturday and an essay to write for English class due on Monday. The son has theatre rehearsal on both Saturday and Sunday and will need one parent to drive him to the high school both days, though he can get a ride home with a friend.

The family dog, a poodle, must be taken to the groomer on Saturday morning. The mother will need to spend time this weekend working on assignments for her finance class she is taking as part of her Executive MBA. The father plans to go on a 100-mile bike ride, which he can do either Saturday or Sunday. The family has two cars, but one is at the body shop. They are trying to save money to pay for an addition to their house.

Potential problem definitions – A family on Friday evening :

The problem definition should not be vague, without clear measures of success. Rather, it should be a SMART definition:

• Action-oriented

Given one set of facts, it is possible to come up with many possible problem statements. The choice of problem statement constrains the range of possible solutions.

Before starting to solve the problem, the family first needs to agree on what problem they want to solve.

• What should the family do for dinner on Friday night?
• How can the family schedule their activities this weekend to accomplish everything planned given that they only have one vehicle available?
• How can the family increase income or reduce expenses to allow them to save $75K over the next 12 months to pay for the planned addition to their house?

Problem Statement Worksheet

This is a helpful tool to use to clearly define the problem. There are often dozens of issues that a team could focus on, and it is often not obvious how to define the problem. In any real-life situation, there are many possible problem statements. Your choice of problem statement will serve to constrain the range of possible solutions.

• Use a question . The problem statement should be phrased as a question, such that the answer will be the solution. Make the question SMART: specific, measurable, action-oriented, relevant, and time-bound. Example: “How can XYZ Bank close the $100 million profitability gap in two years?”
• Context . What are the internal and external situations and complications facing the client, such as industry trends, relative position within the industry, capability gaps, financial flexibility, and so on?
• Success criteria . Understand how the client and the team define success and failure. In addition to any quantitative measures identified in the basic question, identify other important quantitative or qualitative measures of success, including timing of impact, visibility of improvement, client capability building required, necessary mindset shifts, and so on.
• Scope and constraints . Scope most commonly covers the markets or segments of interest, whereas constraints govern restrictions on the nature of solutions within those markets or segments.
• Stakeholders . Explore who really makes the decisions — who decides, who can help, and who can block.
• Key sources of insight . What best-practice expertise, knowledge, and engagement approaches already exist? What knowledge from the client, suppliers, and customers needs to be accessed? Be as specific as possible: who, what, when, how, and why.

In completing the Problem Statement Worksheet, you are prompted to define the key stakeholders.

As you become involved in the problem-solving process, you should expand the question of key stakeholders to include what the team wants from them and what they want from the team, their values and motivations (helpful and unhelpful), and the communications mechanisms that will be most effective for each of them.

Using the Stakeholder Analysis Worksheet allows you to comprehensively identify:

• Stakeholders
• What you need from them
• Where they are
• What they need from you

The two most helpful techniques for rigorously structuring any problem are hypothesis trees and issue trees. Each of these techniques disaggregates the primary question into a cascade of issues or hypotheses that, when addressed, will together answer the primary question.

A hypothesis tree might break down the same question into two or more hypotheses. 

The aim at this stage is to structure the problem into discrete, mutually exclusive pieces that are small enough to yield to analysis and that, taken together, are collectively exhaustive.

Articulating the problem as hypotheses, rather than issues, is the preferred approach because it leads to a more focused analysis of the problem. Questions to ask include:

• Is it testable – can you prove or disprove it?
• It is open to debate? If it cannot be wrong, it is simply a statement of fact and unlikely to produce keen insight.
• If you reversed your hypothesis – literally, hypothesized that the exact opposite were true – would you care about the difference it would make to your overall logic?
• If you shared your hypothesis with the CEO, would it sound naive or obvious?
• Does it point directly to an action or actions that the client might take?

Quickly developing a powerful hypothesis tree enables us to develop solutions more rapidly that will have real impact. This can sometimes seem premature to clients, who might find the “solution” reached too quickly and want to see the analysis behind it.

Take care to explain the approach (most important, that a hypothesis is not an answer) and its benefits (that a good hypothesis is the basis of a proven means of successful problem solving and avoids “boiling the ocean”).

Example: Alpha Manufacturing, Inc.

Problem Statement: How can Alpha increase EBITDA by $13M (to $50M) by 2025?

The hypotheses might be:

• Alpha can add $125M revenues by expanding to new customers, adding $8M of EBITDA
• Alpha can reduce costs to improve EBITDA by $5M

These hypotheses will be further disaggregated into subsidiary hypotheses at the next level of the tree.

Often, the team has insufficient knowledge to build a complete hypothesis tree at the start of an engagement. In these cases, it is best to begin by structuring the problem using an issue tree.

An issue tree is best set out as a series of open questions in sentence form. For example, “How can the client minimize its tax burden?” is more useful than “Tax.” Open questions – those that begin with what, how, or why– produce deeper insights than closed ones. In some cases, an issue tree can be sharpened by toggling between issue and hypothesis – working forward from an issue to identify the hypothesis, and back from the hypothesis to sharpen the relevant open question.

Once the problem has been structured, the next step is to prioritize the issues or hypotheses on which the team will focus its work. When prioritizing, it is common to use a two-by-two matrix – e.g., a matrix featuring “impact” and “ease of impact” as the two axes.

Applying some of these prioritization criteria will knock out portions of the issue tree altogether. Consider testing the issues against them all, albeit quickly, to help drive the prioritization process.

Once the criteria are defined, prioritizing should be straightforward: Simply map the issues to the framework and focus on those that score highest against the criteria.

As the team conducts analysis and learns more about the problem and the potential solution, make sure to revisit the prioritization matrix so as to remain focused on the highest-priority issues.

The issues might be:

• How can Alpha increase revenue?
• How can Alpha reduce cost?

Each of these issues is then further broken down into deeper insights to solutions.

If the prioritization has been carried out effectively, the team will have clarified the key issues or hypotheses that must be subjected to analysis. The aim of these analyses is to prove the hypotheses true or false, or to develop useful perspectives on each key issue. Now the task is to design an effective and efficient workplan for conducting the analyses.

Transforming the prioritized problem structure into a workplan involves two main tasks:

• Define the blocks of work that need to be undertaken. Articulate as clearly as possible the desired end products and the analysis necessary to produce them, and estimate the resources and time required.
• Sequence the work blocks in a way that matches the available resources to the need to deliver against key engagement milestones (e.g., important meetings, progress reviews), as well as to the overall pacing of the engagement (i.e., weekly or twice-weekly meetings, and so on).

A good workplan will detail the following for each issue or hypothesis: analyses, end products, sources, and timing and responsibility. Developing the workplan takes time; doing it well requires working through the definition of each element of the workplan in a rigorous and methodical fashion.

It’s useful to match the workplan to three horizons:

• What is expected at the end of the engagement
• What is expected at key progress reviews
• What is due at daily and/or weekly team meetings

The detail in the workplan will typically be greater for the near term (the next week) than for the long term (the study horizon), especially early in a new engagement when considerable ambiguity about the end state remains.

Here are three different templates for a workplan:

This is the most difficult element of the problem-solving process. After a period of being immersed in the details, it is crucial to step back and distinguish the important from the merely interesting. Distinctive problem solvers seek the essence of the story that will underpin a crisp recommendation for action.

Although synthesis appears, formally speaking, as the penultimate step in the process, it should happen throughout. Ideally, after you have made almost any analytical progress, you should attempt to articulate the “Day 1” or “Week 1” answer. Continue to synthesize as you go along. This will remind the team of the question you are trying to answer, assist prioritization, highlight the logical links of the emerging solution, and ensure that you have a story ready to articulate at all times during the study.

McKinsey’s primary tool for synthesizing is the pyramid principle. Essentially, this principle asserts that every synthesis should explain a single concept, per the “governing thought.” The supporting ideas in the synthesis form a thought hierarchy proceeding in a logical structure from the most detailed facts to the governing thought, ruthlessly excluding the interesting but irrelevant.

While this hierarchy can be laid out as a tree (like with issue and hypothesis trees), the best problem solvers capture it by creating dot-dash storylines — the Pyramid Structure for Grouping Arguments.

Pyramid Structure for Grouping Arguments

• Focus on action. Articulate the thoughts at each level of the pyramid as declarative sentences, not as topics. For example, “expansion” is a topic; “We need to expand into the European market” is a declarative sentence.
• Use storylines. PowerPoint is poor at highlighting logical connections, therefore is not a good tool for synthesis. A storyline will clarify elements that may be ambiguous in the PowerPoint presentation.
• Keep the emerging storyline visible. Many teams find that posting the storyline or story- board on the team-room wall helps keep the thinking focused. It also helps in bringing the client along.
• Use the situation-complication-resolution structure. The situation is the reason there is action to be taken. The com- plication is why the situation needs thinking through – typically an industry or client challenge. The resolution is the answer.
• Down the pyramid: does each governing thought pose a single question that is answered completely by the group of boxes below it?
• Across: is each level within the pyramid MECE?
• Up: does each group of boxes, taken together, provide one answer – one “so what?” – that is essentially the governing thought above it?
• Test the solution. What would it mean if your hypotheses all came true?

It is at this point that we address the client’s questions: “What do I do, and how do I do it?” This means not offering actionable recommendations, along with a plan and client commitment for implementation.

The essence of this step is to translate the overall solution into the actions required to deliver sustained impact. A pragmatic action plan should include:

• Relevant initiatives, along with a clear sequence, timing, and mapping of activities required
• Clear owners for each initiative
• Key success factors and the challenges involved in delivering on the initiatives

Crucial questions to ask as you build recommendations for organizational change are:

• Does each person who needs to change (from the CEO to the front line) understand what he or she needs to change and why, and is he or she committed to it?
• Are key leaders and role models throughout the organization personally committed to behaving differently?
• Has the client set in place the necessary formal mechanisms to reinforce the desired change?
• Does the client have the skills and confidence to behave in the desired new way?

Once the recommendations have been crafted in the problem-solving process, it’s vital to effectively communicate those findings and recommendations.

An executive summary is a great slide to use for this. See more on executive summary slides, including 30 templates, at our Ultimate Guide to Executive Summary Slides .

Great problem solvers identify unique disruptions and discontinuities, novel insights, and step-out opportunities that lead to truly distinctive impact. This is done by applying a number of practices throughout the problem-solving process to help develop these insights.

Expand: Construct multiple perspectives

Identifying alternative ways of looking at the problem expands the range of possibilities, opens you up to innovative ideas, and allows you to formulate more powerful hypotheses. Questions that help here include:

• What changes if I think from the perspective of a customer, or a supplier, or a frontline employee, or a competitor?
• How have other industries viewed and addressed this same problem?
• What would it mean if the client sought to run the company like a low-cost airline or a cosmetics manufacturer?

Link: Identify relationships

Strong problem solvers discern connections and recognize patterns in two different ways:

• They seek out the ways in which different problem elements – issues, hypotheses, analyses, work elements, findings, answers, and recommendations – relate to one another.
• They use these relationships throughout the basic problem-solving process to identify efficient problem-solving approaches, novel solutions, and more powerful syntheses.

Distill: Find the essence

Cutting through complexity to identify the heart of the problem and its solution is a critical skill.

• Identify the critical problem elements. Are there some issues, approaches, or options that can be eliminated completely because they won’t make a significant difference to the solution?
• Consider how complex the different elements are and how long it will take to complete them. Wherever possible, quickly advance simpler parts of the problem that can inform more complex or time-consuming elements.

Lead: Stay ahead/step back

Without getting ahead of the client, you cannot be distinctive. Paradoxically, to get ahead – and stay ahead – it is often necessary to step back from the problem to validate or revalidate the approach and the solution.

• Spend time thinking one or more steps ahead of the client and team.
• Constantly check and challenge the rigor of the underlying data and analysis.
• Stress-test the whole emerging recommendation
• Challenge the solution against a set of hurdles. Does it satisfy the criteria for success as set out on the Problem Statement Worksheet?

No matter how skilled, knowledgeable, or experienced you are, you will never create the most distinctive solution on your own. The best problem solvers know how to leverage the power of their team, clients, the Firm, and outside parties. Seeking the right expertise at the right time, and leveraging it in the right way, are ultimately how we bring distinctiveness to our work, how we maximize efficiency, and how we learn.

When solving a problem, it is important to ask, “Have I accessed all the sources of insight that are available?” Here are the sources you should consider:

• Your core team
• The client’s suppliers and customers
• Internal experts and knowledge
• External sources of knowledge
• Communications specialists

The key here is to think open, not closed. Opening up to varied sources of data and perspectives furthers our mission to develop truly innovative and distinctive solutions for our clients.

• McKinsey Staff Paper 66 — not published by McKinsey but possibly found through an internet search
• The McKinsey Way , 1999, by Ethan M. Rasiel

For consultants

© Copyright 2024 by Umbrex

Designed by our friends at Filez

• Privacy Policy
• Terms of Service

Skip Prichard | Leadership Insights

Ideas, Insight & Inspiration

7 Steps to Problem Solving

Bulletproof Problem Solving

Complex problem solving is the core skill for 21st century teams. It’s the only way to keep up with rapid change. Winning organizations now rely on nimble, iterative problem solving, rather than the traditional planning processes. I had the opportunity to speak with Charles Conn and Robert McLean, two McKinsey alums who share a seven-step systematic approach to creative problem solving that will work in any field or industry. Their new book is BULLETPROOF PROBLEM SOLVING: The One Skill That Changes Everything .

New Skills Required

Would you share a little about the evolution of managerial skills and what skills are needed in the current era?

This new era of focus on creative problem solving has been ushered in by massive disruption of the old order in business and society. New business models are rapidly emerging from revolutionary Internet, machine learning, and bioscience technologies that threaten the status quo in every field. Technology change is speeding business up and providing an edge for disruptive innovators.

As a consequence of accelerating change, the old model of managerial skill development and application is no longer effective.  It used to be that you could learn the core skills for a career in college and graduate school – think management, accounting, law – and then apply it over forty years.  Strategic planning in business assumed an existing playing field and known actors. Today savvy business leaders are prioritizing complex problem solving skills in hiring rather than old domain knowledge, and emphasizing agile team problem solving over traditional planning cycles. This approach rewards the ability to see and quickly respond to new opportunities and threats over the slower traditional big company departmental responses.

We are seeing growing awareness of this. David Brooks of the New York Times said recently, “It doesn’t matter if you are working in the cafeteria or the inspection line of a plant, companies will only hire people who can see problems and organize responses.” And The World Economic Forum in its Future of Jobs Report placed complex problem solving at #1 in its top 10 skills for jobs in 2020.

For those who feel ill-prepared for this era, what are the best ways to acquire the needed skills?

Unfortunately, despite an increasing recognition in the business press that problem solving is the core 21 st century skill, our universities and graduate schools rarely teach systematic problem solving or modern team decision making skills. This is starting to change, and we are seeing that in moves by the OECD and Council for Aid to Education (CAE) which administers the College Learning Assessment plus test.

The OECD Program for International Student Assessment (PISA) started testing individual problem solving skills in 2012 and added collaborative problem solving skills in the 2015 assessments. One of the interesting early findings is that to teach students to become better problem solvers involves other capabilities than simply teaching reading, mathematics, and science literacy well. Capabilities such as creativity, logic, and reasoning are essential contributors to students becoming better problem solvers. That is what this book is about.

You share seven steps in your bulletproof problem solving approach. How did you develop it?

The 7-steps approach to problem solving has its roots in the hypothesis-driven structure of the scientific method, but was developed into an approach for business problem solving at McKinsey & Company.  Charles wrote one of the early internal documents to systematic problem solving in McKinsey, and both of us have developed the approach further for application more broadly to personal, social and environmental problems at all scales in later work with the Nature Conservancy, the Gordon & Betty Moore Foundation, the Rhodes Trust and in start-up companies where we are investors.

1: Define the problem.

2: Disaggregate.

3: Prioritize.

4: Workplan.

5: Analyze.

6: Synthesize.

7. Communicate.

Is there one part of it normally missed or not focused on as much as it should be?

What are some of the best methods for overcoming biases in decision making?

The most important biases to address are confirmation bias, anchoring bias, and loss aversion.  These are deep seated in our psyches and often reinforced by traditional hierarchies. We use some simple team approaches to fight bias, including perspective-taking (the act of modeling another team member’s assertion or belief to the point that you can describe it as compellingly as the other), role playing (where you act out one side or the other of difficult choice, sometimes in a red team/blue team structure), team distributive voting on analyses and solution paths (one approach we have used is to assign each team member 10 votes, represented by sticky notes, and have each team member use them to vote on their favorite analysis, allowing cumulative or bullet voting, with the most senior person voting last, so as not to bias the choices of more junior members). The most important team norm to encourage is the obligation to dissent, which means every team member is required to verbally contest decisions when they disagree, regardless of seniority.

What do leadership teams most struggle with in the new environment?

The biggest challenge is the speed of change, which pressures all the management approaches we were taught in business school, particularly around planning cycles.  The leadership teams that get good at this typically form and re-form cross-functional teams to deploy on issues as they arise, rather than waiting for conventional departmental responses.  And they are comfortable using rapid design cycles to prototype and test products/services in the market, rather than depending on traditional marketing analysis.

How will AI impact the bulletproof approach?

We believe good organization problem solving will increasingly utilize advances in artificial intelligence to predict patterns in consumer behavior, disease, credit risk, and other complex phenomena.  Machine learning is getting better at pattern recognition than most humans. But that isn’t the whole story. To meet the challenges of the twenty-first century, mental muscle and machine muscle have to work together. Machine learning frees human problem solvers from computational drudgery and amplifies the pattern recognition required for faster organizational response to external challenges. For this partnership to work, twenty-first century organizations need staff who are quick on their feet, who learn new skills quickly, and who attack emerging problems with confidence.

For more information, see BULLETPROOF PROBLEM SOLVING: The One Skill That Changes Everything .

Continue Reading

Popular posts.

Learn the important power of prioritizing sleep

Subscribe today and receive a free e-book.  Get  Your Guide to a Solid Night of Sleep   free  when you sign up to receive blog updates via email.

Thank you! Please check your inbox to confirm your subscription.

Pin it on pinterest.

• Print Friendly

• Tension & Compression
• Thermal Expansion
• Pressure Vessels
• Shear Centre
• Longitudinal Shear
• Welded Connections
• Weld Groups
• Unit Conversion
• Geometric Properties
• Soil Stress Distribution
• Shallow Foundations
• Soil Properties
• Material Properties
• Design Tables
• Mathematics First Aid
• Popular Articles
• Handy Calculators

The 7 Steps to Problem Solving

Effective problem solving, document.write("page last modified on: " + document.lastmodified +"");.

Problem solving with a standardized, disciplined and methodical approach is by far the best way of understanding root causes, exploring influences and implementing solutions that not only work, but also stay effective over time. The best solution to a problem is not always the most obvious and only after careful thought and assessment can the most suitable and feasible solution or solutions be implemented. The 7 step problem solving guide provided below has been created to help solve problems where the solution or in some cases the problem itself is not obvious.

STEP 1: The Right Problem to Solve STEP 2: Analyse the Problem STEP 3: Define the Problem STEP 4: Develop Opportunities (Possible Solutions) STEP 5: Select the Best Solution STEP 6: Implement the Solution STEP 7: Evaluate and Learn

When should problem solving be used?

Anytime you have a goal to achieve or simply experience a challenge, problem solving techniques can be adopted. The steps provided can be used on any problem no matter how small and simple, or large and complex with the only difference being the amount of overall time required to be spent on the problem at hand. Unfortunately effective problem solving does take some time and attention to detail but the rewards for the time taken may far outweigh the consequences for leaving problems in place.

STEP 1: The Right Problem to Solve

Identifying the right problem to solve can be by far the most crucial element in the process and it can’t be stressed enough that for this step to work to its full potential it is important to remember to focus on the problem and not just its symptoms or possible solutions, these parts will come shortly. If dealing with multiple problems the right problem is generally the one with the most important outcome, the greatest chance for solution and the nearest deadline. When trying to determine the right problem or if only intending to confirm one, ask yourself the following questions:

• Being as specific as possible what exactly is the problem to be solved?
• a clearly and concisely defined problem avoids confusion.
• A vaguely defined problem could be interpreted as something different.
• Can the problem be broken down further?
• A problem in its most simple form is in the best state for solving.
• Complex problems are possibly multiple smaller problems.
• Is the problem exactly the same from multiple perspectives? If not, can it be reworded so that it is?
• Problems can look different to different people.
• Solving for one person will not necessarily solve for everyone.
• Is there anyone who thinks it is not a problem? Why not?
• Any doubt is worth looking into, they could know something you don’t.
• It is always a possibility that you or your perceptions are the problem.
• Is the problem a symptom of a deeper, underlying condition?
• Fixing the problem will stop future symptoms.
• Fixing a symptom is only temporary.
• Is the problem one that can be solved? If no, can the problem be redefined?
• How to get to work with a broken leg is a problem that can be solved.
• A broken leg itself is not a problem because it can’t be solved, it's broken.
• Can the problem be defined as an opportunity?
• An opportunity is something positive we generally look forward to and want to take advantage of.
• A problem is generally something negative we don’t like and simply want to get rid of.
• Is the problem a beneficial one to solve? Why?
• The most beneficial problem is often a good place to start.
• The world is full of problems and unfortunately we can’t solve them all.
• Are you trying to solve a problem? Or are you confusing cause and effect?
• Building an airstrip so a plane has somewhere to land can be solving a problem.
• Building an airstrip because you know planes land on them does not guarantee a plane.

Once the above questions can be answered concisely you should be left with a well-defined problem which can also be described as an opportunity and more importantly you should have a better understanding of what you will be going to solve or achieve. It is time for the next step, analysing the problem.

STEP 2: Analyse the Problem

Analysing the problem starts with collecting as much information as possible relating to all aspects of the problem. This is where you find out what you already know about the situation and what areas need further looking into. To help discover all the facts it is a good idea to create a number of lists relating to the problem where you in turn list as many points as possible.

Remember that in this stage writing down anything and everything that comes to mind can be a good starting point; irrelevant items can be removed at the end. Some of the information you may find valuable may stem from the following questions. There are quite a few questions to consider, but hopefully they will guide you in the right direction. They are based on the "5 W's and 1 H".

• What does the problem currently affect?
• People or yourself?
• Environment?
• Organisation?
• What will be the benefits of solving the problem? And by how much?
• Credibility?
• Productivity?
• Reputation?
• What influences the problem?
• Does anything seem to aggravate or spread the problem?
• Does anything seem to reduce or delay the problem?
• Does anything tend to speed up / slow down the problem?
• Can the problem be simulated, recreated or acted out in another setting?
• Is there a specific example of an extreme case?
• What would be needed to solve the problem?
• Will new tools and/or policies be required?
• Will new equipment be required?
• Will new people be required?
• Could any new problems arise?
• What would happen if no solution can be found?
• Will a solution be available at a later date?
• What would be the next best thing to finding a complete solution?
• Is there a way to delay the problem?
• What would be the next best thing to solving the problem?
• Is there a chance the problem will go away on its own?
• Is there a way to change the problem for the better?

• Why do you want to achieve a solution?
• Is it something you personally want to do?
• Is it something you have been told to do?
• Is it something you feel you have to do?
• Why did the problem arise in the first place?
• Can the exact cause of the problem be pin pointed?
• Were there numerous reasons for the problem starting?
• Was a problem expected to occur at the time?
• Why was the problem allowed to escalate as far as it has?
• How much further can the problem escalate?
• Have previous attempts at solving the problem been made?
• Does the problem benefit anything/anyone else?

When you ask "How?" you are asking in what way or manner; by what means - "How does it work?" or used to ask about the condition or quality of something - How was your time there?"

• How long has the problem been around?
• Has it always been a problem?
• Has it got worse over time?
• Has the problem occurred at a previous time?
• How will the situation be different once the problem is solved?
• In particular what will be different?
• Can you guarantee the situation will be different?
• How relevant is the information available?
• Is the information up to date?
• Was the information created for the specific purpose it will be used for?
• Does the information need to be modified?
• How can I find out more information on the problem and possible solutions?
• Is all available information available?
• Is any information not available? Why not?
• Will additional research be required?
• Can additional people get involved with finding a solution?
• Is there an expert who can be approached?
• Are additional resources required?

• Where did the problem arise?
• Has the problem always existed?
• Can the exact starting point of the problem be pin pointed?
• Why did the problem arise where it did?
• Where is the problem currently located?
• Is the problem in a single or multiple locations?
• Can the problem be contained in its current location until it is dealt with?
• Is there a chance the problem will spread to different locations?
• Is the “where” component to the problem important? If so, why?

When you ask "Who?" you are asking what or which person or people are involved - "Who is that?" or "Who was there at the time?"

• Who are the stakeholders?
• Who is affected by this problem?
• Who will be affected once it is solved?
• Does anyone think that it is not a problem? What is different about their perspective?
• Who knows about the problem?
• Who has the information needed to solve or release the problem or issue?
• Who can do something or take action as a possible solution?
• Does anyone/s need to be informed about the problem?
• How do processes currently work where the problem is occurring?
• Who does what?
• With what information?
• Using what tools?
• Communicating with whom?
• In what time frame?
• Using what format?

When you ask "When?" you are asking at what time - "When did last witness it?" or at or on which time or circumstance - "Is early mornings when it happens most?"

• When did the problem first appear?
• What was its initial impact?
• How was it identified?
• Who identified it first?
• How did it start?
• Where did it start?
• Why did it start?
• What initially started it?
• When did it start?
• When does a solution need to be found?
• Would it be better to wait for a better time to implement a solution?
• Is too late to look for solutions?

Once every aspect of the problem has been looked into it is not uncommon for other potential problems to be identified as well. It may be necessary to start the entire process again for these new problems, but remember that problems are best dealt with one at a time and with that in mind it is time for the next step, defining the problem.

STEP 3: Define the Problem

Only after the right problem has been identified and analysed can one be sure of the correct definition of the problem. In most cases the definition will remain unchanged from STEP 1, but in some cases once other available information has been brought to light the problem, the opportunity or the desired outcome may have changed to accommodate either new information or a new perspective on the problem itself.

The following definitions should be written down for future reference. If there is any hesitation with any of the definitions it can be a sign that you don’t fully understand the problem at hand and that the previous step should be re-visited.

• Define exactly what the problem is.
• Define exactly what needs to be solved.
• Define your problem as an opportunity.
• Define the desired outcome.

STEP 4: Develop Opportunities (Possible Solutions)

There is always more than one way to solve a problem and in some cases simultaneous solutions may be required. As with the previous steps it is essential that time is taken to develop plenty of innovative and creative ideas. At the end of this step you can be certain you will have the best solution if you have explored all possible avenues and generated every conceivable option. To help you find the best solution the following methods can be used.

Seek advice; ask an expert In today’s day and age there is an expert on pretty much any topic you can imagine. Sometimes the best and fastest approach to getting the information we need can be simply to ask someone who knows more about the subject than we do. Of course finding that someone can be a challenge in itself, but the rewards in doing so could far outweigh other options. If the expert is unsure about the best approach for your situation they will probably be able to point you in the right direction.

Brainstorming Best done with a group of individuals brainstorming is always a good starting point. Brainstorming involves creating a list of ideas spontaneously contributed by an individual or group of individuals. With this method there is no wrong answer and wild or unexpected answers are often encouraged with all suggestions being written down. The process continues until no more suggestions can be thought of and the list of ideas can later be used to develop a solution.

The Scientific Method A method for conducting an objective investigation which is a proven approach to solving problems in a way that is reliable, consistent and non-arbitrary. The scientific method can be seen to underlay the scientific revolution and has helped to create many of the great accomplishments of recent human history. A basic flow chart of the scientific method is shown below.

Have a Guess If there is some indication, a technique you have heard of or a gut instinct about a possible solution, why not look into it further. Starting with an inkling and checking and adjusting it to suit the problem at hand could lead to the ideal solution. This method generally works better for a limited number of potential solutions where you can eliminate the options one at a time but there is no harm in employing the method in any case, it might just lead to the solution you have been looking for.

Work Backwards If the “where to start” is not obvious starting at the end goal and working backwards can be a good approach. Working backwards can sometimes offer the fastest solution because it gets you thinking with where you want to end up in mind. This approach to problem solving can also be effective when used at a point not quite at the end goal or even to back check the starting point from a different perspective.

Do the Opposite What effect does doing the opposite to what you have been doing have on the situation? If you at a dead-end or simply want to explore the opposite of something that clearly isn’t working, doing the opposite can provide a new and refreshing perspective. Rather than avoiding a situation, doing a complete 180 and diving straight in can in some cases be the best and/or fastest approach.

A Randomized Approach When all else fails or there is no indication what so ever to what sort of approach should be taken a random approach may be required. By applying random solutions and seeing how they influence the problem at hand may eventually lead to something more meaningful. You might get lucky and find the solution you have been looking for or worst possible case you may just find yourself where you started.

If after numerous attempts without success it might be necessary to go back to previous steps and try to "look outside the square". Every now and then a problem presents itself that will require a bit more creativity to come up with a feasible solution.

STEP 5: Select the Best Solution

With a list of possible solutions developed in the previous step it is time to select the best individual or best combination of solutions to be put into action and to eliminate the problem at hand. The process of selecting the best solution is a matter of ranking all of the available solutions against one another and defining each options “pluses and minuses”. Some of the key areas that might need to be evaluated and prioritised have been listed below.

• Operational validity: Can the solution actually be implemented or is it just an idea?
• Economic validity: Is the solution economical? Will the solution bring an economic result?
• Degree of Complexity: Is the solution simple to implement or are there complexities involved?
• Ease of Implementation: Is the solution ready to go and easy to install?
• Stakeholder interest: Does the solution satisfy everyone’s interests.
• Potential Risk: Does the solution bring any additional risk with it?
• Personal commitment: Is the solution something that reflects the ideals of all involved? Is the solution something you believe in?
• End result: Will the solution solve all parts of the problem or will the problem just be reduced or concealed?

Keeping in mind that the best solution will be the result of considerable deliberation and also that one solution that is available for any problem is to simply do nothing, everything should now be in place for putting the solution into action. If something happens so that the chosen solution/s cannot be used or if the solution stops working, there will now be a list of alternatives already assessed, prioritised and ready to go.

STEP 6: Implement the Solution

The implementation plan is just as important as implementing the solution/s and monitoring the progress of this step is something that will need to be done also. A brief guide to some of the things that will need to be considered have been detailed below.

• Planning and documentation of a new solution/s
• When will the solution be implemented?
• Where will the solution be implemented?
• How is the solution to be implemented?
• What has to be done before the solution is implemented?
• How long will the solution take to start working?
• What time frame is the solution expected to take before the problem is solved?
• Have monitoring provisions been put in place?
• What are the key signs to look for to indicate the solution is working?
• Who will need to be notified about the changes about to take place?
• At what stages will the progress be reviewed?
• Have contingency arrangements been put in place for if the solution doesn’t work?
• What will be the next step if the solution doesn’t work?
• If required, have all agreements been documented and signed?
• How will it be confirmed that the problem has been solved?
• Are steps required to remove or disable the solution?
• What will happen once the problem has been solved?
• Putting the solution into action
• Put the solution into action
• Monitor the progress and effect of the solution
• Test and ensure the solution is meeting expectations and outcomes

STEP 7: Evaluate and Learn

Hopefully everything went to plan and the problem is now solved and even if it wasn’t, this step is still the same. It is vital that the whole process is evaluated from problem to solution and a good starting point is to document the 7 step procedure. This step is intended to not only provide a future reference but also a learning experience for future problem solving. At a very minimum the following questions should be answered:

• How effective was that particular solution?
• Did the solution achieve the desired outcomes?
• What consequences did problem solving activity have on my situation?

Top of Page

Problems at their most basic

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.

Understanding Process Capability Index (Cpk) [With Calculator]

Why You Should Use a Gantt Chart for Your Project

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…

• Decision Making
• Goal Setting
• Managing Performance
• Managing Projects and Change
• Managing Through Covid
• Personal Development
• Problem Solving
• Time Management
• Workplace Well-being
• Free Downloads

7 Problem Solving Steps

In a minute!

These 7 problem solving steps provide a short outline of a process to help you solve problems effectively. A structured process helps ensure you stay on track but before you start, remember:

“Do not focus on finding an answer: focus on defining the question” Peter Drucker

Part of our manage in a minute series, read this article to gain a quick overview of the right steps for effective problem solving. We end the article with two principles that perhaps aren’t applied often enough when we set out to solve a problem.

You may also want to read our article: problem solving questions, which raises five challenging and provocative questions, based on this 7 step problem solving process:

1 Find the Right Problems to Solve

Too often our approach to problem solving is reactive, we wait for the problems to arise. Firstly in our 7 problem solving steps, we advocate taking a proactive approach, go and find problems to solve; important and valuable problems. The real starting point then for any problem solving process is to find the right problem to solve.

2 Define the Problem

It is very tempting to gloss over this step and move to analysis and solutions. However, like the first step, it is one of the secrets of effective problem solving. Combining problems that are valuable to solve, with defining exactly what you are trying to solve, can dramatically improve the effectiveness of the problem solving process. The secret to defining the problem, is really about attitude. Try to see every problem as an opportunity.

3 Analyse the Problem

Analysis is a process of discovery of the facts, finding out what you know about the situation. In doing so you are breaking down complexity, stripping away the superficial and getting to the causes/issues.

4 Develop Opportunities

There are always more than one way to solve a problem, so take time to develop plenty of creative possibilities to solve the problem.

5 Select the Best Solution

Selecting is about making choices, about deciding. To do this you need to weigh up the competing value and risk of the different options you generated in the previous step.

6 Implement

Good solutions are often only as good as the way they are implemented. Implementation requires project management and a determination to deliver the outcomes essential to solving the problem you originally defined.

7 Evaluate and Learn

You will have done some things really well through this seven step problem solving process. It would be all too easy to forget them in rushing to solve the next problem, or to implement the solution. You should evaluate at least two areas:

• How you carried out the seven step problem solving process
• The effectiveness of the solution you implemented. Did it deliver the outcomes you expected?

7 problem solving steps, 2 principles

This process provides a challenge to other problem solving techniques. It highlights the undervalued problem solving skill of applying two under-used principles, at the start of the process :

Finding the right problems to solve

Focusing on opportunities created by the “problem”

The eighth problem solving step

• Tool 1: When you don’t know what to do
• Tool 2: Defining questions for problem solving
• Tool 3: Finding the right problems to solve
• Tool 4: Problem solving check-list
• Tool 4a: Using the question check-list with your team
• Tool 5: Problem analysis in 4 steps
• Tool 5a: Using 4 Step problem analysis with your team
• Tool 6: Questions that create possibilities
• Tool 6a: Using the 5 questions with your team
• Tool 6b: Putting creativity to work – 5 alternate questions
• Tool 6c: Workshop outline
• Tool 7: Evaluating alternatives
• Tool 8: Creative thinking techniques A-Z
• Tool 9: The 5 Whys technique

Further Reading

Seven step problem solving Problem solving exercises Problem solving questions Problem solving activity

>>> Return to the Problem Solving Knowledge Hub

I am designing a new management development programme for my company and your goal setting guide has really helped..

I like the way you introduced material I haven’t seen before ( SHARP action ) & the tools to apply the learning. The price represents really good value for money and I will be checking out more of your material over the coming months.

Matthew - UK

Other e-guides you may find useful

Problem Solving Bundle

Making Better Decisions

Managing Performance Bundle

Grab a Freebie

Sign up to our newsletter and receive "How to be a Happy Manager"

Grab a Freebie!

Sign up to our newsletter and receive a free copy of "How to be a Happy Manager"

• Name This field is for validation purposes and should be left unchanged.

The Happy Manager

• Testimonials
• Write For Us
• Terms & Conditions

Knowledge Hub

What's new.

• Interview Skills: How to Ace Your Job Interview
• 6 Strategies to Improve Workplace Productivity
• Boosting Workplace Performance Through Effective HR Support Services
• The Worker's Blues: Identifying and Preventing Employee Burnout
• Techniques for Crafting Powerful Team Presentations
• Why Your Business Location Has an Impact on Your Employees’ Happiness

© 2024 The Happy Manager. Part of Apex Leadership Ltd. Tel +44 (0)7572 797430

• Privacy Policy

Website by Limely

Click on the links to download your free tools

• Phone This field is for validation purposes and should be left unchanged.

This website uses cookies to ensure you get the best experience on our website. Learn More

7 Steps to an Effective Problem-Solving Process

September 1, 2016 | Leadership Articles

An effective problem-solving process is one of the key attributes that separate great leaders from average ones.

Being a successful leader doesn’t mean that you don’t have any problems. Rather, it means that you know how to solve problems effectively as they arise. If you never had to deal with any problems, chances are pretty high that your company doesn’t really need you. They could hire an entry-level person to do your job!

Unfortunately, there are many examples of leaders out there who have been promoted to management or leadership positions because they are competent and excel in the technical skills needed to do the work. These people find themselves suddenly needing to “think on their feet” and solve problems that are far more high-level and complicated than they’ve ever really had to deal with before. Are there tools available to these people to help them solve the problem correctly and effectively? Absolutely!

Today, I am going to introduce you to the Seven Steps of Effective Problem Solving that Bullet Proof® Managers are learning about, developing, and implementing in their teams.

Step 1: Identify the Problem

What are things like when they are the way we want them to be?

This question helps you find the standard against which we’re going to measure where we are now. If things were going the way we want them to go, what does that look like? If this person were doing the job we want him or her to do, what would they be doing?

And then ask this important question: How much variation from the norm is tolerable?

Therein lies the problem. From an engineering perspective, you might have very little tolerance. From a behavioral perspective, you might have more tolerance. You might say it’s okay with me when this person doesn’t do it exactly as I say because I’m okay with them taking some liberty with this. Some other issue you may need 100% compliance.

Step 2: Analyze the Problem

At what stage is this problem? This helps you identify the urgency of the problem, and there are generally three stages.

The emergent stage is where the problem is just beginning to happen. It does not cause an immediate threat to the way business operates every day. It is just beginning to happen and you have time on your side to be able to correct it without it causing much damage to the processes it is affecting. The mature stage is where this problem is causing more than just minor damage. Some amount of damage has been done, and you need to jump on it immediately to fix it before it becomes a problem where the consequences may be greater, deeper, and more expensive if we don’t solve this problem fast.

The third stage is the crisis stage, when the problem is so serious it must be corrected immediately. At this stage, real damage has been done to company processes, reputation, finances, etc. that will have potentially long-term effects on your ability to do business.

Step 3: Describe the Problem

You should be able to describe a problem by writing it in the form of a statement and you should do it in 12 words or less, assuming it’s not a complicated, scientific problem. This way, you have clarity exactly what the issue is. Then, perhaps try distributing it to your team to ensure they agree that this is the root of the problem, that it makes sense, and everyone that is working toward a solution is working toward the same goal.

The most important question of all, when describing your problem: Is your premise correct?

Let me give you an example of what I mean. We’ve all heard – or read – the story of the engineer’s take on the old “half empty, half full” question. A speaker holds up the glass of water and asks if the glass is half empty or half full, a discussion within the group ensues, and you generally expect some sort of lesson in optimism, etc. from it. In this version, an engineer is in the room and answers, “I see this glass of water as being twice the size it needs to be.”

You see, sometimes when you are the one in charge of the problem, you tend to set the premise of the problem from your own perspective. But, that premise may not be accurate, or it may just need an alternate perspective from which to see it. If your premise is not correct, or at least incomplete, you are not fully understanding the problem and considering all the best options for a solution.

Step 4: Look for Root Causes

This step involves asking and answering a lot of questions. Ask questions like: What caused this problem? Who is responsible for this problem? When did this problem first emerge? Why did this happen? How did this variance from the standard come to be? Where does it hurt us the most? How do we go about resolving this problem?

Also, ask the most important question: Can we solve this problem for good so it will never occur again? Because an important aspect to leadership is coming up with solutions that people can use for a long-term benefit, rather than having to deal with the same problems over and over and over.

Step 5: Develop Alternate Solutions

Just about any problem you have to deal with has more solutions to it than the one that you think of first. So, it is best to develop a list of alternate solutions that you and your team can assess and decide which one will be the best for the particular problem. I often use the ⅓ + 1 Rule to create consensus around one – or the top two or three solutions – that will be best for everyone involved.

Then rank those solutions based on efficiency, cost, long-term value, what resources you have and that you can commit to the solution of the problem. Then, look at every one of those solutions carefully and decide what you believe to be the best solution to this problem at this time.

Step 6: Implement the Solution

Implementing the solution you decide on can include creating an implementation plan. It could also include planning on what happens next if something goes wrong with the solution if it doesn’t work out the way you thought it would. Implementation means that everyone on your team knows and understands their part in making the solution work, that there are timelines for execution, and also that you have a system in place to track whether or not the solution has corrected the problem.

Step 7: Measure the Results

From your implementation plan in step 6, make sure you track and measure the results so you can answer questions such as: Did it work? Was this a good solution? Did we learn something here in the implementation that we could apply to other potential problems?

These seven simple steps will help you become a more effective, efficient problem solver in your organization. As you practice this process and develop the skills, these steps will become more natural to you until the point that you are using them without noticing!

About Crestcom International, LLC.

Crestcom International, LLC is an international leadership development organization, training more than one million leaders for 25,000 businesses in over 60 countries across the globe. Crestcom achieves this through a blend of live-facilitated multimedia video, interactive exercises, and shared learning experiences. Crestcom implements action plans and coaching accountability sessions to ensure measured development in key leadership competency areas. For more information, please contact your local Crestcom representative found here .

Interested in a free Leadership Skills Workshop with your team?

• Address instantly fixable issues that impact customer perceptions and employee morale.
• Learn and practice a habit that will raise employee performance.
• Set actions with specific and measurable steps that they'll gladly be accountable to achieve.
• Case Studies
• Leadership Articles
• Multi-Generational Leadership
• Owning a franchise
• Press Releases

Latest Posts

Stay Updated

Browse by topic.

[st-tag-cloud]

Privacy Overview

+44 (0)1335 347169

• Jul 12, 2023

The 7 step method for Practical Problem Solving skills & the 10 most common mistakes to avoid

Updated: Sep 13, 2023

Why do you need a Practical Problem Solving method?

Practical Problem Solving models are often shared online BUT the pitfalls are rarely well explained. In this blog we’ll be drawing on our own painful experience gained over 25 years, working across the world with hundreds of companies to illuminate those pitfalls. Here are the top 10 pitfalls as a list, scroll down for tips on how to avoid each.

Too big a problem

Looking in the wrong place

Brainstorming alone

Having a loose focus

Getting hung up on your fishbone

Switching between brain sides

Being rooted to the spot

Changing too much at once

Spending money too early

Not having a Plan to Check against

The Practical Problem Solving (PPS) model we learned and successfully applied from working with Toyota group, has 7 steps. We’ll show you each of those steps and the most common pitfall at each step.

We’ll even “open the kimono” and tell you about our personal biggest practical problem solving failure - more of that later. At the end we’ll share 3 secrets to help you to turbo charge your Practical Problem Solving

The initial question, as ever, has to be “Why do we need a method for Problem Solving?”

There are three main reasons

1) Containment

We’re generally okay at containment when a problem happens, at mopping up

2) Short-term countermeasure

We're not bad at coming up with a short-term countermeasure (solution) but

3) Recurrence Prevention

Most manufacturers aren't particularly strong on recurrence prevention - they don't get to the root cause

A common problem is people jumping to conclusions based on previous experiences, leading to the wrong conclusions because something is different to last time.

A Practical Problem Solving method

So, here's the Practical Problem Solving method, showing the 7 steps.

You can see that it's a funnel shape reflecting the fact that we're going from a large area, vaguely grasped and explained, down to a really focused problem that we've solved.

The 7 steps to our Practical Problem Solving method

The seven steps are:

1) “Grasp the current condition”

Understand what's going on and find your tight focus point

2) “Locate process causing the problem”

That's the process where it's caused not where it's found in in your physical process

3) “Investigate”

Using two tools often here, and for the next couple of steps - 5 why and fishbone

4) “Identify the probable causes”

Where we narrow down from our fishbone into what we think are the most likely causes – one, two or three of them and have a look at each in depth

5) “Identify the root cause”

What we as a team believe, through go-look-see observation and experimentation, is the root cause

6) “Countermeasure”

Try solutions, one at a time

7) “Confirm”

Using our PDCA cycle to make sure that we've got rid of the problem

Note the two things on the right of the funnel to look at. Firstly, it’s very important to protect the customer early and stop bad material or other problems flowing out to them. Secondly, you’ll see halfway down, after you've done a bit of investigation that you're ready to set a target: A “What?” by “How much?” by “When?”

A Problem Solving example: Fizzy drink canning factory

At Sempai we use a fizzy drink canning factory example as a Problem Solving example, along with our training materials, to help our clients start-to-finish through this process on their own shopfloor. Get in touch if you’d like us to help you this way. I’ll reference the fizzy drink can below.

10 Pitfalls in the 7 step Practical Problem Solving method

Let’s go back to the funnel model to look at the Problem Solving pitfalls

Step 1) - “Grasp the current condition” - Pitfall

The key pitfall here is NOT having a tight focus, having too broad a problem to try to solve. This is where our fizzy drink cans come in. On the picture below, having done some Data Analysis and using 80/20 thinking , if we just go after ‘dents’ our focus is too broad as there are actually 3 types of dents - 30 of one type, 8 of a second and 4 of a third. We’d pick the defect with 30 instances as it’s the highest (occasionally there are defects that have a lower frequency but cost more per defect).

Problem Solving is hard enough to do without trying to mix up and unpick a heap of variables affecting 3 different problems. If you try and do them all at once, you won't manage it. Picking 1 of the 3 to solve is good “Problem Framing”.

Step 2) - “Locate process causing the problem” - Pitfall

Critically, here you're not looking for the process where you FOUND the problem. It's where you identify that it's being CREATED. There's a very big difference between treating a symptom and a cause. Be careful that you’re not looking in the wrong spot.

Step 3) - “Investigate” - Pitfalls

This is often the area of biggest weakness, apart from Problem Framing in Step 1 above. When it comes to problem solving there are two major tools - Fishbone (aka Ishikawa diagram) and the 5 Whys. There are others, these are just the most common and useful.

The Fishbone and 5 Whys can be used together or they can be used independently. You don't always have to use both, but I'll come back to that later.

The first pitfall, in the Investigate step, is to brainstorm alone if you use a fishbone. Doing this, you only get one narrow set of ideas and experience. Involving other functions, like Maintenance for breakdowns, or Quality engineers for defects brings in other experts. Never, ever, forget to include the most important expert of all – your Operator. They know the process better than anyone as they live with it for 40 hours a week.

The second pitfall on this step is to remember is that you need a tight scope, a very tight problem well described. Not “dents” but a type of “dent” on a certain flavour of fizzy drink (if it’s made down a different line to the others!)

Step 4) - “Identify the probable causes” - Pitfalls

If you’ve used a Fishbone, you’ll then have maybe 20-40 post-it notes with possible causes on. You now go back over all of your post-it notes to identify the most probable causes. Don't get hung up trying to work out, scientifically, which are the right ones to pursue. Just agree as a team and pick the top two or three you believe. Then pursue them one at a time.

Also, don't try to critique AS YOU brainstorm as switching from one side of your brain (creative) to the other (analytical) gets the worst of both worlds. It’s mentally jarring and ideas won’t flow. Finish the brainstorm first, then critique the ideas respectfully.

Step 5) - “Identify the root cause” - Pitfall

Here you take your “probable causes” one a time and pursue the 5 whys – checking at each why stage whether what you’re suggesting is true. The pitfall here is simply staying in a training room or being rooted to the spot in the factory where you’re doing the Problem Solving. You can’t do either Step 4 or 5 in a training room or without looking at the process close up. Go-look-see and confirm on the shop floor.

Step 6) - “Countermeasure” - Pitfall

It’s really important to countermeasure (put a fix in place) for one thing at a time, otherwise you don't know which change got you the result - it's just a mix of variables. Don’t spend money too early, try solutions with old or scrapped materials, capital is scarce, thinking is free.

Step 7) - “Confirm” - Pitfall

Confirm is where we use our Plan Do Check Act (PDCA) cycle to see if our countermeasure has worked. To know if it has, you need something to compare against. So, at Plan stage, quantify the result you expect. For example, say after Step 4 “Investigate” that you have enough information to set a target. If you set that target at “20% reduction in dents in orange cans vertically across the bottom rim” and you only achieve 5% after countermeasure, you know that you’ve missed something.

Knowing when your Practical Problem Solving has worked!

There are two ways to check whether your countermeasures work:

You can recreate the problem at will

If you can turn it on and off you’ve sorted it

Data Analysis

When you do your daily or weekly Data Analysis, this specific problem doesn't occur again or is greatly reduced.

3 secrets to turbocharge your practical problem solving

We promised earlier to tell you about our biggest ever failure. That was 20 years ago when being trained by a Japanese sensei. We locked a team, for two days, in a room with a vaguely defined problem and created the world's biggest fishbone.

A fishbone that we guessed and speculated about and didn't go to the shop floor enough, to grasp and confirm. That combination of a bad focus and too many guesses meant it was a waste of time.

As promised, here’s a bonus of 3 secrets to turbocharge your practical problem solving:

Secret 1: Speed

If you can get to a problem fast it's like a fresh crime scene for a detective. It's warm, there's a body, there's a smoking gun and blood on the floor. It's easy to crack. If you get there late it's like a cold case

Secret 2: You don't always need a Fishbone

Some people love a fishbone but, to a man with a hammer, everything looks like a nail. We only use it in certain circumstances; like if we can't recreate a defect or it looks as though there are multiple variables involved, or if there's a benefit to getting a team around it.

Secret 3: Avoid problems altogether!

This is the closest we’ll get to a silver bullet. Train your people to be able to spot abnormality early, get your shop floor organised through your 5s and standardised work, so that you can react when things start to go wrong, rather than when there's a problem.

Number 3) is so powerful we've built a module dedicated to avoiding problems in SempaiGuide, our digital lean toolkit for manufacturers. Check out the demo here .

That’s the major pitfalls covered. One last piece of advice is to follow the steps, use data and verify on the gemba at every stage. Otherwise, you’re just guessing. To accompany this article, we’ve created this video on our YouTube channel

• Problem Solving
• Lean Skills

Recent Posts

How to find Abnormalities and not Problems in a lean factory

How to hone your Problem Solving Method through watching movies

80/20 Pareto rule in manufacturing – A key skill for Team Leaders

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)

• 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

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

• Prime Membership
• Team Training
• Career Path New

• No products in the basket.

7 Steps to Improve Your Problem Solving Skills

Our lives are full of problems. And the biggest problem is finding an effective solution to any problem. Seems funny, right? But it’s true. Every day, from your personal to professional life, you have to deal with different kinds of problems, and it’s not unnatural that sometimes you struggle to solve them. Though in the end, you find a solution, it takes too much effort and time. Don’t you think it would be better if you could find the solution in the first place? That’s where problem-solving skills would help you a way out. 

Problem-solving skills are vital to have in professional life. Many issues arise in the workplace and giving a quick touch up on them is an unwritten duty for you. In a professional setting, it doesn’t matter that much what solution you find to a problem. Rather it matters how you find that solution and how much time it takes. In this case, another skill which is Problem Solving Skills  merges up with problem-solving skills. Both are important for your regular duties in the workplace and your job growth, especially when you’re in a leadership or management position. f

7 Key Steps to Improve Your Problem Solving Skills

However, everyone is by born a problem solver. But the thing that counts is how efficiently the problem is being solved. That’s why you should nurture problem-solving skills to become an ultimate problem solver. In this article, you’re going to explore seven effective steps that will help you improve your problem-solving skills. So, without further ado, let’s dig deeper.

Step 1: Define The Problem

The first thing that comes when solving a problem is identifying and defining the problem. Without knowing the problem, you can’t move further. So, have a clear understanding of the problem for which you’re going to find a solution. Define the problem and make it precise. Since you won’t be working alone, describe the context, and make sure it is understandable by others who are involved in the decision-making process. However, different people have different perspectives on what a problem is, and you should keep it in your mind. 

If the problem involves software development or coding challenges, don’t hesitate to get coding help to ensure you’re on the right track and can communicate solutions effectively.

Step 2: Analyse The Problem

The second step to solving a problem is analysing the problem. It helps you understand the nature of the problem and find the possible ways out. Develop some creative problem-solving questions in this stage, such as why it is a problem, why it is required to solve it, how to find the solution, what barriers and opportunities lie within the problem, what effect it will cause if the problem isn’t resolved, etc. 

Develop these questions and assign answers to them. In the end, you’ll find a clear picture of the whole situation. This will help you prepare your strategy to solve the problem. 

Step 3: Develop Potential Solutions

Once you’re done with analysing the problem, you have to look for potential solutions to the problem. Note that I said solutions, not a solution. It’s essential to come up with multiple viable solutions to a problem. Because you don’t know yet what outcomes the action is going to bring about. That’s why you should have alternatives in all possible ways to solve the problem so that you can compare them and pick the best one. 

In this regard, you have to set a standard with which you will compare the expected outcomes of the potential solutions. However, don’t use the standard to judge the solutions, instead, use it only for coming up with ideas. 

Step 4: Evaluate The Options

After listing down the potential solutions to the problem, your next task is to analyse and evaluate the options. This will help you determine the most effective and suitable solution to the problem. Now it comes how to evaluate the options. Do it almost in the same way you’ve analysed the problem before. This means asking some questions and comparing the answers for different options. So, the creative problem-solving questions that you’ll make to evaluate the problem may look like the followings:

• Is the solution easily achievable?
• How much effort and resources it will take?
• Does it fit the organizational processes and cultures?
• What are the pros and cons of the solution?
• What is the possible outcome of this solution?
• Is it well suited to the time and budget?

Prepare the answers for each of the options and compare them. Then eliminate those which don’t pass the criteria and tailor the list for further action.

Step 5: Select The Best Option

After evaluating all the possible solutions and tailoring the list, you have a concise list of solutions to the problem. Now you have to choose the best solution among these options. Select the solution that is best fitted to the organizational cultures and goals, and meets all the criteria that you set for evaluating the options. In this case, your experience, courage, and decision-making skills will help you to determine the option.  

However, you may consult your peers as it would give you different insights into the situation. After selecting the best-suited solution, make the necessary documentation, and submit to the authority for approval.

Step 6: Implement The Solution

You’ve selected the solution to the problem and got it approved by the higher authority. Now it’s time to go for action and showcase your problem-solving skills. So, at first, you have to prepare a detailed work plan putting all the necessary things into it. You have to ensure that every one of your team understands the plan and what are their responsibilities to make the plan fruitful. So, you should communicate well with everyone involved in the plan. 

Also, your plan should include actions to be taken if something goes wrong or doesn’t go just like as you thought it would. This is important to make a concrete plan. After setting the plan, arrange everything you require and put your solution into action, and wait for the results. 

Step 7: Measure The Results

Your duty isn’t finished with the implementation of your solution. You have to keep track to measure the results and make sure the plan is performing well to solve the problem. Great leaders always keep follow-ups and proper documentation of their actions. It’s helpful in their future challenges and acts as a guideline for their successors. Moreover, it will help you show a scalable and notable outcome of your plan to the authority. 

Now it’s time to wrap up. Following these seven simple steps will strengthen your problem-solving skills and make you an efficient problem solver in your organization. However, problem-solving is a vast topic, and there are even more things to explore about it which aren’t possible to include in a single article. If you want to explore more and develop your problem-solving skills, it will be better to take training on this. 

But how can you attend formal training when you’ve lots of duties to do? In this case, you can consider taking online training where you can learn anytime from anywhere, and most importantly, without juggling your regular schedule. To help you in this regard, Training Express is offering an online course on problem-solving skills where you’ll be learning from experts. So what are you waiting for? Have a look at this. 

How Does Maintaining Employee Devices Boost Performance?

Best Ways to Find Email Addresses For Your Qualified Leads

What Are Commodities and Understanding Their Role in the Stock Market?

The Psychological Benefits of Blogging for Students: A Stress Relief Perspective

Unlocking Learning: The Unseen Advantages of Online Education

Finding Your Path: How to Choose the Right Career Using the RIASEC Model

• Available Courses
• Career Bundles 91
• Animal care 7
• Quality Licence Scheme Endorsed 111
• Teaching 13
• Teaching & Academics Primary 26
• Accounting & Finance Primary 34
• IT & Software 170
• Healthcare 129
• Marketing 32
• Health and Safety 417
• Construction 51
• Electronics 27
• Hospitality 22
• Health and Social Care 237
• Child Psychology 37
• Management 385
• Business Skills 277
• First Aid 70
• Employability 268
• Safeguarding 76
• Food Hygiene 105
• Personal Development 1373

https://www.trainingexpress.org.uk/wp-content/uploads/2021/07/logo-final-1-1.png

Upgrade to get unlimited access to all courses for only £49.00 per year, get 5 courses, only at £19.99.

Original Course Bundle Price £49.95

No more than 50 active courses at any one time. Membership renews after 12 months. Cancel anytime from your account. Certain courses are not included. Can't be used in conjunction with any other offer.

7 step problem solving technique

Whilst processes are generally there to protect us from issues (i.e. follow the process and get what you expect) unsurprisingly from time to time things go wrong and problems occur that affect either the output or the success of the process in question.

What do Business problems cause? Well, they can affect a whole host of things, from Quality, Schedule or Cost for example. Left alone they can impact both your customer and business and therefore resolving them is the appropriate route of action but given that there are a plethora of problem-solving tools available which one should you follow? What makes the 7 steps of problem-solving a suitable tool to utilize?

In this article, we’ll take a look at the 7 Step problem-solving tool, what it is, what the steps are, and how to avoid the key problems.

Firstly, let’s state the obvious when problems do occur it’s absolutely fundamental to have a structured method of resolving them. By providing structured problem-solving tools to your workforce, employees should be able to resolve issues in a timely and cost-effective manner and avoid stabbing around in the dark for a possible solution without having done the work to ensure it is.

Whilst we’ve covered more formal methods of problem-solving such as the 8d report , 5 whys (you can check out our post on how to create a 5 why template here) and others, the 7 steps of the problem-solving method represents another structured step by step process which can be used to analyze and resolve problems by uncovering root causes and helping to define corrective actions to fix the problem.

Why Structured problem-solving works

One of the main challenges with problem-solving is to avoid the obvious trap of thinking you know the answer and launching immediately into fix it mode. Unfortunately in many cases particularly in complex business situations the answer is rarely obvious and is often a combination of contributory factors that require a level of uncovering through following a step by step approach ahead of launching off and implementing a random “hit and hope” solutions.

The 7 step problem resolving solution offers just that a methodical approach that can be used to resolve issues by following a standard approach. It must be remembered that effective problem solving does take time. Also, consider that problem solving doesn’t have to be tied down to one tool and that you can choose to combine methods i.e the 7 step method combined with 5 why to help drill down and understand root causes.

The approach can be used in situations where you have large or small issues and works great in a team-based approach or if you’re working on your own as an individual.

What are the 7 problem-solving steps

Below is the list of steps associated with this tool

STEP 1: The Right Problem to Solve STEP 2: Analyse the Problem STEP 3: Define the Problem STEP 4: Develop Opportunities (Possible Solutions) STEP 5: Select the Best Solution STEP 6: Implement the Solution STEP 7: Evaluate and Learn

STEP 1: Identify the problem

The first step is to define the problem that you have.

Generating a robust problem definition is key to the whole process. Start your process with a poor problem definition and you’ll be wasting your time later on which is likely to result in you reworking some of the process steps – worse still you follow the entire process define a corrective action that results in other issues (or costs your firm money in implementation that may not recover!).

A good problem definition includes a clear description of the issue in contrast with the condition that it should be. For example,

• The houses were all painted green instead of blue
• The part was manufactured to a tolerance of 1cm instead of 1/2 a cm
• The part included paint on areas identified by the drawing that should not include paint.

The above show clearly what’s wrong and contrasts the “current condition” with the “should be condition”.

Of course, you could use something like – “the part is manufactured incorrectly” but that would make both developing a solution and implementation somewhat difficult as it is not clear what’s wrong.

STEP 2: Defining your Goal

Once you’re aware of what your problem is the next step is to define where you’ll be at the end of your problem-solving process.

For example – let’s look at one of our examples from above • The houses were painted green not blue.

Here the goal may be defined as “Problem root causes identified/rectified and all houses to be reworked and painted blue within the next 3 weeks.”

The goal clearly removes the problem and sets the end result to the desired condition.

Remember, your goal should be SMART (Specific, measurable, achievable, realistic and time-bound).

STEP 3: Brainstorm the solution

Brainstorming is usually a group based method where through gathering ideas the team endeavors to find an answer to the specific issue or problem. Brainstorming usually requires each member of the team to put forward their ideas.

Ideas are usually captured on a whiteboard, list, or set of post it notes in order to then evaluate them.

With Brain-storming it’s important to ensure all members of the team have an equal voice and that collection of ideas is seen as the priority. Do not let people take over this by thinking they have all the answers (especially the management!!) – you may be surprised by who in the team comes up with best contributions.

STEP 4: Assess your solutions/alternatives

Following the brainstorming session – the next step is to evaluate each idea.

In problem-solving, the best method is to assess whether the idea impacts the believed root cause of the issue and if it does how. Generating ideas is great but if they fail to help fix the thing that’s actually going wrong then they are not going to help much. So initially challenging each idea’s effect on possible root causes is usually a good initial step.

Evaluation usually means a systematic approach to reviewing the positives and negatives of each solution put forward in order that the team can then select a final solution.

STEP 5: Select a solution

Once you’ve brainstormed the possible solutions and evaluated them, you need to pick one (or a collective of some) – this is usually the key element where some teams go awry by selecting solutions that may not have the desired impact.

Using a tool such as a Solution Selection Matrix can often help simplify the process and apply some rigor in ensuring this part of the process remains focussed.

What is a Solution Selection Matrix?

The Solution Selection matrix is a tool that can be used to help review each idea by a standard process and criteria. It’s typically a table that lists the possible ideas and then has columns that then helps you evaluate them.

The Solution Selection Matrix might include evaluation of things like

• Ease of deployment
• resource requirement
• time to implement
• Impact on stakeholders etc.

See below for an example matrix that demonstrates how this can be achieved.

I’d recommend engaging your key stakeholders at this point to discuss the resolution to the problem, how you’ll implement and the impact on the implementation (discussing things like whether the implementation will take effect immediately or after a given time).

I’d also suggest that you review your KPI’s, to understand what the current situation looks like so that you’ll be able to easily demonstrate the impact post-implementation (and if you don’t have KPI”s you can always consider implementing some simple metrics at this point).

STEP 6: Implement

Once you’ve selected your solution it’s time to implement.

Here you should develop the implementation plan that takes you through the steps of the “fix” upfront of the deployment, this way the whole team understands what’s happening and how it will work. This also provides an opportunity to critique the timeline, resource requirement, and likely cost.

The plan is usually best combined with a RAIL (Rolling ActIons List) this explains what actions are active and who owns them and when they need to be done by. A simple implementation plan that shows target dates and owners is normally all that you require to help administer this stage.

Depending on the complexity of the solution you may wish to review possible risks up front of the deployment to assess where things might go wrong.

Don’t overestimate what you can achieve here, it’s best to be realistic, considering:

• Who will implement
• How you will implement
• How you will monitor the fix
• what budget/resources you might require to implement the fix
• Will the fix start working straight away (if not when)

Management can sometimes have a tendency to think that when you come up with the “fix” it impacts straight away so it’s a good time to get everyone on the same page with what your implementation actually means and when results are likely to be seen.

STEP 7: Evaluation

The final stage is to evaluate your problem’s resolution with the key question being – did your problem-solving project drive the result you wanted?

If you have KPI’s you can track them against your fix, you might involve some stakeholder engagement to understand what the fix has meant for them and their views on the implementation, what worked and what didn’t so that you can evaluate your businesses process for next time.

Alternatives to the 7 problem solving steps.

As we discussed at the outset of the article there are a number of problem-solving techniques out there, from 8d to 5 why to SWOT etc, you can check some of them

Before you settle on an approach I’d recommend that evaluate some of these approaches, examining the pros and cons and how they might fare in your industry. As ever it’s likely that one size doesn’t fit all and you and always look to tweak the process whilst keeping the basic steps. Businesses are likely to be far more accepting of a structured process that gets improved upon over time than no process at all.

Got some thoughts on problem-solving, be sure to check out our Problem Solving Guide , perhaps you have a favorite tool or method? We’d love to hear about it, fire us up on Twitter, or our feedback section below.

Our Content

• Calculators
• Career Skills
• Communications
• Human Resources
• Strategy and Leadership
• Supply Chain Management