{"meta":{"slug":"problem-solving-methods","area":"editoriale","tipologia":"Editoriale","data":"2026-10-14","autore":"Redazione Prodability","meta_title":"Problem solving methods: which to choose and where to start","meta_description":"PDCA, 8D, A3, 5 Whys, Ishikawa: a map of 50 problem solving methods and tools, what they have in common and the step that comes before any of them.","keyword_principale":"problem solving methods","keywords_secondarie":"problem solving techniques, types of problem solving methods, how to choose a problem solving method, problem solving tools","copertina":"segnaposto","title":"Problem solving methods: which one to choose and where to start","lunghezza":"10 min read","tags":[],"featuredVisual":null},"content":"# Problem solving methods: which one to choose and where to start\n\nA customer receives the wrong goods. You fix it with a rush shipment, apologize, promise to be more careful. The following month it happens again, with another customer and another product code. The problem had been solved, and yet it came back.\n\nAt that point many business owners reach the same conclusion: they need a problem solving method. They start looking and find all kinds of things: PDCA, DMAIC, 8D, A3, 5 Whys, Ishikawa diagram, Kaizen, Design Thinking. Each with its own steps, its own forms, its own courses.\n\nLining up the main ones, we counted 50, among methods, frameworks and tools, each with the texts it comes from. Faced with a list like that, the question comes naturally: which one should you choose?\n\nIn this article we try to answer. But let's start from a question that comes first: what does any method need in order to work?\n\n## Methods and tools are not the same thing\n\nThe first distinction is between methods and tools.\n\nSome items are complete methods: they guide the whole path, from the problem to the solution, all the way to checking the result. PDCA, DMAIC, 8D, Toyota Business Practices and Kepner-Tregoe are of this kind.\n\nOthers are tools, which you use inside a method to take one specific step. The 5 Whys and the Ishikawa diagram are for finding causes. Pareto analysis is for deciding where to start. FMEA is for predicting where a process might fail.\n\nThe A3 sits in between: it is a way of reasoning and at the same time a sheet that puts that reasoning on a single page.\n\nConfusing the two leads to a common mistake: adopting a tool while believing you have adopted a method. You draw an Ishikawa diagram at every meeting, but then nobody checks whether the solution worked.\n\n## A map of problem solving methods\n\nTo find your way around, it helps to group them by the question they answer.\n\n| The question | Methods and tools |\n| :--- | :--- |\n| How do I solve a problem that already exists? | PDCA, DMAIC, 8D, A3, Toyota Business Practices, QC Story, Kepner-Tregoe |\n| What is the real cause? | 5 Whys, Ishikawa diagram, Root Cause Analysis, Fault Tree Analysis, Is / Is Not analysis, Change Analysis, Barrier Analysis, Apollo, TapRooT, Shainin Red X |\n| Where do I start? | Pareto analysis, Theory of Constraints and its Thinking Processes |\n| How do I keep it from happening? | FMEA, Pre-mortem, Bow Tie Analysis |\n| How do I improve the process every day? | Lean Problem Solving, Kaizen, Kaizen Event, Six Sigma, statistical process control (SPC), 7 basic quality tools |\n| How do I find a new solution? | Design Thinking, Double Diamond, Creative Problem Solving, Osborn-Parnes model, TRIZ, Synectics, SCAMPER, Brainstorming, lateral thinking, Six Thinking Hats |\n| Which alternative do I choose? | Cynefin, OODA Loop, decision tree, cost-benefit analysis, multi-criteria analysis, weighted decision matrix, SWOT analysis, Gap Analysis |\n| What have we learned? | After Action Review, Lessons Learned, Post-mortem |\n\nLooking at how they work, though, almost all of them fall into 2 broad categories:\n\n- techniques that help solve problems in an intuitive, creative and innovative way, such as Design Thinking, TRIZ or brainstorming;\n- techniques that help analyze the causes of the problem, such as the 5 Whys, the Ishikawa diagram or 8D.\n\nThe first look for new paths. The second trace what is wrong back to its origin.\n\n## Why there are so many\n\nSo which one is the best? And why are there so many of them, instead of just one?\n\nIf one method always worked, on any problem and in anyone's hands, everyone would use it and the others would have disappeared. When dozens of different ways of doing the same thing coexist in a discipline, it usually means that none of them works always and for everyone. A universal problem solving method, in short, doesn't exist.\n\nThe same thing happens with diets: the one that works for one person won't necessarily work for another. In the same way, any problem solving method can turn out to be effective or ineffective depending on who applies it and on the problem it is applied to.\n\nEach one works best in a specific context. 8D was born in the automotive industry, at Ford, and is still widely used in factories. Barrier Analysis and TapRooT are used mainly in safety and incident analysis. Design Thinking and Double Diamond come from product and service design.\n\nFor most companies there is no need to know them all. What you need is to understand what they have in common.\n\n## What they have in common\n\nIf you put the complete methods side by side, you notice that the first step is almost always the same:\n\n- PDCA starts by defining the problem and planning;\n- DMAIC starts with Define;\n- the A3 opens the sheet with the problem and the current situation;\n- Toyota's 8-step process starts by clarifying the problem;\n- Kepner-Tregoe keeps problem analysis separate from the decision;\n- even a creative method like the Double Diamond devotes the first half of the path to exploring the problem and defining it.\n\nThey also share the goal. 8D aims to prevent the problem from coming back. Root Cause Analysis looks for the underlying causes instead of acting on the symptoms.\n\nFor all these methods, solving a problem means making sure it doesn't happen again. A patch doesn't solve it: it postpones it.\n\n## The 5 Whys and the fuse\n\nTaiichi Ohno, the engineer who built the Toyota Production System, explained the 5 Whys with an example that has become famous. A machine stops.\n\n- Why did it stop? Because there was an overload and the fuse blew.\n- Why was there an overload? Because the bearing was not lubricated enough.\n- Why was it not lubricated enough? Because the oil pump was not pumping enough.\n- Why was it not pumping enough? Because the pump shaft was worn.\n- Why was it worn? Because there was no filter, and metal chips were getting into the pump.\n\nStopping at the first answer, you replace the fuse, and the machine starts again. Stopping at the fourth, you replace the pump shaft. In both cases, Ohno wrote, the failure would have come back after a few months. Only the fifth why leads to a solution that closes the problem: fitting the filter.\n\nThis example is usually told to show the power of the question \"why?\". But there is a detail that goes unnoticed: the method starts from a stopped machine. That is, from a problem that someone saw, considered a problem and decided to analyze.\n\nA stopped machine is visible. Many problems in a company, on the other hand, make no noise: a quote redone twice, a customer who doesn't reorder, a team member who waits for instructions instead of reporting that something is wrong.\n\n## The step that comes before the method\n\nAll these methods take one thing for granted: that the problem is already there, in front of whoever has to solve it. Seen, written down, chosen as the most important.\n\nIn the reality of companies, this is precisely the step that is often missing. And it is missing in 3 ways.\n\n**1. The problem isn't seen.** Those who live with it every day consider it normal, or don't report it so as not to create tension. The business owner becomes the only one who sees problems, and sees only the ones that reach them.\n\n**2. The problem is seen, but written down badly.** \"People drive the forklift badly\" and \"There are no rules for using the forklift\" describe the same incident, but lead to different solutions. A method works on what it receives: if the definition is wrong, it finds, with great precision, the solution to the wrong problem.\n\n**3. The wrong problem is chosen.** You act on the most urgent or most annoying problem, not on the one that has the most consequences. Pareto analysis helps you choose, but it works on how often problems occur: if nobody writes them down, there is no frequency to count.\n\nWe look at these 3 mistakes in more depth in the article [Organizing business problems](https://blog.prodability.com/fare-ordine-nei-problemi-aziendali/).\n\nSeeing, writing down and ranking problems is a skill in its own right, one that comes before problem solving. We call it Problem Noting.\n\n**The best problem solving technique, then, is not a problem solving technique.**\n\nProblem Noting doesn't replace methods: it is what allows them to work. A company that writes down its problems methodically can use PDCA, 8D or a simple 5 Whys and get results. A company that doesn't can adopt the most sophisticated method and keep solving the same problems.\n\nIt doesn't depend on how good people are, but on how the company treats problems. When reporting them is everyone's habit, and not a task for the business owner alone, problems reach the method in time and written down in a useful way.\n\n## The only universal method\n\nIf no problem solving method is universal, is there a way of managing problems that is?\n\nYes: the one that rests on natural principles. In fact, there are 2 universal methods for managing problems, and every element of nature has been using them for billions of years, including the cells of our own bodies.\n\nAmong the disciplines used in companies, the one that comes closest to this method is called Problem Management, and it is best known in IT.\n\nProblem Management keeps apart two things that many companies confuse: the incident and the problem. The incident is the customer who receives the wrong goods: it has to be fixed right away, with a rush shipment and an apology. The problem is the cause that makes the incident happen again the following month, with another customer and another product code.\n\nThat is why, before looking for a solution, Problem Management asks you to identify problems, including those hidden behind recurring incidents, to record and describe them, and to rank them by the risk they carry. Seeing, writing down and ranking: the same steps as Problem Noting.\n\n## How to choose the right method\n\nOnce this step is taken, choosing the method becomes simpler, because it depends on the type of problem in front of you:\n\n- a problem that keeps coming back: a method for causes, from the 5 Whys up to 8D if the problem is serious or involves several departments;\n- many problems at once and little time: Pareto analysis, to decide where to start;\n- a decision between several alternatives: Kepner-Tregoe or a weighted decision matrix;\n- a risk that hasn't materialized yet: FMEA or a pre-mortem;\n- a project that has just ended: the After Action Review, to understand what to repeat and what to change;\n- a new problem, with no known solutions: Design Thinking or Creative Problem Solving.\n\nTo get started, a simple cycle like PDCA is enough, along with the question \"why?\" repeated until you reach a cause you can act on.\n\n## Conclusion\n\nTo sum up:\n\n- There are dozens of problem solving methods: we counted 50, in different families depending on the question they answer.\n- Methods and tools are not the same thing: an Ishikawa diagram is not a method, it is a step inside a method.\n- Almost all of them fall into 2 broad categories: creative techniques, which look for new solutions, and those that analyze causes.\n- There is no universal problem solving method: as with diets, each one works or not depending on who applies it and on the problem.\n- The complete methods all start from defining the problem and aim at the same result: that the problem doesn't come back.\n- No method works on a problem that nobody has seen, that is written down badly or that isn't the most important one.\n- Before problem solving comes Problem Noting: the habit of seeing, writing down and ranking problems, the same habit Problem Management is built on.\n\n## References\n\n- Deming, W. E. (1986). *Out of the Crisis*. MIT Center for Advanced Engineering Study.\n- Ohno, T. (1988). *Toyota Production System: Beyond Large-Scale Production*. Productivity Press.\n- Ford Motor Company (1987). *Team Oriented Problem Solving (TOPS)*. Ford Motor Company.\n- Pande, P. S., Neuman, R. P., & Cavanagh, R. R. (2000). *The Six Sigma Way*. McGraw-Hill.\n- Sobek II, D. K., & Smalley, A. (2008). *Understanding A3 Thinking*. Productivity Press.\n- Liker, J. K., & Meier, D. (2006). *The Toyota Way Fieldbook*. McGraw-Hill.\n- Kepner, C. H., & Tregoe, B. B. (1981). *The New Rational Manager*. Princeton Research Press.\n- Ishikawa, K. (1985). *What Is Total Quality Control? The Japanese Way*. Prentice-Hall.\n- Juran, J. M., & Godfrey, A. B. (Eds.). (1999). *Juran's Quality Handbook* (5th ed.). McGraw-Hill.\n- U.S. Department of Energy (1992). *Root Cause Analysis Guidance Document*. DOE-NE-STD-1004-92.\n- Klein, G. (2007). Performing a Project Premortem. *Harvard Business Review*, 85(9), 18-19.\n- Design Council (2019). *Framework for Innovation: Design Council's Evolved Double Diamond*.\n- AXELOS (2019). *ITIL Foundation: ITIL 4 Edition*. TSO.","path":"content/articles/art-0185/en.md","routePath":"problem-solving-methods","wordCount":2194,"imageMeta":{},"html":"<p>A customer receives the wrong goods. You fix it with a rush shipment, apologize, promise to be more careful. The following month it happens again, with another customer and another product code. The problem had been solved, and yet it came back.</p>\n<p>At that point many business owners reach the same conclusion: they need a problem solving method. They start looking and find all kinds of things: PDCA, DMAIC, 8D, A3, 5 Whys, Ishikawa diagram, Kaizen, Design Thinking. Each with its own steps, its own forms, its own courses.</p>\n<p>Lining up the main ones, we counted 50, among methods, frameworks and tools, each with the texts it comes from. Faced with a list like that, the question comes naturally: which one should you choose?</p>\n<p>In this article we try to answer. But let's start from a question that comes first: what does any method need in order to work?</p>\n<h2 id=\"methods-and-tools-are-not-the-same-thing\" class=\"article-h2-retrowave\"><span>Methods and tools are not the same thing</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"methods-and-tools-are-not-the-same-thing\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>The first distinction is between methods and tools.</p>\n<p>Some items are complete methods: they guide the whole path, from the problem to the solution, all the way to checking the result. PDCA, DMAIC, 8D, Toyota Business Practices and Kepner-Tregoe are of this kind.</p>\n<p>Others are tools, which you use inside a method to take one specific step. The 5 Whys and the Ishikawa diagram are for finding causes. Pareto analysis is for deciding where to start. FMEA is for predicting where a process might fail.</p>\n<p>The A3 sits in between: it is a way of reasoning and at the same time a sheet that puts that reasoning on a single page.</p>\n<p>Confusing the two leads to a common mistake: adopting a tool while believing you have adopted a method. You draw an Ishikawa diagram at every meeting, but then nobody checks whether the solution worked.</p>\n<h2 id=\"a-map-of-problem-solving-methods\" class=\"article-h2-retrowave\"><span>A map of problem solving methods</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"a-map-of-problem-solving-methods\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>To find your way around, it helps to group them by the question they answer.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<div class=\"article-table-scroll is-fit\" style=\"--table-min:286px\"><table><colgroup><col style=\"width:50.000%\"><col style=\"width:50.000%\"></colgroup><thead><tr><th align=\"left\">The question</th><th align=\"left\">Methods and tools</th></tr></thead><tbody><tr><td align=\"left\">How do I solve a problem that already exists?</td><td align=\"left\">PDCA, DMAIC, 8D, A3, Toyota Business Practices, QC Story, Kepner-Tregoe</td></tr><tr><td align=\"left\">What is the real cause?</td><td align=\"left\">5 Whys, Ishikawa diagram, Root Cause Analysis, Fault Tree Analysis, Is / Is Not analysis, Change Analysis, Barrier Analysis, Apollo, TapRooT, Shainin Red X</td></tr><tr><td align=\"left\">Where do I start?</td><td align=\"left\">Pareto analysis, Theory of Constraints and its Thinking Processes</td></tr><tr><td align=\"left\">How do I keep it from happening?</td><td align=\"left\">FMEA, Pre-mortem, Bow Tie Analysis</td></tr><tr><td align=\"left\">How do I improve the process every day?</td><td align=\"left\">Lean Problem Solving, Kaizen, Kaizen Event, Six Sigma, statistical process control (SPC), 7 basic quality tools</td></tr><tr><td align=\"left\">How do I find a new solution?</td><td align=\"left\">Design Thinking, Double Diamond, Creative Problem Solving, Osborn-Parnes model, TRIZ, Synectics, SCAMPER, Brainstorming, lateral thinking, Six Thinking Hats</td></tr><tr><td align=\"left\">Which alternative do I choose?</td><td align=\"left\">Cynefin, OODA Loop, decision tree, cost-benefit analysis, multi-criteria analysis, weighted decision matrix, SWOT analysis, Gap Analysis</td></tr><tr><td align=\"left\">What have we learned?</td><td align=\"left\">After Action Review, Lessons Learned, Post-mortem</td></tr></tbody></table></div>\n<p>Looking at how they work, though, almost all of them fall into 2 broad categories:</p>\n<ul class=\"article-check-list\">\n<li>techniques that help solve problems in an intuitive, creative and innovative way, such as Design Thinking, TRIZ or brainstorming;</li>\n<li>techniques that help analyze the causes of the problem, such as the 5 Whys, the Ishikawa diagram or 8D.</li>\n</ul>\n<p>The first look for new paths. The second trace what is wrong back to its origin.</p>\n<h2 id=\"why-there-are-so-many\" class=\"article-h2-retrowave\"><span>Why there are so many</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"why-there-are-so-many\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>So which one is the best? And why are there so many of them, instead of just one?</p>\n<p>If one method always worked, on any problem and in anyone's hands, everyone would use it and the others would have disappeared. When dozens of different ways of doing the same thing coexist in a discipline, it usually means that none of them works always and for everyone. A universal problem solving method, in short, doesn't exist.</p>\n<p>The same thing happens with diets: the one that works for one person won't necessarily work for another. In the same way, any problem solving method can turn out to be effective or ineffective depending on who applies it and on the problem it is applied to.</p>\n<p>Each one works best in a specific context. 8D was born in the automotive industry, at Ford, and is still widely used in factories. Barrier Analysis and TapRooT are used mainly in safety and incident analysis. Design Thinking and Double Diamond come from product and service design.</p>\n<p>For most companies there is no need to know them all. What you need is to understand what they have in common.</p>\n<h2 id=\"what-they-have-in-common\" class=\"article-h2-retrowave\"><span>What they have in common</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"what-they-have-in-common\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>If you put the complete methods side by side, you notice that the first step is almost always the same:</p>\n<ul class=\"article-check-list\">\n<li>PDCA starts by defining the problem and planning;</li>\n<li>DMAIC starts with Define;</li>\n<li>the A3 opens the sheet with the problem and the current situation;</li>\n<li>Toyota's 8-step process starts by clarifying the problem;</li>\n<li>Kepner-Tregoe keeps problem analysis separate from the decision;</li>\n<li>even a creative method like the Double Diamond devotes the first half of the path to exploring the problem and defining it.</li>\n</ul>\n<p>They also share the goal. 8D aims to prevent the problem from coming back. Root Cause Analysis looks for the underlying causes instead of acting on the symptoms.</p>\n<p>For all these methods, solving a problem means making sure it doesn't happen again. A patch doesn't solve it: it postpones it.</p>\n<h2 id=\"the-5-whys-and-the-fuse\" class=\"article-h2-retrowave\"><span>The 5 Whys and the fuse</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"the-5-whys-and-the-fuse\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>Taiichi Ohno, the engineer who built the Toyota Production System, explained the 5 Whys with an example that has become famous. A machine stops.</p>\n<ul class=\"article-check-list\">\n<li>Why did it stop? Because there was an overload and the fuse blew.</li>\n<li>Why was there an overload? Because the bearing was not lubricated enough.</li>\n<li>Why was it not lubricated enough? Because the oil pump was not pumping enough.</li>\n<li>Why was it not pumping enough? Because the pump shaft was worn.</li>\n<li>Why was it worn? Because there was no filter, and metal chips were getting into the pump.</li>\n</ul>\n<p>Stopping at the first answer, you replace the fuse, and the machine starts again. Stopping at the fourth, you replace the pump shaft. In both cases, Ohno wrote, the failure would have come back after a few months. Only the fifth why leads to a solution that closes the problem: fitting the filter.</p>\n<p>This example is usually told to show the power of the question \"why?\". But there is a detail that goes unnoticed: the method starts from a stopped machine. That is, from a problem that someone saw, considered a problem and decided to analyze.</p>\n<p>A stopped machine is visible. Many problems in a company, on the other hand, make no noise: a quote redone twice, a customer who doesn't reorder, a team member who waits for instructions instead of reporting that something is wrong.</p>\n<h2 id=\"the-step-that-comes-before-the-method\" class=\"article-h2-retrowave\"><span>The step that comes before the method</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"the-step-that-comes-before-the-method\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>All these methods take one thing for granted: that the problem is already there, in front of whoever has to solve it. Seen, written down, chosen as the most important.</p>\n<p>In the reality of companies, this is precisely the step that is often missing. And it is missing in 3 ways.</p>\n<p><strong>1. The problem isn't seen.</strong> Those who live with it every day consider it normal, or don't report it so as not to create tension. The business owner becomes the only one who sees problems, and sees only the ones that reach them.</p>\n<p><strong>2. The problem is seen, but written down badly.</strong> \"People drive the forklift badly\" and \"There are no rules for using the forklift\" describe the same incident, but lead to different solutions. A method works on what it receives: if the definition is wrong, it finds, with great precision, the solution to the wrong problem.</p>\n<p><strong>3. The wrong problem is chosen.</strong> You act on the most urgent or most annoying problem, not on the one that has the most consequences. Pareto analysis helps you choose, but it works on how often problems occur: if nobody writes them down, there is no frequency to count.</p>\n<p>We look at these 3 mistakes in more depth in the article <a href=\"https://blog.prodability.com/en/organize-business-problems/\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"article-inline-link\">Organizing business problems</a>.</p>\n<p>Seeing, writing down and ranking problems is a skill in its own right, one that comes before problem solving. We call it Problem Noting.</p>\n<p><strong>The best problem solving technique, then, is not a problem solving technique.</strong></p>\n<p>Problem Noting doesn't replace methods: it is what allows them to work. A company that writes down its problems methodically can use PDCA, 8D or a simple 5 Whys and get results. A company that doesn't can adopt the most sophisticated method and keep solving the same problems.</p>\n<p>It doesn't depend on how good people are, but on how the company treats problems. When reporting them is everyone's habit, and not a task for the business owner alone, problems reach the method in time and written down in a useful way.</p>\n<h2 id=\"the-only-universal-method\" class=\"article-h2-retrowave\"><span>The only universal method</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"the-only-universal-method\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>If no problem solving method is universal, is there a way of managing problems that is?</p>\n<p>Yes: the one that rests on natural principles. In fact, there are 2 universal methods for managing problems, and every element of nature has been using them for billions of years, including the cells of our own bodies.</p>\n<p>Among the disciplines used in companies, the one that comes closest to this method is called Problem Management, and it is best known in IT.</p>\n<p>Problem Management keeps apart two things that many companies confuse: the incident and the problem. The incident is the customer who receives the wrong goods: it has to be fixed right away, with a rush shipment and an apology. The problem is the cause that makes the incident happen again the following month, with another customer and another product code.</p>\n<p>That is why, before looking for a solution, Problem Management asks you to identify problems, including those hidden behind recurring incidents, to record and describe them, and to rank them by the risk they carry. Seeing, writing down and ranking: the same steps as Problem Noting.</p>\n<h2 id=\"how-to-choose-the-right-method\" class=\"article-h2-retrowave\"><span>How to choose the right method</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"how-to-choose-the-right-method\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>Once this step is taken, choosing the method becomes simpler, because it depends on the type of problem in front of you:</p>\n<ul class=\"article-check-list\">\n<li>a problem that keeps coming back: a method for causes, from the 5 Whys up to 8D if the problem is serious or involves several departments;</li>\n<li>many problems at once and little time: Pareto analysis, to decide where to start;</li>\n<li>a decision between several alternatives: Kepner-Tregoe or a weighted decision matrix;</li>\n<li>a risk that hasn't materialized yet: FMEA or a pre-mortem;</li>\n<li>a project that has just ended: the After Action Review, to understand what to repeat and what to change;</li>\n<li>a new problem, with no known solutions: Design Thinking or Creative Problem Solving.</li>\n</ul>\n<p>To get started, a simple cycle like PDCA is enough, along with the question \"why?\" repeated until you reach a cause you can act on.</p>\n<h2 id=\"conclusion\" class=\"article-h2-retrowave\"><span>Conclusion</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"conclusion\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>To sum up:</p>\n<ul class=\"article-check-list\">\n<li>There are dozens of problem solving methods: we counted 50, in different families depending on the question they answer.</li>\n<li>Methods and tools are not the same thing: an Ishikawa diagram is not a method, it is a step inside a method.</li>\n<li>Almost all of them fall into 2 broad categories: creative techniques, which look for new solutions, and those that analyze causes.</li>\n<li>There is no universal problem solving method: as with diets, each one works or not depending on who applies it and on the problem.</li>\n<li>The complete methods all start from defining the problem and aim at the same result: that the problem doesn't come back.</li>\n<li>No method works on a problem that nobody has seen, that is written down badly or that isn't the most important one.</li>\n<li>Before problem solving comes Problem Noting: the habit of seeing, writing down and ranking problems, the same habit Problem Management is built on.</li>\n</ul>\n<h2 id=\"references\" class=\"article-h2-retrowave\"><span>References</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"references\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<ul class=\"article-check-list\">\n<li>Deming, W. E. (1986). <em>Out of the Crisis</em>. MIT Center for Advanced Engineering Study.</li>\n<li>Ohno, T. (1988). <em>Toyota Production System: Beyond Large-Scale Production</em>. Productivity Press.</li>\n<li>Ford Motor Company (1987). <em>Team Oriented Problem Solving (TOPS)</em>. Ford Motor Company.</li>\n<li>Pande, P. S., Neuman, R. P., &amp; Cavanagh, R. R. (2000). <em>The Six Sigma Way</em>. McGraw-Hill.</li>\n<li>Sobek II, D. K., &amp; Smalley, A. (2008). <em>Understanding A3 Thinking</em>. Productivity Press.</li>\n<li>Liker, J. K., &amp; Meier, D. (2006). <em>The Toyota Way Fieldbook</em>. McGraw-Hill.</li>\n<li>Kepner, C. H., &amp; Tregoe, B. B. (1981). <em>The New Rational Manager</em>. Princeton Research Press.</li>\n<li>Ishikawa, K. (1985). <em>What Is Total Quality Control? The Japanese Way</em>. Prentice-Hall.</li>\n<li>Juran, J. M., &amp; Godfrey, A. B. (Eds.). (1999). <em>Juran's Quality Handbook</em> (5th ed.). McGraw-Hill.</li>\n<li>U.S. Department of Energy (1992). <em>Root Cause Analysis Guidance Document</em>. DOE-NE-STD-1004-92.</li>\n<li>Klein, G. (2007). Performing a Project Premortem. <em>Harvard Business Review</em>, 85(9), 18-19.</li>\n<li>Design Council (2019). <em>Framework for Innovation: Design Council's Evolved Double Diamond</em>.</li>\n<li>AXELOS (2019). <em>ITIL Foundation: ITIL 4 Edition</em>. TSO.</li>\n</ul>","headings":[{"level":2,"text":"Methods and tools are not the same thing","id":"methods-and-tools-are-not-the-same-thing"},{"level":2,"text":"A map of problem solving methods","id":"a-map-of-problem-solving-methods"},{"level":2,"text":"Why there are so many","id":"why-there-are-so-many"},{"level":2,"text":"What they have in common","id":"what-they-have-in-common"},{"level":2,"text":"The 5 Whys and the fuse","id":"the-5-whys-and-the-fuse"},{"level":2,"text":"The step that comes before the method","id":"the-step-that-comes-before-the-method"},{"level":2,"text":"The only universal method","id":"the-only-universal-method"},{"level":2,"text":"How to choose the right method","id":"how-to-choose-the-right-method"},{"level":2,"text":"Conclusion","id":"conclusion"},{"level":2,"text":"References","id":"references"}],"tldr":"","tldrItems":null}