Every AI pitch deck sells the same promise: faster decisions. Get inside your competitor’s decision cycle, act before they can react, win on speed. But someone who spent years flying C-17s into places where a bad call costs lives thinks speed is the easy part and the part almost everyone gets wrong. The real edge is knowing which calls a machine should never be allowed to make.
This week on the Project Flux podcast, Nate Amidon, a former US Air Force C-17 pilot turned technology consultant and founder of Form 100 Consulting, unpacks what military decision-making teaches us about deploying AI on high-stakes projects: trust, governance, and the discipline to keep a human accountable when the outcome actually matters.
🎧 Short on time? Hit play here — a grounded, hype-free conversation about AI, the OODA loop, and why governance is the thing that actually lets you move fast.
Amidon frames the whole conversation around the OODA loop — observe, orient, decide, act — the decision cycle fighter pilots live by. AI is extraordinary at the first two steps: it can observe more data and orient faster than any human team. The temptation is to hand it the last two as well. His warning is that decide and act are where judgment lives, and a model that can discern patterns is not the same as one that can be held responsible for a decision. Speed without accountability isn’t an advantage, it’s a liability waiting for an audit.
That’s why he spends as much time on governance as on capability. Drawing on the consulting work he now does at Form100 Consulting , he argues that the organisations getting AI right treat it like any other high-risk system: clear SOPs, defined risk ownership, and a way to verify what the machine produced. Trust in AI-generated reporting collapses the moment you can’t prove provenance — which is why watermarking and the authenticity of AI output isn’t a compliance box to tick, it’s the foundation the whole thing stands on.
He’s genuinely optimistic about where this goes. AI taking on longer-horizon tasks and freeing people for the creative and relational work only humans do well. But he’s blunt about the failure mode: teams that over-rely on AI in project management quietly lose the very judgment that made them worth trusting in the first place. The skill worth protecting isn’t prompting the model faster; it’s knowing when to override it.
Why it matters: the discipline that keeps a C-17 in the air is the same discipline that makes AI safe to deploy on a live project — govern the system, verify the output, and never let speed talk you out of accountability. Move fast on observe-and-orient; stay human on decide-and-act.
Links and Stuff
Nate Amidon on LinkedIn — linkedin.com/in/nateamidon
Listen on
Project Flux podcast: this episode on Buzzsprout
Apple Podcasts [VERIFY episode-level link]
Spotify [VERIFY episode-level link]
In partnership with
4x your communication output. Same quality. No burnout.
The bottleneck isn't what you want to say — it's how long it takes to type it. Wispr Flow removes the bottleneck.
Speak naturally and get polished, send-ready text for executive summaries, client updates, board recaps, investor notes, or just the 30 Slack messages you're behind on. Flow strips filler, formats numbers and lists, and preserves your tone.
Used by teams at OpenAI, Vercel, and Clay. 89% of messages sent with zero edits. Works in every app on Mac, Windows, and iPhone.
Enjoyed this? Project Flux breaks down the week’s most important AI and tech news every Monday. Subscribe to the free newsletter here and get a step ahead on the world of AI.
Project Flux is independently owned, funded, and operated by its founder. Any external references or features are for community benefit only and do not imply endorsement, control, or ownership.