Friday, December 23, 2011

"The more things change...": Statecraft and Malice Aforethought Edition

Let's flash back to America near the turn of the century, shall we?
And we can only say that it looks very much as though, in this case, the action of the United States government had been determined primarily on the basis of a very able and quiet intrigue by a few strategically placed persons in Washington, an intrigue which received absolution, forgiveness, and a sort of a public blessing by virtue of war hysteria—of the fact that … victory was so thrilling and pleasing to the American public—but which, had its results been otherwise, might well have found its ending in the rigors of a severe and extremely unpleasant congressional investigation.
Ok, you've found me out. The turn of which century?, you perceptively ask. It's obvious we're not talking about the close of the twentieth, of course; the very suggestion of a modern Congress investigating the executive for a foreign policy failure is risible.

The ellipses above mark where I omitted Admiral Dewey's name in George Kennan's analysis of the fleet action at Manila Bay and subsequent dispatch of an expeditionary army to the Philippines in 1898. Among the "strategically placed persons" were both Dewey and Theodore Roosevelt, then Assistant Secretary of the Navy and aspiring imperialist.

What should we conclude from this episode?
For its part, Congress seemed incapable of analyzing a presidential proposal and protecting its institutional powers. The decision to go to war cast a dark shadow over the health of U.S. political institutions and the celebrated system of democratic debate and checks and balances. 
The dismal performances of the executive and legislative branches raise disturbing questions about the capacity and desire of the United States to function as a republican form of government.
That's all? Oh, wait, sorry: that's Louis Fisher's verdict, in a 2003 Political Science Quarterly article (pdf), on the embarrassing show put on by the White House and Congress in the run-up to the Iraq war. Sorry for that distracting and totally irrelevant non-sequitur! Let's get back to Dewey at Manila.
Thus our government, to the accompaniment of great congressional and popular acclaim, inaugurated hostilities against another country in a situation of which it can only be said that the possibilities of a settlement by measures short of war had been by no means exhausted.
Why do you hate freedom, Kennan, you disgusting peacenik?

[Kennan's words are reproduced from American Diplomacy, a book adaptation of several lectures he gave in 1950. The quotes are from pages 14 and 12, respectively.]

Thursday, December 22, 2011

The Principles of War have not changed, Pt II: the Surge edition

There are a number of now-accepted bromides about COIN generally and the Iraq Surge specifically that I've begun to question. There are a whole host of the pro-COIN types that have been, in my mind, disproven rather adequately. But there are some of the anti-COIN type that I'm beginning to question as well. I'll get to these in later posts, but I want to address a set that has been on mind and coined by Tom Ricks: the Surge succeeded militarily, but failed politically.

I used to think that statement was crap. Our objectives were by nature political, so what difference does it make if military gains were made. Iraq must have been a strategic failure. I can't possibly suggest that Iraq has been a success, but I think a more nuanced view is required from a U.S. perspective. I started down this thought-path after seeing this comment from COL Gian Gentile:
By saying that there can be no black and white, simple answers of yes and no with regard to the Surge you burry ourselves in a never ending discussion about its tactics and methods. But from the angle of strategy, it is clear that the Surge achieved no appreciable gains. If you have any doubt just read what Iraqis are saying about it and the last 8 plus years of war there.
Gian is an officer and thinker that I respect greatly, but I couldn't disagree more. Few things in this world are black and white - I am not the type of person who thinks that most anything falls into dichotomous categories. I also disagree with the idea that the Surge achieved no appreciable gains, even if the Iraqis disagree.

The fact of the matter is that from the perspective of U.S. interests, it doesn't much matter what the Iraqis think about this. Would we, from a policy perspective, have liked Iraq to become a Western-style democracy instead of what the past week is portending? Absolutely. But back in 2007 I suggest we would have settled for something much less. Specifically: the ability to disengage from this ill-advised war with some semblance of success without our tail between our legs, as it were. I don't remember it verbatim, but our military objective from the Surge (I was the planner for the fifth brigade deployed to support it) was to create the conditions to provide the Government of Iraq the breathing room necessary to find a political solution to the conflict.

There is no doubt that there is no viable political solution currently on the table to end the conflict. But can any of the Surge naysayers state emphatically that they were provided with breathing room to find and end to the fighting? Iraqis may not necessarily be better off now than they were in early 2003. But that is not the pertinent issue. The decision to execute the Surge is dissociated from the decision to invade Iraq in the first place. Of course they're in a worse place than they were. At the risk of understatement, it's been a bloody war. Especially for the Iraqi populace and that's a damned tragedy. The question pertaining to the Surge is: are Iraqis better off now than they were in late 2006 and early 2007? I would hazard that the answer is an emphatic yes.

What makes this all very complicated are the ubiquitous questions of causation and correlation. Many factors occurred between January 10, 2007 and the summer of 2008: realization of a nationwide Sunni uprising against AQI begun before the Surge, purging of Sunnis from Baghdad during that capital's barricaded segregation prior to the Surge, war-weariness amongst all factions, better border controls, to name a few. I do not believe that the addition of 25,000 troops to the war was the key to turning the tide, but I don't believe it was inconsequential either. But not necessarily for the reasons that Surge champions argue.

The reality is that addition of these 5 brigade combat teams was in itself a part of the relative pacification of Iraq (please note I said relative pacification - more on that to follow), not some vaporous notion of the application of COIN principles codified in FM 3-24. I will say that between my tour in 2005 and return to Iraq in May 2007 there were significant changes driven from GEN Petraeus: better intel coordination, better use and coordination of SOF units, more USG civilians and funds available. But these were peripheral changes in my mind. For whatever roll these additional troops played in providing the requisite "breathing room", it wasn't due to changes in doctrine or better use of the troops available. It comes back to the Principles of War that the U.S. Army has used for at least decades (for a full listing please see Appendix A to FM 3-0 (Operations)).

It comes down to the principle of mass in this case. From a COIN perspective and its (erroneous) counterinsurgent-to-population ratio the 25K extra troops couldn't make a difference. And it didn't from that perspective. But used in accordance with another principle of economy of force, the U.S. was able to achieve mass in the most militarily contested areas of Iraq: Baghdad proper and the areas surrounding the city from which car bombs were made and trafficked into the city. It wasn't the building of hospitals or canals or the establishment of impotent local councils that made this infusion of warfighting capability useful, it was the application of this force in time and space to dominate the situation. It was the use of these forces to set up these concrete cordons between factions that aided in stemming the violence within Baghdad, concurrent with the other more significant actions outside of the U.S. listed above. But equally important was what happened to stop the mass vehicle bombings of civilians in the much-maligned "belts" around Baghdad. Achieving mass to the south and west of the city - which fortified the disillusioned Sunnis' position - helped defeat AQI and prevent their ability to launch attacks against the capital and thus retard the cycle of violence so prevalent until then. We are all slaves to our own experiences, but we had a hell of a time (and so did Baghdad) until we were able to achieve mass in our battlespace in Arab Jabour and physically defeat AQI. Look at the statistics - already on a downward trend - between January and March 2008 and tell me that a difference wasn't made in the areas south of and within Baghdad.

So no, it wasn't COIN tactics that made the Surge useful to trends already occurring within Iraq in 2007. The Surge was useful because it allowed the coalition to mass on those areas the enemy used to catalyze the cycle of violence as well as their safe havens. But at this point, many of you will point out that Iraq is a less than a success. Car bombs are exploding all over Baghdad this week and the PM has issued a warrant for the arrest of the VP. Frankly, that just doesn't matter to the United States.

Again, you shouldn't examine the Surge through the lens of 2003. You need to look at it through the lens of 2006/7 when we were caught in a costly civil war and were attacked by virtually all sides. Of which there were many. The military objective of the time was to provide this so-called "breathing room" for the Iraqis to sort things out. It simply doesn't matter that they haven't sorted things out in a way we approve of. From a military perspective, breathing room was provided and in that way we did succeed during the Surge even if there were political failures. But the objective of Iraqi democracy exceeded our national ability to affect that change. We could only assist in providing the environment to gain a political solution through military means, not the political solution itself. These military successes throughout Iraq, with significantly lowered violence, gave us the political ability to say we've done our bit and that any other failures were Iraqi failures. What more could we have done?

It may be a correlative relationship strategically, but violence in Iraq decreased precipitously from the beginning of the Surge until its end and that cannot be argued. In my AO at least, it was quite causational (which I can discuss at length at request). But not because of some magical application of COIN principles. It was because, consciously or not, the U.S. military applied the tried and true principles of war to extricate itself from a foolishly-begun war with at least a semblance of having done its best at applying the untried principle of the Pottery Barn Rule. Not through mere coercion or indebting the Iraqis with gratitude to us did we play a part in fantastically lowering violence in Iraq, it was through applying mass and economy of force.

Wednesday, December 21, 2011

The COIN wars: a toe in the water

The gentlemen of On Violence are the latest to raise the whip over the carcass of that old glue-pot COIN, taking aim this week at what they've callled "the Chicago School of Counterinsurgency." The post is filled with generalizations, mischaracterizations, and the spurious received wisdom of second-rate popularizers and third-rate social scientists, but those errors are mostly peripheral to the main theme. This strange little essay is in fact a subtle confirmation of the rational choice theory the authors mean to criticize. The purportedly contentious assertion of what is in fact an entirely uncontroversial banality – that war is not a wholly rational, predictable phenomenon – gives the authors a platform to draw tendentious normative conclusions in purposeful contrast to the ostensible COIN orthodoxy. This serves to situate On Violence on the side "of the faction they assess to be the one most likely to win" the battle for influence and credibility in our new post-counterinsurgency era. It's almost 2012 – every blog needs to have something on record saying look, I told you they were doing it wrong!

Semantic carelessness is often the sign of poorly-formed ideas, and the post in question is rife with lexical errors. Beginning with the assertion that "the Chicago School [of economics] believes that humans always act rationally when it comes to money," the authors on several occasions use words in misleading or ambiguous ways. (Warfare in place of war is another frequent mistake.) The excerpted quotation is a simple mischaracterization of rational choice theory, which is based on the idea that people survey the choices available to them and select the one most likely to maximize gains. To assert that individuals "act rationally" is not to say that they always choose wisely, but rather that they base their choice on some expectation of benefit.

The On Violence guys clearly misunderstand this: their pronouncement that "rational investors frequently make irrational decisions, believing they are rational" is utterly nonsensical to an economist, for whom the actor's willful effort to maximize utility is precisely what defines "rationality." Of course, rationality does not imply perfect information or foreknowledge of consequences; rational actors can take decisions that turn out disastrously for them thanks to a failure to properly account for context or an imprecise evaluation of various costs and benefits. Richard Posner – who knows a fair bit about the dogmas and creeds of the Chicago school, and whose biography one might like to investigate before crowning David bloody Brooks as "our greatest living conservative commentator" – wrote an entire book about the calamitous conspiracy of rational acts that led to the recent financial crisis. (SPOILER ALERT! He does not conclude that "rational investors [made] irrational decisions, believing they [were] rational.")

On Violence further confuses the "rationality" issue by inexpertly applying the lessons of cognitive psychology (or at least Brooks's retelling of Daniel Kahnemann and Amos Tversky) to behavioral economics. According to OnV, Kahnemann and Tversky "proved that actual human behavior often deviates from the old, rational models, revealing flaws in the machinery of cognition." But about this, too, they're mistaken. The "old, rational models" say nothing at all about the machinery of cognition; they merely model the way cognition manifests as action. It's certainly true that emotion, unconscious bias, and other so-called cognitive "flaws" may interfere with the exercise of pure reason, but – as we've discussed above – that's not the same thing as irrationality. To put it rather more simply: the rational actor model may not be perfectly descriptive, but it is adequately predictive.

So who are these folks that populate "the Chicago School of Counterinsurgency"? Who accepts "the idea that in warfare—with death and subjugation on the line—mankind's rationality trumps his unconscious thoughts and emotions"? Who fails to consider how social context and personal psychology may influence the decisions of the enemy or the population held at risk? The only person named among the "military theorists [who] continue to ignore humanity's underlying irrationality" – by which the authors seem to mean the influence of emotion and other cognitive and psychological elements – is Andrew Exum, whose unsourced quote concerning "cold-blooded calculations about their self-interest" is reproduced out of context. Who are the rest?

What of the military theorist who wrote this?
[W]ar is not an exercise of the will directed at inanimate matter, as is the case with the mechanical arts, or at matter which is animate but passive and yielding, as is the case with the human mind and emotions in the fine arts. In war, the will is directed at an animate object that reacts. It must be obvious that the intellectual codification used in the arts and sciences is inappropriate to such an activity [as war]. At the same time it is clear that continual striving after laws analagous to those appropriate to the realm of inanimate matter was bound to lead to one mistake after another. (149)
Later in the same work, this theorist argued that
The effects of physical and psychological factors form an organic whole which, unlike a metal alloy, is inseparable by chemical processes. In formulating any rule concerning physical factors, the theorist must bear in mind the part that moral factors may play in it; otherwise he may be misled into making categorical statements that will be too timid and restricted, or else too sweeping and dogmatic. Even the most uninspired theories have involuntarily had to stray into the area of intangibles; for instance, one cannot explain the effects of a victory without taking psychological reactions into account. (184)
You'll surely have figured out by now that we're talking about Clausewitz. (The page numbers given above are from the Paret/Howard 1984 translation of On War.) The much-misunderstood "remarkable trinity" (pdf) introduced at the close of Book 1, Chapter 1 (89) is indeed composed of "(1) primordial violence, hatred, and enmity; (2) the play of chance and probability; and (3) war's element of subordination to rational policy." To repeat: the foremost theorist in the history of western military thought contends that emotion and chance make up two of the three vital considerations in any useful theory of war. Let's get straight to the point: any analyst who fails to consider the importance of moral factors in war – including the interplay of what On Violence misleadingly dichotomizes as "emotional reactions" and "rationality" – is a failure.

There is, of course, some irony to all of this, what with me here advocating Clausewitzian nuance and balance to a blog that has made a habit of gleefully slaying Clausewitzian straw men; claiming the Prussian's relevance to a form of war that the On Violence men have called "our style of warfare" as they scramble to distance themselves from it, ever in tune with the zeitgeist. I know, I know – try to keep it together. While we're on the subject of irony, how 'bout the OnV guys taking Pape at face value and citing his spurious conclusions as fact in an essay questioning the very legitimcy of the rational choice model?

Unsubstantiated assertion is unfortunately something of a theme in this post, and its conclusion is centered on the grand-daddy of them all: "people aren't rational when it comes to killing and death," an unequivocal pronouncement that is both demonstrably false (why then the persistence of instrumental violence?) and patently at odds with the authors' own previous acknowledgement that "war is about people, politics, and ideology."

The problem with On Violence's Gladwell-deep survey of behavioral economics is that bounded rationality cannot as yet meaningfully inform our models of human agency in conflict. We may recognize that rationality and utility maximization fail to perfectly explain all human behavior, but we have no better predictive model on which to base our efforts to influence the choices of others -- the most extreme of which is war. To paraphrase Milton Friedman, perfect realism may be impossible, but predictive accuracy is still the coin of the realm in social science. Until Kahnemann, Tversky, Thaler, Becker, et al can present a coherent, predictive theory of human choice that can be plausibly applied to economic and political behavior and which definitively falsifies the rational choice model – which is, let's remember, a model, not an attempt at descriptive realism – all this bleating about "humanity's underlying irrationality" is worse than useless: it distracts us from efforts to improve the valid models we have today and the policy prescriptions we may derive from them.

When boiled down to its essence, the message here is a simple if deeply controversial one. The authors of this essay mean to assert that the failure of rational choice theory to completely explain the whole of human behavior renders it useless as a guide to action. Because we cannot perfectly comprehend our interlocutor's decision calculus and cannot be sure his choices will be sensible to us, we must instead assume that calculus will be entirely insensate to our behaviors. If "people aren't rational when it comes to killing and death," then how can we possibly hope to exert our will in predictable ways through violence?

To accept this contention leads the thoughtful man down a dangerous path, at least so far as the anti-Clausewitzian OnV brothers are concerned: to the conclusion that predictable, willful influence is an impossibility, that the choices of an adversary or neutral cannot be shaped, and that our own alternatives are reduced to disengaged indifference to the other or his total annihilation. If we can't persuade, influence, or coerce in a predictable way that's consistent with human reason and our perceptions of causality, we are left to compel by destruction of the enemy's means to resist. This conclusion is perhaps closer to the truth than the chimera of calibrated influence offered by the many proponents of the indirect approach, but I'm quite sure it's not the one the On Violence men would like us to reach.

I'm quite conflicted about the whole thing, in spite of my stridency. The utility of force or its threat for any purpose short of compulsion is something about which I have less and less confidence every day, and I loathe the multivariate philosophies of international engagement that are founded on an unexamined faith in security through transformational change to our operating environment – whether the composition of polities or the hearts and minds of the people who inhabit them. But I see this On Violence post as reinforcing the very worst lessons of the recent COIN era: men can be changed, if only we understand what really drives them, and violence is at best a necessary complement to that transformative action. I fear COINdinistas and COINtras may both be missing the point, and if we throw out the hard-won lessons of counterinsurgency's history and present – that violence is essential to effecting needed change, however temporarily in the absence of legitimacy and consent of the governed – then this decade of "institutional adaptation" will have indeed been a waste.

UPDATE Thurs 22 Dec @ 1125: I see that Ex has responded to the original On Violence post here. I actually took out a fair bit of a draft that dealt with Kalyvas' work, so I'm glad to see that he touched on it.

Monday, December 12, 2011

Clausewitz: first proponent of the weak-states-as-security-threat school?

Ok, I'm just kidding, but try this one on for size: writing in 1831, the by now somewhat less politically progressive Prussian sage argued that "indeed, the partitions [of Poland, which were visited on the unhappy commonwealth in 1772, 1793, and 1795] were made necessary by the disorderly, almost Tartar-like administration of the vast areas the Poles possessed."

I've added emphasis to the awesomely dickish comparison of 18th c. Polish governance to Tatar anarchy; this is especially rich when you consider how it must've been received by Poles, who were (and are) justly proud of the fact that a Polish king had basically saved Western civilization from the Ottoman hordes just a century and a half before, at the conclusion of a series of wars that were largely sparked (or at least fanned) by... the cross-border raids of Ukrainian and Crimean Tatars.

Clausewitz penned this line anonymously as pushback against Jan Zygmunt Skrzynecki's protests that the Prussian government had violated neutrality and favored Russia in its effort to crush the Polish rebellion. "Poles must know little of their own history," he wrote, "or be deeply ashamed of certain pages in it" to posture about neutrality while looking past the productive use of ostensibly neutral Polish territory by Russian armies during the Seven Years War.

The worst thing that Clausewitz's contemporaries had to say about him is that he had liberalizing, reformist tendencies. His modern critics often misleadingly point to Clausewitz's Russian service as an act of disloyalty to the crown and a betrayal of his own country. But Peter Paret argues that this letter substantiates what ought to have been evident all along: Clausewitz was less concerned with supporting freedom abroad than with protecting the existence and prominence of Prussia. An independent Poland would embolden and aid the main enemy -- France -- and pose a strategic dilemma to Prussia that Clausewitz and his contemporaries found unacceptable. Raison d'etat triumphed over political preference, just as it did two decades before, when Clausewitz joined with monarchist Russia to block French hegemony.

Thursday, December 8, 2011

Baby, Bathwater, etc.

I’m taking this quick break from my blogging break because of the recent tenor of the somewhat tired “COIN debate.” It seemed to me that the discussion was going to move forward beyond its normal hostilities, but I’ve noticed a bit of a crescendo in the rhetoric this past month.

It seems to me that the discussion on what place COIN has in the United States’ toolkit should bifurcate into two very separate discussions, unlike where it is now. First and foremost as our forces reset in the wake of two lengthy land wars and in the face of declining resources, we need to examine how COIN fits into the Army and Marine Corps operational plans, what tactics we’ve learned should be kept, and what didn’t work. Second, we need to examine when COIN should be used as a strategy – loosely defined as the application of COIN tactics within an operational environment - and when it shouldn’t. These are two very, very different discussions.

I don’t want to talk much on the latter now as that seems to be where most of the contention is. It’s also so very unique to each intervention. I will go so far as to say that civilian agencies, facing as much if not more pressure to downsize, are unlikely to maintain significant capacity to respond to widespread COIN campaigns. And all this in spite of their utility in such campaigns as well as the fact that after 10 years of war they don’t much have the capacity now. The military on the other hand has executed COIN campaigns, at its most simplistic, as a collection of “COIN tactics,” considering strategy as the sum of the many individual campaigns occurring at the division level and below. If the tactics are maintained, it could be argued that the DoD could scale up to meet a national need to execute a COIN strategy and I’m not so worried about that. I’d also argue that a military COIN strategy is much more about styles of command and control than it as about tactics, but that's another subject. Also, as the veneer of COIN as “graduate-level war” or kinder, gentler war has eroded, future conversations should be considerably more honest than they have in the past 5 years. At least I hope so. Regardless, I feel that this discussion is about the application of assets which vary from conflict to conflict and should center around actual national interests.

Which leaves the first discussion, in my opinion the more important of the two in the short term. As Ex posted this week, the United States has learned a lot in the past 10 years on how to do COIN effectively and to adapt when it’s not. This knowledge has come at a great cost and we’ve learned from the past that the likelihood of our needing this set of tactics in the future is fairly significant. Even the most ardent high-intensity proponents should recognize that the types of operations conducted in Iraq and Afghanistan are very similar to Phase IV operations. We may not want to call it COIN at that point, but if we were to engage a near-peer competitor and were compelled to conduct regime change, we better have an idea of how to control and govern the population until we can get local forces and governance up and running. (This point ties into Gulliver’s post yesterday that SFA and COIN-type operations need to go hand-in-hand.) If we had any clue sitting in Baghdad in April 2003 of what we were about to face in the coming years, I’d like to think we have done things differently. And those things would have resembled what was done in post-2006 Iraq (and previously in smaller units going back to 2004).

Before 2005, Army training focused almost exclusively on Phase I-III operations (not universally, but predominately). I agree with critics like Gian Gentile that we need to get back to our warfighting roots: gunnery and maneuver warfare. But we need training exercises to train what soldiers will face after the end of major hostilities. In my mind, Phase IV tactics are at least the fraternal twins of COIN tactics. And therefore cannot be ignored since the achievement of national objectives rarely ends with the fall of statues. Many of the things we’ve learned, and relearned in many cases, in the past 10 years will apply on future battlefields whether we execute COIN strategy or more “traditional” strategies.

So as we go forward with these important and impassioned debates, let us keep some perspective. There is COIN as strategy and there is COIN as tactics. I firmly believe we cannot lose the latter. It wouldn’t break my heart to jettison the former. But as the title of this post suggests, don’t confuse the two. We don’t want to jettison that baby we know we’ll need some day because of the dirty, tepid bathwater it’s been steeping in these past few years.

Wednesday, December 7, 2011

Back to the future: time to renounce panaceas in Afghanistan

My friend Andrew Exum and two of his colleagues at the Center for a New American Security, retired LTG Dave Barno and Matthew Irvine, published a new paper this week calling for a shift in the primary emphasis of the Afghanistan war effort.
It is time for a change of mission in Afghanistan. U.S. and coalition forces must shift away from directly conducting counterinsurgency operations and toward a new mission of "security force assistance": advising and enabling Afghan forces to take the lead in the counterinsurgency fight.
This change, the authors suggest, is necessary to solidify security gains made by coalition forces in recent years and ensure the continued protection of Western interests after NATO forces leave the country. While the report marks an analytical step forward, environmental and institutional constraints are likely to blunt the effectiveness of its policy prescriptions if not block their enactment altogether. It's difficult to escape the conclusion that what passes for creativity in our contemporary efforts to "save the war" has in fact come as much too little, and far too late.

A simple rendering of the report's main argument goes as follows: of the several courses of action available to U.S. forces between now and their ultimate withdrawal date in 2014, the one most likely to produce lasting positive effects entails an immediate, aggressive, and committed effort to increase the capability of Afghan forces. The other alternatives are presented as unpalatable caricatures: 1) continued emphasis on coalition-led counterinsurgency operations through 2014, then sudden and complete cessation of combat activities by NATO forces and transition to predictably incompetent ANSF; 2) unilateral abandonment of the agreed-to drawdown timeline and indefinite continuation of the presently inconclusive western-led status quo; and 3) a rapid and immediate withdrawal of all coalition forces, leaving 2015 Afghanistan both bereft of capable security forces and denied the potential security gains from 36 more months of sustained NATO counterinsurgency operations. The authors assert that their preferred course "will protect long-term U.S. security interests without a never-ending commitment of immense U.S. resources":
[W]e believe that the most prudent option for U.S. policymakers is to adhere to the Lisbon framework for transition in Afghanistan and accelerate the change in mission. By doing so, the United States and its allies will have more time and resources to support the ANSF ahead of the coming transition in 2014, increasing their capabilities and providing vital support as they take ownership of the fight.
Considering they've characterized the other options as expensive, slow failure; very expensive, very slow failure; and inexpensive, rapid failure, I don't suppose we're left with much choice.

A great deal of hay has been made over the past 48 hours of the fact that Exum was a vociferous advocate for escalation back in 2009, when the president grudgingly accepted GEN McChrystal's proposal for a so-called "fully-resourced counterinsurgency campaign." His many critics imply that Andrew should be embarrassed, should show some shame, should prostrate himself before the we-knew-better masses and ritually cleanse his analytical sins. As they would have it, he is advocating in 2011 for a transition that would've been similarly effective two years ago, and which would've saved lives (and billions) to boot.

Bollocks. The war is not the same. Afghanistan is not the same. America is not the same. I was a critic of escalation in 2009; my views are unchanged with hindsight. It simply does not follow, however, that the historical fact of escalation is irrelevant to the operational and political context of today.

That said: this should've happened two years ago.

Announcing his decision to send additional troops to Afghanistan in December 2009, the president said that those forces would "increase our ability to train competent Afghan Security Forces, and to partner with them so that more Afghans can get into the fight. And they will help create the conditions for the United States to transfer responsibility to the Afghans." The Army had started deploying specially augmented brigades to Afghanistan to focus on the train-advise-assist mission. When a brigade from the 82d Airborne was tapped as the first of these, CNAS honcho John Nagl told the Washington Post that compared to previous SFA efforts, "the change couldn't be more dramatic." So one might fairly wonder why Barno, Exum, Irvine, and even Nagl are now essentially telling us that what Afghanistan needs is a fully resourced security force assistance campaign.

They know the answer, of course: COIN advocates insisted the 2009 escalation would be accompanied by a renewed commitment to generating and training capable Afghan security forces, but it didn't happen; the "surge" in combat and stability operations instead starved those efforts of the personnel, resources, and command emphasis they needed to succeed in parallel. The authors have diagnosed the problem properly, though they don't clearly state this conclusion. Instead we get this:
Evidence suggests that some ANSF units are failing today because they commonly operate in the field without embedded, continuous coalition support. Despite the importance of the security force assistance mission, no senior U.S. headquarters, organization or senior commander is currently dedicated to advising Afghan forces. (One can only observe the way in which the initial training of Afghan forces improved after the appointment of a U.S. three-star general officer in 2009 to appreciate the effect organizational changes can have on priorities -- and results.)
Another excerpt is more to the point: "Because U.S. units can execute counterinsurgency operations better and faster than their Afghan counterparts," the authors write, "they are continuing to do so despite the looming transition." Don't let the obfuscatory syntax fool you: individual units are not making this decision for themselves. ISAF has made a determination to focus on combat operations, to try make as much progress as quickly as possible, and then to transition to ANSF "lead" when the Lisbon deadline hits.

The authors can point to an improvement in initial training thanks to reorganization and re-prioritization, but that, too, came at a cost: by focusing on the rapid expansion of the ANSF to meet benchmarks on the "transition" timeline, the coalition tacitly accepted that the Afghan combat formations they stood up would be of inferior quality. The training and advisory effort became a sideshow, a supporting line of operation to the main effort of Western-led counterinsurgency: ISAF leadership knew that "showing progress in the training mission" would be essential to sustaining political support for the campaign, and that 350,000 mediocre troops brief better than 100,000 capable ones. Combine that with the reality that even exceptionally capable host-nation forces would still require the combat support provided by American enablers -- aviation, precision fires, communications, medical support, and so on -- and it's easy to see why quality and competence were sacrificed to rapid expansion. But let there be no doubt: that's what happened.

The paper's authors' bemoan the fact that the American military lacks "the institutional roots to support specialized combat advisor capabilities," as if this is the reason ISAF chose to emphasize initial training over embedded mentoring and assistance. Even if directed at general purpose forces (and ignoring SOF), it's a misleading and inaccurate suggestion: the Army and especially the Marine Corps may be resistant to specialization, but recent U.S. experience in Iraq forced the institutions to adapt. It is patently false that "neither service has devoted a portion of its U.S.-based force structure to training, organizing, equipping, or championing the delivery of dedicated advise and assist capabilities to Afghanistan." The Army dedicated U.S.-based force structure to training combat advisors in 2007; that function has been institutionalized and continues to this day. The 162nd Infantry Training Brigade (and before that, 1st Brigade, 1st Infantry Division) has prepared individuals for deployment as part of Military Transition Teams and with dedicated advisory brigades (called Advise and Assist Brigades in Iraq and Modular Brigades Augmented for Security Force Assistance -- a tellingly short-lived designation -- in Afghanistan). Upon the transfer of SFA training mission (pdf) from Ft. Riley to Ft. Polk in 2009, the commander of its new home even remarked that the Army sought to avoid "let[ting] the good functions and training and art and science of this task atrophy and die out like we did after Vietnam -- the last time we made a concerted effort to train combat advisors." Much of this "art and science" was codified in doctrine with the Army's publication in May 2009 of FM 3-07.1 Security Force Assistance (pdf), an imperfect manual that nonetheless provided tactical guidance both to AABs and to individual combat advisors. This institutional commitment of more than two years ago looks very much like the one Barno, Exum, and Irvine would like the Army to make today.

The purported institutional shortcomings highlighted in the paper -- such as a failure to offer sufficient promotion and assignment incentives to encourage the most capable officers to volunteer for advisory roles -- were considered and addressed years ago, when the U.S. military first had this conversation with itself during the Iraq war. Most were discarded as unworkable or counterproductive, as was the transformational fantasy of a permanent advisor corps. (Consider the budget and force structure debate currently taking place in Washington, but imagine it's happening in a world where the Army's end-strength includes the equivalent of two-dozen infantry battalions dedicated solely to training and advising foreign military forces -- a task they're not even legally permitted to perform outside of war zones and other exceptional circumstances. Who do you think is first on the chopping block?) The Marine Corps has continued to provide capable personnel for MTTs, while the Army has supported the training and advisory mission through the creation and deployment of MB-SFAs.

This is not a service problem. This is a combatant command problem. It's not a matter of force generation, but force employment. When things went bad in the Arghandab River Valley as the president was finalizing plans for escalation, U.S. commanders threw 2nd Battalion, 508th Parachute Infantry Regiment into the breach to replace Harry Tunnel's Stryker brigade and sustain counterinsurgency operations. Back to COIN for 2/508 -- one of the battalions of the 82d's SFA brigade, whose deployment for the train-advise-assist mission John Nagl had lauded mere months before.

Recognizing that a continuation of the status quo was unsustainable and unlikely to be effective, the U.S. faced very much the same set of questions in Afghanistan in 2009 as it had in Iraq in 2006. Was it still possible to accomplish American objectives? Could more troops or a new concept of operations improve the situation? Would precipitous transition to host-nation lead be too dangerous, risking the collapse of indigenous forces and jeopardizing U.S. interests? In 2006, a very serious and intelligent man wrote a memo for the president entitled "Transitioning to an Indirect Approach in Iraq" (pdf) in which he argued that success was still attainable if lead security responsibility were transferred to Iraqi forces. I want to share with you the meat of his argument, so I hope you'll forgive me quoting at length.
Given Iraq's unsettled politics, it is highly unlikely that American forces, even with growing Iraqi security force assistance, will be able to defeat the insurgency within the next 2-3 years. The current level of insurgency, moreover, is likely to be insensitive across a wide range of force levels. The assertion by many critics that more troops in 2003 could have nipped this insurgency in the bud or fundamentally altered its course are not credible. Likewise, increading the number of U.S. troops now is highly unlikely to be decisive. The insurgents will still control the initiative, and they can always temporarily decline to fight. Insufficient intelligence and continued strong support for the insurgency among the Sunni population will limit the strategic success of any near-term efforts. As long as the political grievances fueling the insurgency remain, the insurgency will remain.
Because of the direct approach's inability to produce decisive near-term results and its increasing cost, the longer we stay with it, the more we place our long-term goals in Iraq at risk. Continuing with this approach, moreover, does not play to American strengths. The insurgents and the states supporting them (i.e., Iran and Syria) retain the strategic initiative in Iraq, while we suffer from significantly reduced strategic freedom of action.
It is imperative that we accelerate our shift to an indirect approach, with Iraqis in the lead and Americans in support. Transitioning to an indirect approach will require that we begin and continue the drawdown of U.S. forces while the insurgency is still raging. It will require additional resources for Iraqi security forces. Most importantly, we must make our stated "main effort" our actual main effort.
Mike Vickers was not alone in his analysis, but the president disagreed. How much of the improvement in Iraq is attributable to his decision to escalate is and will continue to be a matter of debate. Perhaps the indirect approach, too, would have succeeded, but we can't know.

The same is now true in Afghanistan. The "change of mission" advocated by Barno, Exum, and Irvine might have been successful in 2009, with five years to take hold and show progress. (It seems unlikely to me, but I'm skeptical about our "strategy" and the no-safe-havens approach to antiterterrorism.) Or perhaps the course the president did choose for Iraq would have been similarly successful in Afghanistan had it been implemented with the "surge": a comprehensive foreign internal defense campaign that included elements of U.S.-led counterinsurgency and stability operations, SFA, and broad based nation assistance that cemented the authority of the legitimate civilian government and helped enable the exercise of that authority. (I doubt that, too, but it's a thought.) Instead what we got was a shadow of that, a mockery, an example of what happens when military leaders commit wholesale to a mission their government is too afraid to definitively refuse.

U.S. commanders are reaping what their predecessors have sown: giving short shrift to the essential enabling efforts that should have been a key part of their campaign plans, trying to "move the needle," show progress, and convince an indifferent public, an unimpressed president, and perhaps themselves that a war without a plausible strategic rationale is worth waging into infinity. SFA will not save us now. It is likely to be less effective than it would have been if comprehensively administered in 2009 by embedding advisors along with the troop surge, as this would've allowed the U.S.-ANA relationship to proceed along roughly the same path as the U.S.-IA relationship did before: first with U.S. units leading operations and owning battlespace, supported by host nation units with embedded American advisors; then partnered operations, where a more capable host nation unit with U.S. advisors owns its own battlespace and functions as part of a combined operation with U.S. forces; then eventually to host nation lead, where U.S. combat formations no longer operate independently and American advisors really live up to their name -- advising their foreign counterparts in independent operations as opposed to teaching and coaching them. This model may be followed to good effect in a few key districts, but reduced operational tempo with the beginning of the troop withdrawal makes it an unlikely template for the entire country.

Just the same: no matter how capable Afghan security forces may be today or in 2014 or in 2024, there will come a day where the western world forgets that it once seemed normal to spend billions of dollars sustaining an army in a place where a dead terrorist used to live. This day can perhaps be delayed, but it can't be avoided.

All of this may sound like I disagree with the paper's bottom line, but I don't. "By continuing to place its forces in the lead in counterinsurgency operations in Afghanistan, the United States is ultimately working against its long-term security interests." This is almost certainly true. Look back at what Vickers wrote to the president five years ago: "Because of the direct approach's inability to produce decisive near-term results and its increasing cost, the longer we stay with it, the more we place our long-term goals in Iraq at risk." Combat operations in Afghanistan are costing a fortune, depleting our force, wearing out equipment, and reducing our strategic flexibility to little evident effect. Anything that constitutes a step away from that -- even if it's still expensive and unlikely to succeed -- is something I can get behind.

Thursday, December 1, 2011

The tragedy of G. F. Kennan

I've just started reading John Lewis Gaddis's new biography of George Kennan, who I suppose I've spent the last 15 years or so thinking of as a personal hero (I would have done, anyway, if I were the sort of fellow who had personal heroes). It will likely be a great while before I finish it, though, so don't hold your breath for a review; the book is 800 pages, I'm an extremely slow reader, and I'm always working my way through five or six books at a time. You're more likely to get another Pentagonese lesson in the meantime.

For now, you really ought to read Todd Purdum's piece in the forthcoming issue of Vanity Fair. It's called "One Nation, Under Arms." Purdum artfully splices brief reflections from his exploration of Kennan's collected papers with a pessimistic assessment of our collective capacity to halt the campaign of national disfigurement foisted on us by the unfortunate Kennan and his fellow architects of the national security state. Here's my favorite bit:
A theme that runs through page after page of Kennan’s writings—from his astonishment at the leisure culture that thrived in Southern California during his first visits there, in the post–World War II period, to his mordant commentaries on the Reagan era—is a profound love of country tempered by deep disappointment at the ways in which the modern United States has so often been willing to settle for the wasteful, the trivial, the second-rate. In Box 286, one finds a speech to the National Defense University, in 1985, in which Kennan sounded just these themes as he reflected on the broader meaning of containment.
“There is much in our own life, here in this country,” Kennan said, “that needs early containment. It could in fact be said that the first thing we Americans need to learn to contain is, in some ways, ourselves: our own environmental destructiveness; our tendency to live beyond our means and to borrow ourselves into disaster; our apparent inability to reduce a devastating budgetary deficit.”
The old diplomat lived long enough to see another two decades where such tendencies escaped containment; he'd find little to surprise him among the depths we've plumbed in recent months. It's tough to look back over Kennan's diaries and letters in the last decades of his life, to see his disappointment and powerlessness in the face of the un-killable multi-trillion dollar mutant his ideas helped to feed. If that guy spent 101 years feeling frustrated, what's left for the rest of us to do?

Almost makes you want to retire from this business, pack up your books, and move to a place that's never heard of Raytheon, Lockheed Martin, Buck McKeon, "bomb power," or extraordinary rendition. Almost.

Tuesday, November 29, 2011

Rosetta Stone: Pentagonese

Ok, you've been introduced to Pentagonese. You've seen some specimens living in the wild. You've heard about the obscure doctrinal quibbling at the dark center of all of the Pentagon's lexicographic debate. Now witness the power of this fully armed and operational battle sta... uh, fake software package*:

The fine photoshopping work you see above comes courtesy of Caitlin Fitzgerald, she of Clausewitz for Kids and Gunpowder and Lead fame. She's a real artiste. I was sure I'd posted this several months ago when she ginned it up for me, but a search of the archives reveals that my memory has failed us all yet again.

In any event, enjoy (and don't sue me).

* Seriously, this is fake. Don't sue me.

The tip of a really idiotic iceberg

Over time, working in or around the defense bureaucracy inures you to stupidity, contradiction, and doublespeak. That's the only explanation I can give for not having already written about the proposed "empowerment" of the National Guard Bureau (by elevating its chief to membership in the Joint Chiefs of Staff), an idea so prosaically and unremarkably dumb that until last night -- when Twitter started throwing a collective wobbly about the whole thing -- it never even occurred to me to try to explain its fundamental bankruptcy. And maybe I'll get to that at some point, but for right now I want to talk about something that's way more important: the Defense Department can't even decide on the appropriate acronym for its own name.

It's possible that there are people in the world who identify me as marginally overconcerned with taxonomy and the doctrinal lexicon (which is a totally separate condition from typography nerd-ism, with which I am also afflicted). If you don't know what that means, I'll tell you in clearer terms: I like to whine about people using words and acronyms incorrectly. And I'm a particularly careful observer of the strange brand of pseudo-English spoken in the Pentagon. So when my friend Jon Rue asked this morning if I could clarify whether "DOD" or "DoD" is the appropriate form, I was happy to answer. The only problem is that there isn't a good answer, and that's where my desensitization apologia above comes in: somehow, this seems totally normal to me.

You might not have known this, but the U.S. military has its own dictionary. It's called Joint Publication (JP) 1-02, the Department of Defense Dictionary of Military and Associated Terms. The simplest way to explain it is this: JP 1-02 takes all the terms and acronyms included in the various joint doctrinal publications and puts them in one place. If you're conversant in such things, you'll know from the title that the dictionary itself is a joint doctrinal manual; that means it's authoritative.

The preface of the manual lays out its scope and purpose: it "sets forth standard US military and associated terminology to encompass the joint activity of the Armed Forces of the United States," and the terms included "constitute approved Department of Defense (DOD) terminology for general use by all DOD components." To be even more clear:
This publication applies to the Office of the Secretary of Defense, the Services, the Joint Staff, combatant commands, DOD agencies, and all other DOD components. It is the primary terminology source when preparing correspondence, to include policy, strategy, doctrine, and planning documents. [Emphasis mine.]
That seems to just about settle it, right? JP 1-02 applies to everyone, and it's your primary source document for pretty much all writing, right? If you need to know the Department's position on the meaning of a specific term or acronym, you go to the dictionary: JP 1-02.

So what does 1-02 have to say about abbreviating the Department's name? Check out page A-45: it's DOD. This makes a lot of sense, seeing as the Pentagon refers to other Departments using the same format: DOS, DOJ, etc. (Curiously, the Department of the Navy is referred to as DON, while the Department of the Army is just DA. Don't ask me. Perhaps avoidance of "DOA" is self-explanatory.) So there you have it: DOD, simple as.

Oh, but not so fast, my friends. Department of Defense Instruction (DoDI/DODI) 5025.12, which is LULZily titled "Standardization of Military and Associated Terminology," uses "DoD" throughout. So does every other Department of Defense issuance (ppt) -- all other DoDIs and DoD Directives (DoDDs), plus Pubs, Manuals, Administrative Instructions, and Memorandums (sic; yep, that's correct DoD usage, too). You know what else uses "DoD"? DoD 5110.04-M, the "DoD Manual for Written Material."


Want to hear something even more awesome? The "Writing Style Guide and Preferred Usage for DoD Issuances" document (pdf), hosted on "The Official Department of Defense Web Site [sic] for DoD Issuances" and based on a memo from Bob Gates's executive secretary that Spencer Ackerman wrote about earlier this year (in a post called "Pentagon Issues Bitchy Acronym Memo (PIBAM)"), and which is a good quick-reference if you slept through 8th grade language arts, completely elides the whole dispute, noting only that "the acronyms 'DoD,' 'OSD,' and 'U.S.' do not need to be established upon first use." (The document also features a lowercase-o "DoD" in the ALL CAPS TITLE on the first page, not to mention specifying use of "website" in spite of the inclusion of "Web Site" in the header of the website/web site/Web Site on which it is hosted.)

But here's the absolute best part:
3. RESOURCES FOR WRITING DoD ISSUANCES. Use the resources in priority order below when you have questions on English usage, writing style, format, content, and organization of DoD issuances.
a. The Issuance Process
(1) Format, content, and organization Standards for each type of issuance.
(2) Frequently Asked Questions. [on the host website]
(3) Common Mistakes. [on the host website]
(4) DoD 5110.4-M, “DoD Manual for Written Material.”
(5) JP 1-02.
That's right, the authoritative "primary terminology source" that is codified in joint doctrine, the Department's dictionary -- JP 1-02 -- is only to be consulted if a conclusive answer cannot be found in a different DoD/DOD issuance... which in this case happens to offer a contradictory answer.

As if all of that wasn't bad enough, an older version of the usage guide included this provision:
The following acronyms and abbreviations may be used as adjectives only: U.S., DoD, POTUS, SecDef, DepSecDef, CJCS, VCJCS, DJS, VDJS, JCS, JS. Spell the terms out when using them as nouns.
So "DoD issuances" but "documents issued by the Department of Defense." (Or something.) The current version has eliminated that bit; now it only applies to "United States/U.S."

If you're still reading, quit. You've already thought about this for ten minutes longer than anyone else in the Pentagon. Which, in case you're wondering, seems like a safe substitute ("Pentagon," that is) for any of the various titles, acronyms, initialisms, or other forms of address used to collectively refer to the organizations and personnel who work in, around, beneath, or in connection with that building, and which/who seem incapable of conclusively deciding on what to call themselves.

Wait, I've got one last acronym for you: FML.

Friday, November 18, 2011

Where you sit is where you stand, Example No. 671,000,000,000

Secretary of Defense Leon Panetta, speaking at General Dynamics Electric Boat in Groton, CT, November 17, 2011:
I'm not going to hollow out the force. Coming out of World War II, coming out of Korea, coming out of the Vietnam War, coming out of the fall of the Soviet Union, the problem was that cuts were made across the board, and the result was we weakened defense across the board. We hollowed out the force.
Congressman Leon Panetta, Chairman of the House Budget Committee, quoted in the New York Times on January 31, 1990:
Pressure is also building to divert some of the money for costly Pentagon weapons systems and create a ''peace dividend'' that could be used to avoid big cuts in social programs. But Mr. Cheney has largely shunned suggestions to kill any new weapons programs, arguing that the United States military needs a modern force.
Representative Leon E. Panetta, the California Democrat who serves as chairman of the House Budget Committee, said that Mr. Cheney's 1991 military budget was ''very disappointing.''
Mr. Panetta said that when some members of Congress recently complained to Mr. Cheney about the absence of a peace dividend, ''he made the comment that the peace dividend is peace.''
Don't worry, though: Uncle Leon explained this apparent discrepancy when he was over on the Hill back in June, testifying before the Senate Armed Services Committee in support of his nomination. When asked by John Cornyn about his role in the post-Cold War defense drawdown, when he served as President Clinton's budget director, here's how today's SECDEF responded:
As Director of OMB, obviously, I was given the responsibility by the President to try to achieve significant savings as part of the economic plan that was adopted by the Congress that, by the way, reduced the deficit by almost $500 billion. And I think that, plus other agreements that were made in the Bush administration and, ultimately, with the Republican Congress all contributed to our ability to achieve a balanced budget.
Specifically, with regards to the defense area, my responsibility as OMB Director was to provide a number to the Defense Secretary and those at the Defense Department to determine how best to try to achieve those savings. And I do understand that that was part of what they proposed.
But looking at it in hindsight, it might not have been the best way to achieve those savings, but it was a decision that was made at the Defense Department.
A lot to unpack there, but it basically comes down to I was for it before I was against it.

Panetta contends that he's not responsible for whatever negative effects were suffered by the '90s drawdown because he just did his job, just presented a topline number, while Defense officials made the program decisions necessary to get there. "[I]t might not have been the best way to achieve those savings," he says, presumably referring to the major cuts to procurement accounts that Cornyn brought up in his question, "but it was a decision that was made at the Defense Department."

Well, Mr. Secretary, now you are the Defense Department. And you're telling us that it's appropriate for the Congress and the White House to serve you up a topline number that jibes with political reality, just like you did for the Aspin Pentagon. And you're telling us that past procurement holidays might have been a mistake. And you're telling us that you're not going to hollow out the force. And you're telling us that you're not going to break faith with military personnel.

So now what are you going to do?

Are you going to "suck it up, do what's right for the country"? Are you going to "do the work that [you're] supposed to do"? Are you going to prioritize and make decisions and accept risk and put your own ass on the line -- are you going to show some leadership?

Or are you going to stand up in front of a bunch of guys in hard hats and say "damn" and "son of a bitch" a lot, get everybody chuckling at good ol' Uncle Leon, and feed them pathetic applause lines about what Congress needs to do for you?

Monday, November 7, 2011

A telling headline: Defense and foreign policy

There's a profile of Michele Flournoy, the Under Secretary of Defense for Policy, in today's Washington Post. Reaction to the piece on Twitter has been universally positive, at least among the people I follow, and it's little surprise: Flournoy is a great defense policy mind and an effective leader, and her success sets a great example for the next generation of women in the field. I think she's generally done a good job, though I could come up with some inside-baseball complaints that wouldn't hold much significance for people outside the Pentagon.

But you know me: there's always a down-side. For this piece, it's the headline:
Michele Flournoy, Pentagon's highest-ranking woman, is making her mark on foreign policy
No one could quibble with the accuracy of the statement. But it may be worth reflecting for a moment on the fact that we've grown so accustomed to the modern Defense Department's coequal if not primary role in the formulation and execution of foreign policy that there's scarcely a mention of the fact that this isn't the way our government is designed to work.

This isn't a shot at Flournoy -- if she hadn't "made her mark on foreign policy," she'd probably have been fired by now for failing to do her job. No, it's but a wistful recollection of the days when the men and women who wanted to direct foreign policy -- the Nitzes and Kennans and Achesons -- did so at the State Department, when our national leaders recognized that armed force and the plentiful resources that backed it were but one of several tools that the country used to assure its interests around the world.

Tuesday, November 1, 2011

A "hollow force": what it is and isn't

It is almost literally impossible to read an article or essay on the subject of imminent defense budget cuts without coming across expressions of concern about the potential "hollowing of the force." Bob Gates warned about it before he left the Pentagon, and Secretary Panetta's been on the same talking points. Journalists and bloggers sprinkle the term liberally throughout their prose. But it seems that somewhere along the way, nearly everyone stopped paying attention to just what the heck the term "hollow force" actually means. I've been ranting and raving about this (to myself, mostly) for months, so it's time to get this straight once and for all.

This post was prompted by Walter Pincus's column today, in which he at least concedes some uncertainty about the precise meaning of the phrase:
A repeated fear is that defense cuts will result in a “hollowing-out of the military.” As best as can be pinned down, that means reductions, whether in numbers or pay, that would leave the services without the experienced noncommissioned and mid-level commissioned officers who actually run things.
So that's one version: reductions in staff NCOs and field grade officers proportional to the size of the force. Let's look at some other representative examples. (The italicized bits indicate my emphasis.)

Here's Benjamin Friedman writing at The National Interest's blog:
The more substantive claim wielded by Pentagon boosters is that cuts would produce a hollow force, a military overburdened with missions that it is too small to perform and thus unable to protect Americans. These claims exaggerate both the damage cuts would do to our military’s ability to perform current missions and the damage not performing those missions does to our security.
(UPDATE: See Ben's comment below. I understand that Friedman was making an effort to characterize the views of people with whom he disagreed, and I probably should've noted this in the first place. I actually very much agree with the substance of his essay; this was just a clear example of the sort of misimpression that I'm trying to correct with this post, so I had to draw it out -- whether it was his or someone else's.)

Now the "Defending Defense" people at Heritage, AEI, and FPI:
This backgrounder describes the likely results of the significant defense spending reductions now being considered: a “hollow force” characterized by fewer personnel and weapon systems, slowed military modernization, reduced readiness for operations, and continued stress on the all-volunteer force.
Here's how an un-bylined Fox News piece described it (hilariously, this warning came in 2003):
Overdeployment may threaten recruitment and retention for the entire military, particularly the National Guard and Reserve, presenting the risk of a "hollow force" — a military that suffers dramatic drops in volunteers willing to join or stay in the armed services.
Now here's Air Force Chief of Staff GEN Norman Schwartz (via Phil Ewing at DoD Buzz) coming closer to the point:
My pledge for the coming year is to strengthen unit readiness and avoid a creeping hollow force that proves only the illusion of global vigilance, reach and power.
But what about the SECDEF -- what does he mean when he says it?
"Very simply, it results in hollowing out the force," Panetta said during an Aug. 16 event at National Defense University in Washington. "It would terribly weaken our ability to respond to the threats in the world, but more importantly, it would break faith with the troops and with their families."
So we've seen a litany of references to the "hollow force," some of which are vague and ill-defined (like Panetta's), others of which are more specific (like the Fox News/Pincus version). Many suggest that the expression fundamentally has to do with the size of the force and related issues like recruitment and retention.

Now let's check out this excerpt from a 1996 Center for Naval Analyses paper called "Avoiding a Hollow Force" (pdf), which really nails -- with a bit of maritime flavor -- what the expression is actually all about:
[Budget cuts since the end of the Cold War] have raised fears that the Navy may once again be on the verge of a hollow force. Our review of the readiness literature suggests that hollowness is a condition that keeps ships from living up to their design potential. It is the general state that persists whenever maintenance problems dominate a force; when poor quality sailors seem the rule rather than the exception; and when meaningful training is both scarce and questionable.
This explanation is consistent with the way I'd always understood the term and heard it used before the recent glut of references. If you think for a second about what hollowness evokes, this use of the term makes perfect sense: you're talking about an apparently intact form that gives the illusion of completeness and authenticity, but lacks robustness -- lacks real substance.

What "hollowing the force" means is that you keep force structure, you keep major platforms and weapon systems, you keep personnel numbers up, but you start to skimp on the things that make all of that useful -- the money that you spend to translate equipment and units and personnel into effective warfighting capability. A hollow force is one that keeps up the appearance of capability but shorts those things that make the difference between a shiny, impressive garrison army and a world-class fighting force.

What are those things? Realistic, tough, meaningful training. Flight hours. Regular preventive and corrective maintenance. Spare parts and similar contributors to sustainment. Ammunition. Exercises.

Hollowing isn't just about spending less money, but about allocating money improperly. If Congress cut the defense budget by half tomorrow and said to DoD "make it work," there are two basic ways the Pentagon could execute that tasking: 1) by slashing force structure, aircraft, vehicles, and personnel numbers and then training and maintaining that smaller force to accomplish a smaller range of missions; or 2) by keeping all those airplanes, never taking them out of the hangers, and saving money on jet fuel; keeping all those brigade combat teams, never turning a wrench on Strykers or Humvees, and spreading your non-broken down vehicles thinner across the formations; keeping all those personnel but cutting down on their expensive professional military education and realistic live-fire training. (Incidentally, the defense industry doesn't much care whether the force is hollow or not -- they'll happily sell you vehicles and planes for your last dollar, whether or not you've got the cash left over to put gas in them and take them out of the garage.)

A smaller military that does less accordingly is not a "hollow force," even if it's a less capable one. A large, apparently "world-class" military that fights poorly because of insufficient training, low morale, broken vehicles, and a lack of ammunition -- that's a hollow force. So if we know now that a hollow force is a specific type of bad military, one that's bad for a specific reason, can we all agree to stop using the term as a general synonym for "bad military"?

Monday, October 31, 2011

A few interesting Russia notes

Apologies for the infrequent posting of late, but sports (which I don't like anymore) and other real-life developments have intervened. Hopefully you'll see a return to regular service over the coming days and weeks. For now I just want to direct your attention to a few interesting Russia-related pieces: first off, you should definitely read this op-ed in Politico about the continued significance of Russia to U.S. national interests. It's by Graham Allison and Robert Blackwill (who, not incidentally, are promoting the release of a report they've written on the subject; it just went live in the last hour or so, and I haven't read it yet).

I tend to be skeptical about the deterministic certainty so many analysts seem to feel about the potential security consequences of demographic change around the world, but I'm not really a public health guy, and you'll be unsurprised to learn that I know very little about the subject. Like everyone else, I've seen references to the forthcoming bizzaro-Malthusian birthrate crisis in Russia and Japan and western Europe, etc etc, usually accompanied by alarmist commentary about the inevitable and compensatory rise in Muslim/Latino/Other Scary Brown People immigration.

As much as I tease, I'm a near-total ignorant on this issue, so I was eager to read Nicholas Eberstadt's essay in Foreign Affairs about Russian demographic trends. I found it to be reasonably informative if a little alarmist. (I've got to be honest: I get a chuckle out of some folks speculating about underpopulation making Russia more aggressive while others simultaneously speculate about overpopulation making China more aggressive.)

To get the other side of the story, check out Mark Adomanis's response to Eberstadt on the Forbes website. I always enjoy graphical pwnage, and Adomanis delivers it in force with a concise criticism of Eberstadt's use of statistics.

I don't have a dog in this fight, and as I've indicated above, I feel reasonaby confident that Russian public health issues will have a less significant and less predictable impact on international security than a lot of people would like to suggest.  But one of the significant shortcomings of much analysis of foreign security forces is a failure to appreciate the unique national context from which they're generated, and it's definitely worth taking a look at things like demographics when we try to understand the way these forces evolve and adapt. (I spent the last hour trying to think of a particular expression that distilled this sentiment and finally tracked it down in a Colin Gray book. He quotes Bernard Brodie as having written that "good strategy presumes good anthropology and sociology. Some of the greatest military blunders of all time have resulted from juvenile evaluations in this department.")

Tuesday, October 25, 2011

Who needs bipartisanship when we've got pervasive groupthink?

Les Gelb has a not-very-interesting article in the newest issue of The National Interest entitled "We Bow to the God Bipartisanship." In it, he derides what he views as the tendency to overrate the value of bipartisan support to presidents' ability to carry out their foreign policy preferences. "[B]ipartisan backing at home has too often been purchased at the price of good policy abroad," Gelb tells us.

This is a curious assertion, especially since Gelb spends much of the next 3,000 words supplying historical evidence for precisely the opposite point of view: presidents have in large part ignored domestic criticism and succeeded in enacting policies that ranged from the grievously wounding to the mildly successful.

The only real support Gelb provides for his thesis statement comes in the form of fact-free assertion about the Obama administration's purportedly craven pursuit of popular policies "where it has little faith its efforts will succeed," as in the case of Iran, North Korea, Middle East peace, and Afghanistan. To which I can only muster a disinterested and disbelieving "meh."

All of this is more than a little galling coming from the man who perhaps more than any other represents the embodiment of the American foreign policy commentariat's uncritical pro-executive consensus -- and this at his own word. On the subject of the Iraq war, here's Gelb's unashamed explanation:
My initial support for the war was symptomatic of unfortunate tendencies within the foreign policy community, namely the disposition and incentives to support wars to retain political and professional credibility.
Incentives, eh? Perhaps all this "bowing to the god bipartisanship" is more of a distasteful personal habit, one that's left our man with a bit of a guilty conscience.

Friday, October 21, 2011


This is probably a long time in coming and quite overdue, but I am taking a 6 month sabbatical from Ink Spots as of this post. In spite of the dearth of my posting, I feel very strongly that I need a break from all of this for a number of reasons (outlined below) and will be stepping away from here, Twitter, and Hull Defilade until the spring. If anyone cares, here is why:
  1. Time. Realizing I haven't been posting that often, I have found that I have been spending a large amount of my time thinking about posts to write, reading other blogs, and tooling around on Twitter. Those of you who know me personally know that I have had a tough couple of years personally and professionally and Ink Spots (and the military blogo/twittersphere in general) has taken time I do not really have to give. I have a lot things to get in order and this is just not fitting. It is time to reorient on my priorities.
  2. Perspective. Over the past few months I have found myself entrenched on issues and not engaging with others as I had previously. That does not mean that I do not feel strongly about a number of issues, but I am not adding to the dialogue any longer and rather feel like a broken record. I have also found myself internally gauging the success of my posts based on how many people tell me I am right and caring more about page views than content. That is not why I started blogging and I do not wish to continue to do this. Some time off may help with this.
  3. Professionalism. With my change in jobs this past spring, I have changed focus in my professional life. While still working on Defense issues, I do not work on policy any longer. It has been too difficult to stay up to date on issues that I like to blog about while attempting to gain and maintain an edge in my new endeavors.
I'll leave it at that before we break out into an episode of Oprah. My name will stay on the masthead (hey, even if I take 6 months off I'll still post before three of our other contributors! (kidding!)(sort of...)). If there is something someone out there is just dying to hear my opinion on, just email me and I'll be willing to write a guest post somewhere. And if no one wants that, that's okay, too. I'll probably run into a number of you out and about DC and I look forward to that. Otherwise, I'll be back in the spring - hopefully with my life a little more orderly and ready to comment on all sorts of issues. Talk to you then.

U.S. troops and the LRA: What exactly IS "your typical advise and assist mission"?

As you've no doubt already heard, the president is sending approximately 100 U.S. military personnel to central Africa to aid partner security forces in the capture or killing of Joseph Kony, leader of the murderous Lord's Resistance Army. The public found out about this when President Obama informed Congressional leadership in a letter delivered last Friday, as he is statutorily required to do. A number of analysts and commentators have offered thoughts on the matter -- Crispin Burke has a brief but representative rundown on Wings Over Iraq -- but most have failed to provide the sort of context necessary to understand how a mission of this type is carried out. By extension, many people are drawing bad conclusions about what this development means for the U.S. in Africa and for our broader national security policy.

A number of my colleagues will be quick to remind you that I'm not an Africanist. (Less charitably, I "don't know shit" about Africa.) Keep this in mind, but remember that I'm interested in talking to you about U.S. military operations and doctrine -- not central African conflict ethnography. You should seek out area experts if you want to understand the LRA's history, organization, tactics, and so on, as they'll offer far more comprehensive and better-informed analyses than I possibly could. They can further explain how the group is a scourge on the continent, how Kony's elimination would produce cascading positive effects for regional security and stability; they can talk to you about what America's ultimate goals in the region ought to be, etc. I'm not going to do that. I'm going to tell you what American troops in central Africa are likely to be doing, how they're going to contribute to the accomplishment of the anti-LRA mission, and how all of this fits into the context of what we're training, equipping, and organizing our military to do, and what it all has to do with war powers. (Go read Carl Prine's interview with Michael Noonan on this subject, too, while I'm thinking about it.)

First things first: what is it that U.S. military personnel are meant to do here? According to the president, this "small number of combat equipped U.S. forces" will "provide assistance to regional forces that are working toward the removal of Joseph Kony from the battlefield." But Barbara Starr told us yesterday that the African enterprise is "not your typical advise and assist mission"; how exactly the folks at CNN Security Clearance would define such a thing is left to our collective imagination, but perhaps her explanation can give us some clues.
President Obama’s decision to send 100 troops, mainly U.S. Special Forces, to Uganda to help hunt down leaders of the violent Lord’s Resistance Army is not meant to be a combat mission. But the troops will be well equipped if the need to fight arises, them CNN has learned.  The troops will have so-called “crew-served” weapons in the field.  These weapons, unlike a rifle or machine gun, requires more than one person to operate them, such as one person loading ammunition while the other person aims and fires.
The deployment of these particular combat weapons triggered the need for the Obama administration to publicly notify Congress of the operation under the War Powers Resolution, according to a Department of defense official.  That requirement demands that any time troops are put into a country “equipped for combat” Congress must be told to avoid any prospect of a secret war, the official explained.
Let's get the obvious objection out of the way: a machine gun is in fact the very most common and obvious example of a crew-served weapon (pdf). Such a basic error might call into question Starr's reliability and authority on the matters a "Pentagon correspondent" has responsibility for covering. But what about the meat of what I gather to be her argument -- that "deployment of these particular combat weapons" both triggered the WPA reporting requirement (an assertion she attributes to her source) and more generally indicates that the function these personnel will be performing is somehow atypical or rare? Well, both points are pretty plainly wrong.

The law (50 U.S.C. §1543) does require presidential notification when U.S. troops are sent to a foreign country "equipped for combat," as Starr notes. But the suggestion that crew-served weapons mark the threshold between being "equipped for combat" and everything else strikes me as wholly arbitrary. It's obviously a matter of interpretation, as the law doesn't specify the meaning of the term. But Starr and her helpfully explanatory official seem to have missed the much more important provision of the law: the section that explains the meaning of "introduction of United States Armed Forces" (50 U.S.C. §1547 (c)).
For purposes of this chapter, the term “introduction of United States Armed Forces” includes the assignment of members of such armed forces to command, coordinate, participate in the movement of, or accompany the regular or irregular military forces of any foreign country or government when such military forces are engaged, or there exists an imminent threat that such forces will become engaged, in hostilities.
So let's get this straight: CNN Security Clearance wants you to know that this deployment is "not your typical advise and assist mission," apparently because it triggered the WPA reporting requirement. But that requirement applies to every instance in which U.S. forces partner with, augment, lead, or advise a foreign military force that's actually engaged in fighting.

There's no such thing as an "advise and assist mission" in U.S. military doctrine, but that's not to say that the term isn't used. When the American mission in Iraq ostensibly shifted from combat (Operation IRAQI FREEDOM) to transition (Operation NEW DAWN), all U.S. Army brigade combat teams in-country were redesignated as Advise and Assist Brigades. (In the several months preceding this change, several AABs had operated alongside Iraqi formations while BCTs continued to conduct independent combat and stability operations.) "Advise and assist" is also considered by the Army to be one of five component tasks of security force assistance, alongside Organize, Train, Equip, and Rebuild/Build. Here's how the SFA manual (FM 3-07.1 (pdf), paragraph 2-50) explains it:
Advise and assist is a SFA task in which U.S. personnel work with FSF [foreign security forces] to improve their capability and capacity. Advising establishes a personal and a professional relationship where trust and confidence define how well the advisor will be able to influence the foreign security force. Assisting is providing the required supporting or sustaining capabilities so FSF can meet objectives and the end state.
It might have been appropriate for Starr to argue that "this is not your typical training mission," or even to say "this is not your typical security force assistance mission." But this is precisely "your typical advise and assist mission." The distinction is a matter of more than just semantic interest, and to show you why, I'm going to talk for a little while about what's called foreign internal defense.

Look, I know people get bored by doctrine and taxonomy and all that. (Ok, well, people other than me, that is.) But that's where we need to start if this is going to make any sense, so let's look at how FID is defined by the U.S. military:
[T]he participation by civilian and military agencies of a government in any of the action programs taken by another government or other designated organization, to free and protect its society from subversion, lawlessness, insurgency, terrorism, and other threats to their security.
To put it more simply, FID encompasses whole-of-government efforts undertaken to help another government deal with internal threats. The U.S. military's view of its role in those efforts is explained in doctrine (specifically JP 3-22 Foreign Internal Defense and FM 3-05.137 Army Special Operations Forces Foreign Internal Defense), which characterizes DoD activities as being of three types: indirect support, direct support (not involving combat operations), and combat operations.

Indirect support in FID is primarily focused on enabling the host/partner-nation government and security forces to accomplish their internal defense and development objectives independently; it's how the USG helps another government do what it needs to do without doing it for them. This category of activity includes the sale or transfer of military equipment, training of partner-nation units and individuals, personnel exchange programs, and combined exercises. Indirect support is going on every day and with a wide range of countries. Selling helicopters to Mexican federal police? Putting a Filipino special forces officer through the Maneuver Captain's Course? Transferring NVGs to Pakistan for their pilots to use in the frontier provinces? All FID indirect support.

Direct support (not involving combat operations) is where FID really starts to distinguish itself from security force assistance, security assistance, and security cooperation: it entails U.S. military forces providing direct assistance to the host nation's security forces or populace. This type of activity typically takes place during violent conflict, but that need not be the case. Direct support basically means U.S. forces providing, augmenting, or amplifying under-developed or nonexistent host-nation capabilities like intelligence collection, communications, logistics, psychological operations/military information support, and civil-military operations (provision of basic services to the civilian population). Training partner security forces can also be identified as direct support or indirect support depending on the urgency and immediacy of the effort. (U.S. personnel putting Afghan National Army troops through basic combat training prior to operational deployment constitutes direct support, while training an Egyptian mechanic on how to maintain his airplanes might be indirect support.) We're doing FID direct support in a few places right now, with the most obvious being Afghanistan and Iraq (though much of our activity there has transitioned into indirect support as Iraqi security forces have achieved autonomous capability). That thing counter-LRA Starr mentions in her blog from back in '08, the curiously-named Operation LIGHTNING THUNDER, when 17 U.S. advisors gave comms help and intelligence information to Ugandan forces going after Kony? That was direct support.

Combat operations are pretty much what they sound like: that's the part of FID where U.S. forces undertake combat operations in support of the host government's internal defense and development plan. This could mean U.S. combat formations are partnered with host nation forces or simply operating in an adjacent battlespace in support of that government's objectives. It also includes combat advising. Here's what the Army SOF FID manual says:
The primary role for U.S. military forces in tactical operations is to support, advise, and assist HN forces through logistics, intelligence or other support and means. This allows the HN force to concentrate on taking the offensive against hostile elements. If the level of lawlessness, subversion, or insurgency reaches a level that HN forces cannot conrol, U.S. forces may be required to engage the hostile elements. In this case, the objective of U.S. operations is to protect or stabilize the HN political, economic, and social institutions until the HN can assume these responsibilities.
The precise character of FID combat operations is determined not only by operational requirements but also by the type of formation or personnel participating in the mission. Individual embedded advisors or small advisor teams will obviously be unlikely to undertake offensive operations as a constituted whole simply because of a lack of combat power, while an Advise and Assist Brigade maintains the capacity and capability to perform full-spectrum operations and could independently find, fix, and finish the enemy's maneuver elements if required. As you may have worked out from the excerpt above, "combat operations" in this context include things that would be considered "combat support" in a U.S. operational context: enabling functions for maneuver formations engaging the enemy. The reason they constitute FID combat operations is that they expose U.S. troops in the field to hostile action. If you're trucking host nation troops up to the front or turning a wrench on a busted vehicle while taking mortar fire at a forward location, you're performing a direct support function, but the exposure to hostile fire qualifies this as FID combat operations.

Ok, good, so we're all sorted out on FID, right? Then let's get this straight: the USG is doing all three types of FID in central Africa. Indirect support in the form of materiel assistance was announced several months ago. We've done direct support (not involving combat operations) at various times over the last several years, including intel-sharing during LIGHTNING THUNDER. The (presumably) Special Forces soldiers going to central Africa will likely continue to perform similar direct support activities from rear areas while also in some instances engaging in combat operations by embedding with Ugandan, Congolese, South Sudanese, and/or Centrafricain military formations.

So what's new about all this? Nah, it's not about crew-served weapons. It's not about any imagined intent for SF ODAs to conduct direct-action missions against Kony and his "army." It's about the simple fact that the law requires Congressional notification in any instance when U.S. forces may be exposed to hostile fire, including those times when they're embedded or partnered with host nation forces. As I've said above: this is the very essence of an advise-and-assist mission. In point of fact, it's nigh-on impossible to perform the advise-and-assist task without the presidential decision required to permit FID combat operations, at least assuming the supported foreign force is actually engaged in a fight. (And if it's not, then the SFA task U.S. forces are performing in support of them is much more likely to be training or equipping than advising and assisting, which is a term which almost universally connotes combat action. I'm at pains to think of a single instance of what I could call an advise and assist mission that does not involve combat of some type.

American military personnel have provided support to foreign security forces through FID and SFA for decades, if not longer. They've done so in Russia during the post-revolutionary civil war, in Vietnam, across Latin America during the Cold War, in Colombia, the Philippines, Iraq, and Afghanistan in the modern day. In every instance in which they've been exposed to hostile fire, they've required a presidential determination to that effect (enabled by either a declaration of war, a WPA notification, or an executive order/presidential finding/PDD). This instance is perhaps noteworthy to the media and the public because President Obama has decided not to ignore what's required of him by law (including a declaration of "the constitutional and legislative authority under which such introduction [of U.S. forces] took place") and instead sought to legitimize the effort by expressly citing the Congress' very own appeal for action: the Lord's Resistance Army Disarmament and Northern Uganda Recovery Act of 2009 (pdf).

And that's the great irony of all this, really: the media, the public, and apparently the Congress have been so inured to the wholesale and systematic hostility of successive presidential administrations to the distribution of war powers in American law that it's more noteworthy when the president does things properly. This is precisely the sort of activity that it ought to be a presidential prerogative to undertake: FID is fundamentally a matter of foreign affairs, not war, and the Congress should be made aware and kept informed insofar as military activities pursuant to the effort may unintentionally entangle the U.S. in a foreign conflict.

I know, I know: I can't even defend the president on this issue without complaining obliquely about Libya or Afghanistan! And it wouldn't be my style to go to all this trouble talking about a troop deployment without talking about strategy, but I'll be brief (and I'll probably surprise you): I explained why I'm ok with the process of this decision, but I don't have a big problem with the substance of it, either. This sort of FID mission isn't going to cost a tremendous amount of money, and the risk to U.S. personnel is relatively low even if we make an uncharitable estimate of it. It's hard to say that we're risking even a temporary diminution of U.S. readiness or combat power simply because it's such a small number of troops. There is very little risk of unintended escalation (though we should always be wary), and if the president determines that escalation is desirable or necessary, it seems plain to me that he has set the rather unique precedent of needing to take such a decision before the Congress. This type of mission is exactly what SF were conceived, organized, and trained to do. Don't be fooled into thinking this is some kind of panacea, a universalizable model for all future American military action, the cornerstone around which we can base our future security policy. But it seems like a just, affordable, and doable thing that stops short of war, and in this case, I don't see anything particularly un-strategic about it.