Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Some other military practices of interest:

The five paragraph order format: Situation, Mission, Execution, Administrative and Logistics, Command and Signals. Execution always includes the commander's intent, even if it's one sentence. The situation may change, and the lower ranks need to know the goal, not just what to do.

If you like the way the military thinks, read Gen. Krulak's brief memos from when he was Commandant of the USMC. Typical Krulak: "Marines on riot control duty will be armed. If the situation does not require weapons, it does not require a Marine."

Worth reading: "The Defense of Duffer's Drift".[1]

[1] http://www.benning.army.mil/infantry/199th/ocs/content/pdf/T...



They teach 'SMEAC' to remember this, the military is full of these kinds of mnemonics:

http://en.wikipedia.org/wiki/Five_paragraph_order

Though it's generally a bit lame to act all military outside of the military, especially if you've never served, and especially in front of serving or ex-serving members.

Seb would last about 10 seconds at USMC officer school before he learned he needs to stop being so mouthy.


"Commander's intent" and the idea of familiarization courses were two ideas I found in the Army that I think apply to Development/operations.


Another useful concept is the 1/3 rule. If something has to be done, a level of command can use only 1/3 of the time available - 2/3 of the time belongs to the lower levels. This repeats downward.

That doesn't leave much lead time at the bottom, but the military also uses warning orders - "We're going to move out tomorrow, details to follow" - to get units ready.


I've just gone through Warfighting, the USMC's military doctrine pamphlet. Well worth a read, and surprisingly applicable.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: