Pretty much everyone agreed that Nokia's Symbian/MeeGo strategy was a failure, that Nokia were quickly losing marketshare and that they needed a new OS.
The only options were Android and Windows Phone 7. WebOS would have been a better fit than either, but that option had already been and gone.
I think there are compelling reasons why Nokia would choose WP7 over Android.
There is a competitive advantage in being the flagship manufacturer of a platform, they won't have to play catchup against much more established competitors, or have to directly compete with cheap Chinese phones from companies like ZTE in the low-end. That's without going into the favourable terms that Microsoft no doubt offered.
I have to tread lightly here, as I don't want to get anybody in trouble... but I can assure you that the new CEO is doing very much the right thing. Software development is not a core competency (or even a competency) at that company. It's just not. I'm not surprised that about half of tampere left, they are going to be hard hit by this. They should be.. the quality of the work just hasn't cut it.
Their best hope to survive today is to tie themselves to a much healthier eco-system. I would have thought Android to be the very logical choice... but the Microsoft move certainly makes sense.
That's the honest truth. When Nokia opened the Symbian code three years ago, it offered a peek into their software development process... And it wasn't a pretty sight.
I used to spend a fair bit of idle time browsing through the Symbian Foundation wikis and forums (all now offline). It seemed that there were basically two kinds of people working on the operating system. The guys in England, who used to work for Symbian Ltd, were pretty smart but arrogant; in old-school programmer style, they were only concerned with managing some extremely narrow domain and couldn't take any criticism.
Then there were the Finns at Nokia, who were either completely uninterested and oblivious to the world around them, or just obviously incompetent at the job they'd been given. An example of the latter was the "Direct UI" proposal in 2009. It was supposed to outline a completely new touch UI paradigm to ship in Symbian^4. All there was was a few pages in broken English that essentially said "it should be like iPhone because touching stuff is cool".
Unsurprisingly, Symbian^4 was canned last October after years of development. I'd like to know who had made the decision to put the same people who had mismanaged the previous S60 user interface in charge of creating the replacement... But that's how it went at Nokia. No one ever lost their job for screwing up the software -- until now.
I guess my question is maybe a little different, if Nokia is in that much trouble, then isn't WP7 a gamble? Its not just flying off the shelf where Android on the other hand is. Two losers don't usually make a winner. I don't know, seems like Google is all in with Android, they've got a pipeline, they've established themselves and proven themselves and they are legitimately competing with iPhone.
Now if they think WP7 is the future and it's going to take the market away from iPhone and Android then it makes sense, but I don't know that anyone really thinks that, it might carve out a niche but it's not going to beat the other guys. There are now iPhone, Android, RIM, WebOS and WP7 in the smart phone market, seems like a lot to me.
This is not going to go over well in Finland's politics is what I was saying. If this move costs thousands of white-collar jobs, this guy may end up being as popular in Finland as Julian Assange is in Washington DC.
People are also saying that the deal is only beneficial to Microsoft. The two real choices Nokia had were Android and WP7. WP7 seems like a more sensible choice to me. Sure they will have to sacrifice things, but they might gain overall. I think Microsoft and Nokia together make a killer combination that is going to help both these companies to bounce back in the mobile arena.
But if a person is leading a company, they might perhaps consider the psychological impact of their decisions along side with technical and market factors. I mean, his job is to make money - not to make decisions that "would have worked if it hadn't been for those pesky workers" (unless the intent was to gut the company from the get-go - though I doubt that would leave more money in the end either).
Desperate measures were needed. But I don't think I'm alone in feeling depressed that the desperate measures seem involve a move back toward proprietary systems (even if my only involvement with Nokia has been using the excellent QT library).
If, assuming, your aim to get some value out of a company - get some value out of the technical teams that exist in the company, one assumes that one needs to keep the morale of that company at a certain level. And giving the impression that you're gutting everything the company stood-for seems like a not-terribly-effective approach here even if Nokia's internal process was broken.
If you're the underdog, being able to claim you are "fighting for good" is psychologically useful. If Nokia had gone with android, one might be able to believe they'd bring some open source "chops" to the table.
Again, my experience is programmers are willing to work to fix a broken - if they feel like the company if offering them loyalty. Obviously, today's announcement didn't make Nokia's workers feel that was happening.
Nokia's stock dropped a bit after this, btw.
Better link to the story also: http://www.betanews.com/joewilcox/article/Microsoft-is-the-p...
Except, he was only at Microsoft a year and a half and before that he was with Juniper Networks and before that with Adobe Systems.
What I mean is, he knows more about Microsoft and how their offerings might fit in at Nokia (than say an OS by a company he's not familiar with), but it's a stretch to couch it as if he was an old time Microsoft employee who is going to force Microsoft on Nokia.
Whether you agree with the decision or not, nothing about it sounds in the least bit criminal.
I'm not saying anything actually is wrong, I don't know enough about it to care. But what I do see is Nokia being a big employer and part of national pride for Finland. This will likely become an issue in politics there.
They'd be wise not to lay off a single soul due to this deal at this point. Ironically, if Nokia really did need to trim R&D expenses, they may have more trouble doing it now.
Keep in mind the EU is still active in MS antitrust and users are offered the choice of Firefox when they install Windows. I would not want to be the guy who's name was attached to the sinking of Nokia at the advantage of Microsoft.
Does this suggest that the board wanted to do a deal with Microsoft all along? If so, why would they need to hire him to do it?
Or that they didn't know what they wanted and this guy seized the initiative?
Edit: answering my own question. I think the board probably brought this guy in to take the heat in case this deal goes really bad from a PR and legal perspective.
But less surprising than if he was to announce, say, that Nokia is pivoting to become an oil company.
Definitely, since that'd be utterly absurd.Any company that comprises a measurable percentage of a country's GDP and a big share of its exports had better take into account some political considerations.
Developers aren't dumb. Hedging one's bets often makes for a self-fulfilling prophecy.
There are places he could be arrested if there are any hints this value destruction is on purpose.
It's like he took the playbook from ObjectShare (Smalltalk vendor) when the CEO announced, "Hey gang, let's go Java!" then was surprised when the personnel situation started to go pear shaped.
Someone is out of touch with his employees here.
I think the move to WP7 may well be a savvy one (though I too would like to have seen a demo of it running), but can completely understand the employees concern.
Perhaps it would have made more sense to be more specific about what is going to happen with their employees, and done it internally - before rushing to tell the world about their new partnership. The resultant leaks wouldn't have been much bigger than what we already had this week.
So was ObjectShare's move to Java. That's not the issue. The issue is management being so out of touch with the employees. It's like a car with a loose steering linkage. Lots of things can go wrong, but a mechanism by which you'd even feel those things is also compromised.
I've read the same script before. The way this move was presented to the employees had bad results. I doubt the bad parts were really necessary.
It's a complicated situation. I doubt there was a binary choice whether or not to knife the baby.
But I have a lot of sympathy for developers who have good reason to think their employer is steering their job into the trashcan, especially if they're in a city where there aren't a lot of other places to work.
Apparently the market isn't too keen on this either http://www.google.com/finance?q=NYSE:NOK
1. Board isn't impressed with current inhouse developements, and wants a "modern" mobile OS. There aren't really many alternatives to WP7.
2. Old CEO doesn't want to bend over to MS
3. Kick old CEO out and get a guy from MS to do negotiations with MS to license WP7
Can you say it with a straight face? Without laughing?
Reasonably successful? I dare you to name one single Nokia-phone made the last half decade which you would consider relevant.
The truth is that platform-wise and software-wise, the bits you interact with, they've been stagnant since around 2000 and no amount of megapixels or Carl Zeiss optics will be able to compensate for that. They seriously need to throw their old stuff away and start going on something new. Like Microsoft did with Windows Mobile prior to Windows Phone 7.
I'm honestly surprised they didn't do it years ago. Now they've finally gotten a CEO which actually understands this and is willing to act on it. About time! While Microsoft is a risky bet, this move may actually save Nokia from complete annihilation and is certainly better than doing nothing at all.
And so far, Windows Phone 7 looks pretty good. Care to elaborate on how it is a failed platform already? Not disputing it if you have numbers, just that so far I've actually seen more enthusiasm for it than I expected to see.
Well "dare" is a pretty big word, as if you're making some kind of threat of retaliation if I do.
So let's just ask Google: http://www.google.com/search?q=nokia+market+penetration
Second link: http://gigaom.com/2010/03/18/the-mobile-os-market/
Check that out. According to that data, in the 2007-2009 time frame they shipped more cell phone operating systems than everyone else combined. That probably translates into a lot of physical Nokia phones, too.
The point that it may be stagnant is well taken, which is why I said "reasonably successful" instead of "stomping everyone else into the ground".
But irrelevant it is not.
Fair enough. But if you look at how quickly Windows Mobile went from being the de-facto Smartphone OS to completely irrelevant and take into account (as Nokia's CEO acknowledged) that they are being taken on and losing market-share at every point which they've usually excelled at, it's clear that while they may not be irrelevant now, the way there is not very long.
The need to do something drastic was IMO very real. If going for Microsoft and Windows Phone 7 as opposed to other options like Android was the best choice can clearly be debated, but something had to be done. Staying with the "reasonable successful" platform they had would not have been a viable long term strategy.
http://en.wikipedia.org/wiki/List_of_best-selling_mobile_pho...
Do you have a source handy? It would be interesting to see how Nokia's market penetration (however declining it may be) compared to Microsoft's.
But Nokia dropped far less (47.6% -> 37.9%), proportionally, than Microsoft (8.7% -> 4.2%).
No question that Microsoft is the winner here.
1. Hire someone from Microsoft to run the company
2. He says "our platform is burning, we have to do something drastic" which most people interpret as "prepare to come up with a strategy and fight like hell to win".
3. Guess what, he already had something in mind! It was "throw out our current reasonably successful development efforts and become a licensee of Microsoft's failed platform instead". And piss off all our QT-based app developers at the same time.
What could possibly go wrong?
I seriously wonder if this guy might not end up having to leave and not set foot in Finland (or the EU) again for fear of arrest. I have a feeling some Finland business regulators will be going through his emails with a fine-toothed comb.