By the time a plan is clearly failing, you’re the worst-placed person to call it. You’ve already invested - time, budget, credibility - so every reason to keep going feels compelling. “We’re almost there.” “Let’s give it one more sprint.” “We’re too far in to stop now.” The data says change course; you explain it away.
You can’t make this call well in the moment - because in the moment, you’re attached. So you make it earlier, before you’re invested, when you can still see the plan clearly. You set the trigger in advance: the specific thing that, if it happens, means you change course - no re-arguing.
You’re protecting future-you from present-you. A calmer, more objective version of you makes tomorrow’s hardest decision today - before emotion gets involved.
Imagine this: at the start of a project, the team agrees: “if we haven’t landed a paying customer by end of Q2, or if the core integration slips twice, we stop and rethink.” Three months later, the integration slips for the second time. The trigger has fired, so the team changes course - no debate, because the decision was already made before anyone was emotionally invested.
You set the trigger in advance. While you’re still clear-headed - before the plan is failing and before you’re invested - you decide what would tell you to change: a specific event or a date by which you must have seen a specific result.
You write it down. “If X happens, or by date Y we haven’t seen Z, we change course.” Concrete enough that when it fires, it’s unambiguous - present-you can’t explain it away.
You trust the trigger when it fires. When the condition hits, you change - without re-arguing whether it really counts. The decision was already made by a clearer-headed version of you. That’s the whole point.
Team ✓ About 20–30 minutes, with a facilitator, set at the start of a plan.
The time required is indicative and will depend on how many triggers you set and how much the team debates the lines.
The facilitator should read the short facilitation guide first - about 6–8 minutes. It is a downloadable PDF on this page.
Set the trigger at the start of a plan - while you’re still clear-headed and not yet attached.
Use it whenever:
You’ve done it well when: the trigger is specific enough that, when it fires, the team changes course without re-arguing whether it counts.
Once you’ve invested time, money and credibility, stopping feels like failure - even when the evidence says it’s the right call. Setting the trigger before you’re attached lets a clearer-headed version of you make the decision. And when the trigger is concrete, there’s nothing left to argue about when it fires: “does this really count?” has no room to operate.
A plan early enough to change. A plan or initiative early enough that change is still possible - and that you’re not yet invested. The trigger has to be set before attachment, not after.
A clear change trigger. The specific event or missed result that would genuinely mean it’s time to change course - named plainly, while you can still say it. (Not only failure: this protects good plans too.)
A date or an event to bind it to. The trigger is event-based (“if X happens”) or date-based (“by Y we haven’t seen Z”), or both. Concrete enough to fire without debate.
A facilitator. One person keeps the trigger specific and records the final commitment on the capture sheet - and, later, holds the team to it when it fires.
Output
You leave with:
Important rules
Planning to facilitate this activity? Access the resources below to get started.