Daily activities need weekly feedback; strategic…
For daily activities, if feedback latency exceeds one week, or for strategic activities if latency exceeds one month, design a leading indicator or checkpoint that shortens the delay before drift compounds.
When This Fires
- After measuring feedback delay (Measure feedback delay in actual time units before…) and finding it exceeds the relevant threshold
- When designing feedback systems for new activities or initiatives
- When an activity has been drifting for an extended period before anyone noticed — the feedback loop was too slow
- During system reviews when evaluating whether feedback cadences match activity frequencies
Common Failure Mode
Accepting long feedback delays for high-frequency activities: "We'll see quarterly results for our daily social media posting." By the time quarterly results arrive, 90 days of posting strategy are locked in — and if the strategy was wrong from week 2, 76 days of effort were wasted. A weekly engagement metric (leading indicator) would have caught the problem in the first 7 days.
The Protocol
(1) For each recurring activity, identify two timescales: how often does the activity occur (daily, weekly, monthly?) and how long until feedback on its effectiveness arrives? (2) Apply the thresholds: daily activities → feedback must arrive within 1 week. Weekly activities → feedback must arrive within 2-4 weeks. Monthly/strategic activities → feedback must arrive within 1 month. (3) If latency exceeds the threshold → design a leading indicator or checkpoint to shorten the effective delay. (4) The leading indicator can be a proxy metric (Substitute a faster noisy signal for a slower precise one…), a structured self-observation (After recurring activities, spend 60 seconds recording…), or a scheduled review point that forces assessment before the natural feedback arrives. (5) The goal is that no activity runs for longer than one threshold period without at least one feedback-driven course-correction opportunity.