what is a systematic approach to problem solving

• I Want to Learn Project Management
• Core Project Management Courses
• I Want to Study Agile Project Management
• Agile Project Management Courses
• Project Management Software
• I Need my Team to be Better at Project Management & Delivery
• I Want to Study for Project Management Professional (PMP)
• The Project Manager’s PMP Study Guide
• PMI Qualifications and PDUs
• I Want to Study for PRINCE2
• PRINCE2 Qualifications
• Agile Qualifications (Scrum and more)
• Institute of Project Management Courses
• ITIL Qualifications
• Project Management Knowledge Areas
• Leadership and Management Skills
• Professional Personal Effectiveness
• Artificial Intelligence
• Our Latest Project Management Articles
• Themed Directory of PM Articles
• All Our PM Articles: List
• Our Top ‘Must-Read’ Project Management Guides
• Project Management Briefings
• Project Management Podcasts
• All our Project Management Tools & Resources
• Free Online Project Management Resources
• Project Management Productivity Bundle
• Project Management Template Kit
• Project Management Checklists
• Project Management Bookshop
• Project Management Domains
• OnlinePMCourses Kindle-exclusive Project Management eBooks Series
• What is Your Project Management Personality?
• The OnlinePMCourses Newsletter
• About OnlinePMCourses
• Contact OnlinePMCourses
• Frequently Asked Questions
• How it Works
• Volume Licensing of Project Management Courses for Businesses
• Become an OnlinePMCourses Affiliate
• Writing for OnlinePMCourses
• How to Build OnlinePMCourses
• OnlinePMCourses Email Whitelisting Instructions
• OnlinePMCourses Privacy Policy
• Free Academy of PM

3 December, 2018

2   comments

Problem-Solving: A Systematic Approach

By   Mike Clayton

One of the joys of Project Management is the constant need for problem-solving.

The novelty and uncertainty of a project environment constantly throw up surprises. So, a Project Manager needs to be adept at solving problems.

In this article, we look at problem-solving and offer you a structured, systematic approach.

Problem-Solving Methodologies

There are a lot of established approaches to structured problem-solving. And there is a good chance that, if you work in a large organization, one of them is in common use. Indeed, some organizations mandate a particular problem-solving methodology.

For example, in automobile manufacturing industries, the 8 Disciplines or 8-D methodology is used widely. And anywhere that Six Sigma is an important part of the toolset, you will probably find the DMAIC method of problem-solving.

Others I like include Simplex and the catchily-named TOSIDPAR. And there are still others that, whilst highly effective, are also assertively protected by copyright, making them hard to discuss in an article like this. I’m thinking of you, Synectics.

Strengths and Weaknesses

All of these methodologies offer great features. And curiously, while each one feels complete, none offers every step you might want. The reason is simple. Each approach is tailored to focus on a part of the problem-solving process. Other parts are either outside their remit or receive less emphasis.

Comparison of Approaches

The consequence is that every structured approach can miss out steps that are important in some contexts. To illustrate, let’s compare the four methodologies I have mentioned.

Resolving the Gaps

At OnlinePMCourses, we use an 8-step problem-solving approach that covers just about all of the steps that these four methodologies offer. But, before we address these, let’s take a look at some practical approaches to applying problem-solving.

Practical Implementation

Some of the best examples of project problem-solving are in two of my favorite movies:

• Apollo 13 ‘Let’s work the problem’ (Gene Kranz played by Ed Harris)
• The Martian ‘In the face of overwhelming odds, I’m left with only one option, I’m gonna have to science the shit out of this.’ (Mark Watney played by Matt Damon)

In the Apollo 13 movie, there’s a scene where one engineer dumps a big pile of stuff onto a table in front of a bunch of his colleagues.

‘The people upstairs handed us this one and we’ve gotta come through. We’ve gotta’ find a way for this {holds up square thing] fit into the hole for this [a round thing] using nothing but that [a pile of random-looking stuff]. Let’s get it organized.’

They all dive in and we hear a hubbub.

Hubbub is about as reasonable a translation of the Japanese onomatopoeic word Waigaya as I can find. The idea behind Honda’s Waigaya approach is that everyone on the team gets to contribute to the conversation. But it isn’t a simple free-for-all. There are rules:

• Everybody is equal and needs to be able to say what they think.
• The team must listen to all ideas, and discuss them until they can either prove them to be valid or reject them.
• Once someone shares an idea, they don’t own it – it belongs to the team, who can do with the idea what it wants.
• At the end of waigaya, the team has a set of decisions and responsibilities for what to do, by whom, and by when.

There is a fabulous article that is well worth reading, at the Strategy & Business site .

In The Martian, the character Mark Watney is stuck with his problem. This makes it immediate, and also easy to see the context clearly. Another idea from Japanese manufacturing harnesses the value of getting out from behind your desk and going to where the problem is. It’s called ‘ going to the gemba’ – literally, ‘going to the place’ .

There is magic, when we get up, move about, and gather where the problem is happening. Going to the gemba and convening a waigaya is a great way to kick-off even the most complex problem-solving. Unless, that is, the gemba is halfway to the moon, or on Mars.

Recommended 8-Step Problem Solving Method

To reconcile the different methodologies for solving problems on projects, I have developed my own approach. It was tempting just to take the 17 steps in the chart above. But I also found that those four still miss some steps I find important to remember.

Would anyone think a 20-step Problem-solving Process Makes Sense?

I doubt it.

So, I decided to wrap some of the steps into 8 main steps. This gives us an 8-step method, which has everything that I have found you will need for problem-solving in a project context.

In the figure below, you can see those 8 steps as the bold boxes, with the subsidiary elements that form parts of those 8 major steps in fainter type.

So, in the rest of this article, I’ll summarize what I mean by each of these steps.

1. Define the Problem

Defining your problem is vital and takes up four of the 9 steps in the 8 Disciplines approach. But, on a project, this is often clearer than a new problem arising out of the blue in a manufacturing context, where 8D is most popular. So, I have folded the four parts into one step.

Understand the Context

Here’s where you need to find out how the problem impacts the whole of your project, and the circumstances in which it has arisen.

Gather Your Team

On a small project, this is likely to be all or most of your project team. For larger projects, this will center around the team delivering the workstream that the problem affects. For systemic problems, you’ll be asking work-stream leaders to supply expert team members to create a cross-cutting team. We sometimes call these ‘Tiger Teams’ – for reasons I can’t tell you, I’m afraid!

To support you in this stage, you may want to take a look at these articles:

• What You Need to Know about Building a Great Project Team
• Effective Teamwork: Do You Know How to Create it?
• Boost Your Project Team Performance with these Hacks
• How I Create Exceptional Project Collaboration
• How to Make Your Next Kick-off Meeting a Huge Success

Define the Problem

It’s often reasonably easy to define your problem in terms of ‘what’s wrong’. But it pays to be a specific as possible. And one thing that will help you with the next main step (setting an objective) is to define it in terms of what you want.

I like the discipline of defining your problem as:

How to…

Safety First

When I first encountered the 8 Disciplines method, the step that blew me away was D3 – Contain the Problem. I’d not thought of that before!

But it’s clear that, in many environments, like manufacturing, engineering, and transportation, solving the problem is not your first priority. You must first ensure that you do everything possible to limit further damage and risk to life and reputation. This may be the case on your project.

2. Set An Objective for Resolving the Problem

With everything safe and the problem not getting worse, you can move forward. This step is about defining what success looks like.

And, taking a leaf out of the TOSIDPAR approach, what standards, criteria, and measurable outcomes will you use to make your objective s precise as possible?

3. Establish the Facts of the Problem

I suppose the first step in solving a problem is getting an understanding of the issues, and gathering facts. This is the research and analysis stage.

And I like the DMAIC method’s approach of separating this into two distinct parts:

• Fact-finding.  This is where we make measurements in DMAIC, and gather information more generally. Be careful with perceptions and subjective accounts. It may be a fact that this is what I think I saw, but it may not be what actually happened.
• Analysis Once you have your evidence, you can start to figure out what it tells you. This can be a straightforward discussion, or may rely on sophisticated analytical methods, depending on circumstances. One analytical approach, which the 8D method favors, is root cause analysis. There are a number of ways to carry this out.

4. Find Options for Resolving the Problem

I see this step as the heart of problem-solving. So, it always surprises me how thin some methodologies are, here. I split it into four considerations.

Identify Your Options

The creative part of the problem-solving process is coming up with options that will either solve the problem or address it in part. The general rules are simple:

Rule 1: The more options you have, the greater chance of success. Rule 2: The more diverse your team, the more and better will be the options they find.

So, create an informal environment, brief your team, and use your favorite idea generation methods to create the longest list of ideas you can find. Then, look for some more!

Identify your Decision Criteria

A good decision requires good input – in this case, good ideas to choose from. It also needs a strong process and the right people. The first step in creating a strong process is to refer back to your objectives for resolving the problem and define the criteria against which you will evaluate your options and make your decision.

Determine your Decision-makers

You also need to determine who is well-placed to make the decision. This will be by virtue of their authority to commit the project and their expertise in assessing the relevant considerations. In most cases, this will be you – maybe with the support of one or more work-stream leaders. For substantial issues that have major financial, schedule, reputational, or strategic implications, this may be your Project Sponsor or Project Board.

Evaluate your Options

There are a number of ways to evaluate your problem resolution options that range from highly structured and objective to simple subjective approaches. Whichever you select, be sure that you apply the criteria you chose earlier, and present the outcomes of your evaluation honestly.

It is good practice to offer a measure of the confidence decision-makers can have in the evaluation, and a scenario assessment, based on each option.

5. Make a Decision on How to Resolve the Problem

We have done two major articles like this one about decision-making. For more on this topic, take a look at:

• The Essential Guide to Robust Project Decision-Making
• Rapid Decision Making in Projects: How to Get it Right

There are two parts to this step, that are equally important.

• The first is to make the decision.
• The second is to document that decision

Documenting your Decision

Good governance demands that you document your decision. But how documentation to provide is a matter of judgment. Doubtless, it will correlate to the scale and implications of that decision.

Things to consider include:

• What were the options?
• Who were the decision-makers?
• What was the evidence they considered?
• How did they make their decision (process)?
• What decision did they make?
• What were the reasons for their choice?

6. Make a Plan for Resolving the Problem

Well, of course, now you need to put together a plan for how you are going to implement your resolution. Unless, of course, the fix is simple enough that you can just ask your team to get on and do it. So, in that case, skip to step 7.

Inform your Stakeholders

But for an extensive change to your project, you will need to plan the fix. And you will also need to communicate the decision and your plan to your stakeholders. Probably, this is nothing more than informing them of what has happened and how you are acting to resolve it. This can be enormously reassuring and the cost of not doing so is often rumours and gossip about how things are going wrong and that you don’t have control of your project.

Sometimes, however, your fix is a big deal. It may involve substantial disruption, delay, or risk, for example. In this case, you may need to persuade some of your stakeholders that it is the right course of action. As always, communication is 80 percent of project management, and stakeholder engagement is critical to the success of your project.

7. Take Action

There’s an old saying: ‘There’s no change without action.’ Indeed.

What more can I say about this step that will give you any value?

Hmmm. Nothing.

8. Review and Evaluate Your Plan

But this step is vital. How you finish something says a lot about your character.

If you consider the problem-solving as a mini-project, this is the close stage. And what you need to do will echo the needs of that stage. I’ll focus on three components.

Review and Evaluate

Clearly, there is always an opportunity to learn from reviewing the problem, the problem-solving, and the implementation, after completion. This is important for your professional development and for that of your team colleagues.

But it is also crucial to keep the effectiveness of your fix under review. So, monitor closely, until you are confident you have completed the next task…

Prevent the Problem from Recurring

Another phrase from the world of Japanese manufacturing: ‘Poka Yoke’ .

This is mistake-proofing. It is about designing something so it can’t fail. What stops you from putting an SD card or a USB stick into your device in the wrong orientation? If you did, the wrong connections of pins would probably either fry the memory device or, worse, damage your device.

The answer is that they are physically designed so they cannot be inserted incorrectly.

What can you do on your project to make a recurrence of this problem impossible? If there is an answer and that answer is cost-effective, then implement it.

Celebrate your Success in Fixing it

Always the last thing you do is celebrate. Now, when Jim Lovell, Jack Swigert, and Fred Haise (the crew of Apollo 13) returned safely to Earth, I’ll bet there was a big celebration. For solving your project problem, something modest is more likely to be in order. But don’t skill this. Even if it’s nothing more than a high five and a coffee break, always ensure that your team knows they have done well.

What Approach Do You Use for Problem-Solving?

How do you tackle solving problems on your projects? Do tell us, or share any thoughts you have, in the comments below. I’ll respond to anything you contribute.

Never miss an article or video!

Get notified of every new article or video we publish, when we publish it.

Mike Clayton

About the author....

Great structure, Mike. We had a problem once that suited the “contain” step quite well. Lubricating oil and hydraulic fluid, from the same supplier, had been packaged incorrectly. A tech went to add oil to an aircraft’s engine, but dropped the can onto the concrete, and noticed red hydraulic fluid spill out! Obviously there’s now the risk that people have been inadvertently adding hydraulic fluid to aircraft engines… not good. It was actually FAR more important to contain this is real time so that aircraft, some of which could be airborne, could be safely grounded/quarantined. Resolving the subsequent ramifications could then be accomplished in “slow time” with some deliberate planning/execution.

Thank you very much. That’s a powerful illustration and hopefully the incudenbt did not cause any loss of life or serious damage.

 Get notified of every new article or video we publish, when we publish it.

Session expired

Please log in again. The login page will open in a new tab. After logging in you can close it and return to this page.

• Onsite training

3,000,000+ delegates

15,000+ clients

1,000+ locations

• KnowledgePass
• Log a ticket

01344203999 Available 24/7

7 Steps to Better Problem-Solving Process

Discover the Problem-Solving Process, from identifying issues to implementing optimal solutions. Explore the key steps and benefits to enhance decision-making. Read This blog covers each crucial step—identifying, analysing root causes, brainstorming solutions, evaluating options, and ensuring success through monitoring.

Exclusive 40% OFF

Training Outcomes Within Your Budget!

We ensure quality, budget-alignment, and timely delivery by our expert instructors.

Share this Resource

• Introduction to Management
• Introduction to Managing People
• Senior Management Training

Navigating problems is like solving a complex puzzle. It starts with recognising the issue and ends with implementing a successful solution. The Problem-Solving Process includes key steps: identifying the problem, clarifying it, generating solutions, evaluating options, and executing the best one. Each step builds on the previous, ensuring we tackle the root cause rather than just the symptoms.

The Problem-Solving Process embodies a curiosity, open-mindedness, and resilience mindset, viewing challenges as opportunities for growth and learning. Whether facing minor annoyances or major obstacles, this method equips us with the skills to transform barriers into opportunities and make wise choices. In this blog, we’ll explore this approach in depth. 

Table of contents 

1) What is a Problem-Solving  Process?

2) Steps of the Problem-Solving Process

3) Benefits of the Problem-Solving Process 

4) Creating Your Process for Problem-Solving  

5) Conclusion 

What is a Problem-Solving Process?

The Problem-Solving Process is a crucial analytical skill that helps individuals identify, analyse, and develop effective solutions to various challenges. It serves as a guiding framework, promoting logical and systematic approaches to address complex issues. By examining the root causes of problems and assessing potential options, individuals can make informed decisions and optimise outcomes.

Emphasising critical thinking and creativity, the Problem-Solving Process enhances adaptability and resilience in the face of adversity. Whether dealing with personal dilemmas or professional challenges, mastering this process empowers individuals to navigate uncertainties and achieve success.

Steps of Problem-Solving  Process

The Problem-Solving Process is a systematic approach to identifying, analysing, and resolving issues efficiently. Each step is designed to break down complex problems into manageable tasks, leading to effective solutions.

Step 1: Identify the Problem 

Initiate the Problem-Solving process by visualising the ideal scenario. Define the standard against which the current situation will be measured. Ask critical questions like, "If things were going perfectly, what would that look like?"

Further, determine the acceptable variation from the norm, considering factors like engineering precision or behavioural flexibility. Assess how much deviation is tolerable. This step sets the stage for a clear understanding of the problem's context and the criteria for an optimal outcome.

Step 2: Analyse the Problem 

Understand the problem's urgency by identifying its stage: emergent, mature, or crisis. An emergent problem allows time for corrective action without immediate threats. At the same time, a mature problem causes more than minor damage, necessitating quick intervention. A crisis demands immediate correction due to severe repercussions. Thus, evaluating the potential damage guides decision-making and makes sure an appropriate level of urgency is assigned to the problem.

Step 3: Describe the Problem 

Craft a concise problem statement in a clear yet short manner. This concise articulation serves as a focal point for the Problem-Solving effort. Further, statement should be distributed to the team for consensus, ensuring everyone involved agrees on the root cause. 

The critical question to ask here is, "Is your premise correct?" Validating the accuracy of the premise ensures a shared comprehension of the problem.

Step 4: Look for Root Causes  

This step involves a thorough investigation to uncover the underlying issues and come up with targeted solutions. Delve into the root causes of the problem by asking a series of questions: who, what, when, why, how, and where. You can use the 5Why method or Fishbone Diagram to explore the factors that led to a departure from the set standards. Also, assess the possibility of solving the problem permanently while aligning with effective leadership principles.

Step 5: Develop Alternate Solutions

This step emphasises the importance of exploring a range of possibilities before committing to a specific course of action. So, generate a list of diverse solutions beyond the initial perspective. Apply the One-third Plus One Rule for consensus-building, involving key stakeholders in the Decision-making Process. Further, rank solutions based on their efficiency, cost, and long-term value. Carefully select the most suitable solution, considering available resources and potential impacts.

Step 6: Implement the Solution 

Translate the chosen solution into action by creating an implementation plan. Outline responsibilities, timelines, and contingency measures to ensure a smooth execution. Moreover, clearly communicate team roles and track the solution's progress. This step involves strategic planning and coordination to bring the selected solution to completion. Also, anticipate potential deviations from the plan and establish mechanisms for prompt resolution.

Step 7: Measure the Results 

Evaluate the solution's effectiveness by measuring and tracking results. Answer critical questions about its success, learning opportunities, and applicability to future challenges. This step involves a systematic assessment of the outcomes against the desired objectives. Insights gained from this evaluation contribute to continuous improvement and the refinement of Problem-Solving skills. 

The focus is on deriving meaningful conclusions and utilising them for continuous enhancement.

Increase your productivity and efficiency with our Management Courses – Register now!

Benefits of the Problem-Solving Process 

Developing and implementing a Problem-Solving Process brings significant benefits. Listed below are the benefits that develop during this Process: 

1) Improves Analysis 

Individuals develop and refine their analytical skills as they engage in the Problem-Solving journey. This involves systematically examining complex situations, breaking them into manageable components, and comprehensively evaluating each element.

Through analysis, individuals gain a deeper understanding of the underlying factors contributing to the problem, leading to more precise and informed Problem Solving and Decision Making. Moreover, Problem Solving encourages individuals to gather relevant data, conduct research, and consider various perspectives. This can help enhance the accuracy and depth of their analysis. 

2) Improves Risk Management 

Individuals and teams naturally encounter various challenges and uncertainties as they engage in problem-Solving activities. In response, they learn to identify, assess, and mitigate potential risks associated with different solutions. 

This heightened risk management awareness allows for a more comprehensive evaluation of each proposed solution's possible consequences and likelihood of success. By carefully considering and addressing risks, decision-makers can make more informed and calculated choices, minimising potential adverse outcomes. 

3) Promotes Creative Thinking  

The Problem Solving Process serves as a catalyst for promoting creative thinking and unlocking innovative solutions to complex challenges. Individuals and teams engage in Problem Solving activities and are encouraged to explore various ideas and perspectives. 

This fosters divergent thinking, allowing the generation of unconventional and imaginative solutions that may not be initially apparent. By challenging conventional norms and encouraging the exploration of alternative approaches, Problem Solving stimulates the creative faculties of the mind. 

4) Improves Time Management 

The Problem-Solving Process significantly improves time management by instilling a structured approach to tackling challenges, promoting efficient decision-making, and cultivating a habit of prioritisation and productivity. Individuals and teams can better allocate time and resources as they break down complex problems into manageable steps. 

Moreover, the Process encourages swift evaluation of potential solutions, ensuring timely progress. These skills become ingrained, enabling individuals and teams to meet deadlines and optimise productivity. By embracing this process, individuals can effectively manage time in various aspects of life and work. 

Reduces Bias 

The Problem-Solving Process offers the invaluable benefit of reducing bias in decision-making. As individuals and teams work through problem-Solving activities, they are compelled to approach challenges systematically and objectively. This structured approach encourages considering various perspectives and examining evidence and data without preconceived notions or personal biases. 

Learn to strengthen your team with our Team Development Course today!

Potential Risks and How Can They be Mitigated by Problem-Solving Process?

Efficient risk management requires a systematic approach to identifying, evaluating, and minimising potential risks in any project or business endeavour. Here’s how the Problem-Solving process can be beneficial:

1) Risk Identification

The first step involves recognising potential risks that may impact the project or organisation. This includes brainstorming, analysing past data, and consulting experts to uncover hidden risks.

2) Risk Assessment 

 Once identified, each risk is evaluated based on its likelihood and potential impact. This stage involves prioritising risks to address the most significant threats first. Tools like risk matrices can be helpful in this process.

3) Risk Mitigation Strategies 

After assessment, strategies are developed to minimise each risk. This might involve implementing safeguards, exploring alternative approaches, or transferring risk through insurance. The goal is to reduce the likelihood or impact of each risk.

4) Contingency Planning

If mitigation strategies fail, contingency plans are created. These plans outline steps to take if a risk materialises, ensuring the organisation can respond quickly and effectively.

5) Monitoring and Review

Continuous monitoring and reviewing of risks ensure that mitigation strategies remain effective and can adapt to emerging threats.

6) Communication

Effective communication throughout the risk management process ensures that all stakeholders are informed and prepared to address potential risks.

Creating Your Process your Process  for Problem-Solving  

Below are the Problem-Solving  steps that can help you create a suitable process: 

1) Evaluate Problem-Solving Approach  approach 

To create an effective Process for Problem Solving, it is crucial to evaluate the Problem-Solving approach. Assess the success of previous solutions, identify areas for improvement, and gather feedback from team members. Further, adjust the Process based on insights gained, fostering continuous improvement and enhancing Problem-Solving capabilities. 

2) Identify Your Strengths your strengths 

When creating a Problem-Solving Process, it's essential to identify your strengths. Recognise the skills and expertise within your team and your talents. Leveraging these strengths will enable you to assign tasks effectively and collaborate efficiently. It will also help capitalise on your team's unique abilities to achieve successful Problem-Solving outcomes. 

3) Research Strategies  for Problem-Solving  

To create an effective Problem-Solving Process, researching feasible strategies is vital. Explore various Problem-Solving Techniques, methodologies, and best practices. Consider their applicability to your specific challenges and team dynamics. A well-informed approach ensures you adopt the most suitable strategies to tackle problems efficiently and achieve desired outcomes. 

4) Encourage Feedback  

While creating a Problem-Solving Process, it is crucial to encourage feedback. Foster an open and supportive environment for team members to freely share their thoughts and experiences. Valuable insights from diverse perspectives empower continuous improvement, refine Problem-Solving strategies, and enhance overall effectiveness in resolving challenges successfully. 

5) Evaluate Your Process  

When creating your Problem-Solving Process, testing and revising are essential steps. Implement the strategy in real-life scenarios to evaluate its effectiveness. Seek feedback from team members and superiors to examine strengths and areas for improvement. Make necessary adjustments to refine and optimise the process for better Problem Solving outcomes. 

6) Improve Problem-Solving Skills 

To create an effective Problem-Solving Process, prioritise improving Problem Solving skills. Encourage continuous learning through workshops, training, and skill-building exercises—practice solving diverse problems to gain experience and confidence. By investing in skill development, individuals and teams can enhance their Problem-Solving capabilities and achieve better outcomes in challenging situations. 

Conclusion 

Developing a well-defined and adaptive Problem-Solving Process is crucial for navigating the complexities of life and work successfully. By fostering creativity, promoting collaboration, and continuously refining strategies, individuals and teams can approach challenges confidently and with agility, ultimately leading to improved problem resolution and overall success. 

Learn to implement Problem-Solving skills with our Problem-Solving Training – Sign up now!

Frequently Asked Questions

Choosing the appropriate problem-solving tool depends on the nature of the issue. Mind mapping helps generate ideas by visually displaying connections between concepts. On the other hand, the Fishbone diagram systematically identifies potential causes, with branches representing different categories of causes.

The 7-Diamond Problem Solving Process is a systematic approach to tackling complex issues. It involves the following seven steps:

a) Define the Problem

b) Gather Data

c) Analyse Data

d) Develop Hypotheses

e) Verify Hypotheses

f) Identify Root Cause

g) Implement Solution

The Knowledge Academy takes global learning to new heights, offering over 30,000 online courses across 490+ locations in 220 countries. This expansive reach ensures accessibility and convenience for learners worldwide. 

Alongside our diverse Online Course Catalogue , encompassing 17 major categories, we go the extra mile by providing a plethora of free educational Online Resources like News updates, Blogs , videos, webinars, and interview questions. Tailoring learning experiences further, professionals can maximise value with customisable Course Bundles of TKA .

The Knowledge Academy’s Knowledge Pass , a prepaid voucher, adds another layer of flexibility, allowing course bookings over a 12-month period. Join us on a journey where education knows no bounds.

The Knowledge Academy offers various Management Courses , including the Problem-Solving Course, Productivity and Time Management and Costing and Pricing Training. These courses cater to different skill levels, providing comprehensive insights into Problem-Solving . 

Our Business Skills Blogs cover a range of topics related to Leadership, offering valuable resources, best practices, and industry insights. Whether you are a beginner or looking to advance your Business skills, The Knowledge Academy's diverse courses and informative blogs have got you covered.  

Upcoming Business Skills Resources Batches & Dates

Fri 29th Nov 2024

Fri 6th Dec 2024

Fri 14th Feb 2025

Fri 16th May 2025

Fri 25th Jul 2025

Fri 29th Aug 2025

Fri 10th Oct 2025

Fri 28th Nov 2025

Get A Quote

WHO WILL BE FUNDING THE COURSE?

My employer

By submitting your details you agree to be contacted in order to respond to your enquiry

• Business Analysis
• Lean Six Sigma Certification

Share this course

Biggest black friday sale.

We cannot process your enquiry without contacting you, please tick to confirm your consent to us for contacting you about your enquiry.

By submitting your details you agree to be contacted in order to respond to your enquiry.

We may not have the course you’re looking for. If you enquire or give us a call on 01344203999 and speak to our training experts, we may still be able to help with your training requirements.

Or select from our popular topics

• ITIL® Certification
• Scrum Certification
• ISO 9001 Certification
• Change Management Certification
• Microsoft Azure Certification
• Microsoft Excel Courses
• Explore more courses

Press esc to close

Fill out your  contact details  below and our training experts will be in touch.

Fill out your   contact details   below

Thank you for your enquiry!

One of our training experts will be in touch shortly to go over your training requirements.

Back to Course Information

Fill out your contact details below so we can get in touch with you regarding your training requirements.

* WHO WILL BE FUNDING THE COURSE?

Preferred Contact Method

No preference

Back to course information

Fill out your  training details  below

Fill out your training details below so we have a better idea of what your training requirements are.

HOW MANY DELEGATES NEED TRAINING?

HOW DO YOU WANT THE COURSE DELIVERED?

Online Instructor-led

Online Self-paced

WHEN WOULD YOU LIKE TO TAKE THIS COURSE?

Next 2 - 4 months

WHAT IS YOUR REASON FOR ENQUIRING?

Looking for some information

Looking for a discount

I want to book but have questions

One of our training experts will be in touch shortly to go overy your training requirements.

Your privacy & cookies!

Like many websites we use cookies. We care about your data and experience, so to give you the best possible experience using our site, we store a very limited amount of your data. Continuing to use this site or clicking “Accept & close” means that you agree to our use of cookies. Learn more about our privacy policy and cookie policy cookie policy .

We use cookies that are essential for our site to work. Please visit our cookie policy for more information. To accept all cookies click 'Accept & close'.

The Systematic Problem-Solving (SPS) Method:

Make better decisions tom g. stevens phd.

Solving problems is important in every area of human thinking. Learning general problem-solving skills can therefore help you improve your ability to cope with every area of your life. All disciplines of philosophy, business, science, and humanities have developed their own approach to solving problems. Remarkably, the problem-solving models developed by each of these areas are strikingly similar. I describe a simple problem-solving process that you can use to solve almost all problems.

Stages of the problem-solving process. The famous psychologist, Dr. Carl Rogers, was one of the first to help us understand how important self-exploration and problem-solving are for overcoming all types of personal, psychological, and daily-living problems. (1);

Consciously going through each of these four stages when solving any complex problem can be very useful. Following are the five stages of the problem-solving method.

STAGE 1: EXPLORATION OF THE PROBLEM

STAGE 2: EXPLORING ALTERNATIVE SOLUTIONS (Routes to Happiness);

STAGE 3: CHOOSING THE BEST ALTERNATIVE

STAGE 4: PLANNING AND ACTION

STAGE 5: EXPERIMENTING AND GATHERING FEEDBACK

During this stage, we gather all of the information we can about both external aspects of the problem and internal aspects. Good information gathering is not an easy process. Scientists spend their whole lives trying to learn about some very small piece of the world. The type of information-gathering process we use will depend upon the type of problem we are trying to solve. For information about the world the following are powerful skills to use.

•  Library reference skills
•  Observational skills
•  Informational interviewing skills
•  Critical thinking skills
•  Scientific method skills
•  Data analysis and statistical skills

Learning how to become an expert at identifying problems and finding causes is essential to become an expert in any field. The above skills are useful in solving many types of problems--even intra-personal ones. However, the focus of this book is how to be happy; and the key to happiness almost always involves not just external causes but internal ones as well.

It is usually much easier for most of us to observe an external event than an internal one. We have our external sensory organs to see and hear external events, but not internal ones. How do we observe that which we cannot see? We can learn to be better observers of our emotions, self-talk, and images.

The self-exploration process described above provides enough information to make you an expert at self-exploration. That is one of the most essential parts of developing your own inner therapist.

STAGE 2: EXPLORING ALTERNATIVE SOLUTIONS OR ROUTES TO HAPPINESS

Gather all the best information you can about possible solutions. Use brainstorming techniques, observe and consult with people who have overcome similar problems, read relevant material, consult experts, and recall your own relevant past experience. Look at both internal and external solutions.

Once you learn so many different routes to happiness, then you will be truly free to choose to be happy in almost any situation you face in life. The actual choice is made in stage 3 of the /problem-solving process. The appendix contains a very useful decision-making model for helping you make complex choices such as choosing a career or relationship. The following is a simple approach to making a decision between alternatives. (See Carkhuff Decision-Making Model, below, for a method for making complex decisions--for career or life planning.);

(1); List all the alternatives you are considering

(2); List all of the values or criteria that will be affected by the decision

(3); Evaluate each alternative by each criteria or value

(4); Choose the alternative which you predict will satisfy the criteria the best and lead to your greatest overall happiness

STAGE 4:  PLANNING AND ACTION (Experimenting);

Many decisions are made, but never implemented. See that you follow-up with good planning. Once you have made your choice, you can use some of the planning methods suggested in the O-PATSM method from chapter 11 to make sure that you follow through with your decision.

This is the stage of acting on your decision. Many people fear making mistakes and failure as if these were some terrible sins that they should never commit. That view of life of life makes every decision and action seem very serious and they often become very timid people who lack creativity and are plagued by guilt and fear of failure. Instead we can view every action as an experiment. If one of our overall goals in life is learning and growth, then we can never fail to learn. All people who have accomplished great happiness for themselves and contributed to others have shared the courage to act on their beliefs.

STAGE 5: GATHERING FEEDBACK

Many people hate to be evaluated and dread finding out the results of what they have done out of fear that the feedback will be negative. These fears can be serious impediments to the growth that can only happen through getting open, accurate feedback.

However, once learning and growth are important goals, then getting feedback becomes highly desirable. How else can we learn? Even negative outcomes can provide valuable information. Of course, almost everyone would rather have outcomes that maximize happiness; but when we don't, we can at least try to maximize our learning. Learning can help maximize happiness in the future.

We can also make the mistakes of dwelling on past mistakes that goes beyond constructive learning and reasonable reparations to victims and of punishing ourselves unnecessarily. Normally, there is no value to punishment--once a lesson has been learned. (2); Keep clear at all times that this problem-solving process is only a tool to serve the overall life goals of increased health, growth, and happiness.

CARKHUFF DECISION-MAKING MODEL:   This particular decision-making model is based upon one by Dr. Robert Carkhuff and follows the general guidelines of a considerable amount of research on how people can make more effective decisions. It can also be used for any other type of decision--from buying a new car to choosing a mate.

EXAMPLE OF USING THE DECISION-MAKING MODEL

The decision-making model will be illustrated in a way which you can use aa an analogy for making your own career decision. In this example, Henry is trying to decide whether to major in psychology or in computer science. Thus he has narrowed his alternatives to the following two:

1); majoring in psychology with a career goal of either going into high school counseling or teaching or 2); majoring in computer science with a possible goal of working as a computer programmer.

These are represented along the top axis of the following matrix.

  ** is the WINNER-it has the most points of the two alternatives

STEPS TO USING THE DECISION-MAKING MODEL--(use above example);

STEP 1-- LIST YOUR CAREER ALTERNATIVES. This is your refined list of alternatives of which majors or occupations you are trying to decide between. Remember, that you can list as many as you want. You can list unusual combinations of simpler alternatives. For Henry those narrowed alternatives were psychology and computer science.

STEP 2--CAREER SELECTION CRITERIA. Review your Career Selection Criteria list and write all the important career selection criteria in the far left column. Note that repeating the same idea or leaving out an important idea can affect the decision outcome.

STEP 3-- CRITERIA WEIGHTS. Evaluate the relative importance to you of each of your Career Selection Criteria on a scale of 1 to 10 (10 being the most important);. Write your answer in the column next to the selection criteria.

STEP 4--ALTERNATIVE EVALUATION SCALE. Each alternative is to be evaluated from the point of view of each selection criterion. You need to think about what this means for each selection criterion. For example Henry determined that for the selection criteria of income , a "minimally acceptable" income would be $25,000 starting with prospects of making up to $50,000 eventually. An outstanding salary would be starting at about $40, 000 with prospects of making up to $100,000.

+5 = Maximum evaluation--outstanding (example: income begin $40,000 go to $100,000 +4, +3, +2, +1 = intermediate values

0 = Minimally acceptable value. (example: income = begin $20,000 go to $45,000);

-1, -2, -3, -4 = intermediate values

-5 = Minimum evaluation--worst possible (example: income < $10,000

STEP 5--EVALUATE EACH ALTERNATIVE BY EACH SELECTION CRITERION. Use the evaluation scale from step 3 to evaluate each alternative from the point of view of each Career Selection Criterion. Give it rating from -5 to +5. In the example above, both alternatives were evaluated on the criterion of "income": Henry gave the psychology income an evaluation of "+2" and computer science income an evaluation of " +4."

STEP 6--MULTIPLY THE CRITERIA WEIGHTS TIMES THE EVALUATIONS. In the example above for the selection criterion of "income," Henry multiplied the criterion weight of "9" times the evaluation of " +2" for "PSYCH" to get a result of "18." That is its SCORE OR POINTS for psychology on the criterion of income. Put it inside of the parentheses. This score of 18 is an overall prediction much Henry's income in psychology will contribute to his overall happiness. Since he had a score of 36 in computer science, he his predicting that he will be much happier with his income in that field.

STEP 7--FIND THE OVERALL SUM OF THE SCORES FOR EACH ALTERNATIVE. Add together the numbers inside the parentheses for each alternative. In the example above, the overall sum for the "PSYCH" alternative is "405."

STEP 8--COMPARE THE ALTERNATIVES WITH EACH OTHER AND WITH THE "IDEAL." The "ideal" is the maximum possible number of points. Once you have determined all the totals and compared them to each other, try to figure out why one alternative came out ahead of another--where it got its points. Play with the points until you think the points match your true feelings and values.

* The alternative with the most points is the one you are predicting will make you the happiest person.

1. 1 Some might argue that Freud was the first. He clearly did describe many helpful techniques. I think that some of his free association techniques are still very useful for helping to find underlying beliefs, images, or cognitive systems which are related to the problem. However, Rogers was the one that more clearly described the stages of self-exploration and problem-solving and the conditions of unconditional positive regard, empathetic understanding, and genuineness on the part of the therapist which seem to be important to the therapeutic process or to any person attempting to feel better.

Robert Carkhuff (one of Roger's pupils); has developed a structured training system for helping people learn these skills. Robert Cash, a personal friend, has further elaborated these skills in his own courses and introduced me to this process. There is a good deal of research supporting the effectiveness of these techniques.

2. 2 This statement does not address the use of punishment as a deterrent to prevent some persons from profiting from their dysfunctional behaviors. For example if behaviors such as murder, robbery, or selling drugs are not given sufficient punishment, some people will engage in these behaviors. A person whose ultimate concern is money and pleasure may deal drugs to make money with little regard to how it affects others. Increasing the cost for a person with those beliefs can reduce the chances they will sell drugs.

Self-Help and other resources on this website (and site map)

Copyright 2024 Tom G. Stevens PhD  

CSense Management Solutions Pvt Ltd

Search search, systematic problem-solving.

What is Problem-solving?

Before we understand problem-solving, let us first calibrate ourselves on ‘what is called a problem?’

When there is a gap between our expectations and reality, we feel unhappy – which is a Problem . This is how a deviation from the specification, a failure to meet timelines, etc., become our problems. A problem could be defined as “the gap between our expectations and actual state or observation”.

From the gap analogy, we also understand that as the gap increases, our suffering intensifies.

Problem-solving

A fundamental part of every manager’s role is problem-solving. So, being a confident problem solver is really important to your success.

Much of that confidence comes from having a good process to use when approaching a problem. With one, you can solve problems quickly and effectively. Without one, your solutions may be ineffective, or you’ll get stuck and do nothing, sometimes with painful consequences.

Managing the problem (correction) instead of solving it (with corrective action) creates firefighting in our daily work. To solve a problem permanently, we need to understand and act on its root cause. We will also follow the steps of identifying root causes and prevent their recurrence in this workshop.

CSense IC 3 Approach

• Identification
• Containment Action
• Investigation
• Cause Analysis
• Improvement

Applications of methodology

The methodology is simple and applicable to most of the problems faced by the industries. Hence, it is widely accepted and recommended by companies. This also forms a framework for Auto industries’ 8D Problem Solving, Pharma industries’ USFDA recommended 7 step approach and Six Sigma’s DMAIC approach.

Training Contents

• Overview of Problem-solving
• Need for Problem-Solving
• Managing a Problem Vs Problem Solving
• Definitions – Correction, Corrective Action & Preventive Action

Step by Step Approach to Problem-Solving

1. identification.

• Use of 5W2H questions

2. Containment Action

• Assessing the problem and its risk
• Forming Effective Teams
• CFT & CHT
• Damage control – Interim Actions
• Communication plan

3. Investigation

• Data / Evidence Collection

4. Cause Analysis

• Brainstorming for Problem-solving
• Fishbone Analysis
• Is – Is Not Analysis
• Process Mapping
• Data and Statistical Analysis
• Data collection
• Graphical Tools
• Why-Why Analysis
• Validation of Root causes
• Statistical Analysis

5. Improvement

• Permanent Corrective Action
• Solution Generation
• Pilot Implementation
• Solution Action Plan
• Preventing Recurrence
• Control Plan
• Verification of Status
• Verification of Effectiveness
• Training & Documentation

Training Duration

• Two days – 16 hours

About the Course

The Problem-Solving workshop caters to leaders and managers who are interested in solving the recurring problems and want to bring in the culture and team-based approach of systematic problem solving to every level of people in the organisation. We deal with the most relevant tools in the step-by-step approach. We can take up the actual cases of recurring problems in the company as an example and study for the workshop. The course covers essential problem-solving tools like problem definition, containment action, root cause analysis with QC tools, root cause validation using statistical tools, corrective action, preventive action, escape points, Poka-yoke and more.

Course Objectives

At the end of the course, participants will be able to understand and appreciate

• Cost of Poor Quality
• The need for Systematic problem-solving
• Various approaches to problem-solving
• Difference between correction, corrective action and preventive action
• Team approach enhance effective solutions and learning
• Risk assessment and containment actions
• Root cause analysis
• Statistical tools
• Arriving at an effective action plan
• Preventing the defects

Target Audience

• Managers responsible for process improvements
• Quality Managers, Internal and External Auditors
• Shop floor managers and supervisors
• Production and Maintenance Managers
• Product Design Engineers
• Research Engineers & Scientists

Workshop Methodology

CSense Workshop approach is based on scientifically proven methodologies of Learning, which includes Learning by

• Listening – Classroom sessions & Audio-Visuals
• by Teaching
• Examples & Exercises at the end of each step
• We will provide the required Templates and formats for each tool
• During the course, we will form 3 to 4 cross-functional teams
• We will help each team choose a specific problem (either an open Non-conformance or a recently closed out non-conformance)
• We encourage the teams to choose different types of problems like Audit observations, internal failures/rejections, customer complaints, machine breakdown or accidents.
• Then we will guide the participants to work on their assigned problem with the new approach – application & documentation.
• Faculty will help the teams to apply the learning on the problems and explain the practical doubts.
• After each step, teams will present their work.

Min 12 and Max 20 Participants per batch

Customisation

We can customise the deliverable as per client’s requirements.

Certification

• Certification Criteria: 90% attendance in Training Sessions, participation in activities and 70% Score in written test
• The test will be conducted on 2 nd day of training
• Laptop/desktop with provision to install software packages for participants to be arranged by the client.

Additional Support

Continued coaching and hand-holding support could be provided by CSense after the workshop for successful project completion, as an optional engagement.

Guide: A3 Problem Solving

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 one of the key tools a successful business needs to structure improvements and one I have been using to solve problems in a structured way in my career at a range of businesses over the years. When there is a problem in business that is leading to increased costs, waste , quality issues, etc., it is necessary to address these problems. A3 structured problem solving is a Lean Six Sigma methodology that has been designed and developed to support continuous improvement and solve complex business problems in a logical and structured process. 

The guide will give you a full understanding of what A3 Problem solving is and a breakdown of all the steps of how to apply it within your business with an example of where I have made improvements with it previously.

Want exclusive templates, tools and guides?

Join our email list below and for the next 28 days, we will send you exclusive tools, templates and guides unavailable on the website. We developed a short and simple 28-day program designed to develop your ability to implement Lean and Six Sigma methods daily.

Importance of A3 in Lean Management

The A3 problem-solving method is a key tool in Lean Six Sigma and continuous improvement in business, and in my experience, it is often the standard approach all improvement activities must follow and is particularly popular in the automotive industry. This is because of the following:

Focus on Root Causes : Rather than applying a quick fix to a problem or jumping to conclusions and solutionizing, A3 requires gaining a deep understanding of the root causes of the problem. By addressing these root causes, the chances of recurrence is reduced.

Standardization : With a consistent format, the A3 process ensures that problems are approached in a standardized way, regardless of the team or department. This standardization creates a common language and understanding across the organization and ensures all problems are addressed to the same standard and approach.

Team Involvement : An A3 isn’t an individual process. It requires a cross-functional team to work together on problem-solving, ensuring that a range of perspectives and expertise is considered. This collective approach builds a stronger understanding of the problem and ensures that solutions are well-rounded and robust.

Visual Storytelling : The A3 report serves as a visual storyboard, making it easier for stakeholders at all levels to understand the problem, the analysis, and the countermeasures. This visualization enhances communication and drives alignment.

The 6 Steps of A3 Problem Solving (With Real Example)

The A3 problem-solving process can initially seem difficult if you have never done one before and particularly if you have never been a team member in one. To help you with this we will break down the 6 steps into manageable activities, followed by a real-life example to help you apply this method within your business.

As a side note, the A3 problem-solving process was actually one of the first Lean Six Sigma tools I learned to use three weeks into my continuous improvement career after being thrown into the deep end due to resource availability, so I can understand how difficult it can be to understand. 

Step 1: Describe the problem

Problem description.

The problem description is an important first step in the process as it ensures a common understanding with the team of what the issue is that needs to be addressed. This can be done by using a technique called the 5W1H Is/Is Not method to help gain a clear understanding of the problem. 

To understand the 5W1H Is/Is Not the Process, check out our guide for details of that technique. However, in short, it’s about asking key questions about the problem, for example, “What IS the problem?” and “What IS NOT the problem?”

Let’s say you have been asked to look into a problem where “Machine downtime on the automotive assembly line has increased by 30% over the past three months, leading to production delays and increased costs.”

An example of a 5W1H Is/Is Not on this may result in the following output:

 Based on this we can create a clear problem description as the focus of the project that give the team a clear and common understanding of the issue looking to be resolved in the next steps of the process. The problem description could then be written as:

“Over the past three months, machine downtime on Automotive Assembly Line No.3 has increased by 30%. This has predominantly affected the assembly line workers and leads, leading to production delays and higher labour costs. “

Current Condition

Next is demonstrating the current condition and demonstrating the impact on the business. This can often be done with data and charts to back up the problem that might show trends or changes in outputs.

This might look something like the below and demonstrate a good baseline for confirming the improvement at the end of the A3

Containment Actions

Next is containment actions. Since you have identified a problem, there is likely an impact on the business or the customer. As a team, you should consider what can be done to limit or eliminate this problem in the short term. Remember this is just a containment action and should not be seen as a long-term fix. 

In our situation we decided to “Implement temporary overtime shifts to meet production goals, leading to an increase in labor costs.”

At this stage, the A3 should look similar to the one below; you can use charts and graphics to represent the current state as well if they fit within the limit area. Remember, we must include the content of the A3 within the 1-page A3 Document.

Step 2: Set the A3 Goals

The next step of the A3 is to, as a team, set the goal for the project. As we have a clear understanding of the current condition of the problem, we can use that as our baseline for improvement and set a realistic target for improvement. 

A suggested method for setting the Target condition would be to use the SMART Target method.

If you are not familiar with SMART Targets , read our guide; it will cover the topic in much more detail. In short, a SMART target creates a goal statement that is specific, measurable, achievable, relevant and time-bound. 

By doing this you make it very clear what the goal of the project is, how it will be measured, it is something that can be achieved, relevant to the needs of the business and has a deadline for when results need to be seen.

For our A3 we decided that the goal would be “Our goal is to achieve at least a 20% reduction in machine downtime on Automotive Assembly Line No.3, lowering it from 90 minutes to no more than 72 minutes per day per machine, within the next 60 days. This reduction is crucial for increasing productivity and reducing labour costs, aligning with our overall business objectives.”

I also recommend using charts in this section to visualize the benefit or improvement to ensure you have stakeholder and sponsor support. Visuals are much easier and faster for people to understand.

At this point, your A3 might look something like the one below, with the first 1/4 or section complete. The next step is to move on to the root cause analysis to get to the root of the problem and ensure the improvement does not focus on addressing the symptoms of the problem.

Step 3: Root Cause Analysis

Root cause analysis is the next step in the process, often referred to as gap analysis, as this step focuses on how to get to the goal condition from the current condition.

Tip: If at this point you find the team going off-topic and focusing on other issues, Ask the question, “Is this preventing us from hitting our goal statement?”  I have found this very useful for keeping on track in my time as an A3 facilitator.

For root cause analysis, a couple of key tools are usually used: a fishbone diagram and a five-why Analysis . Again, we won’t go into the full details of these tools within this guide, as they have been covered in extensive detail in their own guides.

But the aim at this point is as a team, to brainstorm what is preventing us from achieving our target condition. This is done by allowing all members of the team to input the reasons they think it is not being achieved. These inputs are often written on sticky notes and placed on the fishbone diagram. Following this, you may have results similar to the ones below.  Note: it is important that the inputs are specific so they can be understood. e.g. “Calibration” alone is not specific to how it’s causing the problem; specify it with “Calibration: Inaccurate measurements affecting machine settings.”

After the fishbone diagram has been populated and the team has exhausted all ideas, the team should then vote on the most likely cause to explore with a 5 Whys analysis. This is done because, due to resource limitations, it is unlikely all of the suggestions can be explored and actioned.

In this situation the team decided the “lack of preventative machines: machines not being serviced regularly” was the cause of increased downtime. This was explored with the 5 Whys to get to the root cause of why Assembly Line 3 did not have preventative maintenance implemented.

The result of this root cause analysis can be seen below, and you may end up with more ideas on the fishbone, as generally there are a lot of ideas generated by a diverse team during brainstorming.

Step 4: Solutions and Corrective Actions

Now that we understand what the root cause of the problem is, we need to address it with solutions and corrective actions. Again, as a team, consider the root cause of the problem and discuss what actions need to be taken by the team, who will do them, and when they will be done. The result should be an action plan, for example, like the one below:

This action plan needs to be carried out and implemented.

The result of this section will likely just be an action list and look like the below section.

Step 5: Validate Solution and Standardize

Within step 5 it is time to collect data to validate and confirm the actions that have been implemented resulting in solving the problem and meeting the target state of the problem. This is done by continuing to collect data that demonstrates the problem in the baseline to see if the problem is being reduced.

For example, below, the project team continued to collect Assembly Line 3 downtime data on a weekly basis. Initially, there was a steady reduction, likely due to the focus of the project on the problem, which had some impact. However, once the majority of the action was implemented, a huge drop in product downtime was seen, exceeding the target. This showed the actions have been successful

If, in the validation stage, you find that the improvement required is not being made, you should go back to step 3 and reconsider the root cause analysis with the team, pick another area to focus on, and create an action plan for that following the same steps.

Step 6: Preventive Actions and Lessons Learned

In step 6 after the confirmation of project success you should look at preventive actions and lessons learned to be shared from this project:

• Preventive Action: The new preventive maintenance schedule will be standardized across all assembly lines. This will prevent other lines having similar issues and make further improvements
• Lessons Learned: A formal review will be conducted to document the process, including challenges faced and how they were overcome, which will then be archived for future reference.

In our project, this looked like the one below and will be used as a reference point in the future for similar issues. 

And that is the successful completion of a structured A3 problem-solving technique.

The complete A3 looks like the below image. Yours may slightly differ as the problem and information vary between projects.

Downloadable A3 Reporting Template

To support you with your A3 problem solving, you can download our free A3 problem solving report from the template section of the website.

Problem-solving is important in businesses, specifically when faced with increased costs or quality issues. A3 Structured Problem Solving, rooted in Lean Six Sigma, addresses complex business challenges systematically.

Originally from Toyota’s lean methodology, A3, named after the 11″x17″ paper size, visually maps problem-solving processes. This method ensures concise communication and focuses on crucial details, as illustrated by the provided example.

Emphasized in Lean Management, A3 stresses understanding root causes, standardization across teams, team collaboration, and visual representation for clarity. This tool is not only a guide to understanding the issue but is a standardized format ensuring robust solutions. Particularly for novices, breaking down its six steps, from problem description to setting A3 goals and root cause analysis, provides clarity. Visual aids further enhance comprehension and alignment across stakeholders.

• Sobek II, D.K. and Jimmerson, C., 2004. A3 reports: tool for process improvement. In  IIE Annual Conference. Proceedings  (p. 1). Institute of Industrial and Systems Engineers (IISE).
• Matthews, D.D., 2018.  The A3 workbook: unlock your problem-solving mind . CRC Press.

Q: What is A3 problem solving?

A: A3 problem solving is a structured approach used to tackle complex problems and find effective solutions. It gets its name from the A3-sized paper that is typically used to document the problem-solving process.

Q: What are the key benefits of using A3 problem solving?

A: A3 problem solving provides several benefits, including improved communication, enhanced teamwork, better problem understanding, increased problem-solving effectiveness, and the development of a culture of continuous improvement.

Q: How does A3 problem solving differ from other problem-solving methods?

A: A3 problem solving emphasizes a systematic and structured approach, focusing on problem understanding, root cause analysis, and the development and implementation of countermeasures. It promotes a holistic view of the problem and encourages collaboration and learning throughout the process.

Q: What are the main steps in the A3 problem-solving process?

A: The A3 problem-solving process typically involves the following steps: problem identification and description, current condition analysis, goal setting, root cause analysis, countermeasure development, implementation planning, action plan execution, and follow-up and evaluation.

Q: What is the purpose of the problem identification and description step?

A: The problem identification and description step is crucial for clarifying the problem, its impact, and the desired outcome. It helps establish a common understanding among the team members and ensures everyone is working towards the same goal.

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

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.