8d approach

8/11/2019 8D Approach

1/44

1

Improvement Initiatives presents

TEAM-ORIENTED PROBLEM SOLVING

A SYSTEMATIC PROBLEM SOLVING PROCESS

8-D


2/44

2

Problems take longer to solve than to prevent.

If theres no time to do it right the first time,you will have to find the time to do it over

and over.

and over....

USE THE 8-D PROBLEM SOLVING DISCIPLINE ONLY

WHEN THE CAUSE IS UNKNOWN

If you dont know why a problem happened,

al l your correct ive act ions are guesses, not f ixes.

85% of problem are system oriented.

Only 15% are local causes.

Knowledge of the entire system is essential.


3/44

Problem solving problems:

Problem is described incorrectly or inadequately

Some of the 8-D steps are skipped or sluffed off

Poor team make up or poor participation

Lack of team technical expertise and skills

Incorrect or incomplete root cause was identified

Preconceived notions clouded the problem solving process

3


4/44

The Chosen

Many problem solving methods exist:

Ford typically uses a method called 8D

GM typically uses a method called 5P

Chrysler typically uses a method called 7D

Many companies use a 4S

We have chosen to use the 8D process as it incorporates the

other methods

4freeleansite.com


5/44

5

.

Document a procedure for

problem solving


6/44

6

The 8D process consists of 8 specific problem solving disciplines.

D1. USE TEAM APPROACH

D2. DESCRIBE THE PROBLEM

D3. IMPLEMENT AND VERIFY INTERIM (CONTAINMENT) ACTIONS

D4. DEFINE AND VERIFY ROOT CAUSES

D5. VERIFY CORRECTIVE ACTIONS

D6. IMPLEMENT PERMANENT CORRECTIVE ACTIONS

D7. PREVENT RECURRENCE

D8. CONGRATULATE YOUR TEAM

The initial event is that you BECOME AWARE OF A PROBLEM

You can ignore it - and it will bite you again even harder

Or you can begin the process to eliminate its cause


7/44

freeleansite.com 7

D1. USE TEAM APPROACHEstablish a small group of people with the: process/product knowledge,allocated time, authority, and skill in the required technical disciplines to solve theproblem and implement corrective actions. The group must have an act ivelyinterested d esignated champion.

D2. DESCRIBE THE PROBLEMSpecify the internal/external customer problem by identifying in quantifiableterms the who, what, when, where, why, how, how many (5W2H)for theproblem.

D3. IMPLEMENT AND VERIFY INTERIM (CONTAINMENT) ACTIONSDefine and implement containment actions to isolate the effect of problem fromany internal / external customer until corrective action is implemented. Verify theeffectiveness of the containment action.

D4. DEFINE AND VERIFY ROOT CAUSESIdentify all potential causes which could explain why the problem occurred.Isolate and verify the root cause by testing each potential cause against theproblem description and test data. Identify alternative corrective actions toeliminate root cause.

D5. VERIFY CORRECTIVE ACTIONSThrough pre-production test programs quantitatively confirm that the selectedcorrective actions will resolve the problem for the customer, and will not causeundesirable side effects. Define contingency actions, if necessary, based on riskassessment.

D6. IMPLEMENT PERMANENT CORRECTIVE ACTIONSDefine and implement the best permanent corrective actions. Choose on-goingcontrols to ensure the root cause is eliminated. Once in production, monitor thelong-term effects and implement contingency actions, if necessary.

D7. PREVENT RECURRENCEModify the management systems, operating systems, practices, and proceduresto prevent recurrence of this and all similar problems.

D8. CONGRATULATE YOUR TEAM

Recognize the collective efforts of the team.


8/44


9/44

freeleansite.com 9

DISCIPLINE #2 - (D2)

Define the problem specifically and clearly

Determine the extent of the problem

Narrow the focus of the problem solving

Summarize ALL the known FACTS

In defining the problem:

Truth is separated from fiction

Opinion is separated from fact

Emotion is separated from reality

Frequently the wrong problem is solved and

the issue that caused the customer complaintis not addressed.

It is imperative the customer complaint beclearly understood.

The only method to ensure this is to havedirect customer contact.

It is not unusual for a complaint to be

misrepresented by someone who isreporting it rather than experiencing it.

Reporting systems and tally sheets are oftenused that mis-classify problems in prearrangedbut incorrect standard categories.

Part of the5W2Hproblem definition is to statethe customer complaint clearly and accurately.


10/44

freeleansite.com 10

5W2H HELPS CHARACTERIZE THE PROBLEM FOR FURTHER ANALYSIS.

WHO. Identify individuals associated with the problem. Characterize customers who are complaining. Who is having difficulty?

WHAT. Describe the problem adequately. Does the severity of the problem vary? Are operational definitions clear (e.g., defects)? Is the measurement system repeatable and accurate?

WHERE. If a defect occurs on a part, where is the defect located?

What is the geographic distribution of customer complaints? Where the difficulties being detected?

WHEN. Identify the time the problem started and its prevalence in earlier time periods. Do all production shifts experience the same frequencies of the problem? What time of the year does the problem occur?

WHY.

Any known explanation contributing to the problem should be stated.

HOW. In what mode of operation did the problem occur? What procedures were used?

HOW MANY. What is the extent of the problem? Is the process in statistical control? (e.g., P chart)


11/44

11

In addition to the 5W2H analysis, it is often useful to identify:

What the problem IS - and - What the problem IS NOT

A PROBLEM SOLVING WORKSHEET THAT COMBINES 5W2H AND IS/IS NOT ANALYSIS CAN BE A

GOOD TOOL TO ENSURE ALL ASPECTS OF DEFINING THE PROBLEM HAVE BEEN CONSIDERED


12/44

freeleansite.com 12

WHO, WHAT, WHEN, WHERE, WHY, HOW, HOW MANY:

1. What is the magnitude of the problem?

2. Has the problem been increasing, decreasing, or remaining constant?

3. Is the process stable?

4. What indicators are available to quantify the problem?

5. Can you determine the severity of the problem?

Can you determine the various "costs" of the problem?

Can you express the cost in percentages, dollars, pieces, etc.?

6. Do we have the physical evidence on the problem in hand?

7. Have all sources of problem indicators been used?

8. Have failed parts been analyzed in detail?

9. Is there an action plan to collect additional information?

CUSTOMER TERMS/SYMPTOMS:

1. Who is the customer?

2. What customer first observed the defect?

3. To whom was it reported?

4. What is the problem definition in customer terms?

5. What is the problem definition in our terms?

6. Have we verified the problem with on-site visits with the customer?

Have we seen it for ourselves?

5W2H Questions


13/44

13


Iso late the customer from

reoccu rrences o f the prob lem

Immediate gathering, quarantine, and lock-up of all

suspect product

Stop production from known problem sources /

contributors

Examine DATA - FACTUAL EVIDENCE to help

determine what to contain and who to stop

Verify by experimentation and data tracking and

collection that the problem has been contained

CONTAINMENT ACTIONS

ARE NOT AND NEVER

SHOULD BE CONSIDERED

PERMANENT SOLUTIONS

TO A PROBLEM.


14/44

freeleansite.com 14

D3-IMPLEMENT INTERIM(CONTAINMENT) ACTIONS

OBJECTIVE: Define and implement containment actions to isolate the effect of the problem from any internal

or external customer until corrective action is implemented. Verify the effectiveness of the containment actions.

State all containment actions and when they will be implemented.Perform tests to evaluate the effectiveness. State the results.

State the procedures for on-going evaluation of the effectiveness (e.g., control charts, check sheets, etc.).

Coordinate an action plan for implementing interim actions.

The search for root cause should proceed concurrently with the implementation of containment actions.

ASSESSING QUESTIONS: You are prepared for a review when you can answer these questions:

VERIFICATION

1. Have all alternative actions been evaluated?2. Are responsibilities for correct actions clear?

3. Is the required support available?

4. When will the actions be completed?

5. Does the containment action protect the customer from the effects of the problem?

CONTAINMENT ACTIONS

1. What containment actions have been identified?

2. Have you ensured that implementation of the interim solution will not create other problems?

3. Will all interim actions last until long-range actions can be implemented?

4. Have you coordinated the action plan with the customer?

CONFIRMATION ACTIONS

1. Have tests been done to evaluate the effectiveness of the interim actions?

2. Can you conduct controlled experiments to predict the outcome of the actions?

3. Can you try out the actions on a small scale to test if they will be effective?

4. Is data being collected to ensure actions will remain effective?


15/44


16/44

16

COLLECT AND ANALYZE DATA TO DETERMINE IF A POTENTIALCAUSE IS A ROOT CAUSE

After cause-and-effect diagrams have been completed, data needs to be collected to determine which potentialcauses are important. Pareto diagrams and check sheets are very effective in establishing the importance of the

potential causes.

It is a mistaken belief that data oriented problem solving can be accomplished by collecting relevant data on aproblem, analyzing the results, and deciding the correct solution.

Once data is collected and analyzed, new questions often arise,so another data collection and analysis iteration is necessary.

Many problems can have more than one root cause.Data collected investigating one potential cause may not address other important potential causes.Several potential causes may need to be studied using the data collection and analysis process.

Once a potential cause has been selected for investigation, the following steps are required:

State how the potential cause could have resulted in the described problem. Establish what type of data can most easily prove or disprove the potential cause. Develop a plan on how the study will be conducted. Identify the actions on an action plan. Organize and prepare the required materials to conduct the study. Collect the required data.

Use appropriate statistical tools emphasizing graphical illustrations of the data. Outline conclusions from the study.

Does the data establish the potential cause as being the reason for the problem or does thedata point to another potential cause that needs to be investigated also?

Data collection may be as simple as check sheets or as sophisticated as design of experiments.

By using graphical tools, quick comprehension by all participants as well as accurately communicated information

will result.


17/44

17

DISCIPLINE #4 - (D4) DEFINE AND VERIFY ROOT CAUSES

Once you have satisfied

yourself you have identified

the root cause(s), retest

and verify all data pointing

to the suspected root

cause(s) - Make the

problem come and go!

The important thing here is to be sure you have Identified and tested

ALL potential causes


18/44

18

D4 - DEFINE AND VERIFY ROOT CAUSES

OBJECTIVE:Identify all potential causes which could explain why this problem occurred. Isolateand verify the root cause by testing each potential cause against the problem

description and test data. Identify alternative corrective actions to eliminate rootcauses.

Identify Potential Causes

Define the "effects" for a Cause-&-Effect diagram clearly.

Prepare a 5M, Process, or Stratification Cause-&-Effect diagram for each effect.

You may choose to use a combination.

Team members should each assume their activity causes the problem.Each should ask themselves "How could what I do possibly generate the problem?".

Prepare a Time Line Analysis if the problem was not always present.Identify "what changed, when"?

Perform a Comparative Analysis to determine if the same or a similar problem existed in

related products or processes.

Identify past solutions and root causes which may be appropriate for the current problem.Check the Lessons Learned data and similar product DFMEA / PFMEAs

Identify several potential causes. Develop a plan for investigating each cause, and updatethe Action Plan.

Evaluate a potential cause against the problem description.


19/44

freeleansite.com 19

Problem Solving Tools - Root cause

identification and verification

Flow Charting

Cause and Effect Diagrams

Scatter Diagrams

Histograms

Check Sheets

Pareto Charts

Run Charts

Control Charts

Brainstorming

Problem Solving Techniques

Use brainstorming and Cause and Effectdiagrams to narrow potential root causes Compare selected potential root causes to theIS/IS NOT data

Investigate several root causes at the same time Conduct experiments to verify your selected rootcause(s) Do a DOE - Taguchi Study if necessary Ask for additional help if necessary


Analyze Potential Causes Use the iterative process to analyze each potential cause:

Hypothesis Generation: How does the potential cause result in the problem? Design: What type of data can most easily prove or disprove the hypothesis? Preparation: Obtain materials and prepare a check sheet. Data Collection: Collect the data. Analysis: Use simple, graphical methods to display data. Interpretation: Is the hypothesis true?

Investigate several potential causes independently.

Use an Action Plan to manage the analysis process for each potential cause being studied.


20/44

20


21/44

21

CAUSE AND EFECT DIAGRAMS

ONCE A CLEAR AND SPECIFIC PROBLEM IDENTIFICATION HAS BEEN MADE, A CAUSE ANDEFFECT ANALYSIS SHOULD BE COMPLETED.

Cause and Effect Diagrams are graphic representations of potential problem causes.They are sometimes called:

FISHBONE DIAGRAMS, ISHIKAWA DIAGRAMSor CAUSE AND EFFECT DIAGRAMS

There are various types of cause and effect diagrams including:

PROCESS FLOW, 5M(sometimes called 5M and E), STRATIFICATION

The type C&E diagram utilized should be the one (or more) that provides the best detailed breakdownof potential causes.

Ask yourself: "What variability could result in the stated problem?Add each ident i f ied potent ial so urce of v ar iat ion to the C&E diagram

Without variability, either there are No problems (all good) or Everything's a problem (all bad)With variability, there are probably Some good and some bad.

Continue to ask the question for each main branch of the Cause-and-Effect diagram.

The Objective is to Identify all potential causes of the problem(by identifying sources of variability).


22/44

22


Validate Root Causes

Clearly state root cause(s) and identify data which suggests a conclusion.

Verify root cause factors are present in the product or process.

Can we generate the problem independently?

Can we make it come and go?

VERIFY YOUR ROOT CAUSE CANDIDATES

- Make the problem com e and g o -

- Turn it on and off -


23/44

23

D4 - ASSESSING QUESTIONS:

POTENTIAL CAUSES:

1. Have you drawn the process flow and stratification C&E diagrams and identified all sources of variation?

2. Have all sources of information been used to define the cause of the problem?

3. Do you have the physical evidence of the problem?

4. Can you establish a relationship between the problem and the process?

5. Do you continually challenge the potential root causes with the question "why" then follow with "because"

to construct alternative potential causes?

6. Is this a unique situation or is the likely problem similar to past experience?

7. What are the "is, is not" differences?

8. Has a comparative analysis been completed to determine if the same or similar problem existed in related

products?

9. What are the experiences of recent actions that may be related to this problem?

10. Why might this have occurred?

11. Why haven't we experienced this before?

12. What changed?

Manufacturing: Engineering:

- new suppliers? - any pattern to the problem?

- new tools? - geographically?- new operators? - time of year?

- process changes? - build dates?

- measurement system? - did the problem exist at program sign-off?

- raw materials? - was it conditionally signed-off?

- vendor-supplied parts? - did the problem exist on prototype vehicles?

- do other plants have a similar problem? - did the problem exist on the functional builds?

- did the problem exist on the 4-p's?

(pre-production product prove-out)


24/44

freeleansite.com 24

D4 - ASSESSING QUESTIONS:

DATA:

1. What data is available to indicate any changes in the process?

2. Does data exist to document the customer's problem?

ROOT CAUSE

1. If the potential cause is the root cause, then how does it explain all we know aboutthe problem? How has this been verified?

2. Is there any possibility that there is another contributing cause besides the one we

have identified? How is this being evaluated?

OTHER POTENTIAL CAUSES

1. What evidence do you have that other potential causes are actually occurring?

2. If they are occurring, what unwanted effects might they produce?

3. Do actions need to be taken to ensure that other potential causes do not create

unwanted effects?


25/44

25


To this point we have focused on:

Understanding and defining the

problem

Containing the effects of the

problem

Identifying and Verifying the root

cause of the problem

Now we need to

PERMANENTLY SOLVEthe problem

Select alternative solutions

Confirm the potential solutions

through testing programs

Verify that the solution

ELIMINATESthe problem

and its effects


26/44

26

AVOID BAND-AID SOLUTIONS

Band-Aids generally:

have the term temporary attached to them somewhere cover or hide a problem but dont remove it

are containments - not solutions

WE ARE BEYOND CONTAINMENT - WE ARE LOOKING

FOR THE ONCE AND FOR ALL, ALL TIME,

NEVER SEE THE PROBLEM AGAINFIX

When identifying solutions:

Consider the Cost and the Value

Consider Implementation issues

Consider Timing

Consider the EffectivenessReliability

Feasibility

Accuracy

Consider Potential Side Effects

You dont want to cure a cold only to develop pneumonia



27/44

27

D5 CHOOSE AND VERIFY CORRECTIVE ACTIONS

OBJECTIVE: Through pre-production test programs quantitatively confirm that the selected correctiveactions will resolve the problem for the customer, and will not cause any undesirable side effects. Definecontingency actions, if necessary, based on risk assessment.

Run Pilot Tests. Artificially simulate the solution to allow actual process or field evaluation.Field test the solution using pilot customer groups.Verify carefully that another problem is not generated by the solution.

Monitor Results. Quantify changes in key indicators.Stress the customer/user evaluation.

ASSESSING QUESTIONS:

CONFIRMATION TESTING QUESTIONS.1. Can you list and measure all of the indicators related to this problem?2. Which of the indicators are most directly related to the problem?

Can you use the indicators to measure problem severity?3. Can you determine how often or at what intervals to measure the problem (hourly, daily, weekly,monthly)?4. If there are no changes in the indicators after taking action, can you determine what to do? Willyou need to take cause, action or verification measures?5. Do all indicators reflect conclusive resolution?6. Has the team prioritized the customer/user evaluation after the implementation?

7. What scientific methods are being used to verify effectiveness in the short term and to predict theoutcome in the long term?

VERIFICATION QUESTIONS:1. Has the customer been contacted to determine a date when verification will be evaluated?2. What data has been established for follow-up?3. Has a time line chart been completed?4. Have field tests been conducted using pilot customer groups?5. Have dates been established when verification of effectiveness will be evaluated?


28/44

28


Install the best solution for permanentcorrective action

Use on-going monitoring to ensure root

causes have been eliminated

Monitor the long term effects

Back up the effectiveness with data

CORRECTIVE ACTIONS

REMOVE THE ROOT CAUSE

NOT JUST THE EFFECTS

CORRECTIVE ACTIONS ARE

PERMANENT


29/44

29

D6 - IMPLEMENT PERMANENT CORRECTIVE ACTIONS

OBJECTIVE: Define and implement the best permanent corrective actions. Choose on-going controls toensure the root cause is eliminated. Once in production, monitor the long-term effects and implementcontingency actions, if necessary,

Identify Alternative Solutions. Evaluate how other groups solved similar problems.Consider redesign of the part or process to eliminate the problem.

Anticipate the failure of the solution.Develop contingency actions.

Implement Solution. Use an action plan approach to implement the solution as quickly as possible.Test and verify contingency actions, if possible.

ASSESSING QUESTIONS:1. Do the actions represent the best possible long-term solution from the customer's viewpoint?

2. Do the actions make sense in relation to the cycle plan for the products?3. Has an action plan been defined?- Have responsibilities been assigned?- Has timing been established?- Has required support been defined?- What indicators will be used to verify the outcome of the actions, both short- and long-term?

4. On-Going Controls Ensure the problem will not recurSeek to eliminate inspection-based controls.

Address 5M sources of variation.Test the control system by simulating the problem.

5. Have the corrective action plans been coordinated with all the affected parties?6. What indicators will be used to determine the outcome of the actions?7. What controls are in place to assure the permanent fix is verified as intended?

FORECAST OUTCOME:1. Will actions permanently solve the problem?

Can you try out the corrective actions on a small scale to test their effectiveness?2. Can scientific experiments be conducted to gain knowledge to predict the outcome of the effects ofthe implemented actions?3. Do the permanent corrective actions require support from external sources to be effective?


30/44

30


OBJECTIVE:

Modify those management systems, operating

systems, practices, and procedures to prevent

recurrence of this problem and all similar

problems.

Address system follow-up responsibilities.

MODIFY (As Required):

METHODS

EQUIPMENT

MATERIALS

PROCEDURES

MANAGEMENT SYSTEMS


31/44

31



1. Has the problem occurred due to a mechanical or behavioral system?

2. Has a process flow C/E diagram of the management system been prepared?

3. Have changes been made to the system?

4. Have action plans been written to coordinate actions, if so, who, what, when?

5. Have the practices been standardized?

6. Has a new FM.E.A. been prepared? (Failure Mode Effects Analysis)

7. Have all interested parties been notified of the resolution actions, including input into

the Computer Archiving System, if available?


32/44

32



33/44

33


OBJECTIVE: Recognize the collective efforts of the team.

Use all forms of employee recognition.

Documentation as necessary.

Celebrate successful conclusion of the problem solving effort.

Formal disengagement of the team, and return to normal duties.


1. Have creative solutions been taken to warrant a review for a company sponsored award?

2. Has appreciation been shown to all the team members?

3. How has the team leader identified individual contributions to the problem resolution?

4. What are the presentation plans?

5. Could the problem and the solution be videotaped?

6. Could a paper of the team's effort be written and distributed throughout the organization?


34/44

34

Managements Role

in the

Team Problem Solving Process


35/44

35

MANAGEMENT ROLES, INVOLVEMENT AND EXPECTATIONS

CLIMATEParticipative Leadership - Supportive and People/Team Oriented Management

Team Oriented Problem Solving Process

- Understood and supported by management which is actively involved in nurturing the processTraining - In technical problem solving tools/methods and interpersonal/team skills

Support of the Team Problem Solving Process from "Identification" through "Implementation

Expectations and requirements for team and team members clearly stated and understood "up front

Encouragement to innovate, iterate, and take risk

Coaching - By example, constructive criticism, positive reinforcement

Room to Grow" and "Freedom to Fail

- Tolerance of mistakes and false starts

- Learn from errors

- Non-punitive responseRecognition/Reward - Teamwork and team skills recognized and publicized

Feedback - Communication of "value added" by team effort

MANAGEMENT ROLEHave patience - Problem solving is an iterative process involving people who are continually learning.

There is no "absolute" timetable for the solution of a problem,

Take time and dedicate effort to understand the team problem solving process and "coach" the teams.

Be willing to accept failures and false starts as part of learning process.Continuous improvement requires continuous learning/risk taking.

Provide training and "practice time" to individuals/teams.

Be personally INTERESTED/INVOLVED with teams and team dynamics.

State expectations clearly "up front."

Demand performance to expectations - teamwork, process . . .

Lead and teach by example - model the behaviors you expect.

Provide personal feedback to the team of impact/value added of problem solution.

Be willing to make teamwork/team skills and performance in team environment keys to recognition / reward.


36/44

freeleansite.com 36


IDENTIFICATION-PRIORITIZATION

System to identify problems using operational measurements Customer oriented indicators - "Total Quality" concept

Timely indicators - Support minimum time to containment - or preferably, prevent mode problem

solving

Complexity minimized - Varies based on problem type, complexity and data sources

Priority system

- Must reflect the operational priorities of the organization

- Must be understood by all

Problem solving priority - Must be matched by resource priority

Resources allocated- Must "match" the problem content and context

- Must be committed for the full term of the problem solving effort

Tracking system(s) - Must be effective without creating "non-productive" work

MANAGEMENT ROLE

Establish, maintain, and continuously improve the system.

Refrain from tampering/overriding the priority system. Provide the "right" resources (people, facilities, etc.) in sufficient quantity and quality to

complete the task in a timely manner.

Respect resource commitments.

Provide clear expectations - before the fact.

Share significance (impact) of problem with team.


37/44

37


PROBLEM SOLVING

Team process- Team must have the "right" members

- Knowledge

- "Team" Skills and Orientation

- Authority to act for their activity

- Time to do the job right

8-D process

- Complete and thorough follow through on all 8 D's

- Iteration as required

Tools - Correctly applied/applicable to taskAccess To all required information, facilities and resources

Methods Appropriate to the specific problem

MANAGEMENT ROLE

Be willing to give up the "right" people to the team.

Live up to commitments - People, time, resources . . .

Understand the process and support the team.

Give authority to team members.Refrain from "Monday morning quarterbacking."

Provide constructive/supportive interest in team and process.

Review progress and ask constructive coaching questions.

Require adherence to proper process and appropriate documentation.

Be patient

Demanding "instant solutions" to problems forces teams to shortcut the process which

often results in failure to identify root cause or otherwise fatally flaws the process.


38/44

38


IMPLEMENTATION

System to carry out corrective actions promptly and efficiently

Minimum procedural requirements and financial/management approval levelsProvision for "expediting" corrective actions within the system

Rigorous mechanism to institutionalize "prevent actions" and provide ongoing maintenance of prevent

actions "in place"

System to retain problem solving experience with no added workload - 8-D write-ups and backup as

"case studies"

Capability to learn from experience - Case studies organized and accessible to future problem solving

teams

Current experience published to applicable activities - Promote prevent mode problem solving

Feedback - Long term results and value added to team

Recognition and reward of team

MANAGEMENT ROLE

Establish, maintain and continuously improve implementation systems.

Commit funds, resources and personal attention/support to follow through on implementation

phase.

Provide "knowledge system" to retain, organize and publish experience/knowledge gained.Become an "advocate for implementation"

Be personally involved

Eliminate roadblocks

Expedite action

Demonstrate support/interest

Recognize team effort and reward "team players"

Acknowledge value of teams' problem solution

Make systems changes as necessary to prevent problem recurrence


39/44


40/44

freeleansite.com 40

1. USE TEAM APPROACHAction plan for team formation.

2. DESCRIBE THE PROBLEMProcess flow diagram to define the processPareto analysis to select priority problemsControl charts to indicate special causesCheck sheets to define 5W2HAction plan to coordinate problem definition actions

3. IMPLEMENT AND VERIFY INTERIM (CONTAINMENT) ACTIONSCheck sheets to evaluate effectiveness of actionsControl charts and histograms with intensive sampling for process monitoringAction plan to coordinate interim fixes

4. DEFINE AND VERIFY ROOT CAUSE(S)Identify Potential Causes

Brainstorming to develop the potential causesCause-and-effect diagrams to identify and organize potential causesFailure mode and effects analysis (FMEA) to identify potential causes from observed failure mode

Analyze Potential CausesCheck sheet to collect data

Comparison plots, histograms, and stratified graphs to evaluate stratification factors or different process or product parametersScatter plots to evaluate relationships between characteristicsGage studies to evaluate the measurement systemAction plan to manage analysis steps

Validate Root CausesComparison plots, histograms, and stratified graphs to validate cause (e.g., with/without comparison)Stratified graphs to validate presence of root cause factorsAction plan to manage validation actions

Identify Alternate SolutionsBrainstorming to solicit ideasAlternative solution C/E diagram to address potential areas for solutions

5. CHOOSE AND VERIFY EFFECTIVENESS OF PERMANENT CORRECTIVE ACTIONControl charts and histograms to evaluate process stability and capabilityCheck sheets to collect product or process evaluation informationFMEA

6. IMPLEMENT PERMANENT CORRECTIVE ACTIONSControl charts and check sheets to monitor process performanceComparison plots to periodically ensure stratification factors are not influencing process outputDimensional Control Plan

7. PREVENT RECURRENCEProcess flow diagram to define the management system that did not prevent the problemAction plan to coordinate needed changesFMEA

8. CONGRATULATE YOUR TEAM

8D PROBLEM SOLVING PROCESS


41/44

41

When assessing

MEASUREMENT

SYSTEMS

a gage R & R is often

required

See the AIAG Reference Manual

titled:

MEASUREMENT SYSTEMS

ANALYSIS

for help and guidance in this area.


42/44

42


43/44


44/44

Improvement Initiatives presents

TEAM-ORIENTED PROBLEM SOLVING

A SYSTEMATIC PROBLEM SOLVING PROCESS

8-D

8d approach

Documents