By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.
a16zCan the Military Move at Startup Speed? How the Army and Navy Are Rebuilding
Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.
At a glance
WHAT IT’S REALLY ABOUT
Army and Navy CTOs Plan to Blow Up Acquisition Bureaucracy
- Army CTO Alex Miller and Navy CTO Justin Fanelli describe the DoD as a black box built on decades-old rules, and say they are working to cut through the bureaucracy rather than keep building workarounds.
- Fanelli explains the shift from programs of record toward portfolios and buying capability per dollar, while Miller argues PEOs are not in statute and wants to reshape anything below law.
- Both describe replacing thousand-page requirements with short capability need statements, citing a Navy process cut from 18 months to three and an electronic warfare system the Army fielded in three months for 300K.
- They stress enterprise and shared services across the services, modular vendors, and divesting legacy systems, while reserving unique mission needs for the services themselves.
- They argue the main barrier is culture and risk calculus, since acquisition staff are trained to avoid waste rather than lose time, and they invite startups to engage directly with units and bring data and success stories.
IDEAS WORTH REMEMBERING
5 ideasThe problem is culture and process, not technology
Miller says the issue is a culture and process problem that technology can be applied to, and that startups can't fix the department's inability to describe its own problems.
Requirements documents are a major drag
Fanelli cites a 4,000-page requirements document nobody read in full, and Miller describes one whose metrics implied a system that only had to work 51% of the time; both favor short capability need statements.
Programs of record create perverse incentives
Miller argues long-term budgets encourage maintaining inertia rather than improving, and says no startup should have to aim to become a program of record; Fanelli points to portfolio-based buying as a move toward 'military Moneyball.'
Overmatch requires order-of-magnitude improvements
Fanelli says switching is hard for a 15% gain, so vendors should show A/B results proving the old option is no longer viable, which enables divesting legacy systems.
Reuse across services and enterprise services saves effort
Examples include a hyper-converged edge compute box moving to ships and an electronic warfare system painted brown and put on a Humvee, plus Miller's story of 17 mission command programs each with their own mapping stack.
WORDS WORTH SAVING
5 quotesIt is shocking to me how much stuff we buy for soldiers that no one would accept if I handed it to you in your everyday life.
— Alex Miller
This is not a technology problem. This is a culture and a process problem that we can apply technology to.
— Alex Miller
Only superior military technology can credibly deter war.
— Justin Fanelli
If a quarterback was measured on not making mistakes versus throwing touchdowns or winning games, the performances would be 100% different, right?
— Justin Fanelli
The only reason it exists is because the process doesn't work.
— Alex Miller
High quality AI-generated summary created from speaker-labeled transcript.