Feeds

Microsoft bricking lesson bodes badly for Elop's Brave New Nokia

There are times when you need a bureaucracy...

Designing a Defense for Mobile Applications

If the WP team didn't know this, they do now. This is something that's very hard to do right. There are OEM variants, and each has diverse variants for multiple operators in multiple territories. Keeping track of all this is a job, and this is where it helps to have a large, experienced and highly structured set of engineering and administrative QC procedures. It helps to have something resembling - dare I say it - a bureaucracy. And this is what Nokia has, and is actually quite good at.

This is also what Elop has set out to destroy.

He evidently has a low regard for Nokia's ability to get things done quickly, and so has handed Nokia's WP development to small teams, to work closely with Microsoft and in isolation from the juggernaut of the bureaucracy he inherited. In essence, he's created a skunkworks within Nokia, while the old company is destroyed around it.

Jobs did something similar when he returned to Apple. Elop's conundrum is that he still needs a large, complex administrative apparatus to produce modern phones.

So what can he do? When Steve Jobs carried out his reverse-takeover of Apple, he brought with him staff experienced in creating high quality hardware, and mature, proven software, along with the people who had written it. They had experience of working together. That "skunkworks" was the NeXT.

Elop's job is so much harder. Little has prepared him for this, and even less has been written about this aspect of the strategy since he announced it on Black Friday.

There are very few precedents for what Nokia must do, and I'm stumped if I know. It's why I'm not a management consultant. I don't even know what a change management paradigm is (remember), or care particularly much that I don't know.

But if you multiply the damage caused by this week's patch, by the volumes of Windows Phone that Nokia wants to sell, you can see the problem. It's going to have to be fixed. ®

HP ProLiant Gen8: Integrated lifecycle automation

More from The Register

next story
Scotland's BIG question: Will independence cost me my broadband?
They can take our lives, but they'll never take our SPECTRUM
Bring back error correction, say Danish 'net boffins
We don't need no steenkin' TCP/IP retransmission and the congestion it causes
Auntie remains MYSTIFIED by that weekend BBC iPlayer and website outage
Still doing 'forensics' on the caching layer – Beeb digi wonk
NBN Co adds apartments to FTTP rollout
Commercial trial locations to go live in September
Samsung Z Tizen OS mobe is post-phoned – this time for good?
Russian launch for Sammy's non-droid knocked back
Telstra to KILL 2G network by end of 2016
GSM now stands for Grave-Seeking-Mobile network
Seeking LTE expert to insert small cells into BT customers' places
Is this the first step to a FON-a-like 4G network?
What FTC lawsuit? T-Mobile US touts 10GB, $100 family-of-4 plan
Folks 'could use that money for more important things' says CEO Legere
prev story

Whitepapers

Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Consolidation: The Foundation for IT Business Transformation
In this whitepaper learn how effective consolidation of IT and business resources can enable multiple, meaningful business benefits.
Application security programs and practises
Follow a few strategies and your organization can gain the full benefits of open source and the cloud without compromising the security of your applications.
How modern custom applications can spur business growth
Learn how to create, deploy and manage custom applications without consuming or expanding the need for scarce, expensive IT resources.
Securing Web Applications Made Simple and Scalable
Learn how automated security testing can provide a simple and scalable way to protect your web applications.