Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Eric Zeman

Former Nokia Exec Slams Elop And Windows Phone

Former Nokia senior executive says CEO has wrecked the company with his choice to adopt Windows Phone.

Nokia is in terrible trouble, and Lee Williams, Nokia's former SVP of Series 60 software, blames it all on CEO Stephen Elop. The problem, according to Williams, is that the company is bleeding cash, executive talent, and market share at a frightening pace. In a lengthy and far-ranging interview with CNET U.K., Williams vents about Nokia's downward spiral and casts aspersions aplenty at the Finnish firm's leadership.

In a nutshell, here are the problems, as Williams sees them:

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

No Vision. Nokia CEO Stephen Elop has no long-term vision for the company. "Elop hasn't delivered a roadmap. There's no overarching vision for this company. That to me is akin to stepping completely out of the leadership role and running behind the bus now... Before Elop, Nokia would never give up that leadership position and role in the marketplace, [and] would always talk about the future."

[ For more on Nokia's challenges, see Nokia's Lumia 'Not Good Enough' Say Carriers. ]

Ditching Symbian was a bad idea. Symbian was Nokia's bread and butter for a decade or more and is still among the top smartphone platforms in the world as far as installed bases go. Williams believes that Nokia should have continued developing and selling Symbian to maintain its economic footing.

"[Symbian] was Nokia. That was Nokia's brand, we knew we could count on that [to generate handset sales,"] notes Williams. Without Symbian to keep it afloat, Nokia's financial free-fall is no big surprise. (Never mind the fact that Symbian had become a terrible, bloated, fussy OS over the years. It has become obsolete for a reason.)

Adopting Windows Phone was a bad idea. While Williams gives some credit to Microsoft's platform, he believes Nokia's decision to use it as its sole smartphone platform moving forward was the wrong thing to do.

"I did not see a good reason to change course so frantically," he said to CNET. "I don't think Nokia was going in the wrong direction with some of the things it was doing--it was simply executing poorly before Elop got there and they weren't giving it enough time. It might have made sense to introduce a product or two into the portfolio based on Windows Phone. What I do not think they should have done is pretend it is a one-horse race, and that one software system is all you need."

Nokia failed to execute even with Lumia. Sure, Nokia may have sold about one million or so Lumia smartphones to date, but they have major shortcomings that will eventually bite Nokia in the behind.

"Now they have a Windows Phone product, and the differentiators are nonexistent, the battery life is orders of magnitude behind their other products, and the best imaging or camera features are not able to be fully realized leveraging the Windows Phone code. These products will have some success in the marketplace, but not at the scale or level needed. They can fix some of these things over time and with substantial ecosystem support, but the marketplace is a harsh mistress. I don't think they have that kind of time."

Android won't save Nokia, either. Last week, PCMag's John C. Dvorak ran an interesting piece foretelling Nokia's doom if it doesn't drop Windows Phone right away and switch to Google's Android platform for its smartphones. Boy, does Williams disagree with that position.

"Android is a less capable offering than a few options that still exist within Nokia," said Williams. "It's certainly not what I would refer to as an open system. More than that, I think that Nokia has little opportunity to differentiate here in the near term, and the Android platform is so highly fragmented that returns on investment become difficult at best for an ecosystem participant."

Losing Finnish employees is a bad idea. Williams also bemoans the heavy changes within Nokia's leadership ranks. Finns are leaving in epic proportions and are being replaced with North Americans. This is a problem, says Williams, because "Nokia is Finland, and Finland is Nokia."

I can't disagree with this sentiment. One thing I've noted about Nokia's recent press conferences is that Finns never take the stage any more. It's always Americans or British Nokia employees who make the announcements. Nokia is, at its core, a Finnish company, and the penetration of the top ranks with non-Finns isn't the best thing for the company.

Here's the salt lick, caveat, etc. Williams does make some interesting points in his diatribe, but from my perspective he comes off as a jaded ex-employee. The man ran the company's Symbian software division for nearly four years, so what he sees is his baby being dragged out back and shot in the head. It's hard not to feel bitter about such a thing.

Williams in particular seems to believe that devices such as the Meego-powered N9 prove that Nokia can get things right. Perhaps. The N9 was a solid device with decent software, but it took Nokia three or more years to get that software to market--and it's still far from perfect. The usability factor of Meego is nowhere near what it is with Android, iOS, or Windows Phone.

The bottom line is this: Yes, Nokia has made some mistakes and is in a wee bit of trouble. Things are bleak, but not as bleak as some former employees might suggest. It is entirely possible that Nokia can--with Windows Phone--eventually turn itself around. It won't be easy, but it's not an unattainable goal.

See the future of business technology at Interop Las Vegas, May 6-10. It's the best place to learn how cloud computing, mobile, video, virtualization, and other key technologies work together to drive business. Register today with priority code CPQCNL07 to get a free Expo Pass or to save 25% on Flex and Conference passes..



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.