Showing posts with label Gian Gentile. Show all posts
Showing posts with label Gian Gentile. Show all posts

Monday, September 24, 2012

Afghanistan strategy three-fer

I haven't been writing much on anything other than veterans issues lately and for good reason. This has been the result of my increasing interest in the problems facing veterans and the policies that attempt to address those problems. But this increasing interest also coincides with an interesting turn in dialogue on conflict these past few months where writing has generally dug existing positional trenches deeper instead of progressing the conversation, such as with Syria.

That said, with the official end of the surge in Afghanistan last week, a few interesting pieces about that war were published in the past week that you should be aware of. I'll add some commentary at the end of this post, but these three are interesting in that they all address significant flaws with our strategy in Afghanistan from different perspectives.

Frances Brown: The U.S. Surge and Afghan Local Governance
This USIP report (linked to by Josh Foust) is an excellent and erudite review of our local governance efforts in Afghanistan since 2009. Importantly, this review is analyzed through the context of the strategy put forth by the Obama administration in late 2009 which elucidated as its goal "to disrupt, dismantle and defeat al Qaeda in Pakistan and Afghanistan, and to prevent their return to either country in the future." Brown, who has extensive experience in-country, goes on to quote the "Integrated Civilian-Military Campaign Plan for Support to Afghanistan" which states that to "promote a more capable and accountable Afghan government" is essential to the strategy of disrupting, dismantling, and defeating al Qaeda. More on that later, but even if were to assume that this is the case we screwed up implementation of the governance plan.

I've written before about the importance of assumptions during planning. Brown lays out three assumptions that were, in her words, unrealistic with regard to local governance:

  1. Governance and development timelines would mirror security progress;
  2. Bottom-up progress would be reinforced by top-down progress; and
  3. "Lack of government" as the problem to be addressed.
She picks each of these assumptions apart point by point to the extent that you wonder how it's possible anyone created these assumptions in the first place. The hints of derision throughout the paper also makes it quite readable (I especially recommend the paragraph on Marjah on page 6 as an example). Brown ends the paper with three recommendations:
  • Exert leverage to impact select systemic, rather than tactical-level, problems.
  • In a resource-constrained era, prioritize assistance to a few key efforts.
  • All the usual Afghanistan governance recommendations still apply. 
There are plenty of details beneath the lists. If you're curious as to why our local governance efforts haven't worked in Afghanistan, I highly recommend you read this paper in its entirety. 

Jonathan Rue: Auditing the US surge in Afghanistan
Rue, who hangs his hat at Gunpowder & Lead, had this piece published in The Guardian. Rue is an exceptional military analyst and always worth reading - especially for a Marine (I kid!). After discussing events over the past couple of weeks, of note the attack on Camp Bastion, he states that it's difficult to measure success in Afghanistan. On one hand, U.S. forces have achieved gains at the tactical level. On the other hand, those gains haven't affected our strategic ends. This is the same problem we faced when we left Iraq: superiority on the battlefield was ineffectual towards our goals. As Rue notes towards the end of his piece, this is the same problem we had in Vietnam as well. He doesn't talk much about why this is the case (it is the Guardian after all), but his quoting of SECDEF Panetta is indicative of a government that still does not understand insurgency or counterinsurgency even after 10 years of war:
Secretary of Defense Leon Panetta claimed the latest attacks were merely the "last gasp" of a weakend Taliban. If the aforementioned actions are the hallmark of a dying insurgency, I'd hate to think what actions characterize on on the ascendency.
Indeed. Rue is also right that maybe the best news about the surge of troops is that it's over and they're now home. 

COL Gian Gentile: War: Sometimes there is a substitute for victory
In the Jerusalem Post, Gentile picks apart the famous (at least to West Pointers) MacAurthur quote: "There is no substitute for victory." He notes that sometimes "winning" wars isn't worth the cost required to do so. Gentile is well known for his anti-counterinsurgency (of the nation-building sort) writing and he uses this piece to take a swipe at the current strategy. He notes, much as Brown and Rue have, that while trying to defeat a decentralized terrorist organization the United States has set as its goal the building of a nation-state in Afghanistan, an approach that has not worked thus far. He says:
Today in Afghanistan the effect of the American military's embrace of and belief in the efficacy of armed nation building, with its never ending stream of statements of progress, has obscured the vast amount of blood and treasure invested in a military methodology that has not produced results. Yet still we hear the calls to try harder, stay a bit longer, and keep the faith that it will all turn out right, because in war there is, as they say, no substitute for victory.
I think those calls are becoming few and far between at this point in the war. We have a plan of sorts to withdraw from Afghanistan in the coming years and I doubt that anything will derail that plan. Gentile focuses too much on the military ways that our generals have decided. In his oft-repeated attacks on armed nation building, he seems to focus in on this aspect of strategy formulation and not on the political determinations of ends and means. If we were to take the President's statement of ends literally (disrupt, dismantle, defeat al Qaeda), we could probably declare the war over and probably could have years ago (Gentile does say this). 

Gentile is right in calling out military leadership for not correctly aligning ends-ways-means, but he gives the political leadership a pass for not controlling the military more effectively and exercising their constitutional and precedential prerogative. Is that not the lesson learned of the famous MacAurthur vs Truman conflict he uses to set his argument? Nits aside, Gentile has valid points that speak loudly on the failure of our strategy. 

Strategy, strategy, strategy
The recurring theme of these three works is that the United States has had a serious strategy problem in Afghanistan. We haven't aligned ends, ways and means and the assumptions we've used for that analysis was off to begin with. This is not how great powers plan for success, which becomes infinitely more difficult if we can't even define what success means. Policy-makers who should define ends and means have not done so. Military strategists and leadership have chosen ways that certainly do not align with the ends that have been stated and have not likely used the means available as effectively as possible. 

Another important theme throughout is the equivalence of tactical and strategic success, a trap the United States has been prone to since at least Vietnam. I've argued here before that all strategies are in part a summation of tactics used to achieve strategic ends. But the "in part" is essential to understanding the connection between strategy and tactics. Tactical gains and successes do not create strategic successes and gains on their own. There are other variables that when added to tactical gains creates strategic success and we haven't yet identified what those are (and logically haven't figured out how to address them). A lesson seemingly lost in Afghanistan. 

Anyway, go read these three excellent pieces by three very smart people about a ridiculously hard problem. It's definitely worth your time. 

Friday, February 10, 2012

Strategy is intelligent design and willful, intended action

I've recently become acquainted with a principle of constitutional law called the rational basis test. When a questionable law is subjected to legal challenge, it must first clear this very low hurdle: the court must be able to conceive of a plausible way in which the law's enactment could serve a legitimate interest of the government. The government isn't required to testify as to the legislature's purposes, and the law need not even be effective in serving the stated interest—it simply needs to be a plausible attempt. In short, the court must find that the government has behaved rationally; whether or not it has behaved intelligently is a separate – and for the purposes of the rational basis test, irrelevant – question. This strikes me as a good place to kick off a conversation about strategy and tactics.

Strategy is intelligent design: the reasoned application of available resources in a rational way, offering a plausible, logical path to the accomplishment of our goals. Clausewitz defined it narrowly as "the use of the engagement for the purpose of the war," but in the modern era its use has broadened to apply at nearly every level; "strategy" now essentially means something like the willful use of activity and resources to accomplish specified ends.

By this standard, strategy can be applied at all levels of war—not just the strategic. (Bear with me; I know this gets a little confusing.) One can have a generalized strategy for success in certain types of tactical engagement; this is frequently manifest as a set of procedures, the sort of thing that immediate action/battle drills are intended to perfect—performance of the required actions for tactical success. But to call this a "strategy" is a little misleading, if only because it obscures an important reality: at the tactical level, we're talking not about the reasoned, case-sensitive, tailored administration of resources and performance of planned actions to meet unique objectives, but a somewhat more mechanical application of accepted prodedures and best practices. This is the stuff of doctrine, which sets down a military organization's authoritative, collective view of how it conducts specific missions or types of operations. Doctrine's value is that it can be considered and codified in the abstract, as its tenets are presumed to be somewhat generalizable across a range of roughly similar conditions.

Moving up the levels of war, one can also have a strategy for operational or campaign success: how various tactical engagements will be combined to achieve campaign objectives. There is, of course, more art to this than at the tactical level simply because there is more uncertainty and more choice. No two tactical engagements are precisely the same, but it's much simpler to identify general "rules" for success when confronted with an L-shaped ambush than to prescribe methods for translating battlefield success into operational progress. No two campaigns are the same. It is at the operational level that strategy begins to take on the meaning with which we're familiar: a general idea of how we hope to use operational mobility and battle in phased, sequential actions to achieve goals within the broader framework of the war, while accepting the need for flexbility and adaptability in response to the enemy and war's fundamental unpredictability.

And then we come to the familiar strategic level of war, where campaigns are sequenced and combined to achieve the political objectives of the combatants. Here we see strategy from a slightly different angle: as the ways that the means of military action are applied to achieve the ends set out by policy. Let me explain this a little more.

The various levels of war are overlapping and nested within one another, and within the overarching framework of policy. Often the ends of the lower level serve as the means of the next-higher level: that is, tactical success is a means (to be combined with other means along various lines of effort) to achieve operational objectives, which are then used as means to be translated through operational art into strategic success. This means-ways-ends construct – reasoned activity conducted to produce conditions which are manipulated and exploited by yet more reasoned activity as we ascend the levels of war – is the very essence of strategy. Planning is strategy worked in reverse—beginning with a desired end, identifying objectives that will enable and facilitate this end, planning campaigns and operations to attain those objectives, and allocating resources, capabilities, and tactical actions in line with those plans. This construct can be extended even further into the development of capabilities: an armed force can have a strategy for manning, training, equipping, organizing, and so on to deliver the capabilities required for tactical, operational, and strategic success.

Effective tactical actions must be combined in rational ways to achieve operational ends.

Successful operations must be combined in rational ways to achieve campaign objectives.

Meaningful campaigns must contribute in rational ways to the satisfaction of strategic goals.

And the accomplishment of strategic goals should rationally lead to the enactment of policy's ends.

The fabric that holds all of this together is strategy. And it follows that strategy must always involve what we call a theory of victory: at every level, the actions we choose to take must form a plausible narrative that leads to the accomplishment of our objectives and enables the next element of the overarching plan. The strategist must continually ask himself not only to what end?, but how?

As I noted above, the so-called theory of victory is more empirical – almost mathematical – at the level of tactical action. My forces will do X, Y, and Z to produce effects A, B, and C. Operational-level doctrine, too, suggests a certain institutional confidence in an accepted way of doing business, how tactical actions can be combined to create successful campaigns. But it is at the strategic level that procedures and doctrine mostly lose their value, giving way to operational art and strategic theory. Just the same, the strategist must begin with a clear idea of how it is that he hopes to achieve his goals through directed action—a theory of victory.

To come to the point of all this: Jason wrote a post earlier this week in which he considered the validity of Gian Gentile's repeated claim that counterinsurgency as practiced in Iraq and Afghanistan is a "strategy of tactics." Carl is right to point out in the comments that the good colonel did not invent this construction, though there's a ring of sophistry to his claim that it "predates Gian Gentile by decades and has been bandied about by a Who's Who of strategic savants."

The phrase did indeed originate with Andrew Krepinevich, whose 1986 book The Army and Vietnam described Westmoreland's approach as a "strategy of tactics." This went hand-in-hand with the argument that the U.S. fought that war in line with the "Army concept"—a set idea of how war ought to be fought that springs not from strategic logic but rather organizational imperative: what the Army mans, organizes, and trains to do. LTC D.W. Beveridge paraphrased Krepinevich's argument (enormous pdf) in asserting that "the upshot of viewing the war in terms of the Army Concept was a preoccupation with 'grand tactics' rather than strategy, resulting in a perpetuation of the search and destroy operations imposed on the ARVN [South Vietnamense Army] during the earlier advisory period" (89).

This complaint is reflective of the flaws of the incrementalist approach in Vietnam: as the U.S. commitment increased and the correlation of forces (between U.S., ARVN, North Vietnamese Army, and VC/NLF) shifted, American commanders failed to re-assess the strategy being employed and consider a change in the role of U.S. forces. Westmoreland had been convinced that large NVA formations posed the greatest threat to South Vietnam, so he built a strategy focused on the use of American firepower and mobility to find, fix, and destroy them. In short, he misperceived the political nature of the war and suffered the consequences.
But Krepinevich's complaint about Westmoreland's "strategy of tactics" in Vietnam rings slightly hollow. A more accurate description would recognize that Westmoreland had a rational strategic plan and a sense for how American forces could be tactically employed to achieve it, but lacked a theory of victory: that is, he had no concept of how tactical action by U.S. forces could create strategic success because he permitted an essential element of his campaign plan – pacification of the South Vietnamese countryside, which was left to the ARVN – to exist outside his control. He seemed not even to recognize that the effective accomplishment of this mission was essential to strategic success. Westmoreland had too much strategy and not enough sense of how it would be accomplished. After the Battle of Ia Drang Valley, he had effective, proven tactics with which to destroy the NVA in the South but no concept for how those victories could be translated into political success.

The story with COIN (specifically in Afghanistan) is quite different: the campaign plan there has plenty of "theory of victory," but there's room to question whether or not it is plausible—that is, whether or not the tactics prescribed will actually produce the effects they're meant to. U.S. commanders have a clear idea of what they mean to accomplish and how, but there is far less certainty over whether the available tools are suited to this approach. It is plausible that the pacification of towns and villages, expanding territorial control in the countryside, reductions in violence, and increasingly effective Afghan governance and security forces will create an environment that is inhospitable to insurgents, one in which the enemy cannot sustain himself, and eliminate the possibility of extremist safe havens. This is a rational concept. The problem is that we're not sure our tactical actions can actually produce these effects—that is, we're not sure our resources, personnel, units, and capabilities can be combined along the lines of effort specified in doctrine to actually do the things that need to be done. This is the very opposite of Krepinevich's problem with Vietnam strategy.

As a peripheral but related note: it strikes me as very unlikely that Gentile adopted the "strategy of tactics" construction from Gray, whose use of the term is limited to approving references to Krepinevich. (The same is true, I think, of Owens.) In fact, the argument that Americans are or were ineffective counterinsurgents owing either to an unsuitable strategic or military culture (Gray) or misdirected doctrinal emphasis (Krepinevich) is one that Gentile rejects. He reads Brian Linn's The Echo of Battle as describing a "better way of American war" in the historical culture of the Army, one that is defined by "improvisation and practicality." (This has is apparently being thrown out, Gentile tells us, in favor of "the American Army's new way of war, otherwise called population-centric counterinsurgency.")

COL Gentile's fundamental inconsistency is here exposed: he rejects Krepinevich's critique while mirror-imaging it. He asserts that doctrinal bias and intellectual inertia have determined our strategic course in Iraq and Afghanistan while rejecting the very idea that our Vietnam strategy was shaped similarly. Gentile has cribbed Krepinevich's phrase while rejecting the very substance of what it means; this, he seems to be telling us, is actually a strategy of tactics. What Krepinevich was describing was a failure of strategy, but not the same kind!

I happen to share COL Gentile's conviction that both the Vietnam and Afghanistan (at least post-2002) wars were and are strategically senseless, which is part of the reason I'm so troubled by his insistence that the deus ex machina of "the American Army's new way of war, population-centric counterinsurgency" is what's responsible for our national foolishness. The strategy may be a poor one, and I think that it is. That's not because it lacks a theory of victory, though – i.e., because it's simply an assemblage of uncoordinated tactics – but because we aren't sure that the tactics are effective. If I developed a campaign plan to liberate Syria from the Asad regime by the destruction of its military through happy thoughts, text messages, and pictures of rainbows, the appropriate criticism would not be that I had employed a "strategy of tactics" but rather that my strategy was dependent on unproven and ineffective tactics. And don't get me wrong, COL Gentile levels this criticism at modern COIN doctrine, as well. "COIN doctrine directs an operational method based on uncertain causality and tactical actions of questionable effectiveness" may not roll off the tongue quite so easily, but it's much more accurate than this "COIN is a strategy of tactics" trope.

Monday, February 6, 2012

be-SoT-ted: COIN tactics and strategy through the lens of ends, ways, means

The last year or so of the COIN debate has seen a modicum of consensus that COIN is a strategy of tactics, a concept that I can attribute first to Gian Gentile (unless someone has another, older source for the statement). Gian has written about here, here, and to an extent here (.pdf, starting on page 21). And plenty of other places and by plenty of other people. I've even used the term myself from time to time. But lately I've been questioning the validity of this point of view.

My main beef with COIN as a strategy of tactics (I'm going to go ahead and call it SoT from now on) is that all military strategy is made up in part as a summation of its tactics. In the ends-ways-means calculus of strategy, a large chunk of the "ways" section is the aggregation of tactical actions based on operational concepts and/or TTPs. For example, the strategy for the invasion of Iraq (flawed as it may have been) was Ends = regime change; Means = 180K troops or whatever it was, organized as it was; and Ways = at least partially the cumulative maneuver (air, mounted, indirect, dismounted, etc) tactical actions executed in a sequence that creates the desired Ends. This is an elegant way of saying it, but all military strategies are in part SoT, in a non-pejorative sense. You can't have strategic success without tactical successes. COIN, IW, UW, maneuver warfare are all common in this regard.

There's a bit of a semantic argument in all of this as well, better made by Gulliver than myself, especially on the pervasive use of the term strategy as a synonym for "plan" instead of the ends-ways-means construct. All around we need to clean up how we use terms that have meaning. In spite of using the term often, I've never read Gian use ends-ways-means to make the pejorative SoT argument, which I think is a shame as that's how we conceptualize strategy in the U.S. My initial instinct is that if ends, ways, and means are not aligned (ends are not achievable, means are not enough, ways not the right tool) then you run into a true SoT problem. Afghanistan may be a good case study for such a label - commanders focused on a set of tactics (ways) that may or may not be capable of achieving (arguably) already un-achievable ends, not least because the means they were given weren't enough to use effectively wage the ways they had already determined. So yeah, in Afghanistan COIN probably is a SoT due to the misalignment of strategic elements.

On the other hand, Iraq may be a study in COIN as element of a proper strategy. Ends were reasonably achievable, means were adequate given the population density of Iraq, and the ways were universally applied to the lowest levels. Whether by design or luck, the Iraq military strategy in 2007-08 seemed to align. COIN tactics were a major element of the ways used, although COIN in a population-centric sense did not encompass all of the tactics used during the Surge. Iraq seems to be an example not of COIN as SoT, but a military strategy (ends-ways-means aligned) that contained COIN tactics as an element of ways, but also included CT tactics and maneuver/conventional warfare tactics, as well as non- and quasi-military ways associated with taking advantage of the plight of the Iraqi people and the Sunni shift in allegiance that started before the Surge.

I realize I'm just scratching the surface of this topic and have simplified a few concepts here. Hopefully I'll find the time and grey cells to explore this more - hopefully with your help. But for now I disagree that COIN is inherently a strategy of tactics any more than any category of tactics can be labeled a strategy. Those tactics may be part of a military strategy that logically connects ends, ways, and means. On the other hand, COIN tactics may be the commander's ways in an illogical or inaccurate strategic equation and thus we may see COIN as a SoT. One can take issue (and many have) with commanders choosing pop-COIN as their ways irrespective of their ends and means, but that is different from declaring COIN itself a SoT. The fault lies with the men and women in command who use COIN when they shouldn't, not with a set of TTPs that may be useful in other circumstances on other days.

Friday, February 11, 2011

Karl Hack on Malaya and counterinsurgency

After last week's post and the brief discussion that followed it, this could not have come along at a better time: "Setting the Record Straight on Malayan Counterinsurgency Strategy: Interview with Karl Hack" at Small Wars Journal.

I hate to keep hinting at a big, earth-shaking post that I keep not writing, but this bit in particular just absolutely nails something that I think is absolutely essential to understanding COIN in a broader context and to talking and writing about it in an accurate, honest way:
Yet for counterinsurgency, people do sometimes ask ‘what is the one key ingredient’? The answer is, menus do not work like that, and neither did the Malayan Emergency. There were distinct phases or stages. I would argue that many other insurgencies are also likely to have distinct stages, and indeed that within a single insurgency different provinces or regions may be at different stages at any one time. It is quite possible that Helmand and Herat, Kandahar and Nangarhar, could simultaneously be at very different stages, requiring very different policies.
The question above, therefore, encompasses what I would like to dub the ‘temporal fallacy’ (that policies abstracted from one defining moment might be equally valid in qualitatively different phases), and the spatial fallacy (that different geographic regions will be in the same phase, so allowing a single strategy for a country no matter how fractured and diverse).
Much popular writing and most military messaging about counterinsurgency is guilty of both the termporal fallacy and the spatial fallacy; whether this is a matter of disingenuous manipulation of public and political opinion or innocent but misleading oversimplification is still something of an open question.

Thursday, August 26, 2010

Old Tanker Syndrome

"Mostly Dead" must describe the horse it was beating - or so I thought. But alas, it is another post-mortem on the Armor Corps. Granted, LTC Weiss seems to fall somewhere between COL Gentile and MAJs Smith and Harbridge when it comes to his thoughts on "how dead" the Armor Corps really is. But this is still what I'm starting to call "Old Tanker Syndrome" (and yes, I noticed that LTC Weiss is an artilleryman) - or OTS.

OTS seems to cause those it afflicts to see the Armor Corps through the lens of their pre-Iraq experiences, when NTC was king and careers were made out of the brigade breach into the Northern Corridor. I'm not going to call it nostalgia - I don't think Gian is nostalgic - but their formative years in the Army were defined by these realities. I think that the biggest symptom of OTS, though, is a pre-GWOT conception of combined arms operations.

For these older field grades with OTS, combined arms operations are those brigade breaches and large maneuver formations - both Gian and LTC Weiss refer to them as lost capabilities. I have to say, as a former company grade, that I take umbrage at that. Tell any lieutenant or captain who has lead in Iraq or Afghanistan that they don't understand combined arms operations because they've never done an old school breach or brigade live-fire. Go ahead. I dare you.

Or maybe these young officers know combined arms better than their superiors - or at least more advanced at younger grades. They know how to work with host nation forces, call in fixed- and rotary-wing fires, artillery, and work with dismounts (conventional and SOF) and mechanized forces. Simultaneously. As lieutenants. If that's not "combined arms" then I don't know the meaning of the term.

And let's take a look at this focus on brigade and above operations. Do both of these experienced officers really believe that younger officers are "unschooled" in combined arms because of the nature of decentralized counterinsurgency operations? Both current theaters have plenty of examples of large-scale, combined arms operations - but just because the unit's front is more circular than linear doesn't dismiss the fact they are brigade-level operations. Further, employing weapons systems in this manner requires greater understanding of their capabilities because of the greater risk of fratricide.

Even during the invasion of Iraq, which was a corps-level operation, all I ever cared about was my commander's intent two levels up, my mission, and the missions of the units to my left and right. After the invasion, nothing changes except I now had to worry about what the units to my front and back and indigenous forces in the AOR were doing. Decentralized operations are the same in high- and low-intensity conflict. Even at NTC, I couldn't tell if we were doing a company or brigade operations, except that latter had three times as many observer/controllers wandering around. It doesn't matter to a company-level officer. Just as experience at corps-level operations isn't a prerequisite to effective leadership of battalions.

What I'm trying to get at, in a verbose way, is that today's younger officers are probably the most tactically competent officers our nation has seen in a long time with regard to maneuver and combined arms operations. Where I'll agree with Gian and LTC Weiss is that technical skills such as gunnery have atrophied - but this can be easily remedied. But the fact remains - the principles of warfare are the same for COIN as they are for HIC and our junior leaders are very, very good at executing those principles. So let's just stop with this "Armor is dead" leitmotif - it's not, nor is it endangered. Don't let OTS jade your perception of the quality and esprit of our Armor Corps. Please.

Wednesday, August 18, 2010

Gian Gentile on CFR's website

Col. Gentile is currently a Visiting Fellow at CFR and to start off his time there with a bang, he did this interview with their consulting editor. The interview is titled "Conflicting Objectives for US in Afghanistan."

This is the intro bit:
General David H. Petraeus, in his first extended public interviews as chief U.S. and NATO commander in Afghanistan, made news over the weekend when he argued against a hasty withdrawal of U.S. troops in July 2011 and expressed optimism that an achievement of the U.S. objectives there is possible. But Colonel Gian P. Gentile, a visiting CFR fellow who heads West Point's military history program, says there is a mismatch between U.S. President Barack Obama's limited political objectives in Afghanistan, which could be accomplished in some eighteen months, and the U.S. military's "operational objectives." These objectives are "euphemistically called counterinsurgency," he says, and could take a generation to achieve. "We have the means to tactically and operationally achieve success in Afghanistan," says Gentile, but "we become mired in the tactics and operational methods of doing counterinsurgency."
I didn't know COIN was the same thing as "nation-building" but I guess you learn something everyday. The argument does strike me as a bit muddled though. Anyway, go and read it and then come back here and argue (and yes, I'm having a particularly slow day at the office).

Friday, June 4, 2010

More on the future of the Armor Corps

This week saw a minor resurgence of the "death of Armor" motif through a paper on SWJ in response to COL Gentile. I found the discussion somewhat interesting if not really a rehash of the common themes to this topic between a number of SWJ regulars and fellow Spartan Brigade alumni. There was one comment that I think really sums up the danger facing the Armor Corps, from a great officer and commander who I had the honor of serving with at Fort Stewart, Mark Battjes. Here is most of his comment:

Do we have now in the Armor branch, or heavy portion of the Infantry branch, the junior leaders (SGTs, SSGs, SFCs, LTs, and CPTs) who know how to train to conduct heavy combined arms maneuver?

I worry less about whether we will be able to train 18-24 year olds to be able to hit targets with an M1 or M2. I worry far more about whether or not a SSG can develop a plan to train his section to not only shoot gunnery, but also conduct mounted maneuver.

My own experience as a company commander training a company to shoot gunnery for the first time without significant training experience in my formation (1 x SFC MG and only a handful of NCOs who had ever shot gunnery) is instructive. We got through it with brute force and ignorance, but it was a lot more painful than it should have been. The results are instructive as well. We qualified everyone on Table VIII reasonably well, but the Table XIIplatoon qualifications were much more difficult, primarily because none of the NCOs, and certainly not the LTs, had learned how to train to conduct mounted maneuver. They know how to train a squad to enter and clear a building or conduct a dismounted patrol.

Overall, I agree with the authors' point that the Armor corps will ultimately survive and thrive. However, it will require the active efforts of BN CDRs and S3/XOs with significant training experience to show a lot of young CPTs, LTs, and NCOs who are long on combat experience, but short on training experience, how to go about training a tank platoon or scout platoon. Somehow we have to rebuild the training capabilities of our junior leaders, something that we were very good at before we had to quickly train up for repeat combat tours.


I couldn't have put this better myself. As Iraq and Afghanistan wind down, this should probably be the number one focus of the Maneuver Center of Excellence.

Tuesday, April 20, 2010

The Combat Arm of Decision

I'm sure most of you have read Gian Gentile's latest at SWJ on the death of the Armor Corps. I don't intend to dissect the entire paper here, but I do want to talk about a couple of points.

Gian is absolutely correct that today's mechanized force does not know how to do a combined arms operation at the brigade level (he mentions division, but I'm not so concerned with that - I'm not sure what that would even look like). Now, being a cavalryman, I have no time or patience for breech operations - I'm more of a bypass, re-gas, haul ass kind of guy - but you older tanker folks know how hard a battalion/brigade-level obstacle breech is. If you think COIN is graduate-level war, a brigade breech is something closer to post-doc. And we don't train it anymore at NTC with live bullets like we used to. If I recall correctly, my brigade was one of the last to do it and that was back in 2004 sometime. Someday, somewhere, the U.S. Army is going to have to do that and we won't be prepared for it.

Gian is also partially correct on individual crew skills. I think that gunnery skills are important for tank and Bradley crews and it's true that we don't spend the time we used to on those skills. On the other hand, tank platoons are doing what they can to prepare their units for combat. Rest assured, the M1 series tank has been used quite a bit in Iraq. In 2008, one of my favorite tank platoon sergeants was slinging 120mm all over Sadr City when that area rose against the government again. And he and his platoon did it very well and played a big role in pacifying the area. I don't imagine he was the only SFC making sure his crews were ready for a big fight and I don't think that gunnery skills have eroded to the point where the Armor Corps is now dead.

Many of our readers will dismiss (or embrace) Gian's paper out of hand. I don't agree with all of it nor do I think all of it is accurate, but there are a number of points in it that need to be heeded. The Armor Corps is certainly not dead and is not nearing its demise. Yet. Hopefully longer dwell times will help bring competencies back to the level where they were and provide the time to train those skills required in today's fights.

Wednesday, March 3, 2010

De la contre-insurrection

Francophones interested in COIN should check the latest issue of Securite Globale (No.10, Summer 2009). Stephane Taillat, whose blog En Vérité still holds, to my knowledge, the monopoly over francophone COIN blogging, co-edits a series of articles on “contre-insurrection(s).” Among other contributions, David Ucko has an article on the dilemmas of the US COIN doctrine, Michel Goyat describes the British experience in Helmand, and Christian Olsson examines the link between COIN and the responsibility to protect. Not to surprise anyone, Gian Gentile has an article denouncing the “myths” and “dangers” of the COIN doctrine where he offers a “vision critique de l’US Army” (no translation needed for this one, I believe).

Gentile has found a new fan on the other side of the pond. Jean-Dominic Merchet from the (usually excellent) Secret Défense blog had a “Aha!” moment when reading Gentile’s contribution. In a post titled “To get down with the counterinsurgency dogma” (“Pour en finir avec les dogmes de la contre-insurrection”), Merchet marvels at Gentile’s revelations about the “mythification of the 2007 surge,” (apparently paying off the Sons of Iraq played some part in that success—oh, really?) and the fact that it is now “more important for the army to learn and adapt than to be capable of fighting” (what I usually read runs more along the lines of “it is important to learn and adapt to be capable of better fighting”, but I may be unnecessarily subtle here). Apparently unaware of the fact that Gentile has as much a vested interest as Petraeus in promoting his own Iraq narrative and interpretation of what worked or not there, Merchet concludes that the French army should learn from Gentile’s article and not get carried away by the COIN precepts.

I'd say that the French army will be just fine, thanks, but I may simply be blinded by the COIN dogma...

Wednesday, September 9, 2009

Airstrikes down in Afganistan

According to a report in USA Today, the number of airstrikes conducted by coalition forces in Afghanistan has dropped by close to 50 percent since GEN McChrystal took command three months ago.

NATO fixed-wing aircraft dropped 1,211 bombs and other munitions during the past three months — the peak of the fighting season — compared with 2,366 during the same period last year, according to military statistics. The nearly 50% decline in airstrikes comes with an influx of more than 20,000 U.S. troops this year and an increase in insurgent attacks.

The shift is the result of McChrystal's new directives, said Air Force Col. Mark Waite, an official at the air operations center in southwest Asia. Ground troops are less inclined to call for bombing or strafing runs, though they often have an aircraft conduct a "show of force," a flyby to scare off insurgents, or use planes for surveillance, Waite said.

The decrease in air attacks may also be the result of having more ground troops, Waite said. Air attacks are often used when ground forces aren't available to secure an area or seize an objective.

So instead of repeating platitudes about how civilian casualties are the key metric for success in a counterinsurgency war, I'll just post a relevant quote that I recently came across in Kalyvas. It's from John Paul Vann, a U.S. adviser in Vietnam and prominent participant in the CORDS program (and the source of several other quotable COIN-ish witticisms):

This is a political war and it calls for discrimination in killing. The best weapon for killing would be a knife, but I'm afraid we can't do it that way. The worst is an airplane. The next worst is artillery. Barring a knife, the best is a rifle -- you know who you're killing.
Interestingly, during his active-duty Army time, Vann was awarded the Distinguished Flying Cross for his role in coordinating the battle of Ap Bac from a spotter plane while serving as an ARVN adviser. He would later (posthumously) be awarded the Distinguished Service Cross -- the only civilian recipient in the Vietnam War.

Oh, and I'd be remiss if I didn't note that the hard-working USA Today reporter sought out two COINtras to challenge what COL Gentile calls "the dominant narrative":

By exercising so much restraint, the U.S. military may sacrifice a key firepower advantage on the battlefield and expose ground troops to more risk, some officers and analysts say.

"There is a tradeoff," said Col. Gian Gentile, a former battalion commander in Iraq who has publicly criticized counterinsurgency doctrine. "You reduce civilian casualties, but you potentially increase your own casualties."

Doug Macgregor, a retired Army colonel and military historian, says the emphasis on having conventional forces trying to win over the population is futile.

"You surrender whatever military advantage you have by compelling the U.S. conventional soldier or Marine to fight on terms that favor the enemy, not the American soldier or Marine," Macgregor said.

Gentile's comment is entirely accurate. Though I disagree with him on a great many other things, it is absolutely true to say that executing counterinsurgency tactics in an effective manner will erode some long-established strictures that privilege force protection over other mission concerns. Doug MacGregor, on the other hand, is just lost in the sauce. But then, are we surprised?