Intervention Point Review¶
Decision review — instantiates Circular Causality Mapping
Uses the loop map to compare candidate places for damping, amplifying, redirecting, monitoring, or redesigning the feedback structure.
An Intervention Point Review is the downstream decision step that takes a finished loop map and asks the one question mapping defers: given this structure, where should we act, and how hard? Its defining feature is comparative evaluation of already-identified candidate points against each other — weighing each by how much of the behavior its loop actually drives, how the loops interact, and what would have to be monitored to know whether acting there worked. It does not build the map or elicit new links; it consumes a map and converts its intervention hypotheses into a ranked, monitorable decision. Crucially it separates where the leverage is from where the change is easy or visible, since the two rarely coincide and the map exists precisely to resist the pull toward the obvious symptom.
Example¶
An SRE team's on-call is drowning. A loop map already exists from earlier mapping: alert volume raises fatigue, fatigue slows and coarsens incident response, poor response lets incidents grow, larger incidents trigger more alerts — a reinforcing spiral — plus a delayed balancing loop where sustained pain eventually funds reliability work that reduces alerts months later. The review convenes to compare candidate intervention points, not to remap. On the wall are four: (1) hire more on-call engineers, (2) mute noisy alerts, (3) fund a reliability sprint to fix the top incident sources, (4) add an incident-severity router so serious pages aren't buried.
The review scores each against the map, drawing openly on Donella Meadows' ordering of leverage points — that changing rules and information flows usually beats adding capacity.[n1] Hiring (1) adds capacity but leaves the reinforcing loop intact; muting (2) cuts the alert-to-fatigue link but risks silencing real signals; the reliability sprint (3) attacks the loop's generating source but pays off only after a delay; the router (4) is a cheap information-flow change that weakens the fatigue link immediately. Because loops interact, the review recommends pairing the fast router with the slow reliability sprint, and — critically — attaches a monitoring plan: watch fatigue proxies and incident-growth rate weekly, and expect the sprint's effect only after the mapped delay, so nobody kills it early for looking inert.
How it works¶
- Take the map as given. Start from a finished loop map with candidate points already marked; the review evaluates, it does not elicit or redraw structure.
- Weight candidates by loop influence. Estimate how much of the observed behavior each candidate's loop actually drives, so a visually prominent but weak loop doesn't win attention.
- Read the interactions. Use the multi-loop overlay to see how acting on one loop shifts the others — whether interventions reinforce, cancel, or trigger a compensating loop elsewhere.
- Attach a monitoring design. For the chosen point, specify what signals to watch and over what window (respecting mapped delays) so the intervention's real effect can be told from noise.
Tuning parameters¶
- Leverage vs. feasibility weighting — how much the ranking favors high-leverage points over cheap, easy ones. Favoring leverage attacks the structure; favoring feasibility ships something now but may treat a symptom.
- Number of points compared — a shortlist versus every marked candidate. A short list forces focus; a long list guards against missing a sleeper high-leverage point.
- Portfolio vs. single pick — choose one intervention or a coordinated set. Portfolios can pair fast and slow loops but multiply monitoring burden and confound attribution.
- Reversibility preference — how strongly the review prefers moves that can be undone. High reversibility suits an uncertain map; low reversibility may be needed to actually break a strong reinforcing loop.
- Monitoring horizon — how long a window the plan watches before judging effect. Too short and a delayed intervention is abandoned as a failure; too long and a bad move runs unchecked.
When it helps, and when it misleads¶
Its strength is that it protects the leverage insight the map paid for: by scoring candidates on loop influence and interaction rather than on visibility or ease, it stops a team from spending its intervention on the loudest symptom. Pairing that with a delay-aware monitoring plan is what keeps a slow, structural fix from being killed before it can work.
Its failure mode is false confidence in the underlying map. A review that treats an unvalidated map as ground truth can rank interventions with spurious precision, and loop-strength estimates are especially soft — the "dominant" loop is often asserted, not measured. A classic misuse is to use the review to rationalize the intervention leadership already prefers, arranging the scoring to crown it. The guarding discipline is to treat the map's strengths as provisional, prefer reversible moves and staged commitment while the map is uncertain, and let the attached monitoring plan feed back to revise both the map and the choice.
How it implements the components¶
intervention_point_hypothesis— the review's object: it compares, ranks, and selects among candidate places to act rather than generating them from scratch.loop_strength_indicator— it weights each candidate by how much of the behavior its loop drives, so leverage rather than salience decides.multi_loop_overlay— it reads how acting on one loop propagates through the others, catching interventions that trigger a compensating loop.monitoring_plan— it attaches the signals and delay-aware windows that will reveal whether the chosen intervention actually changed the dynamic.
It does not build the map, name variables, or draw the links (loop_variable, causal_link, stakeholder_perspective_check) — that construction is the Feedback Analysis Workshop — and it does not verify polarity assignments (polarity_marker), which is Loop Polarity Review.
Related¶
- Instantiates: Circular Causality Mapping — it turns the map's intervention hypotheses into a ranked, monitorable decision.
- Consumes: Feedback Analysis Workshop or System Dynamics Mapping — the review needs a finished map with candidate points already marked.
- Sibling mechanisms: Feedback Analysis Workshop · Influence Mapping Interviews · Causal Loop Diagram · System Dynamics Mapping · Behavior-over-Time Graph · Root-Cause Loop Analysis · Loop Polarity Review · Policy Resistance Map · Scenario or Simulation Testing
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Intervention Point Review operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it uses the loop map to compare candidate places for damping, amplifying, redirecting, monitoring, or redesigning the feedback structure
Independent corroboration: The frozen evidence defines Intervention Point Review as 'Uses the loop map to compare candidate places for damping, amplifying, redirecting, monitoring, or redesigning the feedback structure', so its operative form is Decision, Gate & Allocation.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Systems Thinking & Cybernetics
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: Comparing places to damp, amplify, redirect, or redesign feedback is canonical systems-thinking leverage-point analysis.
Related originating lineages:
- Organizational & Management Science — Structured decision review contributes comparison, ownership, and monitoring of candidate interventions.
Review resolution: Both independent reviews place the primary lineage in systems_cybernetics. The queued differences (alternate_origin_disagreement, origin_mode_disagreement) concern secondary metadata rather than primary provenance. The final retains organizational_management only where a reviewer supplied a formative-lineage rationale; this does not convert downstream applicability into origin. origin_mode=convergent because the reviewers document independently established or materially co-developing traditions. domain_reach=universal records application breadth separately from provenance.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Donella Meadows' essay Leverage Points: Places to Intervene in a System ranks kinds of intervention by their power to change system behavior, arguing that shifting rules, information flows, goals, and paradigms is generally far more effective — and less intuitive — than adjusting parameters or adding capacity. ↩