Daily activities need weekly feedback; strategic activities need monthly — longer delays let drift compound undetected

Why This Is a Rule

Drift — gradual deviation from intended behavior or outcomes — compounds over time. Each day of uncorrected drift adds to the accumulated deviation. If feedback arrives weekly for a daily activity, up to 7 iterations of drift can compound before correction is possible. If feedback arrives quarterly for a strategic initiative, 90 days of strategic drift compound before the next checkpoint.

The thresholds — one week for daily activities, one month for strategic activities — represent the maximum acceptable compounding window for each frequency class. Daily activities (writing, exercise, communication habits) change rapidly enough that weekly feedback catches drift before it becomes entrenched. Strategic activities (market positioning, team development, skill building) change slowly enough that monthly feedback catches directional drift before resources are significantly misallocated.

When feedback latency exceeds these thresholds, the intervention is to design a leading indicator (Substitute a faster noisy signal for a slower precise one — speed compensates for noise in feedback loops) or checkpoint that provides interim signal. The checkpoint doesn't need to be as precise as the final feedback — it just needs to detect drift early enough for correction before the compounding becomes costly.

When This Fires

• After measuring feedback delay (Measure feedback delay in actual time units before improving — unmeasured delays appear shorter than they are through habituation) 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 — speed compensates for noise in feedback loops), a structured self-observation (After recurring activities, spend 60 seconds recording output + potential change — convert open-loop repetition into closed-loop learning), 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.