This page summarize the process for handling gap-from-standard problems documented in the Four Types of Problems. Examples from the daily work of software delivery are included.
The seven step process is effectively a larger PDCA loop, where the final step spreads effective countermeasures across the organization.
Explain the problem using narrative. Consider four points:
You’re ready for step two when you have an easily transmissible description of the current condition including the expected outcome and the gap. This is typically time series graphs or other visual representations.
This step is a detailed continuation of the previous step. This is where you zoom in to the specifics and break the problem down into addressable chunks.
The AQD (Analytical, Quantitive, Detailed) acronym will help you refine the problem definition.
Analytical means deconstructing the problem into small parts so you can analyze the cause-effect relationship. Ultimately, you want to end with describable problems that addressing them will impact the larger system.
Quantitate refers to the measurable aspects of the system.
Detailed is a continuous converging process. Problem solvers continuously focus on details until the problem is defined and scoped. Apply these three principles:
<aside> 💡 Genchi and genbutsu are typically shortened to genchi genbutsu.
</aside>