Welcome to a special series on the acquisition talk podcast that gives you an audiobook tour of my research project titled, Programmed to Fail: The Rise of Central Planning in Defense Acquisition 1945 to 1975. I’m Eric Lofgren of the Baroni Center for Government Contracting at George Mason University. You can find this book for free and over 1,300 blog posts on my website, AcquisitionTalk.com.

In this third episode, we look at the 1950s debates over how weapons development should proceed. The listener will find strong parallels to the modern debates over waterfall vs. agile development practices. Weapons development in the 1940s and 50s followed an agile method of iterative and incremental decisions made by small, empowered teams. Yet this practice became supplanted by the belief that iteration and competitive developments revealed a failure to plan, and that planning could relieve all uncertainties in weapons development.

As you listen to the story, consider how weapons today are expected to proceed linearly from science, to prototyping, to full scale development, production, then operations and sustainment. There is little or no room for feedback mechanisms and learning.

However, another important aspect of software today is not just agile development, but continuous development and deployment of capability in what is called devops. The lines between development and production are not as clear today as they were presented in the hardware-oriented world of the 1950s. 

Listen in on our third chapter of the Programmed to Fail story, this time focusing of the emerging religion of systems analysis, a religion which continues to pervade the defense acquisition system 70 years later.

This podcast was produced by Eric Lofgren. You can follow me on Twitter @AcqTalk and find more information at AcquisitionTalk.com

Programmed to Fail - 3. Systems Analysis

International Policy students will be spending their careers in an AI-enabled world. We wanted our students to be prepared for it. This is why we’ve adopted and integrated AI in our Stanford national security policy class – Technology, Innovation and Great Power Competition.

Here’s what we did, how the students used it, and what they (and we) learned.

Teaching National Security Policy with AI

We just finished our 10th annual Hacking for Defense class at Stanford.

What a year.

Hacking for Defense, now in 70 universities, has teams of students working to understand and help solve national security problems. At Stanford this quarter the 8 teams of 41 students collectively interviewed 1106 beneficiaries, stakeholders, requirements writers, program managers, industry partners, etc. – while simultaneously building a series of minimal viable products and developing a path to deployment.

Hacking for Defense @ Stanford 2025 – Lessons Learned Presentations

We just finished the 15th<>annual Lean LaunchPad class at Stanford. The class had gotten so popular that in 2021 we started teaching it in both the winter and spring sessions.

During the 2025 spring quarter the eight teams spoke to 935 potential customers, beneficiaries and regulators. Most students spent 15-20 hours a week on the class, about double that of a normal class.

Lean Launchpad at Stanford – 2025

I’ve been having coffee with lots of frustrated founders (my students and others) bemoaning most VCs won’t even meet with them unless they have AI in their fundraising pitch. And the AI startups they see are getting valuations that appear nonsensical. These conversations brought back a sense of Déjà vu from the Dot Com bubble (at the turn of this century), when if you didn’t have internet as part of your pitch you weren’t getting funded.

Why Investors Don’t Care About Your Business

How did you go bankrupt?”
Two ways. Gradually, then suddenly.”
Ernest Hemingway, The Sun Also Rises

Every disruptive technology since the fire and the wheel have forced leaders to adapt or die. This post tells the story of what happened when 4,000 companies faced a disruptive technology and why only one survived.

Blind to Disruption – The CEOs Who Missed the Future

How To Sell to the Dept of War – The 2025 PEO Directory

When Sh!t Hits the Fan – Founders in a Crisis

Tons of words have been written about the Trump Administrations war on Science in Universities. But few people have asked what, exactly, is science? How does it work? Who are the scientists? What do they do? And more importantly, why should anyone (outside of universities) care?

No Science, No Startups: The Innovation Engine We’re Switching Off

The October 2025 PEO Directory – Update 2.

The Department of War (DoW) is one of the world’s largest organizations.  If you’re a startup trying to figure out who to call on and how to navigate the system, it can be – to put it politely – challenging.

How to Sell to the Dept of War – The 2025 PEO Directory – Now with 500 more names

I’ve always thought of myself as a practitioner. In the startups I was part of, the only “strategy” were my marketing tactics on how to make the VP of Sales the richest person in the company. After I retired, I created Customer Development and co-created the Lean Startup as a simple methodology which codified founders best practices – in a language and process that was easy to understand and implement. All from a practitioner’s point of view.

It only took 20 years, but the Strategic Management Society now Believes the Lean Startup is a Strategy

A podcast on the management, technology, and political-economy of weapon systems acquisition.

Programmed to Fail - 3. Systems Analysis

Acquisition Talk

Related tracks