Build measurement systems when you design the strategy…

When This Fires

• When launching any new initiative, project, or strategy
• When building a new process or workflow — add measurement at the design stage
• When you realize a current initiative has no measurement system — retrofit is better than nothing, but note the limitation
• During project kickoffs when scope and success criteria are being defined

Common Failure Mode

"We'll figure out how to measure it later." Later arrives when something goes wrong and you have no baseline data, no leading indicators, and no causal metrics — only lagging symptoms. You spend weeks building instrumentation retroactively, and the metrics you choose are biased by the specific failure that prompted the crisis rather than the strategic model that should govern measurement.

The Protocol

(1) When designing any strategy or initiative, simultaneously design its measurement system. Treat measurement as a deliverable of the design phase, not a follow-up task. (2) Define: what are the causal levers this strategy pulls? What leading indicators will show whether those levers are working? What lagging indicators will confirm overall success or failure? (3) Set baselines before the strategy launches — you need "before" data to evaluate "after." (4) Build the dashboard or tracking system and verify it produces data before the strategy begins executing. (5) If you're joining an initiative already in progress with no measurement → retrofit. But acknowledge that the metrics you choose now are influenced by current conditions rather than original strategic intent. Review them with the original strategy document to check alignment.