3 ms·
But is the distance from the top to the bottom surprising? Microsoft in 2010 is a much more complex animal than it was in 1996. IE, Xbox, Azure, Windows Mobile,
by ilamont 17y ago
But is the distance from the top to the bottom surprising? Microsoft in 2010 is a much more complex animal than it was in 1996. IE, Xbox, Azure, Windows Mobile, Bing, etc. didn't exist back then, or were in the early stages of development. With more products and more interconnection between product groups, there is bound to be an increase in managers and layers because the existing management can't scale to take on all of these new tasks.
- hga 17y agoI'm not addressing your point, I'm only saying that harsh experience shows that an organization gets grossly disfunctional as you increase the number of layers from 5. My answer to your point would be that it's the job of the CEO and board to structure the company so that it's as close to the ideal as possible. In the case of Microsoft, one approach would be to force less coordination on some of these separate units. As it is, they pay a terrific "architecture tax" by having to use and support (and generally only use and support) Microsoft products. If it turns out they must do that to keep the core of Windows, Office and server products viable, well, that suggests they shouldn't get into the businesses that can't be usefully built on top of the core in the first place, and get out once they realize that.
- ilamont 17y agoI agree that in Microsoft's case, less coordination on some of these separate units would really help. I've read elsewhere that getting buy-in from different departments/product groups has led to some seriously delayed or disfunctional products. But regarding one of your other statements, I am not so sure: Harsh experience shows that an organization gets grossly disfunctional as you increase the number of layers from 5. What about other organizations like Wal-Mart or the Navy? Surely there are more than five layers from door greeter or new recruit to CEO or 4-star admiral, yet the organizations are able to function and carry out their missions. Or are software companies different?
- henrikschroder 17y agoOne obvious difference is that in the military, there is only one career advancement path, where each level trains you in the skill-set needed for the next. In software development, being a good programmer doesn't make you a good project manager, which in turn doesn't make you a good middle manager, which in turn doesn't make you good at making the business decisions of the management group.
- hga 17y agoAnd the emphasis on this in successful military establishments is very strong: if a superior officer becomes unable to carry out his duties in a battle a subordinate is expected to immediately step up and take command. Companies have the luxury of being able to do this in time frames not measured in minutes and seconds. The US officer corps post-WWII also (in theory) defeats the Peter Principle by an "up or out" rule. If you do not advance in rank and responsibilities within set time frames, you are retired (which of course has its own problems). I suppose the Microsoft "long at level" concept is related to this ... but I don't think it works in this field for some of the very reasons you noted.
- hga 17y agoI don't know about Wal-Mart (but I'd expect their management structure to be lean in the Sam Walton era), but the DoD in the Vietnam period was where I first heard of this principle. And the US Army certainly didn't go a good job of carrying out their mission then (the US Navy hasn't been put to the test since WWII ... and one might say they haven't been doing a bang up job of policing the sea lanes as of late (South China Sea, off the Horn of Africa)). I don't think most companies are different, at least when it comes to the non-rote stuff. I.e. in a fast food restaurant the people are the bottom are supposed to be following a "book". With the exception of navies, I don't think that works in warfare (I make this exception since most of the lower people have clear missions like "keep the ship afloat" and "fire this gun"; that doesn't work for infantry, armor or tactical air (might work in part for artillery)). It most certainly applies for software firms, e.g. the IBM Chief Programmer Team concept has been shown not to work in practice.