Tech Companies & Strategy — Failure Stories
The Smartest People in the Room Built the Wrong Room
Nokia's engineers had a working touchscreen smartphone in 2004 — four years before the iPhone launched — and the company still collapsed because of it.
The Idea
There is a particular kind of corporate failure that is far more instructive than simple incompetence: the failure of a company that saw the future clearly, built the technology correctly, and still managed to destroy itself. Nokia's fall is the canonical example, but the mechanism behind it recurs so reliably across tech history that it deserves its own name. Call it capability trap — when an organisation's existing strengths become the very reason it cannot change course. Nokia in the early 2000s was not asleep. Internal teams had prototyped touchscreen devices, app ecosystems, and mobile internet browsers. Researchers understood where the market was heading. What they lacked was not vision but permission — the organisational courage to cannibalise a product line that was generating extraordinary profits and global market share. Every incentive in the company pointed toward protecting the present. Bonuses, promotions, internal status — all tied to the hardware business that was working. This is what makes capability trap so dangerous: it is invisible from the inside. The metrics look healthy. The engineers are talented. The strategy documents say the right things. But somewhere between insight and execution, the institution's immune system activates and neutralises the threat. Not through malice, but through the accumulated weight of existing commitments — to suppliers, to shareholders, to the identity of the business itself. The company does not fail to see the future. It fails to become it.
In the World
The clearest window into what happened at Nokia comes from a study published in 2010 by researchers Quy Huy and Timo Vuori, who interviewed dozens of Nokia's middle and senior managers as the company unravelled. What they found was not strategic blindness but something more unsettling: pervasive fear. Middle managers, aware that touchscreen smartphones were the future, were afraid to surface bad news to a leadership that had built its identity around Nokia's dominance. Senior leaders, in turn, were afraid to show uncertainty to their boards and markets. The result was a kind of institutional performance — everyone acting more confident than they felt, decisions made on the basis of what was politically safe rather than what was technically real. One telling detail: when internal teams demonstrated the touchscreen prototypes and flagged that the underlying Symbian operating system could not elegantly support the interface they were building, the response from above was not to greenlight a new OS — it was to make the existing one work well enough. The technical debt was papered over. The window closed. By 2007, when Steve Jobs pulled an iPhone from his pocket on stage in San Francisco, Nokia had better hardware supply chains, more handsets in more markets, and more carrier relationships than Apple could have dreamed of. None of it mattered. Within five years, Nokia's mobile division was sold to Microsoft for a fraction of its peak value. The room they had built was magnificent. It just faced the wrong direction.
Why It Matters
Most lessons drawn from Nokia get reduced to 'innovate or die' — which is too blunt to be useful. The more precise insight is about the relationship between success and rigidity. The more thoroughly a company has optimised for one reality, the more structurally resistant it becomes to a different one, even when the people inside it can see what is coming. This applies well beyond tech. Any organisation — a media company, a hospital system, a university — can fall into capability trap. And on an individual level, the same logic holds: the skills, habits, and identities that made you effective in one context can become anchors in another. Recognising when you are in a version of Nokia's position — competent, successful, and quietly too committed to the present — is genuinely difficult, because the warning signs look a lot like stability. The question worth sitting with is not 'are we innovating?' but 'what are we afraid to honestly say out loud?' At Nokia, the problem was not the technology. It was the silence.
A Question to Ponder
What is something you can see clearly needs to change — in your work, your team, or your own habits — that you have been quietly unwilling to say out loud, and why?
Get a new one of these every morning.
Start learning with Thinkable