Define the system and unit of analysis
Specify process, population, product, time window, boundaries and aggregation level. Without a defined unit of analysis, measures and comparisons may represent different phenomena.
Structures a complete PDCA with team, current state, target, measures, causes, solutions, actions, verification, standardization and decision.
Before opening a form, define the question that must be answered. A management tool is useful when it reduces ambiguity, exposes assumptions and makes clear which decision will be made from the evidence produced.
PDC-02How can current state, target, causes, countermeasures, execution, verification and standardization be connected in one management logic?
Continuous improvement requires separating opinion from evidence and turning a broad problem into a sequence that can be observed, tested and revised. The tool creates value when it starts from an explicit current condition, applies criteria before concluding and ends with a verifiable decision — not merely a completed document.
Use it when you need to reduce variation, solve recurring problems, test changes, prioritize causes or preserve learning beyond the meeting in which it was produced.
An improvement cycle creates temporal discipline: plan with a hypothesis, execute under control, observe effects and decide the next move. Closing the cycle should produce reusable knowledge, not merely confirmation that a task was completed.
Specify process, population, product, time window, boundaries and aggregation level. Without a defined unit of analysis, measures and comparisons may represent different phenomena.
Translate abstract concepts into operational definitions, scales, classification rules and data sources. Criteria should exist before the result to reduce retrospective interpretation.
Link each conclusion to data, observations, assumptions and owners. When a score is used, retain its components; when a hypothesis is used, record how it will be tested.
Compare what was observed with what was expected. Record deviations, test conditions, data and the rationale to adopt, adapt, standardize or test again.
On a line with 91% FPY, the target is 97%. The complete PDCA stratifies defects, tests parameter countermeasures, tracks weekly FPY and scrap, and changes the standard only when the gain is sustained.
The example is intentionally specific. Numbers illustrate the reasoning and are not universal benchmarks: limits, scales and targets must be defined for the process being analyzed.Measures should serve reasoning. Whenever possible combine outcome, process and contextual evidence. For time series, look for patterns and variation rather than only point-in-time before/after comparisons.
Ask whether another person, using the same definitions and evidence, would reach a similar interpretation. If the answer depends heavily on individual judgment, refine the operational definition, scale or data source.
Established method/tool in professional and academic literature; exact implementation should be tailored to context.
The main risk is retrofitting the stages to justify a preselected solution. Maintain traceability between cause, countermeasure and effect.
Define an owner, review frequency, official data source and condition for reopening the decision. Link actions to deadlines and indicators, hypotheses to tests, and risks to treatment and follow-up.
The references below support the methodological family or principle used. Struckel’s digital implementation operationalizes application, documentation and traceability; it does not change the conceptual limits of the original sources.
ISO/TC 176/SC 2. The Process Approach in ISO 9001:2015.
Montgomery DC. Introduction to Statistical Quality Control. Wiley.
Struckel Forms offers a free way to structure this methodology with guided fields, contextual help and print/PDF preparation. Use the tool to organize reasoning; use consulting when the challenge requires design, implementation, facilitation or executive follow-up.