🎓 CSSBB Quest › Learn

Poka-yoke at Black Belt level

Poka-yoke (Japanese: ポカヨケ, from poka, "inadvertent mistake", and yokeru, "to avoid") is a design principle that makes it impossible — or immediately obvious — to perform a step incorrectly. The concept was developed and popularized by Shigeo Shingo in the 1960s, in his work with Toyota. At the BB level, the exam expects you to classify, design, and evaluate poka-yoke solutions, not just recognize the term.

Why poka-yoke over training

Training-based solutions depend on human memory, attention, and discipline — all of which degrade under fatigue, distraction, and high-volume production. Poka-yoke solutions work regardless of human state. They are more reliable, and in the FMEA they lower the Occurrence rating (when they prevent the cause) or the Detection rating (when they detect the error or defect). The best poka-yokes prevent errors entirely (no inspection needed); the next best detect them immediately (before the next process step).

Two poka-yoke functions

Function	What it does	Example	FMEA effect
Control (shutdown)	Stops the process when an error is detected. The error cannot proceed.	Machine physically cannot close when part is loaded incorrectly; press stops if force exceeds limit	Lowers Occurrence (if the error is prevented) or lowers Detection to the lowest ratings (automated, proven detection that stops the part)
Warning (signal)	Alerts the operator that an error has occurred or is about to. Operator still must respond.	Alarm sounds when wrong reagent is selected; light flashes when weight is out of range	Lowers Detection, but less than a control function — the operator can still miss or ignore the warning

Control function > warning function in reliability. A warning that an operator can acknowledge and override is still a detection control, not a prevention control.

Three poka-yoke detection methods

Method	How it works	Example
Contact method	Detects shape, size, or position by physical or sensory contact with the item	A pin that prevents a bottle from loading unless the cap is correctly oriented; a vision sensor that reads a barcode to verify identity
Fixed-value method	Detects whether the correct number of actions or items is present (count-based)	A parts tray with a defined number of slots — operator cannot proceed until all slots are empty; a click-counter for fastener torque cycles
Motion-step method	Detects whether the steps were performed in the correct sequence or within the required motion range	A checklist interlock that requires electronic sign-off on each step before the next step is enabled; a timer that confirms an operator dwell time was met

Levels of mistake-proofing (effectiveness hierarchy)

Eliminate the step — redesign so the error-prone step is no longer needed. Highest leverage.
Substitute — replace a human step with an automated one that cannot make the mistake.
Prevent — physical or design constraint makes the error impossible (pins, asymmetric connectors, keyed fixtures).
Facilitate — make correct action easier than incorrect action (color coding, labels, spatial arrangement).
Detect and stop — device catches the error immediately and halts the process, so the defect cannot move on.
Detect and signal — device catches the error and warns the operator, who must react.
Mitigate — reduce the effect of an error that still gets through (least effective).

FMEA linkage: evaluating a poka-yoke proposal

When proposing a poka-yoke solution for a high-risk FMEA row, evaluate which ratings it actually changes. (The example uses RPN; the AIAG-VDA FMEA Handbook (2019) replaces RPN with Action Priority, shown at the end.)

FMEA row: Incorrect vial loaded → wrong fill volume → patient harm Before poka-yoke: S=10, O=4, D=6 → RPN=240 Proposed solution: Vision system + physical stop prevents wrong vial from seating → This is a CONTROL function, CONTACT method → Prevents the error: O reduces to 1 (failure can't occur if device works) → Vision system also detects any bypass: D drops from 6 to 2 After: S=10, O=1, D=2 → RPN=20 (92% reduction: 220/240) Note: Severity stays at 10 — the effect if it somehow still happened is unchanged. AIAG-VDA Action Priority: S=10, O=4, D=6 → High; after S=10, O=1 → Low.

Test yourself in 2 minutes

Try 5 free CSSBB practice questions on poka-yoke and mistake-proofing. No account needed.

Take the free CSSBB diagnostic

More: DMAIC overview · Project charter · VOC & CTQ · SIPOC · MSA in DMAIC · Process capability · Data collection planning · Graphical analysis · Root cause analysis · Multi-vari analysis · Hypothesis testing · Regression · DOE · FMEA · Define tollgate · Change management · Financial benefits · Team dynamics · Improve tollgate · Piloting & scaling · Poka-yoke (BB) · Solution selection · Control plan · SPC in DMAIC · Sustaining gains

CSSBB Quest by Bizarre Act. Original study material; not affiliated with ASQ. CSSBB is a certification of ASQ. Terms · Privacy