Nokia saw the iPhone coming, but couldn’t act on what it knew about itself

On 10 January 2007, the morning after Steve Jobs held up the first iPhone in San Francisco, people inside Nokia met to work out what they had seen.

The slides from that meeting are public now, held in the Nokia Design Archive at Aalto University, which opened to the world in 2025. The executive summary calls the iPhone a serious high-end competitor. Further down, the deck records that the user interface had been a strength for Nokia, that consumer research showed it slipping, and that urgent action was required. Nokia needed to build a touch interface to fight back, it said, and S60 should remain the focus.

Nokia didn’t fail because it couldn’t see what was coming, it saw the fault line the next morning.

Timo Partanen, then Nokia’s director of market and competitor analysis, was in the room. Speaking to IEEE Spectrum in 2026, he described the mood as untroubled. Apple was another competitor with a good product. If it worked, Nokia would do the same.

The numbers agreed with him.

Ten months later, in the first week of November 2007, Nokia’s New York-listed shares reached a high they have never returned to. The company accounted for around a third of the entire market capitalisation of the Helsinki exchange. Gartner would report that Nokia passed 40 per cent of the global handset market in the fourth quarter of 2007, the first time it had crossed that line, after selling 435 million devices across the year.

Interbrand and BusinessWeek had already ranked Nokia as the fifth most valuable brand in the world, worth $33.7 billion. It was the highest-ranked non-American brand on the list.

Nokia’s own results for the year showed net sales of €51.1 billion and operating profit of €8.0 billion. The devices businesses contributed approximately €7.6 billion of that profit. In the fourth quarter alone, Nokia shipped 133.5 million devices at an operating margin of 23.3 per cent. Olli-Pekka Kallasvuo, the chief executive, called the quarter excellent.

Every one of those numbers was true and every one of them was measuring the visible canopy.

Nokia’s own people had correctly identified the fault line in January. The warning didn’t disappear, but neither did it become action proportionate to the threat. It was absorbed into the existing plan: develop touch, keep S60 at the centre, and trust Nokia’s scale and engineering capacity to close the gap.

The company understood what Apple had built, but it didn’t yet comprehend what Nokia itself had become.

The distance between what an organisation knows somewhere inside itself and what it can accept, decide and act upon has no line or representation in the accounts. It carries no recognised liability and attracts no auditor’s note. Yet it can decide the future of the whole enterprise while every reported measure is still improving.

Very few readers of this run a business holding 40 per cent of a global market. The mechanism doesn’t care about size. It works in the same way in a twelve-person engineering company.

Somebody sees something important. The information is softened as it travels, interpreted through what leadership already believes, or acknowledged without accepting the cost of acting upon it. By the time a decision is made, the organisation is responding to a safer version of the truth.

The most careful account of what happened inside Nokia comes from academic research rather than contemporary reporting. Timo Vuori of Aalto University and Quy Huy of INSEAD interviewed 76 people, including senior executives, middle managers, engineers and outside experts. Their study, published in Administrative Science Quarterly in 2016, examined the period from 2005 to 2010.

It begins two years before the applause peaked.

What they describe is shared fear moving in two directions.

Senior managers feared competitors and shareholders. That fear translated into pressure on the people beneath them, but without a full explanation of how serious the external threat had become.

Middle managers feared their superiors and their peers. What they feared was less the loss of their employment than the loss of internal standing: appearing weak, obstructive, disloyal or unable to deliver.

So the bad news softened on its way up.

Engineers who understood the scale of Symbian’s limitations communicated them in ways that protected their position. Deadlines that people privately regarded as unachievable remained in the plans. Comparisons between what Nokia’s software could actually deliver and what senior management believed it could deliver became progressively less reliable.

The result at the top was a picture of Nokia’s technological capacity that was better than the capacity itself. Capital, deadlines and product commitments were allocated to match the picture.

One senior manager told the researchers that he could not say publicly that Symbian was finished because of what that admission would do to Symbian sales.

“You must believe in the gun you are holding,” he said, “because there is nothing else.”

That is the economic trap at the centre of the story.

Nokia had to hold two contradictory truths at once. Symbian was still producing billions of euros in revenue and profit. Symbian was also becoming incapable of securing the company’s future.

The organisation could sell the first truth or act upon the second. It could not easily do both.

Calling the platform structurally compromised would have weakened confidence among customers, operators, developers and investors while Nokia still depended upon it. It would have challenged years of investment, the standing of senior leaders and the influence of a large internal organisation built around Symbian. It would have required Nokia to damage the current profit engine before a replacement was ready.

The issue was therefore larger than whether somebody felt safe enough to speak, because the truth itself carried a cost.

None of that appeared in a quarterly result for a long time. Nokia’s handset volumes continued climbing into 2008. The market share, margins and brand remained formidable. The reckoning ran on a different clock.

Nokia demonstrated a touch interface for S60 on concept devices in October 2007. Its first touchscreen S60 handset, the 5800 XpressMusic, was announced on 2 October 2008 and shipped that November. It had a resistive touchscreen and no multitouch.

Partanen’s account of its development is that it was repeatedly delayed and arrived watered down. Nokia’s first multitouch phone did not appear until 2010.

The company had not ignored the signal. It had translated a change in the basis of competition into a feature-development programme for the platform it already owned.

Apple had made software, interface and the relationship between hardware and software central to the value of the phone. Nokia responded as though touch were an additional capability that could be fitted onto its existing advantage.

The distinction consumed the time.

In the first quarter of 2012, Samsung passed Nokia to become the world’s largest handset manufacturer, shipping 93.5 million devices against Nokia’s 82.7 million. Nokia’s run at number one, which had lasted since 1998, was over.

Standard & Poor’s and Fitch both cut the company’s debt to junk status in the same week.

In September 2013, Nokia agreed to sell substantially all of its Devices & Services business to Microsoft. Microsoft paid €3.79 billion for the operating business and a further €1.65 billion for a ten-year licence to Nokia’s patents: €5.44 billion in total. The transaction completed in April 2014.

Put two of those numbers beside each other.

Nokia’s devices businesses generated around €7.6 billion of operating profit in 2007.

Six years later, substantially all of that operating business, together with the patent licence, was sold for €5.44 billion.

In July 2015, Microsoft announced a $7.6 billion impairment associated with the acquisition, close to what it had paid.

The visible collapse arrived quickly. The organisational conditions behind it had been developing while the visible performance was still exceptional.

Which leaves the question this piece exists to answer.

What could an outsider have seen at the time from the public record, dated on or before Nokia’s peak?

Not the academic study, whose first interviews were not conducted until years later. Not the January presentation, which remained inside Nokia. Not the internal deadlines, softened reports or private assessments of Symbian’s condition.

The honest answer is very little.

Two things were visible.

On 20 June 2007, Nokia announced that it was taking apart the structure of its devices business and rebuilding it as three units from 1 January 2008. Its spokeswoman, Arja Suominen, said it was not a cost-cutting exercise and that the company was seeking greater efficiency. It was reported largely as organisational housekeeping.

On 16 October 2007, at the Symbian Smartphone Show in London, Nokia demonstrated a touch interface for S60 running on concept devices. Anyone with an internet connection could watch the video.

Nine months had passed since the iPhone was unveiled and four months since it had gone on sale. The world’s largest phone manufacturer was demonstrating a prototype response.

The public could see that Nokia was reorganising and developing touch. It could not see that deadlines were regarded internally as unrealistic, that information was being softened or that leaders held an inflated view of Symbian’s readiness.

The prototype was received as evidence that Nokia was responding rather than evidence of how far it might have fallen behind.

There were clues, but no public signal powerful enough to outweigh the record volumes, market share, margins, profit and brand value. Almost everything conventional analysis measured in November 2007 pointed in the same direction.

There was no visible crisis to detect.

The crisis was in the system through which reality became a decision.

For investors, acquirers and lenders, that is where this matters. Financial diligence can tell you what the organisation has produced. It is far less capable of telling you whether the people closest to the work can contradict the assumptions behind the forecast, whether the contradiction reaches the people allocating capital, and whether those people are willing to bear the cost of acting upon it.

The question sits somewhere other than the numbers.

Does the business have a working route for bad news to reach the person who can act on it?

Does the information remain intact as it travels?

Can leadership distinguish a manageable product problem from a shift in the basis of competition?

Has anyone tested the route using information that threatens current revenue, status or sunk investment?

Samsung met the same disruption, in the same market, at roughly the same moment. It is not a controlled experiment. Samsung had different assets, less software legacy to protect, substantial display and semiconductor capabilities, and fewer reasons to defend a single proprietary smartphone platform.

That difference is part of the point.

Across 2007, Samsung was the third-largest handset manufacturer. It had shipped devices running Windows Mobile and Symbian. It announced its own operating system, Bada, in November 2009 and continued developing it.

It also placed its flagship smartphone on Android.

Samsung launched the Galaxy S in June 2010 across roughly 110 operators in 100 countries. It accepted that its most important handset would run software controlled by another company and that the success of Android could weaken the relevance of its own platform.

That was the cost Nokia’s managers feared. It meant surrendering a degree of control, weakening the case for proprietary software and redirecting investment away from capabilities the company had spent years building.

Samsung paid the price of dependency on Android.

Nokia continued paying the price of protecting Symbian.

Nokia’s past success made the necessary decision more expensive. The larger the revenue stream, internal organisation and accumulated identity attached to the existing model, the harder it became to treat evidence against that model as an instruction rather than a problem to be managed.

The transferable lesson has little to do with mobile phones or platform strategy.

The quality of a business’s decisions is capped by the quality of the unwelcome information that reaches its leaders and by their willingness to bear what acting on that information will cost.

Where honesty carries a personal charge, bad news will soften. The charge need not involve dismissal or formal punishment. A cooler tone, a shorter hearing, an irritated response or exclusion from the next discussion is enough to teach somebody what kind of truth is welcome.

Where the truth threatens current revenue, internal status or sunk investment, its implications can soften even when the words arrive intact.

A leader can hear the warning, thank the messenger and continue funding the same plan.

Creating safety for the messenger costs little. Acting on the message may cost a great deal. It may mean abandoning investment, cannibalising a profitable product, changing a public commitment or admitting that the capability on which the strategy depends is weaker than leadership believed.

That is the test.

The marker can be checked this week.

Bring to mind the last three occasions when somebody reporting to you brought unwelcome news: a date that had slipped, a product that was not working, a competitor pulling ahead, a customer preparing to leave or a capability that was weaker than the plan required.

Did the messenger pay for it, through your tone, the length of the hearing or the access they received afterwards?

Then ask what changed because they told you.

Which decision was reopened?

Which resource moved?

Which assumption was tested?

Which commitment was stopped?

If the answer is that you listened carefully and carried on, the information arrived and the truth still did not.

If you cannot bring three occasions to mind at all, the absence is the finding.

Somebody in your business already knows what an analysis like this would uncover. They may have explained it carefully, softened it into language the organisation can tolerate, or decided that the consequences of saying it plainly are greater than the consequences of staying quiet.

The question is whether you have taught them that saying it is safe.

The harder question is whether you are willing to pay what acting on it will cost.