The Derivation Method: Finding the One Fact Everything Else Depends On

A operational system usually has a small number of things that are actually measured, and a much larger number of things that get reported as if they were separately measured when they're really just derived from the first ones through fixed, known relationships.

A real example: a foundry production system HSA's founder built in 2014 started from one fact — a cast part's weight. A fixed recipe ratio connects mould volume to metal volume; density connects volume to mass on both sides of that ratio. Sum that across every mould on a machine and you have material usage. Count the moulds and you have machine time. Machine time against headcount gives productivity. None of that required five separate measurements — it required one measurement and the ratios already built into how the process works.

Once a system's numbers are laid out as a derivation chain instead of a pile of separately-tracked metrics, the step with the worst ratio of input to output is usually visible without a separate investigation — it's the same work that produced the rest of the chain, not an additional step.

This is the reasoning pattern a Constraint Discovery Engagement is built around: find the one real, measured fact a business's operation actually depends on, trace what's derived from it, and let the constraint show itself in that structure — rather than starting from a checklist of things to measure separately.