Apple’s profit line has beaten Microsoft’s profit line.
It’s an occasion whose importance rivals one of a bygone era: The day the “Whopper beat the Big Mac,” back when the burger wars were upon us.
Comparing very much of anything having to do with Apple to anything having to do with Microsoft is about as sensible as comparing, say, General Mills and New Line Cinema. They compete where, exactly?
The usual stomping ground for this analysis is Apple’s legendary success with innovation (iPod, iPhone, iPad) compared to Microsoft’s failure with competing products (Zune, the quickly disappeared Kin, and the tragically aborted Courier).
Not to defend the indefensible … and both the Kin’s existence and Courier’s nonexistence are pretty close to indefensible … but really. Apple is a consumer products company. Its successes are in its core business. Microsoft’s most frequently ridiculed failures are in its consumer products, which, for both you and Microsoft, just aren’t very important.
What’s gone wrong with Microsoft’s innovation might be less a failure of innovation than of explanation.
Think of it as Microsoft channeling the old Novell. Back when, Novell introduced a brilliant innovation that just about killed it: Netware Directory Services (NDS), which replaced the Bindery when Novell introduced Netware 4.0. NDS offered incredible advantages over all preceding identity management technologies, along with just one small disadvantage: Nobody could make heads or tails of it, and Novell couldn’t figure out how to help them.
The upshot: Many of its customers figured the Netware 4.0 upgrade was a sufficiently radical change from its predecessor that conversion to, say, Windows NT Server was easier. Brilliant innovation resulted in a permanent loss of marketshare.
Microsoft is an IT infrastructure company, not a consumer products company. Among the disadvantages: Most in the business press who like to write about subjects like innovation and strategy lack the background to understand what successful infrastructure innovation even looks like. So they fall back on the Zune to illustrate Microsoft’s haplessness.
As is so often the case when business commentators take on technology, they’re missing the point entirely, which in this case is that Microsoft appears to be in the forefront of technology-enabled collaboration. SharePoint, Office 2010’s “simultaneous editing,” and their tight integration appear to be a strong match to the requirements of a modern workforce. That Microsoft has been inept in promoting these capabilities changes nothing about the technology itself.
And “inept” is a pale word to use in describing its failings.
Here’s just one example … a very prosaic one … of what you ought to be doing with this technology: Using it to replace all shared folders.
Right now, many employees in most organizations waste quite a lot of time managing document versions. Typically, employees send documents to each other as e-mail attachments and then, later on, struggle to merge edits performed on multiple independent copies. (Dialog: “What’s the date/time stamp on your copy? I think mine is later. What does yours say in the second paragraph of the Executive Summary? I’m pretty sure that’s the old version.”)
Or, they might make use of shared folders only to have edits from different users collide when they try to save.
Most companies, when they do roll out SharePoint, implement it as yet another place to store documents, thereby creating confusion. Were they to use it to replace shared folders and e-mail attachments, educating end-users in the miracles of document check-out, check-in, and simultaneous editing, it would be like spraying WD-40 on a squeaky hinge.
On lots and lots of squeaky hinges.
And that’s just one, very simple example.
One other dimension to this: Unlike its competitors, which seem bent on wasting the CPU that sits in front of the end-user, Microsoft hasn’t lost confidence in its value. I just wish its marketing included an emphasis on re-legitimizing the personal in personal computing.
Doing so is long overdue.
Then there’s .Net, which I confess I expected to be a miserable failure when Microsoft first introduced it. Instead, it seemingly has more mindshare than Java for mainstream application development.
Microsoft has more than its share of flaws these days, and the quality of Steve Ballmer’s leadership there is debatable. Still, it’s bad enough when we fall for great marketing that masks poorly constructed products … not a bad description of our relationship with Microsoft over the past few decades.
We now might just be facing the opposite: Marketing so poor that it disguises innovations we ought to be leveraging to the hilt.