Zone to Win by Geoffrey Moore — Cliff Notes Summary

The two operating models Moore forces you to choose between

The entire book turns on a single either/or that most executives refuse to name out loud: you can run a business optimized to hit the number, or you can run one optimized to create a new number, but you cannot run both inside the same P&L, the same governance cadence, and the same comp plan. Moore's framing is not that one is better. It is that they are structurally incompatible, and that pretending otherwise is what kills incumbents.

Option A — the single operating model. This is the default state of nearly every company above roughly $1B in revenue. There is one annual operating plan, one forecast cadence, one set of KPIs (revenue, gross margin, operating income, retention, win rate), one hiring profile, one procurement process, one approval threshold for capital. New ventures are treated as line items inside an existing GM's P&L. The advantages are real and worth stating fairly: total clarity of accountability, one language for the board, no internal arbitrage between units, and the lowest possible coordination overhead. Companies that run this way execute beautifully — right up until the market shifts underneath them.

The failure mechanics are mechanical, not moral. A $5M emerging line inside a $5B P&L is 0.1% of the number. It cannot move the GM's bonus. It consumes the GM's scarcest resource — attention and headcount — and returns nothing measurable inside the fiscal year. So the GM does the economically rational thing: staffs it with whoever was available, benchmarks it against enterprise-grade revenue expectations it cannot possibly meet, and quietly lets it die at the 18-month review. Moore's point is that no amount of "innovation culture" survives this arithmetic. The incentive gradient beats the poster on the wall every single time.

Option B — the four-zone model. Here the company deliberately runs four different operating models under one roof, each with its own rules:

• Performance Zone — the businesses that produce the current revenue line. Measured on revenue, gross margin, win rate, retention, operating income, and above all forecast accuracy. Not measured on innovation output, and explicitly relieved of that expectation.
• Productivity Zone — the shared services that everyone consumes: finance, HR, IT, legal, marketing operations, sales operations, enablement. Measured on cost of delivery and cycle time, not on revenue it does not own.
• Incubation Zone — small autonomous teams, typically 5-20 people each, chasing emerging categories on a three-to-five-year horizon. Measured on category-creation evidence — design wins, lighthouse customers, a repeatable use case — not on near-term revenue.
• Transformation Zone — the single initiative the CEO has personally committed to scaling from venture into a material business inside 12-24 months.

The cost of Option B is honest coordination overhead: four sets of metrics, four capital rules, four governance cadences, and a board that has to be re-educated about why one unit is deliberately not profitable. The benefit is that each kind of work is finally judged against a standard it can actually meet.

A third option Moore treats sceptically: the separate subsidiary. The classic Christensen prescription — spin the disruptor out, insulate it completely, let it run its own race — solves the incentive problem by amputation. Moore's objection is that it also amputates the incumbent's only real advantage: the installed base, the sales force, the brand, the balance sheet, the channel. If the new venture could win on its own, it would not need you. The four-zone model is deliberately harder because it keeps the venture inside the corporate body while giving it different rules. That is the whole design intent — same body, different metabolism.

Worth noting where this sits relative to neighboring frameworks. Govindarajan's Three Box Solution partitions by time (manage the present, selectively forget the past, create the future) and is closer to a leadership discipline than an org chart. McKinsey's Three Horizons partitions by maturity of the revenue stream and is mostly a portfolio-planning lens. Moore's zones partition by *operating model* — which is why his framework maps directly onto reporting lines, comp plans, and QBR calendars in a way the other two do not. If you want a planning vocabulary, take Horizons. If you want to redraw the org, take zones.

How to decide which posture you are actually in

Before choosing a zone structure, Moore makes you answer a prior question: are you playing offense or defense? The distinction sounds academic and is anything but, because it changes who resists you and how hard.

Zone Offense means you are the attacker. Your Performance Zone is healthy, the numbers are good, and you are choosing to reallocate resources toward a category where you are not yet the incumbent. This is politically brutal precisely *because* the numbers are good. Every Performance GM you ask for headcount, quota relief, or R&D capacity has a defensible answer: "my segment is growing 14% and you want to take three of my best reps." They are not being obstructive; they are being correct within their own frame. Only the CEO can overrule that, and only with board cover.

Zone Defense means someone is attacking you. A native competitor with a structurally lower cost base or a fundamentally better UX is compounding into your category. Defense is politically easier — the burning platform is visible — and existentially harder, because you are starting late against someone faster. Moore's caution here is about timing: most companies recognize defense conditions eighteen months after the optimal entry point, which turns a manageable reallocation into an emergency one.

The decision to enter a Transformation Zone at all should clear a specific bar. Moore's rough shape: the candidate business has graduated out of Incubation, has demonstrated a repeatable use case with real lighthouse customers, is at a scale where materiality is credible (he uses the neighborhood of $100M as the point where a business can plausibly be scaled toward $1B), and there is a path where the category itself is growing fast enough to absorb aggressive investment. If the candidate fails any of those, you do not have a Catalyst Initiative — you have an Incubation project that someone wants to over-fund.

The single most-skipped step in that flow is the board ratification box. Moore is emphatic that entering a Transformation Zone creates near-term P&L pressure that public-market analysts will punish, and that a CEO who has not secured explicit board sign-off will fold the moment a soft quarter prints. The ratification is not ceremony — it is the political insurance that keeps the reallocation from being unwound in month seven.

The numbers and time horizons behind each zone

Moore is a strategy writer, not a metrics vendor, and he is deliberately light on precise financial figures. What he does give you are horizons, team sizes, and metric *categories* — and those are the operationally useful parts. Here is what each zone actually runs on.

Performance Zone economics. Horizon: the current fiscal year, reviewed quarterly. Metrics: revenue against plan, gross margin, operating income, win rate, net retention, and forecast accuracy. Moore singles out forecast accuracy as the underrated one — a Performance GM who consistently calls the number within a tight band is doing the job, because everything downstream (hiring plans, capital allocation to other zones, the transformation trade itself) depends on the current business being predictable. The cadence is annual operating plan, quarterly business reviews, monthly segment forecasting. Capital rules: incremental, ROI-justified, payback inside the planning horizon.

Productivity Zone economics. Horizon: continuous. Metrics: cost of service delivery, cycle time, and — the one most companies miss — *responsiveness to non-Performance zones*. Moore's sharpest practical insight in this section is that shared services default to serving the Performance Zone, because Performance is the loudest customer and the one whose requirements (predictability, compliance, low-risk procurement, enterprise-grade security review) are most legible. The result is that an Incubation team of eight people needing a lightweight stack gets routed through a procurement process designed for a $40M ERP rollout, and dies of paperwork. The fix Moore prescribes is explicit zone-aware SLAs: a fast lane for Incubation with different thresholds, different approval limits, and an accepted higher risk tolerance. Practically this means someone in the Productivity Zone owns "startup services" as a named responsibility with its own turnaround targets.

Incubation Zone economics. Horizon: three to five years to category materiality, with a hard prove-or-kill checkpoint Moore places around 36 months. Team size: small and dedicated — roughly 5-20 people, not a matrixed side-of-desk arrangement. Metrics: design wins, lighthouse customers, evidence of a repeatable use case, and progress against milestone-based funding tranches. Capital rules: venture-style. Fund the next milestone, not the next fiscal year. The default expected outcome is failure, and Moore treats that as a feature — the zone's economic function is to *kill bad bets cheaply and early* so the company is not carrying zombie projects that consume attention without consuming enough budget to trigger a review. A portfolio where most incubations die on schedule is working correctly.

Transformation Zone economics. Horizon: 12-24 months from entry to materiality. Metrics: market share, design wins, reference customers, gross adds — deliberately *not* gross margin or operating income, because optimizing margin during a land-grab is how you lose the category. Capital rules: fund for growth, accept negative contribution. Moore's scale intuition is that a Catalyst Initiative worth a Transformation Zone is one that can plausibly reach the $1B line-of-business level, which is why he pegs the graduation-out-of-Incubation threshold well below that — around the $100M mark, with a credible path to roughly 10x from there.

The comp rewiring is the part everyone underestimates. Moore is explicit that the field force must be paid to lead with the Transformation product. If a rep can hit quota selling the mature Performance product at a familiar discount and a known cycle length, they will — and no amount of enablement changes that. The mechanics are unglamorous: separate quota retirement rates, accelerators on Transformation bookings, sometimes a carve-out where Transformation revenue does not count against a Performance GM's cost-of-sales ratio. Get this wrong and the Transformation Zone becomes a marketing exercise with a product attached.

The R&D cadence changes too. Moore contrasts an 18-month enterprise release cycle against roughly a six-month cadence for the Transformation product. That is not a tooling preference; it is a consequence of the metric change. If you are measured on reference customers rather than margin, you need to close the feedback loop with those customers several times inside the transformation window.

Sequencing the change without breaking the current quarter

Knowing the model is easy. The implementation is where nearly all of the failure lives, and Moore's final chapters are effectively a catalog of how it goes wrong.

Failure mode one — declare without funding. The most common by a distance. The CEO announces a Transformation Zone at the kickoff, the press notices, and then the resources never move. The venture gets a fractional team, borrowed engineers, and a sales overlay of three people covering a global territory. Eighteen months later it has missed every milestone, the initiative is quietly wound down, and the organization concludes that "disruption is hard" — when what actually happened is that the trade was never made. The diagnostic is simple and brutal: look at the headcount and capital that physically moved out of Performance in the first two quarters. If the answer is approximately none, the Transformation Zone does not exist regardless of what the org chart says.

Failure mode two — two or three transformations at once. This is the sophisticated version of the same error. The company genuinely funds three simultaneous pivots, splits the reallocated resources three ways, splits the CEO's calendar three ways, and produces three underpowered efforts instead of one decisive win. Moore's single-transformation rule is not about capacity in the abstract — it is about the specific scarcity of CEO attention and political capital, which do not scale by hiring.

Failure mode three — commingling Incubation and Performance. The $5M line inside the $5B P&L. Structurally guaranteed to be starved, ignored, or killed for missing expectations it was never sized to meet.

The sequencing that avoids all three has a rough order:

1. Separate the books before you separate the org. Get Incubation and Transformation candidates out of Performance P&Ls and into their own reporting lines with their own metric sets. This is a finance exercise and can happen quietly, before any announcement.
2. Establish the Productivity fast lane. Stand up zone-aware SLAs so that when Incubation teams start moving fast, the shared services layer does not become the bottleneck. Doing this after you launch ventures means the first two die of procurement.
3. Build the Incubation portfolio and let it run. You cannot have a Catalyst Initiative without a pipeline that produced one. Fund several small bets on milestones, enforce the prove-or-kill discipline honestly, and accept that most will end.
4. Ratify the Catalyst at board level. Explicit sign-off on the trade, including the expected softness in near-term results and the specific quarters where it will show.
5. Move the resources in one visible block. Partial, apologetic reallocation signals to the organization that the trade is negotiable — and it will be renegotiated in every subsequent forecast call. One decisive move, announced with the reasoning, is more survivable than six months of attrition.
6. Rewire comp in the same cycle as the resource move. Not the following plan year. The field will follow the comp plan, not the strategy deck.
7. Graduate and reset. When the Transformation business becomes material, move it into the Performance Zone under a GM — often the leader who scaled it — and free the CEO's calendar for the next Catalyst.

The sequenced example Moore leans on hardest is Salesforce: Sales Cloud as the original Performance business, then Service Cloud as the first Catalyst, then Marketing Cloud (arriving via the ExactTarget acquisition), then the platform play, then AppExchange as an ecosystem move, with Einstein and later Data Cloud and Agentforce continuing the pattern. The instructive part is not that each wave succeeded — it is that they were run *in sequence*, each personally driven from the top, with the prior wave's leader graduating into a Performance role as the next one started. That sequencing discipline is the transferable lesson, not the specific product names.

What holds up a decade on, and what needs amending

The book landed in 2015. Read now, parts of it have aged into obviousness and parts have genuinely strained.

What has strengthened. The central incompatibility claim is more true in the AI era, not less. Every incumbent with a large, healthy, margin-rich Performance business facing a native competitor built on a fundamentally different cost and interaction model is living the exact problem Moore described — and most are visibly struggling to authorize a real Transformation Zone rather than an innovation-theater version of one. The single-Catalyst rule has also been repeatedly re-validated by conglomerates that attempted several simultaneous pivots and diluted all of them.

What needs amending. Three things.

First, Moore underweights bottom-up, product-led adoption. His model assumes scaling requires top-down mobilization — the CEO reallocating enterprise sellers toward a new product. In a product-led motion, adoption can compound through self-serve usage before any executive reallocates anything, which blurs the boundary between Incubation and Transformation. The graduation gate in a PLG context looks less like "the CEO decided" and more like "the usage curve decided, and the CEO is now catching up."

Second, ecosystem and platform transformations do not fit cleanly. When the catalyst is an API surface or a partner ecosystem rather than a product with a quota attached, the Transformation Zone's metrics (design wins, reference customers, gross adds) map awkwardly onto what actually matters — developer adoption, integration depth, partner-sourced pipeline.

Third, the one-transformation-at-a-time rule is under real pressure when the disruption surface is multi-dimensional. If the shift simultaneously touches the model layer, the data layer, the interaction layer, and the regulatory layer, some practitioners now argue for a single Catalyst *theme* with two or three tightly coordinated sub-zones under one executive owner. That is a friendly amendment rather than a refutation — it preserves the underlying point (concentrated attention beats distributed attention) while acknowledging that a modern catalyst may not be a single product.

For anyone selling into large enterprises, the practical use of this Cliff Notes summary is diagnostic rather than academic. Draw the four zones for your largest account. Identify which zone your product lands in. If it lands in Performance, you are selling efficiency against a budget that exists — a shorter cycle, a smaller deal, a procurement-led process. If it lands in Transformation, you are selling into a CEO-sponsored initiative with real urgency, real budget, and a compressed timeline — but you will lose if the account's transformation is a declared-but-unfunded one. The tell is whether resources physically moved. Ask the question directly in discovery, and you will qualify better than a competitor selling on features.

The same diagnostic runs internally. Pick your own company, name which zone each initiative belongs to, and find the one being asked to do two jobs at once. That mismatch is where the next failure originates — and it is the single most useful thing to carry out of Geoffrey Moore's book.

Related questions

How is Zone to Win different from Crossing the Chasm?

Crossing the Chasm is about a single product moving from early adopters to mainstream buyers. Zone to Win is about the *organization* — how an established company structures itself to run several such crossings over time without the mature business smothering the new one.

Can a company under $100M in revenue use the four zones?

Partially. The logic — separating sustaining work from new bets and refusing to judge both on the same metrics — applies at any size. The formal governance, board ratification, and dedicated shared-services lanes assume enterprise scale and are usually overkill below a few hundred million.

What happens to a Transformation that fails?

Moore's prescription is to sunset or divest rather than let it linger. The cost of a failed transformation is not primarily the money; it is the CEO's calendar and the organization's political capital, both of which stay locked up until the initiative is formally ended.

Does the Incubation Zone need its own P&L?

It needs its own books and milestone-based funding, but not a conventional P&L, because a conventional P&L imports the wrong metrics. Fund tranches against evidence — design wins, lighthouse customers, repeatable use case — rather than against a revenue forecast it cannot honestly produce.

How does this compare to the Three Horizons model?

Three Horizons partitions by revenue maturity and is mainly a planning lens. Moore's zones partition by operating model, which makes them actionable on reporting lines, comp plans, and governance cadence — a redraw of the org rather than a slide in the strategy deck.

FAQ

What is the core problem Zone to Win solves?

It explains why established companies fail at disruption. Moore's argument is that the cause is structural rather than creative: sustaining performance and transformational growth are run inside a single operating model wired to protect the current quarter, and that model reliably starves the new work. The book's prescription is to stop asking one operating model to do two incompatible jobs.

How does Moore define the four zones?

Performance owns the current revenue line and is measured on the number. Productivity delivers shared services — finance, HR, IT, legal, sales and marketing operations — at reasonable cost without becoming a bottleneck. Incubation runs small autonomous bets on emerging categories over a three-to-five-year horizon. Transformation scales one graduated venture into a material business. Each zone gets its own metrics, governance, hiring profile, and capital rules.

What is a Catalyst Initiative?

The single transformation the CEO personally leads in a given cycle. It has graduated out of Incubation, proven a repeatable use case with real customers, and now needs concentrated resources to scale into a material line of business inside roughly 12-24 months. Moore's rule is one at a time — the binding constraint is CEO attention and political capital, neither of which scales by delegating.

Why does the CEO have to lead it personally?

Because the transformation requires taking resources — headcount, capital, sales capacity, R&D bandwidth — away from Performance Zone leaders who are hitting their numbers and have every incentive to resist. A sponsor or a steering committee cannot make that trade stick. Only the CEO, with explicit board ratification, has the authority to reallocate and to keep the reallocation from being quietly unwound.

Is Zone to Win only useful to Fortune 500 executives?

That is the primary audience, and the governance assumptions are built for enterprise scale. But the underlying discipline — don't judge new bets on mature-business metrics, don't run three pivots at once, don't leave an emerging line buried inside a large P&L — transfers to any organization with an established core and something new it is trying to grow. Adapt the mechanics; keep the logic.

Does the book give hard financial figures?

Sparingly. Moore works in horizons, team sizes, and metric categories rather than precise financials — three-to-five-year Incubation horizons, roughly 36-month prove-or-kill checkpoints, 12-24 month transformation windows, small dedicated teams, and materiality thresholds expressed as orders of magnitude. Treat the specific dollar figures as illustrative scale markers, not as benchmarks to plan against.

Sources

• https://www.geoffreyamoore.com/
• https://hbr.org/2015/05/zone-to-win
• https://www.diversionbooks.com/
• https://www.hbs.edu/faculty/Pages/profile.aspx?facId=6496
• https://en.wikipedia.org/wiki/Crossing_the_Chasm
• https://en.wikipedia.org/wiki/The_Innovator%27s_Dilemma
• https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights
• https://www.tuck.dartmouth.edu/faculty/faculty-directory/vijay-govindarajan
• https://investor.salesforce.com/
• https://www.goodreads.com/book/show/25733988-zone-to-win

Related on PULSE

• [Escape Velocity by Geoffrey Moore — Cliff Notes Summary](/knowledge/bs0203)
• [Inside the Tornado by Geoffrey Moore — Cliff Notes Summary](/knowledge/bs0201)
• [Crossing the Chasm by Geoffrey Moore — Cliff Notes Summary](/knowledge/bs0046)
• [Conversations That Win the Complex Sale by Erik Peterson and Tim Riesterer — Cliff Notes Summary](/knowledge/bs0294)
• [The Win Without Pitching Manifesto by Blair Enns — Cliff Notes Summary](/knowledge/bs0067)