Why the Thing That Built You Breaks You.
Why does the pattern survive?
This is the question worth sitting with. Not why did Nokia fail — but why did an organisation full of intelligent, capable people continue to protect a pattern that was visibly harming them?
The answer is not stupidity. It is not cowardice. It is something more structural, and more human.
Systems theorist Donella Meadows observed that complex systems do not pursue the goals written in their strategy documents. They pursue the goals encoded in their structure — in their incentive systems, their hierarchies, the unspoken rules about what is safe to say and to whom. And they are extraordinarily good at it. Even when the goal is no longer useful. Even when the people inside genuinely want something different. The system keeps running the logic that once worked, because nothing has happened to convince it the original threat has passed.
Neuroscientist Lisa Feldman Barrett adds a further dimension. The brain, she demonstrates, is not a passive receiver of experience. It is a prediction engine, continuously building models of what is likely to happen next based on what has happened before. When a person enters an established system, they read it immediately and accurately: what is rewarded, what is punished, what happens to the person who steps out of line. The brain updates its behaviour not as a conscious decision to conform, but as basic survival assessment. The system reshapes the individual. Not the other way around.
This is why hiring people from the outside rarely changes organisations. The newcomer enters, reads the system clearly, and adapts. Within eighteen months they sound like everyone else. Not because they lack courage. Because the system is stronger than the individual. Almost every time.
The pattern does not survive because people are weak. It survives because the system genuinely believes it still needs what the pattern provides.
Your system is not broken.
When leaders look at a dysfunctional culture — the fear, the silence, the meetings where everyone agrees and nothing changes — the instinct is to diagnose a broken system. Something that needs fixing.
But the system is not broken. It is functioning exactly as designed. It is doing precisely what it learned to do, in response to a specific historical moment — a near-collapse, a founding character, a period of crisis — that encoded a particular logic into its structure. The behaviour that looks dysfunctional from the outside is, from the system’s perspective, a perfectly coherent response to a threat it believes is still present.
The question that changes everything is not: how do we fix this culture?
It is: what was this system built to survive? And does that thing still exist?
That question — asked with genuine curiosity rather than defensiveness, tracing the current pattern back to its origin — is where real change becomes possible. Not by dismantling what the system built. The intelligence that kept the organisation alive is still valuable. But by updating it. Bringing it into contact with the present, rather than the crisis it was written for.
The lesson Nokia actually teaches.
The Nokia story that gets taught in business schools is about innovation and disruption. The Nokia story worth teaching is about something harder to see: that the behaviours most likely to destroy an organisation are almost always the same behaviours that once saved it.
The pattern was not a mistake. The culture of speed, strength, and unquestioning execution was a rational, effective response to a genuine existential threat. It worked. It saved the company. And then, fifteen years later, without anyone consciously choosing it, that same pattern closed off the one thing Nokia needed most: the truth.
Most organisations you will lead, work in, or advise are running some version of this. Responding, with perfect internal logic, to something that happened before most of their people arrived. The pattern is real. The protection of the pattern is predictable. And the origin is almost always older than anyone in the room thinks.
Your system is not broken. It is working perfectly. The question is what it was built to survive — and whether that thing still exists.
SOURCES.
Vuori, T.O. & Huy, Q.N. (2016). ‘Distributed Attention and Shared Emotions in the Innovation Process: How Nokia Lost the Smartphone Battle.’ Administrative Science Quarterly, 61(1), 9–51.
Meadows, D.H. (2008). Thinking in Systems: A Primer. Chelsea Green Publishing.
Feldman Barrett, L. (2017). How Emotions Are Made: The Secret Life of the Brain. Houghton Mifflin Harcourt.
Ollila, J. & Saukkomaa, H. (2016). Against All Odds: Leading Nokia from Near Catastrophe to Global Success. Maven House.
Peltonen, T. (2018). ‘The Collapse of Nokia’s Mobile Phone Business.’ In Towards Wise Management. Springer.
You know the Nokia story. Everyone does. But the lesson everyone takes from it is the wrong one — and the right one is considerably more unsettling.
You know the Nokia story. Everyone does.
It gets taught in business schools, cited in boardrooms, referenced in keynote presentations between slides about disruption and the need for agility. The facts are always the same. Nokia dominated the global mobile phone market through the late 1990s and early 2000s, holding close to 40 per cent of worldwide handset sales at its peak. Then Apple launched the iPhone in 2007. Nokia failed to respond. Its Symbian operating system was outdated. The company was too slow, too siloed, too committed to hardware in a world that had shifted decisively to software and ecosystems. Microsoft acquired the phone business in 2013 for €5.4 billion — a fraction of its former value. Lesson learned. Move on.
The lesson, as it is usually delivered, is about innovation. About the danger of complacency. About what happens to market leaders who fail to see change coming.
It is a clean story. A satisfying story. And it is the wrong story.
They knew.
In 2016, researchers Timo Vuori and Quy Huy published a study in the Administrative Science Quarterly — one of the most rigorous academic journals in management science — based on 76 interviews conducted over several years with Nokia managers, engineers, senior executives, and external consultants.
What they found reframes the entire narrative.
Nokia’s engineers and middle managers had known the operating system was failing. They understood, with technical precision, that Symbian could not compete with what Apple was building. The intelligence existed inside the organisation. It was documented, discussed, and understood by the people closest to the work.
Nobody told the top.
Not because they lacked access. Not because they were disengaged or incompetent. Because they were afraid. Nokia’s senior leadership carried a well-documented reputation for publicly humiliating managers who delivered unwelcome information. Vuori and Huy’s informants described senior figures as ‘extremely temperamental’ — known for dressing down colleagues in front of fifteen or twenty peers until, as one interviewee put it, the target’s confidence was visibly destroyed. In that climate, the rational choice was silence. Raise a problem and risk your position. Say nothing and survive another quarter.
So the people who could see clearly said nothing. Top management, insulated from reality by the atmosphere they had created, made critical decisions based on information that had been filtered, softened, and in some cases simply constructed to match what leadership wanted to hear.
Nokia did not fail because it missed the future. It failed because the people who could see the future were too afraid to say so.
Which raises the question the standard story never asks: where did that culture of fear come from? And why did no one stop it?
Where it came from.
In the late 1980s, Nokia nearly went under. The company had overextended across too many divisions — rubber, cables, consumer electronics, paper — and a combination of financial mismanagement and external pressures had brought it to the edge. A new CEO, Jorma Ollila, took over in 1992 with a clear mandate: survive. He did it by being decisive to the point of ruthlessness. He cut everything that wasn’t mobile phones. He moved at a speed that left no room for debate or dissent. He built around him a culture where strength, execution, and unquestioning forward momentum were the only currencies that mattered.
It worked. By 1998, Nokia was the world’s largest mobile phone manufacturer. One of the most dramatic corporate reversals of the twentieth century, achieved in six years.
The management culture that saved Nokia in 1992 became the management culture that ran Nokia in 2007. The aggression that had been genuinely necessary during a crisis — move fast, show strength, do not question upward — had long since become simply how things were done. Nobody had revisited it. Nobody had asked whether it still served the organisation. The system had encoded it as survival logic. And survival logic, by its nature, does not question itself.
Here is what matters. The culture of fear that killed Nokia was not an accident, a personality flaw, or a management failure in isolation. It was the direct residue of the thing that had once saved the company. The behaviour that destroyed Nokia in 2007 was the same behaviour that rescued it in 1992. The pattern had not changed. The world had.
