During the holidays, I built a simple app to test one of the most discussed — and least landed — concepts in the enterprise: portfolio discipline, enabled by segmentation.
Boards are increasingly spending more and more time debating capital allocation, resilience, and focus — yet most enterprises still lack a practical way to test whether their strategic preferences actually survive contact with operations.
This is where portfolio discipline quietly fails.
Not because organisations lack insight, but because segmentation has never been treated as what it really is: a mechanism for declaring where the enterprise will deliberately invest, constrain, and differentiate under real operating limits.
But now, in the context of our recent Continuous Planning report and working with our members to bring it to life, segmentation is top of mind. Not only is it emerging as a clear and critical enabler of this new era of planning, it sits at the fault line between strategic intent and operational execution.
For the first time, new tools now exist to make it possible to test decision logic. And that's a game-changer for ops leaders.
Why Segmentation Always Breaks
In every organization I've worked with, segmentation follows the same pattern: Marketing builds sophisticated customer segments. Product designs portfolio logic. Finance allocates capital. Operations inherits the complexity and is asked to make it work.
The problem is that these decisions never meet each other until it's too late. Insight never becomes executable because, by the time segmentation hits the supply chain, the tradeoffs are already locked in. The richness of segmentation lives in documents and decks; portfolio logic is applied globally, bluntly, or quietly negotiated through politics; and planning inherits complexity it did not create and is asked to absorb it. Customer differences pull toward variety. Brand expression pulls toward breadth. Supply constraints pull toward simplicity.
What’s missing isn’t collaboration — it’s a shared portfolio logic that reconciles these forces before they hit the operating system.
When they aren’t reconciled upstream, they collide downstream, where the cost of ambiguity is highest. The result is familiar: SKU sprawl, fragile plans, and planning teams burdened with complexity they never chose.
The Tech Shift
For most of my career, there's been no practical way to test whether segmentation logic actually contact with operational reality. Pressure-testing meant workshops, debate, and eventual compromise. Breakage was discovered only after decisions were made. But now? I used Claude, Replit, and a few hours of stubborn curiosity.
Lightweight product-building makes it possible to externalise assumptions, apply real operating constraints, and observe how strategic choices behave when forced to interact with reality. What used to be debated in slides can now be interrogated.
The lightweight simulator I built (low code/no code, rather than vibecoding) wasn't the complexity of the problem. It was how quickly weak logic surfaced once it had to make actual decisions. Marketing's customer segments collapsed into the same SKU mix. Product's portfolio logic couldn't survive regional constraints. What looked like strategic differentiation in slides turned into operational chaos when tested.
For ops leaders, this enables:
- turning assumptions into inspectable logic
- surfacing tradeoffs early
- arriving at vendor and RFP conversations with clarity instead of aspiration
Segmentation Is a Strategic Discipline — Not an Analytical One
This shift isn’t really about tools. Low-code and no-code platforms have simply removed the excuse. What once required a dev team and six months can now be prototyped in hours. The deeper change is strategic. Leaders can no longer rely on belief when the means exist to test whether decision logic actually works.
Segmentation sits at the intersection of consumer understanding and operating model design. It translates variation in demand into deliberate differences in how the enterprise allocates capital, capacity, and attention.
In that sense, segmentation is the mechanism through which portfolio discipline becomes executable.
At its best, it doesn’t attempt to capture every nuance of demand. It defines how much variation the operating model is designed to absorb — and where discipline must be imposed through decision rules the organisation can run.
When done well, segmentation provides the connective tissue between long-term intent and day-to-day planning — ensuring that what leaders say they want is reflected in how the business actually operates.
In practice, effective segmentation does three things:
- acts as an end-to-end connector
- clarifies sensing versus shaping decisions
- focuses organisational effort where it truly matters

The Coca-Cola Company offers a useful illustration. Its revenue growth management discipline makes segmentation executable — not through perfect consumer insight, but through enforceable decision rules across products, channels, and bottlers. Those rules determine where variation is allowed and where it isn’t.
That’s what enables planning to move from alignment theatre to real tradeoffs at scale.
That’s portfolio discipline in action.
So what?
Here's what changes when you can test segmentation logic before it breaks:
Politics get replaced by evidence. When marketing, product, and operations can see how their decisions interact in a simulator, the conversation shifts from "who owns segmentation" to "does this logic actually work?" That removes the negotiation tax that's plagued planning for decades.
RFP clarity increases. Artefacts like this should exist before an RFP is written, not after a solution is selected. When you arrive at vendor conversations with tested logic instead of aspirational slides, you're buying a solution to a defined problem, not hoping software will figure it out for you.
Costs come down. When you know where your segmentation logic actually drives differentiation—and where it collapses into the same behavior—you stop funding complexity you don't need. Capital allocation becomes intentional, not accidental.
Evidence>Belief
The question is no longer “What is our segmentation?” It’s “What decisions are we making on the back of it, and have we tested whether that logic holds?”
In 18 months, operations leaders who can’t answer that question will be at a serious disadvantage. Not because they lack insight, but because they’ll still be operating on belief while competitors operate on tested logic.
This shift isn’t just technical. It’s a leadership shift — because it forces clarity, ownership, and tradeoffs where ambiguity has long reigned.