Framework

OODA Loop

John Boyd's four-stage decision cycle — Observe, Orient, Decide, Act — for fast, adaptive calls under pressure, run as a loop.

OODA Loop Find this on the mind-map

Introduction

John Boyd was a U.S. Air Force colonel and fighter pilot turned military strategist, and he built this loop to answer one question: why did some pilots survive aerial dogfights while others didn't? The answer wasn't strength or flying hours. The pilots who processed new information faster and acted on it stayed ahead of the situation — Boyd just named what they were already doing without realizing it. The model has since spread from the military into business strategy, emergency response, cybersecurity, and leadership, because all of them share the same condition: fast decisions made under real uncertainty.

How It Works

OODA Loop diagram

Stage The question it answers
Observe What is happening? What are the facts, and what's missing?
Orient What does this mean in context? What assumptions and mental models am I filtering it through?
Decide Based on what I now see and believe, what's the smartest next move?
Act Execute — then immediately loop back and observe what the action produced.

Two things set this apart from other decision models.

The first is speed. The goal is to cycle through the loop faster and better than the chaos around you. Boyd's insight was that a faster loop doesn't win by being smarter — it wins by staying ahead of the other side's ability to orient and respond.

The second is Orient. It's the heart of the loop, and the stage you're most likely to skip. Orientation is where raw observation gets interpreted, and it never happens in a vacuum — it runs through your biases, your beliefs, your past experience, your team's values, and whatever your company is prioritizing right now. Your orientation determines what you even notice in the first place.

Why It Matters for Leaders

The hard part of a leadership decision is rarely the decision itself. It's the time pressure sitting around it. New inputs keep arriving, you're still processing the last meeting, and something new lands in your inbox marked urgent. Under those conditions, you tend to do one of two things: overthink, or default to whatever you did last time.

OODA gives you a third option. It turns a wide-open problem into four small questions you can answer in minutes, then repeat. That matters most in three situations you'll recognize.

Prioritization chaos. Fourteen items on your list, three marked urgent, two blockers from the team, and a new top priority just handed down from your boss. A fast loop asks what's actually at risk, reads your team's energy and the week's real business priority, picks one or two things that unblock everything else, and communicates the plan. You trade reaction for intention.

Firefighting. An outage or an escalation puts everyone on edge, and the temptation is to fix something fast just to look in control. Acting before you orient usually makes it worse. Nail down what's actually known versus what's rumor, then define a first move — isolate the issue, name an owner — and you cut the panic instead of adding to it.

Ambiguity. A poorly defined project with a vague goal and no roadmap paralyzes most people. This is ideal OODA territory, because every cycle produces a little more clarity. The project moves out of the fog not because you solved everything, but because you solved something.

If you never run the loop on purpose, you tend to fail in one of two directions: stuck in Observe, waiting for clarity that never arrives, or skipping Orient entirely and acting on a guess dressed up as decisiveness.

Your chat with Kyoshi about the OODA Loop framework

What to do next

Test your knowledge of OODA Loop

Take the quiz →

Practice OODA Loop

Apply OODA Loop to a real situation

Skills related to OODA Loop

Frameworks related to OODA Loop

Books related to OODA Loop