To attract innovation, the DoD is shifting its procurement process. Instead of issuing rigid, 300-page requirement documents that favor incumbents, it now defines a problem and asks companies to propose their own novel solutions.

The Army's "Transforming in Contact" initiative abandons long development cycles. Instead, it saturates units with abundant new technology, allowing soldiers to rapidly iterate and provide feedback on what is truly effective in the field, accelerating modernization.

Rather than passively waiting for government RFPs, Johnson's team often identified a military need and submitted a complete proposal before an official requirement existed. This positioned them as strategic partners who defined the problem, not just vendors who solved it.

Unlike the US model of a single "drone guy" per platoon, Ukraine has entire battalions focused on drone warfare. These units have frontline labs that debrief missions and iterate on drone technology within days, creating a dramatically faster innovation cycle.

In AI, low prototyping costs and customer uncertainty make the traditional research-first PM model obsolete. The new approach is to build a prototype quickly, show it to customers to discover possibilities, and then iterate based on their reactions, effectively building the solution before the problem is fully defined.

Instead of perfecting AI in a lab, Project Maven deliberately deployed flawed, early-stage systems to frontline operators. They accepted initial user frustration and system failures as a necessary cost to gather real-world feedback and rapidly iterate, a stark contrast to traditional, slow-moving military procurement.

To combat slow, costly development cycles, the Department of War is shifting from hyper-specific requirement documents to stating clear, high-level objectives (e.g., 'I need a missile that goes this far'). This new model empowers innovative companies to propose their own solutions and moves to fixed-price contracts.

The traditional product workflow—writing PRDs, waiting for mocks, then building a prototype—is being collapsed by agentic tools. A single "Builder PM" can now perform user research, generate PRDs, create functional mocks, and build a working prototype, drastically shortening the feedback loop.

The best way for entrepreneurs to find a meaningful problem in the defense sector is not through research papers but by directly engaging with end-users. The advice is to go to naval bases, listen to the pain points of sailors and marines, and identify high-impact challenges worth solving.