It's fun to think of our businesses as just like a Seal team and try to glean lessons from stories of heroism, but the reality is if the military were in the business of making a profit, retaining employees, or pleasing customers, it would fail miserably.
The reality of the U.S military is far different than the impression that the leadership papers give you.
As an enlisted infantry Marine who transitioned very easily into software engineering, I find my leadership training in the Marine Corps a distinct advantage I have over my peers. I have been called the best manager other engineers have ever had by multiple people, as well as called the best engineer many have worked with.
The only thing I wish is more people understood what true leadership looked like, and that is one thing I generally have missed from my time in the Marine Corps. The principles are probably some of the best set of general leadership principles you can find out there and they prove their worth day in, day out.
To set the record straight, Van Riper exploited deficiencies in the nature of the simulation itself as opposed to finding actual deficiencies in Navy doctrine.
For example, the small boat armada armed with missiles could never, in real life, physically support the missile systems used or even power the necessary controls. He used messengers on motorcycles that would effectively teleport from Point A to Point B, again an impossibility.
So the Navy hit reset on the exercise and asked him to please stick to reality instead of attempting to exploit the rules of the simulation.
As a hacker I have to chuckle at his exploits. As a taxpayer I'm a bit pissed that he not only wasted time and money, but then went on a media campaign to malign the folks running the event because he was angry he didn't get away with his clever hack.
Please stop spreading this as some sort-of "Look at how pitiful the military is!" stories. It is absolute bullshit.
There is a brief Reddit thread with sources available. The initial post sources DoD transcripts of a post-exercise interview, and although this doesn't go into the missile weight issue it directly mentions that active air defense was turned off on the real-world ships in the simulation and they were unrealistically geographically constrained due to rules about shipping channels as they were operating in active, crowded seas.
Regarding the issue of unrealistic missile weights, please read the "rebuttal" and subsequent discussions regarding why the missile setup was unrealistic.
Note: At the time of writing, I freely admit I am unable to source a reliable entry on the motorcycle teleportation bit, so I may be mislead on the matter. I have to get back to work, but will provide more additional sources if and when I can find the time.
 - https://www.reddit.com/r/CredibleDefense/comments/4qfoiw/mil...
 - http://archive.defense.gov/Transcripts/Transcript.aspx?Trans...
 - https://www.reddit.com/r/CredibleDefense/comments/4qfoiw/mil...
> because I can't just take your word for it.
I have to take a moment to point out that you have not provided an authoritative reference for your claims. The Wikipedia entry itself merely cites newspapers quoting Van Ripper, and doesn't even mention criticisms which seems rather suspect. In fact, there is a giant warning at the top of the article stating that the neutrality is suspect.
The non-reddit reference you have provided points to a transcript from 1999, it looks like it's an incorrect link.
I couldn't examine the reference mentioned in the reddit post either, since the web page doesn't open, but there seems to be some disagreement on reddit regarding the topic itself.
Newspapers quoting van Ripper are one of the best sources we have access to, unless the military published an official account.
I've resigned over unrealistic expectations from leadership about deadlines, and what was to be asked of my team to complete said deadlines. I would do it again. I'm sure I've had many many many failings as a manager, but I will not death-march any team under me with zero chance of success. There are several others in the GP's post. You are correct, they don't all apply and many may be harmful in a corporate environment, but that's why you get paid to separate the wheat from the chaff, right? :)
This sets great example. Thank you.
The team was not asked to pull any overtime to complete it in the proposed time frame.
I took a 6 month sabbatical and then was asked to contract for them remotely as a developer (instead of manager) which I did for several years after that.
So, wins all around, I suppose.
Military leadership has the extra ace up its sleeve that all the people reporting to you are bound by law to do what you command.
Leading Civvies is like herding cats by comparison.
"In the civilian world, you think that in the Army you can just order someone to do what you want. In the Army, you think you can sack whoever you choose in the Civilian world."
I'm curious why you have that impression. I spent 6 years in the Marine Corps Infantry and I've found it super helpful now 6 years into my career as a software developer. Specifically, because of the leadership style you learn.
The only thing I'd say it made it more difficult to adapt to was college where I had to interact with a bunch of kids with no life experience and lots of strong opinions about how the world does and should work.
Is that because of management issues or because of the intrinsic issues that come from being in the business of killing people to gain land, resources, power, or whatever?
Obviously, the job is stressful all in itself. While I did not go to combat myself, I have lost friends, I've delivered flags to families of Marines who fell in combat, and have also just had a lot of beers with friends who could not cope with some of the actions that they had to endure in combat.
Secondly, management is certainly an issue like any other company. I won't go in lots of details here, but for half of my enlistment, I loved my leadership as they pushed me hard and helped me grow. They very clearly wanted to make me a better Marine and person. They were as close as family to me. They were very balanced. They knew when to be be hard, and when not to be. On the other hand, for the second half, It was the complete opposite and my time was miserable.
I experienced similar things in the private industry, only with much less physical labor. :)
Especially in the case of Marines, if you have a very well defined objective that requires brute force to solve, that's the ideal situation for them and they'll do amazing things. Anything that's a gray area, not covered by rules, or that requires creativity or questioning authority... It's not going to end in a good result.
I can't count the number of times Marine officers did ridiculously inefficient or plain stupid things because an authority figure or regulation said so. Usually the justification was, "the rules are there for a reason," or something similar. Whole that might be true, the idea that someone in authority can, in advance, create a set of rules that we can blindly follow to a successful outcome is insane for all but the most desperate situations.
Most of the military was like that to some extent.
I can think of two redeeming qualities for such sets of rules, if applied and understood correctly:
1. Eliminating indecision. If figuring out what to do is too difficult (or none of the options are better than others), you have a somewhat sane defaults to fall back to. Indecision has costs too.
2. Making things more predictable upstream. Authorities may make up some rules that may not be most effective when applied by the bottom line, but they normalize the entire bottom line, making it easier to manage. This is similar to what we do with frameworks in software - we trade efficiency and flexibility for consistency, in order to build an abstraction layer that's less complex to work with. Misapplied, this of course leads to tragic/comical examples, both in organizations and in software (e.g. Electron).
You could argue that this has in fact been the reality of late...