The Innovators Studio with Phil McKinney
Phil McKinney
Podcast
Episodes
Listen, download, subscribe
The $1.2 Billion Innovation Disaster: 5 Decision Mistakes That Kill Breakthrough Technology (HP WebOS Case Study)
In 2011, HP killed a $1.2 billion innovation in just 49 days. I was the Chief Technology Officer who recommended buying it. What happened next reveals why smart people consistently destroy breakthrough technology—and the systematic framework you need to avoid making the same mistake. HP had just spent $1.2 billion acquiring Palm to get WebOS—one of the most advanced mobile operating systems ever created. It had true multitasking when iOS and Android couldn't handle it, an elegant interface design, and breakthrough platform technology. I led the technical due diligence and recommended the acquisition because I believed we were buying the future of mobile computing. We launched it on the HP TouchPad tablet. Then, the CEO killed it just 49 days after launch. Here's a question that should keep every innovation leader awake at night: How do you destroy breakthrough technology worth over a billion dollars in less than two months? The answer isn't what you think. It's not about bad technology, poor market timing, or insufficient resources. It's about systematic thinking errors that intelligent people make when evaluating innovation under pressure. And these same patterns are happening in companies everywhere, right now. I'm going to show you exactly how this happens, why your company is vulnerable to the same mistakes, and give you a proven framework to prevent these disasters before they destroy your next breakthrough innovation. On my Studio Notes on Substack, I share the personal story of watching this unfold while recovering from surgery. In this episode, I want to focus on the systematic patterns that caused this disaster and the decision framework that can prevent it. Here's my promise: by the end of this episode, you'll understand the five thinking errors that consistently destroy innovation value, you'll have a complete decision framework to avoid these traps, and you'll know exactly how to apply this to your current innovation decisions. Because here's what this disaster taught me: intelligence doesn't predict decision quality. Systematic thinking frameworks do. The Pattern That Destroys Billion-Dollar Innovations Let me start with the fundamental problem that makes these disasters predictable. When the HP Board hired Leo Apotheker as CEO, they created what I call a "cognitive mismatch," and it reveals why smart people make terrible innovation decisions. Apotheker came from SAP, where he'd run a $15 billion software company. HP was a $125 billion technology company with breakthrough mobile platform technology. The board put someone whose largest organizational experience was half the size of HP's smallest division in charge of evaluating platform innovations he'd never encountered before. But here's the crucial insight: the problem wasn't his experience level. The problem was how his professional background created mental blind spots that made him literally unable to see WebOS as an opportunity. Here's what's dangerous: Apotheker couldn't see WebOS as valuable because his entire career taught him that software companies don't do hardware. His brain was wired to see hardware as a distraction, not an advantage. To him, WebOS represented exactly the kind of hardware business he wanted to eliminate. Your expertise becomes your blind spot. You literally can't see opportunities outside your professional comfort zone. And this is the first critical principle: Your job background creates mental filters that determine what opportunities you can even see. And this pattern is happening in your company right now. Your finance team evaluates platform investments using metrics designed for traditional products. Your marketing team rejects concepts they can't explain with existing frameworks. Your engineers dismiss breakthrough ideas that don't fit current technical roadmaps. The pattern is always identical: intelligent people using the wrong thinking frameworks to evaluate breakthrough technology. Let me show you exactly how this destroys innovation value. The Five Systematic Thinking Errors That Kill Innovation WebOS died because of five predictable cognitive errors that occur when smart people evaluate breakthrough technology under pressure. These aren't unique to HP—I've seen identical patterns destroy innovation value across multiple industries. Error #1: Solving the Wrong Problem The most dangerous mistake happens before you evaluate any options: framing the wrong decision question. Apotheker was asking "How do I transform HP into a software company?" when the strategic question was "How do we build competitive advantage in mobile computing platforms?" When you optimize solutions for the wrong problem, you get excellent answers that destroy strategic value. The Warning Sign: Your team jumps straight to evaluating options without questioning whether you're solving the right challenge. Error #2: Identity-Driven Decision Making Your professional background creates systematic blind spots about breakthrough opportunities. Software executives see software solutions. Hardware leaders focus on hardware opportunities. Financial experts optimize for traditional metrics. This cognitive filtering happens automatically and distorts how you evaluate platform technologies that don't fit conventional categories. The Warning Sign: Your evaluation team all have similar backgrounds and reach the same conclusions about breakthrough technology. Error #3: Tunnel Vision Under Pressure When executives become obsessed with major initiatives, everything else feels like a distraction. Apotheker became obsessed with acquiring Autonomy, a software company that fit his transformation vision. This tunnel vision made everything else—including breakthrough mobile technology—feel like a distraction from his primary goal. The Warning Sign: Leadership dismisses promising innovations because they don't support the current primary initiative. Error #4: Timeline Compression Under Stress Platform technologies require different evaluation timeframes than traditional products. Forty-nine days isn't enough time to build developer ecosystems, establish retail partnerships, or demonstrate platform traction. But pressure to show decisive leadership compressed HP's decision timeline artificially, creating the illusion of strong leadership while increasing the probability of strategic errors. The Warning Sign: Your team is evaluating breakthrough technology using the same timelines as conventional product launches. Error #5: Wrong Evidence Framework Innovation decisions require fundamentally different success metrics than traditional business evaluation. HP focused on TouchPad sales numbers instead of developer adoption rates, user engagement patterns, or platform differentiation sustainability. They used product metrics to evaluate platform potential, which guaranteed they would see failure instead of recognizing early-stage ecosystem development. The Warning Sign: You're applying traditional business metrics to evaluate breakthrough technology investments. Here's what makes these errors so dangerous: they're invisible to the people making them. Smart teams use these flawed frameworks and feel confident they're making data-driven decisions while systematically destroying innovation value. But these patterns are preventable. After analyzing hundreds of similar disasters, I developed a systematic framework specifically designed to avoid these thinking traps. The DECIDE Framework: Your Innovation Decision Protection System The DECIDE framework addresses each cognitive vulnerability that consistently traps intelligent leaders in innovation contexts. Let me show you exactly how it works and why it would have saved WebOS. D - Define the Real Decision Most innovation failures begin with teams optimizing excellent solutions for poorly defined problems. The Tool: Reframe your decision question three different ways. If all three point to the same choice, you're probably asking the right question. If they point to different choices, you need to determine which frame captures the real strategic challenge. Examples of Different Frames: Financial Frame: "How do we minimize losses on this investment?" Strategic Frame: "How do we build long-term competitive advantage?" Market Frame: "How do we capture emerging opportunities?" Competitive Frame: "How do we position against industry leaders?" Customer Frame: "How do we create unique value for users?" HP's Application: Original Frame: "Should we continue investing in TouchPad given poor sales?" Strategic Reframe: "How do we build a sustainable mobile platform business?" Competitive Reframe: "What's our path to competing with Apple and Google in mobile?" What This Reveals: The reframes show TouchPad was one product in a larger platform opportunity that deserved different evaluation criteria entirely. E - Examine Your Thinking Process Your professional background creates invisible filters that can systematically distort how you interpret breakthrough opportunities. The Tool: If you hired someone with completely different expertise to make this decision, what would they choose? When the gap is huge, you need outside perspectives with different cognitive frameworks. HP's Gap: Enterprise software CEO versus consumer platform strategy requirements. They needed mobile platform thinking, not enterprise software optimization, but never brought that expertise into the decision process. C - Challenge Your Assumptions The most dangerous assumptions feel like established facts and shape your entire analysis without being examined. The Tool: What would have to be true for your least favorite option to actually be the right choice? This forces you to consider alternative interpretations of the same evidence. HP's Assumptions: Platform businesses need immediate profitability, mobile computing won't dominate, differentiated operating systems can't compete with Apple and Google. All of
The Innovators Studio with Phil McKinney RSS Feed
