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

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

 Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims:  Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)