Instrument before executing — drift detection requires baselines that must exist before deviation starts
Design measurement infrastructure before executing strategies rather than after problems become visible, because drift detection requires baseline instrumentation that must exist before deviation occurs.
Why This Is a Rule
Drift — gradual deviation from intended behavior or outcomes — is invisible without a baseline to compare against. If you don't measure your starting point before beginning a strategy, you can't determine whether current performance represents improvement, degradation, or stasis relative to where you started. You can only compare to what you remember, and memory of initial conditions is unreliable and systematically biased.
This is Build measurement systems when you design the strategy, not after problems appear — crisis instrumentation measures symptoms, not causes (build measurement concurrent with strategy) narrowed to the specific requirement for baselines. Concurrent design ensures you capture the pre-change state that gives all subsequent measurements meaning. Without it, your first measurement is already post-change — you've lost the reference point.
The practical consequence: if you launch a new process without baseline measurements, and three months later the process seems to be working, you can't quantify how much improvement occurred. If it seems to be failing, you can't determine whether it's actually worse than before or just mediocre-as-always. The baseline is the foundation of every before/after comparison.
When This Fires
- Before executing any new strategy, process change, or initiative
- Before implementing any intervention whose effectiveness you want to evaluate
- When someone proposes measuring effectiveness "after we get going" — the baseline must be captured now
- Complements Build measurement systems when you design the strategy, not after problems appear — crisis instrumentation measures symptoms, not causes (concurrent instrumentation) with the specific baseline-capture requirement
Common Failure Mode
Retroactive baselining: "Let's look at last quarter's data to establish a baseline." If last quarter's data wasn't captured with measurement intent, it may be incomplete, measured differently, or missing the specific metrics you need for comparison. True baselines are captured deliberately, with the same instrument that will measure post-change performance, at a defined moment before the change.
The Protocol
(1) Before any strategy execution begins, define: what will you measure to determine whether the strategy is working? (2) Measure those specific metrics now, before the strategy launches. This is your baseline. (3) Use the same measurement method (same instrument, same time window, same definitions) for baseline and ongoing measurement. Methodological consistency is essential for valid comparison. (4) Document the baseline measurements explicitly: "On [date], before [strategy] launched, [metric] was at [value]." (5) Compare ongoing measurements against baseline, not against memory or intuition. The baseline is the objective reference point that subjective recall cannot provide.