A NYT piece about how the Army is using wikis to write doctrine made the rounds on a Gartner analyst e-mail DL today.
Doctrine is supposedly doctrine because the principles it teaches age slowly. So, is a wiki the right vehicle for maintaining doctrine? I imagine the colonels who really write the Army’s doctrine must be chewing up their cigars and spitting ‘em out after reading this piece.
The Navy and Marine corps have always looked down on written doctrine — one of my favorite sayings attributed to a Navy admiral is: “Doctrine is guidance to be followed in the absence of any other intelligence, including human.”
The sea services looking down their nose at written doctrine is not merely services rivalry; rather the Army has tended to put too much in the way of operational procedures and instructions in its doctrine — in fact, if doctrine is considered to be a set of core beliefs or principles, most of what is in Army doctrinal manuals is not doctrine. The Marines have doctrine too — for instance “every Marine is a rifleman.” But try finding a 100 page doctrinal discussion of that — it doesn’t exist — never has.
The Army saw the failures of doctrine in Iraq, and how the gaps were filled by social networking. To the Army’s great credit, they learned the lesson and then brought the social networking in-house and have supported it.
So — what we may be looking at in the Army is the end of doctrine as training manuals, procedures and instructions — expeditionary warfare requires that those be changed more often than the Cold War system can support — so doctrine exists, but it is stripped of the operational procedures which much change rapidly.
What’s left as doctrine are the core principles of operation — not procedures. Perhaps unfortunately, the sea services have adopted the “doctrine” word in recent decades, but on the other hand, they seem to have stuck to core principles of operation when they use the term — compare this Marine Corps list of doctrinal publications to the Army list. See the difference?
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.