Skip to main content

Poka Yoke - Six Sigma

What is Poka Yoke?

  •  PokaYoke can be translated as “Mistake Proofing”.
  • Eliminate error before occur rather than finding and fixing them

The ideal Poka Yoke are:

  1. Inexpensive
  2. Simple and easy to implement
  3. Deployed to every employee

The 2 types of Poka Yoke are:

The two main types of Poka Yoke (mistake-proofing) are generally categorized by their function in relation to the error:

  1. Prevention Poka Yoke (Control Method): These techniques are designed to make it physically or logically impossible for an error to occur in the first place, or they automatically stop the process immediately when an error is detected, forcing corrective action. This is the most effective type.

    • Example: A microwave oven that will not turn on if the door is open.

  2. Detection Poka Yoke (Warning Method): These techniques are designed to detect an error as soon as it happens and alert the operator, so they can take corrective action before the mistake becomes a defect that moves further down the process or reaches the customer.

    • Example: A buzzer that sounds if a car is turned off but the headlights are still on.

The three primary methods used for implementing either the Prevention or Detection types are:

  • Contact Method: Uses physical attributes (shape, size, color, etc.) to detect errors (e.g., a uniquely shaped connector that only fits one way).

  • Fixed-Value Method/ Constant Number Type: Ensures a set number of actions or components are used (e.g., a container with the exact number of parts needed for an assembly step).

  • Motion-Step Method (or Performance Sequence Method): Ensures a correct sequence of operations is followed (e.g., a system that won't allow the next step to start until the previous one is confirmed).

Poka Yoke 3 Golden Rules:
  1. Don't accept defects from your suppliers
  2. Don't make your defect yourself
  3. Don't pass on a defect to your customer



Comments

Popular posts from this blog

Voice of the Customer (VoC) vs Voice of the Business (VoB)

  Tthe differences and strategic importance of Voice of Business (VoB) and Voice of Customer (VoC) in Lean Six Sigma: Voice of Business vs Voice of Customer: Aligning Strategy with Value In the world of Lean Six Sigma , success hinges on understanding and balancing two critical perspectives: the Voice of the Customer (VoC) and the Voice of the Business (VoB) . While both are essential for driving sustainable growth and operational excellence, they represent distinct priorities that must be harmonized for optimal results. 🔊 Voice of the Customer (VoC) Definition : VoC refers to the needs, expectations, preferences, and feedback of the customer—whether internal or external. Focus Areas : Product/service quality Delivery timelines Customer experience Responsiveness and support Methods of Capturing VoC : Surveys and interviews Focus groups Customer complaints and feedback Net Promoter Score (NPS) Goal : To ensure that processes and outputs are aligned with what the customer truly ...

Control Chart in Lean Six Sigma

Control Chart in Lean Six Sigma Introduction In Lean Six Sigma , a control chart is a fundamental statistical tool used to monitor process performance over time and ensure that improvements are sustained . It belongs primarily to the Control phase of DMAIC , where the focus is on maintaining process stability and preventing regression after improvements have been implemented. A control chart helps distinguish between normal process variation and abnormal variation that requires investigation and corrective action. What Is a Control Chart? A control chart is a time-ordered graphical display of process data with statistically determined limits. It answers a critical question: Is the process stable and predictable, or is something unusual happening? A typical control chart consists of: Center Line (CL) – the process average or mean Upper Control Limit (UCL) – upper boundary of expected variation Lower Control Limit (LCL) – lower boundary of expected variation Plotted data points o...

Defect Leakage

Defect leakage occurs on the Customer or End User side after the delivery of the application. Once the application has been released to the client, if the end user gets any kind of defect using the application, it is called "Defect leakage". Formula for Defect Leakage: Defect Leakage = Number of Defect found during next phase / ( Number of Defects found during testing + Number of Defects found during next phase) * 100 For Example, During the UAT production site, 50 defects were detected by the end users and 150 defects were detected throughout the QA process, including both the test site and the production site. Therefore, the defect leakage would be: Defect Leakage = (50/150)*100 Defect Leakage =33 % Reasons for Defect Leakage: Absence of stringent test cases walkthrough and review process. Environment differences. Missing test cases to cover appropriate condition. Poorly designed test case due to misunderstood requirements. Incorrect deployment in UAT or production. Use of ...