Skip to content

Reopening Trigger Review

Post-commitment monitor — instantiates Divergence-Convergence Cycle Orchestration

Predeclares the specific conditions that would justify reopening a committed decision, then watches incoming reality against them so reconsideration is triggered by evidence, not by whoever complains loudest.

A commitment that can never reopen becomes a trap when the world moves; one that reopens on every objection never gets executed. Reopening Trigger Review threads this by settling the reopening question in advance: at the moment of commitment it writes down the specific, observable conditions — thresholds, deadlines, external events — that would make reconsideration legitimate, and it names, for each, which layer that condition would invalidate. Then it simply watches. Its defining discipline is that reopening is authorised by a predeclared trigger firing against recorded evidence, not by fresh advocacy, and that a fired trigger reopens only the narrowest layer it undermines — a criterion, an option, a dimension, or, rarely, the whole frame — rather than tipping the entire decision back onto the table.

Example

A city commits to a bus-rapid-transit corridor after a full divergence-convergence cycle. Before service opens, the review arms a small set of tripwires and binds each to a layer: if peak ridership is under a target by month nine, reopen the service-pattern layer; if bus-bunching exceeds a set frequency, reopen signal-priority; if the regional rail extension gets funded, reopen the corridor frame itself. Nine months in, ridership is healthy but bunching breaches its threshold. The review fires — but only on the signal-priority layer. The alignment, the stations, and the mode all stay committed; the team reopens exactly the sub-decision the evidence invalidated, pulls the pre-recorded rationale from the trace, and re-runs a bounded mini-cycle on frequency. What would otherwise have been a political argument about "the whole BRT was a mistake" is contained to the one layer the data actually challenged.

How it works

  • Predeclare triggers, not vibes. Each trigger is an observable condition — a metric threshold, a date, a named external event — tied to a specific assumption the commitment rested on.
  • Map every trigger to a reopen scope. A firing condition names the narrowest layer it invalidates, so reopening the criteria never means restarting the frame.
  • Monitor the trace against the thresholds. The review reads the decision's own record and telemetry rather than waiting for someone to raise a hand.
  • Fire, reopen the layer, and log it. When a trigger trips, the review authorises a bounded reopening of just that layer and records that it fired and why — so the learning accumulates instead of resetting.

Tuning parameters

The dials that adapt this monitor to a specific commitment:

  • Trigger sensitivity — tight thresholds catch problems early but risk thrash and relitigation; loose ones keep execution stable but can miss late evidence until it is expensive.
  • Reopen scope per trigger — how surgically each condition is mapped to a layer; coarse mapping turns any wobble into a full reopening, fine mapping contains it.
  • Review cadence — continuous monitoring versus scheduled checkpoints; continuous is responsive but noisy, scheduled is calm but laggy.
  • Trigger-versus-objection bar — what clears the threshold to count as a firing condition rather than ordinary grumbling that the commitment is meant to withstand.
  • Arming window — how long triggers stay live before the decision is allowed to harden into a durable commitment.

When it helps, and when it misleads

Its strength is adaptivity without amnesia: the decision can respond to disconfirming evidence and resist being reopened by whoever is loudest, because the terms of reopening were agreed before anyone knew who would benefit. It blunts both premature lock-in and endless cycling, and it keeps prior learning intact by reopening only the invalidated layer.

Its failure modes are mostly about how the triggers are set and honoured. Set too loose, nothing fires until outright failure and the review becomes decorative; set too tight, the project thrashes as every fluctuation trips a reopening. The classic misuse is political: a stakeholder who lost the original decision dresses a plain objection as a "trigger" to relitigate it, or — the mirror image — an inconvenient trigger is quietly disarmed when it threatens to fire.[1] The discipline that guards against both is to predeclare the triggers and their reopen scope at commitment time, bind each to a named assumption, and require the trace record to show that a condition actually fired before exploration reopens.

How it implements the components

Reopening Trigger Review fills the adaptive-capacity components that operate after commitment:

  • reopening_trigger — its core artifact: the predeclared conditions, each mapped to the layer it would reopen, monitored and fired against evidence.
  • learning_and_trace_record — the review both reads the trace to detect a firing and appends what fired and why, so each reopening compounds prior learning instead of erasing it.

It does not hold the alternatives a fired trigger switches to — those live on the Reserve Option Board — nor does it record the original selection, which is also the board's job. Deciding how much to invest at each stage is Stage-Gate Concept Review, not this monitor.

Notes

This monitor and the Reserve Option Board are a deliberate pair: the review decides when and whether to reopen; the board holds what to switch to. Keeping them separate is what stops "reopening" from silently meaning "start over" — a fired trigger should hand off to a live reserve, not to a blank page.

References

[1] Committing in advance to a concrete condition that will force reconsideration — so a drifting situation gets a scheduled second look instead of sliding unexamined — is the tripwire discipline described by Chip and Dan Heath in Decisive. A reopening trigger is a tripwire pointed at a specific layer of an already-made decision. ↩