In 2004, a marketing manager at Nokia was shown a prototype. It was a phone with a big screen, no keypad, and a working internet connection. You touched the glass and things happened.
Three years before the iPhone existed.
His name was Ari Hakkarainen, and years later he told the New York Times what happened to it. Nobody knew what a touchscreen was worth yet. The device would be expensive to make. There was risk. So, in his words, management did the usual thing. They killed it.
That same year Nokia also turned down a design for an online app store. Two years before that, in 2002, it rejected a plan for a 3D interface in its software. One former engineer, Juhani Risku, said his team put forward five hundred proposals to improve Nokia's operating system. Not one of them made it through.
Sitting on top of the world
You have to remember how big Nokia was. In 2007 it held something close to half of the entire global smartphone market. If you picked up a phone anywhere on earth, there was a very good chance it said Nokia on it. The 1100 is still one of the best-selling electronic devices ever made.
Then in January 2007, Apple showed the iPhone. Nokia's CEO at the time, Olli-Pekka Kallasvuo, said publicly that Nokia had nothing to worry about.
And on paper, he was right. The first iPhone had no app store, no 3G, no copy-paste, and a battery you could not remove. Nokia's engineers pulled it apart and found plenty to laugh at.
In 2008 Google released Android and gave it away free to any manufacturer who wanted it. Now Nokia was fighting on two fronts: a premium enemy above and a free enemy below.
The memo
In September 2010, Nokia hired Stephen Elop from Microsoft — the first non-Finn ever to run the company.
On 8 February 2011, an internal memo of his leaked to the world.
In it he told a story about a man standing on a burning oil platform in the North Sea. The man has seconds to decide. He can stay on the burning rig, or jump thirty metres into freezing black water. He jumps, because staying is certain death and jumping is only probably death.
That, Elop wrote, was Nokia. The platform was on fire. Standing still was not an option.
It was a brilliant piece of writing. It was also, many people now think, the single most expensive memo ever written.
The Android decision
Three days later Nokia announced its jump: Windows Phone, in partnership with Microsoft.
So yes — Nokia said no to Android. Elop confirmed it openly at a press conference in Barcelona. Both Google and Microsoft had come courting in the weeks before the decision. He chose Microsoft.
His reasoning was this. If Nokia went Android, it would be one hardware maker among many, fighting Samsung and HTC on price, with no way to stand out. With Windows Phone it could be the favoured partner and build a third ecosystem next to Apple and Google.
He also said a swing to Android would have tilted the industry into a duopoly, and Nokia wanted to be a challenger instead.
You can argue with that decision, and most people do. But hold it for a second, because it is not the part that killed the company.
The thing that actually did the damage
Elop declared Symbian dead in February 2011.
The first Windows Phone from Nokia, the Lumia 800, did not go on sale until November 2011.
Nine months.
For nine months Nokia had told the entire world that the phones sitting in every shop window were finished — and had nothing to replace them with. No customer wants to buy a phone whose maker has just announced it is a dead end. No shop wants to stock it. No developer wants to build apps for it.
Sales did not decline. They collapsed.
Nokia's own board saw it that way too. The memo was treated internally as a serious error of judgement, and the chairman, Jorma Ollila, gave Elop stinging feedback over it.
The lesson in one line
Never announce the death of the thing that feeds you before the thing that will replace it is ready to feed you.
You can build the new thing quietly. You can even build it badly at first. But the day you tell everyone the old thing is over, the old thing is over — whether or not the new one has arrived.
The saddest phone ever made
There is a footnote to this story that is almost too perfect.
In 2011, after the Microsoft announcement, Nokia went ahead and released the N9 — a phone running its own software, MeeGo. One piece of polycarbonate, no home button, everything done by swiping the screen. The reviews were almost uniformly positive. Reviewers said it was the phone Nokia had needed to make.
It was launched by a company that had already publicly killed its own operating system. No developer was going to build for a platform with a death certificate. It sold what it sold and then it was over.
Nokia had the good idea and the good product. It just no longer had permission from itself to believe in them.
How it ended, and how it didn't
In September 2013, Microsoft bought Nokia's entire phone business for €5.44 billion. Elop went back to Microsoft. The company that had made most of the world's mobile phones was, within a few years, out of the phone business completely.
But here is the part people forget, and it matters.
Nokia did not die. It sold the part that was burning, kept the part that worked — the network equipment business, the thing that quietly builds the mobile infrastructure of whole countries — and is still a real company today. The Nokia name even came back on phones years later, under licence, running Android.
They got there eventually. They just paid about a decade and a hundred thousand jobs for the delay.
What you can take from this
1. Your problem is rarely a lack of ideas
Five hundred proposals. Nobody at Nokia was short of ideas. They were short of a way to say yes to one. If you have been "thinking about starting something" for two years, you do not need a better idea. You need to pick the mediocre one you already have and start it badly.
2. Do not burn the boat until the new one floats
This is the single most useful thing in the whole story. People hear "burn the boats" as motivation, and it is terrible advice for almost everyone.
The personal version of Nokia's nine-month gap is quitting your job the week you register a domain name. Or telling everyone you are done with your trade before the new work pays a single bill. Keep the income. Build the new thing in the evenings, at the weekend, badly, for as long as it takes. Announce nothing. Switch when the numbers switch, not before.
3. Being on top makes you deaf
Nokia's engineers were not wrong about the first iPhone. It genuinely was worse in most measurable ways. That is exactly why they missed it. When you are the best at something, every new threat arrives looking incomplete, because new things always do.
4. Being different is not automatically better
Elop wanted to stand out rather than be one of the crowd. It sounds wise. But there is a version of standing out that just means standing alone in a place customers are not. Ask which you are doing: being different where people already are, or being different somewhere empty.
The honest part
We do not actually know that Android would have saved Nokia. That is the comfortable version of the story and it deserves some suspicion.
Plenty of companies did choose Android and still lost badly — HTC, LG, Sony and others made Android phones and made almost no money doing it while Samsung took the profits. Elop's fear of becoming a commodity was not stupid. It may have been correct.
And Nokia's decline started years before Elop arrived, in those meeting rooms in 2002 and 2004 where the good ideas were quietly killed. Blaming one memo lets everyone who came before it off the hook.
The clearest lesson is not "they picked the wrong operating system." It is that they spent eight years not deciding, and then made the biggest decision of the company's life in a hurry, and announced it before they were ready.
Two companies, one ending
Kodak invented the future, looked at it, and said no.
Nokia invented the future, looked at it, said no, then panicked, said yes to something else, and burned the present down before the future arrived.
Opposite mistakes. Same result.
Which is the real point. There is no safe option. Refusing to change ends you slowly; changing in a panic ends you quickly. What works is the unglamorous middle: keep what pays, build the new thing quietly beside it, and move across only when it can carry your weight.