The Motte-and-Bailey Problem in Product: Why Your Real Defences Don’t Match Your Story
In last week’s post on Moats in AI, I argued that defensibility now comes from composite, compounding learning loops — not isolated assets. But there’s a related pattern I keep seeing across scaleups and incumbents that quietly undermines even the best strategies. It’s what, from this day forth, I hereby dub ye, the motte and bailey problem in product.
Welcome to the first article that uses this analogy, and is not to be confused with the Motte and bailey fallacy.
If you’ve not bumped into the medieval version recently, or experienced the thrill of learning the UK national curriculum as an 11-year old, you’ve likely only been exposed to the adjacent concept of ‘moats’ via the late-90s introduction by Warren Buffet. And most definitely not the concept of a “motte” or “bailey”. The setup and principle is simple:
-
The “motte” is the small, highly defensible stronghold.
-
The “bailey” is the larger, more valuable territory you want to hold.
-
When attacked > you retreat to the motte.
-
When conditions are favourable > you claim the bailey.
In product, this maps almost too neatly onto a pattern every experienced product leader will recognise: the widening gap between the story organisations tell and the reality they operate from.
Here’s how it shows up:
1. The Bailey — the expansive strategic story (your positioning)
This is the version of the company that appears in pitch decks, investor narratives, category design exercises and all-hands meetings. It’s the story you want the market to believe — and often need the market to believe in order to justify valuation, win deals or hire talent. It’s what world-class product leaders excel at, being the evangalist and getting people excited and drawn into their vision.
The Bailey is where positioning lives.
Typical Bailey claims look like:
“We’re an AI-native platform built around intelligent automation.” Reality: Your “AI” is three prompt templates and a Zapier flow nobody monitors.
“We’re category-defining — not another point solution.” Reality: 80% of your revenue still comes from a single legacy module.
“We’re moving upmarket with enterprise-grade workflows.” Reality: The permission model breaks whenever a customer has more than two roles.
“We’re the system of record for X.” Reality: Customers still export data to Excel because they don’t trust your reporting.
“We’re a unified platform post-acquisition.” Reality: You have three authentication flows, two data models and a migration backlog no one owns, nor wants to own.
These statements are rarely lies. They’re directionally true aspirations.
But aspirations are not defences.
The Bailey is what you want to stand for. It’s what the deck says you are. And it’s where most teams, and executives, prefer to spend their time.
The challenge (and occasionally the upside) is that positioning creates gravity. Once you commit to a narrative, the whole organisation starts optimising for that story… even if the product isn’t ready to support it.
That’s where the gap begins.
2. The Motte — the entrenched operating truth (your defensibility)
The Motte is the part of your product and organisation that actually holds when pushed — by customers, revenue pressure, competitors or internal politics.
This is the reality you fall back on when the Bailey can’t carry the weight.
This is your true defence, whether you like it or not.
Examples of Motte truths:
-
The one or two features that drive 75% of usage — even though it’s never mentioned in your “platform” positioning.
-
The workflow everyone is scared to touch because it’s brittle — but losing it would wipe out half your renewals.
-
The manual backend process everyone pretends is automated — but remains your hidden moat because no competitor wants to replicate it.
-
The revenue dependency you can’t admit out loud — like an out-of-date module that no longer fits your narrative but pays the bills.
-
The architectural debt that makes the AI strategy in the deck virtually impossible for at least 18 months.
This isn’t the product you talk about. It’s the product you depend on.
And when deals get tough, when users churn, when competitors move, when investors press you — you’re really defending from the Motte and rarely setup to be successful in the Bailey.
The market positioning says one thing. The operating reality defends another.
That’s the whole problem.
Most companies are fluent in the Bailey story… …but are defended almost entirely by the Motte reality.
And that mismatch is one of the biggest risks in any product company or product leadership role. It’s our job to make sure that gap reduces over time, in pace with internal and expectations.
Why the gap exists
1. Vision is cheap; operating alignment is not.
Anyone can publish a strategy deck. Very few can align incentives, architecture, team structure, and workflow to actually deliver it. The gap between “what we say” and “what we do” appears immediately in how work gets funded, shipped, measured and killed.
2. Legacy features carry political and commercial weight.
Some of your oldest, least-loved features are also the ones tied to targets, renewals or internal status. No one wants to say it aloud, but these are the gravity wells that pull you back to the Motte and keep you there.
3. AI has widened the narrative gap.
Companies announce AI faster than they can adapt their data structures, workflows, governance or architecture. The positioning leaps ahead; the operating model stays exactly where it was.
4. Inertia is invisible until you look closely.
From a distance, everything looks aligned. Spend five minutes tracing a customer journey, a permissions flow, or an approval chain — and the cracks appear instantly. Most teams don’t see the misalignment because they work inside it.
Examples you’ll recognise
Here’s a brief reminder of the lived reality — and why it matters:
A company says it’s a platform… but 70% of revenue comes from one module built in 2018. Why it matters: your positioning says breadth, your metrics say dependency. When sales leans on the story and delivery can’t support it, trust frays and Product becomes the “blocker.”
A deck says AI-first… but the data model hasn’t been touched since 2017. Why it matters: customers expect something you physically can’t ship that the story promises. Product carries the blame, engineering takes the strain, and the narrative erodes the moment a customer says, “Show me.”
A team says customer-led… but hasn’t run a real discovery session in two months. Why it matters: decisions get made on assumption, not insight. Vocal leadership say ‘we know what the customer wants, just build it’. Roadmap confidence drops, debates get louder, and Product ends up defending other people’s choices built on thin ice. The “learning loop” dies.
Leadership says pace matters… but every change still passes through a steering or oversight group. Why it matters: the operating model contradicts the message. Teams optimise for survival, not velocity, and Product gets squeezed between “go faster” rhetoric and slow, political reality.
The website shows a unified platform… but customers still log in through three separate URLs. Why it matters: trust breaks instantly when the product experience contradicts the pitch.
In every case, the Bailey (the story) and the Motte (the truth) aren’t just out of sync; they create friction, erode trust, and place Product in the crossfire between aspiration and reality.
These gaps don’t stay abstract. They show up as tension in meetings, misalignment between teams, roadmap derailments, constant requests for more detail and the quiet organisational cynicism that forms when the story outpaces the substance.
But let’s not be too concerned with just the internal problems. Worse still, Customers will always feel the gap.
Why this matters more in 2025
In the past, story and substance could maintain divergence for quite a period, some even for years. You could sell the Bailey and gradually drag the Motte along behind you. Not anymore.
AI has compressed timelines, raised expectations and made execution brutally comparable. Customers can now test claims in seconds. Investors can spot architectural debt in one roadmap review. Competitors can close narrative gaps faster than incumbents can articulate them.
When your positioning outpaces your product, three things happen — fast:
1. Credibility erodes. The gap shows up in demos, onboarding, support tickets and renewal conversations long before it shows up in the numbers.
2. Trust fractures internally. Sales, Product and Engineering stop believing the same story. Alignment collapses quietly at first, then all at once.
3. Your defensibility shrinks. Your moat isn’t the story you tell; it’s the reality you can sustain under pressure.
And in 2025, your moat is only as strong as the thing you actually defend — not the thing you present in the deck.
And customers can feel the difference instantly.
So what can real product leaders do? (Practical steps)
Simple, maybe uncomfortable, but effective:
1. Map your Motte and Bailey explicitly
Get a brutally honest list of:
-
What you say you are
-
What actually drives the metrics that matter (e.g. revenue, adoption, retention)
-
What customers reliably trust you for
-
What your org is structurally capable of delivering today
If you can’t draw the gap, you can’t close it.
Action:
-
Run a “Narrative vs Reality” workshop with Product, Engineering, Sales and Support.
-
60 minutes. Whiteboard only.
-
End with two columns: What we claim vs What we defend.
-
If the lists don’t match, that’s your agenda to resolve and get alignment around asap.
2. Identify your “Motte dependencies”
These are the features, behaviours or processes you rely on for survival — even though they contradict the story you want to tell.
Examples:
-
The onboarding wizard everyone hates but customers refuse to migrate off
-
A single workflow that props up 30% of revenue
-
A brittle back-end service blocking every other roadmap innovation or strategic bet
-
The manual ops process everyone pretends is automated
These normally surface as annoyances, but they are structural risk hotspots.
Action:
-
Name them.
-
Rank them.
-
For each, decide: protect, modernise or retire.
-
If everything ends up in “modernise”, you don’t have a strategy, you have a wish list.
3. Shrink the Bailey into something actually defensible
Most product strategies fail because they try to change everything at once.
If you want credibility, shrink the vision until it fits your operating model. Then grow from there.
Most product strategies fail because they’re too big, too vague, or too divorced from the operating model. They aspire to do everything at once for everyone.
Your Bailey should be the smallest strategic territory you can actually deliver with conviction — not the largest narrative you can present to the board or put in a deck.
If you want credibility, shrink the strategy until it fits your architecture, team shape and delivery muscle. It’s ok to have an aspirational vision and I’m personally a fan of them. But you need to have a strategy behind it that grows deliberately, not rhetorically.
Action:
-
Rewrite your strategy statement in one sentence: “Over the next 30-60 days, we will be defensibly excellent at X and intentionally ignore Y.”
-
If you feel you can’t complete that sentence, the Bailey is still too big.
-
Do this for 30-60 days, 3 months, 6 months and 12 months being intentional above impact expected
-
This creates a basic product strategy template that can evolve dynamically as you learn within each time period.
4. Build a learning loop around the gap
This connects directly to last week’s piece on compounding learning loops.
Real defensibility will come from: Work (transparently + small + meaningfully + swiftly) + Inspect/Adapt = high-cadence learning, compounding value, real accountability.
Apply that loop to the Motte/Bailey gap. Don’t just ship features — ship alignment.
Action: Every iteration should reduce the distance between what you say you are and what the product proves you are.
Action:
- Add a standing agenda item to your product review: “Where did our last cycle narrow the Motte/Bailey gap? e.g. are we closer or our vision than we were before” If the answer is “no or nowhere”, you’re not building defensibility — you’re accumulating narrative debt which will lead to all the problems called out above
5. Align incentives to reality, not narrative
This is where most organisations quietly and invisibly can break.
People don’t really follow the strategy; they follow the incentives baked into process and culture.
If your teams are incentivised on the Bailey vision but rewarded (explicitly or implicitly) for protecting the Motte revenue, they will always default to survival. Not because they’re wrong, but because the system teaches them to.
Here’s what those misaligned incentives look like in real life:
-
Sales quotas tied to legacy features → sales keeps selling the old thing, product becomes the villain for “slowing deals down.”
-
Engineering measured by output, not outcomes → teams optimise for volume, not impact, and innovation consistently loses to maintenance or polish.
-
Roadmap “commitments” made in QBRs → PMs ship what was promised, not what was learned, killing adaptability and real innovation
-
Design rewarded for speed over quality → UX debt piles up and “platform” claims fall apart under scrutiny as small disconnected slices of UI are delivered only.
-
Leadership praising “big bets” publicly but penalising small experiments privately → teams stick to safe work and strategy stagnates.
-
Performance reviews focused on stakeholder satisfaction → PMs avoid hard truths and keep the Bailey shiny while the Motte rusts.
The majority of investives don’t involve involve money. All of them shape behaviour.
Misaligned incentives will trap you in the Motte forever. As a product leader it is your job to identify what is really going on and surface these more difficult and sometimes more intangible aspects.
Action:
-
Run a simple audit with your leadership team: “What behaviour does this process, KPI or ritual actually reward?”
-
If it pulls people back to the Motte, acknowledge it and change the mechanism — not the messaging.
-
Repeat for what you are noticing and feeling.
Strategic alignment doesn’t happen because you tell a better story or just have the strategy written down in a way people can consume it. It happens because people are rewarded (socially, politically and operationally) for doing the work that makes the story true.
Closing thought
In an AI-first world, anyone can paint a bold story. The real advantage belongs to the product leaders who can close the space between story and substance. That’s why this matters. The Motte/Bailey gap isn’t a philosophical idea — it’s the root cause of slow delivery, eroded trust, confused teams and strategy that never lands. If you can name the gap and reduce it cycle by cycle, you build something far more durable than a moat. You build an organisation that learns, adapts and delivers in reality, not just in narrative. That’s the only defensibility that lasts.
The companies that thrive in this next era won’t be the ones with the flashiest narrative. They’ll be the ones whose narrative matches their operating truth.
Originally published on the Product Leaders Substack .