a16zEmil Michael: The Department of War Is Moving Faster Than Silicon Valley on AI | The a16z Show
CHAPTERS
Emil Michael’s path from Silicon Valley to Defense CTO
Emil Michael explains how a post-acquisition break from tech led him into government through the White House Fellows program, where he worked under Secretary of Defense Robert Gates. That experience created a lasting interest in national security, setting up his return to public service years later.
Why “wartime speed” is necessary now (and how peacetime speed took hold)
Michael argues the Department of War/Defense cannot operate with the post–Cold War tempo that encouraged consolidation and slower innovation. He frames today’s urgency around China’s historic military buildup and U.S. reliance on fragile, often offshore supply chains.
Supply-chain fragility as a national-security risk (the Skydio example)
Ulevitch highlights how sanctions and geopolitical dependency can instantly break defense readiness when critical components are sourced abroad. The discussion emphasizes that the defense industrial base includes upstream “precursors,” not just final weapons systems.
Cutting 14 priorities down to 6 to drive execution
On entering the role, Michael found an outdated, overly broad list of 14 “critical priorities” that had barely changed in a decade. He narrowed them to six to improve focus, clarity, and workforce alignment—putting applied AI at the top.
Applied AI: reorganizing for speed and driving adoption at scale
Michael describes moving the Chief Digital and AI Office into his organization to accelerate deployment. He claims rapid adoption across the workforce, citing a jump from tens of thousands of users to over a million using AI tools in roughly 90 days.
Where AI helps most: enterprise efficiency, intelligence, and warfighting/logistics
Michael breaks defense AI into three buckets: back-office productivity, intelligence analysis, and warfighting applications like logistics and planning. He stresses that AI can unlock value from massive, siloed datasets and multiply analyst throughput via anomaly detection and pattern discovery.
Commercial AI models in defense: restrictions, single-vendor risk, and operational exposure
Reviewing prior contracts, Michael says he discovered extensive use restrictions and a dangerous level of vendor lock-in within sensitive operational commands. He warns that if model behavior or terms-of-service constraints can disable capability mid-operation, it creates unacceptable risk to missions and lives.
The Maduro raid catalyst and the clash between company values and lawful military use
Michael cites a moment when a vendor questioned whether its software was used during a successful raid, which raised alarms about external influence over lawful operations. He argues that as AI approaches a “substrate” like the internet, private model constitutions cannot supersede democratically authorized command decisions.
Democratic oversight, civil liberties, and guardrails (without self-handicapping)
The conversation emphasizes that guardrails for defense AI should flow from U.S. law and democratic processes, not private actors. Michael notes existing directives on autonomy and argues adversaries are removing guardrails and stealing models—making unilateral restraint strategically dangerous.
What “good” looks like: multiple frontier partners and never being single-threaded again
Michael argues the U.S. needs redundancy and choice among frontier AI providers to avoid lock-in and policy shock. He references the post-2018 Project Maven shift—where some firms initially resisted government work but later became strong partners—as a model for today’s AI companies.
Fixing procurement bureaucracy: simpler requirements and firm fixed-price outcomes
Michael describes a push to dismantle bureaucratic processes that favor slow, cost-plus development and unrealistic requirement lists. He advocates outcome-based requirements, faster cycles, risk-sharing, and fixed-price structures—citing the SpaceX-style incentive model as a blueprint.
What startups must deliver: production scale, real buying signals, and faster yes/no decisions
Michael advises startups that primes’ key advantage is manufacturing and scale, not inventiveness—so new entrants must build production muscle and quality systems. He also urges founders to look for real procurement signals (tests, buys) and supports a cultural shift toward faster decisions so startups aren’t trapped in endless maybes.
Why serve: rebuilding the culture of government service and patriotism in tech
In closing, Michael explains his motivation to serve as an immigrant who benefited from the U.S. system and wants his children to see that national strength requires sacrifice and builders. He calls for more technologists to view public service as an honored profession again, akin to historic moments like the Manhattan Project.
Get more out of YouTube videos.
High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.
Add to Chrome