Some mistakes get corrected and forgotten. Others just become part of what you are. Here is how to tell the difference, and what to do with the second kind.
Every operator I know has a list. Mine has three or four decisions I would take back if I could, and I can’t, so I have had to learn to operate with what they built instead of waiting to resolve them. This piece is about that second category — not the mistakes you fix and move past, but the ones that just become part of the record, permanently, and the different discipline that requires.
Most leadership writing about mistakes treats them as lessons: something happened, you extracted the learning, you moved on wiser. That model works for a large share of the mistakes any leader makes. It does not work for all of them. Some decisions do not resolve into a lesson. They just sit there, unresolved, as part of your operating history, and the job is learning to carry that weight rather than waiting for it to convert into wisdom.
Two different categories
It is worth being precise about the distinction, because conflating the two categories produces bad advice in both directions. A correctable mistake is one where the cost can be reversed, apologized for, or absorbed without lasting structural effect — a bad call that gets caught in time, a miscommunication that gets cleared up, a wrong decision that simply gets replaced with a better one before the cost compounds.
A structural decision is different. It is usually a personnel call, a resource allocation, or a moment of genuine enforcement that produced a second-order cost nobody fully saw coming — and once it has played out, there is no version of events where it did not happen. You cannot apologize your way back to the moment before the decision. You can only decide how you operate with it afterward.
One decision, plainly told
Early in an assignment where I inherited an operation with a serious performance gap, I made a personnel change I believed the standard required. The person I moved out had genuine strengths, had been loyal under difficult conditions, and by any reasonable accounting deserved more patience than the timeline I was working under allowed. I made the change anyway, because the unit’s performance gap was real and the clock on fixing it was shorter than the clock on developing that person into the role.
The unit’s performance improved. That part of the calculation was correct. What I did not fully account for was the cost to that individual’s career trajectory — a cost that, several years later, I learned had been more significant and more lasting than I had estimated at the time I made the call. I do not know, to this day, whether a more patient version of that decision would have produced both the unit’s recovery and a better outcome for that person. I made the decision I made, on the timeline I had, with the information I had. It is one of the ones I cannot undo.
I am not telling this story to argue the decision was wrong. I am telling it because the honest accounting includes a real cost to a real person, and no amount of retrospective reasoning makes that cost disappear. That is what makes it structural rather than correctable. The unit’s recovery does not erase the individual cost. Both are simply true.
What changed operationally
The specific change in how I operate afterward was not “be more careful” — that is not a practice, it is a sentiment, and sentiments do not survive contact with the next deadline. The specific change was a question I now ask before any personnel decision made primarily on a timeline: what is the fastest path that does not require removing this person, and have I actually tested it, or have I just assumed it would take too long. In the decision I described, I do not know if I asked that question rigorously enough. I ask it rigorously now, every time, because I know exactly what it costs when I don’t.
Why this matters for enforcement
The reason this belongs in a conversation about standards and enforcement, rather than filed separately as a leadership-regret essay, is that decisions like this one are what enforcement actually costs when it is real. It is easy to talk about enforcing a daily standard in the abstract. It is a different thing to enforce it knowing that the specific decision in front of you might be one of the ones you cannot undo, and to make the enforcement decision anyway because the standard requires it.
If none of your enforcement decisions carry that weight, they were probably not enforcement decisions. They were easy calls dressed up as hard ones. What you tolerate, you teach. What you enforce, you build — and the decisions that build the most are usually the ones you cannot take back.
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.
