Case Study: BlackBerry, a Dominant Product Disrupted by a Platform

BlackBerry didn't lose on hardware, and it didn't really lose on the keyboard-versus-touchscreen call everyone remembers. At its peak it had the strongest product position in the industry, with a subscriber base still climbing toward roughly 80 million in 2011 and 2012. It lost because it treated the iPhone as a competing product to out-feature, when the iPhone was the leading edge of a platform that continues, to this day, to redefine the scope of what a smartphone can enable. BlackBerry kept winning the product contest it understood while losing the platform contest it never really entered.

That distinction is the whole story, so it's worth being precise about it. A platform in the sense that matters here isn't just a good product with an app store bolted on. It's what we call a PIVA, a Platform of Increasing Value of Adoption: a system whose value compounds as more people adopt it and more third parties build on it, so that each side creates value and opportunity for the other. A great product can be copied or leapfrogged. A platform that has reached that compounding state is far harder to dislodge, because you aren't just competing against a company, you're competing against the whole ecosystem that has already built on it.

The world BlackBerry was winning in

To see why the danger was invisible, you have to remember the world of 2006. Mobile data was slow and metered. The web and its software were still overwhelmingly PC-centric. Smartphones were mostly an enterprise tool, and BlackBerry owned that use: secure, reliable corporate email, managed through IT, sold hand in glove with the wireless carriers. And the carriers, not the handset makers, controlled the mobile experience. Software mostly came pre-installed, "apps" were a handful of Java programs, and where a market for mobile content existed at all, it ran through carrier walled gardens that took forty to fifty percent of the revenue and decided what got distributed.

In that world, BlackBerry's strategy wasn't just sound, it looked dominant and correct. Its product fit the constraints of the era precisely, its carrier relationships were an asset rather than a liability, and its numbers were excellent. Everything that made BlackBerry strong was measured at the product level, and at the product level it was winning.

A differentiated product that expanded the system of use

The iPhone did not win because it was a straightforwardly better phone. On the things BlackBerry optimized for, like a physical keyboard, battery life, secure enterprise email, it was arguably worse at first. What it was, was differentiated in a way that mattered: a capacitive touch screen, a much larger display, a full web browser running something close to the real desktop web rather than a stripped-down mobile version, and websites and apps that users could pin to their home screen.

Those differences changed what a smartphone could be used for. A device that can render the actual web and present a large, direct-manipulation canvas can do a vast range of things a keyboard-and-email device could not, so the scope of the system of use expanded, from secure messaging to the open web and, soon, to rich third-party software. That is the first of the critical elements of a platform strategy, an evolving system of use, and here it was being enlarged from the product layer up.

Critical mass of adoption is another critical prerequisite for a successful platform, and Apple didn't really start from zero. The iPhone was grounded in iTunes, which already had an enormous installed base and a genuinely high-value, high-adoption use case in music, shared with the iPod. That gave the iPhone an inherited store of real and perceived critical mass and a running relationship with media and content partners, so it entered the market with ecosystem momentum a standalone new device would have had to build from scratch. BlackBerry, meanwhile, kept refining a product optimized for the older, narrower system of use.

The divergence that decided it

Here is the part that turned a product contest into a platform one, and it did not start as a grand plan. Apple initially resisted native third-party apps. At its 2007 developer conference it told developers to build web apps that ran in the iPhone's Safari browser, and the room reportedly answered with a polite golf clap. The trouble was that the mobile web of the time gave developers almost no way to make money: the obvious option was display advertising, which translated badly to a small screen. Web apps were a real capability, but not a business a developer could invest in.

So Apple shipped a software development kit in March 2008 and opened the App Store that July, and the model diverged from BlackBerry's for good. The App Store gave developers native capabilities and, more importantly, a low-friction way to actually earn: a simple 70-30 split that Apple, at the time, framed as barely a business at all. Steve Jobs said in 2008 that Apple didn't intend to make money on the store, that the 30 percent just covered the cost of running it. Whether or not that lasted, the early posture was unmistakably complementor-friendly: keep the platform's take low, let the developers get paid, and let their investment make the platform more valuable.

Set that against the carrier walled gardens BlackBerry lived inside. Those took forty to fifty percent, and they curated what got distributed based on the value BlackBerry and the carriers could capture, not the value created for the people adopting the phones or the developers building for them. One model was designed to grow a two-sided ecosystem; the other was designed to extract from a captive one. Apple compounded the gap with platform-centric marketing that sold the ecosystem itself, the idea that whatever you wanted to do, there was an app for it, while BlackBerry marketed a product to an enterprise buyer. Complementor economics and value capture, the third and fourth critical elements of a successful platform strategy, both broke in Apple's favor, and the developer ecosystem BlackBerry never built became the moat it could not cross.

It is worth naming that a healthy value-capture posture is dynamic and needs constant monitoring for balanced returns. Apple's low early take was a critical-mass strategy, and as the platform became dominant Apple monetized it far more aggressively, to the point of the Epic v. Apple litigation and the European Union's Digital Markets Act findings against its App Store rules. The early generosity built the flywheel; the later extraction is the fight over who keeps the value once the flywheel is spinning. Both are part of the same platform, and both are lessons.

The signals that stayed green

The reason BlackBerry's leadership did not panic is that the numbers they watched kept going up. Subscribers grew to that ~80 million peak. Enterprise lock-in looked secure, the security reputation was intact, revenue was strong. Every one of those is a product-level signal, and every one of them can keep climbing well into a platform-level defeat, because a large installed base is the momentum of a dominant legacy product: it takes years to erode even after the force that will erode it is already in motion. And it is worth being clear about what that base was and wasn't. BlackBerry's subscribers were a lagging record of past product success, not an asset the company could readily tap to expand its system of use or attract complementors. Apple's iPod and iTunes base could be turned into platform critical mass; BlackBerry's could mostly only be spent down.

The signals that actually mattered were platform signals, and they were flashing, just not on BlackBerry's dashboard. They were showing up for Apple: the relative rate of adoption and, more tellingly, its acceleration; the number of developers building for the platform and how much they were investing; and the mindshare among both users and developers about where the future was. Those are the measures that tell you whether a flywheel is spinning up, and we treat them as the real instrument panel for a platform in our work on managing a platform versus a product. Measuring the wrong layer is exactly how a capable company gets blindsided while its own reports look healthy, which is the deeper version of the accountability problem we take up in how to measure innovation.

The deeper reason it couldn't turn

Even once the threat was undeniable, BlackBerry could not simply decide to become a platform, and the reason is worth calling out because it is the hidden cause underneath the more obvious one. Every organization is built around a particular set of resources, processes, and priorities, its RPPs, and those are tuned to the business it already runs. Apple came to the platform contest with resources and habits already suited to it: years of running macOS and a real third-party developer ecosystem, and a consumer-marketing capability built on the iPod. Its RPPs were, in effect, platform-ready.

BlackBerry's RPPs were not, and worse, they were co-dependent on the carriers'. Its resources, processes, and priorities were built for secure-messaging hardware and for a business model interlocked with carrier subscriber lock-in and revenue extraction, not for cultivating and serving an independent developer ecosystem. Turning toward a platform would have meant working against both its own operating model and its most important partners' at the same time. That is why the pivot was nearly impossible rather than merely late, and it is the same organizational-fit problem, Resources, Processes, and Priorities, that decides most disruptive strategic transformation attempts.

This is the exact inverse of the companion case. Nvidia won the AI platform because it had the organizational fit to fund a compounding platform for years; we tell that side of the story in CUDA, Nvidia's disruptive platform strategy. BlackBerry lost the smartphone platform because it had the organizational fit to run a superb product business and not a platform.

What it teaches

The transferable lesson is not "build an app store" or "add open interfaces to your product." It is that a dominant product position is not a platform position, and a product cannot win against a platform aimed at its market, because it is competing against an entire ecosystem's accumulated investment rather than against a rival's feature list. The signals that measure product health will keep you comfortable right up until the platform layer moves out from under you.

So the discipline is to watch the platform signals as well as the product dashboard, to run the honest disqualifier test before assuming your position is defensible, and to ask the harder question of whether your resources, processes, and priorities could actually enable an ecosystem if the contest moved to that layer. BlackBerry is the cautionary half of a pair, and the caution is specific: by the time a platform shift shows up in your product numbers, the contest is usually already over. Doing that read early, and honestly, is the work our consulting and Growth Forge® Software are built to support.

BRI Associates helps companies grow by drawing on decades of practitioner experience in corporate innovation and new business development — practitioners, not pundits or academics — through direct consulting, training workshops, and Growth Forge® Software, built for the unique requirements of corporate innovation and growth organizations.