How to Strengthen America's Military: Put the Bean-Counters in Charge
On Monday, I wrote of how Carly Fiorina, the former CEO of Hewlett Packard, who is running for president, wants a bigger Army, Navy, and Marine Corps. A large part of the solution involves cutting staff at headquarters, and in streamlining management. The corporate parallel is indicated at HP with Fiorina’s successor, Meg Whitman, who is not running for president, but who plans to dismiss 33,300 staff over the next three years, mostly out of the old Electronic Data Systems (EDS) unit. Cloud computing is crushing that business. EDS, of course, was founded in 1962 by H. Ross Perot, who twice ran for president. Perot built that company from scratch when he failed to convince IBM that running computers could be as lucrative as making them. After making a few billion dollars, he sold the company off to General Motors in 1984, around the same time that the car market acquired the Hughes Aircraft Company, in a dream of putting computers and heads-up displays in Oldsmobiles. If that seemed a little ahead of schedule for the 1980s, it says a lot about what’s wrong with the structure of the U.S. armed forces today.
While later (albeit briefly) a board member at GM, Perot clashed with management over the future of the iconic company, but neither his efforts at reform nor the corporate marriages went far. EDS was spun out in 1996, and Hughes was sold to Raytheon in 1997. As Bob Lutz argued in his book Car Guys versus Bean Counters: The Battle for the Soul of American Business (Portfolio, 2011), all the problems of that industry were well-understood by the 1970s. The management of the largest companies and the leadership of United Auto Workers just couldn’t bring themselves to drive towards the solutions they knew they needed. Lutz might know what he knew; he worked as a top executive at Ford and Chrysler, and retired in 2010 as vice-chairman of GM. One problem, as Devin Leonard summarized in his review of the book for Bloomberg Business, was that around 1977 the balance of power across the automotive business began shifting from the car guys to the number crunchers. As a consequence, product planners determined which customers to target with a new sedan or wagon; engineers fretted over inexpensive assembly; and managers fretted about cheap mass production. Only at the end were designers summoned to wrap a steel body around a nearly completed vehicle. The results, Lutz laments, were the not-so-fondly remembered Cadillac Cimarron, GMC Envoy XUV, Pontiac Aztek, and others.
In between there were enough years flush with cash from sport utility sales that the problems could be ignored. But by 2008, both Chrysler and GM—companies that just couldn’t shake their heritage or their labor costs—had been run into bankruptcy. Ominously, there’s a notion afoot that the American military-aerospace industry today is in a position analogous to that of the American automotive industry forty years ago. Think of the problem in terms of products. Lockheed Martin's F-35 JSF is something of a Lincoln Blackwood of a fighter-bomber: an impressive piece of engineering, but an awfully expensive way to haul iron. Fairly, Boeing’s X-32 idea for the JSF was a Pontiac Aztek of an airplane—all that and hideous too.
But as several Lockheed engineers have confided to me, this wasn’t their idea. They wanted to build a sleeker, more maneuverable airplane, just in case air-to-air combat wouldn’t all be from beyond visual range. The requirements-writers, however, demanded internal carriage of two 2000-pound bombs—for a single (classified) target type—and that miracle of a lift-fan, aft of the cockpit, for the jump-jet version. On the viewgraphs, this probably made sense at one point. Along the way, the purchasing power of the Defense Department dropped such that half a trillion dollars annually is buying half the force structure of the 1980s.
I was thinking about the issue at COMDEF, as I heard Under Secretary Frank Kendall complain that he was getting "out-invested” by the Chinese military. Through this year, the U.S. Defense Department will have spent just short of $100 billion on the JSF, and mostly for development. On paper, that’s not out-invested. But when you put the product planners (requirements-writers) in charge, by the time the engineers get it, there’s only so much that they can do to keep the costs in line. The Department winds up pouring money into massive sinks, and the bean counters are left trying to figure out how to restrain the cost growth, when they should be tasked with finding ways to cut the costs in half. The accountants can only work on the margins; they can’t dream up new systems from whole cloth.