Courtesy Reuters

Fixing the Pentagon

By Jonathan E. Czarnecki; Steven A. Sliwa

Just about every year, it seems, Foreign Affairs publishes at least one essay by a current or former senior leader of the U.S. Department of Defense with a narrative that goes something like this: “The Pentagon was a broken, inflexible bureaucracy when I came into office. There was a problem with [insert specific problem here]. I created/encouraged/supported a nifty solution, and it worked great. If only the solution stays/had stayed in place after I leave/left, the Pentagon would work once again.”

Ashton Carter’s latest missive (“Running the Pentagon Right,” January/February 2014) is but one more addition to this narrative series. What Carter apparently does not realize, along with his predecessors, is that in becoming a leader in the Pentagon, he became a member of its bureaucracy and can no longer stand apart from it.

Carter’s mistaken self-conception as a guerrilla in the inflexible Pentagon bureaucracy seemingly enabled him to encourage structural reforms to loosen up that bureaucracy, including the so-called Joint Urgent Operational Needs process. Such reforms were meant to bypass a sclerotic acquisition process to get needed equipment to troops quickly. Indeed, Carter presents evidence that they worked.

What Carter ignores is the larger legacy of such structural reforms, which invariably end up complicating existing Pentagon processes and systems, making them even more inflexible than they were before the introduction of the reforms. The truth is that supposedly straightforward solutions often create larger problems.

The real underlying problem for such a complex system as the Department of Defense is the mismatch between its fundamental methodology for accomplishing things and its twenty-first-century operating environment. The department’s decision cycle is too slow for its environment, and it is too slow to adapt when that environment changes. What amplifies the problem is that the environment is changing far quicker than in the reliably staid days of the Cold War.

Addressing this fundamental problem requires a persistent and determined leadership team that can focus on developing, implementing, and evaluating solutions. Having worked in the Pentagon for 14 years, I can state with some certainty that such an effort is very difficult to sustain. Secretary of Defense Robert McNamara and his so-called whiz kids attempted to do so in the 1960s, and they created systems that his leadership descendants structurally altered. In his second term as defense secretary, Donald Rumsfeld attempted to address this fundamental problem but ended up being distracted by the “global war on terror.”

JONATHAN E. CZARNECKI
Professor, Naval War College, Monterey

Ashton Carter’s essay is both poignant and timely. As the director of the U.S. Army’s Rapid Equipping Force (REF), I lead an organization whose mission is to rapidly address the urgent capability shortfalls of deployed army units by inserting emerging technologies into the field. From our assessment, the army agrees with Carter’s argument and is taking the steps necessary to institutionalize its rapid-response equipping elements. As we look to the future, one thing will remain constant: war fighters will always need a way to quickly procure technologies to defeat emerging threats and address operational shortfalls.

But it is also important to note that not all requirements are as complex as developing and fielding the mine-resistant, ambush-protected vehicles that Carter describes in his essay. In some cases, urgent requirements are specific to a unit, time, or place and thus do not apply to the entire army. When such requirements can be met only with equipment not currently in the army’s inventory, an organization such as the REF becomes critical. The REF can rapidly equip a small number of units in as few as 90 days -- addressing niche gaps with quick-to-the-field solutions.

STEVEN A. SLIWA
Colonel, U.S. Army, and Director, U.S. Army’s Rapid Equipping Force

This site uses cookies to improve your user experience. Click here to learn more.

Continue