Ask most executives what their culture produces and you get a value. Ask what it manufactures and most can’t answer. I always answered the second question first.
Ask most executives what their organization’s culture produces, and you will get a value in response: integrity, excellence, accountability, respect. Ask what it manufactures — what specific, inspectable thing comes off the line every day — and most cannot answer at all. I have always answered the second question first. Our product was readiness. Not a value we aspired to. A product we built, with a defect rate, an inspection point, and an owner accountable for supply.
The claim
Values are aspirational and, in practice, unfalsifiable. Nobody can prove an organization does not have integrity — the claim is too diffuse to test. Products are different. Products have specifications. They have defect rates. They have inspection points where you check whether the spec was met. Treating readiness as a product rather than a value changes what you can measure, what you can audit, and who you can actually hold accountable when the product fails to ship.
What changes when readiness is a product
Three specific shifts follow from this reframe, and they are genuinely distinct from one another.
First, a product has a defect rate, not a sentiment score. An annual engagement survey asking people whether they feel the organization is “ready” measures sentiment. An inspection that tests whether a specific unit can perform a specific function under specific conditions measures a defect rate. The two numbers can move in opposite directions, and when they do, the defect rate is the one that is real.
Second, a product has an inspection point, not an annual event. You do not inspect a manufacturing line once a year and call the output validated for the next twelve months. You inspect it on a cadence tied to the actual rate at which defects can enter the process. Readiness, treated as a product, gets inspected on a similar cadence — frequently enough that a defect entering the process gets caught before it compounds.
Third, a product has an owner accountable for supply, not a committee accountable for culture. Culture initiatives are frequently owned by committees, because culture is diffuse enough that no single person can reasonably be asked to own it alone. A product cannot be owned that way. Somebody has to be accountable for the fact that the readiness the organization needs on a given day is actually available on that day, the same way somebody is accountable for a factory’s output meeting the day’s order.
The operating-partner application
This distinction matters most directly to anyone evaluating a portfolio company or acquisition target from an operating-partner seat. Most diligence processes evaluate a target’s culture through interviews, surveys, and reference checks — essentially treating readiness as a value to be assessed qualitatively. I would evaluate it the way you would evaluate a manufacturing line’s defect rate.
Ask for the specific inspection points the organization runs against its own readiness — not the annual survey, the actual operational tests. Ask how long it has been since one of those inspections surfaced a real finding, and treat an answer of “a long time” as a flag rather than a comfort, per the same logic that applies to any self-assessment discipline that has gone quiet. Ask who, specifically, is accountable for the organization’s readiness on a given day — not who owns the culture initiative, who owns the supply. If the honest answer is a committee, you have found your diligence finding before you have even opened the data room.
The trap of value language
Naming readiness as a value invites the organization to feel good about believing in it, which is a much easier achievement than actually building it. Values get affirmed in town halls and printed on posters. Nobody has ever been held accountable for a value’s defect rate, because values do not have one. The moment you name readiness as a product, you have created the possibility of a defect — and the obligation to find out whose job it was to prevent it.
That obligation is uncomfortable, and it is exactly why most organizations prefer the value framing. It is also why the organizations that treat readiness as a manufactured product, inspected and owned like any other output, are the ones actually ready when the pressure event arrives. What you tolerate, you teach. What you enforce, you build — and you cannot enforce a spec you have never written down.
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.
