Substitute a faster noisy signal for a slower precise one…

When This Fires

• When the natural feedback signal for an activity takes weeks, months, or years to arrive
• When you're operating blind during a long feedback delay and want earlier warning
• When Measure feedback delay in actual time units before… (measure delay) reveals a delay that can't be shortened structurally
• When designing measurement systems for long-term initiatives (strategy, health, learning)

Common Failure Mode

Waiting for the "real" signal because the leading indicator is "too noisy": "Weekly traffic numbers fluctuate too much — let's wait for quarterly data." By the time quarterly data arrives, three months of potentially misallocated marketing effort have passed. The weekly fluctuation, while noisy, still reveals directional trends within 2-3 weeks — enough for meaningful course-correction that the quarterly signal can't provide.

The Protocol

(1) When feedback delay exceeds one cycle of the activity (Daily activities need weekly feedback; strategic…), identify a leading indicator: what faster, observable signal correlates with the delayed outcome? (2) Validate the correlation: does the leading indicator actually predict the final outcome, at least directionally? Test with historical data if available. (3) Accept the noise: the leading indicator will fluctuate more than the true signal. This is the cost of speed. Smooth the noise by looking at trends across 3-5 readings rather than reacting to individual readings. (4) Use the leading indicator for directional course-correction, not precise calibration. "We're trending in the wrong direction" justifies adjustment; "we're 3.2% below target this week" doesn't justify panic. (5) When the true signal eventually arrives, calibrate your leading indicator against it to improve the correlation over time.