Commentary

Dave Methvin
 

Microsoft Needs To Want Change--It's Not There Yet

In October 2005, Ray Ozzie told Microsoft executives what needed to happen to make Microsoft a leader in Internet services. Ozzie had been at the company for about six months at the time. Now it's more than three years since Ozzie joined Microsoft. Is he making progress on this goal?

In October 2005, Ray Ozzie told Microsoft executives what needed to happen to make Microsoft a leader in Internet services. Ozzie had been at the company for about six months at the time. Now it's more than three years since Ozzie joined Microsoft. Is he making progress on this goal?In his memo, Ozzie stressed the opportunities in advertising-driven business models. Microsoft is a distant third in Internet advertising, but quite a bit of that has to be because of the lack of compelling content in Microsoft's own sites. The Yahoo bid must have been intended to jump-start Microsoft in an area it clearly thinks is important, but you have to wonder why Microsoft made so little progress on its own in three years.

Here's my reason: Microsoft doesn't yet want to change badly enough. Too many parts of the company are comfortable doing business the way it's being done today. I'm sure that there are many executive meetings where the division heads nod in agreement at Ozzie's master plan. When it comes down to implementation, though, they point out that these new ideas pose a threat to their existing products, and it's inevitable that revenue on existing product lines will go down faster than new product and service revenue goes up. Timid action, then, is the best course for near-term profitability.


More Windows Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Here's one quote from Ozzie's e-mail:

Complexity kills. It sucks the life out of developers, it makes products difficult to plan, build and test, it introduces security challenges, and it causes end-user and administrator frustration. Moving forward, within all parts of the organization, each of us should ask "What's different?" and explore and embrace techniques to reduce complexity.

To at least some parts of Microsoft, this is heresy. Complexity seems part of the intellectual challenge and key to Microsoft's competitive advantage. Plus, all the pieces-parts have to be Microsoft through and through for complete and total control of their products. The job isn't done at Microsoft until it's embraced, extended, or reinvented Java, Flash, browsers, and every other technology it may need to use. Nothing needs to be taken as given in a Microsoft plan; Microsoft can tweak every piece, and every division of the company wants to be a major player in the vision. Microsoft Web sites will be built with the .Net Framework, C#, Silverlight, and other Microsoft products; thousands of Microsoft employees will be needed to support those technologies.

Google, whether by necessity or by choice, has decided to take advantage of outside work on browsers, programming languages, and other technologies. Yahoo can't force users to choose a browser, so it focuses on a Web framework and design patterns to make its sites work with whatever the user has. As a result, these companies put most of their attention on delivering content, services, and advertising. Microsoft can't do that, not even its Internet group, because those choices are constrained by what the other Microsoft groups want to deliver.

With that perspective, Ray Ozzie's vision seems to be too ambitious. It manages to include nearly every nook and cranny of Microsoft's empire, and tries to tie them together into the master plan. But that will just make things harder to change. The Internet group is the tail of Microsoft; every other part of the dog is more profitable and therefore more influential -- no matter the lip service to the Internet. The technical complexity can't be eliminated because it reflects organizational complexity and priorities. Unfortunately for Microsoft, there's no sign that the company has a plan to address that problem.


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

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek 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. InformationWeek 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.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links