News broke overnight about Microsoft Office executive Stephen Elop moving to Nokia as CEO. This by itself is shocking news, but what other shocking aftershocks might follow?
I’m no Nokia expert. All I know is that my first mobile phone was from Nokia back in the 90s but that nothing they’ve made recently has been compelling enough for me to seriously consider it. Many have given up on Nokia, especially in the US where most of the smartphone action has been.
Microsoft, I’m much more familiar with. Had one of the very first Windows Mobile phones before they even called them by that name. For a while, they were competitive, but as time went on, others, notably Apple and Google left them in the dust. Many have given up on Microsoft in mobile. But Windows Phone 7 is about to launch. And I’m not ready to write it off.
The market has spoken and said it likes the idea of alternative, more open offerings than those from Apple. It also still likes Apple, but a lot of the Android success is due to offering more choices than Apple does (carriers, form factors, etc.). But with that openness comes tradeoffs. Ironically closedness due to increased carrier power. A bit of fragmentation. Things that Microsoft has learned the hard way through a decade of Windows Mobile mistakes. Google is learning them now. So, timing for Microsoft with a hopefully ‘just right’ balance between control and open, could be very good.
Elop, in his short time at Microsoft, was involved in deals that put Office and Silverlight on Nokia phones. There’s been a lot of ‘advice’ given to Nokia that has suggested they drop everything and go Android. Here’s my radical thought: Nokia will go Windows Phone 7.
Many have written each off. However, together they have a much better chance.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.