OODA is about tempo, not decision quality
18 Apr 2026
The OODA loop — Observe, Orient, Decide, Act — was developed by US Air Force Colonel John Boyd in the 1950s after analysing why American F-86 pilots dominated technically-superior Soviet MiG-15s in the Korean War at roughly 10:1. Boyd’s conclusion: the F-86 wasn’t winning through better decisions, it was winning through faster cycling. By the time the MiG had completed its loop, the F-86 had already cycled three times. The MiG was always responding to a world that no longer existed.
This is the insight most people miss: OODA is about tempo, not quality. The pilot whose loop runs faster gets inside the slower pilot’s loop, forcing them to respond to stale information.
The four stages
| Stage | What it is | Where most people fail |
|---|---|---|
| Observe | Collect raw data from the environment | Confuse observation with interpretation |
| Orient | Synthesise data through your existing models, history, biases, culture | Loop here forever — this is overthinking |
| Decide | Choose the next action | Defer decisions or decide impulsively (skip Orient entirely) |
| Act | Execute, then return to Observe | The execution gap — where good decisions die |
Orient is the crux. Boyd believed Orient was the most important stage because it determines what you see, how you decide, and what action even feels available. A bad Orient corrupts every other stage — you observe correctly, but you interpret through the wrong lens, decide on the wrong basis, act in the wrong direction.
Speed without quality is just impulsivity
The trap: confusing “fast cycling” with reactive decisions. Speed only beats slowness when the cycles are complete — actual Observe, actual Orient, actual Decide, actual Act. Otherwise you’re just generating noise faster than your opponent.
Nested tempos
The OODA loop runs at multiple time scales simultaneously, each acting as a safety net for the one below it failing:
- Real-time (seconds): trigger response
- Daily (5-min journal at night): catch what real-time missed
- Weekly (Sunday review): catch what daily missed
- Quarterly (strategic review): restructure if patterns persist
Each tempo’s job is to catch what the faster tempo couldn’t. A miss at one level doesn’t ruin the system if the next level catches it.
Why this matters outside fighter pilots
Your “opponent” doesn’t have to be a fighter pilot. It can be a competitor in business (the original use case beyond combat), a negotiation counterpart, a deadline, or your own past version. Each of those runs its own loop. The faster, more complete loop wins — provided the cycles are complete and the Orient stage is honest.