INTRODUCTION TO EIGHT DISCIPLINES OF PROBLEM SOLVING (8D) AND TECHNICAL REPORT WRITING

INTRODUCTION FOR INTRODUCTION TO EIGHT DISCIPLINES OF PROBLEM SOLVING (8D) AND TECHNICAL REPORT WRITING

The Eight Disciplines of Problem Solving (8D) is a problem-solving methodology designed to find the root cause of a problem, devise a short-term solution, and implement a long-term solution to prevent recurring problems. When your product is defective or is not satisfying your customers, an 8D is an excellent first step to improving Quality and Reliability.

When you have to communicate complex technical information, your technical report has to deliver your message clearly while demonstrating the rigorous methodology that underpins your findings and conclusions.

In this specially designed program addresses both 8D problem solving skills and technical report writing course, The training will address the need to solve problem in a structured methodology and  write technical reports easily resulting in more effective technical documents. 

LEARNING OBJECTIVES

     Participants can expect to learn and develop skills to confidently:

• Perform 8D step by step.
• Facilitate an effective 8D.
• Participate in 8D exercises.
• Define root causes and mechanisms of failure.
• Determine effective Interim Containment Action
• Manage and store 8D content (Lessons Learned) for future use.
• When to select and utilize tools such as:
• 5 Why
• Ishikawa/Fishbone
• Affinity
• Is / Is Not
• Complete the 8D format correctly.
• Design and structure a document by analyzing the readership and selecting the right information.          
• Write clearly and in the correct style for your readers.
• Use correct language and grammar.
• Use layout, typography, and illustrations to help get your message across

WHO SHOULD ATTEND

Engineers, Quality Engineers, Quality Managers, Customer Quality Engineers, Supplier Quality Engineers.

COURSE CONTENT                                                                                               

• 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
• Review of Analytical Tools in 8D
  • Brainstorming Rules
  • Ishikawa / Fishbone
  • Affinity Diagram
• D0 – Awareness of the problem/Plan for the 8D
  • Problem Symptom
  • Quantified Symptom
  • Criteria for 8D Continuance
• D1 – Establish the Team
  • Roles and Responsibilities
  • Team Preparation
  • Agenda and Rules
  • Core Team and SMEs
• D2 – Define Problem Statement
  • Repeated Why
  • Affinity Diagram
  • Is / Is Not
  • Workshop on Problem Statements and Brainstorming
  • Workshop on Problem Description Development
• D3 – Interim Containment Action (ICA)
  • Reassuring the customer
  • Containment Plan
• D4 – Identify and evaluate root cause/RCA.
  • Process Mapping
  • Human Factors
  • Comparative Analysis
  • Root Cause Theories
  • Root Cause Verification
  • Escape Point
  • Workshop on Root Cause Analysis
• D5 – Permanent Corrective Action (PCA)
  • Methods for Selecting PCA
  • Correction and Prevention
  • Error Proofing
  • Verification of PCA
• D6 – Implementation and Validation of PCA
  • Plan, Do, Study, Act (PDSA) Implementation Plan
  • Change Management
  • Stakeholders
  • Validation Criteria and Sample Size
• D7 – Prevent Occurrence
  • Risk Management
  • Processes and Procedures
  • Lessons Learned
  • Looking forward in time
• D8 – Closure and Congratulate the Team
  • Lesson learned.
  • Communicating across organizations.
  • Congratulations on the team.
  • Archive of Documents and Learning.

TECHNICAL WRITING

• Technical Report Writing – the Basics
• • Technical Reports – What They Do
  • Analysis of Bad Reports – What is Not Right?
  • Writing Assessment – How Good Are You in Writing Technical Reports? – What is Your Writing Problem
  • The Decoding and Interpretation Preference – How the Reader’s Mind Assimilates Information
  • The Encoding and Delivery Preference – How the Writer’s Mind Generates & Reports Information
  • The Mismatch Between Encoding, Decoding and Interpreting Information
  • Reader-friendly Technical Reports
• Technical Report Objectives – Primary, Secondary, Tertiary
  • The Audience and Your Assumptions
  • Information (including Data) and Details Required
  • Quality of Information – its Levels
  • Information Reliability
  • Information Quality Control Tools and Techniques
  • Assessing Precision & Accuracy of Technical Reports
  • Components of a Technical Report
  • The Flow – Presenting Complex Technical Information
  • Writing Architecture – Paragraph Logic and Linking
  • Report Strategy Challenge – Becoming a Report Architect
• Technical Report Storyboarding
  • An Analysis of the Best Reports
  • How Did They Tell the “Story”?
  • Nature of Quality, Professional Reports
• Technical Report Writing -Summary and reporting format.
  • The Clarity in Reporting – Use of Emphasis, Concise Active Voice
  • Abbreviations, Acronyms and Double Meanings
  • Why Readers Become Confused
  • One Person’s Jargon Is Another Person’s Vocab
  • Technical Report Tones for Style and Impact
  • Using Bullet Points and List.
  • The Art of Managing Redundancy
  • Visual Literacy – Using Images, Charts, Graphs, Pictures, Diagrams, Sketches, Tables
  • Reducing the Access Time to Critical Information