Be Prepared; You Can’t Bleed Your Way to Victory
In school, it might be the “3-R’s” of Readin’, Ritin’, and ‘Rithmatic that get you through, but in business its Robustness, Readiness, and Resiliency. And the order matters more than you might realize.
I was standing at the back of the room at a conference a few years ago — one of those events where you hear the same five presentations reshuffled into slightly different slide decks — and a speaker said something that made me put down my coffee.
“We need to build more resilient organizations,” he said.
The room nodded. Vigorous, knowing nods. The kind you give when you agree with something that sounds right but costs you nothing to believe.
I didn’t nod.
I’ve spent more than 30 years inside manufacturing plants, supply chains, and boardrooms on six continents. I’ve watched companies pour millions into “resilience programs” that amounted to little more than expensive security blankets; and then collapse at the first serious disruption anyway. Not because they weren’t resilient enough. Because they’d skipped the two things that actually had to come first.
Resilience without robustness and readiness isn’t a strategy. It’s just a slower way to fail.
Robustness: You Have to Be Good Before You Can Be Ready
Let me tell you about a plant I visited (I’ll leave the name out, but you’d recognize the company) where management had invested heavily in contingency planning. They had documented backup suppliers. They had a crisis response team. They had a binder. A literal three-ring binder, on a shelf, labeled Emergency Response Protocol, gathering dust next to a fire extinguisher that was two years past its last inspection.
Their processes, the day-to-day operations, were broken. Not catastrophically, but chronically. Yield was sitting at 71% when industry standard was 88%. Their changeover times were twice what they should have been. Their first-pass quality rate was embarrassing. But they had the binder.
When their primary supplier went under (and it did go under, abruptly, during a raw materials shortage) the backup suppliers couldn’t absorb the volume because this company had never qualified them properly. The crisis response team convened and promptly discovered they had no idea what their actual production capacity was on a good day, which made calculating alternative scenarios on a bad day something between a guess and a prayer.
They bled for eight months. I know because I was brought in four months into the bleeding.
Robustness is your baseline. It’s how well your processes and protocols actually work when everything is running as planned. It’s your operating efficiency and effectiveness on a normal Tuesday; not a crisis Tuesday, just a regular Tuesday when nothing is on fire and the machinery is cooperating.
Can you deliver what you promised? On time? At the quality you specified? Can your teams execute without heroics? Do your systems work the way they’re designed to work, or do they work because three specific people know all the workarounds?
This is where the work starts. Not with resilience. Not even with readiness. Here. With the unsexy, painstaking, relentless effort to make your baseline operations genuinely good.
I’ve seen organizations chase “resilience” because building robustness felt too slow, too granular, too much like admitting the house was built on sand. It’s easier to talk about weathering storms than to fix your foundation before the storm comes.
Here’s the brutal truth: you cannot be ready for disruption if you can’t reliably execute when there isn’t any. You cannot bounce back from a crisis if your normal state is already a slow-motion crisis. Robustness isn’t a nice-to-have. It’s the ground floor. Everything else is built on top of it.
Readiness: Because ‘If’ Left the Building a Long Time Ago
The CEO I mentioned in my Chairman’s Note (the one who asked me how much data he needed before he could make a decision with certainty) was running a Fortune 500 company. Smart guy. Serious pedigree. Built his career on analysis.
When I told him the only honest answer was “an infinite amount of data and an infinite amount of time to analyze it,” he wasn’t amused. But I wasn’t trying to amuse him. I was trying to wake him up.
We’ve been seduced by data. Not data itself; data is valuable. But the idea that enough data eventually yields certainty. It doesn’t. The world is not a closed system. The variables keep multiplying. And the world will absolutely not wait while you’re building your spreadsheet.
So we have a choice. We can wait for certainty that will never arrive. Or we can build the capacity to move with confidence even in the absence of certainty.
That capacity is readiness.
Readiness is your ability to respond when something throws you off course. Not if something happens. When. There is no ‘if.’ There hasn’t been an ‘if’ for years. If you’re still planning for ‘if,’ I don’t know how to help you.
I wrote about this at length in State of Readiness. The distinction I keep coming back to is this: readiness is not a reactive posture. It’s not about having a plan you pull out when things go wrong. It’s about having the systems, the skills, the organizational agility already embedded in your operations; so that when your primary supplier goes bankrupt, when the regulation changes overnight, when a competitor launches something you didn’t see coming, you don’t have to invent your response from scratch.
You already know how to pivot. You’ve practiced it. The muscle memory is there.
I think about it like a hospital trauma team. They don’t wait for the trauma to figure out their roles. They’ve drilled. They’ve simulated. When the ambulance pulls up, there’s no committee meeting about who’s going to do what. They move. Every person knows their assignment. The equipment is ready. The protocols are practiced until they’re automatic.
Now imagine that same trauma team running a hospital where the operating rooms are understaffed, the equipment is outdated, and the basic procedures are inconsistently followed. All the drilling in the world won’t save you if the foundation is broken. That’s why robustness has to come first.
But readiness – genuine readiness – is what separates organizations that adapt from organizations that freeze. And in a VUCA world, freezing isn’t a neutral option. Freezing is a decision with consequences.
I’ve proposed that we make decisions “when our level of confidence exceeds our level of fear.” Readiness is what builds that confidence. Knowing your team. Knowing your capacities. Knowing your capabilities; not in theory, but from having tested them. Having the organizational agility to say, “Go.”
That’s readiness. And you can only build it on top of robustness. Skip robustness, and your readiness is a house of cards. It looks like preparation. It isn’t.
Resiliency: The Last Line, Not the First
Now we get to the word everyone loves. The one that gets standing ovations at conferences. The one on the cover of four Harvard Business Review issues in the last three years.
Resilience.
I want to be careful here, because I’m not dismissing it. Resiliency is real and it matters. But the way we talk about it — as if it were the primary goal, the North Star, the thing you build toward — is, I think, getting us into serious trouble.
Resiliency is your reserve capacity. It’s your financial buffers. Your redundant capabilities. Your alternative supply chains. Your ability to absorb a genuine hit – not a disruption, an actual hit – and keep operating.
It is, almost by definition, a fallback position.
Think about what resiliency actually means in practice. It means that when robustness fails and readiness isn’t sufficient, you have something in reserve. You can take the hit. You can absorb the loss. You can keep going.
That’s critically important. And here’s why it scares me that we’ve elevated it to the top of the hierarchy:
Because if your primary operational strategy is absorbing hits, you are going to get hit a lot.
A resilient organization that isn’t robust is efficient at bleeding. It has well-managed hemorrhaging protocols. The financial buffers give it more runway to hemorrhage. The redundant capabilities mean it can bleed from multiple wounds simultaneously and still function. This is not a compliment.
A resilient organization that isn’t ready can take a punch, but it can’t duck. It can recover, but it cannot adapt. It survives disruptions by brute financial force, not by agility. And brute financial force is expensive. You can only take so many hits before even the deepest reserves are gone.
You cannot bleed your way to victory.
I’ve watched companies burn through their reserves during disruptions that a genuinely robust and ready organization would have navigated without drawing on reserves at all. I’ve watched them call it resilience. I’ve watched them rebuild the reserves slowly, then watch the next disruption arrive before the rebuilding was done.
The cycle doesn’t end well.
Resiliency is essential. Do not misread what I’m saying. In a VUCA world, you need reserves. You need redundancy. You need the capacity to survive when everything else fails. But it should be your last line – your insurance policy – not your operating model.
The organizations that win (and I mean genuinely win, not just survive) are the ones that have built all three. Robustness as the foundation. Readiness as the operating capability. Resiliency as the reserve.
Why the Order Matters as Much as the Elements
There’s a reason I named them in this sequence. Robustness, Readiness, Resiliency. It’s not alphabetical. It’s not arbitrary. It’s causal.
Each one depends on the success of the one before it.
Robustness alone makes you efficient in stable conditions. And stable conditions are nice when you can get them. But stable conditions in 2026 are approximately as reliable as a weather forecast for next month. You need more than robustness. But you start with robustness, because nothing else works without it.
Readiness without robustness means you can pivot quickly; to nowhere useful. I’ve seen this. A company with impressive organizational agility and genuinely broken core operations. They could change direction on a dime. Unfortunately, every direction they pivoted to was built on a foundation that couldn’t support the weight. The agility just meant they failed faster in more creative ways.
Resiliency without the other two just means you can bleed longer. I’ve said it and I’ll say it again, because it bears repeating: absorbing hits is not a strategy. It’s a symptom of not having a better strategy.
But all three, in sequence, built intentionally on top of each other? That’s a high-performance organization.
That’s an organization that performs well in stable conditions because the foundation is solid. That adapts when conditions shift because the readiness is already built in. That survives when conditions genuinely collapse because there are reserves to draw on; and because the robustness and readiness mean those reserves aren’t being drawn on constantly.
Operational Excellence is often described as process improvement. I have a different view. I think Operational Excellence is the discipline of building all three of these capacities, in the right order, until they’re embedded in the DNA of the organization. Until the organization doesn’t just do these things; it is these things.
The difference between an organization that freezes when the unexpected happens and an organization that moves – confidently, deliberately, effectively – is almost always traceable to whether they built robustness before they tried to build readiness. And whether they built readiness before they leaned on resiliency.
What I Know for Certain
I told that CEO something he didn’t want to hear: certainty isn’t coming. You make your decisions when your confidence exceeds your fear. And you build that confidence; not through more data, but through knowing your organization. Deeply. Honestly. Without the comfortable fictions we tell ourselves in annual strategic plans.
Robustness tells you: Here’s what we can actually do. Not what the slide deck says. What we can actually do.
Readiness tells you: Here’s how fast we can adapt. Here’s what our teams can handle. Here’s where our agility actually lives.
Resiliency tells you: Here’s how long we can survive if we have to.
Together, those three things are what confidence is made of. They are what “Go” is made of.
The world is not going to become less volatile. It is not going to become less uncertain, less complex, less ambiguous. The organizations that figure out how to build Robustness, then Readiness, then Resiliency – in that order, for the right reasons – are the organizations that are going to be standing when others aren’t.
I know which organizations I want to be part of. I know which ones I want to help build.
The question is whether you’re willing to start at the foundation; even when it’s slower, even when it’s less glamorous, even when “resilience” is what’s trending on LinkedIn this week.
Start with robustness. Build to readiness. Hold resiliency in reserve. In that order. For those reasons.
Everything else is just the binder on the shelf.
“Accept the challenges so that you can feel the exhilaration of victory.”
— General George S. Patton
About the Author
Paris is an international expert in the field of Operational Excellence, organizational design, strategy design and deployment, and helping companies become high-performance organizations. His vehicles for change include being the Founder of; the XONITEK Group of Companies; the Operational Excellence Society; and the Readiness Institute.
He is a sought-after speaker and lecturer and his book, “State of Readiness” has been endorsed by senior leaders at some of the most respected companies in the world.
Click here to learn more about Joseph Paris or connect with him on Linkedin.
