When problems appear, discipline is vital. Disciplines also help, and the eight disciplines of problem-solving (also referred to as the 8Ds) offer a proven process improvement structure that provides a framework for identifying root causes, eliminating them, and preventing reoccurrence.

The enduring popularity of the 8Ds attests to their power. It’s a tried and tested format on which you can rely — no matter what has gone wrong elsewhere.

How the 8 Disciplines of Problem Solving Evolved

In the 1980s, the Ford Motor Company published its manual, Team Oriented Problem Solving (TOPS), the first articulation of the 8Ds. Eventually, it refined the original procedures into the current 8Ds.

Ford also added an initial planning stage (D0). There are now nine steps of 8D. Fortunately, the actual process is more intuitive than its numbering.

Initially developed for the auto industry, the 8D problem-solving process has been successfully adopted across multiple industries, including healthcare, government, finance, retail, and manufacturing.

How 8D Can Help You

The benefits of 8D include:

  • More effective and efficient problem solving
  • A team-oriented approach
  • Open communication within the team and with management
  • A framework for corrective action that allows for systemic changes and continual improvement
  • Intense examination of the control systems that permitted the problem
  • Easy integration with process-improvement tools

You can apply the 8Ds whenever processes break down. Engineers and manufacturers often turn to them when they receive customer complaints or discover safety or regulatory issues. They also come in handy when a system’s amount of waste or a product’s failure rates hit problematic levels.

What Are the 8 Disciplines of Problem Solving?

The 8Ds provide a methodical approach to problem-solving. The sequence of nine steps will take you from the initial discovery of an issue to your celebratory toast when you fix it.

D0: Plan

The designers added a planning stage to the original 8D methodology. This stage focuses on the one following, bringing clarity and intention to the project.

Summarize the Issue

You’ll describe it in greater detail later, but you’ve started this process because you identified a problem. What is it?

Collect the information on the problem’s symptoms and identify apparent gaps or additional needs. You might also want to consult a subject matter expert and get their input on your issue. They may be able to save you time further down the road.

Identify and Take Emergency Responses

If your house is on fire, put it out. Then you can take a hard look at the wiring.

As soon as you’ve identified a problem, take any necessary action to limit or contain a dangerous situation. Don’t overreact or prematurely make uncertain changes. Just exercise common sense.

Plan for the 8Ds

Your actual project plan will change as you make discoveries. This document is simply an outline of the project’s space within your company. It’s a theory about the necessary investment of time and other scarce resources.

Identify the resources you have and need. Sketch out schedules and note the variables that will affect them.

D1: Form Your Team

Create a team to tackle the problem.

Add the Right People

The group should be small enough to be efficient but large enough to cover all necessary process/product knowledge and technical skills. Some recommend a team of about five members. Make sure this team has the necessary authority and allotted time they need.

Identify both a team leader and a project champion in management (if necessary). Establish guidelines for harmonious group work.

This is also the time to perform team-building exercises if you want.

Review the Problem

Get team members up to date and fully on board. Review the initial brief for the project and discuss scope and priorities. Team members should all have the opportunity to voice initial concerns and complications.

D2: Define and Describe the Problem

Outline the problem in as much detail as possible, using quantifiable terms. Clarify both what the problem is and is not. The latter will help you begin eliminating potential reasons for failure.

As you define the problem, you should also understand whether your situation is “something changed” or “never been there.” Has something gone off course, or has a new variable or context appeared?

Identify Critical Process Steps

Create a flowchart for the flawed process, and indicate which steps are critical to the problem at hand. In this step, you will start to approach root cause analysis, though you won’t isolate and verify a root cause until D4.

Outline Project Plan

At this point, you will develop a more detailed, high-level project plan that includes milestones, objectives, and a fuller schedule.

D3: Contain the Problem

D3 focuses on interim containment action rather than permanent and preventive action.

This step isn’t about emergency action, which should have been taken already. You’ve put out the house fire, but you still need to lodge your tenants elsewhere while your electricians go through the place.

Find a Temporary Solution

Take whatever action is necessary for the satisfaction of your customers or the effectiveness of your organization. You may need to develop workarounds, issue (non-emergent) recalls, or establish a resource for affected customers.

The ideal interim solution is:

  • Inexpensive
  • Simple and quick to implement
  • Easy to reverse
  • Validated by customer or employee feedback

When you’ve realized your long-term solution, you can do away with interim measures.

D4: Find the Root Cause

Root cause analysis is at the heart of most problem-solving tools and processes. It’s time to dig deep into the problem and find out what’s gumming up the works.

Develop Root Cause Theories

You’ll complete the process of elimination that you began when defining the problem. Refer to your flowchart. What could be causing the problem?

Use root cause analysis tools like the Fishbone Diagram and the five whys. Find all possible factors that could contribute to the breakdown.

Test and Review Causes

Test each of your potential causes, collecting data until you can rule out all but one.

Identify Escape Point

In addition to finding the root cause, you need to figure out what part of the control system allowed it to escape detection and be contained. Find the point where someone or something should have caught the issue. That’s the escape point.

Correctly identifying and solving escape-point issues is essential to preventing future problems.

D5: Identify and Test Solutions

You’ve found the problem and its escape point. Of course, that’s only half the battle. Now you need to solve them — permanently and completely.

Define what “solved” looks like. Is there a threshold of minimum acceptability?

Develop Solutions

Give your team the time to consider potential approaches to both the root cause and escape point issues. The first idea may not be the best, and brainstorming tools such as affinity diagrams can help.

Test Solutions

Make sure they work. You should also perform risk and cost analysis for any final contenders.

D6: Choose Solutions and Put Them Into Practice

Choose your best solutions, outline your implementation plan, and move forward with it. Both management and team members should sign off on the solution.

Implement, Validate, Monitor

After putting your plan into practice, check with customers and stakeholders to ensure that their concerns are fully addressed. Continue to monitor the situation to make sure the solution is sustainable and effective. You’ll also keep an eye out for any unintended consequences.

Move From the Interim to the Permanent Solution

Once you have the permanent solution up and running, you can end interim measures.

D7: Prevent Recurrence

By addressing the escape point and continuing to monitor the situation, you’re doing a fair amount to prevent an exact recurrence. But make sure that all contributing systems have been updated to reflect new input.

You should also preserve all documentation so that future teams have it as a resource for similar problems. Even better, prevent those similar problems.

Improve and Standardize Systems Across the Organization

Are there analogous areas of the organization that could use review? Are their policies and procedures in line with those you’ve developed?

Conduct an audit of operational procedures, management processes, and training manuals.

D8: Celebrate and Recognize Contributions

You’re not done quite yet. Recognition and validation are vital for a healthy organization, so take time to acknowledge individual contributions and the team’s accomplishments.

Perform a Final Review

Look at team output with a focus on before-and-after results. Finalize documentation and add it to the company library.

You should also take the time to reflect on your 8D experience. Explore trouble spots or areas that could use clarification for the next problem-solving team.

Celebrate

Reward your team appropriately. This can include anything from company-wide emails to dinner to bonuses. Even a personal email goes a long way toward making people feel like valued members of a community.

Then Do It All Again

When you make the eight disciplines of problem-solving part of your organizational DNA, you prepare to solve all kinds of problems in a streamlined, effective way.

The 8Ds integrate seamlessly with the Six Sigma methodology and make a great addition to your toolkit.