Buzzword bingo: MOAT

Every strategy deck has one. Almost no one is building it where it actually lives.

Let's play a game. Take any pitch deck from a Series B company. Flip to the slide that says "competitive advantage." I'll bet you a very expensive off-site that somewhere on that slide — tucked between a market map and a hockey stick image — you'll find the word moat.

It will be presented as a strategic assertion. Something about proprietary data, or network effects or brand. It will sound confident. It will have been debated in a board meeting. And in most cases, it will have almost nothing to do with how the company actually operates on a Tuesday morning.

That's the problem with moat as a concept. It has been colonised by strategy. And in being claimed by strategy, it has been quietly abandoned by the people who actually build it.

Here's the provocation: your moat is not a strategic position. It is an operational reality. And most companies don't realise it until someone else has already crossed it.

Where the word came from, and what got lost

Warren Buffett popularised the term. His definition was elegant: a moat is a durable competitive advantage that protects a business from its competitors, the way a water-filled trench protects a castle. Width matters. Depth matters. And crucially: maintenance matters. A moat that isn't actively tended, silts up.

What Buffett understood, and what most strategy conversations forget, is that moats are not declared. They are accumulated. They are the sediment of thousands of operational decisions made over years; decisions about how you hire, how you build processes, how you serve customers, how you retain knowledge, how you scale without breaking.

The moat is not the castle. It is the ground beneath it.

The four moats that operations actually builds

When I work with COOs and operations leaders, I see four types of durable advantages that are genuinely difficult for competitors to replicate. None of them appear on a strategy slide. All of them are built — or destroyed — through operational decisions.

Execution velocity / time to market / operational speed ... or whatever other name you want to give it. The ability to move faster than your competitors at equivalent quality. This is not a technology advantage. It is a process, structure and decision-making advantage. Companies that have stripped unnecessary approval layers, clarified decision rights and built feedback loops into their operations can outpace larger rivals not because they are smarter, but because they are faster to learn and act. Velocity compounds. A company that iterates 30% faster than its competitor doesn't just win this quarter, it wins every quarter, forever, by an ever-widening margin.

Institutional information and knowledge architecture. How a company captures, organises and transfers what it knows. Most organisations "bleed" knowledge constantly; it walks out the door with every departure, sits locked in one person's head, or drowns in a Confluence or Notion graveyard, nobody reads. The companies that build genuine knowledge moats are the ones whose operations leaders have treated data, information and knowledge as infrastructure. They've designed onboarding that actually transfers capability. They've built documentation cultures where the process lives in the system, not the person. When a key person leaves, the work continues at 90% quality, not 40%.

Operational consistency at scale. The ability to deliver the same experience to customers, to employees, to partners ... as the organisation grows. This sounds so obvious. It is unfortunately extraordinarily rare. Most companies that scale quickly do so by adding people and hoping, wishing, praying ... the culture holds. The ones that build a moat do so by designing operating models that encode their standards into structure rather than relying on individual heroics. Consistency at scale is the thing customers eventually pay a premium for, because it is the thing they can actually rely on.

The compounding cost of imitation. This is the moat most people miss entirely. When your operations are genuinely excellent; when your processes are tight, your data is clean, your people are well-structured, your decision-making is fast and clear ... the cost for a competitor to replicate you is not just high. It is rising.

Every month you operate well, you pull further ahead. Every month they operate poorly, they fall further behind. The gap is not static. It is a flywheel. And it is built one operational decision at a time.

The misunderstanding that costs companies the most

Here is where the buzzword does its real damage.

When leadership teams treat moat as a strategic concept, something to be declared rather than built, they systematically underinvest in the operational infrastructure that would actually create one. They spend on brand and reputation. They hire for strategy. They debate positioning. And they chronically underfund the work of building the processes, the systems, the organisational design and the operational discipline that would make the moat real.

The COO sits in that gap. And the COO's job, often the hardest version of it, is to make the argument that operational excellence is not execution support for the strategy. It is the strategy.

The moat doesn't live in the pitch deck. It lives in the org chart, the process map, the knowledge base and the decision-making culture that the operations function builds and protects every single day.

What this means for you

If you are an operations leader, I want to offer you a reframe that I think changes how you walk into rooms.

You are not implementing someone else's moat. You are building it. Every time you design a process that scales without breaking, you're adding water to the trench. Every time you build a structure that retains knowledge when people leave, you're deepening it. Every time you create decision-making clarity that lets your organisation move faster, you're widening it.

The strategy team will name the moat. The finance team will model it. The board will celebrate it.

But you are the one building it. (Stop letting that be invisible!) ;-)