Commitment & Rollback Toolkit
For hiring, pricing, or architecture moves that are hard to undo.
- Time
- 45-60 minutes per major commitment.
- Who
- Decision owner, finance owner, delivery owner, and communications counterpart.
- Decide now
- Approve or reject the commitment, and name who can roll it back, now.
- What it gets you
- A decision note that names the rollback trigger before any money that cannot be recovered is spent.
- What you leave with
- Signed commitment note with rollback trigger register and comms packet.
What to do at each pace
- • Do now in tighter conditions: Shorten the rollback window and set the trigger thresholds earlier.
- • Do now in easier conditions: Widen the experiment's scope; keep one named person able to roll it back.
- • Go ahead when: Proceed only when the unwind cost, the owner, and the trigger thresholds are written down.
- • Pause if: Stop expanding the commitment when a leading indicator crosses a trigger in the register.
- • Restart when: Roll back immediately when the trigger owner calls it.
By pace: When conditions say slow down, set the rollback triggers earlier; when they say speed up, widen what an experiment may try.
Prep checklist
- • Quantify sunk cost exposure at day 7, day 30, and day 90.
- • Pre-identify the metric dashboard that will be used to trigger rollback.
- • Draft customer and internal rollback messaging before the decision is approved.
Run sequence
Classify
Objective: Determine whether the commitment is reversible, partially reversible, or locked-in.
Prompts
- • What is the fastest path to unwind this decision within 30 days?
- • Which costs become sunk immediately after launch?
Deliverable: Reversibility classification with unwind cost estimate.
Pre-wire
Objective: Define observable signals that trigger rollback.
Prompts
- • Which two leading indicators tell us this move is failing early?
- • Who has the authority to trigger rollback in real time?
Deliverable: Rollback trigger register with thresholds and owners.
Rehearse
Objective: Check that the team can roll back without confusion.
Prompts
- • What sequence would we run in the first 24 hours of rollback?
- • Which customers, teams, or vendors must be informed first?
Deliverable: Pre-mortem and rollback communication plan.
Signs it worked
- • Rollback threshold and owner are written into the launch/commitment note.
- • A dry-run confirms teams can unwind within the stated window.
- • A review date is set before resources are committed.
What's in this toolkit
Common mistakes to avoid
- • Making irreversible bets without contingency paths