Are You Confusing Operational Excellence for Strategy?

A few years ago, a senior executive I worked with — a COO, sharp, respected, someone who had built his career on getting things done — looked at me across the table during a strategy session and said:

"Strategy is bullshit. I know what to do."

He wasn't being difficult, and he wasn't stupid — he was one of the most capable operators I'd worked with. But that sentence has stuck with me for years. It captures the single most common, and most dangerous, confusion in corporate life.

Keep him in mind. I'll come back to him.

It's Not a Strategy Problem. It's a Definition Problem.

After two decades in corporate strategy — across banking, private equity, and the Gulf region — I've sat in hundreds of rooms where "strategy" was on the agenda. Most of those organizations didn't actually have a strategy problem. They had a definition problem.

They were confusing two things that are fundamentally different: Operational Excellence and Strategy. Both matter enormously. Both are non-negotiable if you want to build something that lasts. But they answer completely different questions, they live in different parts of the organization, and when you mistake one for the other, you don't just slow down — you execute brilliantly in the wrong direction.

The clearest way I know to expose this confusion is a simple test: ask your executive team to produce a strategy.

What you'll most likely get back is an operational plan. More efficiency. Lower cost. Faster turnaround times. Maybe a headcount optimization or a process improvement roadmap. It's polished, it's quantified, and it feels strategic — because it's serious work that serious people produced in a serious room.

But it is not strategy.

Why does this keep happening? Because it is always easier to think of ways to improve what we're already doing. Operational improvements are visible, measurable, and familiar. Strategy — real strategy — requires something harder: imagining a different version of your organization than the one that exists today.

Strategy is the plan through which you'll accomplish your current mission by creating a unique and valuable market position. And accomplishing that mission will most probably entail big change — to whom you serve, what you sell, and why they'll choose you over every alternative. That's not an operational question. It's a strategic one. And it lives somewhere completely different in the organization.

The clearest way I know to illustrate where is a picture I've used with boards, executive committees, and founders for two decades: the steamship.

The Steamship

Picture an old steamship crossing an ocean. There are two worlds on that ship, and they rarely talk to each other.

The engine room is where Operational Excellence lives. It's loud, it's hot, and it's relentless. The questions down there are practical and immediate:

• When do we add more coal to the furnace?
• How do we make the coal burn more efficiently?
• What size shovels should the crew use?
• How do we optimize every process, every shift, every ounce of fuel?

The workers in the engine room are excellent at their jobs. The foreman — let's call him the COO — is proud of what his team has built. And he should be. The engine is running at peak performance. Fuel efficiency is up. Downtime is down. By every operational measure, this is a well-run machine.

But nobody in the engine room knows where the ship is going. That's not their job. It was never their job.

The captain's bridge is where Strategy lives. Up there, the questions are entirely different:

• Where are we going? That's the mission.
• Which route do we take? That's the strategy.
• How do we gear up for the journey? Those are the capabilities we need to build.
• What stops will we make along the way? Those are the milestones.
• What do we do when we hit a storm or an obstacle? Those are the OKRs — the tactics that keep us on course.

The Captain sees the full picture: the weather, the competition, the coastline, the destination. The Captain decides where the ship is headed. In a modern organization, that's the Chief Strategy Officer — or whoever is genuinely doing that job, regardless of title.

Here's the insight that changes how people see their own organizations once they really absorb it: a perfectly optimized ship sailing in the wrong direction is not a success. It is an efficient disaster.

You can burn the cleanest coal in the world, with the best shovel technique ever developed, and still arrive in entirely the wrong port — on time, on budget, and completely irrelevant.

Why This Confusion Actually Costs Companies

This isn't an academic distinction. I've watched it play out in real institutions with real consequences.

Companies that mistake Operational Excellence for strategy become world-class at doing the wrong things. They get faster, leaner, more efficient — and further from where they needed to be. I've seen banks perfect their loan processing times while the market they were built for quietly disappeared. I've seen private equity portfolio companies hit every operational KPI in the deck while the thesis behind the deal stopped being true. The dashboards were green. The direction was wrong.

The best operators in the world cannot save a business that has no destination. No amount of shovel technique fixes a ship headed for the wrong continent.

But the reverse is just as true, and strategists need to hear this as much as operators do. The most brilliant strategy dies the moment it meets an engine room that can't execute it. A strategy without operational excellence isn't a strategy — it's a slide.

You need both. That's not a compromise — it's the actual answer. But you must never confuse them, because they require different people, different skills, and different seats at the table.

Back to the COO

So — the COO. "Strategy is bullshit. I know what to do."

He wasn't wrong that he knew what to do. In the engine room, he was excellent — probably one of the best I've worked with. His instinct, his read on operational risk, his ability to squeeze performance out of a tired process were all real and valuable.

What he was wrong about was what "what to do" meant at his level. He was answering engine room questions with engine room confidence, and assuming that was the same as answering bridge questions. It isn't. Knowing exactly how to make the ship go faster tells you nothing about whether you're headed for the right port.

Both roles are essential. Neither is superior. But the two roles are not interchangeable, and organizations that let one mindset dominate both eventually pay for it.

One More Distinction Worth Making

Inside strategy itself, there's a further split worth understanding: corporate strategy is where you choose to play. Business strategy is how you plan to win.

The Captain decides which ocean to sail — which markets, which businesses, which bets are even worth making. The engine room then determines how fast and how efficiently you cross whichever ocean has been chosen. Confuse these two and you get companies that are excellent at winning in markets they should never have entered.

So What Do You Do About It?

If you suspect your organization is confusing Operational Excellence for Strategy — or running both on instinct — the fix isn't a framework or a consultant. It starts with two things that most leadership teams have never truly pinned down: mission and value.

Start with Mission

Before any strategy work begins, your current mission needs to be clearly articulated and genuinely agreed upon — not a sentence on a wall that no one believes, but a real declaration of what you exist to accomplish right now. Not your vision for ten years from now. Your mission: the purpose you serve today.

And here's what most organizations get wrong about mission: it should stretch you. A mission that fits comfortably within your current capabilities isn't a mission — it's a description of what you already do. A real mission pushes you into uncharted territory. It demands capabilities you don't yet have. It should make you slightly uncomfortable, because it means you're committing to a destination that requires genuine change to reach. That discomfort is the point.

Build Strategy Around Value

Once your mission is pinned down, strategy development should have one central preoccupation: value. Not efficiency. Not competitive benchmarking. Not best practices from your industry. Value — specifically, what your customers actually value, and how much more of it you could create for them if you thought differently about what you do.

This is the hardest part, because value-based thinking almost always leads to the same uncomfortable conclusion: the real opportunity is not in doing what you currently do a little better. It's in doing fundamentally different things, or doing familiar things in fundamentally different ways. Big leaps, not incremental improvements. The engine room is built for incremental improvements. The captain's bridge is where big leaps are decided.

If your strategy is essentially a plan to do more of the same, faster and cheaper, you are in the engine room. The bridge asks a different question: what would we have to believe about our customers, our market, and our own potential to justify a genuinely bold move?

That question — answered honestly, with rigor, and with the full leadership team in the room — is where strategy actually begins.

Why I Built TheStrategist.me — and How the OS Helps

Here's what I've concluded after 25 years of watching this play out: most organizations don't struggle because they lack smart people. They have plenty, in the engine room and on the bridge.

They struggle because they have no methodical path for the Captain's work. There are processes, KPIs, dashboards, and operational reviews for the engine room — entire disciplines built around Operational Excellence. But the bridge, more often than not, runs on instinct, politics, and PowerPoint.

That gap is exactly why I built TheStrategist.me — and why the TheStrategist.me OS is structured the way it is.

The OS is a sequenced method — 12 processes across 4 phases — that keeps you on the captain's bridge from the first step to the last. It opens with mission confirmation: locking down what you exist to accomplish today, in language that stretches you. It moves through value discovery — identifying your primary customer, understanding what they truly value, and building your strategy around delivering more of that value than anyone else can. Every step is a bridge decision, not an engine room one.

The reason this matters is structural: when you follow a sequenced method that starts with mission and builds through value, you cannot accidentally spend your strategy session optimizing processes. The method won't let you. You are on the bridge, doing bridge work, the entire time.

If you'd like to see how the method works — and try it on your own strategy — you can get the OS at thestrategist.me/pages/os.

In your organization, who is on the captain's bridge — and how do they actually make decisions?