Schedule reviews at intervals shorter than natural feedback latency — forcing functions tighten loops that can't be structurally accelerated

Why This Is a Rule

Some feedback loops have inherently long delays that can't be structurally shortened. You can't get annual health check results monthly. You can't observe the impact of a strategic pivot in less than a quarter. You can't see whether a mentoring investment paid off in less than a year. When the natural signal is this slow, you're operating blind between signals — and blind operation in a changing environment produces drift.

Forcing functions — scheduled reviews at intervals shorter than the natural latency — create artificial checkpoints that substitute for the missing natural feedback. A weekly review forces you to assess progress on a project whose natural feedback (delivery outcome) won't arrive for months. A monthly retrospective forces evaluation of team dynamics whose natural feedback (retention, performance) takes quarters to materialize.

The key calibration: the forcing function interval must be shorter than the natural feedback latency. If strategy feedback takes 6 months, quarterly reviews provide two checkpoints before the natural signal arrives. If project feedback takes 3 months, monthly reviews provide two checkpoints. The goal is at least 2-3 forced observations between natural signals to detect drift before it compounds.

When This Fires

• When Measure feedback delay in actual time units before improving — unmeasured delays appear shorter than they are through habituation (measure delay) reveals feedback latency that can't be shortened
• When designing review cadences for long-duration initiatives
• When operating in domains where natural feedback is inherently slow (health, strategy, relationships, learning)
• When you're already using leading indicators (Substitute a faster noisy signal for a slower precise one — speed compensates for noise in feedback loops) but want additional structured checkpoints

Common Failure Mode

Setting forcing functions at the same interval as natural feedback: "We'll review the strategy quarterly, which is when results come in." This provides zero additional checkpoints between natural signals — the forcing function and the natural feedback arrive at the same time. The review interval must be shorter to provide useful early warning.

The Protocol

(1) Identify the natural feedback latency for the activity or initiative. (2) Set the forcing function interval at 1/2 to 1/3 of the natural latency: 6-month feedback → monthly or bi-monthly reviews. 3-month feedback → monthly reviews. 1-month feedback → weekly reviews. (3) At each forcing function, review: are leading indicators (Substitute a faster noisy signal for a slower precise one — speed compensates for noise in feedback loops) trending as expected? Has the context changed since the last check? Are assumptions still valid? (4) Document the review — even "on track, no changes" is worth recording to maintain the review habit and create a baseline for detecting when drift begins. (5) The forcing function is itself a behavioral agent (Document every agent with five components: Name, Trigger, Conditions, Actions, Success Criteria — undocumented agents degrade silently) with a time-based trigger — apply the same design principles to ensure it fires reliably.