Nokia owned four phones in ten worldwide — and had already built the future it lost to. What actually happened?
Easier version: read this lesson at A2/B1 level →
Ten items. Work through the four activities — say your answer out loud before you reveal it.
Three terms: burning platform · ecosystem · complacency. Say the right one, then reveal.
Read each part. After it, there's a quick check (answer from memory first), then one question to discuss.
In 2007 Nokia was not merely the market leader in mobile phones; it practically was the market. Roughly four in every ten handsets sold on earth carried its name. It was Europe's most valuable technology company, Finland's national champion — at its peak it accounted for a remarkable share of the entire country's exports and corporate tax revenue — and it had reached that position by out-engineering everyone: better logistics, better manufacturing, phones that survived being dropped down stairwells and worked for a week on one charge.
And it had seen the future — that is the detail that makes this case worth fifty minutes of anyone's time. Nokia had built internet-connected touchscreen prototypes years before anyone else shipped one. Its research teams had experimented with app stores, mobile internet services and tablet-like devices while its competitors were still selling plastic keypads. The threat that eventually arrived was not a surprise attack; versions of it had been sitting in Nokia's own labs.
In January 2007 Apple — a computer maker with no experience of phones, no relationship with the network operators and no distribution — announced the iPhone. Inside the industry the first reaction was widely dismissive, and not entirely without reason: the device was expensive, fragile by Nokia's standards, poor at actual phone calls, and locked to a single network in one country. Measured by every metric the incumbent used, it was a worse phone. Measured by a metric nobody was yet using, it was not a phone at all — it was a computer that happened to make calls, waiting for its ecosystem to arrive. The App Store followed in 2008. Android, given away free to every other manufacturer, followed within months.
1. What made Nokia's position in 2007 look unassailable?
2. Why is "they never saw it coming" the wrong summary of this case?
1. Roughly 40% global handset share, Europe's most valuable tech company, dominance built on genuine engineering and logistics excellence — and enormous importance to Finland's whole economy.
2. Because Nokia had already built touchscreen internet-phone prototypes and experimented with app stores years earlier. The future arrived first in its own labs; the failure was not one of foresight.
What happened next took place mostly in meeting rooms, which is why it gets argued about to this day. Nokia responded — on paper. Touchscreen devices were commissioned; the Symbian operating system was pushed through revision after revision; services were launched. But Symbian had been designed for a different age, and adapting it for modern touchscreens was slow, expensive and demoralising. Software deadlines slipped by quarters, then by years, while the hardware teams — still world class — waited for code that kept not arriving.
Later academic research, built on interviews with dozens of Nokia insiders, surfaced the more uncomfortable mechanism: fear. Middle managers, the studies reported, were afraid to tell their superiors how bad the software situation really was — afraid for their budgets, their standing, their careers. Reports were softened at each level they passed through. Senior leaders, shown filtered information, set targets the engineers privately knew to be impossible, and the engineers, being asked for the impossible, reported progress that did not exist. Nobody lied, exactly. The organisation as a whole lied, one reasonable-sounding meeting at a time.
Externally, the numbers held up remarkably long — smartphone share stayed high on paper well after 2007, which itself became an argument for calm. In February 2011 the newly arrived chief executive, Stephen Elop, recruited from Microsoft, circulated a memo that leaked within days and became one of the most famous internal documents in business history. He compared the company to a man standing on a burning oil platform in the North Sea: staying meant certain death, so he had to jump into freezing, uncertain water. Nokia, Elop wrote, was standing on a burning platform — and its response would be to abandon its own software and bet the company's future on Microsoft's untested Windows Phone.
1. What mechanism did the later research identify inside the company, and how did it work?
2. What did the burning platform memo announce, and why was the choice so radical?
1. A culture of fear that filtered information: middle managers softened bad news upwards, leaders set impossible targets on the basis of filtered reports, and engineers reported progress that did not exist. No single liar — a lying system.
2. That Nokia would abandon its own operating system entirely and commit to Microsoft's Windows Phone — throwing in its lot with an outside partner whose platform had almost no market share, rather than fixing or replacing its own software.
The jump did not save the handset business. Announcing the death of your current platform while its replacement is a year away is now taught as a textbook error — sales of the old devices collapsed immediately, while the new ones did not yet exist. Windows Phone devices, when they came, were praised by reviewers and largely ignored by buyers; the ecosystem war was already a two-horse race, and developers would not build for a distant third. In 2013 Nokia sold its entire devices business to Microsoft for around five and a half billion euros — a fraction of the value of the company at its peak. Barely two years later, Microsoft wrote essentially the whole acquisition off and retreated from phones altogether. The brand that had defined the mobile phone vanished from the product it invented.
And yet the case has a second ending that the obituaries usually skip. Nokia itself — the corporation, not the phone — survived. Freed from the handset war, it doubled down on its network-equipment business, bought Alcatel-Lucent, and today sells the infrastructure that mobile networks run on, profitably, in quiet competition with Ericsson and Huawei. Finland, whose economy the collapse was supposed to devastate, absorbed the shock: thousands of released Nokia engineers seeded a start-up scene that produced, among much else, a games company that made Angry Birds and an entire generation of founders. The company lost the future it had invented. The people and the country, on the whole, did not.
Which leaves the question the case never stops asking. Nokia had the technology first, the money, the brand, the distribution and the best engineers of their generation — and lost. Was it lost in the labs, in the operating system, in the Microsoft decision, or years earlier, in a thousand meetings where nobody wanted to be the one holding the bad number? Every explanation implies a different lesson, and boards have been drawing the convenient one for fifteen years.
1. Why is announcing a platform's end before its replacement ships considered a textbook error, and what happened here?
2. What are the two endings of this case?
1. Because customers immediately stop buying the platform you have declared dead, while the replacement cannot yet be bought. Old-device sales collapsed a year before Windows Phones arrived — and those never gained ecosystem traction.
2. The handset business died — sold to Microsoft in 2013 and written off within two years. But the corporation survived as a profitable network-equipment company, and the released talent seeded Finland's start-up scene.
Every post-mortem runs on two families of modal verbs: what we conclude about the past (they must have known) and what was possible but didn't happen (they could have moved earlier). Confuse them and your analysis says something you don't mean.
Complete each sentence with must have, might have or can't have + the verb in brackets.
1. The engineers (know) the deadlines were impossible — they were the ones writing the code.
2. The board (see) the raw numbers; everything reaching them had passed through three filters.
3. Some senior managers (suspect) the truth — a few later said as much — but the record is unclear.
1. must have known (only one conclusion available)
2. can't have seen (the filtering rules it out)
3. might have suspected (one possibility, evidence mixed)
Rewrite each idea with the modal indicated. Write only the missing words.
1. Adopting Android was possible; they didn't do it. → They Android. (could)
2. In my judgement, keeping quiet until the new phones shipped was the right course. → They quiet until the new phones shipped. (should)
3. Declaring the platform dead so early was unnecessary as well as damaging. → They the platform dead so early. (needn't)
1. could have adopted 2. should have kept / should have stayed 3. needn't have declared
Complete the analysis with the modal forms the meaning requires, then read the whole paragraph aloud.
The leadership (see) the iPhone launch — everyone in the industry did — and they (understand, negative: ruled out) what the ecosystem would mean, or they would never have relied on Symbian for three more years. They (replace, possible-but-didn't) the operating system as early as 2008, and doing so (change) the whole race. Reasonable people still disagree on the Microsoft decision: it (be, one possibility) the least bad option by 2011. But on one point the record is hard to argue with: they (announce, judgement: wrong course) the old platform's death while its successor was still a year away.
must have seen · can't have understood · could have replaced · would have changed · might have been · shouldn't have announced
Six modals, three degrees of certainty, two judgements — that is the full instrument panel of a post-mortem.
Take these into the Speak tab — you'll deliver a post-mortem, and then defend a decision of your own against one.
A note on the figures: market shares and valuations here are rounded, and some of the internal detail rests on later interview-based research rather than contemporaneous records — which is itself worth remembering when you read any post-mortem.
All of it out loud, against the clock. Keep deduction and judgement separate — that separation is what makes a post-mortem sound senior rather than smug.
Present the case to a board that has never heard it, as background to a technology decision of your own. Structure it: the dominance of 2007 → the future already in the labs → the launch everyone dismissed → the quiet years and the filtered truth → the burning platform memo → the jump, the sale, the write-off → the second ending.
Finish with the one lesson you take. Use at least five key terms (incumbent, disruption, ecosystem, filter, complacency, burning platform, cannibalise, playing catch-up, wake-up call, throw in its lot with) and at least three past modals.
You are the chair of a dominant company in your own industry, at your annual general meeting. A shareholder stands up: "Nokia had forty per cent share and the best engineers in the world, and it was gone in six years. Convince me we are not Nokia."
Answer properly: name the honest parallels before dismissing the lazy ones, state what you measure differently, and close on commitment, not comfort. Then compress it to ninety seconds.
Chair a post-mortem on a decision that went wrong — keeping deduction (what the evidence shows) rigorously separate from judgement (what should have been done).
Prefer not to use your own organisation? Take one of these: