At a smaller organization, I could still walk the floor. At a much larger one, I never could again. The standard had to survive a distance I could no longer close myself.
Early in my career, running a smaller operation, I could walk the floor myself. I could see what was actually happening, correct it in the moment, and let my presence do a meaningful share of the enforcement work. Later, running an organization more than twenty times that size, I never could again. There was no floor I could walk that covered a meaningful fraction of the operation. The standard had to survive at a distance my own presence could no longer close. That gap — between what a leader can enforce personally and what an organization actually needs enforced — is the real scaling problem, and it is narrower and harder than most scaling advice acknowledges.
The claim
Most advice about scaling an organization focuses on process, systems, or delegation in general terms. I want to name a more specific problem inside that broader one: how do you make a daily standard that started as something you personally enforced survive once you are structurally removed from the place where the standard actually gets tested. This is not a delegation question in the ordinary sense. It is a question about what enforcement even means once your physical presence has stopped being part of the mechanism.
Why personal enforcement doesn’t scale
At small scale, a leader’s presence is itself a meaningful part of the enforcement mechanism. People behave differently because the leader might walk in at any moment, and that possibility does real work — it is not nothing. At large scale, that mechanism mathematically cannot reach every unit. The leader’s physical presence becomes a rounding error against the size of the organization, and any enforcement model still relying on it is quietly failing in every place the leader is not currently standing.
The false comfort that catches leaders here is believing that because they set a standard once, clearly, and enforced it personally in the units they could reach, the standard has propagated to the rest of the organization on its own. It has not. A standard that lives in the leader’s presence rather than in the organization’s structure does not propagate. It just becomes true in the rooms the leader visits and unknown everywhere else.
What replaces presence
The standard has to become structural: embedded in what gets inspected, what gets reported upward, and what gets rewarded — not dependent on whether the leader happens to be in the room. In the jump from a smaller organization to a much larger one, the specific change was this: the informal habit of personally checking a handful of units became a formal inspection cadence applied uniformly, with findings that fed directly into what got reported to leadership and, separately, into what got rewarded at the unit level. Neither of those existed in the same explicit form at smaller scale, because they did not need to — my presence was doing enough of that work informally. At scale, informal does not reach far enough, and the same standard that used to live in my walking the floor had to get written into what the organization inspected, reported, and rewarded whether or not I was ever physically present.
The test for any leader scaling up
There is a simple test for whether a standard has actually become structural or is still borrowed from your presence: ask whether the standard would hold if you disappeared for six months. Not whether performance would dip slightly — organizations absorb the loss of any single leader to some degree. Ask specifically whether the standard itself, the daily practice of what gets tolerated and what gets enforced, would hold or would revert to whatever the organization’s default was before you arrived.
If the honest answer is that it would revert, the standard was never structural. It was borrowed presence, and it was always going to expire the moment your presence stopped being available — whether because you scaled past the point where your presence could reach, or because you left, or because you were never going to be in every room forever in the first place.
What gets built survives you
What gets built into the structure — the inspection, the report, the reward — is what gets enforced without you in the room. That is the only version of a standard that actually scales, because it is the only version that was never dependent on scaling your own presence in the first place. What you tolerate, you teach. What you enforce, you build. But past a certain size, you can only enforce what you have built into something other than yourself.
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.
