Account for delays between action and effect

Identify where the time lag is between cause and consequence before you diagnose a problem.

Why it works

Delays are one of the most common sources of systems surprises: an action is taken, nothing appears to happen, so the action is repeated — and then the accumulated effect of multiple actions arrives simultaneously. Senge calls this "policy resistance": the system looks unresponsive until it suddenly overcorrects. Knowing where the delays are in a system prevents both premature correction (quitting a strategy before it has had time to work) and overcorrection (doubling down on something that has already done its work, whose effects just have not arrived yet).

How to do it

1. For any intervention you plan, estimate the time delay before the effect will be visible.
2. Ask: "If I’m not seeing results yet, is it because the intervention is not working, or because the delay has not elapsed?"
3. Mark the delay on a causal loop diagram and check whether your planned feedback frequency is appropriate for it.
4. Set a calendar reminder to evaluate the intervention at the end of the delay period, not before.

Evidence

The role of delays in system oscillation and policy resistance is mathematically well-established in control theory and is extensively documented in system dynamics simulations and organizational case studies. (mechanistic)

Estimating actual delay times in social systems is difficult and imprecise; the practice reduces but does not eliminate misjudgments about timing.

Sources

• Forrester (1961), Industrial Dynamics — original treatment of delay effects in organizational systems

Common mistake

Abandoning a strategy during the delay period and switching to a new one, which resets the delay clock — a pattern that produces constant change with no results and is usually misdiagnosed as a "strategy problem" rather than a patience problem.