The Army Capstone Concept: the Army wants your comments
Brigadier General H.R. McMaster has sent to Small Wars Journal the latest draft of Army Capstone Concept version 2.7. McMaster leads a team at TRADOC that is charged with revising the Capstone Concept, which provides fundamental guidance to the Army’s doctrine and training efforts.
By December, McMaster and his team will complete their work on the Capstone Concept. Between now and then, he wants to hear from you. So please open this file, read it, and provide your comments, either here or at the Capstone Concept post at SWJ Blog. McMaster and his team will read these comments and use them to improve this important document.
(You will note that the Capstone Concept draft we received is marked “For Official Use Only.” I assure you that we received this document openly from the Army and for the purposes explained above. McMaster and his colleagues at TRADOC want Small Wars Journal’s readers to help them improve the Capstone Concept.)
First Cut, Looks pretty good.
Attached is a Word document with some initial comments / recommendations.
Wilf, I generally agree with you...
Quote:
Originally Posted by
William F. Owen
You cannot "manage" anything in war. You either react to it, or force it to do your will, by what ever means (ask nicely, ask, tell, and then force )
and I totally agree with that.
Quote:
Sorry, the idea that "The media" has changed War is evidence free. The idea that modern war is complex, is progressed by those unable to understand it.
On this, though in reverse order -- I agree that modern war is no more complex. In fact all things considered, it's probably slightly less complex than it was a century ago due to better communication and broader knowledge.
On the media affecting war being evidence free, I agree. However, I think it does affect some, say about 10 to 20%, warfighters. The rub and the perception that media affects war can come from where in the chain of command representatives of that small percentage are found. A senior commander with a fear of adverse publicity can do strange things. I have seen good senior commanders who totally ignored the media and others, less good, who were quite concerned with their image... :rolleyes:
Then, of course, there's the effect of media attention on Politicans. Those Squirrels tend to be quite media sensitive -- and they tend to have directive or budgetary authority... :mad:
he's heavy, he's my brother...
Quote:
LN349-352 Currently reads: “ Consequently, the U.S. Army must develop the capability to think in terms of friendly (partners and allies), the enemy, and the people, and possess the flexibility to secure populations while simultaneously attacking or defending to defeat and destroy enemy forces and organizations.”
Suggested change: “ Consequently, the U.S. Army must develop the capability to think in terms of supportive (partners and allies), oppositional (the enemy) and neutral (the “population”, NGOs, etc.) groups, and possess the flexibility to secure populations while simultaneously attacking or defending to defeat and destroy or neutralize (convert) oppositional forces, organizations and ideologies.”
Rationale: (I) The current wording maintains current military taxonomies (“the enemy”, “the people”) that have
caused significant problems in current conflicts. A much more flexible version of this taxonomy is based on situational motivational attitudes of groups as “oppositional”, “neutral” and/or “supportive”, a taxonomy that not only allows for but, also, is conducive of thinking that would encourage groups to shift their stance in ongoing conflicts (e.g. The Anbar Councils).
(II) Simplistic taxonomies of enemy, friendly and neutral encourage thinking by US Army forces that is contrary to the lived reality of the actual populations, sometimes producing associated “perceptions” that are completely erroneous (e.g. Of the “if they are friendly, then they will do X, Y and Z. If the don't, they must be the enemy.”).
This was the first change I was gonna suggest, but didn't have the cojones. Also Marc puts it more elegantly than I could've done.
I may get round to printing it out today...
....but does anyone else feel uneasy about a document of this nature, never using the word "kill," and only ever mentions suppression once. - so essentially it ignores the two primary methods of applying force, or choose to describe them in other ways. Hmmmm...
OK, printed it and read it twice.
It is not my intention to be needless rude of provocative here, but having been asked my opinion, here it is.
1. This document serves no useful purpose, as it stands. Doing what it intended should have taken no more 2,500 words and/or 5 pages. Having claimed not to be telling the reader what to think, it then sets out to be telling the reader that the enemy “will do X,” as opposed to “might do X, given Y or Z circumstance, and context, A, B or C.” - and where is the dividing line between Doctrine and Concept?
2. The document lacks clear and precise descriptions, and uses un-clear and highly convoluted language, none of which is helpful. - why use "new terms?"
3. Implicitly this document progresses a vision of conflict that the US Army wishes to fund, and not one based on history. It seems to serve a human and organisational need, rather than a foundation for teaching (Doctrine?).
4. The idea that the US was proficient as “old Warfare” and “new Warfare” is somehow “more complex” and more challenging is untrue, and evidence free.
5. The description is the 2006 Lebanon conflict is highly simplistic, inaccurate, selective and substantially un-true. It is what the US Army wants to believe instead of looking at the facts.
Given the above, the rest begins to fall apart pretty quickly.
As concerns capability you have to wonder about a document that never says “tank,” , and only says “Armor” twice. It says artillery and infantry each only once.
Yet in contrast it mentions :
- the V-22?
- Mentions un-manned 5 times?
- Cyber and network over 30 times?
I can only assume that this is to progress a belief in new technologies and “networks” to serve a budgetary need.
There are some very odd statements such as:
• “The future force requires the support of Joint Synergy (redundancy versus interdependencies) in certain capability areas such as fires and surveillance platforms. – I have no idea what that means.
• The future force requires the capability to conduct combined arms offensive operations and to overcome complex web defenses in complex/urban terrain. – so the US Army does not have this capability? Same capability as 1918 perhaps?
I could go on for another >5 pages, but I hope the largely negative comments so far may serve some useful purpose. There is some good stuff, but that is largely obvious to all, and there is too little of it to bother. :mad:
I guess I spent too much time in the buu-ock-rasy...
I saw all the flaws mentioned above but ignored them. Is that conditioning or what... :D
It is, broadly, a waste of time and the taxpayer's dollar -- but it is the way we do business. :(
It is, as someone mentioned, as much a pre-budgetary guide as it is a pre-doctrinal guide. It isn't a schedule and certainly isn't a map, it is an Echelons Above Reality encapsulation of syllabus. Maybe not even that, maybe a prospectus.
Having worked for a few years at that level, I can thus ignore the flaws and realize that it is to lay the groundwork for doctrinal revamp that is aimed probably far more at the civilian side of government than it is at working Soldiers. Considering the raw ignorance among many in and working for Congress. Particularly dangerous are those with five years or so of service who think they know the system but really do not and are now staffers and exercise baleful influence on the many more with no service...
It is also designed for the proliferation of Think Tanks filled with academics with little or no experience. It will give them things to mull and prate about. Then there's the clueless media who need elementary guides... :wry:
The Army used to be able to write tight, clear and very concise documents and publications. It ceased doing that in the late 70s when masses of civilian Educators were hired into all the TRADOC schools and that unintentionally adverse influence became just that only because they caught the post-Viet Nam Army in a state of flux and angst and flapping about. They meant well, were some smart and hard working folks but they sold the Army an extremely poor industrial training system that is totally inappopriate for a professional force and they created a syndrome that believed volume was a substitute for quality of content in writing.
So look at it as a sales brochure for the layperson. ;)
Problem-Solution Framework
In lines 427 through 436, the authors present three components to the framework analysis they used, which make up the military “problem” to be solved.
In lines 454 through 482 “Iraq from 2003-2009” is used to illustrate a hybrid threat, one of the challenges guiding the framework analysis toward solutions. This section focuses more on what the insurgency “got right” then what the U.S. forces got right. It seems a valuable exercise to look at how the insurgency was successful. On the other hand, it’s even more valuable to look at examples of what the U.S. forces did right and how to appreciate in value the efforts that worked well. Where are the positive examples of what the Army did right, which we want to see more of in the future, to appreciate in value that which worked well?
The authors present the “solutions” to the military “problem,” and I’d like to read more of how they arrived at these solutions based on what worked well in the past, instead of just based on the identification of problems from the past and the probability of future challenges.
I’ve been reading, studying, practicing, and learning more about the Appreciative Inquiry method of organizational development. Instead of framing concepts as problems and solutions by looking backward at what went wrong or what didn’t work and trying to “fix it,” the idea of Appreciative Inquiry is to discover and move towards what is going right. The idea is to encourage and embrace what works.
“In problem solving it is assumed that something is broken, fragmented, not whole, and that it needs to be fixed. Thus the function of problem solving is to integrate, stabilize, and help raise to its full potential the workings of the status quo. By definition, a problem implies that one already has knowledge of what "should be"; thus one's research is guided by an instrumental purpose tied to what is already known. In this sense, problem solving tends to be inherently conservative; as a form of research it tends to produce and reproduce a universe of knowledge that remains sealed” (Cooperrider & Srivastva, 1987, http://www.stipes.com/aichap3.htm).
I don’t mean to take issue with the whole problem-solution framework of the capstone. It’s probably not something that can really be changed at this point. I just wanted to point out that possibly adding to the document more positive examples of what worked well in the past could guide the future concepts and provide more support for the “solutions” presented (this is my main idea, so I put in boldface type).