OODA Loop: The Fighter Pilot Framework Jamie Dimon Uses for Trillion-Dollar Decisions (And You Can Use Tomorrow)

· 5 min read

OODA Loop: The Fighter Pilot Framework Jamie Dimon Uses for Trillion-Dollar Decisions (And You Can Use Tomorrow)

Jamie Dimon, CEO of JPMorgan, credits part of his success to a military framework created in the 1960s.

It's not an MBA. It's not strategic consulting. It's the OODA Loop.

And 90% of people who know it are using the wrong part.

The Framework That Changed Aerial Warfare (And Business)

John Boyd was a fighter pilot. His obsession: understanding why some pilots won dogfights even with inferior aircraft.

He discovered it wasn't the plane's speed. It was decision speed.

He created the OODA Loop:

  • **Observe**: Gather information from the environment
  • **Orient**: Process that information through your context
  • **Decide**: Choose a course of action
  • **Act**: Execute the decision

Seems simple. And that's the trick.

Why Everyone Gets It Wrong

Most articles about OODA focus on the complete cycle. "Iterate fast." "Decide faster than your competition."

They're missing the point.

Boyd discovered that Orient is where you win or lose everything.

Orienting isn't just processing information. It's filtering it through:

  • Your past experience
  • Your cultural context
  • Your mental models
  • Your analysis of the situation
  • Your synthesis capability

Two people can observe exactly the same thing and reach completely different decisions because their Orientation phase is different.

The Secret Boyd Discovered (And Dimon Applies)

Here's where it gets interesting:

If you can disorient your competition, you win before the battle starts.

Boyd called it "getting inside their OODA loop."

In aerial combat: you make a move your opponent can't interpret with their mental models. While they try to understand what happened, they've already lost.

In business: Dimon uses it to anticipate market moves that other banks don't see coming. Not because he processes information faster, but because his Orient phase includes contexts others ignore.

For founders: It's building something the market doesn't know how to categorize yet.

How I Apply It In My Projects

When evaluating whether to build a new project, my OODA Loop is this:

1. Observe (1 day)

  • What are people saying on Reddit/Twitter/forums?
  • What solutions already exist?
  • What are early adopters using?

2. Orient (2-3 days) - This is where the value is

I don't just process the info. I filter it against:

  • **Circle of Competence**: Can I build this with my current stack? (Next.js, Supabase, Claude)
  • **CENTS Framework**: Does it have control, scalable entry, need, time, and scale?
  • **Anti-fragile mental model**: Does this make me stronger even if it fails?
  • **Spanish/European market context**: Do regulations help or complicate this?

Most founders jump from Observe to Decide. They lose all the value.

3. Decide (30 minutes)

With good orientation, deciding is trivial. It's a clear yes or no.

4. Act (2 weeks for MVP)

Build fast because I already know I'm building the right thing.

Contrast With Traditional Frameworks

Typical business frameworks (Business Model Canvas, Lean Canvas, etc.) are static.

They make you think at a point in time.

OODA is dynamic. It assumes the environment changes while you decide.

That's critical in 2025, where:

  • AI models improve every month
  • No-code tools eliminate barriers every week
  • Your competition can appear from India or Argentina overnight

A 50-page Business Plan is obsolete before you finish it.

A well-executed OODA Loop keeps you relevant because you keep iterating.

The Real Advantage: Orient Better, Not Faster

Here's the insight that changed how I build:

You don't need to iterate faster than your competition.

You need to orient better.

If your Orient phase includes mental models your competition doesn't use, you reach decisions they don't even consider.

Examples of how I improve my Orient:

  • I read Munger, Naval, Howard Marks - they give me different lenses to see problems
  • I build in public - constant feedback updates my orientation
  • I use Claude to process information in non-obvious ways
  • I maintain Shoshin (beginner's mind) - prevents my experience from limiting my orientation

Each mental model is an extra filter in my Orient phase.

How to Start With OODA Tomorrow

For your next product decision:

1. Observe (without judging): - Collect objective data - Don't interpret yet - Include data that contradicts your beliefs

2. Orient (invest time here): - What mental models apply here? - What is my competition seeing that I'm not? - What am I seeing that they ignore? - Are my assumptions still valid?

3. Decide (should be easy if Orient was good): - If the decision is hard, go back to Orient - Good orientation makes decisions obvious

4. Act (fast and complete): - Execute with conviction - But keep sensors active (return to Observe)

Common trap: Confusing speed with effectiveness.

Boyd didn't win by being fastest. He won because his Orient was superior. He saw combat in ways his opponents couldn't.

The Meta-Game

The most powerful thing about OODA: you can use it to improve your own OODA.

  • Observe how you make decisions
  • Orient on what mental models are limiting you
  • Decide what frameworks to add to your toolkit
  • Act by incorporating them into your next cycle

It's a recursive framework.

And that's exactly what makes it so powerful for founders and builders.

Takeaway

OODA Loop isn't about deciding fast.

It's about orienting better.

Next time you have to make a product or business decision:

Don't rush to Decide.

Stay in Orient.

Add a mental model your competition doesn't use.

Process the information in a way they don't consider.

And when you finally decide, it will be obvious what to do.

While your competition is still trying to understand what changed in the market, you'll already be three moves ahead.

That's OODA well executed.

And you don't need to be a fighter pilot (or a bank CEO) to use it.

Brian Mena

Brian Mena

Software engineer building profitable digital products: SaaS, directories and AI agents. All from scratch, all in production.

LinkedIn