How BlackBerry Died
Why this is in the vault
This is the closing case in Commoncog's "Navigating Disruptive Shifts" sequence (case count at 15 per the email) — the canonical "incumbent saw it, understood it, and still lost everything" example, worth keeping on file as the counterweight to the Blockbuster case's "incumbent nearly won" counter-example already in the vault.
The core argument
The email itself is a curated pointer to a members-only case (full body paywalled; visible content is the framing intro plus a WebFetch preview of the opening section). Cedric frames this as the fourth and last installment before he publishes his own cross-case reactions next week, following Amazon Surviving the Dotcom Bust, Ford Surviving the GFC, and Blockbuster vs. Netflix. The case draws on Jacquie McNish and Sean Silcoff's 2016 book Losing the Signal and asks the reader to role-play RIM co-CEOs Mike Lazaridis and Jim Balsillie's decisions at each turn.
What's visible: Research in Motion built BlackBerry from a niche pager maker into the smartphone market leader — 40% US market share by 2008, ~60,000 devices sold daily at peak — on push email, enterprise-grade encryption, and efficient hardware. When the iPhone launched in 2007, Lazaridis and Balsillie dismissed the threat publicly while privately recognizing what they were up against: Apple had built, in Lazaridis's words, "a full Mac computer shrunk down to fit in a pocket." Obama's public reluctance to give up his BlackBerry in 2009 is cited as a marker of how entrenched the device still felt even as the ground was shifting. The preview cuts off before RIM's actual collapse — the point Cedric is building toward across the series is that disruption doesn't have one shape: Blockbuster saw Netflix coming and nearly won anyway before a boardroom fight killed it; BlackBerry's leadership understood the iPhone's threat correctly and still couldn't out-execute the paradigm shift with a touchscreen-native platform. Different failure mechanism, same "recognition wasn't the bottleneck" pattern the series keeps surfacing.
Mapping against Ray Data Co
This sharpens the Blockbuster note's read on RDCO's "agent-deployer, not incumbent-disruptor" positioning by adding the other failure mode: it's not just that a correctly-executing strategy can get killed by an unrelated internal decision (Blockbuster/Icahn), it's that correct recognition of a paradigm shift is not sufficient to survive it if the response requires re-architecting the product rather than tuning the existing one. RIM tried to compete on their own terms (physical keyboard, enterprise security, push infrastructure) rather than rebuilding around the new paradigm (touchscreen, app ecosystem) until it was too late. Worth holding against RDCO's own AI-agent bet at L4→L5: the live risk isn't "did we notice agents are the new paradigm" — RDCO clearly has — it's whether the phData cert-escalator and L5 north-star bets are structured to re-architect toward where agent capability is going, versus optimizing the current toolset the way RIM optimized the keyboard.
Related
- [[2026-08-18-commoncog-blockbuster-vs-netflix]] — same "Navigating Disruptive Shifts" sequence; the paired counter-example (incumbent recognized the threat and nearly won, then lost to an unrelated internal failure, vs. this case's recognized-the-threat-and-still-lost-to-execution)
- [[2026-08-06-commoncog-ford-survived-gfc]] — same sequence; the case Cedric lists as the second installment before this one
- [[2026-07-28-commoncog-disruption-calibration-case-method]] — the sequence's launch note and Calibration Case Method framing this case sits inside