Zone Offense vs. Zone Defense

Definition

Disruption hits a company from one of two directions: either the company voluntarily adds a disruptive new line of business to attack someone else's market ("zone offense"), or an outside disruptor attacks the company's own established franchise ("zone defense"). The two demand opposite moves — offense reallocates resources toward a new, unproven business at the expense of the core; defense reallocates resources to modernize and protect the core, shelving any offensive ambitions. The annual planning process must declare the transformation zone's state as exactly one of inactive, proactive, or reactive — "it is imperative... to declare one—and only one—of these states unequivocally."

In the Book

Chapter One frames the split from the outset: "In markets where you want to be the disruptor... you must catch the next wave. At the same time, in those markets where your current franchise is the incumbent... you have to play defense." The book's running examples make the asymmetry concrete — Salesforce under Marc Benioff plays offense, taking ExactTarget's marketing-cloud incubation-zone business and promoting its GM into the performance matrix as a new row, dramatically reallocating sales, marketing, and business-development resources toward it. Microsoft, described in Chapter Eight, plays defense against the shift to mobile and cloud, where the priority is reengineering the existing Windows/Office operating model rather than launching something net-new. Chapter Seven's "Installing Zone Management" makes the discipline explicit: declare the transformation zone inactive, proactive, or reactive before proceeding, because "depending on which state is declared, the remainder of the planning process unfolds very differently."

Why It Matters

Treating "we need to innovate" and "we need to protect the core" as the same problem is why so many transformation efforts stall — the two require contradictory resource decisions (fund the new thing vs. fortify the old one) and contradictory leadership styles (bold risk-taking vs. steady defense). Forcing an organization to name which game it is playing, before allocating a single dollar, prevents the muddled half-measures that satisfy neither the offense nor the defense.