How to Build with the Department of Defense

Episode Summary

Executive Summary: The episode argues that DoD procurement is not mainly a technology problem but a culture, incentives, and process problem. Army and Navy CTOs describe efforts to speed adoption, reduce bureaucracy, shift from program-of-record thinking to portfolio/outcome-based buying, and create clearer front doors for startups and commercial tech to reach the field faster.

Main Topics: DoD procurement as a “black box” (Priority: 5/5): The speakers explain that defense buying is hard to navigate because of legacy rules, dense requirements, and too many fragmented entry points. They frame this as an institutional/process issue rather than a technical one. From program-of-record to portfolio and outcomes (Priority: 5/5): The Navy and Army are trying to replace sacred, long-lived programs with more flexible portfolio management and capability-per-dollar decisions, so new tech can be adopted and older systems sunset faster. Accelerating startup and industry pathways (Priority: 4/5): They discuss SBIR/STTR, DIU, AFWERX, OTAs, software acquisition pathways, and other on-ramps, while arguing that startups still need simpler rules and direct access to units and requirement writers. Culture, incentives, and risk appetite (Priority: 5/5): A major theme is that acquisition culture rewards risk reduction and paperwork over mission outcomes. The guests argue the department should reward speed, experimentation, and measurable warfighting value instead. Horizontal/common services and scaling what works (Priority: 4/5): The conversation emphasizes building enterprise services for common needs like identity, maps, data, and AI so every service does not reinvent the same capability in its own silo. Real-world examples of rapid fielding (Priority: 4/5): The guests share examples where capabilities moved from prototype to field use in months, including C2 on an Android TAC device, edge compute on a ship, and an EW system fielded after being painted brown and mounted on a Humvee. Near-term defense tech priorities (Priority: 4/5): They highlight next-generation command and control, counter-UAS, autonomy, AI, and modular toolchains as areas where the department wants to scale proven commercial solutions quickly.

Key Arguments: The DoD’s slow adoption cycle is driven more by culture and process than by lack of technology; technology can be applied to fix the process. The government should buy outcomes and capability per dollar, not optimize around rigid program-of-record structures and thousand-page requirements documents. Startups should not need to understand the entire acquisition maze; the department should simplify entry points and meet companies where they are. Enterprise/shared services should handle common problems, while services focus on what is truly unique to their missions. Speed matters as much as correctness: if a better solution exists, the department should be willing to divest legacy systems and move quickly. Risk metrics used by acquisition personnel are misaligned with technology progress; spending slowly can be as harmful as spending wastefully. Direct proximity to operators/warfighters helps startups understand real problems and build useful solutions faster. The services are beginning to use data-driven A/B testing and outcome-driven metrics to prove that new solutions are superior to the old ones.

Data Points: Pentagon construction time: 16 months - Used as an example of historic government speed in the early 1940s. Manhattan Project duration: 3 years - Cited to show rapid federal execution during WWII. Explorer 1 response time after Sputnik: 84 days - Used to illustrate U.S. government responsiveness in the space race era. Program executive offices in DoD: 75 - Navy CTO describes the scale of procurement fragmentation across the department. Department of the Navy PEOs: 18 - Navy-specific subset of the broader 75 PEO structure. Army share of defense budget: 21% - Army CTO notes the service’s limited budget flexibility despite broad global responsibilities. Innovation activity share of budget: less than 1% - Describes how small innovation programs still are relative to total defense spending. In-Q-Tel leverage ratio: 25 outside dollars per 1 federal dollar - Used as a model for attracting non-federal capital into national security innovation. Requirements document length: 4,000 pages - Example of legacy acquisition bureaucracy that slows decision-making. Requirements compressed: 18-month process reduced to 3 months - Capability need statements and software acquisition pathways were used to accelerate fielding. EW prototype cost: $300K - An electronic warfare solution was rapidly adapted and fielded after cross-service collaboration. Pilot-to-production timeline: 30 days - Army CTO recalls quick reaction capability during the global war on terror being delivered to Afghanistan in about a month. A/B test scale: 100,000 reps - Used to show how cloud and simulation can prove value without lengthy live trials. Risk/reward framing: 51% vs. 49% - Example of a flawed requirement that effectively accepted a system working only 51% of the time. Identity management solutions: 1,000 - Navy CTO uses this as an example of excessive redundancy that enterprise services could consolidate. Navy/Army examples of fielding: Android TAC device on an M1A2 SEP V3 tank; Red Sea deployment; Humvee-mounted EW system - Illustrates rapid translation of commercial tech into operational use. Expected startup/industry scaling: 90% of portfolio (aspirational) - Army CTO argues the department should aim for a much larger share of portfolio decisions to reward breakthroughs.

Pivotal Quotes: "This is not a technology problem. This is a culture and a process problem that we can apply technology to." — Alex Miller: Summarizes the core thesis of the episode. "We want to overwhelm the system with how much better it can be." — Alex Miller: Describes the strategy for driving adoption by showing undeniable performance gains. "The U.S. Army should never trade blood for blood in first contract, and it should always be blood for an iron, and it should always be their blood." — Alex Miller: A forceful statement about prioritizing better equipment and autonomy over exposing soldiers to unnecessary risk.

Implications: For startups, the message is to build proven products, get close to operators, and avoid relying on DoD as the only market. For industry and government, the future is enterprise services, faster software pathways, and aggressive replacement of legacy systems with better outcomes.