── ── Mental model

OODA Loop

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.

How it works

Step 1 — Map your loop. For each stage (Observe / Orient / Decide / Act): what happens, who does it, how long does it take? Get actual time estimates.

Step 2 — Estimate the opponent's loop. Same analysis for the competitor. The relative cycle time is the strategic variable — if you take 2 weeks and they take 4 days, you are at a 3-4x disadvantage.

Step 3 — Find the bottleneck. Observe slow = data/instrumentation problem. Orient slow = synthesis/authority/framework problem (most common). Decide slow = political/sign-off problem. Act slow = capability problem. Speeding up non-bottleneck stages does nothing.

When to use it

• competitor outmaneuvers you despite worse resources
• decisions take longer than the situation allows
• team is losing a competition they should win
• setting up crisis or incident response
• someone says 'Boyd', 'decision cycle', 'get inside their loop', or 'tempo'

Worked example

John Boyd and the F-86 vs MiG-15, Korean War 1950-1953

The OODA Loop emerged from Boyd's analysis of Korean War air combat. The empirical puzzle was specific and quantifiable.