February 18th, 2013
(written by lawrence krubner, however indented passages are often quotes). You can contact lawrence at: email@example.com
Having lived in Seattle for a couple of years, and knowing many Microsoft employees during that time, my outsider’s view is that MS’s consumer-side failures are largely geographical and cultural.
Redmond, or even Bellevue, is extremely isolated from Seattle, which in and of itself is not exactly deeply intertwined with the cultural centers of the US. Locals know this – Microsoft employees who move from Seattle across the lake to the east side often joke about nobody ever visiting them again (sometimes less-than-jokingly). It’s also more or less a company town – Microsoft’s presence is so overwhelming and absolute that a lot of the technological zeitgeist from the rest of the country never make it there. If you lived/worked there it’s easy to believe Microsoft’s ridiculously optimistic PR pieces – pieces that would be hilarious when read in any other environment.
This isn’t even an urban/suburban argument (though it has shades of it), it’s a “company town vs. diverse city” thing. Microsoft’s geographical location gives its people tunnel vision and a grossly false picture of the technology sector.
The second part I’ve observed is a lack of internal honesty within Microsoft. Failure seems to be couched in safe corporate-speak to the point where it’s greatly muted (maybe that’s the intent). You cannot expect your work force to pivot and fight hard when they’ve been falsely told their giant failure was a minor hiccup. I saw this after the WinPhone launch – MS employees were still honestly bullish about its prospects even when the market as a whole had completely rejected it.
If MS wants to be nimble in the consumer space, it needs to set up shop in cities where their competitors play – you will not get an honest impression of how your products (or your competitors’ products) are doing otherwise. They also need to have frequent, honest, no-holds-barred accountings of how they are doing. If a product was a flop, call it a flop
This is also good:
Your observation in many ways can be extended to the Microsoft ecosystem as a whole. Microsoft as a company has always had this weird thing where the materials they release (marketing, documentation) are written in an alternative universe where no non-Microsoft technology exists. I haven’t been part of the MS ecosystem for a number of years but I do get the sense this has been changing. But in many ways I don’t think it’s a deliberate framing, it’s likely just as much due to the reality that inside of the Redmond/Bellevue bubble, things like Ruby on Rails, the iPhone, and non-IE browsers are weird, untrusted 3rd party technologies that nobody uses (partly because they think Microsoft products by definition are better, partly because they fear if word gets out they are toying with these things there will be negative consequences.) I remember when C# was originally released the degree to which Microsoft managed to pretend like Java did not exist was just plain bizarre.
I guess one way to look at it is Microsoft is a good counterweight to the argument you should eat your own dogfood. You should, but you should not do so exclusively.