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



Labels:

Comments

Post a Comment

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...
Post a Comment
Read more

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...
Post a Comment
Read more

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .
Post a Comment
Read more