Blog is on pause, but please do enjoy my tweets :)

Showing posts with label thoughts. Show all posts
Showing posts with label thoughts. Show all posts

What hit Nokia - Elop or mediocre Middle Managers?

I have been repeatedly asked that what killed Nokia. I thought I'd better do the analysis now, when I still remember something about it. Tomi Ahonen writes exhaustively how incompetent formal Microsoft executive ruined it all, but I have to disagree with Ahonen that much, that there were also other reasons than just Elop.

Accusations on the burning platform memo are valid, but Symbian had already been burning for years. It was like a fireplace that keeps the house warm, but must be watched. More or less the memo peaked the crisis both externally and internally. Despite the crisis, the issue of what was the pothole that caused the decline of the competitiveness and consumed majority of the R&D resources, has not been discussed. Here I name a factor that hasn't been accused before: middle management.


I have several posts where you can find me reflecting this very topic, but in very general level. Now to be more concrete, I'll list few major reasons why Nokia among other big organizations failed:

Culture of finding problems, risks and saying no.
Engineers are taught to find problems. Under pressure, stress can create impossible obstacles out of ordinary challenges. If company culture does not support positive approach of accepting both the challenges And the cruel facts which might follow, the Culture of No get's into speed and managers prefer to make anticipated setbacks easy for their teams and themselves.

Culture to support innovation.
Despite Elop accused his employees of failing to deliver innovation, good proposals never stopped flowing despite repeated setbacks. What explains these contradicting views could be explained by having a highly innovative employees and a middle management cutting the wings of the proposals. According to Johtopätkii, creativity consists of competence, motivation and commitment which were in order thanks to the good reputation of the company among earlier recruits.

Making good work.
Everybody wants to make a good work. It's a matter of what you measure. If project has multiple stakeholders, everyone of them wants to optimize their part of the project. Abstract example; if sourcing, project manager and finance do magnificent work, the result can be poor hardware, hasty design and lousy experience. The need to make good work is also connected to fear of mistakes and to the pressure of getting good results to keep your job.

Pressure and fear.
Before starting in Nokia I had experienced two lay offs and been part of terminating two contracts, but I still thought that it was a unusual situation. Lay off waves in Nokia came more often than once a year. Even a single wave has a huge effect to the motivation, self esteem and effectivity - and repeated more so. Also reorganizing, replanning and the mistakes along with the corrective actions consume a huge amount of time and resources. Further if management anticipates new waves, they try to do extra good work and to say often no, which leads paralyzing the other half of the company.

Lack of vision.
Before Nokia seemed to know what was it and where it was going. But during the great rush Nokia had around the time first iPhone launched, they had focused on money and productivity. When readjusting the organization and portfolio to face the new challenge, mission and vision was replaced by an internal disputes about whether to rely on it's true competences. (Competencies that had already producticed the first touch screen smartphone four years before Apple, but was cancelled due the lack of managerial trust.) Or to make fast correction move and glue the touch onto the existing platform and rely on the ridiculous services agenda.
After that the vision has been jumping from side to side, which enabled the next point.

Rise of the career opportunists.
The questionable character in humans is that when things seem hopeless, they face up and hope that some extraordinary force turns everything good again. In Nokia this meant getting new talent to lead things. Positions started to slide outside of Finland due to the appeal of London and Silicon Valley. What happened was that new people started repeating old stupid mistakes, but now their accent was sexy and their designs rocked - at least on paper. Unfortunately when the faith is strong and you made the hire, seeing the truth takes usually way too long.



A job too well done?

In the morning I made our regular oat porridge and while rinsing the pot I started to think that how far the qualities of oat flakes are tuned to enable easy washing of the pot.

Sometimes doing a really good work can end up ruining the rest of the process. Lately I been pondering how to open up this paradox with an example. This might not be the best of examples, but I promise to discuss this issue further in the next post about What hit Nokia.


If I ever got an assignment to develop a better porridge, I would probably consider rinse-ability as one of the most important issues to solve. Likely I would find it as a pain point in user research and likely that would be something what I could develop and the management would like it because it could be easily measured..

Totally other story might be that is it wise.
People might appreciate actually more organic, unprocessed flakes.
But that wouldn't be my business - so most probably I'd end up overdoing and ruining the whole point of eating oat porridge.

Results reflect the working environment?

Sometimes it can be difficult to justify why nice functional environment is important for designers.

At those moments you can discuss whether a top musician would be expected to enjoy a karaoke bar or further - to do work in such.

How to benefit of a cross functional organization

If organization wants to learn from other domains, it first requires accepting that the other disciplines are not doing it Wrong - just differently.

Time, management and how to optimize those two?

Difference of managerial and creative work is
that the first is done in meetings and the latter in between.