TWEGSLog inThe OODA Loop.
A decision framework built for situations where the world fights back. Observe, Orient, Decide, Act — then immediately do it again. The point isn't completing the cycle. It's running it faster than whoever you're up against.
"He who can handle the quickest rate of change is the one who survives."
Col. John Boyd, USAF
Each phase has a different cognitive flavor.
Treating OODA as four equal steps is the most common mistake. They're not equal — they have different jobs, different failure modes, and one of them is much harder than the others.
Gather raw, unfiltered data about the current situation. What is actually happening — not what should be happening?
Failure mode: mistaking your model of the world for the world itself.
Make sense of what you observed — given your context, history, and biases. What does this mean, and what does it imply?
Failure mode: the hardest step. Most people skip it or do it badly.
Pick a hypothesis to test. Not the perfect answer — the best move given your current understanding.
Failure mode: waiting for certainty that won't arrive.
Execute the decision. Then — and this is the whole point — go back to Observe. The world has changed because you acted.
Failure mode: treating the action as the end, not the next observation.
Orient is the step. Everything else is plumbing.
Boyd spent more time on Orient than on the other three phases combined. Why? Because Observe gives you data, but data doesn't decide anything — interpretation does. And interpretation is where your mental models, biases, cultural assumptions, and past experiences either help you see clearly or make you blind. Two people can observe the same thing and orient to opposite conclusions. The one whose orientation matches reality wins.
Run two OODA loops on a real situation.
Pick a scenario or use one of your own. We'll walk you through one full cycle — and then immediately a second one, with new information that the world threw at you while you were acting. That second loop is where the framework actually teaches.
Pick your situation
Choose a scenario or load your own. Real situations work better than hypothetical ones.
When to reach for it — and when not to.
OODA is built for fluid, adversarial, fast-moving situations. It's overkill — and even harmful — for stable decisions where deliberation pays off.
- The situation is changing in real time and waiting for full information costs you something.
- There's a competitor, adversary, or counterparty actively responding to your moves.
- You're in crisis mode and need to act with imperfect data — letting a small action teach you more than a big plan.
- The team is paralyzed by analysis — running one quick loop gets the wheel moving again.
- The decision is irreversible and high-stakes — slow it down, run a Pre-Mortem instead.
- The situation is stable and waiting for better data is costless.
- You're in a domain where being wrong has compounding costs (regulated industries, safety).
- You'd be using OODA as cover for restless, reactive thrashing — that's not iteration, it's anxiety.
Col. John Boyd, US Air Force.
Boyd developed the OODA Loop while studying why American pilots in Korea won dogfights at a 10-to-1 ratio against technically superior MiG-15s. His answer: the F-86 had better visibility and a faster control system, letting pilots cycle through observation and reaction faster than their opponents — even when their opponents had better planes.
He spent the rest of his life arguing this principle generalized. Whoever can iterate faster — whether in air combat, business, or politics — disorients the slower party until they collapse. The framework now appears in Marine Corps doctrine, hedge fund strategy, and startup playbooks.
"The key to victory is to operate at a faster tempo than the adversary. We need to bring our adversary inside our O-O-D-A loop."