Defense Secretary Pete Hegseth wants one, and he’s on the right track. Critical to that will be his willingness and ability to fire the bureaucrats in DoD who stay in the way of the critical changes Hegseth wants, but that’s a separate story. What Hegseth wants is faster, more flexible acquisition processes that enable, rather than hinder, competition in acquisition and production and that foster rapid contract letting and fast production of the contracted for articles. In loose sum,

… Overregulation, diffused accountability, and insufficient competition [must be eliminated]. “Every process, every board, and every review must justify its existence,” the secretary said.
The Pentagon essentially wants to make faster and more flexible contracting authorities the default instead of the exception, and give more priority to the private economy to solve military problems.

One step along this evolution was this that the WSJ editors noted:

Welcome is concentrating more authority in a “portfolio acquisition executive,” who could oversee a suite of programs and make tradeoffs on cost and performance. The current system includes far too many layers of authority. “Program managers answer to dozens and dozens of folks” and “have to go get permission to move a dollar to a better priority,” a former US Navy secretary for acquisition told Congress this year.

Hegseth needs to be absolutely draconian in removing those extraneous layers and terminate the vast majority of the bureaucrats incumbent in them. Very few bureaucrats will warrant reassignment within DoD, and there are—or should be—very few open slots for reassigning into.

I add a couple of improvements to all of this. Hegseth wants to buy the 85% solution and iterate together over time to achieve the 100% solution, but as articulated, it’s insufficient, with too much room for weasel-wording added pricing costs by the contractor. Rather than simply jawboning against endless specs, requirements creep must be stopped cold. Changes to the specs often are warranted, but better is the enemy of good enough, preventing the good enough from being acquired at all, leaving us completely without. “Better” should be included in follow-on contracts—or new contracts—and only after “good enough” has been in operation for some years. That will determine whether that “better” really is and, if so, will provide justification for that “better” going to testing and production.

In parallel with cutting off requirements creep by the contractor, requirements creep by DoD personnel must be cut off, also. Those new and better requirements that come from Pentagon bureaucrats (and here I include the myriad flags and O-6s and O-5s looking for Efficiency Report material for the sake of their personal careers and/or for post-retirement employment with those contractors) must only be considered after the system they’re “improving” has been in the field, operationally employed for some years.

A second parallel is cutting off mission creep by DoD personnel. The system under consideration is being designed, built, and employed for a particular class (narrow or broad) of missions. If the mission changes, or a new mission is identified—and they will be—those needs can only be considered for the next upgrade to the existing system, or the changed/new mission’s needs will call for a new system.

And this: those systems will consist of a platform for carrying and delivering to the targets those bullets, bombs, missiles, drones, what-have-you that will do the destruction of the targets. Those platforms must be as generic as possible so as to be able to carry new and improved bullets, bombs, … with as little physical modification as possible, requiring only software upgrades (which means the platform’s computers must be capable handling the newer generations of software). The flip side of that must include the requirement that the upgraded/replacement bullets, bombs, … and software must be designed to fit onto the existing platform as much as possible. It’s certainly the case that a platform will wear out or the new and improved bullets, bombs, … and software will truly need a new platform, but those should be the greatly infrequent exception rather than the norm.