Pentagon’s software reforms prioritize speed, but critics warn of deeper systemic flaws

The Pentagon’s new Software Acquisition Pathway, mandated by Defense Secretary Pete Hegseth’s 6 March memo, aims to fast-track how the Department of Defense buys, deploys, and updates software. By exempting software programs from the milestones of Major Defense Acquisition Programs (MDAPs), the pathway expedites deployment, agile practices, and annual updates. However, critics argue that in pursuit of speed, DOD is sidelining oversight, introducing new risks, and failing to address deeper structural issues.

While proponents celebrate reduced bureaucracy and faster timelines—example: contracting vendors for the Replicator drone initiative in just 110 days—veteran acquisition experts warn of unintended consequences. A former Air Force official told Air & Space Forces Magazine that speed alone is a flawed metric: “The question should be, does it work under fire?”

The increasing use of OTAs for production contracts has also raised concerns. With low entry barriers via platforms like Tradewinds, DOD’s AI-focused OTA marketplace, unproven firms could land multimillion-dollar no-bid contracts based on a five-minute pitch. The Pentagon now requires undersecretary-level approval for OTAs over $100 million.

Beyond procurement, experts point to cultural and technical obstacles. “Software is still the backroom of the Pentagon,” said analyst Jacquelyn Dopkeen. Pilots still dominate top Air Force roles, and few acquisition professionals “speak software.” Programs like DIU’s ICAP are helping train a more software-literate workforce, but structural inertia remains.

Additionally, legacy code and network restrictions create technical debt that delays updates and limits toolsets for developers. “You can’t move fast when you’re blocked from using modern tools,” one source noted.

Critics argue the Pentagon’s acquisition overhaul tackles process but not the root problem: its outdated infrastructure and mindset. “If you want to move fast,” Dopkeen said, “you need to fix the way software is built and maintained on military networks—not just how it’s bought.”