structured problem solving benefits

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

• Quality Improvement
• Talk To Minitab

The Basics of Structured Problem-Solving Methodologies: DMAIC & 8D

Topics: Minitab Engage

When it comes to solving a problem, organizations want to get to the root cause of the problem, as quickly as possible. They also want to ensure that they find the most effective solution to that problem, make sure the solution is implemented fully, and is sustained into the future so that the problem no longer occurs. The best way to do this is by implementing structured problem-solving. In this blog post, we’ll briefly cover structured problem-solving and the best improvement methodologies to achieve operational excellence. Before we dive into ways Minitab can help, let’s first cover the basics of problem-solving.

WHAT IS STRUCTURED PROBLEM-SOLVING?

Structured problem-solving is a disciplined approach that breaks down the problem-solving process into discrete steps with clear objectives. This method enables you to tackle complex problems, while ensuring you’re resolving the right ones. It also ensures that you fully understand those problems, you've considered the reasonable solutions, and are effectively implementing and sustaining them.

WHAT IS A STRUCTURED PROBLEM-SOLVING METHODOLOGY?

A structured problem-solving methodology is a technique that consists of a series of phases that a project must pass through before it gets completed. The goal of a methodology is to highlight the intention behind solving a particular problem and offers a strategic way to resolve it. WHAT ARE THE BEST PROBLEM-SOLVING METHODOLOGIES?

That depends on the problem you’re trying to solve for your improvement initiative. The structure and discipline of completing all the steps in each methodology is more important than the specific methodology chosen. To help you easily visualize these methodologies, we’ve created the Periodic Table of Problem-Solving Methodologies. Now let’s cover two important methodologies for successful process improvement and problem prevention: DMAIC and 8D .

8D is known as the Eight Disciplines of problem-solving. It consists of eight steps to solve difficult, recurring, or critical problems. The methodology consists of problem-solving tools to help you identify, correct, and eliminate the source of problems within your organization. If the problem you’re trying to solve is complex and needs to be resolved quickly, 8D might be the right methodology to implement for your organization. Each methodology could be supported with a project template, where its roadmap corresponds to the set of phases in that methodology. It is a best practice to complete each step of a given methodology, before moving on to the next one.

MINITAB ENGAGE, YOUR SOLUTION TO EFFECTIVE PROBLEM-SOLVING

Minitab Engage TM was built to help organizations drive innovation and improvement initiatives. What makes our solution unique is that it combines structured problem-solving methodologies with tools and dashboards to help you plan, execute, and measure your innovation initiatives! There are many problem-solving methodologies and tools to help you get started. We have the ultimate end-to-end improvement solution to help you reach innovation success.

Ready to explore structured problem-solving?

Download our free eBook to discover the top methodologies and tools to help you accelerate your innovation programs.

See how our experts can train your company to better understand and utilize data. Find out more about our Training Services today!

You Might Also Like

• Trust Center

© 2023 Minitab, LLC. All Rights Reserved.

• Terms of Use
• Privacy Policy
• Cookies Settings

Continuous Improvement Toolkit

Effective Tools for Business and Life!

A3 Thinking: A Structured Approach to Problem Solving

• 5 MINUTES READ

Also known as A3 Problem Solving.

Variants include 8D and CAPA.

A significant part of a leader’s role involves addressing problems as they arise. Various approaches and tools are available to facilitate problem-solving which is the driving force behind continuous improvement. These methods range from the advanced and more complex methodologies like Six Sigma to the simpler and more straightforward A3 thinking approach.

The power of the A3 approach lies in its systematic and structured approach to problem-solving. Although it appears to be a step-by-step process, A3 is built around the PDCA philosophy. It relies on the principle that it is much better to address the real root-cause rather than trying to find a solution. Hence, it’s important not to jump to the solution when solving a problem as it is likely to be less effective.

A3 thinking provides an effective way to bring together many of the problem-solving tools into one place. For example, techniques such as the 5 Whys and fishbone analysis can be used during the ‘Analysis’ stage to help identifying the root causes. Additionally, visual aids and graphs are highly recommended in the A3 report, as they are more effective than text in communicating ideas and providing concise project updates.

A3 thinking involves the practice of consolidating the problem, analysis, countermeasures, and action plan onto a single sheet of paper, commonly an A3-sized sheet. This brief document serves as a summary of the project at hand and is regarded as a valuable storytelling tool for project communication. Utilizing the A3 approach doesn’t require any specialized software or advanced computer skills. You may however use readily available A3 templates , or rely on basic tools such as paper, pencil and an eraser as you will need to erase and rewrite several times.

One of the characteristics of the A3 approach is that it does not get into specific details. Detailed documents are usually attached to the A3 report to prevent overwhelming the reader with an excess of information.

The A3 process is typically structured in multiple stages based on the PDCA model. The primary focus is on developing understanding of the current situation and defining the desired outcome before thinking about the solution. While the exact number of stages may vary depending on the preference of the company, what truly matters is adhering to a structured approach to problem-solving.

A3 Seven Stages Model

An A3 process is often managed by an individual who should own and maintain the A3 report. This individual takes the lead in steering the process, facilitating team involvement, and preparing the A3 report with team input. One of the most common models for A3 thinking is the seven stages model which is described in the following.

1. Background – The first step is to identify the business reason for choosing this problem or opportunity. In this stage, you need to identify the gap in performance and the extent of the problem.

2. Current situation – The purpose of this stage is to document the current state of the problem. You may need to refer to the process map or go to the Gemba to truly understand the current situation.

3. Target – The purpose of this stage is to define the desired future state. Clearly identify the expected benefits from solving the problem, the scope, and the key metrics that will help measure the success of the project.

4. Analysis – The objective of this stage is to conduct an in-depth analysis of the problem and understand why it’s happening. It might involve tools like the 5 Whys and cause-and-effect analysis, as well as advanced statistical methods.

5. Countermeasures – Countermeasures are the actions to be taken to eliminate root causes or reduce their effects. The team should brainstorm and evaluate possible countermeasures based on the analysis conducted earlier.

6. Implementation Plan – To achieve the target, develop a workable plan to implement the countermeasures. Gantt charts are great ways to manage implementation plans very simply and easily. Once the action plan is finalized, the team should begin working on the activities needed to implement the countermeasures.

7. Follow-up – The final stage involves evaluating the implementation of the plan and the results achieved. Follow-up actions are important to ensure the benefits extend beyond the project’s completion.

A3 thinking is considered to be the practical form of the PDCA model.

There are many online templates that can be used to manage your problem-solving efforts. One of the simplest and most straightforward ways is to use this A3 problem solving template .

Wrapping Up

A3 thinking represents a logical and structured approach for problem solving and continuous improvement. This approach can be used for most kinds of problems and in any part of the business. Originating from the Toyota Production System (TPS), it has been adopted by many Lean organizations around the world.

A3 thinking not only provides a systematic approach for problem-solving. The development of a continuous improvement culture is at the core of A3 thinking. It has become one of the most popular Lean tools today where people and teams work together to solve problems, share results and learn from each other.

Other Formats

Do you want to use the slides in your training courses?

A3 Thinking Training Material – $18.85

Related Articles

Project Charter

Gantt Chart

Related Templates

A3 Problem Solving

Written by:

CIToolkit Content Team

The Complete Guide to Structured Problem Solving

When you are looking to thoroughly solve a pesky problem, structured problem solving is the way to go. Structured problem solving allows you to explore the problem, get to the heart of the issue, and develop a creative solution that finally solves the issue.

To illustrate this example, Takashi Amano was a nature photographer and avid aquarist. He started developing art in the form of fish tanks – which he called nature aquariums. The problem was algae would grow in his tanks and ruin his art. Not deterred, Mr. Amano found a shrimp distributor who bred, small, and clear micro-shrimp which were various algae eaters. Mr. Amano ordered thousands of them and promoted them in the hobby – to the point where the shrimp are now called Amano Shrimp.

He got creative. Knowing he needed a lasting solution to his algae problem, a clear shrimp that would eat the algae and not detract from his art was perfect.

The Basic idea of Structured Problem Solving

Professionals who solve complex problems for a living all start from the same place. They need to understand the actual problem they are solving. They ask themselves questions to get to the heart of the problem.

Usually promoting thinking with questions like what is the real problem, how can we gather data about the root problem, brainstorm solutions, test a solution and monitor it?

Why Structured Problem-Solving Works

Often, we are eager to jump into solving the first apparent problem with a variety of solutions. Why structured problem-solving works is because it forces us to slow down. By slowing down, we understand the problem first, without leaping into “fix-it” mode with preconceived notions of how the problem should be solved.

Studies have also found that having explicit techniques (methods for problem-solving) in the structured problem-solving workflow not only improves the problem-solving process but also increases the knowledge base all individuals can pull from.  Basically, using structured problem solving allows better solutions to be developed while ensuring everyone participates in sharing their own unique knowledge.

The two ideas translate into the problem-solving principles of:

• Seek to understand before we seek to solve
• Search early, search often

By understanding the problem inside and out, the individual, or team can make more informed decisions and generate appropriate solutions.

There are a variety of techniques to work through the process. Below are some sample ways to do structured problem solving before getting into the walk-through further down in the article.

Multiple Ways of Structured Problem Solving

There are many techniques to perform structured problem solving, or at least get more in-depth in certain aspects of the process. Some of my favorite ones include

Pre-mortem analysis: Instead of working through a project and assessing what went wrong at the end, run through a simulation of the project to see where the project could fail before you even start. Where and why did it fail? Then brainstorm solutions to avoid those issues without creating new ones.

The Hat Technique: There are 6 colored hats, all with different roles. Whether alone or in a group, assign some time or a specific person to that role. Having a person designated to each role means that all ideas are validated through six different lenses. Plus, everyone has a designated role which helps keep people engaged, and limits feelings getting hurt since everyone is simply doing their assigned role.

PDCA Cycle: An easy way to remember the process is the PDCA cycle. Which stands for Plan-Do-Check-Act. PDCA is a high-level way to remember how the structured problem-solving process works. 

You can also use the PDCA Model to manage your personal development too !

Get the Creative Juices Flowing

I like to start all my structured problem-solving sessions with some fun at the beginning of the session to get everyone’s creative juices flowing. By taking the 5 minutes to have a little fun, it is surprising how much more creative and engaged people are with the structured problem-solving process!

Problem-solving can be a stressful process, and it can even be high-stakes with the future of the group’s work hanging in the balance. However, laughing together helps relieve stress, makes people more creative, and improves social bonding.

The New Idea: One creative thinking exercise to start your session in a fun way, the goal is to split into two groups. Each group generates two dissimilar words. Then they swap words. For instance, “bug” & “sky-diving” and “winter” and “bikinis” for the other. Then the groups must devise the best ideas for those two words. For the bugs, you could make parachute designs that are themed after a different butterfly, and for the other, you could make a winter work-out with the goal have bikini-ready bodies by the summer. Silly ideas but shows there is a solution to even the weirdest problems.

Horrible idea challenge: Think of your problem. Then have everyone compete to come up with the worst idea. The practical part is that it helps to see what not to do – plus, part of the fun is seeing how creative people can be!

Beyond the two creative ideas, there are also 13 mental models which make work easier overall as well.

The Structured Problem Solving Process

1. define the problem statement.

The first step is defining what the real problem is. Below are some prompts to get the right decision-makers and problem-solvers sent in the right direction to tackle the challenge.

• Is the problem many problems?
• What requirements must a solution meet?
• Which problem solvers should we engage?
• What information and language should the problem statement include?
• Tip: To engage the largest number of solvers from the widest variety of fields, a problem statement must meet the twin goals of being extremely specific but not necessarily technical.
• What do solvers need to submit?
• What incentive do solvers need?
• How will solutions be evaluated, and success measured?

Problem statements are a statement of a current issue or problem. For example , Problem: Voter turnout in the southwest region of Florida has been significantly decreasing over the past decade, while other areas of the state continue to see increasing numbers of voters at the polls.

Writing one or two sentences takes the whole issue and makes it very clear what the issue is.

2. Root Cause Analysis

After getting the foundation set, an understanding of the root problem is critical. If you want to go through all the effort of structured problem solving, you might as well get to the real problem in the end.

Think of weeds in a garden. A potential solution is to mow over the weeds and they are gone. However, every few days the weeds keep coming back. That is because the root is the root issue in this scenario. You need to get the whole root system of the weed out to stop those pesky weeds in your garden.

Below are three techniques to help with Root-Cause Analysis

5 whys: When a problem occurs, drill down to its root cause by asking “Why?” five or more times. Then, when a counter-measure becomes apparent, you follow it through to prevent the issues from recurring.

Fishbone diagram: (Also called Ishikawa diagram named after Kaoru Ishikawa) is a cause-and-effect diagram that helps managers track down the reasons for imperfections, variations, defects, or failures.

Cause mapping: a cause map provides a visual explanation of why an incident occurred. It connects individual cause-and-effect relationships to reveal the system of cause within an issue.

3. Gather Data

After analyzing the problem and getting to the root cause – you need to gather information to understand why the problem and situation are happening. Doing the research and understanding how the different forces are interacting lets you understand why the problem is happening and how the overall solution is occurring.

Below are three different methods for gathering data to understand the context and interplaying forces in the current problem.

Gemba walk: The purpose is to allow managers and leaders to observe actual work process, engage with employees, gain knowledge about the work process, and explore opportunities for continuous improvement

Process mapping: A process map is a planning and management tool that visually describes the flow of work. Allowing you to see hiccups, bottlenecks, or high-failure points in the process.

Focus groups : Asking open-ended questions to a group of individuals ranging from 6-10 people. Letting you get different perspectives on the same issue.

4. Develop Potential Solutions

The next part is the fun part. You take all the research you’ve gathered in the first three aspects and put them together to come up with a solution to solve the problem. The common way is do Brainstorming.

Harvard Business Review sites that traditional brainstorming, in groups trying to answer the question, isn’t as effective as individuals coming up with ideas on their own first. Working in a big group doesn’t work for many reasons. Working in groups encourages social loafing (coasting on other’s ideas), some members experience social anxiety (introverted members feeling self-conscious of throwing in ideas), and it focuses too much on the solutions over the problem.

The better way to brainstorm is to have everyone work on the main problems and their solutions alone, and then reconvene after twenty minutes. Then everyone shares their top one or two ideas and what features of the problem it tackles.

This method gives everyone time to think about their solutions, present their ideas, and lets all the voices be heard. Plus, all the ideas can then smashed together to come up with a solution based on everyone’s input.

Remember, the solution has to solve the core of the issue and get to the root cause. Plus, it must be feasible in terms of the money, time, and manpower allocated to the project. Use the constraints as a guide to direct the project!

5. Implement a Solution

After running through the potential solutions – pick one and trial run it. Think of the minimum viable product to get to the root cause. You won’t know if you are alleviating the problem until a potential solution is out in the field.

For example , Airbnb founders, Brian Chesky and Joe Gebbia could not afford the rent for their apartment (the problem). They decided to put an air mattress in their living room and turn it into a bed and breakfast (MVP solution). The goal was to make a few bucks, but instead, they discovered the idea the connect Bed and Breakfasts to people looking for renters. They started advertising on Craiglist, then their website, and the story continues.

The point of the story is to illustrate that small tests can be done to see if you are solving the main issue! Their issue was not that someone needed to stay in their apartment for them to make rent – the issue was there was no service that easily let Bed and Breakfasts work with potential clients.

6. Monitor for Success

Once a solution is implemented, that is not the end. You must make sure the solution works. Keeping in mind the below questions

• Who is responsible for the solution?
• What are the risks of implementing the solution?

Some ways to monitor for success are:

Failure mode and effect analysis: A step-by-step approach for identifying all possible failures in a design, a manufacturing process, product, or service.

Impact analysis: A detailed study of business activities, dependencies, and infrastructure. It reveals how critical products and services are delivered and examines the potential impact of a disruptive (or additive solution) event over time

Kaizen : The Japanese term for “continuous improvement”. It is a business philosophy regarding the process that continuously improves operations and involves all employees.

Illustrated Example

A often find it helpful to see someone do the process as well. Here is a great video of IDEO re-working the shopping cart.

Key Take-Aways

What sets apart okay problem solvers from great problem solvers is the ability to think in repeatable, useful frameworks.

Structured Problem Solving is a general concept used to solve challenging problems, and there are hundreds of different methods that fall underneath it.

Action Item

Think of a tough challenge you are facing at work or in your personal life. Test run your problem through the structured problem-solving process with a few of the above techniques, and see what solution you can generate to get to the root of the issue!

Share this:

• Click to share on Pinterest (Opens in new window)
• Click to share on LinkedIn (Opens in new window)
• Click to share on Facebook (Opens in new window)
• Click to share on Twitter (Opens in new window)
• Click to share on Reddit (Opens in new window)
• Click to share on Tumblr (Opens in new window)

Post navigation

Previous post.

I do agree with all of the ideas you’ve presented in your post. They’re really convincing and will definitely work. Still, the posts are too short for starters. Could you please extend them a bit from next time? Thanks for the post.

Hello, I love hearing the feedback. I will write a follow-up post the structured problem solving that dives into more detail!

Thank you for some other fantastic article. The place else could anyone get that kind of information in such an ideal method of writing? I have a presentation subsequent week, and I am at the search for such info.

Hello – for similar content, the perspective and ambition parts of the blog have similar content! Some posts to investigate are “A 4 Step Plan to Better Goal Setting (WOOP)” ( https://themobiusstripblog.com/4-step-process-to-better-goal-setting/ ) and “How to Give a Better Presentation” ( https://themobiusstripblog.com/better-presentation/ ). Let me know how your presentation goes!

Hey there! I know this is kinda off topic nevertheless I’d figured I’d ask. Would you be interested in exchanging links or maybe guest authoring a blog post or vice-versa? My blog covers a lot of the same subjects as yours and I feel we could greatly benefit from each other. If you might be interested feel free to shoot me an email. I look forward to hearing from you! Great blog by the way!

Hello, I am always interested in providing valuable content to my readers! Send me an email either directly from the “Contact Us” page or fill-out the interest form and I can get back to you!

Leave a Reply Cancel reply

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

Notify me of follow-up comments by email.

Notify me of new posts by email.

A Step-by-Step Guide to A3 Problem Solving Methodology

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.

Problem-solving is an important component of any business or organization. It entails identifying, analyzing, and resolving problems in order to improve processes, drive results, and foster a culture of continuous improvement. A3 Problem solving is one of the most effective problem-solving methodologies.

A3 Problem solving is a structured and systematic approach to problem-solving that originated with the lean manufacturing methodology. It visualizes the problem-solving process using a one-page document known as an A3 report. The A3 report provides an overview of the problem, data analysis, root causes, solutions, and results in a clear and concise manner.

A3 Problem Solving has numerous advantages, including improved communication, better decision-making, increased efficiency, and reduced waste. It is a powerful tool for businesses of all sizes and industries, and it is especially useful for solving complex and multi-faceted problems.

In this blog post, we will walk you through the A3 Problem Solving methodology step by step. Whether you are new to A3 Problem Solving or simply want to improve your skills, this guide will help you understand and apply the process in your workplace.

What is A3 Problem Solving?

A3 Problem Solving is a structured and systematic approach to problem-solving that makes use of a one-page document called an A3 report to visually represent the process. The A3 report provides an overview of the problem, data analysis, root causes, solutions, and results in a clear and concise manner. The method was created within the framework of the Lean manufacturing methodology and is based on the principles of continuous improvement and visual management.

Looking for a A3 Problem solving template? Click here

Origin and History of A3 Problem Solving

A3 Problem Solving was developed by Toyota Motor Corporation and was first used in the manufacture of automobiles. The term “A3” refers to the size of the paper used to create the report, which is an ISO standard known as “A3”. The goal of the A3 report is to provide a visual representation of the problem-solving process that all members of the organisation can easily understand and share. A3 Problem Solving has been adopted by organisations in a variety of industries over the years, and it has become a widely used and recognised method for problem-solving.

Key Principles of A3 Problem Solving

The following are the key principles of A3 Problem Solving:

• Define the problem clearly and concisely
• Gather and analyze data to gain a deep understanding of the problem
• Identify the root causes of the problem
• Develop and implement effective solutions
• Evaluate results and continuously improve

These principles serve as the foundation of the A3 Problem Solving methodology and are intended to assist organisations in continuously improving and achieving their objectives. Organizations can effectively solve problems, identify areas for improvement, and drive results by adhering to these principles.

Step 1: Define the Problem

Importance of clearly defining the problem.

The first step in the A3 Problem Solving process is critical because it lays the groundwork for the remaining steps. To define the problem clearly and accurately, you must first understand the problem and identify the underlying root cause. This step is critical because if the problem is not correctly defined, the rest of the process will be based on incorrect information, and the solution developed may not address the issue effectively.

The significance of defining the problem clearly cannot be overstated. It aids in the collection and analysis of relevant data, which is critical for developing effective solutions. When the problem is clearly defined, the data gathered is more relevant and targeted, resulting in a more comprehensive understanding of the issue. This will enable the development of solutions that are more likely to be effective because they are founded on a thorough and accurate understanding of the problem.

However, if the problem is not clearly defined, the data gathered may be irrelevant or incorrect, resulting in incorrect conclusions and ineffective solutions. Furthermore, the process of collecting and analysing data can become time-consuming and inefficient, resulting in resource waste. Furthermore, if the problem is not accurately defined, the solutions developed may fail to address the root cause of the problem, resulting in ongoing issues and a lack of improvement.

Techniques for Defining the Problem

The first step in the A3 Problem Solving process is to clearly and accurately define the problem. This is an important step because a clearly defined problem will help to ensure that the appropriate data is collected and solutions are developed. If the problem is not clearly defined, incorrect data may be collected, solutions that do not address the root cause of the problem, and time and resources may be wasted.

A problem can be defined using a variety of techniques, including brainstorming , root cause analysis , process mapping , and Ishikawa diagrams . Each of these techniques has its own advantages and disadvantages and can be used in a variety of situations depending on the nature of the problem.

Best Practice for Defining the Problem

In addition to brainstorming, root cause analysis, process mapping, and Ishikawa diagram s, best practices should be followed when defining a problem in A3 Problem Solving. Among these best practices are:

• Define the issue in a specific and quantifiable way: It is critical to be specific and concise when defining the problem, as well as to quantify the problem in terms of its impact. This will help to ensure that all stakeholders understand the problem and that data collection is focused on the right areas.
• Focus on the problem’s root cause: The A3 Problem Solving methodology is intended to assist organisations in identifying and addressing the root cause of a problem, rather than just the symptoms. Organizations can ensure that their solutions are effective and long-lasting by focusing on the root cause of the problem.
• Ascertain that all stakeholders agree on the problem’s definition: All stakeholders must agree on the definition of the problem for the A3 Problem Solving process to be effective. This ensures that everyone is working towards the same goal and that the solutions developed are relevant and appropriate.
• Consider the problem’s impact on the organisation and its stakeholders: It is critical to consider the impact of the problem on the organisation and its stakeholders when defining it. This will assist in ensuring that the appropriate data is gathered and that the solutions developed are relevant and appropriate.

Organizations can ensure that their problem is defined in a way that allows for effective data collection, analysis, and solution development by following these best practices. This will aid in the development of appropriate solutions and the effective resolution of the problem, resulting in improvements in the organization’s processes and outcomes.

Step 2: Gather Data

Gathering data in a3 problem solving.

Data collection is an important step in the A3 Problem Solving process because it allows organisations to gain a thorough understanding of the problem they are attempting to solve. This step entails gathering pertinent information about the problem, such as data on its origin, impact, and any related factors. This information is then used to help identify root causes and develop effective solutions.

One of the most important advantages of data collection in A3 Problem Solving is that it allows organisations to identify patterns and trends in data, which can be useful in determining the root cause of the problem. This information can then be used to create effective solutions that address the problem’s root cause rather than just its symptoms.

In A3 Problem Solving, data collection is a collaborative effort involving all stakeholders, including those directly impacted by the problem and those with relevant expertise or experience. Stakeholders can ensure that all relevant information is collected and that the data is accurate and complete by working together.

Overall, data collection is an important step in the A3 Problem Solving process because it serves as the foundation for effective problem-solving. Organizations can gain a deep understanding of the problem they are attempting to solve and develop effective solutions that address its root cause by collecting and analysing relevant data.

Data Collection Methods

In A3 Problem Solving, several data collection methods are available, including:

• Observations
• Process diagrams

The best data collection method will be determined by the problem being solved and the type of data required. To gain a complete understanding of the problem, it is critical to use multiple data collection methods.

Tools for Data Analysis and Visualization

Once the data has been collected, it must be analysed and visualised in order to gain insights into the problem. This process can be aided by the following tools:

• Excel Spreadsheets
• Flow diagrams
• Pareto diagrams
• Scatter Plots
• Control diagrams

These tools can assist in organising data and making it easier to understand. They can also be used to generate visual representations of data, such as graphs and charts, to communicate the findings to others.

Finally, the data collection and analysis step is an important part of the A3 Problem Solving process. Organizations can gain a better understanding of the problem and develop effective solutions by collecting and analysing relevant data.

Step 3: Identify Root Causes

Identifying the root causes of the problem is the third step in the A3 Problem Solving process. This step is critical because it assists organisations in understanding the root causes of a problem rather than just its symptoms. Once the underlying cause of the problem is identified, it can be addressed more effectively, leading to more long-term solutions.

Overview of the Root Cause Analysis Process

The process of determining the underlying causes of a problem is known as root cause analysis. This process can assist organisations in determining why a problem is occurring and what can be done to prevent it from recurring in the future. The goal of root cause analysis is to identify the underlying cause of a problem rather than just its symptoms, allowing it to be addressed more effectively.

To understand Root cause analysis in more detail check out RCA in our Lean Six Sigma Yellow Belt Course Root Cause Analysis section

Techniques for Identifying Root Causes

There are several techniques for determining the root causes of a problem, including:

• Brainstorming
• Ishikawa diagrams (also known as fishbone diagrams)
• Root Cause Tree Analysis

These methods can be used to investigate the issue in-depth and identify potential root causes. Organizations can gain a deeper understanding of the problem and identify the underlying causes that must be addressed by using these techniques.

Best Practices for Conducting Root Cause Analysis

It is critical to follow these best practices when conducting root cause analysis in A3 Problem Solving:

• Make certain that all stakeholders participate in the root cause analysis process.
• Concentrate on determining the root cause of the problem rather than just its symptoms.
• Take into account all potential root causes, not just the most obvious ones.
• To identify root causes, use a systematic approach, such as the 5 Whys or root cause tree analysis.

Organizations can ensure that root cause analysis is carried out effectively and that the root cause of the problem is identified by adhering to these best practises. This will aid in the development of appropriate solutions and the effective resolution of the problem.

Step 4: Develop Solutions

Developing solutions is the fourth step in the A3 Problem Solving process. This entails generating ideas and options for dealing with the problem, followed by selecting the best solution. The goal is to develop a solution that addresses the root cause of the problem and prevents it from recurring.

Solution Development in A3 Problem Solving

A3 solution development Problem solving is an iterative process in which options are generated and evaluated. The data gathered in the previous steps, as well as the insights and understanding gained from the root cause analysis, guide this process. The solution should be based on a thorough understanding of the problem and address the underlying cause.

Techniques for Developing Solutions

There are several techniques that can be used to develop solutions in A3 Problem Solving, including:

• Brainwriting
• Solution matrix
• Multi voting
• Force field analysis

These techniques can help to generate a range of options and to select the best solution.

Best Practice for Developing Solutions

It is critical to follow the following best practices when developing solutions in A3 Problem Solving:

• Participate in the solution development process with all stakeholders.
• Make certain that the solution addresses the underlying cause of the problem.
• Make certain that the solution is feasible and achievable.
• Consider the solution’s impact on the organisation and its stakeholders.

Organizations can ensure that the solutions they develop are effective and sustainable by adhering to these best practises. This will help to ensure that the problem is addressed effectively and that it does not reoccur.

Step 5: Implement Solutions

The final and most important step in the A3 Problem Solving methodology is solution implementation. This is the stage at which the identified and developed solutions are put into action to address the problem. This step’s goal is to ensure that the solutions are effective, efficient, and long-lasting.

The implementation Process

The implementation process entails putting the solutions developed in the previous step into action. This could include changes to processes, procedures, and systems, as well as employee training and education. To ensure that the solutions are effective, the implementation process should be well-planned and meticulously executed.

Techniques for Implementing Solutions

A3 Problem Solving solutions can be implemented using a variety of techniques, including:

• Piloting the solution on a small scale before broadening its application
• Participating in the implementation process with all relevant stakeholders
• ensuring that the solution is in line with the goals and objectives of the organisation
• Monitoring the solution to determine its effectiveness and make any necessary changes

Best Practice for Implementing Solutions

It is critical to follow these best practices when implementing solutions in A3 Problem Solving:

Make certain that all relevant stakeholders are involved and supportive of the solution. Have a clear implementation plan that outlines the steps, timeline, and resources required. Continuously monitor and evaluate the solution to determine its efficacy and make any necessary changes. Encourage all stakeholders to communicate and collaborate openly. Organizations can ensure that solutions are effectively implemented and problems are effectively addressed by adhering to these best practices. The ultimate goal is to find a long-term solution to the problem and improve the organization’s overall performance.

In conclusion, A3 Problem Solving is a comprehensive and structured methodology for problem-solving that can be applied in various industries and organisations. The A3 Problem Solving process’s five steps – Define the Problem, Gather Data, Identify Root Causes, Develop Solutions, and Implement Solutions – provide a road map for effectively addressing problems and making long-term improvements.

Organizations can improve their problem-solving skills and achieve better results by following the key principles, techniques, and best practices outlined in this guide. As a result, both the organisation and its stakeholders will benefit from increased efficiency, effectiveness, and satisfaction. So, whether you’re an experienced problem solver or just getting started, consider incorporating the A3 Problem Solving methodology into your work and start reaping the benefits right away.

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.

Lean Manufacturing vs Six Sigma: What Are They

5 Simple Steps to Sustain 5S in Your Organization for Long-Term Success

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…

McKinsey Problem Solving: Six steps to solve any problem and tell a persuasive story

The McKinsey problem solving process is a series of mindset shifts and structured approaches to thinking about and solving challenging problems. It is a useful approach for anyone working in the knowledge and information economy and needs to communicate ideas to other people.

Over the past several years of creating StrategyU, advising an undergraduates consulting group and running workshops for clients, I have found over and over again that the principles taught on this site and in this guide are a powerful way to improve the type of work and communication you do in a business setting.

When I first set out to teach these skills to the undergraduate consulting group at my alma mater, I was still working at BCG. I was spending my day building compelling presentations, yet was at a loss for how to teach these principles to the students I would talk with at night.

Through many rounds of iteration, I was able to land on a structured process and way of framing some of these principles such that people could immediately apply them to their work.

While the “official” McKinsey problem solving process is seven steps, I have outline my own spin on things – from experience at McKinsey and Boston Consulting Group. Here are six steps that will help you solve problems like a McKinsey Consultant:

Step #1: School is over, stop worrying about “what” to make and worry about the process, or the “how”

When I reflect back on my first role at McKinsey, I realize that my biggest challenge was unlearning everything I had learned over the previous 23 years. Throughout school you are asked to do specific things. For example, you are asked to write a 5 page paper on Benjamin Franklin — double spaced, 12 font and answering two or three specific questions.

In school, to be successful you follow these rules as close as you can. However, in consulting there are no rules on the “what.” Typically the problem you are asked to solve is ambiguous and complex — exactly why they hire you. In consulting, you are taught the rules around the “how” and have to then fill in the what.

The “how” can be taught and this entire site is founded on that belief. Here are some principles to get started:

Step #2: Thinking like a consultant requires a mindset shift

There are two pre-requisites to thinking like a consultant. Without these two traits you will struggle:

• A healthy obsession looking for a “better way” to do things
• Being open minded to shifting ideas and other approaches

In business school, I was sitting in one class when I noticed that all my classmates were doing the same thing — everyone was coming up with reasons why something should should not be done.

As I’ve spent more time working, I’ve realized this is a common phenomenon. The more you learn, the easier it becomes to come up with reasons to support the current state of affairs — likely driven by the status quo bias — an emotional state that favors not changing things. Even the best consultants will experience this emotion, but they are good at identifying it and pushing forward.

Key point : Creating an effective and persuasive consulting like presentation requires a comfort with uncertainty combined with a slightly delusional belief that you can figure anything out.

Step #3: Define the problem and make sure you are not solving a symptom

Before doing the work, time should be spent on defining the actual problem. Too often, people are solutions focused when they think about fixing something. Let’s say a company is struggling with profitability. Someone might define the problem as “we do not have enough growth.” This is jumping ahead to solutions — the goal may be to drive more growth, but this is not the actual issue. It is a symptom of a deeper problem.

Consider the following information:

• Costs have remained relatively constant and are actually below industry average so revenue must be the issue
• Revenue has been increasing, but at a slowing rate
• This company sells widgets and have had no slowdown on the number of units it has sold over the last five years
• However, the price per widget is actually below where it was five years ago
• There have been new entrants in the market in the last three years that have been backed by Venture Capital money and are aggressively pricing their products below costs

In a real-life project there will definitely be much more information and a team may take a full week coming up with a problem statement . Given the information above, we may come up with the following problem statement:

Problem Statement : The company is struggling to increase profitability due to decreasing prices driven by new entrants in the market. The company does not have a clear strategy to respond to the price pressure from competitors and lacks an overall product strategy to compete in this market.

Step 4: Dive in, make hypotheses and try to figure out how to “solve” the problem

Now the fun starts!

There are generally two approaches to thinking about information in a structured way and going back and forth between the two modes is what the consulting process is founded on.

First is top-down . This is what you should start with, especially for a newer “consultant.” This involves taking the problem statement and structuring an approach. This means developing multiple hypotheses — key questions you can either prove or disprove.

Given our problem statement, you may develop the following three hypotheses:

• Company X has room to improve its pricing strategy to increase profitability
• Company X can explore new market opportunities unlocked by new entrants
• Company X can explore new business models or operating models due to advances in technology

As you can see, these three statements identify different areas you can research and either prove or disprove. In a consulting team, you may have a “workstream leader” for each statement.

Once you establish the structure you you may shift to the second type of analysis: a bottom-up approach . This involves doing deep research around your problem statement, testing your hypotheses, running different analysis and continuing to ask more questions. As you do the analysis, you will begin to see different patterns that may unlock new questions, change your thinking or even confirm your existing hypotheses. You may need to tweak your hypotheses and structure as you learn new information.

A project vacillates many times between these two approaches. Here is a hypothetical timeline of a project:

Step 5: Make a slides like a consultant

The next step is taking the structure and research and turning it into a slide. When people see slides from McKinsey and BCG, they see something that is compelling and unique, but don’t really understand all the work that goes into those slides. Both companies have a healthy obsession (maybe not to some people!) with how things look, how things are structured and how they are presented.

They also don’t understand how much work is spent on telling a compelling “story.” The biggest mistake people make in the business world is mistaking showing a lot of information versus telling a compelling story. This is an easy mistake to make — especially if you are the one that did hours of analysis. It may seem important, but when it comes down to making a slide and a presentation, you end up deleting more information rather than adding. You really need to remember the following:

Data matters, but stories change hearts and minds

Here are four quick ways to improve your presentations:

Tip #1 — Format, format, format

Both McKinsey and BCG had style templates that were obsessively followed. Some key rules I like to follow:

• Make sure all text within your slide body is the same font size (harder than you would think)
• Do not go outside of the margins into the white space on the side
• All titles throughout the presentation should be 2 lines or less and stay the same font size
• Each slide should typically only make one strong point

Tip #2 — Titles are the takeaway

The title of the slide should be the key insight or takeaway and the slide area should prove the point. The below slide is an oversimplification of this:

Even in consulting, I found that people struggled with simplifying a message to one key theme per slide. If something is going to be presented live, the simpler the better. In reality, you are often giving someone presentations that they will read in depth and more information may make sense.

To go deeper, check out these 20 presentation and powerpoint tips .

Tip #3 — Have “MECE” Ideas for max persuasion

“MECE” means mutually exclusive, collectively exhaustive — meaning all points listed cover the entire range of ideas while also being unique and differentiated from each other.

An extreme example would be this:

• Slide title: There are seven continents
• Slide content: The seven continents are North America, South America, Europe, Africa Asia, Antarctica, Australia

The list of continents provides seven distinct points that when taken together are mutually exclusive and collectively exhaustive . The MECE principle is not perfect — it is more of an ideal to push your logic in the right direction. Use it to continually improve and refine your story.

Applying this to a profitability problem at the highest level would look like this:

Goal: Increase profitability

2nd level: We can increase revenue or decrease costs

3rd level: We can increase revenue by selling more or increasing prices

Each level is MECE. It is almost impossible to argue against any of this (unless you are willing to commit accounting fraud!).

Tip #4 — Leveraging the Pyramid Principle

The pyramid principle is an approach popularized by Barbara Minto and essential to the structured problem solving approach I learned at McKinsey. Learning this approach has changed the way I look at any presentation since.

Here is a rough outline of how you can think about the pyramid principle as a way to structure a presentation:

As you build a presentation, you may have three sections for each hypothesis. As you think about the overall story, the three hypothesis (and the supporting evidence) will build on each other as a “story” to answer the defined problem. There are two ways to think about doing this — using inductive or deductive reasoning:

If we go back to our profitability example from above, you would say that increasing profitability was the core issue we developed. Lets assume that through research we found that our three hypotheses were true. Given this, you may start to build a high level presentation around the following three points:

These three ideas not only are distinct but they also build on each other. Combined, they tell a story of what the company should do and how they should react. Each of these three “points” may be a separate section in the presentation followed by several pages of detailed analysis. There may also be a shorter executive summary version of 5–10 pages that gives the high level story without as much data and analysis.

Step 6: The only way to improve is to get feedback and continue to practice

Ultimately, this process is not something you will master overnight. I’ve been consulting, either working for a firm or on my own for more than 10 years and am still looking for ways to make better presentations, become more persuasive and get feedback on individual slides.

The process never ends.

The best way to improve fast is to be working on a great team . Look for people around you that do this well and ask them for feedback. The more feedback, the more iterations and more presentations you make, the better you will become. Good luck!

If you enjoyed this post, you’ll get a kick out of all the free lessons I’ve shared that go a bit deeper. Check them out here .

Do you have a toolkit for business problem solving? I created Think Like a Strategy Consultant as an online course to make the tools of strategy consultants accessible to driven professionals, executives, and consultants. This course teaches you how to synthesize information into compelling insights, structure your information in ways that help you solve problems, and develop presentations that resonate at the C-Level. Click here to learn more or if you are interested in getting started now, enroll in the self-paced version ($497) or hands-on coaching version ($997). Both versions include lifetime access and all future updates.

Share this:

• Click to share on Facebook (Opens in new window)
• Click to share on LinkedIn (Opens in new window)
• Click to share on Twitter (Opens in new window)
• Click to share on Pocket (Opens in new window)
• Click to share on WhatsApp (Opens in new window)

Get the Free Mini-Course

Learn to solve complex problems, write compellingly, and upgrade your thinking with our free mini-course.

Work With Us

Join 1,000+ professionals and students learning consulting skills and accelerating their careers

Limited Time Discount

• What's different about BSM?
• What vice presidents say about BSM
• Sample Clients
• Lean in Labs
• What We Find In Labs
• Key Lean Labs Concepts
• Lean in R&D
• Lean in Regulatory Affairs
• Lean Manufacturing
• Global Lean Programs
• Digital Visual Management
• Articles and Reports
• Case Studies
• Lean R&D
• Lean Programs
• Real Lean Blogs

Structured Problem Solving – The key to Lean?

We are all familiar with the “House of Lean”; with how the twin pillars of Just in Time (JIT) and Jidoka (built-in Quality) fundamentally drive profitability by increasing cashflow and reducing cost. That is why most Lean implementations focus on these two aspects.

Companies that have successfully implemented Lean understand that the “Stability” or foundation the House of Lean is built upon is Structured Problem Solving. The iterative improvement loop offered by Structured Problem Solving allows for the correct Lean tools to be used at the correct time and in the correct way.

Despite this, Structured Problem Solving is underutilized and laboratories are especially slow to embrace it.

So, what is Structured Problem Solving? Toyota defines the following 8-steps:

• Clarify the Problem
• Breakdown the Problem
• Set the Target
• Analyze the Root Cause
• Develop Countermeasures
• Implement Countermeasures
• Monitor Results and Process
• Standardize and Share Success

The irony is that most laboratories will be using a similar set of steps (or a sub-set) everyday as part of their deviation process. So why the resistance to applying Structured Problem Solving to their business processes?

I would argue that the underutilization of the 8-step process is analogous to why Lean implementations all too often fail. A focus and reliance on the tools with a lack of understanding of the core foundations that guide their use. The power and efficacy of 8-step problem solving lies not in the use of root cause analysis tools – the Ishikawa diagrams or the 5-whys – to develop and implement counter measures. Rather, it lies in the first three steps – to develop a shared, concise understanding of the problem and more importantly, alignment on what would be considered solving it.

Unfortunately, these first, critical steps are often rushed or neglected entirely. Whether due to the flawed assumption that everyone’s understanding of the problem is the same (it very rarely is), a lack of time or resources available to collect the necessary data, or an enthusiastic team who want to launch directly into the root cause analysis, the end result is often the same; ineffective, box ticking CAPAs that fail to address the underlying issue.

BSM’s methodology inherently supports good Structured Problem Solving. The visual management systems developed as part of our Lean Lab implementations allow the perfect framework to facilitate the 8-steps. The use of Short Interval Control and properly developed KPI’s ensure that first three steps are easy to complete as the data and targets are readily available, while also serving as triggers themselves. As such a complete Lean Lab solution will make it easy to identify when failures are occurring and will provide the information to support Structured Problem Solving. Also, as Lean Lab solutions are developed and owned by lab members the process can help embolden the lab to tackle and solve the problems they face.

Our consultants can provide further information on the above and discuss any aspect of Real Lean Transformation, simply set-up a call today.

A3 Problem Solving: Structured Approach to Solve Process Problems

Companies have various methods of solving problems. The effectiveness of a problem-solving approach influences the solutions achieved. A3 thinking is one way that businesses can come up with effective remedies for process challenges. 

Toyota developed A3 problem solving to facilitate collaboration, learning and personal growth amongst workers. The vehicle manufacturer is famous for its commitment to continuous improvement . Even with a large workforce, Toyota is always finding ways to boost performance. 

Through the A3 process, the manufacturer promoted in-depth problem-solving. Can the problem-solving template work for your enterprise, as well?

What is A3 Problem Solving

The A3 process is a structured problem solving and continuous-improvement lean methodology that reports issues then finds a way to solve them. It’s a structured approach that promotes continuous improvement . A3 refers to the paper size (European) the equivalent to the 11″x17″ (American), which is used to outline plans throughout the problem-solving process. 

A3 problem solving is similar to other problem-solving methodologies which all seem to be similar to Deming’s Plan-Do-Check-Act PDCA .

What is A3 thinking process?

A3 thinking is a team collaborative process and continuous improvement tool developed by Toyota

Toyota employs the A3 thinking process format in their Toyota lean manufacturing process in three areas: proposals, status and problem-solving. Taiichi Ōno from Toyota contributed to the popularity of the A3 template. Apparently, he preferred to have reported on a single page. As with other Lean systems, the A3 process focuses on visualisation. 

By outlining the problems that require solutions, it’s less complicated for employees to envision the results. Putting your process challenges on paper doesn’t guarantee that they will get fixed. However, the A3 planning principle makes a lot of difference.

A3 Problem Solving Process

How to Use an A3 Template. The A3 process requires you to understand the problem before devising solutions. The structured approach involves the following steps:

• Identify : Begin by identifying the challenges the background information. Different people can have varying views about the problem, and it’s crucial to learn this. The problem statement is developed at this stage.
• Summary : Next is a comprehensive summary of the current state. A proper understanding of the situation is necessary to find solutions.
• Goals : Come up with the goals or desired future statement. All stakeholders should agree on the objectives.
• Analysis : Conduct a root cause analysis to learn where the inefficiencies lie. The the 5 Whys and the Ishikawa Diagram ( Fishbone Diagram ) can help with this process.
• Solutions : Decide the countermeasures necessary to correct the situation. Short-term solutions might be necessary.
• Plan : Have a plan to implement the countermeasures. The plan should identify roles and a timeframe.
• Results : Check the outcomes to confirm if the executed solutions meet the objectives.
• Follow Up : The final stage should include follow-ups. Consider any actions that might improve the process and help maintain the positive results of the A3 exercise.

Benefits of A3 Problem Solving Process

With the correct implementation, businesses can get good value from the A3 structure. One is effective and quick problem-solving. The A3 process involves several steps that show you what to do at every point. Therefore, workers can approach problems through logical reasoning. Rather than jump straight to solutions, employees get to work through the stages.

The process boosts company growth. Businesses stagnate when they have to deal with the same issues over and over again due to poor problem-solving. An effective problem-solving method makes it easy to sustain good operating policies. The better a company can solve its challenges, the more it grows.

The objective thinking requires in the A3 process simplifies planning. Any great problem-solving approach involves a concrete blueprint. The stages of A3 thinking take the stress out of planning because you know what to do and when.

A3 thinking enhances collaboration across teams, thus promoting development. When employees have to use a structured tool repeatedly, it fosters knowledge sharing. The more people work together, the better they relate and learn to complement each other.

Companies can completely change how they see problems and deal with them through A3 thinking. However, implementing A3 problem solving is not enough. Organisations must know how to incorporate the tool into the existing Lean culture.

What is Six Sigma?

Six Sigma methodology is not a mysterious magic solution but a well-studied and tested set of tools and techniques that aim to solve problems of inefficiency within your business or projects. These techniques consist of spotting and removing all those faults cluttering your processes and stopping them from running as smoothly and effectively as possible.

Read More: Six Sigma Continuous Process Improvement

What is lean six sigma?

Lean six sigma is a combination of two methodologies,  lean  manufacturing and six sigma, designed to improve processes to drive businesses toward increased efficiency, productivity and improved customer satisfaction.

Read More:  Lean Six Sigma

Difference between six sigma, Lean and lean six sigma?

Six sigma, lean, and lean six sigma are all focused on improving processes to create more value for the customer.

Lean refers to removing waste in any process, while six sigma refers to optimizing a specific process. Lean focuses on reducing waste from a system, while six sigma’s goal is to improve quality.

Process Improvement Methodologies

Process Improvement Methodologies are a way to identify inefficient processes that can affect your business's performance. These methodologies can be incorporated into your business to help increase its productivity and profits!

Read More: Process Improvement Methodologies

Lean Methodology

With the lean methodology, you are stripping back the wasteful aspects of your business and either fine-tuning existing processes or replacing them entirely.

Read More: Lean Methodology: Optimising Business Processes

Toyota Lean Manufacturing Maximise Productivity

Toyota lean manufacturing production system has  13 core pillars  that guide them in their decisions and continuous improvement.

Workers are central to the whole process and treated as a precious resource for the business

Read More: Toyota Lean Manufacturing: Maximise Productivity and Efficiency

We care about the protection of your data. Read our Privacy Policy

• Public Speaking Training
• Effective Communication Training
• Storytelling with Data
• AI Pitch Deck Generator
• Venture Capital Investor Mindset
• Startup Funding
• Small Business Startup Financing
• Creating the Winning Pitch Deck
• Startup Funding for Entrepreneurs
• Go To Market Strategy
• Terms of Service

Introduction to Structured Problem Solving

Structured problem solving is an invaluable skill for managers, team leaders, and emerging leaders. It allows for systematic analysis and resolution of complex issues, resulting in more effective decision-making and optimized team performance.

In this article, we will delve into the core principles of structured problem solving, offering real-world examples and practical strategies. Our goal is to equip you with the tools necessary to enhance your managerial dynamics and leadership skills.

What is Structured Problem Solving?

Structured problem solving is a methodical approach to identifying, analyzing, and resolving problems. It involves breaking down a problem into smaller, manageable components and systematically addressing each part to find a solution.

This approach is widely used in various fields, including business, engineering, healthcare, and education, due to its effectiveness in dealing with complex and multifaceted issues.

Systematic Approach

A systematic approach to problem solving involves a step-by-step methodology that ensures all aspects of a problem are addressed. This process begins with a clear understanding of the problem, followed by thorough data collection, analysis, and the development of strategic solutions.

Cross-Disciplinary Applications

Structured problem solving transcends industries and is applicable in any scenario where complex issues arise. Whether it’s a logistical challenge in supply chain management or a critical health diagnosis, the principles of structured problem solving remain consistent and reliable.

Benefits Over Ad-Hoc Methods

Compared to ad-hoc or spontaneous problem solving, structured problem solving offers a more reliable and repeatable path to success. Ad-hoc methods may sometimes result in quick fixes, but they lack the thoroughness and sustainability of a structured approach.

The Importance of Structured Problem Solving

Enhances analytical and critical thinking.

Structured problem solving promotes analytical thinking by encouraging a systematic examination of issues. This fosters a deeper understanding of the problem and its underlying causes, leading to more effective and sustainable solutions.

Cultivating a Methodical Mindset

A methodical mindset is crucial for dissecting complex problems and uncovering the root causes. It involves adopting a disciplined approach to thinking, where one evaluates evidence, recognizes patterns, and deduces conclusions based on logic.

Overcoming Cognitive Biases

Structured problem solving helps in mitigating cognitive biases that can cloud judgment. By following a structured approach, decision-makers are more likely to consider all relevant information and avoid jumping to conclusions based on incomplete data or personal biases.

Long-Term Strategic Thinking

Encouraging long-term strategic thinking, structured problem solving ensures that solutions are not only effective in the short term but also sustainable in the long run. It promotes foresight and anticipation of future challenges, contributing to more resilient and adaptable strategies.

Promotes Data-Driven Decision Making

Structured problem solving often involves collecting and analyzing data to inform decisions. This data-driven approach ensures that decisions are based on objective evidence rather than assumptions or intuition, leading to more accurate and reliable outcomes.

Emphasis on Quantitative Analysis

Quantitative analysis plays a pivotal role in structured problem solving by providing measurable and empirical evidence to support decision making. This can include statistical analysis, key performance indicators, and other numerical data that offer insights into the problem.

Integration of Qualitative Insights

While data-driven decision making often focuses on quantitative data, qualitative insights are equally important. Structured problem solving integrates both quantitative and qualitative data, including stakeholder interviews, surveys, and observational studies, to provide a holistic view of the problem.

Reducing Uncertainty in Decision Making

By basing decisions on data, structured problem solving significantly reduces uncertainty. It provides a clear rationale for chosen solutions and establishes a foundation for predicting outcomes, thus minimizing the risks associated with decision making.

Improves Team Collaboration

By following a structured approach, team members can work together more effectively to identify, analyze, and resolve problems. This collaborative effort promotes a sense of shared responsibility and fosters a more cohesive and productive team environment.

Encouraging Diverse Perspectives

Structured problem solving encourages the inclusion of diverse perspectives, which can lead to more innovative and comprehensive solutions. By valuing the input of all team members, it leverages the collective expertise and creativity within the group.

Streamlining Communication

Clear and streamlined communication is a byproduct of structured problem solving. As team members follow a defined process, it becomes easier to share information, provide updates, and maintain transparency throughout the problem-solving journey.

Building Trust and Accountability

A structured approach to problem solving helps build trust and accountability among team members. As individuals understand their roles and the rationale behind decisions, they are more likely to take ownership of their tasks and work together towards common goals.

Steps in Structured Problem Solving

1. define the problem.

The first step in structured problem solving is to clearly define the problem. This involves identifying the issue, understanding its impact, and determining the desired outcome.

Clarifying the Situation

It’s critical to clarify the situation by asking questions that narrow down the specifics of the problem. Understanding the who, what, when, where, and why provides a comprehensive background to the issue at hand.

Establishing the Scope

Determining the scope of the problem helps to focus efforts on what is truly important. It involves setting boundaries to ensure that the problem-solving process remains manageable and relevant.

Identifying Stakeholders

Identifying the stakeholders affected by the problem and the potential solutions is essential. Stakeholders can provide valuable insights and may be key to implementing the solutions effectively.

2. Gather and Analyze Data

Once the problem is defined, the next step is to gather relevant data and analyze it to identify the root causes of the issue.

Data Collection Methods

Choosing the right data collection methods is crucial for effective analysis. Methods can include surveys, interviews, observation, or data mining, depending on the nature of the problem.

Tools for Data Analysis

Various tools can be used to analyze the collected data, including statistical software, spreadsheets, or specialized analysis software. These tools help to organize, visualize, and interpret data to uncover patterns and insights.

Interpreting Results

Interpreting the results of data analysis involves looking for trends, correlations, and anomalies that point towards the underlying causes of the problem. It’s a critical step that guides the development of potential solutions.

3. Generate Potential Solutions

Based on the data analysis, brainstorm potential solutions to address the root causes of the problem. Consider the feasibility, impact, and potential risks of each solution.

Brainstorming Sessions

Organizing brainstorming sessions with team members can yield a diverse set of potential solutions. Encouraging open and creative thinking during these sessions is key to uncovering innovative ideas.

Assessing Feasibility

After generating ideas, assess the feasibility of each solution in terms of resources, time, and constraints. This step helps to filter out impractical solutions and focus on those that can be realistically implemented.

Considering Risk and Impact

Evaluating the potential risks and impact of each solution is essential. This includes looking at the possible side effects and long-term consequences of each option to ensure sustainable success.

4. Evaluate and Select the Best Solution

Evaluate the proposed solutions and select the one that best addresses the root causes of the problem and aligns with the desired outcome.

Criteria for Selection

Develop criteria for selecting the best solution, which may include effectiveness, cost, time, and alignment with organizational goals. This ensures a balanced and objective decision-making process.

Decision-Making Techniques

Leveraging decision-making techniques such as cost-benefit analysis, decision matrices, or multi-voting can help in choosing the most appropriate solution. These techniques provide a structured way to compare options and make informed choices.

Gaining Consensus

It’s important to gain consensus among team members and stakeholders on the selected solution. This fosters buy-in and commitment to the implementation process.

5. Implement the Solution

Once the best solution is selected, develop an action plan and implement it. Ensure that all team members are aware of their roles and responsibilities in executing the plan.

Developing an Action Plan

An action plan outlines the steps needed to implement the solution, including timelines, resources required, and responsible parties. It serves as a roadmap for execution.

Communicating the Plan

Effective communication of the action plan to all involved parties is crucial for successful implementation. It ensures clarity, aligns expectations, and prepares everyone for their roles.

Providing Resources and Support

Ensure that adequate resources and support are available for team members. This may include training, budget allocation, or access to necessary tools and technology.

6. Monitor and Evaluate Results

After implementing the solution, monitor its progress and evaluate its effectiveness. Make any necessary adjustments to ensure the desired outcome is achieved.

Setting KPIs and Metrics

Setting key performance indicators (KPIs) and metrics helps to objectively measure the success of the solution. These should be aligned with the goals established in the problem definition phase.

Regular Review Meetings

Holding regular review meetings allows the team to discuss progress, address challenges, and make informed decisions about any adjustments needed.

Iterative Improvement

Structured problem solving is an iterative process. Evaluating results may lead to further refinements of the solution or additional problem-solving cycles if the desired outcomes are not met.

Real-World Examples of Structured Problem Solving

Case Study 1: Improving Customer Satisfaction

A retail company faced declining customer satisfaction scores. By following the structured problem-solving approach, the company identified that long wait times at checkout were the primary cause. They implemented a new checkout process and trained staff to improve efficiency, resulting in increased customer satisfaction.

Analyzing Customer Feedback

The retail company analyzed customer feedback to understand the reasons behind the dissatisfaction. This highlighted the issue of long wait times and provided a clear target for improvement.

Process Redesign

The company redesigned the checkout process to streamline operations. This included the introduction of self-service kiosks and additional staff during peak times.

Measuring Results

Post-implementation, the company measured customer satisfaction through surveys and found a marked improvement. This validated the effectiveness of the structured problem-solving approach.

Case Study 2: Reducing Manufacturing Defects

A manufacturing plant experienced a high rate of defects in their products. Through structured problem solving, they identified that poor quality control procedures were to blame. They implemented stricter quality control measures and provided additional training for staff, leading to a significant reduction in defects.

Root Cause Analysis

The manufacturing plant conducted a root cause analysis to identify why defects were occurring. This revealed gaps in quality control and areas for process improvement.

Implementing Quality Standards

The plant established new quality standards and implemented rigorous testing procedures. This ensured that products met the required specifications before leaving the factory.

Tracking Defect Rates

By tracking defect rates before and after the changes, the plant was able to quantify the improvement and demonstrate the success of their structured problem-solving efforts.

Case Study 3: Enhancing Employee Engagement

A tech company struggled with low employee engagement. By using structured problem solving, they discovered that a lack of career development opportunities was the main issue. They introduced new training programs and career development plans, resulting in higher employee engagement and retention.

Employee Surveys and Interviews

The tech company conducted surveys and interviews to gauge employee sentiments. This data revealed that employees desired more opportunities for professional growth.

Creating Professional Development Programs

In response, the company developed a range of professional development programs tailored to different career paths within the organization.

In conclusion, structured problem-solving approaches, such as leveraging decision-making techniques, gaining consensus, implementing solutions, developing action plans, communicating effectively, providing resources and support, monitoring and evaluating results, setting KPIs and metrics, holding regular review meetings, and embracing iterative improvement, are essential for addressing complex issues in various scenarios. Real-world examples demonstrate how organizations can successfully apply these methods to improve customer satisfaction, reduce manufacturing defects, and enhance employee engagement. By following a systematic problem-solving process, businesses can identify root causes, implement effective solutions, and measure outcomes to achieve their desired goals. Embracing structured problem-solving not only resolves current challenges but also fosters a culture of continuous improvement and innovation within an organization.

• Case Studies on Structured Problem Solving
• Steps to Implement Structured Problem Solving
• Tools and Techniques for Structured Problem Solving
• The Art of Problem Solving
• 5 Effective Strategies to Find Solutions

©  2024 Kelvin Michael. Built using WordPress and the Materialis Theme