8d (eight disciplines) problem solving methodology

How it works

For Business

Join Mind Tools

Article • 8 min read

8D Problem Solving Process

Solving major problems in a disciplined way.

By the Mind Tools Content Team

(Also known as Global 8D Problem Solving)

When your company runs into a major problem, you need to address it quickly. However, you also need to deal with it thoroughly and ensure that it doesn't recur – and this can take a lot of effort and elapsed time.

The 8D Problem Solving Process helps you do both of these seemingly-contradictory things, in a professional and controlled way. In this article, we'll look at the 8D Problem Solving Process, and we'll discuss how you can use it to help your team solve major problems.

Origins of the Tool

The Ford Motor Company® developed the 8D (8 Disciplines) Problem Solving Process, and published it in their 1987 manual, "Team Oriented Problem Solving (TOPS)." In the mid-90s, Ford added an additional discipline, D0: Plan. The process is now Ford's global standard, and is called Global 8D.

Ford created the 8D Process to help teams deal with quality control and safety issues; develop customized, permanent solutions to problems; and prevent problems from recurring. Although the 8D Process was initially applied in the manufacturing, engineering, and aerospace industries, it's useful and relevant in any industry.

The eight disciplines are shown in figure 1, below:

Figure 1: The 8D Problem Solving Process

The 8D Process works best in teams tasked with solving a complex problem with identifiable symptoms. However, you can also use this process on an individual level, as well.

Applying the Tool

To use the 8D Process, address each of the disciplines listed below, in order. Take care not to skip steps, even when time is limited; the process is only effective when you follow every step.

Discipline 0: Plan

Before you begin to assemble a team to address the problem, you need to plan your approach. This means thinking about who will be on the team, what your time frame is, and what resources you'll need to address the problem at hand.

Discipline 1: Build the Team

You should aim to put together a team that has the skills needed to solve the problem, and that has the time and energy to commit to the problem solving process.

Keep in mind that a diverse team is more likely to find a creative solution than a team of people with the same outlook (although if outlooks are too diverse, people can spend so much time disagreeing that nothing gets done).

Create a team charter that outlines the team's goal and identifies each person's role. Then, do what you can to build trust and get everyone involved in the process that's about to happen.

If your team is made up of professionals who haven't worked together before, consider beginning with team-building activities to ensure that everyone is comfortable working with one another.

Discipline 2: Describe the Problem

Once your team has settled in, describe the problem in detail. Specify the who, what, when, where, why, how, and how many; and use techniques like CATWOE and the Problem-Definition Process to ensure that you're focusing on the right problem.

Start by doing a Risk Analysis – if the problem is causing serious risks, for example, to people's health or life, then you need to take appropriate action. (This may include stopping people using a product or process until the problem is resolved.)

If the problem is with a process, use a Flow Chart , Swim Lane Diagram , or Storyboard to map each step out; these tools will help your team members understand how the process works, and, later on, think about how they can best fix it.

Discovering the root cause of the problem comes later in the process, so don't spend time on this here. Right now, your goal is to look at what's going wrong and to make sure that your team understands the full extent of the problem.

Discipline 3: Implement a Temporary Fix

Once your team understands the problem, come up with a temporary fix. This is particularly important if the problem is affecting customers, reducing product quality, or slowing down work processes.

Harness the knowledge of everyone on the team. To ensure that each person's ideas are heard, consider using brainstorming techniques such as Round Robin Brainstorming or Crawford's Slip Writing Method , alongside more traditional team problem solving discussions.

Once the group has identified possible temporary fixes, address issues such as cost, implementation time, and relevancy. The short-term solution should be quick, easy to implement, and worth the effort.

Discipline 4: Identify and Eliminate the Root Cause

Once your temporary fix is in place, it's time to discover the root cause of the problem.

Conduct a Cause and Effect Analysis to identify the likely causes of the problem. This tool is useful because it helps you uncover many possible causes, and it can highlight other problems that you might not have been aware of. Next, apply Root Cause Analysis to find the root causes of the problems you've identified.

Once you identify the source of the problem, develop several permanent solutions to it.

If your team members are having trouble coming up with viable permanent solutions, use the Straw Man Concept to generate prototype solutions that you can then discuss, tear apart, and rebuild into stronger solutions.

Discipline 5: Verify the Solution

Once your team agrees on a permanent solution, make sure that you test it thoroughly before you fully implement it, in the next step.

• Conducting a Failure Mode and Effects Analysis (FMEA) to spot any potential problems.
• Using Impact Analysis to make sure that there will be no unexpected future consequences.
• Using Six Thinking Hats to examine the fix from several different emotional perspectives.

Last, conduct a Blind Spot Analysis to confirm that you and your team haven't overlooked a key factor, or made an incorrect assumption about this solution.

Discipline 6: Implement a Permanent Solution

Once your team reaches a consensus on the solution, roll your fix out. Monitor this new solution closely for an appropriate period of time to make sure that it's working correctly, and ensure that there are no unexpected side effects.

Discipline 7: Prevent the Problem From Recurring

When you're sure that the permanent solution has solved the problem, gather your team together again to identify how you'll prevent the problem from recurring in the future.

You might need to update your organization's standards, policies, procedures, or training manual to reflect the new fix. You'll likely also need to train others on the new process or standard. Finally, you'll need to consider whether to change your management practices or procedures to prevent a recurrence.

Discipline 8: Celebrate Team Success

The last step in the process is to celebrate and reward your team's success . Say "thank you" to everyone involved, and be specific about how each person's hard work has made a difference. If appropriate, plan a party or celebration to communicate your appreciation.

Before the team disbands, conduct a Post-Implementation Review to analyze whether your solution is working as you thought, and to improve the way that you solve problems in the future.

In the late 1980s, Ford Motor Company developed the 8D (8 Disciplines) Problem Solving Process to help manufacturing and engineering teams diagnose, treat, and eliminate quality problems. However, teams in any industry can use this problem solving process.

The eight disciplines are:

• Build the Team.
• Describe the Problem.
• Implement a Temporary Fix.
• Identify and Eliminate the Root Cause.
• Verify the Solution.
• Implement a Permanent Solution.
• Prevent the Problem From Recurring.
• Celebrate Team Success.

The 8D Problem Solving Process is best used with a team solving complex problems; however, individuals can also use it to solve problems on their own.

Ford is a registered trademark of the Ford Motor Company: https://www.ford.com/

You've accessed 1 of your 2 free resources.

Get unlimited access

Discover more content

Vmost analysis.

Ensuring That Organizational Activities Deliver Your Vision of the Future

The CATWOE Checklist

Developing a Robust Problem Definition

Add comment

Comments (0)

Be the first to comment!

Get 30% off your first year of Mind Tools

Great teams begin with empowered leaders. Our tools and resources offer the support to let you flourish into leadership. Join today!

Sign-up to our newsletter

Subscribing to the Mind Tools newsletter will keep you up-to-date with our latest updates and newest resources.

Subscribe now

Business Skills

Personal Development

Leadership and Management

Member Extras

Most Popular

Newest Releases

7 Reasons Why Change Fails

Why Change Can Fail

Mind Tools Store

About Mind Tools Content

Discover something new today

Top tips for tackling problem behavior.

Tips to tackle instances of problem behavior effectively

Defeat Procrastination for Good

Saying "goodbye" to procrastination

How Emotionally Intelligent Are You?

Boosting Your People Skills

Self-Assessment

What's Your Leadership Style?

Learn About the Strengths and Weaknesses of the Way You Like to Lead

Recommended for you

Peter drucker: the coming of the new organization.

We Discuss Drucker's Groundbreaking Ideas and Accurate they have Proven to Be

Business Operations and Process Management

Strategy Tools

Customer Service

Business Ethics and Values

Handling Information and Data

Project Management

Knowledge Management

Self-Development and Goal Setting

Time Management

Presentation Skills

Learning Skills

Career Skills

Communication Skills

Negotiation, Persuasion and Influence

Working With Others

Difficult Conversations

Creativity Tools

Self-Management

Work-Life Balance

Stress Management and Wellbeing

Coaching and Mentoring

Change Management

Team Management

Managing Conflict

Delegation and Empowerment

Performance Management

Leadership Skills

Developing Your Team

Talent Management

Problem Solving

Decision Making

Member Podcast

.css-s5s6ko{margin-right:42px;color:#F5F4F3;}@media (max-width: 1120px){.css-s5s6ko{margin-right:12px;}} AI that works. Coming June 5, Asana redefines work management—again. .css-1ixh9fn{display:inline-block;}@media (max-width: 480px){.css-1ixh9fn{display:block;margin-top:12px;}} .css-1uaoevr-heading-6{font-size:14px;line-height:24px;font-weight:500;-webkit-text-decoration:underline;text-decoration:underline;color:#F5F4F3;}.css-1uaoevr-heading-6:hover{color:#F5F4F3;} .css-ora5nu-heading-6{display:-webkit-box;display:-webkit-flex;display:-ms-flexbox;display:flex;-webkit-align-items:center;-webkit-box-align:center;-ms-flex-align:center;align-items:center;-webkit-box-pack:start;-ms-flex-pack:start;-webkit-justify-content:flex-start;justify-content:flex-start;color:#0D0E10;-webkit-transition:all 0.3s;transition:all 0.3s;position:relative;font-size:16px;line-height:28px;padding:0;font-size:14px;line-height:24px;font-weight:500;-webkit-text-decoration:underline;text-decoration:underline;color:#F5F4F3;}.css-ora5nu-heading-6:hover{border-bottom:0;color:#CD4848;}.css-ora5nu-heading-6:hover path{fill:#CD4848;}.css-ora5nu-heading-6:hover div{border-color:#CD4848;}.css-ora5nu-heading-6:hover div:before{border-left-color:#CD4848;}.css-ora5nu-heading-6:active{border-bottom:0;background-color:#EBE8E8;color:#0D0E10;}.css-ora5nu-heading-6:active path{fill:#0D0E10;}.css-ora5nu-heading-6:active div{border-color:#0D0E10;}.css-ora5nu-heading-6:active div:before{border-left-color:#0D0E10;}.css-ora5nu-heading-6:hover{color:#F5F4F3;} Get early access .css-1k6cidy{width:11px;height:11px;margin-left:8px;}.css-1k6cidy path{fill:currentColor;}

• Product overview
• All features
• App integrations

CAPABILITIES

• project icon Project management
• Project views
• Custom fields
• Status updates
• goal icon Goals and reporting
• Reporting dashboards
• workflow icon Workflows and automation
• portfolio icon Resource management
• Time tracking
• my-task icon Admin and security
• Admin console
• asana-intelligence icon Asana Intelligence
• list icon Personal
• premium icon Starter
• briefcase icon Advanced
• Goal management
• Organizational planning
• Campaign management
• Creative production
• Marketing strategic planning
• Request tracking
• Resource planning
• Project intake
• View all uses arrow-right icon
• Project plans
• Team goals & objectives
• Team continuity
• Meeting agenda
• View all templates arrow-right icon
• Work management resources Discover best practices, watch webinars, get insights
• What's new Learn about the latest and greatest from Asana
• Help Center Get lots of tips, tricks, and advice to get the most from Asana
• Asana Academy Sign up for interactive courses and webinars to learn Asana
• Events Find out about upcoming events near you
• Community programs Connect with and learn from Asana customers around the world
• Support Need help? Contact the Asana support team
• Partners Learn more about our partner programs
• Developers Learn more about building apps on the Asana platform
• Asana for nonprofits Get more information on our nonprofit discount program, and apply.

Featured Reads

• Project management |
• What is 8D? A template for efficient pr ...

What is 8D? A template for efficient problem-solving

How you respond when problems arise is one of the most defining qualities of a manager. Luckily, there are tools you can use to master problem-solving. The 8D method of problem-solving combines teamwork and basic statistics to help you reach a logical solution and prevent new issues from arising.

You’ve spent months overseeing the development of your company's newest project. From initiation, planning, and execution, you’re confident this may be your best work yet.

Until the feedback starts rolling in.

There’s no sugar-coating it—things don’t always go as planned. But production or process issues are hardly a signal to throw in the towel. Instead, focus on honing your problem-solving skills to find a solution that keeps it from happening again. 

The 8D method of problem solving emphasizes the importance of teamwork to not only solve your process woes but prevent new ones from occurring. In this guide, we’ll break down what 8D is, how to use this methodology, and the benefits it can give to you and your team. Plus, get an 8D template to make solving your issue easier. 

What is 8D?

The eight disciplines (8D) method is a problem-solving approach that identifies, corrects, and eliminates recurring problems. By determining the root causes of a problem, managers can use this method to establish a permanent corrective action and prevent recurring issues. 

How do you use the 8D method?

The 8D method is a proven strategy for avoiding long-term damage from recurring problems. If you’re noticing issues in your workflow or processes, then it’s a good time to give this problem-solving method a try. 

To complete an 8D analysis, follow “the eight disciplines” to construct a statistical analysis of the problem and determine the best solution.

The eight disciplines of problem-solving

8D stands for the eight disciplines you will use to establish an 8D report. As you may notice, this outline starts with zero, which makes nine total disciplines. The “zero stage” was developed later as an initial planning stage. 

To illustrate these steps, imagine your organization experienced a decline in team innovation and productivity this past year. Your stakeholders have noticed and want to see changes implemented within the next six months. Below, we’ll use the 8D process to uncover a morale-boosting solution.

D0: Prepare and plan

Before starting the problem-solving process, evaluate the problem you want to solve. Understanding the background of the problem will help you identify the root cause in later steps. 

Collect information about how the problem has affected a process or product and what the most severe consequences may be. Planning can include:

Gathering data

Determining the prerequisites for solving the problem

Collecting feedback from others involved

If we look back at our example, you may want to figure out whether this decline in morale is organization-wide or only applies to a few departments. Consider interviewing a few employees from different departments and levels of management to gain some perspective. Next, determine what knowledge and skills you will need to solve this lapse in productivity. 

D1: Form your team

Create a cross-functional team made up of people who have knowledge of the various products and workflows involved. These team members should have the skills needed to solve the problem and put corrective actions in place. 

Steps in this discipline may include:

Appointing a team leader

Developing and implementing team guidelines

Determining team goals and priorities

Assigning individual roles

Arranging team-building activities

From our example, a solid team would consist of people with first-hand experience with the issues—like representatives from all departments and key people close to workshop-level work. You may also want to pull someone in from your HR department to help design and implement a solution. Most importantly, make sure the people you choose want to be involved and contribute to the solution.

D2: Identify the problem

You may have a good understanding of your problem by now, but this phase aims to break it down into clear and quantifiable terms by identifying the five W’s a and two H’s (5W2H):

Who first reported the problem?

What is the problem about?

When did it occur and how often?

Where did it occur (relating to the sector, supplier, machine, or production line involved)?

Why is solving the problem important?

How was the problem first detected?

How many parts/units/customers are affected?

Use your team’s insights to answer these questions. From our example, your team may conclude that: 

Employees feel overwhelmed with their current workload. 

There is no real structure or opportunity to share new ideas.

Managers have had no training for meetings or innovation settings.

Disgruntled employees know they can achieve more—and want to achieve more—even if they seem disengaged.

Once you answer these questions, record an official problem statement to describe the issue. If possible, include photos, videos, and diagrams to ensure all parties have a clear understanding of the problem. It may also help to create a flowchart of the process that includes various steps related to the problem description.

D3: Develop an interim containment plan

Much like we can expect speedy first aid after an accident, your team should take immediate actions to ensure you contain the problem—especially if the problem is related to customer safety. 

An interim containment plan will provide a temporary solution to isolate the problem from customers and clients while your team works to develop a permanent corrective action. This band-aid will help keep your customers informed and safe—and your reputation intact.

Because your findings revealed workers were overworked and managers lacked training, your team suggests scheduling a few mandatory training sessions for leaders of each department covering time and stress management and combating burnout . You may also want to have a presentation outlining the topics of this training to get key managers and stakeholders interested and primed for positive upcoming changes. 

D4: Verify root causes and escape points

Refer back to your findings and consult with your team about how the problem may have occurred. The root cause analysis involves mapping each potential root cause against the problem statement and its related test data. Make sure to test all potential causes—fuzzy brainstorming and sloppy analyses may cause you to overlook vital information. 

In our example, focus on the “why” portion of the 5W2H. You and your team identify six root causes:

Managers have never had any training

There is a lack of trust and psychological safety

Employees don’t understand the objectives and goals

Communication is poor

Time management is poor

Employees lack confidence

In addition to identifying the root causes, try to pinpoint where you first detected the problem in the process, and why it went unnoticed. This is called the escape point, and there may be more than one. 

D5: Choose permanent corrective actions

Work with your team to determine the most likely solution to remove the root cause of the problem and address the issues with the escape points. Quantitatively confirm that the selected permanent corrective action(s) (PCA) will resolve the problem for the customer. 

Steps to choosing a PCA may include:

Determining if you require further expertise

Ensuring the 5W2Hs are defined correctly

Carrying out a decision analysis and risk assessment

Considering alternative measures

Collecting evidence to prove the PCA will be effective

Your team decides to roll out the training used in the interim plan to all employees, with monthly company-wide workshops on improving well-being. You also plan to implement meetings, innovation sessions, and team-coaching training for managers. Lastly, you suggest adopting software to improve communication and collaboration. 

D6: Implement your corrective actions

Once all parties have agreed on a solution, the next step is to create an action plan to remove the root causes and escape points. Once the solution is in effect, you can remove your interim containment actions.

After seeing success with the training in the interim phase, your stakeholders approve all of your team’s proposed PCAs. Your representative from HR also plans to implement periodic employee wellness checks to track employee morale .

To ensure your corrective action was a success, monitor the results, customer, or employee feedback over a long period of time and take note of any negative effects. Setting up “controls” like employee wellness checks will help you validate whether your solution is working or more needs to be done. 

D7: Take preventive measures

One of the main benefits of using the 8D method is the improved ability to identify necessary systematic changes to prevent future issues from occurring. Look for ways to improve your management systems, operating methods, and procedures to not only eliminate your current problem, but stop similar problems from developing later on.

Based on our example, the training your team suggested is now adopted in the new manager onboarding curriculum. Every manager now has a “meeting system” that all meetings must be guided by, and workloads and projects are managed as a team within your new collaboration software . Innovation is improving, and morale is at an all-time high!

D8: Celebrate with your team

The 8D method of problem-solving is impossible to accomplish without dedicated team members and first-class collaboration. Once notes, lessons, research, and test data are documented and saved, congratulate your teammates on a job well done! Make an effort to recognize each individual for their contribution to uncovering a successful solution.

8D report template and example

Check out our 8D report template below to help you record your findings as you navigate through the eight disciplines of problem solving. This is a formal report that can be used as a means of communication within companies, which makes for transparent problem-solving that you can apply to the entire production or process chain.

Benefits of using the 8D method

The 8D method is one of the most popular problem-solving strategies for good reason. Its strength lies in teamwork and fact-based analyses to create a culture of continuous improvement —making it one of the most effective tools for quality managers. The benefits of using the 8D method include: 

Improved team-oriented problem-solving skills rather than relying on an individual to provide a solution

Increased familiarity with a problem-solving structure

A better understanding of how to use basic statistical tools for problem-solving

Open and honest communication in problem-solving discussions

Prevent future problems from occurring by identifying system weaknesses and solutions

Improved effectiveness and efficiency at problem-solving

Better collaboration = better problem solving

No matter how good a manager you are, production and process issues are inevitable. It’s how you solve them that separates the good from the great. The 8D method of problem solving allows you to not only solve the problem at hand but improve team collaboration, improve processes, and prevent future issues from arising. 

Try Asana’s project management tool to break communication barriers and keep your team on track.

Related resources

3 visual project management layouts (and how to use them)

Grant management: A nonprofit’s guide

Everything you need to know about waterfall project management

Smooth product launches are simpler than you think

Advisory boards aren’t only for executives. Join the LogRocket Content Advisory Board today →

• Product Management
• Solve User-Reported Issues
• Find Issues Faster
• Optimize Conversion and Adoption

An overview of the 8D problem-solving method

The 8D problem-solving method is a powerful tool in product management. It’s designed to help product managers tackle issues systematically and enhance product quality. This method follows eight steps in total, hence the name 8D.

The steps range from identifying problems to implementing long-term solutions. Today you’ll explore how you can effectively apply 8D to your products. You’ll also learn about the benefits of using this approach and analyze some real case studies.

What is 8D?

The 8D problem-solving method is designed to address and resolve problems by identifying, correcting, and eliminating recurring issues.

It involves eight different steps:

• Plan — Prepare for the problem-solving process
• Team selection — Assemble a team with the necessary knowledge and skills
• Problem definition — Clearly define the problem and its impact
• Interim containment action — Implement temporary measures to contain the problem
• Root cause identification — Identify the underlying cause(s) of the problem
• Permanent corrective action — Develop and implement a solution to address the root cause
• Preventive measures — Take steps to prevent the recurrence of the problem
• Team recognition — Acknowledge and reward the team’s efforts in resolving the issue

These steps focus on root cause analysis, preventive measures, and long-term solution implementation. The end goal is to improve product quality and operational efficiency.

The eight disciplines of 8D

The eight disciplines of the 8D method represent a comprehensive approach to solve problems within an organization. Each discipline is designed to guide teams through the process at each stage. Here’s a deeper look into each stage:

This initial step involves preparing for the problem-solving process. The goal here is to understand the problem’s magnitude and set up objectives. It’s about getting ready to tackle the issue systematically.

Team selection

In this step, a cross-functional team is formed. The team should consist of individuals with the necessary knowledge, skills, and experience to address the problem effectively. The team works together throughout the 8D process.

Problem definition

Next, the team has to describe the issue in specific terms. The goal here is to understand the impact and scope of the complication. A well-defined problem is easier to solve.

Interim containment

In the process of finding a solution, temporary measures are taken to contain the problem and prevent it from worsening. This reduces further damage or impact to the involved operations.

Root cause identification

In this phase, the team uses various tools and techniques to identify the underlying cause of the problem. An understanding of the root cause is essential for developing an effective, lasting solution.

Permanent corrective action

With the root cause identified, the team moves to develop a permanent corrective action plan to resolve the issue. Now, the team needs to choose the best solution, implement it, and monitor its effectiveness. This analysis will ensure that the problem is truly resolved.

Over 200k developers and product managers use LogRocket to create better digital experiences

Preventive measures

With such vast processes, there is always a possibility of the problem recurring. To resolve this, the team identifies and implements measures that address the root cause. There might be a need for changes to different aspects of the overall approach.

Team recognition

The final stage focuses on acknowledging and rewarding the team’s efforts. Recognizing the team’s hard work and success in resolving the issue is important for morale. It also promotes a culture of continuous improvement.

By following these eight disciplines, product managers can solve problems more effectively. The other benefit is that it builds a proactive culture that addresses issues before they escalate.

Applying 8D in product management

Applying the 8D problem-solving method in product management involves leveraging its structured approach. This helps you eliminate problems and process improvement initiatives.

Problem identification

The 8D process begins with gathering data and feedback to quickly identify potential issues. After that, a diverse team from various departments works together to uncover issues. And finally, the team solves the problems efficiently.

Once a problem is spotted, quick fixes are applied to limit its impact. Simultaneously, you explore root causes of an issue using methods like the Five Whys . The final step is to implement the solution based on these insights. Occasionally, redesigns or process upgrades are also used to resolve the issue thoroughly.

Elimination

To eliminate recurring problems, it’s crucial to establish preventive measures. Several steps support the main goal of elimination including process adjustments, quality control improvements, and updates to design standards.

The insights gathered from each 8D cycle help with continuous improvement. It also aids in formulating strategies to avert future issues.

Benefits of the 8D method

The main benefit of using the 8D method is its impact on teamwork and continuous improvement. The more obvious benefits focus on root cause analysis and prevention of issues:

• Enhanced quality control
• Efficient problem resolution
• Systematic and thorough approach
• Teamwork and knowledge sharing
• Focus on root cause analysis
• Reduced recurrence of issues
• Cost reduction
• Improved customer satisfaction

The systematic approach to address issues ensures that no effort goes to waste. Eventually, it helps the teams to quickly propose long-term solutions to a range of problem patterns.

Challenges in implementing 8D

The 8D problem-solving method is extremely valuable when used in the right manner. However, there can be challenges at every stage of this process. Because of this, it’s beneficial for you to have an understanding of how to quickly identify these challenges.

These include:

• Resistance to change among team members
• Insufficient teamwork and collaboration
• Lack of training on the 8D methodology
• Difficulties in data collection and analysis

How to solve them?

• Clearly communicate benefits to overcome resistance
• Foster collaboration and teamwork among participants
• Provide targeted training on the 8D process
• Encourage data analysis for effective problem-solving

For a deeper understanding, let’s take a look at two case studies of how the 8D process can enhance the product management workflow.

Real-life examples of 8D

A leading tech company, (similar to Apple) faced public backlash over smartphones overheating and reduced battery life. In this context, the 8D method helped to quickly identify and contain the issues.

The root cause analysis helped it track the problem back to a battery design flaw. Collaborative efforts with the battery supplier led to a redesigned battery and an update to the operating system. This not only resolved the issue but also restored consumer trust. Eventually, the brand’s reputation for quality was restored.

Similarly, a major automaker found a software glitch in its driver-assistance systems. This issue was risking driver safety. Using the 8D method, it pinpointed outdated algorithms as the root cause. The solution was simple, it issued a software update and enhanced its development processes.

Both of these examples are evidence of how the 8D method can be utilized to prevent complications efficiently.

Key takeaways

In wrapping up, it’s clear that this approach is more than just a procedure. Think of it as a strategic framework designed for the product manager. The 8D method equips you with a robust toolkit for addressing and preempting issues, systematically.

On top of that it helps you to:

• Promote teamwork and continuous improvement
• Reduce problem recurrence through root cause analysis
• Overcome implementation challenges with effective communication

Feel free to comment with any questions you may have!

Featured image source: IconScout

LogRocket generates product insights that lead to meaningful action

Get your teams on the same page — try LogRocket today.

Share this:

• Click to share on Twitter (Opens in new window)
• Click to share on Reddit (Opens in new window)
• Click to share on LinkedIn (Opens in new window)
• Click to share on Facebook (Opens in new window)
• #agile and scrum
• #project management

Stop guessing about your digital experience with LogRocket

Recent posts:.

The role of a product owner: Key responsibilities and skills

A product owner sets the direction, keeps the team focused, and ensures that the product becomes a source of value.

Leader Spotlight: Taking a human-centric approach to fintech, with Suhas Reddy

Suhas Reddy discusses the principles of human-centric design and its emphasis on delivering products in the context of the customer.

Leader Spotlight: Focusing on quality and engagement in tech plus services, with Liz Li

Liz Li, CPO of Velocity Global, discusses the importance of meaningful interactions in tech plus services that contribute to company goals.

Brand equity: Building and measuring brand value

By prioritizing brand equity as a key driver of success, you can build enduring relationships with your customers.

Leave a Reply Cancel reply

8D Chess: How to Use The 8 Disciplines for Problem Solving

Hospitals have developed something of a reputation for being rife with bad processes . When processes aren’t adequate, the result is an abundance of “workarounds”.

For example, when equipment or supplies are missing, a nurse might waste time running around searching for what is needed, and once the item is found, return to their previous duties.

One study indicates that nurses spend 33 minutes of a 7.5-hour shift completing workarounds that are not part of their job description.

This may well “put out the fire” so-to-speak, but really it is just a hastily applied band-aid that does nothing to treat the root cause of the problem.

More time is wasted and more problems will arise in the future because nothing has been done to prevent the initial problem from happening again.

Individual nurses are not at fault here; workplace culture often values expertise in the form of those who “get the job done”, which tends to pull against the notion of spending time building good processes (time in which the job is perhaps not “getting done”).

So how to approach the problem of problem solving ?

In a lean context, problem solving can be distilled into two simple questions:

• What is the problem and how did it happen?
• How can we make sure that it doesn’t happen again?

The 8D, or eight disciplines methodology, is a problem solving process – most likely one of the most widely used problem solving processes out there. It is used by many different countries, in many different industries, and many different organizations.

8D is designed to help you put out those fires, and make sure they don’t happen again.

In this article, I’ll introduce you to the 8D problem solving methodology and provide you with an outline of the basic process that you can hopefully apply in your own business, plus how you can enhance 8D with other tools and methodologies like Six Sigma , FMEA , and Process Street .

Here’s what I hope you’ll take away after reading:

• An understanding of the basics of 8D
• Advantages of using 8D
• The purpose and objectives of each phase of the 8D process
• An understanding of how to use 8D for problem solving
• How 8D works with other problem solving tools
• How you can use Process Street to maximize the potential of the 8D framework

Let’s begin with the origins of 8D – what is it, and where did it come from?

What is 8D?

8D (sometimes Global 8D or G8D) stands for eight disciplines, and is a problem solving methodology. It’s basically a process for understanding and preventing problems.

Much like how risk management seeks to take a proactive, preventative stance, 8D aims to gain insight into the root causes of why the problems happen, so they won’t happen again.

The 8D process involves eight (sometimes nine) steps to solve difficult, recurring problems. It’s a transparent, team-based approach that will help you solve more problems in your business.

8D origins: Where did it come from?

Despite the popular story that 8D originated at Ford, it was in fact developed in 1974 by the US Department of Defence, ultimately taking the form of the military standard 1520 Corrective Action and Disposition System for Nonconforming Material .

Ford took this military standard, which was essentially a process for quality management , and expanded on it to include more robust problem solving methods.

In 1987, Ford Motor Company published their manual, Team Oriented Problem Solving (TOPS) , which included their first iteration of the 8D methodology.

Initially termed Global 8D (or G8D) standard, it is currently used by Ford and many other companies in the automotive supply chain.

8D, PDSA, & other problem solving processes

The disciplines of 8D follow the same logic as the Deming Cycle (also known as PDSA, and sometimes PDCA).

PDSA stands for Plan, Do, Study, Act (or Check, in the case of PDCA).

The similarity lies in the fact that both PDSA and 8D are designed to be used to improve processes. They’re both examples of cycles of continuous improvement.

Whereas 8D may be painted as a more generic problem-solving framework, structurally speaking both 8D and PDSA share a lot in common.

The simple idea of beginning with a clear objective, or desired output, and then testing, analyzing , and iteratively tweaking in a continuous cycle is the basis for both methodologies.

There are, of course, differences. We’ll cover the different applications of both 8D and PDSA in this article.

8D advantages

One of the main strengths of 8D is its focus on teamwork. 8D philosophy encourages the idea that teams, as a whole, are more powerful than the sum of the individual qualities of each team member.

It’s also an empirical methodology; that is to say that it is a fact-based problem solving process.

A branch of continuous improvement, proper use of 8D will help you coordinate your entire team for effective problem solving and improved implementation of just about all of the processes used in your business.

The 8 disciplines for problem solving

As you may have noticed, we’re starting with zero, which makes nine total disciplines. This “zero” stage was developed as an initial planning step.

D0: Plan adequately

Make comprehensive plans for solving the problem including any prerequisites you might determine.

Be sure to include emergency response actions.

D1: Establish your team

Establish your core team with relevant product or process knowledge. This team will provide you with the perspective and ideas needed for the problem solving process.

The team should consist of about five people, from various cross-functional departments. All individuals should have relevant process knowledge.

A varied group will offer you a variety of different perspectives from which to observe the problem.

It is advisable to establish team structure, roles, and objectives as far ahead in advance as possible so that corrective action can begin as quickly and effectively as possible.

D2: Describe the problem

Have your team gather information and data related to the problem or symptom. Using clear, quantifiable terms, unpack the problem by asking:

D3: Contain the problem (temporary damage control)

Depending on the circumstances, you may need to mobilize some kind of temporary fix, or “firefighting”.

The focus of this stage should be on preventing the problem from getting worse, until a more permanent solution can be identified and implemented.

D4: Identify, describe, and verify root causes

In preparation for permanent corrective action, you must identify, describe, and verify all possible causes that could contribute to the problem happening.

You can use various techniques for this, including a Failure Modes and Effects Analysis , or Ishikawa (fishbone) diagram .

It’s important that the root causes are systematically identified, described in detail, and promptly verified (or proved). How each cause is verified will depend on the data type and the nature of the problem.

Take a look at the section towards the end of this article for some more problem solving tools to help you decide the right approach.

D5: Identify corrective actions

You must verify that the corrective action you identified will in fact solve the problem and prevent it from happening again in the future (or whatever is your desired threshold of recurrence).

The best way to do this is to collect as much data as possible and by performing smaller-scale “pilot” tests to get an idea of the corrective action’s impact.

You can’t begin to identify the optimal corrective action until you have identified the root cause(s) of the problem.

D6: Implement and validate corrective actions

Carry out the corrective actions, and monitor short and long term effects. During this stage, you should assess and validate the corrective actions with empirical evidence.

Discuss and review results with your team.

D7: Take preventative measures (to avoid the problem happening again)

Here is where you make any necessary changes to your processes, standard operating procedures , policies , and anything else to make sure the problem does not happen again.

It may not be possible to completely eliminate any chance of the problem recurring; in that case, efforts should focus on minimizing possibility of recurrence as much as possible.

D8: Congratulate your team

It’s important to recognize the joint contribution of each and every one of the individuals that were involved in the process.

Team members should feel valued and rewarded for their efforts; this is crucial and perhaps the most important step – after all, without the team, the problem would not have been fixed.

Providing positive feedback and expressing appreciation helps to keep motivation high, which in turn improves the sense of process ownership and simply increases the likelihood your team will actually want to improve internal processes in the future.

How to use 8D for problem solving

The 8D method above outlines a proven strategy for identifying and dealing with problems. It’s an effective problem solving and problem prevention process.

In addition to avoiding long-term damage from recurring problems, 8D also helps to mitigate customer impact as much as possible.

More than just a problem-solving methodology, 8D sits alongside Six Sigma and other lean frameworks and can easily be integrated with them to minimize training and maximize efficacy.

8D is definitely a powerful framework on its own, but it really shines when combined with other synergistic concepts of lean and continuous improvement.

More problem solving tools that synergize well with 8D

8D has become a leading framework for process improvement, and in many ways it is more prescriptive and robust than other more simplistic Six Sigma approaches.

However, there are many Six Sigma methodologies, and even more frameworks for problem solving and process improvement .

The following improvement tools are often used within or alongside the 8D methodology.

DMAIC: Lean Six Sigma

DMAIC stands for:

The DMAIC process is a data-driven cycle of process improvement designed for businesses to help identify flaws or inefficiencies in processes.

Simply put, the goal with DMAIC is to improve and optimize existing processes.

Interestingly, the development of the DMAIC framework is credited to Motorola , whose work built upon the systems initially developed by Toyota .

In terms of working alongside 8D, you could use DMAIC to identify root causes as in D4; you could also implement the same techniques to better understand prospects for corrective actions as in D5, and D6.

We have a whole article on the DMAIC process, if you’re interested.

SWOT analysis

Strengths, Weaknesses, Opportunities, and Threats. You can use a SWOT analysis to gain insight into your organization as a whole, or on individual processes.

The main synergy with 8D is in the identification of opportunities, threats, and weaknesses.

These can represent opportunities for process improvements, weaknesses in your process that could produce problems further down the line, and threats, both internal and external, that may be out of your direct control but that could cause problems for you.

Here’s a SWOT analysis checklist you can use to structure your own analysis:

FMEA: Failure Mode and Effects Analysis

FMEA (Failure Mode and Effects Analysis) is a way of understanding the potential for problems and making preemptive preparations in order to avoid them. It is a method of risk management .

It is a type of preventative risk management process, and so works well in the context of identifying causes of problems so you can better deal with them.

FMEA and 8D work well together because:

• 8D can make use of information gathered during an FMEA process, like brainstorming sessions, to identify potential problems and their root causes.
• You can reuse possible cause information gathered during an FMEA process to feed into different representational diagrams like the Ishikawa (fishbone) diagram, which will help in the 8D process.
• 8D brainstorming data is useful for new process design. This allows the FMEA to take actual process failures into account, which produces more effective results.
• FMEA completed in the past can be used as databases of potential root causes of problems to inform 8D process development.

Here’s a free FMEA template for you to get started ASAP:

The Pareto Chart

The Pareto Chart helps us understand the impact of different variations of input on our output.

In relation to 8D, Pareto Charts can help us prioritize which root cause to target, based on which will have the greatest impact on improvement (where improvement is the desired output of the 8D process).

Here’s the Six Sigma Institute’s example Pareto Chart :

Here we have a simple deductive reasoning technique that asks “why?” five times to dig into the root cause of a problem.

The logic here is that by asking the same question five times, you work progressively “deeper” into the complexity of the problem from a single point of focus.

Ideally, by the fifth question you should have something that has a high likelihood of being a root cause.

This example from Wikipedia does a great job of conveying how the process works:

• The vehicle will not start. (the problem)
• Why? – The battery is dead. (First why)
• Why? – The alternator is not functioning. (Second why)
• Why? – The alternator belt has broken. (Third why)
• Why? – The alternator belt was well beyond its useful service life and not replaced. (Fourth why)
• Why? – The vehicle was not maintained according to the recommended service schedule. (Fifth why, a root cause)

Ishikawa diagrams (fishbone diagrams)

Sometimes called “cause-and-effect diagrams”, they are as such used to visualize the cause and effect of problems.

The approach takes six different categories and places information about the problem into different categories to help you understand what factors could be contributing to the problem.

One advantage over the 5 Whys approach is the way this method forces a more holistic perspective, as opposed to the potentially narrow vantage point offered by zooming in on a single aspect or question.

According to the Six Sigma Institute, the 6 key variables pertaining to root causes of problems are:

• Machine: Root causes related to tools used to execute the process.
• Material: Root causes related to information and forms needed to execute the process.
• Nature: Root causes related to our work environment, market conditions, and regulatory issues.
• Measure: Root causes related to the process measurement.
• Method: Root causes related to procedures, hand-offs, input-output issues.
• People: Root causes related people and organizations.

There’s also this useful illustration of a company using a fishbone diagram to better understand what factors contribute to a company’s high turn around time.

Gap analysis

A gap analysis is concerned with three key elements:

• The current situation, or “performance”
• The ideal situation, or “potential”
• What needs to be done in order to get from performance to potential, or “bridging the gap”

The “gap” is what separates your current situation from your ideal situation.

Businesses that perform a gap analysis can improve their efficiency and better understand how to improve processes and products.

They can help to better optimize how time, money, and human resources are spent in business.

There’s a lot that goes into a gap analysis, and quite a few different ways to approach it. Check out our article for a deeper dive into the gap analysis process.

Superpowered checklists

Checklists can be a great way to simplify a complex process into a series of smaller, easy-to-manage tasks. They’re one of the best ways to start using processes in your business.

By using checklists, you can reduce the amount of error in your workflow , while saving time and money by eliminating confusion and uncertainty.

What’s more, if you’re using Process Street, you have access to advanced features like conditional logic , rich form fields and streamlined template editing .

How to use Process Street for 8D problem solving

Good problem solving relies on good process. If you’re trying to solve problems effectively, the last thing you want is your tools getting in your way.

What you want is a seamless experience from start to finish of the 8D methodology.

The best kinds of processes are actionable. That’s why you should consider using a BPM software like Process Street to streamline recurring tasks and eliminate manual work with automation .

Process Street’s mission statement is to make recurring work fun, fast, and faultless. By breaking down a process into bite-sized tasks , you can get more done and stay on top of your workload.

Sign up today for a free Process Street trial!

Problem solving is an invaluable skill. What’s your go-to process for problem solving? We’d love to know how it compares with the 8D method. Let us know in the comments!

Get our posts & product updates earlier by simply subscribing

Oliver Peterson

Oliver Peterson is a content writer for Process Street with an interest in systems and processes, attempting to use them as tools for taking apart problems and gaining insight into building robust, lasting solutions.

Leave a Reply Cancel reply

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

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

Take control of your workflows today

8D Training

8d training (onsite).

– Training at Your Facility –

⇓   8D Training Course Details

⇓   8D Training Course Description

⇓   8D Training Course Objectives

⇓   8D Training Course Outline

⇓   Learn More About 8D Training

8D Course Details (Onsite)

When you choose onsite Eight Disciplines of Problem Solving (8D) Training, Quality-One brings the knowledge to you, resulting in immediate benefits for your team. The convenience of Onsite Technical Training has made it a popular option for many of our clients who require five or more participants to be trained.  Expenses are minimal compared to having the whole team travel.

8D Course Description (Onsite)

The Quality-One 8D problem solving training course follows the steps of 8D in a dynamic, instructor-led environment. The course describes to participants the methodologies that have proven to be best practices for effective 8D development. Each participant will be able to interact with all of the elements of the 8D process, including the use of tools such as: Ishikawa/ Fishbone, Affinity Diagrams, Is / Is Not, Process Flow and Comparative Analysis. All activities will include industry-specific examples and terminology.

Participants will learn how to follow the 8D process steps while working in a Cross Functional Team (CFT). They will also practice problem solving tools to support a root cause and eliminate it through permanent corrective action. Participants can expect team activities and relevant exercises in a workshop format. The Quality-One 8D training materials and examples also provide an invaluable resource for review time after time.

8D Course Objectives (Onsite)

Participants can expect to learn and develop skills to confidently:

• Perform 8D step by step
• Link 8D to Failure Mode and Effects Analysis (FMEA) , Product Development Process and Advanced Product Quality Planning (APQP)
• Facilitate an effective 8D
• Participate in 8D exercises
• Define root causes and mechanisms of failure
• Set up a Cross Functional Team (CFT)
• Determine effective Interim Containment Action
• Manage and store 8D content (Lessons Learned) for future use
• Ishikawa/Fishbone
• Is / Is Not
• Statistical Process Control (SPC)
• Poka Yoke (Error Proofing)
• Understand links to Control Plan Methodology
• Complete the 8D format correctly

8D Course Outline (Onsite)

Section 1 – 8D Overview

• Team Problem Solving Principles
• Process Description (9 Step Process)
• Team Structure (Cross Functional Team)
• Inductive vs. Deductive Problem Solving
• Change-Induced Problems
• Never-Achieved Problems

Section 2 – Review of Analytical Tools in 8D

• Brainstorming Rules
• Ishikawa / Fishbone
• Affinity Diagram
• Control Chart
• Relationship between 8D and FMEA
• 5 Why (3-Legged Approach)
• Interfaces and Noise Factors
• Error Proofing

Section 3 – 8D Process Step by Step

• Problem Symptom
• Quantified Symptom
• Criteria for 8D Continuance
• Roles and Responsibilities
• Team Preparation
• Agenda and Rules
• Core Team and SMEs
• Repeated Why
• Workshop on Problem Statements and Brainstorming
• Workshop on Problem Description Development
• D3 – Interim Containment Action (ICA)
• Human Factors (Operator Error)
• Comparative Analysis
• Root Cause Theories
• Root Cause Verification
• Escape Point
• Workshop on Root Cause Theories
• Methods for Selecting PCA
• Verification of PCA
• Plan, Do, Study, Act (PDSA) Implementation Plan
• Change Management
• Stakeholders
• Validation Criteria and Sample Size
• Processes and Procedures
• Lessons Learned
• Archive of Documents

8D Training (Offsite)

– Training at Our Facility –

8D Course Details (Offsite)

8D Training in a Quality-One Technical Training Center provides participants with a learning environment that is free from interruption from daily activities. This type of course is recommended for individuals or organizations with less than 5 people who require training. Our offsite Eight Disciplines of Problem Solving (8D) Training activities are developed around principles that all participants can relate to. Offsite training also allows participants from different backgrounds and industries to share their viewpoints and experiences. This discussion often helps participants from one industry take advantage of best practices that are used in another.

8D Course Description (Offsite)

This engaging, instructor-led 8D problem solving training course takes participants through each step of the 8D problem solving process. The course offers each participant the knowledge of methodologies which have proven to be the best practices for 8D development. Each participant will be able to interact with all of the elements of the 8D process, including the use of tools such as: Ishikawa / Fishbone, Affinity Diagrams, Is / Is Not, Process Flow and Comparative Analysis.

Participants will learn how to follow the 8D process steps while working in a Cross Functional Team (CFT). They will also practice problem solving tools to support a root cause and eliminate it through permanent corrective action. Participants can expect team activities and relevant exercises in a workshop format. The Quality-One reference materials and examples also provide an invaluable resource for review time after time.

8D Course Objectives (Offsite)

8d course outline (offsite).

• Ishakawa / Fishbone
• 5 Why (3-Legged 5 Why Approach)
• D0 – Prepare (Plan) for the 8D

8D Training (Online)

– Technical Training Overview –

8D Course Details (Online)

The Quality-One Online Eight Disciplines of Problem Solving (8D) Training Overview is an excellent introduction to the 8D methodology. The course is completely interactive, featuring audio, video, animation and downloadable reference materials. Online training gives you immediate access to 8D process content and is available 24 hours a day.

8D Course Description (Online)

Quality-One Online 8D Training Overview introduces participants to the basic principles of 8D, including each step required in the 8D format. Participants will also be able to understand the sequence of the 8D process and receive guidance on what tools are involved with each step. This course follows a structured approach for defining problems and identifying root causes. The participant will have 30 days to complete this course and can access it at any time.

8D Course Objectives (Online)

Upon completion of this overview, the participant will acquire the knowledge to:

• Understand the 8D process and describe each step
• Describe the tools and methods used in support of 8D
• Explain how 8D teams are structured
• Identify Symptoms, Problem Statements, Problem Descriptions, Possible Causes, Most Likely Causes and Root Causes
• Describe Interim Containment and Permanent Corrective Actions
• Explain how Preventative Analysis benefits organizations
• Explain verification vs. validation during problem solving
• Explain how the escape points link to control plans

8D Course Outline (Online)

• Change Induced Problems
• Never Achieved Problems
• Ishakawa Fishbone
• 5 Why (3-legged Approach)
• D3 – Interim Containment Action
• Root Cause theories
• PDSA Implementation Plan
• D8 – Closure and Congratulate the Team

Learn More About 8D Training

Quality-One offers Quality and Reliability Support for Product and Process Development through Consulting, Training and Project Support. Quality-One provides Knowledge, Guidance and Direction in Quality and Reliability activities, tailored to your unique wants, needs and desires. Let us help you Discover the Value of 8D Consulting , 8D Training or 8D Project Support .

Contact Us | Discover the Value!

(248) 280-4800 | [email protected]

Remember Me

• Don't have an account? Register
• Lost your password? Click here
• Already have an account? Log in

Project Review Insights

Empowering Management Excellence

The harder you work for something, the greater you'll feel when you achieve it.

Guide to Problem-Solving Methodologies: 8D, PDCA, DMAIC, and Kaizen

Welcome 2024! Embracing and mastering problem-solving methodologies is essential for organizations on their continuous improvement journey throughout the year. By learning these techniques, teams can streamline and enhance their problem-solving processes, fostering a culture of innovation and resilience in the face of challenges.

This proactive approach will empower organizations to navigate uncertainties, drive efficiency, and achieve sustainable growth in the dynamic landscape of 2024 and beyond.

This article explores four widely adopted methodologies: 8D (Eight Disciplines), PDCA (Plan-Do-Check-Act), DMAIC (Define-Measure-Analyze-Improve-Control) , and Kaizen .

Each methodology brings a unique approach to problem-solving, tailored to different contexts and challenges.

Problem-Solving Methodologies

1. 8d (eight disciplines).

The 8D problem-solving methodology is structured into eight steps, providing a systematic approach to identifying, solving, and preventing problems.

The steps include:

• D1: Form a Team
• D2: Define the Problem
• D3: Develop Interim Containment Actions
• D4: Identify the Root Cause
• D5: Choose Permanent Corrective Actions
• D6: Implement Corrective Actions
• D7: Prevent Recurrence
• D8: Congratulate the Team

8D emphasizes teamwork, data-driven analysis, and a focus on both short-term containment and long-term solutions. It encourages a thorough investigation into the root cause to prevent recurrence.

2. PDCA (Plan-Do-Check-Act)

PDCA, also known as the Deming Cycle, is a continuous improvement method popularized by W. Edwards Deming.

The PDCA cycle comprises four stages:

• Plan : Identify the problem and plan for change
• Do : Execute the plan on a small scale
• Check : Analyze the results and compare against the expected outcomes
• Act : Implement necessary changes on a larger scale and standardize improvements

PDCA is iterative, promoting a constant feedback loop for ongoing improvement. It is versatile and applicable across various industries and processes.

3. DMAIC (Define-Measure-Analyze-Improve-Control)

DMAIC is a core component of the Six Sigma methodology, designed to improve processes by eliminating defects. The five stages of DMAIC are:

• Define : Clearly articulate the problem, project goals, and customer requirements
• Measure : Collect relevant data to understand the current state of the process
• Analyze : Identify root causes of problems through data analysis
• Improve : Develop and implement solutions to address the root causes
• Control : Sustain the improvements and monitor the process to prevent regression

DMAIC emphasizes data-driven decision-making and statistical analysis to achieve measurable and sustainable improvements.

Kaizen , a Japanese term meaning “continuous improvement,” is a philosophy that promotes incremental, continuous changes.

Key principles of Kaizen include:

• Standardize processes
• Practice 5S (Sort, Set in order, Shine, Standardize, Sustain)
• Empower employees to suggest and implement improvements
• Focus on small, manageable changes

Kaizen fosters a culture of continuous improvement at all organizational levels, encouraging employees to contribute to the evolution of processes and systems.

Related Article: Understanding the 5S Methodology: Streamlining Success in Workspaces

Choosing the Right Tool or the Right Problem-Solving Methodologies

While each methodology offers a unique approach, the most effective one depends on the specific context:

• 8D:  Ideal for complex problems, customer complaints, and team-based problem-solving.
• PDCA:  Suitable for quick improvements, testing new ideas, and cyclical progress.
• DMAIC:  Effective for data-driven, statistically controlled process optimization and defect reduction.
• Kaizen:  Perfect for fostering a culture of continuous improvement, small incremental changes, and employee engagement.

Final Thoughts

Effective problem-solving is essential for organizational success and continuous improvement. The 8D , PDCA, DMAIC , and Kaizen methodologies offer distinct approaches, allowing organizations to choose the one that aligns best with their goals and context.

By incorporating these methodologies, businesses can enhance their problem-solving capabilities, driving efficiency, quality, and overall success.

As the New Year begins, I wish you all lots of happiness and good luck in your projects!

Join our vibrant community of enlightened readers! Elevate your knowledge with exclusive updates and insights by subscribing today!

A heartfelt thank you for investing your time in reading this article. For a deeper dive into Project and Operations Management, along with best practices, delve into more of my articles at www.projinsights.com .

Your thoughts and feedback are invaluable to us. Reach out to us at [email protected] ; we cherish every comment.

If you’ve found value in my content and feel like supporting, why not treat me to a coffee ?

And here’s an invitation: Subscribe to experience daily blog posts. Don’t keep this treasure to yourself—share it with your family and friends. Thank you!

Subscribe Our Free Newsletter

Are you a ComplianceQuest Customer?

8D Management (8 Disciplines Management)

8D Management & The 8D of Problem Solving

Problems are a part of life and a business is no exception. Even with the best of intentions and systems, some errors can creep in and be hard to detect. It may be nothing serious or can have serious repercussions such as reputation damage, heavy fines, product recall, property loss, and so on. It becomes essential to identify the problem, its consequences on the one hand, and causes on the other to be able to not only resolve it for now but also ensure prevention of its recurrence. One of the methodologies, popular amongst engineers and professionals mainly in the automotive industry but now applied across several industries is the eight disciplines (8D) model. It helps to identify, correct, and eliminate recurring problems, affecting improvement in product and process.

Related Assets

Key Highlights: 8D is an extremely effective, proven problem-solving framework, especially in the manufacturing and automotive sector. However, to truly…

What is Quality 4.0? Is it a buzzword for defining the next generation of quality management systems? Does it refer…

Unless you live in an alternate universe, as a business leader you are bound to encounter problems, issues, or challenges.…

What are the Eight Disciplines of Problem Solving (8D)?

The Eight Disciplines of Problem Solving (8D) is a systematic, holistic and proven methodology designed to identify the root cause of a problem, plan a quick fix, and implement corrective actions and preventive actions to avoid their recurrence. If your product is defective or not meeting your customer requirements, then 8D is an excellent first step to improve Quality and Reliability.

8D has become very popular among manufacturers, assembly, and services around the globe because it is effective and comparatively easy to teach.

Why Apply Eight Disciplines of Problem Solving (8D)

The 8D methodology, developed to represent the best practices in problem-solving, provides the engineering teams with an effective and efficient team-oriented problem-solving skill, a better understanding of Root Cause Analysis (RCA) and how to use basic statistical tools required for problem-solving. 8D helps the management understand and resolve problems better, identify necessary systemic changes and inputs for change , and facilitate a more candid and open communication in problem-solving discussions.

8D improves the Quality and Reliability of your products, and if performed correctly, prepares the engineering team for future problems.

When to Apply Eight Disciplines of Problem Solving (8D)

The 8D problem-solving process is used to solve major, critical, chronic, and recurring problems. The 8D is typically required during safety or regulatory issues, customer complaints , warranty concerns, poor performance or test failures, internal rejects, and to minimize waste and scrap.

How to Use Root Cause Analysis to Transform Your Safety Program

How to apply eight disciplines of problem solving (8d).

The 8D is a systematic process for the introduction and improvement of quality, and elimination of problems. Here we will show you the step by step approach of the problem-solving tools that can make you proficient at identifying causes of problems, defining problems, and errors. Additionally, it helps identify root causes and take actions to solve and prevent identified problems in processes. So, let’s take a peep inside:

D0: Planning and preparing for the 8D

Proper planning and preparation are always a good start before taking any action. So, you need to consider the following before forming a team:

• Problem description
• Timeframe for the resolution
• The number of resources to accomplish this

D1: Team establishment

Create a team with people who varied backgrounds and experiences which will lead to the best quality inputs and a complete solution. For the team to function smoothly, define clear roles, and responsibilities for your people, and have a team leader.

D2: Problem description

The 8D method’s primary focus is to describe the problem appropriately and objectively such that it captures all the vital information. During this analysis, repeated 5W1H (why, what, who, where, when, and how) are required to be asked to develop a clear description.

D3: Problem containment plan

A temporary problem containment plan is sometimes needed to minimize the impact of the problem until you develop permanent solutions. On developing the plan based on the hypothetical cases, the resources for addressing the main problem can be released. At times, new processes may be required to work around the problem until you have a permanent fix.

D4: Root Cause Analysis (RCA)

With the problem temporarily contained, you can now turn to identify all of the root causes of the nonconformance . There are several tools to identify the actual root cause of an issue including the 5W1H to understand the problem in-depth, Fishbone diagrams to visually categorize causes, and Pareto charts to identify the vital causes.

D5: Permanent Corrective Action

Once the root cause of the problem is determined, the team can start brainstorming permanent corrections to identify what the best long-term solution will be. Brainstorming sessions combined with tools such as affinity diagrams help organize ideas based on their relationships and determine the best course of action.

D6: Implement and Validate the Permanent Corrective Action

Once the solution is identified, the management needs to implement and verify the corrective action using the PDCA (plan-do-check-act) approach for small-scale testing before large-scale rollout. Thus, the outcomes and corrective actions are tracked to ensure expected results. To successfully implement a permanent change, a project plan should incorporate:

• Development of the project plan for implementation
• Communicating the plan to all stakeholders
• Validating improvements using measurement

D7: Prevent Recurrence

A complete solution of problems means preventing them from occurring. Besides, preventative measures should also be implemented for corrective actions in the 8D methodology. This requires reviewing management processes, operating procedures, and training manuals to ensure that best practices are followed.

At this stage, organizations should consider actions including updating process audit questions and regularly verifying them based on corrective actions to reduce risk in other processes, presenting poka-yoke or error-proofing devices to big-risk processes, and conducting red rabbit tests to see how long it takes poka-yoke devices to detect defective product.

D8: Verification and Team Celebration

Once the problem is solved, the ultimate step is to congratulate the team. It’s important to recognize their efforts and share their success across the organization because teams require feedback to allow for satisfactory closure. This facilitates motivation and employee engagement while helping you improve quality control, execute process improvements, and aid change management as you grow.

Create a team with people who are having varied backgrounds and experiences which will lead to the best quality inputs and a complete solution. For the team to function smoothly, define clear roles, and responsibilities for your people, and have a team leader.

A complete solution of problems means preventing them from occurring initially. Besides, preventative measures should also be implemented for corrective actions in the 8D methodology. This requires reviewing management processes, operating procedures, and training manuals to ensure that best practices are followed.

8D and Root Cause Analysis (RCA)

Root Cause Analysis (RCA) is embedded within the 8D process and includes the following steps and techniques:

Problem Symptom is measured and transformed to “Object and Defect”

Problem Symptom is reformed to Problem Statement using the 5W1H process

Potential Causes are gathered using the tools like Fishbone or Affinity Diagram

Problem Statement should fit using both the “is” and the “isn’t” sections of the question

Root Cause concepts are developed from remaining possible causes on the tool and related changes from is/is not

Compare theories with recent data and develop experiments for Root Cause Verification

Test and confirm the Root Causes

Customer Success

3 Women Leaders Making a Powerful Impact in Global Quality and Safety Management

How to use the 8d approach.

8D portrays 8 steps of a structured approach to solve difficult, recurring, or critical problems by providing transparency, driving a team approach, and increasing the chances of solving the problem.

Proper plan for solving the problem and identify the prerequisites.

Team creation

Gather a cross-functional team with product/process knowledge.

Problem description and definition

Use the data and information to specify the problem by identifying in quantifiable terms the who, what, where, when, why, how, and how many (the 5W1H) for the problem.

Problem Containment Plan development

Develop and implement interim actions to eliminate the problem from any customer in the future.

Specify and assess Root Causes

Identify and review all relevant causes and sources of variation that analyze why the problem has occurred and figure out why the problem was not noticed at first using 5W1H or diagrams.

Verify Permanent Solutions

After collecting data confirm that the possible solutions will actually resolve the problem.

Implement and Validate Corrective Actions

Discuss and review results and develop plans to implement the best solutions or countermeasures.

Preventive measures

Transform the operation systems, management systems, procedures, and practices to avoid the recurrence of similar problems.

Compliment your team

Recognize the collective efforts of your team and formally thank them for their involvement.

Great product, support, and people to work with!

We have rolled-out CQ across our company to automate various elements of QMS requirements such as Document Management, Complaints, Non-conformances, Corrective Action (8D and A3), Supplier Management and Audit Management. We have been using the software for more than 2 years. We are glad to see how well the system is being used across the company. We have several thousand users on the system currently and working to scale the usage further. CQ solution has been configured to meet our needs, works elegantly across languages, across time zones, and business verticals. With integration between CQ and SAP to exchange critical data, the process automation provides a lot of productivity.

CQ configuration team and support have worked hard to ensure that our needs continue to be met. They consistently go above and beyond. We cannot be more pleased with our use of CQ QMS capabilities and would definitely recommend to anyone who is looking for a modern cloud based EQMS solution especially if you want a scalable EQMS solution.

Lia Budiman, Continental Contitech

8D Problem-Solving Report

8D problem-solving reports and templates are useful tools to initiate a problem-solving process. These reports are used to explain what 8D is and including information about each step so that one will know what needs to be done by attempting this to solve problems. Keeping these reports easily available can avoid repeating work on the same problems over and over again.

8D reports must be detailed and incorporate information at every step within the 8D process. Those who are working on the problem should provide sufficient information when completing a report so that someone who was not on the current 8D team can pull it out and understand what the problem was and what solutions were implemented.

Who Can 8D Help?

The 8D methodology is universally applicable for every organization that needs solving. Although, there are a few industries and sectors where this 8D approach is successfully used such as manufacturing, the automotive idustry, engineering companies that manufacture products or parts, and medium and large-scale enterprises.

Improve quality, eliminate problems and identify the root cause of a problem with 8d Methodology

Related checklists.

Quality Assurance Checklist – Part A (Project Management)

Checklist | September 7th, 2022

Quality Assurance Checklist – Part B (Project Deliverables)

Quality Control Area Safety Audit Checklist for Pharmaceutical Companies

Checklist | April 22nd, 2022

Quality-centric Companies Rely on CQ QMS

Frequently Asked Questions

The 8D methodology is often used since it provides a consistent, simple, and thorough approach to solving raised problems at various stages. If properly applied, it gives several advantages such as:

A systematic approach for improving team-oriented problem-solving skills

A clear understanding of basic statistical tools needed for problem-solving

A practical understanding of the ‘ root cause analysis’ tool

Creating and expanding relative information about past failures and lessons learned to avoid future problems in the organization

Improving skills for corrective action deployment

When the team is trying to find the root cause of the problem and deploy corrective actions, some defective products will continue to be manufactured. To prevent these defective parts from reaching the customer, interim containment ensures that the defects are contained in the facility till the problem is completely solved. If defective parts reach the customer, it may result in warranty claims, field failures, and customer complaints.

To implement the 8D process successfully, the following factors are crucial:

The right team

An accurate description of the problem

Avoiding skipping through steps

Ensuring cooperation within the team and management support

Understanding the difference between real causes and possible causes

Related Insights

Cost of Quality: Finding the Sweet Spot Between Expense and Excellence

Every company has a key responsibility to take into account the cost of achieving quality, since their goal is to satisfy…

Countdown Begins: Preparing for FDA’s Amended Quality Management System Regulations (QMSR) Final Rule

On January 31, 2024, the US Food and Drug Administration…

PPAP Management: Streamline Your Product Approval Process Digitally

Optimize and manage your PPAP process with the innovative features…

‘Quality Touches Everything’ Series: Infuse Quality into Your Product Lifecycle

In a recent engagement with a medical device company known…

Connect with a CQ Expert

Learn about all features of our Product, Quality, Safety, and Supplier suites. Please fill the form below to access our comprehensive demo video.

Please confirm your details

By submitting this form you agree that we can store and process your personal data as per our Privacy Statement. We will never sell your personal information to any third party.

In Need of Smarter Ways Forward? Get in Touch.

Got questions we can help.

Chat with a CQ expert, we will answer all your questions.

The Evolution of 8D Problem-Solving: From Basics to Excellence

• Learn Lean Sigma
• 8D Problem Solving

In a world where efficiency and effectiveness are more than just buzzwords, the need for robust problem-solving methodologies is greater than ever. Among the myriad of approaches that organizations adopt to tackle challenges, the 8D Problem-Solving framework stands as a testament to both versatility and efficacy. Originating from military standards and later popularized by the automotive industry, 8D has evolved to become a universal tool for identifying issues, analyzing root causes, and implementing sustainable solutions.

This blog post aims to guide you through the captivating history and evolution of the 8D Problem-Solving approach. From its early days as a checklist in quality management to its modern adaptation using advanced statistical tools and cross-industry applications, we’ll explore how 8D has transformed into a comprehensive, adaptable, and highly effective method for tackling problems in various sectors. Whether you’re new to 8D or looking to deepen your understanding, this article offers valuable insights into its development and current applications.

Table of Contents

The genesis: where it all began, the military origins.

The very first seeds of the 8D Problem-Solving methodology were sown during World War II. It was incorporated into Military Standard 1520, a framework aimed at addressing product and service failures. At the time, the military faced complex challenges that often involved multiple variables and high stakes. These challenges required a disciplined approach to problem-solving that could help identify and eliminate the root causes of failures.

Limited Initial Reach

Despite its structured approach, the method had limited reach and was not extensively used outside military applications. This was primarily due to two reasons:

• Specificity : The original framework was tailored for military applications, which made it less relatable to civilian industries.
• Complexity : The depth of the method often required specialized training, which acted as a barrier for broader adoption.

The Automotive Revolution: Ford Takes the Wheel

Fast forward to the 1980s, and the landscape of quality management began to change. Companies were increasingly focusing on systematic approaches to problem-solving and continuous improvement. It was during this era that the 8D Problem-Solving approach got a second life through its adoption by the Ford Motor Company.

Ford was facing growing competition and realized the need for a structured, repeatable problem-solving methodology. The 8D framework fit the bill perfectly, as it provided a step-by-step approach to identify issues, analyze their root causes, and implement corrective measures.

Standardization and Beyond

Once Ford demonstrated the success of implementing the 8D methodology, it became part of the larger Quality Management Systems. Organizations began to see the value in a disciplined approach to problem-solving, and thus, 8D started its journey towards standardization and broader industrial application.

By embracing quality management principles like ISO 9001, the 8D approach transformed from a ‘military-specific’ solution to a universally applicable method for problem-solving. This was a pivotal moment in its history, paving the way for the methodology’s future evolutions and its adoption across diverse sectors.

The origin story of 8D Problem-Solving is a compelling tale of adaptation and evolution. From its military roots to its mainstream industrial applications, the methodology has proven its mettle in solving complex problems methodically and effectively.

The 8 Disciplines: A Quick Overview

Understanding the 8 Disciplines that make up the 8D Problem-Solving approach is crucial for comprehending its comprehensive nature. For a comprehensive guide on how to navigate each of the eight disciplines, you can visit Learn Lean Sigma’s 8D Problem Solving Guide .

Here’s a brief rundown:

This is the preparatory stage where you outline the scope of the problem and plan the resources required for the problem-solving process.

D1: Team Formation

A cross-functional team is assembled with individuals who have the skills and knowledge needed to solve the problem effectively.

D2: Problem Description

The issue at hand is clearly defined, often using tools like the 5W2H (Who, What, When, Where, Why, How, How much) to ensure everyone understands it.

D3: Interim Containment Actions

Temporary actions are taken to contain the problem and prevent it from causing immediate harm while the root cause is being investigated.

D4: Root Cause Analysis

Through data collection and analysis, the underlying cause of the problem is identified. Methods like the Fishbone Diagram or 5 Whys are commonly used.

D5: Permanent Corrective Actions

Once the root cause is known, permanent solutions are developed and tested to ensure they effectively solve the problem.

D6: Implement and Validate Solutions

The validated solutions are fully implemented. Metrics are set up to monitor the effectiveness of the solutions over time.

D7: Preventive Measures

Actions are taken to prevent the recurrence of the problem in the future. This often involves updating procedures or training.

D8: Closure and Team Celebrations

The project is formally closed, and the team’s efforts are recognized and celebrated, often leading to increased motivation for future projects.

These eight disciplines provide a structured, step-by-step approach to problem-solving, ensuring that issues are not just solved but also prevented from recurring.

Would you like to know how each of these disciplines integrates with modern tools and methodologies like Lean Six Sigma? Stay tuned for more in-depth articles on this topic.

The Evolutionary Milestones of 8D Problem-Solving

1. initial adoption and standardization, the checklist era.

In its formative years, the 8D methodology was primarily a checklist approach to problem-solving. Organizations used it as a guide to ensure that they didn’t miss critical steps in the problem-solving process. While effective, it lacked the rigor and structure to be universally adopted as a standard.

Integration into Quality Management Systems

The game-changer came when 8D was integrated into Quality Management Systems like ISO 9001. This move provided the methodology with the structure and standardization it needed to be widely accepted. It moved from being a simple checklist to a deeply structured, documented process that required evidence-based actions at every stage.

2. Cross-Industry Application

Breaking industry barriers.

By the late 1990s and early 2000s, the 8D methodology began to show its versatility. What started in the automotive and military sectors soon found applications in healthcare, FMCG, logistics, and even software development.

Universal Principles

The universality of its principles meant that it could provide a structured way to approach problem-solving in different settings. The discipline it instilled in the process made it a favorite across industries, proving that good problem-solving techniques are not confined by industry boundaries.

3. Integration with Other Methodologies

The synergistic approach.

In more recent years, 8D has been combined with other methodologies like Six Sigma, Kaizen, and Lean. This integration has made the process far more robust, marrying the structured approach of 8D with the data-driven and continuous improvement aspects of these methodologies.

Enhanced Problem-Solving

For instance, integrating Six Sigma techniques into the Root Cause Analysis stage (D4) has allowed for a more sophisticated and accurate identification of root causes, making the solutions more effective and sustainable.

4. Technological Enhancements

The data revolution.

The advent of advanced statistical tools and software has significantly impacted the 8D methodology. Data analytics platforms and specialized software have made the data analysis phase far more sophisticated, improving the accuracy and efficiency of the entire process.

5. Adaptation for Smaller Issues

Quick 8d and micro 8d.

Recognizing that not every problem requires a full-blown 8D approach, the methodology has been adapted into “Quick 8D” or “Micro 8D” versions. These are less resource-intensive and can be implemented much quicker, making 8D accessible for smaller issues without sacrificing the integrity of the problem-solving process.

The 8D Problem-Solving methodology has shown remarkable adaptability and resilience, evolving over the years to meet the demands of a rapidly changing industrial landscape. Each evolutionary milestone has added layers of effectiveness, making it a reliable choice for organizations aiming for excellence in problem-solving.

Modern-Day Applications and Case Studies of 8D Problem-Solving

The 8D Problem-Solving methodology has come a long way from its military and automotive roots. Today, it has been adopted by a variety of industries and sectors, demonstrating its versatility and effectiveness in solving a wide range of problems. Below are some noteworthy applications and case studies.

Service Industries

Hospitality sector.

In the hospitality sector, 8D has been employed to improve customer satisfaction and operational efficiency. For example, a hotel chain used 8D to identify the root cause of frequent customer complaints about room cleanliness, eventually implementing new training programs for housekeeping staff.

Hospital Operations

Hospitals have applied 8D to solve problems related to patient safety, medical errors, and operational bottlenecks. One case study from a leading hospital showcased how 8D helped reduce the time required for the emergency room triage process, thus saving lives.

Software Development

Debugging and quality assurance.

In software development, 8D has found a place in debugging and quality assurance phases. It helps teams systematically identify, analyze, and resolve software bugs, leading to more reliable products.

Manufacturing Giants and Their Case Studies

General electric.

GE used the 8D methodology to improve the reliability of their turbine engines. After identifying the root cause of frequent failures, they implemented corrective actions that increased the lifespan of the engines, saving both time and resources.

Toyota, a name synonymous with quality and efficiency, has frequently turned to 8D for solving complex engineering and manufacturing challenges. One documented case study revealed how Toyota used 8D to reduce the defect rate in one of its assembly lines, thus improving productivity and quality.

In the consumer electronics industry, Samsung employed 8D to tackle the battery issues plaguing its Galaxy Note series. By systematically identifying the root cause, Samsung was able to implement corrective actions that restored consumer trust in their products.

The wide-ranging applications of 8D in various industries underscore its flexibility and robustness as a problem-solving methodology. These case studies are not just isolated examples; they are a testament to the adaptability and efficacy of the 8D approach in solving real-world problems.

The 8D Problem-Solving methodology has undergone a remarkable journey, evolving from its origins in military applications to becoming a universally adopted framework across a spectrum of industries. Its structured, step-by-step approach not only solves immediate issues but also lays down preventive measures to avoid future occurrences. This adaptability is evidenced by its successful implementation in sectors as diverse as healthcare, software development, and manufacturing.

Companies like General Electric, Toyota, and Samsung have leveraged 8D to drive impactful changes, highlighting the methodology’s potential for fostering organizational excellence. As we move forward in an increasingly complex and dynamic world, the 8D approach will undoubtedly continue to be a cornerstone for effective problem-solving and continuous improvement.

• Zarghami, A. and Benbow, D.W., 2017.  Introduction to 8D problem solving . Quality Press.
• Camarillo, A., Ríos, J. and Althoff, K.D., 2017.  CBR and PLM applied to diagnosis and technical support during problem solving in the Continuous Improvement Process of manufacturing plants .  Procedia Manufacturing ,  13 , pp.987-994.

Daniel Croft

Daniel Croft is a seasoned continuous improvement manager with a Black Belt in Lean Six Sigma. With over 10 years of real-world application experience across diverse sectors, Daniel has a passion for optimizing processes and fostering a culture of efficiency. He's not just a practitioner but also an avid learner, constantly seeking to expand his knowledge. Outside of his professional life, Daniel has a keen Investing, statistics and knowledge-sharing, which led him to create the website learnleansigma.com, a platform dedicated to Lean Six Sigma and process improvement insights.

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.

5S Floor Marking Best Practices

In lean manufacturing, the 5S System is a foundational tool, involving the steps: Sort, Set…

How to Measure the ROI of Continuous Improvement Initiatives

When it comes to business, knowing the value you’re getting for your money is crucial,…

8D Problem-Solving: Common Mistakes to Avoid

In today’s competitive business landscape, effective problem-solving is the cornerstone of organizational success. The 8D…

In a world where efficiency and effectiveness are more than just buzzwords, the need for…

8D: Tools and Techniques

Are you grappling with recurring problems in your organization and searching for a structured way…

How to Select the Right Lean Six Sigma Projects: A Comprehensive Guide

Going on a Lean Six Sigma journey is an invigorating experience filled with opportunities for…

8D Methodology

In this topic, 8d internal report, 8d customer report, 8d action items, d0: prepare, d1: gather the team, d2: describe the problem, d3: implement interim containment, d4: identify and verify root cause, d5: define and verify corrective action, d6: implement and validate corrective action, d7: prevent recurrence, d8: celebrate team success.

• Who and what does the problem affect?
• What is the root cause of the problem?
• What temporary containment actions can we take to protect the customer?
• What permanent corrective actions can we take to prevent similar problems in the future?
• D0: Prepare : Gather data and collect feedback to determine if 8D is the right methodology to solve the problem.
• D1: Gather the Team : Establish a cross-functional team that has the right level of skills, competencies, and technical expertise to address the problem.
• D2: Describe the Problem : Define the problem in quantifiable terms and focus on the symptoms, its impact on the customer, when and where it occurred, and any other relevant details. Use evidence to support your claims.
• D3: Implement Interim Containment : Identify, evaluate, and implement immediate actions to contain the problem to keep customers informed and protected.
• D4: Identify and Verify Root Cause : Use various problem-solving tools and techniques to identify and analyze the underlying cause of the problem.
• D5: Define and Verify Corrective Action : Develop and implement corrective actions to eliminate the source of the problem and prevent it from recurring.
• D6: Implement and Validate Corrective Action : Test and monitor the corrective actions to verify that the problem does not exist anymore.
• D7: Prevent Recurrence : Develop long-term actions, such as process changes, monitoring, and training to ensure that the problem does not recur.
• D8: Celebrate Team Success : Recognize the team as well as individual contributions and document lessons learned for future projects.
• What are the key details from each phase?
• What actions did the team take at each phase?

The data in this form is shared with the 8D phase forms. Any data you enter in this form automatically populates the forms that share this data and vice versa. At the end of the project, the 8D Internal Report will be complete and serve as a summary of the project for the team.

• Initially, enter as many details about the project as possible.
• If necessary, edit the form.
• What is the customer's claim?
• What evidence supports the claim?
• What corrective actions did you take to resolve the problem?

The data in this form is shared with the 8D phase forms. Any data you enter in this form automatically populates other forms that share this data and vice versa. At the end of the project, this form will be complete and ready to share with the customer.

• After gathering initial information about the problem, enter details about the customer's claim.
• Summarize the root cause of the problem and any evidence to support the customer's claim.
• Summarize the corrective action plan.
• After your organization implements the corrective action plan, update this form to include evidence of the improvement.
• Provide the customer with a copy of this report.
• What actions did the team take at every phase of the project?
• Who was responsible for each action?
• What is the status of each action?
• Throughout the project, add any new action items that occur as you move through each phase of the 8D methodology.
• Monitor and update the status of each item.
• Refer to this form as a historical record of the steps you took to address the problem and prevent it from happening in the future.
• Is the 8D methodology the appropriate approach to this problem?
• What resources are required to solve the problem?
• Is an emergency response necessary?
• Determine if the 8D methodology is appropriate, then justify your decision to proceed.
• Document the tracking data for the project, including start and end dates, the customer claim, and any affected parts.
• Determine the time and effort required to complete the project.
• Identify the necessary technical skills and competencies of the people required to solve the problem.
• Use a Risk Matrix to determine if an Emergency Response action plan is necessary, and if so, describe the plan. For more information, go to Risk Matrix .
• Who are the team members?
• Are all team members qualified and available?
• Who will be responsible for leading the project?
• After you determine if 8D is appropriate, determine who has the skills, experience, availability, and authority to be an effective team member.
• (Optional) Use the RACI (Responsibility Assignment Matrix) form to identify the team members and clarify their roles on the team. For more information, go to RACI (Responsibility Assignment Matrix) .
• Identify the project leader and champion.
• Add all team members and their contact information to the table.
• What is the problem?
• How does the problem impact the customer?
• What quantifiable evidence of the problem do we have?

Use the CATWOE and the Is Is Not forms during this phase to help you define the problem and narrow its scope. For more information, go to CATWOE and Is Is Not .

• After you establish your team in phase D1, gather as a team to define the problem. Identify what is happening, where it is happening, when it occurs, and who it impacts.
• Collect any evidence of the problem, including data and images, and add these items as related documents and/or hyperlinks to the roadmap of the 8D Project template.
• Create a specific, measurable, and well-documented problem statement based on your findings and the data you collected.
• From the problem statement, define the scope so the team can collectively set goals and establish a timeline for the project.
• Update the 8D Action Items form.
• What is the immediate problem?
• How can we prevent it from getting worse?
• After you clearly define the problem in phase D2, issue a Quality Alert (see below) to inform customers of the problem, what they can do until you implement a permanent solution, and what they can expect until then.
• Use a brainstorming tool to brainstorm potential containment solutions.
• Use a Solution Desirability Matrix to determine the best solution, then describe the solutions you considered and which one you plan to pursue. For more information, go to Solution Desirability Matrix .
• Summarize your Interim Containment Plan.

Quality Alert

A Quality Alert form ensures that you manage the problem promptly and systematically.

• Who should you notify about the problem?
• What will the notification be and who is responsible for it?
• When and how will you deliver the notification?
• Document the details of the problem including the date, time, and location of its discovery and information about the product, processes, or equipment involved.
• After analyzing the problem, determine its impact on the customer.
• Document what actions the customer can take to address immediate issues and what they should expect as a follow-up from your organization.
• Itemize the deliverables you plan to produce to address the problem and communicate this information to your customers.
• Include the purpose of each deliverable, who will deliver it (owner), who will receive it (audience), and when and how they will receive it.
• What is the problem's root cause?
• What is the problem's escape point, or the earliest point at which the problem should have been detected, but was not?
• What tools were used to investigate the problem?
• After you implement the interim containment plan from phase D3, use a Fishbone diagram to brainstorm likely causes of the problem. Next, use the Five Whys form to help narrow the likely causes. For more information, go to Fishbone and Five Whys .
• Perform a root cause analysis. Summarize the results of your analysis and how you verified the actual root cause. Be sure to include any tools that were used in your analysis and verification and link them to the project.
• Use a Fishbone diagram to brainstorm likely escape points. Summarize the results of this exercise and how you verified the actual escape point.
• Update the 8D Action Items Items form.
• What corrective action will best solve the problem?
• Does the corrective action have any potential side effects or negative consequences?
• Based on your findings from the D4 phase, summarize the corrective actions you plan to take to eliminate the problem's root cause.
• Use a PFMEA to identify the causes of failure and evaluate the risks associated with each cause. For more information, go to FMEA .
• Use an Impact Analysis to identify who and what are impacted by potential change to evaluate the severity of the impact. For more information, go to Impact Analysis .
• Based on the results of the PFMEA and Impact Analysis , determine if there are any side effects from the corrective actions you plan to take. If so, summarize how you plan to mitigate them.
• Did corrective actions result in a significant improvement?
• What evidence do we have to verify that the corrective actions were effective?
• After you implement the corrective actions, collect data to assess and verify the results.
• Use a 2-Sample t Test to compare past performance with current performance.
• Use Control Charts and Time Series Plots to monitor the results of the corrective actions.
• Gather feedback from customers to ensure the corrective actions resolved the problem from their perspective.
• Summarize your data collection methods and any evidence of the improvement. Include any data sets or graphs.
• Document any unexpected side effects the corrective actions caused and how you addressed them.
• Do we need to change any systems, processes, or procedures to prevent the problem from happening again?
• What internal documentation do we need to update to support these changes?
• Who needs to be aware of these changes?
• Use a brainstorming tool to identify potential systemic failures that could lead to a recurrence of a similar problem in other areas, such as product lines, departments, or locations.
• After you identify potential systemic failures, use a process map to reflect any proposed process changes to prevent these potential failures.
• Use a Solution Implementation Checklist to document items to consider before you implement any proposed process changes. For more information, go to Solution Implementation Checklist .
• After you determine which proposed changes to implement, complete a Communication Plan to ensure that you can effectively communicate the proposed process change. For more information, go to Communication Plan .
• Identify, review, and update any internal documentation affected by the proposed process change.
• Implement the process change, then communicate the change to the affected personnel.
• What did we accomplish as a team?
• How did each team member contribute to the team's success?
• What lessons did we learn?
• At the end of the project, gather as a team to celebrate your success and complete the Project Retrospective and Lessons Learned form (see below).
• Acknowledge the effort and commitment of the team.
• Recognize and appreciate each team member and their individual contributions.
• Share success stories and lessons learned from the experience.
• Encourage team members to provide feedback on what went well and what did not go well to foster a positive work environment and open communication.

Project Retrospective and Lessons Learned

• What went well?
• What did not go well?
• What did we learn from the project?
• As a group, share what went well and what did not go well throughout the course of the project.
• From this discussion, identify issues that affected productivity or quality of work. Try to recognize and understand patterns or themes that contributed to the teams' successes and challenges.
• Based on this insight, generate specific action items for future improvements.
• Minitab.com
• License Portal
• Cookie Settings

You are now leaving support.minitab.com.

Click Continue to proceed to:

• Leadership Development
• Operational Excellence
• Industry 4.0 – Management Digitalization
• Food & Bev
• Construction
• Manufacturing
• Heavy Industry
• The Manager's Journey
• Cross-platform tool
• Digital Gemba Walk
• Collaboration and Rituals
• Coaching and Improvement
• Knowledge Center - New
• All Features
• Industry 4.0 and 5.0

Case Studies

• Continuous Improvement
• Frontline Managers
• Key Behaviroral Indicators
• Management Skills
• Productivity
• Free Resources

TABLE OF CONTENT

Share this article, download a pdf version., subscribe to our newsletter, 10 effective tools and problem-solving methods for manufacturers.

Downloaded on: May 1, 2024

• April 30, 2024

Variability of demand, quality management, equipment maintenance, and integration of new technologies : problems are frequent and inevitable, and manufacturers face challenges very often. Acknowledging this reality enables teams to remain vigilant, quickly identify and resolve these difficulties, and constantly improve processes and products alike.

Why focus on problem-solving? In the Lean philosophy , a problem isn't just a problem; it's also, and above all, an opportunity to do better. Rather than hiding or ignoring what's not working, the idea is to face up to it, to find structured methods for optimizing efficiency and quality. For this, there are a number of possible solutions and tools available.

What are the different stages of problem-solving? Which methods and tools are most effective in production environments? And how do you use them? 

This article provides all the answers and problem-solving tips.

In a hurry? Save this article as a PDF.

Tired of scrolling? Download a PDF version for easier offline reading and sharing with coworkers.

Key steps of a problem-solving process in a factory

To better understand each of these steps, let's take the example of a factory manufacturing automotive components, faced with a sudden rise in the number of defective parts.

1. Identify the problem

The first step is to recognize that a problem exists. This involves observing the symptoms and identifying the gaps between the current state and the desired goal.

The QQOQCCP tool enables you to identify the problem by collecting factual information on incidents.

• Observation: Abnormal increase in the number of defective parts at the quality inspection station.
• Action: Collect data on the number of defective parts, the types of defects, and the times when they occur.

2. Define the problem

After identification, you need to precisely define the problem. This involves determining its scope (using the Four A’s method, for example), representing it clearly, and understanding its impact on operations.

• Analysis: 10% of parts produced have surface defects (higher than the acceptable standard of 2%).
• Action: Clearly define the problem as a significant increase in surface defects on automotive parts.

3. Find the root cause of the problem

This step aims to analyze the factors contributing to the problem in order to identify its root cause. This is a critical process requiring in-depth examination to avoid treating symptoms alone. 

• Investigation: After using the 5 Whys method, the root cause turns out to be premature machine wear.
• Action: Examine maintenance records and machine operating parameters to confirm this cause.

4. Brainstorm solutions

Once the root cause has been identified, it's time to focus on finding solutions. This phase encourages creative problem-solving and innovation from the whole team. They have to explore existing ideas and generate new ones.

• Brainstorming: Several potential solutions are considered, such as replacing tools more frequently or modifying machine parameters. 
• Action: Evaluate the advantages, disadvantages, and feasibility of each solution using the PDCA method.

5. Test your solutions

Before implementing a solution on a large scale, it is essential to test it in a controlled environment. This enables you to assess its effectiveness in real-life situations and adjust the action plan.

• Experimentation: Replace tools more frequently to see if this reduces the defect rate.
• Action: Implement the test plan over a set period using the "Do" phase of PDCA, then collect data on the impact of this change.

6. Standardize and document the chosen solution

Once you’ve found the best solution, it must be standardized and integrated into the organization's procedures. Documenting the process helps prevent the problem from recurring and facilitates employee training .

• Implementation: After confirmation that more frequent tool replacement reduces defects, this practice is standardized across the entire production line using the DMAIC method.
• Action: Document the new process using the 8Ds, train operators in the new practice, and integrate the change into standard operating procedures.

5 Useful problem-solving strategies for manufacturing

1. 8d (eight disciplines problem solving).

8D is a quality approach to solving complex problems requiring in-depth analysis and lasting corrective action.

The method comprises eight steps:

• Prepare the 8D process
• Describe the problem
• Identify and implement immediate actions
• Identify the real causes
• Identify and implement permanent corrective actions
• Validate permanent corrective actions
• Prevent recurrence
• Congratulate the team

Use case in the manufacturing industry

Problem: Recurrent failure of a major piece of equipment, leading to costly production stoppages.

8D would enable a multi-disciplinary team to systematically identify, analyze, and eliminate the root cause of the failure while implementing sustainable corrective actions.

2. PDCA (Plan-Do-Check-Act)

Also known as the Deming wheel, this systematic, iterative model comprises four stages or cycles: Plan, Do, Check, Act.

The PDCA method helps companies test changes under controlled conditions, evaluate the results, and then implement improvements progressively to optimize production and ensure consistent product quality.

Problem: Variation in the quality of the finished product, which does not always meet standards.

PDCA would address this problem by planning improvements, testing them, evaluating their effectiveness, and adjusting the production process to stabilize product quality.

3. DMAIC (Define, Measure, Analyze, Improve, Control)

This Six Sigma method is highly effective in optimizing production processes, reducing variation, and eliminating defects by focusing on data and statistical analysis.

It involves clearly defining the problem (Define), measuring (Measure), and analyzing process data to identify root causes (Analyze), then implementing improvements (Improve) and controlling processes to ensure sustainable quality gains (Control).

Problem: High scrap and rework rates on an assembly line.

DMAIC would be used to specify the problem, measure performance, analyze data to find the cause, implement improvements, and control the process to reduce defects.

4. QRQC (Quick Response Quality Control)

This fast, effective method inspired by Lean Management, consists in identifying, analyzing and solving problems directly on the shop floor. It is particularly well suited to fast-paced production environments where immediate detection and resolution are necessary to maintain production continuity and efficiency.

Problem: Frequent safety incidents in the workplace.

QRQC would enable rapid reaction to identify and resolve the causes of such incidents immediately, thereby reducing their frequency and improving overall safety.

5. Four A’s

The Four A’s method is a structured approach that is designed to systematically address and solve problems within an organization. 

• Assess: This step involves identifying and understanding the problem. 
• Analyze: Once the problem is assessed, the next step is to analyze it to find the root causes.  
• Address: With a clear understanding of the root causes, the third “A” involves developing and implementing solutions to address these causes.  
• Act: The final “A” focuses on standardizing the correct solution and integrating it into the organization’s processes.   

It is used where problems need to be solved quickly and efficiently while ensuring that lessons learned are integrated into standard practices.

Problem: Missed delivery deadlines due to production bottlenecks.

The Four A’s method would help to quickly detect bottlenecks, analyze their causes, find and implement effective solutions, and then integrate these changes into regular operations to improve on-time delivery.

How to choose the right problem-solving method

The choice of problem-solving method depends on several factors:

• The nature and complexity of the problem: Before choosing a problem-solving approach, you need to understand exactly what is wrong. If it's a complex and multifactorial problem, structured, in-depth methods such as 8D or DMAIC may be appropriate. For more immediate or quality-related problems, QRQC or Four A’s may be more appropriate.
• Company objectives: Look at the big picture; align the method with your strategic objectives, such as improving quality, reducing costs, or increasing customer satisfaction. For example, DMAIC is often chosen for defect reduction and process optimization objectives.
• Available resources: Think about the resources you can allocate to problem-solving processes (time, skills, budget). For example, PDCA can be implemented more quickly when resources are limited.
• Team expertise and problem-solving skills: Use a method that matches your team's qualifications. Training may be required for more complex approaches such as DMAIC or 8D.
• The need for standardization and documentation: If documentation and standardization of processes are essential, opt for methods that integrate these aspects, such as 8D or DMAIC.

5 Tools for structuring your problem-solving methods

Now it's time for the problem-solving tools! These will help structure the process and keep it moving in the right direction.

1. The 5 Whys

This problem-solving technique, created by Toyota founder Sakichi Toyoda, involves repeatedly asking the question "Why?" until the root cause of a given problem is revealed. It's a simple but powerful tool for finding root causes.

A factory has a problem with late delivery of finished products:

• Why is the plant experiencing delays in the delivery of finished products? Because the production of final units is often late.
• Why is the production of final units behind schedule? Because assembly takes longer than expected.
• Why does assembly take longer than expected? Because parts needed to complete assembly are often missing.
• Why are parts often missing? Because supplies regularly arrive late from the supplier.
• Why do supplies arrive late from the supplier? Because orders are placed too late, due to an inefficient procurement process.

2. The Ishikawa diagram (5M)

Also known as the "fishbone diagram" or "5M", this tool developed by Kaoru Ishikawa helps to systematically visualize all the potential causes of a specific problem, as well as the contributing factors.

Causes are divided into 5 main categories.

A factory encounters a problem with a drop in product quality:

• Problem or "Effect" (fish head): Decline in product quality
• Categories of causes (main branches):
• Manpower: Operator skills , training, motivation.
• Methods: Work procedures, quality standards, operating instructions.
• Materials: Raw material quality, batch variability, supplier specifications.
• Environment: Working conditions, temperature, humidity, dust.
• Equipment: Equipment wear, machine calibration, maintenance. 

This evolution of the Ishikawa diagram focuses on not five, but seven major problem areas: Manpower, Method, Materials, Environment, Equipment, Management, Measurement.

A factory is experiencing machine failure problems:

• Manpower: Inadequate operator training, human error due to fatigue, or lack of experience.
• Methods: Obsolete production processes, and lack of standardized operating and maintenance procedures.
• Materials: Inconsistent quality of raw materials, premature wear of spare parts.
• Environment: Unsuitable working conditions, disturbances due to excessive noise or vibration.
• Equipment: Outdated equipment, neglected or inadequate preventive maintenance.
• Management: Inadequate decision-making, and insufficient communication between departments.
• Measurement: Uncalibrated or faulty measuring instruments, lack of regular quality controls.

4. The Pareto principe

The Pareto or 80/20 principle is very useful for focusing on the problems that will have the greatest impact once solved, and for making informed decisions.

In a factory producing electronic components, 80% of production defects stem from just 20% of the manufacturing processes.

By analyzing production data, the company could discover that the majority of defects are linked to errors in the soldering and PCB inspection stages. These two stages, although representing a small part of the total manufacturing process, are crucial and require special attention to reduce the overall number of defects.

5. The QQOQCCP

This tool helps gather comprehensive information on a problem by answering these key questions: Who, What, Where, When, How, How much, Why. Thus, it provides an in-depth understanding of the situation.

There is a delay in production at a furniture manufacturing plant:

• Who is affected by the problem? Assembly line operators and production managers are directly affected by the delay.
• What exactly is the problem? Deliveries of finished furniture to customers are several days behind schedule.
• Where exactly is the problem occurring? The problem occurs in the final assembly shop, where the furniture is prepared for shipment.
• When was the problem detected or when does it occur? The delay has been observed over the past two weeks, mainly during the third shift.
• How does the problem occur? The delay is due to a bottleneck in the finishing and packing stage, where there is a lack of personnel and problems with the packing equipment.
• How often has the problem occurred, or what is the scale of the problem? The problem caused a 30% delay in orders during this period.
• Why does the problem occur? The problem could be due to inadequate staff planning and recurring packaging equipment failures.

Other tools can also be useful for structuring problem-solving methods:

• Brainstorming
• Gemba Walks
• SWOT analysis
• Control charts
• Prioritization matrices

Tips for effective implementation of problem-solving techniques

Integrate problem-solving into daily routines.

Instead of seeing problem-solving as a separate activity, integrate it into daily routines. For example, set up SIM meetings to discuss ongoing problems as a group and monitor progress on solutions.

Use technology for your benefit

Adopt a Daily Management System (DMS) like UTrakk to quickly identify problems, track corrective actions, facilitate collaboration between teams, and document solutions in a centralized repository.

Develop specific key performance indicators for problem resolution

Define Lean KPIs that measure the effectiveness of the problem-solving process (average time to solve the problem, problem recurrence rate, and impact of solutions on business performance).

Practice problem-solving on the shop floor

To understand problems, you need to go where value is created. Encourage managers to go on the shop floor to directly observe processes, interact with operators, and identify possible improvements.

Create cross-functional problem-solving groups

Form teams with members from different departments to tackle complex problem-solving. Integrating different angles, perspectives, and expertise broadens the point of view on the subject, enriches the analysis, and generates more creative ideas.

Adopt a coaching approach to skills development

In addition to basic training, use mentoring and coaching to develop problem-solving skills . Experienced employees can guide less experienced ones, sharing their know-how.

Conduct post-mortem reviews

When a problem is solved, conduct a post-mortem to discuss what went well, what didn't, and how processes can be improved.

Tracking and evaluating each solution implemented allows you to adjust strategies as needed, learn from past experiences, and foster continuous improvement .

UTrakk: Your ally in structuring and optimizing problem-solving

Using organized methods and analytical tools to tackle challenges is essential for manufacturers seeking to improve operational efficiency and product quality. UTrakk DMS is the perfect solution for this structured approach to daily problem-solving. With its multiple functionalities – rituals, actions, dashboards, and more – this Daily Management System can adapt to any problem-solving method to optimize every step of the process. Once a solution is standardized, it can be documented in UTrakk’s Knowledge Center to ensure compliance and prevent recurrence.

Adopting these problem-solving techniques not only enables manufacturers to respond effectively to today's challenges, but it also lays the foundations for continuous improvement, ensuring their competitiveness in an ever-changing industrial environment .

Turn your production challenges into opportunities for improvement!

In addition to providing the UTrakk solution, Proaction International supports you in implementing the best problem-solving methods and helps you achieve operational excellence.

Adeline de Oliveira

Writer and editorial manager for about 15 years, Adeline de Oliveira is passionate about human behavior and communication dynamics. At Proaction International, she covers topics ranging from Industry 5.0 to operational excellence, with a focus on leadership development. This expertise enables her to offer insights and advice on employee engagement and continuous improvement of managerial skills.

Déli-Porc Develops an Agile, Digitalized Culture Focused on Optimization

Kefor maximizes its performance by optimizing manager skills, le goupe maurice: motivate and retain talents by focusing on the leadership development of managers.

© 2023 Proaction International Inc. All rights reserved. Terms of Use | Privacy Notice | Cookie Notice