OODA Loop

Overview

Colonel John Boyd (1927-1997) derived the OODA Loop from Korean War air-combat data: the F-86 Sabre achieved a ~10:1 kill ratio over the technically superior MiG-15 because better cockpit visibility and hydraulic controls let pilots cycle Observe → Orient → Decide → Act faster — the slower pilot was always reacting to obsolete information.

The strategic claim: whichever side cycles faster wins — but the bottleneck is almost always Orient (the synthesis step), not raw speed. A team that orients badly just produces wrong decisions faster.

Composes with metacognition (Orient is where reasoning errors surface), feedback-loops (OODA is a competitive feedback loop), first-principles (orient from bedrock, not inherited belief), and momentum-and-form (cycle-time advantage builds momentum).

When to Use

• Competitor outmaneuvers you despite your better resources, capital, or product
• Decisions take longer than the situation allows; losing a competition you should win
• Designing org structure where decision-speed is a competitive variable
• Crisis / incident response — OODA is the operational frame
• AI-native startup out-shipping a slower incumbent as model capabilities shift monthly (AI adoption, AI capex, ship-on-release-day tempo)

Not when: genuinely non-competitive setting; your slowness is high-quality orientation worth keeping; speed was recently pushed at the expense of orient quality.