Reforming the Defense Innovation Ecosystem
Published: January 19, 2026
Federal Market AnalysisAcquisition ReformDEFENSEInnovationPolicy and LegislationResearch and Development
The DOD’s new organizational structure will support rapid prototyping and acquisition.
On January 9, 2026, the Secretary of Defense/War published “Transforming the Defense Innovation Ecosystem to Accelerate Warfighting Advantage,” a memorandum that fundamentally restructures the Department of Defense’s technology innovation ecosystem under a single Chief Technology Officer (Under Secretary for Research & Engineering).
Organizational Changes
The Under Secretary for R&E becomes the sole CTO in the new structure with authority over all technology innovation in the DOD. Three existing bodies are immediately disestablished by the guidance (the Defense Innovation Steering Group, Defense Innovation Working Group, and the CTO Council) and replaced by a single CTO Action Group for streamlined decision-making.
The Defense Innovation Unit (DIU) and Strategic Capabilities Office (SCO) are also reframed as DOD Field Activities, giving them new authorities and streamlined governance while maintaining small, fast organizational models. Congress will need to certify this change to make it permanent.
The memo further establishes three distinct innovation categories and the technical leads over them:
- Technology Innovation (the Defense Advanced Research Projects Agency leads) - defense-unique capabilities, often classified.
- Product Innovation (the DIU leads) - commercial/dual-use technology adoption.
- Operational Capability Innovation (the SCO leads) - combining technologies with new tactics/doctrine.
Key Requirements for Services and Programs
Military department heads must brief the CTO within 90 days on how they're organizing their innovation communities (labs, rapid capabilities offices, software factories) around the three innovation categories listed above. Then, starting FY 2028, every Portfolio Acquisition Executive (PAE) must fund a dedicated Innovation Insertion Increment (III) for rapid capability insertion that is sized to portfolio scale and tracked through quarterly CTO Action Group reviews.
As for industry partners, the currently fragmented approach to defense innovation is replaced by two complementary channels that provide “clear demand signals.” These are the Mission Engineering and Integration Activity (MEIA), which will work with industry to solve the Joint Force's top Operational Problems. The DIU, meanwhile, will execute product-driven engagement in support of its mission and CTO adoption priorities, i.e., helping PAEs and program offices better adopt what industry has built.
Implications for Government Contractors
Industry partners will need to clarify which innovation pathway their capabilities align with. For defense-unique technology, DARPA remains your avenue. For commercial/dual-use products ready for production, DIU becomes the front door. For operational concepts that combine existing systems in new ways, SCO is your contact.
The consolidation from multiple department front doors to two industry engagement channels (MEIA for problems, DIU for products) means contractors should reassess their DOD engagement strategies. If you've been navigating multiple overlapping innovation organizations, this simplification could streamline your business development efforts. Just be sure to align your efforts with the right channel as soon as possible.
New emphasis on "adopt faster than our adversaries can copy" signals a shift from build-to-spec toward adopting external commercial innovation. If your company has been simply responding to requirements documents, you should develop a more proactive product development strategy that demonstrates your capability before solicitations appear.
In addition, the memo's emphasis on operational capability innovation means offering a technology solution alone won't guarantee a win. Contractors will need to articulate tactical applications and operational concepts alongside their products. Partnering with experienced operators to align with the "new ways of fighting" narrative could make a difference.
Lastly, small, fast organizations, such as the DIU and SCO, are being made field activities to preserve their agility. This suggests the acquisition environment will increasingly favor rapid prototyping, production-ready commercial products, and contractors who can move at venture-backed speed rather than along traditional defense timelines.