A sixty-day turnaround and a decision I still think about years later ran on the same instinct, at two very different speeds. Most people assume fast and careful require different mindsets. They don’t — they require accurate classification.
I once reversed a failing operation in sixty days. I have also sat with a personnel decision for years that I still cannot fully resolve. Both used the same underlying instinct, running at two very different speeds. Most leadership advice treats speed and diligence as opposite ends of a dial — more of one automatically means less of the other. That is wrong for a specific and important category of decision, and getting the category wrong is where most leaders actually get hurt.
The claim, and the framework it has to answer to
This idea is not new, and it deserves to be credited honestly. Jeff Bezos, in his 2016 shareholder letter, drew the well-known distinction between one-way doors and two-way doors — decisions you can reverse if you’re wrong, and decisions you can’t. It is one of the most cited frameworks in operating leadership for good reason: it is correct. Reversible, bounded-risk decisions should be made fast, with incomplete information, because the cost of being wrong is low and the cost of moving slowly is real. Irreversible, structural decisions deserve real deliberation, regardless of how much pressure exists to move quickly.
What I want to add to that framework, from the operating floor rather than the boardroom, is this: knowing the category exists is not the same skill as classifying the door you are actually standing in front of, under real time pressure, when everyone around you is confidently calling it one thing and you suspect it might be another. That misclassification — not ignorance of the concept — is where I have seen leaders, including myself, actually get it wrong.
The fast case
The operation I reversed in sixty days had failed its certification and had a fixed window to recover. Every specific action I took inside that window — which processes to re-inspect, which habits to correct, which reports to demand daily instead of weekly — was a two-way door. If a specific correction did not work, I could adjust it the next day at almost no cost. That is exactly why sixty days was enough time. I was not making one large irreversible bet. I was making dozens of small, fast, correctable ones, and testing each one in real time instead of trying to design the perfect intervention in advance.
The slow case
Contrast that with a personnel decision I made earlier in my career, under a real deadline, where I removed someone from a role because the operation’s performance gap required faster progress than I believed that person’s development curve could deliver. The unit’s performance recovered. What I did not fully account for at the time was that this was not a two-way door. There was no version of events where the decision, once made and acted on, could be quietly reversed without real cost to the person affected — and I have never been fully certain the timeline pressure I was operating under justified moving as fast as I did. I do not resolve that story into a lesson. I carry it as a reminder that the decision deserved more deliberation than the fast-moving operational tempo around it was giving me room for.
The actual failure mode
The mistake is almost never applying diligence to a two-way door — that just costs you some time you didn’t need to spend. The expensive mistake is applying two-way-door speed to a one-way-door decision, because the organizational pressure to look decisive rewards visible speed regardless of which category the decision actually belongs to. Nobody gets credited in the moment for saying “I need another week to think about this.” Everybody gets credited for saying “done” fast. That asymmetry is what pulls leaders toward misclassifying doors under pressure.
The reader’s application
Before your next consequential decision, ask one question before anything else: if this goes wrong, can I actually undo it, or am I only telling myself I can because undoing it would be fast? Test the reversibility claim itself before you decide how much speed the decision deserves. Trust what’s tested. Not what’s told — including what you are telling yourself about how reversible a decision really is.
Scott Pleus is an operating executive who has built his career on a single conviction: an organization’s confidence in its own readiness is only as good as the last time someone actually tested it. If nobody told you your numbers were good, would you still believe them? That conviction was forged over three decades of command in the United States Air Force, retiring as a Lieutenant General and the longest-serving Acting Vice Chief of Staff in the role’s 79-year history. His command experience is the civilian equivalent of running large, high-consequence operations at every level of scale — from a single division, to a joint international operation, to the number-two position in a 680,000-person global organization. In every one of those roles, the product was readiness, and there was no such thing as a plausible excuse for being wrong about it. His standard, in his own words: accountable, not responsible. That is the experience most executive backgrounds don’t have, and it is what any organization needs when it wants to know — not hope — that it can perform under pressure. Early in his career, he noticed something worth learning from: a self-assessment that had never once produced a failure. Rather than take that as good news, he treated it as a signal that the test itself needed to evolve. He built a new version of the check — one that measured real readiness instead of rehearsed readiness — and kept refining it, even when the organization pushed back, because he was committed to the standard underneath it, not just the version of it that was easiest to pass. That same instinct shaped how he led. He made a habit of showing up unannounced, not to catch anyone, but to see the organization as it actually ran day to day — and to ask the one question a prepared briefing never answers. That habit paid off when he inherited a struggling unit: he gave its two senior leaders a clear deadline and clear ownership of the turnaround, and in sixty days, the unit had rebuilt the standard for itself. The stakes in his operating environment left no room for a wrong answer — there was no version of a readiness failure that was merely inconvenient. That is precisely why the discipline transfers: an executive who has enforced a verification standard with zero margin for error brings a rigor to operating risk that most executive backgrounds never have to develop. Trust what’s tested. Not what’s told.
