John Boyd
The OODA loop
Fast means turning, not moving
Boyd's briefing, Patterns of Conflict
He was a fighter instructor who could win from any position in forty seconds. What 'fast' meant in the loop he built.
What actually happened?
Boyd compressed all conflict into one loop: observe, orient, decide, act. The claim isn't that each step should be quick, but that you should operate inside the opponent's loop: you finish two cycles while he finishes one, so what he observes is the world your last move made — every reaction fights a version of you that no longer exists. Facing an ambiguous, fast-changing environment, his loop slows until he collapses from the inside. In Korea the outmatched F-86 posted a lopsided kill ratio; Boyd's explanation was hydraulic controls — it switched between manoeuvres faster.
The bottleneck is almost always orient
Observe, decide and act can all be sped up with tools. The slow one is orient: fitting new information into your existing frame. The more successful the old frame, the less new information gets in — organisations do see the change, they just file it under the old map.
The data showed the new channel growing on Monday and it wasn't called a trend until the quarterly review. Those six weeks were orient, not observation.
Getting inside means producing rapid change
You don't wait to get faster; you make him slower. Keep the rhythm and direction of your moves unpredictable so his last read expires before he can act on it. He spends more time understanding you and less executing his own plan. That is how initiative changes hands.
A predictable opponent is the easiest kind: his launches and promotions are on a calendar. Come off the calendar and every response he makes is late.
Turning fast requires low internal friction
Boyd's prescription for organisations wasn't acceleration, it was less friction: shared intent, mutual trust, authority pushed down. Every approval layer is delay in the loop; every ounce of suspicion is paid for in confirmations. Trust isn't a soft metric. It is the loop speed.
Two equally able teams: one acts and reports, one asks first. The gap isn't the people, it's the delegation.
How do I use it today?
Where you are: you and your competitor are both accelerating, and you're buying tools for every step.
Ask first: which step is our loop stuck on? Usually the one where we saw it and didn't change the frame.
Where it goes wrong: turning fast into thrashing, motion with no direction; or internally, adding speed without removing friction, which just makes the mess arrive sooner.
Lines to keep
Observe, orient, decide, act.
Operate inside his loop, and give him an ambiguous, fast-changing world.
Machines don't fight and terrain doesn't fight. People do.