We scan new podcasts and send you the top 5 insights daily.
Establishing a combatant command to lead autonomous weapons transformation misunderstands how combatant commands function. These commands prioritize immediate, near-term operational problems, rendering them susceptible to vendor pitches while operating on the periphery of the Pentagon's core budgeting processes. Historically, enduring force transformation has required service staff institutions, program and budgeting levers, and demand signals rather than operational warfighting headquarters.
Creating a dedicated 'AI Force' is counterproductive. By segregating expertise, it prevents AI from becoming a ubiquitous, force-wide capability. This approach risks creating an isolated bureaucracy rather than raising the median AI competency of the entire military, which is the actual goal.
Forcing autonomous platforms to integrate directly into manned combat units compromises their unique operational value. Autonomous systems possess distinct risk profiles, greater persistence, and expendability compared to crewed platforms. Subordinating them to human formations forces them to operate merely as extensions of manned tactics rather than enabling distinct operational concepts, specialized reach, and independent formations.
Innovation initiatives from entities like the DIU or OSD are destined to fail unless a military service champions the technology and integrates it into its budget. Services have enduring priorities and will not fund external projects long-term, regardless of top-down pressure. You must bring them along culturally.
Debates over military budgets are often implicitly debates about the discount rate of combat power. In an era of rapid AI-driven change, power delivered in 10 years is heavily discounted. This framework favors immediate software and autonomy investments over long-term hardware programs.
The military lacks the "creative destruction" of the private sector and is constrained by rigid institutional boundaries. Real technological change, like AI adoption, can only happen when intense civilian leaders pair with open-minded military counterparts to form a powerful coalition for change.
A reform-minded leader can create ad-hoc teams and force collaboration between operators and technologists. However, these changes are often temporary. Once the leader departs, the military's established cultural norms and organizational structures, like powerful four-star commands, tend to reassert themselves, erasing the progress.
The Department of Defense (DoD) doesn't need a "wake-up call" about AI's importance; it needs to "get out of bed." The critical failure is not a lack of awareness but deep-seated institutional inertia that prevents the urgent action and implementation required to build capability.
Rather than standing up a permanent four-star functional command for autonomous weapons, the Department of Defense would field systems faster through temporary, sunsetting task forces. A permanent combatant command creates layers of subordinate two-star headquarters and self-preserving equities that become impossible to dislodge. A focused task force can formalize tactical lessons into field doctrine without creating an unmanageable general-officer bureaucracy.
Creating a centralized four-star command for autonomous weapons risks stalling real-time testing conducted by theater task forces. Rather than accelerating deployment, a centralized headquarters introduces committee-driven staffing processes, hundreds of headquarters personnel, and bureaucratic delays. Distributed experimentation at the tactical edge allows faster operational feedback and prototyping than a centralized Pentagon clearinghouse can provide.
Creating a separate command for drones and autonomy could segregate these capabilities, much like CyberCom. Instead of being integrated into combined arms at the lowest level, they become a resource that operational commanders must request through layers of bureaucracy, hindering agility.