> 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

Designing a process to prevent or correct human errors before they occur

The Poka-Yoke Principle is a concept originating from Japanese manufacturing processes, particularly associated with the Toyota Production System.&#x20;

"Poka-Yoke" translates to "mistake-proofing" or "error-proofing."&#x20;

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="<https://uxknowledgebase.com/the-poka-yoke-principle-in-ux-design-20aeb771de5f>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.designreference.xyz/cognitive-tools/ux-laws-principles/foundations/poka-yoke-principle.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
