The PDCA cycle (Plan–Do–Check–Act) is an iterative method for continuous process improvement and problem solving. Teams plan actions, execute them, inspect results, and adjust processes accordingly. The cycle promotes systematic learning loops, measurable improvements, and can be applied across quality management, operations, and service delivery contexts.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
The PDCA cycle structures continuous improvement into Plan, Do, Check, and Act.
Walter A. Shewhart developed the iterative improvement cycle, and W. Edwards Deming spread it through quality management and manufacturing practice. PDCA names learning through planned trials and feedback.
Plan defines the problem, hypothesis, goal, and measurement. Do tests the change in a controlled way. Check compares observations with expectations. Act standardizes an effective change or adjusts the hypothesis and begins another cycle.
The team sets problem, goal, assumption, intervention, and measurement before the trial.
Observed results are compared with the goal and baseline.
The team adopts, corrects, or rejects the change and captures learning.
PDCA makes improvement traceable and experimental. It requires meaningful measures, short learning loops, and actual follow-through; documentation alone does not improve a system.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.