An operating system, not a methodology
Six principles, a twelve stage decision chain running from structural design through execution feedback to the data foundation underneath it, and a control layer of architecture, policy, people, measurement and proof. Select any node to open its definition, worked example and self test.
Layer 1 · Principles
Layer 2 · The decision chain
Layer 3 · Control layer
Twenty steps, in dependency order
Not the order of the process. The order in which the model becomes understandable: outcome first, then its control mechanism, then its precondition, then the machinery.
Move the input, watch the system answer
Each model is illustrative and deliberately simple. The point is the direction and the shape of the response, not a forecast of your own numbers.
Show the numbers
The working vocabulary
Terms and metric abbreviations as the model uses them. Metric definitions and targets are organisation specific unless stated.
What each KPI measures, and how it is counted
Metrics are diagnostic instruments, not scorecards. Each entry gives the definition, the counting logic, and the distortion that most often makes the number lie. Read the set as a stack: master data feeds plan performance, plan performance feeds execution, execution feeds customer service.
It rarely fails through missing documents
It fails through design decisions nobody made, or made once and never revisited. Each pattern breaks a specific principle, which is what makes it diagnosable rather than merely regrettable.