The Department of War just shot the accountants and opted for speed

As someone who has some familiarity with this process, just like safety regulations are written in blood, Federal Acquisition rules are written in misuse of money, sometimes criminally.

Yes, we have swung too much towards the bureaucrats but I'm not sure throwing out everything is solution to the issue.

Move fast works great when it's B2B software and failures means stock price does not go up. It's not so great when brand new jet acts up and results in crashes.

Oh yea, F-35 was built with move fast, they rolled models off the production line quickly, so Lockheed could get more money, but it looks like whole "We will fix busted models later" might have been more expensive. Time will tell.

The F-35 was Lockheed's entry in the Joint Strike Fighter program. The JSF has roots going back to 1996. The X-35 first flew in 2000. The F-35 first flew in 2006, and didn't enter service until 2015(!!).

That's nearly 20 years to develop a single airframe. Yes, it's the most sophisticated airframe to date, but 20 years is not trivial.

The F-35 had many issues during trials and early deployment - some are excusable for a new airframe and some were not. I suspect the issue wasn't "move fast, break things" but rather massive layers of bureaucracy and committees that paralyzed the development pipeline.

The F-22 was part of the Advanced Tactical Fighter (ATF) program which dates back to 1981. It's prototype, the YF-22 first flew in 1990, and the F-22 itself first flew in 1997. It entered production in 2005. Again, 20+ years to field a new airframe.

Something is very wrong if it takes 20+ years to field new military technologies. By the time these technologies are fielded, a whole generation of employees have retired and leadership has turned over multiple times.

Most of time, this delay is in peacetime, it makes sense to do a ton of testing, wait until testing results then go to full production. Your primary concern is not spending a ton of money and not getting a bunch of people killed. It's basically waterfall in fighter development.

Wartime is more agile, you quickly close the loop but downside is sometimes does not work and when it does not work, there might be a people cost. US has done it with fighters before, F-4U Corsair was disaster initially in carrier landings and killed some pilots in training. However, this was considered acceptable cost to get what was clearly very capable fighter out there.

So then what value does the bureaucratic process add if it's the first thing that gets shitcanned when good results in good time matter?

At the end of the day it's all people cost. Just because it's fractional lives wasted in the form of man hours worked to pay the taxes to pay for unnecessary paper pushing labor instead of whole lives doesn't actually make the waste less (I suspect it's actually more in a lot of cases).

> what value does the bureaucratic process add if it's the first thing that gets shitcanned when good results in good time matter?

This is like asking what good do reserves do if you spend them down in a crisis.

The bureaucracy aims to keep waste and corruption to a minimum during peacetime. In war, the aims change--you're now not only ramping up production, but the penalties for fucking with a war are typically more drastic than lining one's pockets during peacetime.

Think about the local implications of what you just said. If we toss the process when effective expenditure of resources toward results matter and consequences are the most serious then the process must be less efficient at producing good results for the expenditure than the corruption (or whatever else the process is replacing). So then why are we running it at all?

You can absolutely make an argument about accepting reduced efficiency to dilute concentrated harms (e.g. keep a test pilot from dying), but none of the peddlers of process dare even make that argument so I suspect the math is questionable without hand waving or subjective valuation (e.g. face saved avoiding errors).

War and peacetime are two different things. During wartime you need lots of materiel quickly, so value for money estimates, anti corruption practices all get reduced in the name of production numbers at all costs. Verification is easier because you go directly from the assembly line to the front line. If it doesn’t work, you find out and make changes quickly. You know what you need because you’re in the process of using it.

In peacetime, everything is different. You don’t know who your next opponent is going to be, so you need to keep options open. You don’t know if you’ll have a war before the equipment you just bought rots away. You don’t want wartime production levels and stifling your wider economy. You also don’t want a Russia situation where you ignore value for money estimates and audits only to find the money you spent on missiles went in the back pocket of a random colonel.

> During wartime you need lots of materiel quickly, so value for money estimates, anti corruption practices all get reduced in the name of production numbers at all costs

Everyone keeps saying this yet it seems to be the opposite, results for dollars tradeoffs are better in wartime.

If anything it seems like the difference is that during wartime it's easier for the end users to tell the bureaucracy to get out of the way and as a result value for money is unchanged or even improved.

>You also don’t want a Russia situation where you ignore value for money estimates and audits only to find the money you spent on missiles went in the back pocket of a random colonel.

There is no difference to the taxpayer or the soldier in the trench whether the money went into one specific colonel's back pocket or got pissed away on running organizational process. The money is gone and the missile isn't there.

At you can least throw colonel in jail (or out a window, because Russia). Imagine if instead of a colonel's pocket the money was spent pushing papers around to no end? It would be the Spiderman pointing at Spiderman meme and nobody would be held responsible except perhaps an unlucky scapegoat.