Zone to Win: Geoffrey Moore's Portfolio Framework for Balancing Your Product Investment

This is one of RoadmapOne ’s articles on Objective Tagging methodologies .

I’ve never sat in a board meeting where the phrase “we need a balanced product portfolio” wasn’t met with quiet agreement. I’ve sat in plenty where nobody in the room could actually tell me what the current mix was.

Zone to Win is Geoffrey Moore’s 2015 portfolio-management framework for allocating product and engineering spend across four zones: Performance (today’s revenue), Productivity (enablement and operational efficiency), Incubation (tomorrow’s bets), and Transformation (a bet being scaled into a material new line of business). Every pound of spend sits in exactly one zone, each zone runs under a different operating model, and the portfolio’s overall mix becomes visible at board level.

Moore’s 2015 book is the follow-up to Crossing the Chasm , and the four zones give you a vocabulary to have the “where is the money going?” conversation honestly. Once every pound you spend is tagged to one of the four, you can see your mix — and the board can tell whether it’s deliberate, or whether it’s whatever fell out of last year’s decisions plus inertia.

Tag your roadmap by zone — free sign-up

1. The Four Zones in Plain Language

Moore’s four zones describe what a pound of spend is actually doing. They are mutually exclusive: the same work cannot belong to two zones simultaneously, because each zone demands a different operating model, different metrics, and a different level of CEO attention.

Performance Zone

The Performance Zone is where today’s revenue comes from. It’s populated by the people whose work directly earns money from an established product or line of business — sales, account management, and the product and engineering capacity keeping that product competitive. The metrics are financial: revenue, margin, retention, profitability. This is the zone most of the company lives in, and almost always the zone that absorbs the most capacity.

Productivity Zone

The Productivity Zone is the enabling machinery. IT, HR, finance systems, internal tooling, platform infrastructure, customer success process, developer experience, onboarding flows, compliance — anything that supports the Performance Zone’s ability to earn revenue without directly earning it itself. The metrics are process metrics and operational efficiency: cycle time, cost-per-unit, automation rates, NPS.

Productivity is the zone that quietly absorbs capacity without anybody noticing. It’s where a CPO’s “just a quick internal tool” becomes 15% of the engineering roster over three years. See also Core vs Context and SAFe Enabler vs Business Work for adjacent framings of the same problem.

Incubation Zone

The Incubation Zone is where tomorrow’s bets live before they’ve proved they should be scaled. Small teams, VC-style milestone funding, explicitly insulated from Performance and Productivity metrics. The purpose is disciplined learning against the riskiest assumptions using the cheapest possible tests — exactly the territory covered by the early-stage validation cluster .

Crucially, Incubation Zone work is dedicated. This is the zone that fails most often in practice because it gets pattern-matched to “innovation time” or “Friday projects” — side-of-desk work that never reaches escape velocity.

Transformation Zone

The Transformation Zone is where an Incubation-Zone bet is being scaled into a material new line of business. Moore’s specific threshold is ≥10% of current enterprise revenue. Below that, the bet hasn’t “transformed” anything — it’s still an Incubation bet in denial. Above it, you’ve changed the company’s revenue mix.

The Transformation Zone is episodic, not continuous. You’re in it rarely — maybe once every five to ten years — and when you are, Moore’s framework is uncompromising: everything else subordinates to it for two to three years. The CEO personally runs the scale-up. Performance Zone metrics are relaxed where necessary. Productivity Zone improvements are deferred. Everybody knows what the company is trying to do.

2. The Real Question Boards Ask

Stripped of framework theatre, the question your board is asking at every meeting is: where is the money going?

Every piece of product and engineering capacity is fungible. Two million pounds allocated to Product X is two million pounds not allocated to Product Y. Total spend is roughly fixed year-on-year — you might flex it by 10–20% depending on the cycle, but no board approves a doubling of product spend without a lot of scrutiny. So the real portfolio question isn’t whether to spend more in aggregate. It’s what share of a fixed pot is doing which job.

Zone to Win translates that question into something a non-technical board director can reason about. Instead of asking “how much are we spending on the Acme platform versus the Zenith platform?” — which requires the board to know what each product does — the question becomes “what percentage of our total capacity is in Performance, Productivity, Incubation, and Transformation this year, and is that deliberate?”

That’s a question the CFO, the non-exec, and the PE board observer can all engage with. And it’s the same question they already ask about every other capital allocation the company makes.

3. Zone to Win Isn’t Prescriptive — It’s Diagnostic

Most of the existing internet coverage of Zone to Win treats it as a prescriptive framework: here’s the right mix, here’s how to organise to hit it. I think that misses the point.

Moore’s zones are most useful as a diagnostic vocabulary — a way of forcing honest visibility of your current portfolio shape. The framework’s value is not that it tells you to spend 15% in Incubation. It’s that once you’ve classified every pound against a zone, you can see whether your 15% is a real 15% or whether it’s a spreadsheet artefact. Most of the time, it’s the latter.

The comparison to Run / Grow / Transform is useful. RGT is the simpler three-bucket version of the same idea — “how much of our resource is keeping the lights on, growing the business, and making speculative bets?” Zone to Win sharpens the diagnosis in two ways. It separates Performance (direct revenue generation) from Productivity (enabling support), which RGT collapses into “Run”. And it distinguishes episodic Transformation (a specific bet being scaled) from continuous Incubation (the pipeline of experiments that feed Transformation), which RGT collapses into “Transform”.

If your board is already having the RGT conversation, Zone to Win doesn’t replace it — it extends it. It gives you one more lens to apply when the three-bucket picture looks reasonable but you suspect something’s off.

4. The Two Symmetric Failure Modes

Almost every portfolio I’ve reviewed as a non-exec or in PE diligence falls into one of two failure patterns. They look like opposites. They share a root cause.

The Zero-Transformation Portfolio

The first failure is a company whose spend is 100% Performance and Productivity Zone — no Incubation pipeline, no active Transformation. On paper this looks efficient: every pound is either earning revenue or directly supporting it. In reality it’s a company that has stopped investing in its next curve.

These companies are always surprised when disruption arrives. They have no bets in the Incubation pipeline, so they have nothing to scale when a market signal appears. The Innovator’s Dilemma playbook unfolds exactly as Christensen predicted — the current curve is defended optimally right up to the point where it stops mattering. By the time the board realises the company needs a Transformation, there is nothing in the pipeline credible enough to transform into.

The Transformation Theatre Portfolio

The second failure is the opposite on the surface and identical in substance. Three or four concurrent initiatives, all of them labelled “strategic” or “transformational”, none of them committed to, none of them staffed properly, none of them capable of reaching Moore’s 10% threshold. The core Performance Zone is under-resourced because of the distributed drain. The Incubation Zone has no discipline — it’s just a label applied to whichever pet projects the ExCo currently likes.

This is what Transformation theatre looks like. The company claims to be investing in the future. It is, in fact, buying several lottery tickets with money it should have used to defend the current curve. When you force honest zone-mix visibility against actual capacity, the picture resolves quickly: Performance Zone is down to 45% of capacity when it should be north of 60%, the “three Transformations” are three starving Incubations, and the board has been comfortable for two years because the narrative sounded strategic.

Both failures are fixable. Neither is fixable until the mix is visible.

Sign up (free) to see your honest zone mix

5. Why You Can’t See Your Mix Today

If visibility is the framework’s real job, the obvious question is: why don’t most companies already have it? A few recurring reasons — none of them deliberate, all of them structural.

Claimed vs Actual Spend

The claimed zone mix — the one in the board deck — is usually derived from project headers in a strategy document. The actual zone mix is the one you’d see if you audited how every engineer and every product person actually spent last quarter. These two numbers diverge in predictable directions: claimed Incubation always exceeds actual Incubation; claimed Transformation is almost always overstated; claimed Performance is almost always understated, because nobody wants to tell the board “most of our spend is just maintaining what we already have”.

The Shared-Services Illusion

Productivity Zone capacity absorbs the invisible middle of every engineering organisation. Platform teams, developer experience, internal tooling, observability, compliance — each of these has a legitimate claim on being “enabling”. But once you add them up, they frequently consume 25–40% of total capacity. Until they’re explicitly tagged as Productivity Zone and counted, they hide inside the “Performance” number and make Performance spend look considerably higher than it actually is.

Side-of-Desk Incubation

Incubation Zone capacity is almost never dedicated in the companies I see. It’s usually “20% time”, “innovation days”, or a senior engineer’s pet project running next to their Performance Zone commitments. The claimed Incubation Zone figure may be 10% of engineering; the actual, protected, genuinely-Incubation-Zone spend is closer to 1%. The rest is theatre — people pretending to do the future while actually doing the present.

The fix is simple and unpopular. Genuine Incubation Zone work requires a dedicated minimum viable team — two engineers and one product person, full-time, protected from Performance Zone demands, with a proper business case and explicit milestone funding. Anything less is side-of-desk theatre.

Maintenance Masquerading as Incubation

The final distortion is maintenance work wearing an Incubation label. A rewrite of an existing feature using new technology isn’t Incubation — it’s Performance Zone work with an interesting tech stack. Migrating a monolith to microservices isn’t Transformation — it’s Productivity Zone work that should be measured on operational efficiency, not on revenue uplift. A lot of engineering organisations quietly reclassify internal work into more exciting zones to keep the narrative fresh. The board then congratulates itself on an Incubation bet that’s actually just platform maintenance.

6. How AI Changes the Zone Mix You Should Expect

Zone to Win was written in 2015, and every existing article on the internet treats the framework as AI-neutral. It isn’t. The build-cost collapse of the last three years changes the economics of two of the four zones dramatically — and your zone mix should shift in response.

Incubation Zone is dramatically cheaper than it was. A two-engineer-and-one-product-person Incubation team can now get a working, testable product in front of real users in weeks rather than quarters. The cost of running a well-disciplined Incubation Zone has collapsed. The implication is that the number of bets you can reasonably carry is higher — but the discipline of killing the ones that don’t cross validation milestones is more important than ever, because cheap experiments without kill criteria quickly become a swamp of unfinished work.

Transformation Zone is harder, not easier. The cost of convincing a customer to switch products hasn’t changed at all since 2015. If anything it’s harder, because every competitor now has AI-powered cheap build costs too. What actually gets a new line of business to 10% of enterprise revenue is distribution, trust, references, brand, and channel — none of which AI has made cheaper. Transformation Zones in 2026 demand more CEO attention to the sales motion and the channel, not less.

Performance Zone is under more pressure. AI-era entrants can undercut mature products faster than ever. What used to be a five-year window to respond to a new entrant is now 12–18 months. Performance Zone capacity that isn’t at least partly defending against AI-era substitutes is quietly under-investing in its own survival.

Productivity Zone is in flux. AI tooling has made a lot of internal work redundant — you no longer need the bespoke reporting tool you built in 2019. Some Productivity Zone spend should be releasable back into Performance or Incubation. Equally, AI introduces new Productivity work: evaluation pipelines, observability for non-deterministic systems, model governance, prompt management. Expect churn in this zone, not stability.

The net is that the “right” mix, if such a thing exists at all, has moved. More Incubation in parallel, sharper Transformation discipline, more active Performance defence, and a net churn in Productivity that frees capacity rather than consuming it.

7. Products, Not Companies

A theme that runs through most of the lifecycle cluster applies to Zone to Win as well: the framework applies to a product, not to a company. A mature company has a portfolio of products at different lifecycle stages, and each of those products may belong to a different zone at the same moment.

A good example: a software company might have a mature flagship product in the Performance Zone, an internal platform in the Productivity Zone, three small Incubation experiments testing adjacencies, and — occasionally — a single Transformation Zone scale-up where one of last year’s Incubations earned enough validation to be committed to. The company isn’t “in the Performance Zone” or “in the Transformation Zone”. Its products are in different zones, and the portfolio-level picture is the sum of those individual diagnoses.

This matters because the commonest misuse of Zone to Win is to apply it to the company as a whole and conclude “we are in the Performance Zone” or “we need to shift to the Transformation Zone”. That’s a category error. Companies don’t move between zones; products do. Zone to Win is a tagging framework for the portfolio composed of those products, not a diagnosis of the company overall.

Try RoadmapOne — free sign-up to visualise your zone mix

8. When Zone to Win Doesn’t Fit Your Company

Moore wrote Zone to Win for mature enterprises. Its explicit assumptions are that you have material revenue to protect, a CEO with enough runway and board confidence to subordinate the company to a single Transformation bet for two or three years, and enough organisational slack to run a genuine Incubation pipeline. In the companies I do PE diligence and NED work with, those assumptions break more often than they hold.

Scale-ups Without Material Revenue

A Series B scale-up with £10m ARR doesn’t have a Performance Zone to protect in Moore’s sense. Everything it does is either direct revenue generation or a bet on becoming material. The four zones collapse into two: the work that is earning revenue now, and the work that is trying to make the core product good enough to scale. Forcing a Series B to tag capacity as “Productivity Zone” and “Transformation Zone” produces false precision. Use RGT or a Three Horizons view instead.

Mid-Market Without Organisational Slack

A £50m–£150m ARR company has material revenue but often lacks the organisational slack to commit to a true Transformation Zone. There is no CEO runway to subordinate the company for 2–3 years, and there is rarely a second-tier leadership bench deep enough to let the CEO focus exclusively on the Transformation. In these companies, Zone to Win is useful as a diagnostic vocabulary — what do we have in Incubation, is any of it scale-ready? — but the Transformation Zone itself is more often a “not yet” than a current bucket.

Single-Product Companies

If you have one product, you have one lifecycle curve. The zone question collapses into a lifecycle question: where is this product on the curve, and what does it need? Lean on the product lifecycle cluster rather than force-fitting a four-zone portfolio vocabulary onto a single-product business. Zone to Win becomes genuinely useful as soon as you have two or three products at different lifecycle stages — i.e. as soon as you are really a portfolio rather than a bet.

9. Making the Zone Mix Visible

The practical implementation of Zone to Win in a company running on RoadmapOne looks like this:

1. Tag every objective in the roadmap with exactly one zone. Performance, Productivity, Incubation, or Transformation. No compound tags. No “mostly Performance but partly Incubation”. If you can’t pick one, you haven’t decided what the work is for.
2. Allocate objectives to squads and sprints as usual, then aggregate the capacity-weighted zone mix at board level. This is the actual mix, not the claimed one.
3. Compare the actual mix to the claimed mix. The delta is the honesty gap. Discuss it with the board, and treat a large delta as a diagnosis in its own right.
4. Show the mix across products as well as across functions. Because products sit at different lifecycle stages , the healthy zone mix for each product is different. A mature product should be 70%+ Performance; a new product should be mostly Incubation. An aggregate mix that looks balanced can hide two products that are each badly misallocated for their stage.
5. Review quarterly, not continuously. The mix shouldn’t drift week-to-week. If it does, something else has gone wrong with your planning discipline.

This is exactly what the RoadmapOne analytics view already does for RGT tagging , and the same machinery applies to Zone to Win tagging. The point isn’t that Zone to Win is harder to implement than RGT — it’s that it produces a slightly sharper diagnostic for boards who want more granularity than three buckets.

10. What Healthy Looks Like (Without Being Prescriptive)

I said earlier the framework is diagnostic, not prescriptive, and I stand by that. But I can offer rough bands to watch, with the strong caveat that what’s healthy depends on your sector, your company’s lifecycle, and the state of your market.

These are bands, not targets. A 60/20/10/10 mix isn’t “correct” — it’s just not obviously broken. A 40/15/5/40 mix tells you something very specific is happening: a Transformation is underway and Performance is being squeezed. That might be exactly the right call. Or it might be a CEO pet project eating the core. Zone to Win doesn’t tell you which. It forces you to look.

11. When the Diagnosis Calls for a Dedicated Team

If your zone-mix review reveals that Incubation Zone spend is actually zero (or a theatre figure), the fix is a recurring pattern you’ll see across this blog. When an Incubation bet genuinely deserves capacity, it needs a dedicated minimum viable team — two engineers and one product person, full-time, insulated from Performance Zone demands, with a proper business case and protected milestone funding.

• A Horizon 3 bet that’s side-of-desk work for a Horizon 1 team is not an Incubation Zone bet. It’s Performance Zone work with aspirational labelling.
• A “Transformation” that doesn’t have the CEO personally running it is not a Transformation Zone bet. It’s a prioritisation problem.
• An Incubation team that’s being measured on Performance Zone metrics will fail within two quarters. The whole point of the zone is that the operating model is different.

If the framework tells you something needs investment, the framework also tells you the shape of that investment — dedicated, protected, and measured on zone-appropriate metrics. Skipping the shape question and throwing half a team at the problem is where most Incubation and Transformation bets die.

12. How Zone to Win Relates to Other Portfolio Frameworks

Zone to Win isn’t the only lens. It’s a sharper version of a broader family of portfolio-balance frameworks, and it pairs well with several:

• Run / Grow / Transform — Three-bucket simpler cousin. Start here if your board hasn’t had this conversation before; upgrade to Zone to Win once the RGT mix looks fine but something still feels off.
• McKinsey Three Horizons — Time-horizon view. Performance Zone ≈ H1, Incubation Zone ≈ H3, Transformation Zone is the moment an H2 becomes an H1.
• Innovation Ambition Matrix — Bansi Nagji and Geoff Tuff’s 70/20/10 core/adjacent/transformational split. Complementary risk-profile view.
• BCG Growth-Share Matrix — Financial-performance portfolio view (Stars, Cash Cows, Question Marks, Dogs). Pairs with Zone to Win — BCG tells you which products are Cash Cows; Zone to Win tells you what the whole portfolio’s capacity mix should look like.
• Core vs Context — Also Geoffrey Moore. A micro-version of the Performance vs Productivity Zone split, applied at the team level rather than the portfolio level.

Pick the framework whose question matches the question you’re trying to answer. Most boards don’t need more than one of these running at a time — running all five produces a flat mass of analysis and usually fewer honest decisions.

Frequently Asked Questions

What are Moore’s four zones?

Geoffrey Moore’s Zone to Win framework divides company capacity into four mutually exclusive zones. The Performance Zone generates today’s revenue from established products. The Productivity Zone enables that revenue generation — IT, internal tooling, compliance, developer experience. The Incubation Zone runs small, disciplined experiments against tomorrow’s bets, insulated from Performance metrics. The Transformation Zone is where a proven Incubation bet is being scaled into a material new line of business — defined by Moore as ≥10% of current enterprise revenue.

What does Zone to Win mean?

Zone to Win is shorthand for Geoffrey Moore’s 2015 portfolio-management framework, in which every pound of product and engineering spend is tagged to one of four zones: Performance, Productivity, Incubation, or Transformation. The phrase captures Moore’s central thesis — that mature enterprises win when they manage each zone under a different operating model, with different metrics, different governance, and different CEO attention, rather than applying a single performance lens to the whole portfolio.

How does Zone to Win work?

You tag every objective, initiative, and team to exactly one zone based on what the work is actually doing — earning revenue today (Performance), enabling revenue generation (Productivity), experimenting against tomorrow’s bets (Incubation), or scaling a proven bet to material size (Transformation). Aggregating the capacity-weighted mix at board level reveals the real portfolio shape, which can then be compared against what leadership claims the mix is. The framework forces honesty, not a specific ratio.

What are the benefits of Zone to Win?

The primary benefit is visibility of your actual portfolio mix versus the claimed one. Competing articles list benefits like “strategic clarity” or “aligned decision-making”, but those are downstream of the real mechanic. Once every pound of spend is tagged to one of four zones, the board can see whether the company is over-investing in Performance, starving Incubation, or running three simultaneous “Transformations” that are really starved bets in disguise. The framework diagnoses; leadership decides.

How is Zone to Win different from Run / Grow / Transform?

RGT is the simpler three-bucket framework. Zone to Win splits RGT’s “Run” into Performance (revenue-generating) and Productivity (enabling), and splits RGT’s “Transform” into Incubation (continuous pipeline) and Transformation (episodic scale-up). If RGT is telling you enough, stay with RGT — it’s easier to report and easier for a board to engage with. Reach for Zone to Win when your three-bucket picture looks fine but you suspect something’s wrong that the extra granularity would surface.

Can a company be in more than one Transformation Zone at once?

Not really. Moore is unambiguous on this point, and experience bears him out: the Transformation Zone demands CEO-level attention and company-wide subordination. Two concurrent Transformations means at least one isn’t actually a Transformation — it’s a starved Incubation with a label problem. If your strategy document says you have three Transformations underway, you almost certainly have zero.

What’s the “right” allocation percentage for each zone?

There isn’t one. Healthy bands are 50–70% Performance, 15–25% Productivity, 5–15% Incubation, and 0% Transformation most of the time with 10–20% when a Transformation is active. But these are bands to spark discussion, not targets to chase. The framework is diagnostic — it helps you see your mix and judge whether it’s deliberate. Hitting a specific ratio isn’t the point.

What if we have no Incubation Zone spend at all?

Then you have no future-curve pipeline, and you should expect to be surprised by disruption. That’s not automatically a bad call — a business harvesting a mature product for cash may legitimately have zero Incubation. But the board should be making that choice knowingly, not discovering it by accident. If the zero is deliberate, fine. If it’s emergent, fix it.

How often should we review our zone mix?

Quarterly is about right. Monthly is over-sampling — the mix doesn’t move that fast. Annually is under-sampling — you won’t notice the Productivity Zone absorbing capacity until it’s already happened. Tie the review to the board cycle so the conversation has stakes.

Does Zone to Win still apply in the AI era?

Yes, but the economics have shifted. Incubation is much cheaper (smaller teams can run more experiments in less time), Transformation is harder (distribution and trust haven’t got cheaper), Performance Zone is under more pressure from AI-era entrants, and Productivity Zone is churning — some old internal tooling is redundant, some new AI-specific work has appeared. Expect the healthy zone mix to tilt slightly more toward Incubation and sharper Transformation discipline, with more active Performance defence.

Is Zone to Win the same as the Three Horizons model?

No, though they overlap. Three Horizons is a time-based view — short, medium, long-term. Zone to Win is an operating-model view — four zones, each with different metrics, governance, and CEO attention. H1 roughly maps to Performance, H3 roughly to Incubation, and the Transformation Zone is where an H2 becomes an H1. They ask different questions and can be used together.

Sign up (free) to tag objectives by Zone to Win

Conclusion

Zone to Win is one of the sharper portfolio-tagging frameworks available. Four zones, mutually exclusive, directly mapped to what a pound of spend is actually doing — the vocabulary is good. But the framework’s real value isn’t that it prescribes the right mix. It’s that once every objective in your roadmap is tagged to exactly one zone, the mix becomes visible. The board can see whether you’ve invested zero in Transformation (a slow-motion disruption waiting) or whether you’ve got three concurrent “Transformations” starving the core (theatre dressed as strategy).

Most of the time, the conversation that matters isn’t “are we at the right zone mix?” It’s “is our zone mix deliberate?” The framework earns its keep by forcing that question into the open. What you do with the answer is up to the board.

Pick up Zone to Win when you already have RGT -style tagging running and want a sharper view; reach for RGT or Three Horizons if you’re at an earlier stage of portfolio maturity. Either way, the underlying discipline is the same: tag every objective, aggregate the mix, compare claim to reality, and let the board see what’s actually happening.