31 ms·
I 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 de
by ilamont 17y ago
I 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.
- philwelch 17y ago"And the US Army certainly didn't go a good job of carrying out their mission [in Vietnam] (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))" In both cases, the mission was hampered by political leadership. The military was winning the Vietnam War, it was just taking longer than necessary because the White House was micromanaging the war and establishing unrealistic rules and requirements. As for piracy, the Navy has been kept out of the game because it's cheaper to pay ransom than to pay for any significant military operations against pirates. There was a time where we would say "millions for defense but not a penny for tribute", land the Marines in North Africa, and force the pirates to allow safe passage. Nowadays we'd rather pay the tribute--and invading Somalia would be a far more difficult mission.
- hga 17y agoAgreed on "hampered by political leadership", but my studies of the US Army in the period tells me it also was a very large factor in the early to middle part of the mess (About Face by Hackworth would be a good first book to read on this). I could go into many details but this is probably not the forum for that. One big leadership one, though, is apropos: the 6 month tour of duty "ticket punch" for officers. For the Army at large (at least for a long time) it was perceived that Vietnam was a side show to the greater Cold War. However it was also perceived that getting "combat experience" was going to be a necessary part of one's "resume" for higher advancement. So officers would come in for a 6 six month tour ... and I probably don't have to detail how badly that worked out.
- philwelch 17y agoIn any significant engagement you're going to have a long period where you consistently fuck up and have to adjust. A healthy organization actually will adjust, though, and that's more important, because whether you get it right at first has more to do with whether you've been doing substantially the same thing recently, which for the military largely depends upon how warlike the politicians have been lately ;)
- philwelch 17y agoWhile the military is far more top-down, there's still only about 5 layers between a newish recruit and a general or admiral. A Marine rifleman at the rank of private in a deployed MEF reports to a platoon leader who reports to a company commander w.r.t. a regiment commander w.r.t. a division commander w.r.t. the MEF commander. Private to general in 5 steps--and that general commands a full task force complete with air and support units. The MEF commander reports to a combatant commander, a 4-star with authority over all military operations within a given theater. There are ten of these unified commands. (Sometimes a special command is created underneath the unified command, as in Iraq--the US Forces, Iraq command reports to US Central Command.) The combatant commander reports directly to the secretary of defense, who reports to the president. So the chain of command is around 9-10 deep for the entire US military, but about half as long for a task force. Almost as importantly, just about every servicemember knows--and can tell you--his entire chain of command between him and the President. There's no ambiguity at all. You're fully responsible for everyone beneath you, and you are fully responsible to a single person above you. It's probably impractical to organize a software company similar to the military, but militaries are very consciously attentive to organizational structure, and their organizational structure probably meets their needs more than most businesses.
- cabalamat 17y ago> A Marine rifleman at the rank of private in a deployed MEF reports to a platoon leader who reports to a company commander w.r.t. a regiment commander w.r.t. a division Have you missed out the squad and battalion levels, or is the USMC organised differently from how it used to be?
- philwelch 17y agoYeah, I missed those actually.