Lesson 20: If You Can’t Write Your Escape Plan in One Sentence, You Don’t Have One
If you can’t sum up your escape plan in a single sentence, you don’t really have a plan at all. Sounds harsh, maybe, but when things go sideways in business, the difference between bouncing back and spiralling into disaster boils down to one moment of clarity: someone asks, “So, what do we do if this fails?” Either there’s an answer, or there isn’t.
Every big change in your operation should start with that question: If this blows up, what is the move? And you want specifics-not vague “we’ll figure it out,” or “we’ll call a meeting,” or “someone will escalate.” What actually happens? Who does it? What does everything roll back to while you work things out?
When nobody has a clear answer, small issues turn into major headaches. It’s not about skill or dedication, most teams have plenty of both. The problem is the reversal path everyone thought would be easy, suddenly isn’t. Everyone’s got different ideas about what “undoing” means, and now, under pressure, those gaps become real problems.
The solution is simple and way less complicated than most risk management docs make it seem. Instead of writing up huge contingency plans or maintaining a “risk register,” just write one sentence for every change. Yes, one. Attach it to the change before you do anything else.
The Rule: Every Change Needs a One-Sentence Escape Plan
By now, according to lesson 19 in the series, every delivery needs a reversal plan-one of three must-have items. Lesson 20 takes it even further: it’s not just about having a reversal plan, but making sure it’s clear, it works, and, honestly, the process of writing it matters as much as what it says.
Why one sentence? It’s a test. If you can explain the reversal in a single, clear line, you really understand it. You know what you’re switching back to, how you’ll do it, and who needs to know. If you need a full paragraph or lots of “ifs and buts,” that’s a sign you’re not ready yet. Better to catch that now, not when everything’s falling apart.
This applies to any kind of change: new processes, pricing tweaks, launching a campaign, updating systems, restructuring teams. The form changes, but the discipline doesn’t.
Case Study: “We Have a Plan” vs. “We Have a Working Plan”
Let’s look at a real scenario. The team had good habits: change tickets, documented reversal procedures, solid governance. And then – surprise!!!!, something went wrong. They want to run the reversal, only to find it was useless. The system had changed, backups were outdated, the person named in the plan had switched teams months ago.
So, the plan existed, but it didn’t work. Worst time to find out? Right in the middle of an incident, with customers affected and the clock ticking.
What did we do different? We started requiring a template for every change ticket:
“If [the change] fails, restore [what] from [where] and notify [who].”
No sloppy variations. Just a precise restoration, source, and notification. If any piece wasn’t nailed down, the change didn’t proceed.
Then we brought in monthly validation-randomly pick three recent changes, review the plans, and check: Is the backup still there? Is the owner still in place? Did something change that makes the plan useless?
Next time there was a failure, the team ran the reversal as planned. The backup was current. The owner was ready and reachable. Notification went out in minutes. Minimal customer pain. Recovery was twice as fast as before. And best of all, the team didn’t scramble, they followed a plan that had already been proven.
Having a reversal plan doesn’t guarantee nothing goes wrong. It just makes sure you can bounce back.
How to Actually Write a One-Line Reversal Plan (The Nuts and Bolts). Use this template:
“If [X] fails, restore [Y] from [Z] and notify [N].”
What goes in each slot:
- X – the change or action that could flop
- Y – what state, version, process, or condition you’re going back to
- Z – the exact source or mechanism for that restore
- N – who you’re telling, by name
Everything needs to be specific enough that someone with zero context can follow it under pressure, no questions asked. Where does it live? Stick the plan right on the change ticket, project brief, or wherever you document the change. Don’t bury it in a risk register nobody reads.
Ownership matters: Name one person. Not a team or “management.” The person’s name is on the plan, and they know they’re responsible before the change happens.
Then, monthly, pick three changes at random and ask:
- Is the backup actually usable?
- Is the owner still responsible?
- Has anything shifted since the plan was made that affects it?
If anything is off, update the plan before that operation moves forward. This drill takes less than twenty minutes and gives real confidence that things won’t go sideways.
Before delivery, review the one-line plan in your pre-launch readout. Make sure it exists, the owner understands it, and they’re ready if something breaks.
The Bigger Picture: Operations Don’t Have to Be Fragile
Twenty lessons of solid discipline add up to more than just a bunch of individual habits-they create a robust system. Processes are visible, failure points are fixed before they grow, signals and experiments are owned and reviewed, handovers are made explicit, deliveries are protected, retros turn incidents into improvements, SOPs make proven moves repeatable, redundancy covers gaps, and every change comes with a clear escape plan.
Each step is useful, but together, they shift your operations from brittle and reactive to reliable and resilient.
Let me drill down on this point this way:
“When fixes become SOPs, when people are doubled-up, and when every change carry a clear escape, operations stop being a fragile art and become a reliable discipline. Keep the artifacts tiny, the rituals short, and the ownership explicit, that is how any business operation produce big leverage.”
That has been the big goal: simple, visible habits that stack up into real operational strength. Not more complexity or red tape; just tiny, enforced steps with huge payoff.
The Honest Takeaway
Reversal plans only work if you practice them. Writing them is step one. Checking them often is what makes them reliable.
The teams I have mentioned had plans, but they didn’t check if they worked. That is where most contingency planning dies quietly -plans get made, things change, the plan sits, and the situation drifts away.
Monthly validation is the bridge. Just a little routine effort and suddenly, when things go south-and they will-the escape path is real, up-to-date, and ready.
Write it before the change. Validate it regularly. Name the owner, and treat the ability to reverse as a badge of good ops, not just a safety net for bad luck.
Take five recent changes in your org. For each one, is there a written reversal plan? Is it still accurate? Is someone actually responsible? If not, that’s where you should focus next.
Next time, I’ll dig into “Resilience, Automation & Customer-Connected Decisions”, see you then.