A company is taught as the hero who beat disruption and the victim who lost to it — same company, same decade. The textbook says it forgot the lesson. The lesson never fit the second fight.
Pairs with the Cannibalization Decision Tree — a ready-to-use strategy tool. Get it — included with a subscription, or $1.99 →
In April 1998, Intel did something a company at the top of its market almost never does on purpose: it shipped a deliberately worse, deliberately cheaper version of its own crown jewel. The Celeron stripped out the fast cache, undercut the Pentium II's price, and pointed straight at the part of the market where Intel made the least money per chip.4 It looked like corporate self-harm. It is now taught in business schools as the opposite - the canonical case of a giant that ate its own lunch before a rival could. Clayton Christensen put Intel in his book as the firm that beat the innovator's dilemma. Nine years later, the iPhone shipped with no Intel inside, and the same company that had been the textbook hero became the textbook victim.
The official story is that Intel got paranoid, won, then got fat and stopped being paranoid, and lost. It's a tidy arc and it's mostly wrong. The Celeron wasn't a blank-sheet act of strategic foresight; Intel was already bleeding low-end units when it moved. And the mobile failure wasn't a failure of paranoia at all. Intel saw the disruption, owned a mobile chip, and tried to enter the market. The two episodes look like the same lesson learned and then forgotten. They were never the same test.
The Celeron wasn't foresight. It was a counterpunch.: the heroic version has a CEO seeing the future; the record has a company already bleeding and swinging back
The heroic version has Andy Grove staring into the middle distance and choosing to cannibalize the Pentium before someone else did. The record is less flattering and more interesting. By 1998, Cyrix's 6x86, AMD's K6, and IDT's WinChip had carved into the cheap-PC market Intel had been ignoring, and the Celeron was the response to that loss - reactive, not prophetic.4 Worse, the first version Intel shipped, the cacheless Covington, performed so poorly it earned a bad reputation almost immediately. The Celeron that actually worked - the Mendocino, with 128 KB of on-die L2 cache - didn't arrive until that August.4 Intel didn't conjure the right answer; it shipped the wrong one first and fixed it under fire.
But here is why it still counts as beating the dilemma: Intel was willing to take the financial pain on purpose. Look at the years on either side of the launch. In FY1997, Intel earned $9.887 billion in operating income on $25.070 billion of revenue. In FY1998 - the Celeron year - revenue actually grew to $26.273 billion, yet operating income fell to $8.379 billion.12 More sales, less profit. That's not what an accident looks like. That's the signature of a company deliberately compressing its own margins to deny a rival oxygen, and by the end of 1998 the Celeron was the second-highest-volume PC microprocessor in the world.5
And notice what made it possible. The Celeron threat was x86-adjacent. The same instruction set, the same fabs, the same software, the same customers - a cheaper chip aimed at the bottom of the exact market Intel already owned. Intel had done this before: its own filings note that 486 revenues 'declined substantially' as demand shifted to its more advanced chips, and Intel rode that shift rather than fighting it.3 Cannibalizing the low end of x86 with more x86 is the easiest hard decision in the world. You lose margin, not identity.
The thing Intel actually was: not a chip company that made x86, but x86 itself — a self-image, not a product line
Here is the thesis. Intel wasn't a chip company that happened to make x86. Intel was x86 - a performance company whose entire muscle memory, fab strategy, and self-image were built around making the fastest x86 processors on earth and charging for the privilege. The Celeron didn't threaten that identity; it served it, by extending x86 down-market. Mobile threatened the identity itself, because mobile didn't want performance-at-any-power. It wanted the opposite: just-enough performance at almost-no-power. That isn't a cheaper version of what Intel was. It's a different thing entirely.
| The Celeron threat (1998) | The mobile threat (2007) | |
|---|---|---|
| What was at risk | Margin on the low end | The whole architecture |
| Instruction set | x86 - Intel's home turf | ARM - someone else's |
| What it asked of Intel | Sell x86 cheaper | Be a different kind of company |
| Could paranoia fix it | Yes - and did | No - wrong tool entirely |
The iPhone chip Intel passed on was never x86: the one fact that dismantles the tidy margin-cowardice story everyone repeats
The mobile story usually gets told as a margin failure - Intel's then-CEO Paul Otellini turning down Apple because the price was too low, the same failure of nerve that the Celeron supposedly cured. Otellini said as much in his 2013 exit interview: the chip Apple wanted was priced 'below our forecasted cost. I couldn't see it.' He added the brutal coda - 'in hindsight, the forecasted cost was wrong and the volume was 100x what anyone thought.'6 If that were the whole story, it would indeed be the innovator's dilemma in its purest form: a fat incumbent protecting its margins into irrelevance.
But the chip Apple approached Intel about was the ARM-based XScale - not x86.7 That single fact dismantles the popular synthesis. There was no architecturally feasible path to putting an x86 chip into the original iPhone; x86 simply could not hit the power budget. So the decision wasn't 'should we let Apple buy our crown jewel cheaply.' It was 'should we commit to a non-x86 architecture we're skeptical of, at a price below cost, for a phone that might not sell.' And Intel, being an x86 performance company at its core, did the consistent thing - and then sold the XScale business to Marvell in 2006, walking away from the very asset that could have carried it into mobile.7
“There was a chip that they were interested in that they wanted to pay a certain price for and not a nickel more and that price was below our forecasted cost. I couldn't see it.”6
Even the price story is contested. Steve Jobs's biography tells it differently: Apple, in this account, soured on Intel partly because it was 'slow like a steamship' and partly over fears of IP leakage - not purely cost.8 Otellini disputed that framing. Two senior accounts, neither confirmed by a primary document, pointing at different villains. The popular version that flattens all of it into 'Intel guarded its margins' is the one thing the record doesn't actually support.
But isn't this just the dilemma, dressed up?: the fair objection — and why paranoia is the wrong tool against a threat to your premise rather than your business
The fair objection: this is too convenient. 'Identity, not margin' sounds like an excuse for a company that simply got lazy after winning. And Intel did own XScale, did have the ARM asset, did try to enter mobile - which on the surface looks exactly like the firm that 'failed to listen to the disruptive signal' that Christensen described. So why isn't this the dilemma?
Because the dilemma, in its classic form, is a failure of attention - the incumbent can't see the cheap-and-worse product coming until it's too late. Intel saw mobile fine. It held the asset. The failure was the layer underneath attention: an organization whose every advantage - the world's best fabs, a process roadmap tuned for raw performance, a sales force that sold gigahertz - was built for a game ARM wasn't playing. Grove-style paranoia is a tool for fighting threats to your business. It is useless against a threat to your premise. You can be maximally paranoid and still lose, if the thing you're paranoid about is the thing that made you. The Celeron proved Intel could cannibalize a product. Mobile asked it to cannibalize itself - and there is no quarter where that shows up as a clean, profitable down-market launch.
Not every threat is the same threat, and treating them alike is how good companies die confidently. One kind attacks your margin - a cheaper version of what you already are, aimed at the bottom of your own market. That one you can fight by cannibalizing yourself, because winning costs you profit, not identity, and the muscles you already have still work. The other kind attacks your premise - it rewards the opposite of what you're built to be best at. No amount of vigilance fixes that, because vigilance points your existing strengths at the problem, and your existing strengths are exactly what's now a liability. Before you reach for the Celeron playbook, ask the harder question: is the disruptor selling a worse version of my thing, or a different thing that makes my thing irrelevant? The first you out-execute. The second you have to become someone else to survive - and most companies can't.
Intel didn't forget how to be paranoid. It remembered perfectly. It just discovered that the lesson it had learned in 1998 - cut your own margin before someone else does - was an answer to a question mobile never asked. The Celeron was a company defending its territory and winning. The iPhone was a company being told its territory had moved, to ground its tools couldn't reach. The genius of beating the innovator's dilemma the first time turned out to be the trap the second time: it taught Intel that the disruption it would face next would also be x86, also be performance, also be a thing it could simply outspend. The most dangerous lesson is the one that worked.
Cannibalization Decision Tree
A decision tree for the moment the new thing threatens the cash cow: is the disruption real, will someone else do it if you don't, and can you afford to bleed your own margin to own the future? Blank to run on your own line; filled as the worked example tracing how the story's incumbent chose to cannibalize — or flinched and got cannibalized.
Included with any subscription, or unlock this tool for $1.99. Get it → · See plans →
Sources
Where this comes from — the filings, records, and reporting behind it.
- 1Intel FY1997 net revenues were $25.070 billion and net income was $6.945 billion; FY1998 net revenues were $26.273 billion with operating income of $8.379 billion, down from $9.887 billion in FY1997.
- 2Intel FY1998 net revenues were $26.273 billion and operating income was $8.379 billion.
- 3Intel FY1996 10-Q: revenues from the Intel486 microprocessor family 'declined substantially, primarily due to a major shift in market demand toward the Company's more advanced microprocessors'; Pentium revenues drove H1 1996 growth of 24% YoY.
- 4The Celeron was introduced April 15, 1998, in response to Intel's loss of the low-end market to Cyrix 6x86, AMD K6, and IDT Winchip. The initial cacheless Covington Celeron was performance-poor; the successful Mendocino revision (with 128 KB on-die L2 cache) launched August 24, 1998.Wikipedia, Celeron ↗ · 2025-07-01
- 5Intel's official history states that by end of 1998, Celeron was the second-highest volume PC microprocessor in the world, second only to Pentium II, and was introduced to appeal to the growing market for inexpensive PCs.
- 6Paul Otellini, in a 2013 exit interview with The Atlantic, stated Intel passed on building the iPhone chip because Apple's offered price was below Intel's forecasted cost: 'there was a chip that they were interested in that they wanted to pay a certain price for and not a nickel more and that price was below our forecasted cost. I couldn't see it.' He also said 'in hindsight, the forecasted cost was wrong and the volume was 100x what anyone thought.'
- 7The chip Apple approached Intel about for the iPhone was the ARM-based XScale—not an x86 processor. Intel subsequently sold XScale to Marvell in 2006. There was no architecturally feasible path to putting x86 in the original iPhone.Stratechery / Ben Thompson, Paul Otellini's Intel ↗ · 2013-03-21
- 8Steve Jobs's biography records a conflicting account: Apple rejected Intel for future iPhone chips partly because Intel was 'slow like a steamship' and partly due to IP leakage concerns—not purely on price. Otellini disputed this framing.