> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/cognitive-tools/ux-laws-principles/foundations/poka-yoke-principle.md). # Poka-Yoke Principle The Poka-Yoke Principle is a concept originating from Japanese manufacturing processes, particularly associated with the Toyota Production System. "Poka-Yoke" translates to "mistake-proofing" or "error-proofing." The principle aims to prevent or detect errors during manufacturing or processing to avoid defects in the final product. There are two main approaches to Poka-Yoke: 1. **Prevention**: This involves designing processes or systems in a way that makes errors impossible or extremely difficult to occur. For example, using shape-coded connectors that only fit into corresponding slots prevents assembly mistakes. 2. **Detection**: This approach involves implementing mechanisms to detect errors as soon as they occur so that corrective action can be taken promptly. An example is an alarm that sounds when an incorrect part is inserted into a machine. The Poka-Yoke Principle is about designing systems and processes with built-in safeguards to ensure quality and prevent errors or defects from occurring. It promotes efficiency, reduces waste, and enhances overall product quality. #### Further Reading {% embed url="" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.designreference.xyz/cognitive-tools/ux-laws-principles/foundations/poka-yoke-principle.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.