Memos Internal memo 8 February 2011

The “Burning Platform” Memo

Stephen Elop, CEO, Nokia

You have just become chief executive of the world’s largest phone maker, and it is losing the smartphone market on every front. Do you fix your own platform, adopt a rival’s, or join a competitor’s ecosystem?

The choice

Options on the table

  1. Push MeeGo to market and build Nokia’s own third ecosystem

    For Full control of the platform and a chance to differentiate.

    Against MeeGo was late, had few developers, and was years behind iOS and Android in apps and services.

  2. Adopt Android, like Samsung, HTC and others

    For Instant access to the fastest-growing ecosystem, using Nokia’s manufacturing scale and brand.

    Against Nokia would compete with many manufacturers on a platform Google controlled, with little differentiation.

  3. Keep investing in Symbian

    For No disruption, and an existing base of customers and developers.

    Against Symbian was losing to iOS and Android, and developers found it difficult to work with.

  4. Partner with Microsoft and make Windows Phone Nokia’s primary platform Chosen

    For Nokia would be Microsoft’s lead partner, with financial support and differentiation from Android makers.

    Against Windows Phone had the smallest ecosystem of the three, leaving Nokia dependent on a partner with its own app problem.

The situation

For more than a decade Nokia was the largest phone maker in the world. Its Symbian operating system ran most of the smartphones sold before the iPhone, and its feature phones dominated emerging markets. By 2010 the position was collapsing. The iPhone had redefined what a smartphone was, Android was being adopted by manufacturers across the industry, and Nokia’s own next-generation platform, MeeGo, was late.

In September 2010 Nokia appointed Stephen Elop, previously head of Microsoft’s business division, as its first chief executive from outside Finland. Within five months he had to decide how Nokia would compete.

What the memo argues

The memo opens with a story. A man working on an oil platform in the North Sea wakes to find it on fire. Surrounded by flames, with the sea far below, he has seconds to choose. “He decided to jump.” The point is that the man jumped because staying meant certain death, and he survived. Elop draws the comparison directly: “We too, are standing on a ‘burning platform,’ and we must decide how we are going to change our behaviour.”

He then describes the fire with unusual candour for a chief executive. On Apple: “The first iPhone shipped in 2007, and we still don’t have a product that is close to their experience.” On Google: “Android came on the scene just over 2 years ago, and this week they took our leadership position in smartphone volumes.” On Nokia’s own platforms, he writes that Symbian “is proving to be an increasingly difficult environment” for developers, and that “we thought MeeGo would be a platform for winning high-end smartphones,” a hope that had not been realised. He adds pressure from low-cost Chinese manufacturers at the other end of the market: “we have more than one explosion.”

Then comes the strategic claim that frames everything: “The battle of devices has now become a war of ecosystems.” Competitors were winning by building or joining ecosystems of apps, services and developers, and Nokia was not.

He does not spare the company: “We fell behind, we missed big trends, and we lost time,” and, most memorably, “We poured gasoline on our own burning platform.” The memo ends with a call to action: “Together, we can choose to define our future.”

The decision it carried

The memo does not name the decision, but it prepared employees for it. On 11 February 2011, three days later, Nokia announced a partnership with Microsoft: Windows Phone would become Nokia’s primary smartphone platform, Symbian would be phased out, and MeeGo would be reduced to a research effort.

The alternatives were the subject of intense debate at the time. Nokia could have pushed MeeGo to market and tried to build a third ecosystem of its own. It could have adopted Android, as Samsung, HTC and others had, using its manufacturing scale and brand to compete within the largest ecosystem. Or it could choose Windows Phone, where Microsoft offered support and Nokia would be the leading partner rather than one of many.

What happened

Nokia’s smartphone sales fell sharply as customers and retailers, told that Symbian was finished, stopped buying Symbian phones before the Windows Phone models were ready. The Lumia phones that followed were well reviewed but struggled to attract the apps that iPhone and Android users expected, because developers prioritised the two larger platforms. Windows Phone never gained a large share of the market.

In September 2013 Microsoft announced it would buy Nokia’s devices and services business; the deal closed in April 2014, and Elop returned to Microsoft. In July 2015 Microsoft announced an impairment charge of about $7.6 billion related to the acquisition, along with thousands of job cuts, effectively writing off the purchase. Nokia itself survived as a telecommunications networks company.

How to read it as a product manager

The memo is studied for good reasons and for bad ones.

Its candour is valuable. Many companies in decline describe their position in euphemisms. Elop named competitors, admitted specific failures and said plainly that the existing strategy was not working. That honesty is a precondition for change.

Its central insight was correct. Smartphones were becoming ecosystems, and a phone maker without strong apps and developer support could not win on hardware alone.

Its weaknesses are just as instructive. First, it was written as if its only audience were employees. Any memo to tens of thousands of people will leak, and this one told customers and retailers that Nokia’s current phones had no future. Second, the conclusion that Nokia had to “jump” did not determine where to jump. The insight about ecosystems arguably pointed toward the largest ecosystem, Android, or toward building one’s own; joining the smallest of the three made Nokia dependent on a partner that faced the same developer problem. Third, by declaring the old platform dead before the new one shipped, the strategy removed revenue during the transition, a classic mistake known in the industry as the Osborne effect.

What is contested

Supporters of the Windows Phone decision argue that adopting Android would have turned Nokia into one manufacturer among many competing on price against Samsung, and that Microsoft offered differentiation and money Google would not. Critics argue that Android would have preserved Nokia’s volume while it found its place. Some in Finland at the time suspected Elop’s Microsoft background influenced the choice; Elop and Nokia’s board said the decision followed a full evaluation. What happened is clear; what would have happened under the alternatives is not.

The decision, examined closely

What triggered it

By early 2011 every measure of Nokia’s smartphone business was moving the wrong way. Android had just passed Nokia in smartphone volumes, as the memo itself notes, and Apple dominated the high end. Nokia had a scheduled strategy briefing on 11 February. The memo was written to prepare employees for a radical announcement three days later.

The constraints

Nokia had enormous manufacturing scale and distribution, but its software was behind, and software had become the basis of competition. Any choice would take years to deliver products, during which Nokia would have to keep selling the phones it already had. That made the timing and communication of the decision as important as the decision itself.

What the author was optimising for

The memo optimises for urgency. Its story, its candour and its striking language are designed to make employees accept that the status quo was not an option. What it does not do is explain why the particular destination was the right one. The “war of ecosystems” framing tells readers that Nokia needed an ecosystem; it does not establish that Windows Phone was the best one to join.

Second-order effects

The memo leaked within hours, and its message reached customers, retailers and operators: Nokia’s current phones had no future. Sales of Symbian devices fell faster than planned, reducing revenue before the replacement arrived. Developers, seeing a small and uncertain Windows Phone market, did not rush to build apps for it, which weakened the very ecosystem Nokia had bet on.

The counterfactual

The most discussed alternative is Android. Supporters argue Nokia’s scale and brand would have made it a leading Android manufacturer; critics argue it would have been squeezed by Samsung and low-cost rivals and become a commodity supplier. Either way, the case shows that a strategic insight (devices had become ecosystems) can be correct while the specific bet that follows from it fails.

Sources and limitations

Quotations were verified against Engadget’s publication of the leaked memo, which Engadget later confirmed with multiple sources; Nokia declined to comment on it at the time. The account of later events relies on news reporting of company announcements, including Microsoft’s 2015 write-down. Reported purchase prices for the Nokia devices business differ between sources and are not given here. The analysis of what the strategy got wrong is the author’s interpretation, based on outcomes and on arguments made at the time.

Before and after

Timeline

  1. 2007 Apple launches the iPhone.
  2. 2008 The first Android phone goes on sale.
  3. September 2010 Stephen Elop becomes Nokia’s chief executive.
  4. 8 February 2011 The “burning platform” memo is posted internally and leaks.
  5. 11 February 2011 Nokia announces its partnership with Microsoft; Symbian is to be phased out.
  6. October 2011 Nokia announces its first Lumia Windows Phone devices.
  7. September 2013 Microsoft announces it will buy Nokia’s devices and services business.
  8. April 2014 The acquisition closes, and Elop returns to Microsoft.
  9. July 2015 Microsoft announces a write-down of about $7.6 billion related to the acquisition, and thousands of job cuts.
  10. 2016 A new company, HMD, licenses the Nokia brand for Android phones.

For people who build products

Lessons

  1. A memo that tells everyone the current product is doomed will reach customers and retailers, not only employees; plan for that audience.
  2. “The battle of devices has become a war of ecosystems” was the right insight; joining the third-largest ecosystem did not follow from it.
  3. Announcing the end of a product before its replacement ships can cut revenue at the moment you most need it.
  4. Honesty about failure is necessary for change, but it is not a plan.

Take it to your team

Questions to ask

  • If this internal document leaked tomorrow, what would customers and partners conclude?
  • Are we choosing a partner because it is strong where we are weak, or because it is available?
  • What revenue are we risking between announcing a change and delivering it?

Read the original

Sources and rights

Where it came from. Posted to an internal Nokia employee system in February 2011 and leaked to the press; Engadget reported multiple sources confirming it was genuine.

Rights. The memo belongs to Nokia. This page quotes short passages for commentary and criticism and links to the reporting that published it.

How to cite

Shrikant Kumar. “The “Burning Platform” Memo: annotated.” Annotated memo, Telos. https://shrikantk.com/memos/burning-platform/

↑ ↓ to move↵ to open⌘K to toggle