← ELI5 · Nestor G Pestelos Jr

What Is the OODA Loop?

How fighter pilots, chess masters, and smart AI robots outthink the competition by updating their mental map faster.

Story 1. The 40-Second Fighter Pilot

Imagine a fighter pilot named John Boyd. In dogfights, he could defeat any challenger in under 40 seconds—even flying an older, slower jet!

How did he do it? He realized that winning isn't about having the biggest engine or pulling the trigger the fastest. It’s about figuring out what is actually happening before the other person does.

Why did the other pilot lose?
The other pilot was reacting to where Boyd used to be two seconds ago. By changing maneuvers faster than the opponent could update their mental picture, Boyd created pure confusion in the opponent’s brain.

The 4 Steps 2. Observe, Orient, Decide, Act

Boyd turned his secret into a 4-step thinking engine called OODA:

👁️ 1. Observe
Look around
🧭 2. Orient
Make sense
🎯 3. Decide
Pick a plan
⚡ 4. Act
Try it out

The Secret 3. Orientation is the Real Boss

Most people think the OODA loop is a simple circle. But Boyd said Orientation is the center of gravity.

Two people can look at the exact same chessboard or crash report (Observe) and see completely different things. Why? Because their Orientation (their internal mental model, past experience, and training) is different!

Orientation blends 5 ingredients:
  1. Past Experience: Mistakes you survived before.
  2. Culture & Language: The concepts and words you have to describe things.
  3. Hardware / Biology: How much memory or energy you have.
  4. Fresh Clues: What your sensors just caught.
  5. Smash & Rebuild: Breaking old ideas apart when they stop working!

Pitfalls 4. The Three Big Traps

AI Agents 5. Why Coding Robots Use OODA

Autonomous AI agents (like Antigravity, Claude Code, or Hermes) aren't just autocomplete typing words—they are full OODA loops in software!

👁️ Observe: The robot reads terminal output, git diffs, and test failure traces.

🧭 Orient: The robot scans the repository architecture, loads project rules, and parses function ASTs.

🎯 Decide: The robot chooses which exact file edit or tool call will fix the bug.

⚡ Act: The robot writes the patch and runs the test suite to observe what happened!