The briefing room at Nellis Air Force Base, 1955. A young captain named John Boyd stands in front of a chalkboard with a bet written on it: $40 says I can beat any pilot on this base in simulated air combat — starting from a position of disadvantage — within 40 seconds.
The pilots who took him up on it never collected.
Boyd would deliberately position his aircraft in the most vulnerable spot imaginable — the enemy behind him, guns leveled — and then, in less time than it takes most people to parallel park, he’d have the positions reversed. Attacker becomes target. Target becomes ghost. Forty seconds from dead to dominant. He did this over and over, to every pilot on the base, to visiting hotshots from other squadrons, to veterans who’d been flying longer than Boyd had been shaving. Nobody won. His nickname, inevitable and permanent: “Forty-Second Boyd.”
Nobody could explain it. Boyd could fly, sure — but so could everyone he beat. His aircraft wasn’t faster. His eyesight wasn’t better. He wasn’t some genetic anomaly of reaction time. And yet he won, every time, with a gap of margin that bordered on insulting. When the debriefers asked what he was doing differently, Boyd’s answer landed like a koan: “I think faster than they do.”
That wasn’t arrogance. It was a description of a specific mechanical process he’d developed, refined, and could now run at a speed that no one around him could match. He wasn’t making better decisions in those 40 seconds. He was cycling through the decision process more times than his opponent could manage. By the time the other pilot had assessed the situation and started forming a response, Boyd had already assessed it twice, responded once, and was collecting new information from the result of his first move.
He was inside his opponent’s decision cycle. And inside is the only place to be.
Boyd spent the next three decades turning that 40-second intuition into a formal theory. He analyzed every gun camera film from Korea, where F-86 Sabres were beating the technically superior MiG-15 at a 10-to-1 kill ratio. He developed the Energy-Maneuverability Theory that reshaped fighter jet design for a generation. He built a 194-slide briefing called “Patterns of Conflict” that he refined obsessively for twenty years, delivering it to anyone who’d sit still long enough. He never wrote a book. He never published a peer-reviewed paper. He simply refined a single idea with the intensity of a man who believed it was the most important idea anyone had ever had.
The idea was this: in any competitive environment — combat, business, sport, life — the person who can observe what’s happening, orient to what it means, decide on a response, and act on that decision, and then immediately do it all again, faster than the situation is evolving, wins. Not because they’re smarter. Not because they’re braver. Because they’re operating at a tempo the opponent can’t track.
He called it the OODA Loop. And it works in your life the same way it works at 40,000 feet.
What the OODA Loop Actually Is (And Why Orient Is the Only Step That Matters)
This is one of 12 Mindset Tools in the Resilient Wisdom system. Each builds on the others — and the OODA Loop is the one that gives the others velocity.
Observe. Raw data collection. What is actually happening right now? Not what you think is happening. Not what you expect. Not what you’d prefer. What do you see, hear, feel, notice? The hard part is that most people observe through a filter of expectation — they see what they’re looking for rather than what’s there. The F-86’s bubble canopy wasn’t just an engineering feature. It gave the pilot more raw data than the MiG pilot had. Better inputs, faster everything downstream.
Orient. This is where the loop is won or lost, and it’s the step almost everyone rushes past. Orientation means making sense of what you observed — running it through your experience, training, mental models, cultural background, and previous outcomes. Two people observe the same event and orient to it completely differently based on what they bring to the table. A Marine and a negotiator both walk into a tense room. The Marine orients to tactical threat indicators. The negotiator orients to power dynamics and emotional temperature. Same room. Radically different understanding. Boyd called orientation the “schwerpunkt” — the focal point — of the entire loop. Fix this step and the other three fall into line. Corrupt it with outdated mental models and no amount of speed in the other steps will save you.
Decide. Choose a course of action based on your orientation. Not the ideal course — the best available course given what you know right now. The perfectionist impulse here is lethal. A good decision now beats a perfect decision in five minutes, and that margin grows the faster the situation is moving. The decision doesn’t have to be final. It has to be actionable.
Act. Execute. And here’s the part that separates the framework from every other decision model: the moment you act, you immediately go back to Observe. Your action changed the situation. It produced a response — from the environment, from other people, from the problem itself. That response is new data. Observe it. Orient to what it means. Decide again. Act again. The loop closes, and immediately opens.
The four steps aren’t what makes the OODA Loop powerful. The cycle is what makes it powerful. Boyd’s core insight — the one that took a decade to fully articulate — is that the person who can complete the full loop more times than the opponent can complete it once controls the tempo of the entire engagement. They’re not reacting to the opponent. The opponent is always reacting to them. By the time the opponent processes Move One, you’re already executing Move Three. That’s what “inside the decision cycle” means. And tempo control is the closest thing to a cheat code that competitive reality allows.
This is your Bias for Action made systematic. It’s Extreme Ownership applied in real time. It’s Working the Problem at cycle speed rather than planning speed. The OODA Loop doesn’t replace the other tools in this system — it’s the rhythm they run inside.
Decision Velocity: The Real Metric You Should Be Tracking
Most people evaluate decisions by outcome quality. Was the decision right or wrong? Did it work? This is natural, and it’s mostly useless as a feedback mechanism, because outcome quality is downstream of a dozen factors you don’t control — timing, luck, other people’s decisions, market conditions, chance. Optimizing for it is like a surgeon evaluating their skill by whether patients survive cancer, when what they actually control is whether they performed the procedure correctly.
The metric Boyd would have you track instead is best understood as Decision Velocity — how fast you cycle through Observe-Orient-Decide-Act. Because Decision Velocity determines outcomes more than the quality of any single decision. The speed of the loop IS the advantage. A fast loop with imperfect decisions out-performs a slow loop with good ones, because the fast loop generates enough feedback cycles to self-correct, while the slow loop is still trying to get the first decision right while the situation has moved past it entirely.
Here’s how Decision Velocity shows up in your actual life, not in a cockpit:
You’re running a project and something goes sideways — a deliverable is late, a budget assumption turns out to be wrong, a key person quits. Your Decision Velocity on this problem is the time between the moment you observe the problem (something changed) and the moment you take the first corrective action. Not the full corrective plan. The first action. If that gap is four hours, you’re running a fast loop. If it’s four days while you gather more information, consult more people, and wait to be certain before acting — that’s a slow loop, and in a fast-moving situation, the four days of information gathering is worth less than four hours of active response.
The reason low Decision Velocity feels rational is that more observation genuinely does produce better orientation, up to a point. The trap is that the point arrives quickly and most people don’t recognize it. Boyd’s 40-70 rule captures this: if you have between 40% and 70% of the information you’d ideally want, you have enough to decide and act. Below 40%, wait — you need more. Above 70%, you’re paying for information you don’t need and losing tempo while you pay.
This connects to what kaizen gets at from a different angle: small, fast cycles of improvement beat large, slow cycles every time, in every domain. The OODA Loop applied to a business problem, a relationship friction, a career stall, or a health challenge is the operational form of that principle. Loop fast. Observe the result. Adjust. Loop again. Decision Velocity is the skill that makes every other improvement faster.
The research on this is striking. Gary Klein at Klein Associates spent years studying how expert decision-makers operate under time pressure — military commanders, fireground commanders, ICU nurses, chess grandmasters — and published his findings in Sources of Power: How People Make Decisions (1999). What he found contradicts the classical model of decision-making almost entirely. Experts under pressure don’t evaluate multiple options and select the best one. They pattern-recognize: they observe the situation, their orientation (built from years of experience) suggests the first workable course of action, and they run a rapid mental simulation to check whether it’ll work. If the simulation holds, they act. No comparison shopping. No optimization. First workable option, fast simulation, immediate execution. Klein called it Recognition-Primed Decision-making, and it’s OODA at full speed in the hands of someone whose Orient phase is highly trained.
The implication: the way to increase Decision Velocity isn’t to think faster. It’s to build a better Orient — a more accurate, more current, more comprehensive set of mental models — so that when you observe a situation, the right course of action is immediately apparent rather than laboriously derived. The reps you take cycling through small decisions daily train the Orient that handles large decisions under pressure. You don’t get Decision Velocity for free. You build it over thousands of small loops.
How to Build the OODA Loop as a Daily Practice
This isn’t a theory exercise. This is a reflex you train until it runs automatically under conditions that would normally shut your decision-making down entirely.
-
Separate observation from interpretation for five minutes daily. Sit somewhere — a coffee shop, a park bench, a conference room before a meeting — and spend five minutes writing down only what you observe. Not what it means. Not what you assume about the people around you. Raw data: “Woman in the corner checking her phone every twenty seconds and not looking at the man across from her.” “Meeting started seven minutes late and two of the five people opened laptops immediately.” “Temperature dropped noticeably in the last hour.” This practice trains the most common failure point in the loop: most people observe and orient simultaneously, which means their biases contaminate the data before it’s even fully collected. The separation is the skill. When you can genuinely observe without interpreting, your Orient phase works on clean inputs rather than pre-filtered ones, and your decisions become immediately more accurate.
-
Identify your three load-bearing mental models and stress-test them monthly. Your orientation runs on mental models — patterns and assumptions built from past experience. Some are accurate. Some were accurate once and have since expired. Some were never accurate and you’ve been running on them for years without noticing. Every month, identify the three biggest assumptions you’re operating under. “My industry is stable.” “My partner is satisfied.” “My health baseline is what it was at 30.” Now ask: what evidence would change this assumption, and am I actively looking for it? Boyd called the willingness to destroy an outdated mental model and build a new one “the most important cognitive skill a fighter can have.” The pilot whose orientation matches current reality beats the pilot whose orientation matches yesterday’s reality, every time, regardless of all other factors. Check your models. Break the ones that reality has already broken. Build new ones from current observation.
-
Apply the 40-70 rule to every decision under moderate stakes. If you have somewhere between 40% and 70% of the information you’d ideally want, make the decision and act. Don’t wait for 90%. Certainty is a story you tell yourself after the fact — during the decision, it doesn’t exist. The action itself is a probe; it generates feedback that no amount of prior observation could have produced. The small decisions — which project to prioritize, which conversation to have first, which problem to address this week — are where you train Decision Velocity. When a genuinely high-stakes decision arrives, the speed is already built in. You’ve been running the loop on small decisions hundreds of times. The reflex is there when you need it.
-
Observe the result of every significant action immediately. This is where most people break the loop entirely. They decide, they act, and then they move on to the next thing without running the O in the next cycle. Your action changed something. What changed? The email you sent — what was the reply, and more importantly, what did the person not say? The product you launched — what are the first-week usage patterns, not the ones you predicted, but the actual ones? The conversation you had — how did their posture shift in the last ten minutes? The loop requires that every action immediately feeds new observation. Skip this and you’ve acted once and stopped learning. The loop is closed, permanently, when you refuse to loop back through Observe after Act.
-
Debrief on loop speed, not just outcome quality. At the end of each week, review the five most significant decisions you made. Resist the reflex to evaluate whether they were right or wrong. Instead, measure the velocity: how long were you in the Observe phase before moving to Orient? Where did the loop stall? What slowed it down — information hunger, fear of commitment, waiting for consensus? Identify the bottleneck. The following week, target it. Decision Velocity compounds: a loop that took four days this month takes two days next month, and two days next quarter takes two hours. The tighter the loop, the more cycles you complete in a year, and more cycles means more feedback, more learning, more adaptation. You don’t improve by deciding better once. You improve by deciding and learning and adjusting faster than the problem can evolve.
Five practices. They look simple. Running them consistently, especially on the days when the situation is moving faster than your comfort allows, is the work. The loop isn’t trained in classrooms. It’s trained in the friction of actual decisions taken at actual speed.
Decision Velocity in Action: Desert Storm and the Company That Looped While Blockbuster Planned
General Schwarzkopf’s famous “left hook” — the flanking maneuver through the western Iraqi desert — is a textbook OODA operation. The Iraqi military had oriented their defensive posture toward a frontal assault into Kuwait. They’d fortified the expected axis of attack, dug in, pre-positioned their response. Their observation had been correct: American forces were massing. Their orientation was wrong: they expected the fight to come from the direction they were watching. By the time Iraqi commanders received reports about the flanking movement, processed the information, reoriented to the new threat axis, and issued orders to reposition — the Americans had already moved again.
The Iraqis were perpetually responding to a situation that no longer existed. They were inside the American OODA Loop, playing catch-up to a cycle they couldn’t track. The ground war lasted 100 hours. The fourth-largest army in the world, defeated not because it was outgunned (though it was), but because its Decision Velocity was measured in days while the American cycle ran in hours. Boyd, had he been alive to see it, would have said: of course. The faster loop always wins.
The civilian version of this principle, played out over a longer timeline but with equivalent decisiveness, is Netflix versus Blockbuster.
In 2007, Reed Hastings observed something: broadband penetration had crossed the threshold where streaming video was viable for mainstream consumers. He oriented to what this meant — the DVD-by-mail business printing money today was going to die, and the company that built streaming infrastructure first would own the next twenty years of entertainment. He decided to split Netflix’s focus, funding streaming development from DVD profits. He acted immediately, launching with 1,000 titles.
Then he looped. Customers loved the convenience but hated the thin library. Orient: content is the bottleneck. Decide: license aggressively. Act. Loop. Licensing from studios is expensive and gives studios too much use. Orient: original content. Decide: commission programming. Act. “House of Cards” launched in 2013. Netflix’s Decision Velocity through this period was measured in months. Blockbuster’s, by every account, was measured in years — committees, reports, strategic reviews, debates about whether streaming was a genuine threat or a consumer novelty. By the time Blockbuster completed one OODA cycle, Netflix had completed fifteen. Blockbuster filed for bankruptcy in 2010.
The companies weren’t different in intelligence or resources. Blockbuster had smart people and more capital in 2007 than Netflix. The difference was entirely in loop speed. The faster loop compounded its advantage with every cycle until the gap was unbridgeable. This is what low Decision Velocity costs, measured in the most concrete terms available: a company worth $5 billion in 2004, sold for $320 million in 2011 after bankruptcy, then shut down entirely.
The lesson isn’t “move fast and break things” so much as moving at the tempo the situation actually requires — which is almost always faster than comfort recommends — then immediately observing what broke and fixing it on the next loop. Boyd wouldn’t have called that recklessness. He’d have called it the loop, run correctly.
The Year a Fast Operator Looped Slowly and Paid For It
Take an operations lead we’ll call Devon, forty-something, running supply chain for a mid-sized manufacturer. Devon spent most of 2020 in a slow loop on a decision that should have taken a week.
The situation had changed — significantly, clearly, in ways that were plain to observe without much difficulty. The orientation was obvious to anyone who looked at it honestly. The decision, once Devon finally made it, was exactly what the data had been pointing toward for months. But Devon kept cycling back to Observe instead of moving through to Decide and Act, because the observation phase felt productive and the action phase felt final. More information seemed like due diligence. It was, in hindsight, the professional-class version of sleeping in.
The pattern that emerged afterward was that Devon’s slow loops clustered in two categories: situations where the data was clear but the action was uncomfortable, and situations where the observation phase was being used as a negotiation with reality — as if gathering enough information might somehow change what the information said. Neither was a real information deficit. Both felt exactly like one.
The tell, once Devon learned to spot it, was whether the question in play was “what do I need to know before deciding?” or “what would need to be true for the decision I already want to make to be correct?” The first question is Observation doing its job. The second is Observation cosplaying as analysis while actually serving as a delay mechanism. Once that distinction clicked, Devon adopted a rule: 24 hours maximum to observe, then Orient, Decide, Act — and use the first action as a probe to generate the information actually needed. Every slow loop eventually got resolved the same way: by acting. And every single time, the action generated more useful information in 48 hours than the preceding weeks of observation had produced.
Decision Velocity isn’t a gift some people have and others don’t. It’s a muscle. And like every muscle, it atrophies when you don’t use it and strengthens with reps. The reps are the small decisions taken at speed, daily, before anyone feels ready — because nobody ever feels ready, and waiting to feel ready is the slow loop’s favorite disguise.
The Science: What Cognitive Research Actually Says About Rapid Decision-Making
Boyd built the OODA Loop from observation and intuition, working in an era when the cognitive science to validate it didn’t yet exist. The science has since caught up, and the picture it paints is, if anything, more supportive of Boyd’s framework than he could have known.
Daniel Kahneman’s work, summarized in Thinking, Fast and Slow (2011) and drawing on decades of research with Amos Tversky, describes two systems of cognition: System 1 (fast, automatic, pattern-driven) and System 2 (slow, deliberate, analytical). The common assumption is that high-stakes decisions should run through System 2 — slow down, analyze, don’t let instinct corrupt the calculation. Boyd’s framework suggests something more detailed: the goal isn’t to use System 2 for everything, but to train System 1 (the Orient phase’s automatic pattern recognition) until it’s operating on accurate, current mental models. An expert’s fast loop isn’t System 1 running unchecked. It’s System 1 that’s been so thoroughly trained by deliberate experience that its pattern recognition is genuinely reliable — and System 2 is used selectively to stress-test the most consequential decisions, not to slow down every one.
Gary Klein’s naturalistic decision-making research, conducted across military commanders, firefighters, and ICU nurses, confirms this. In Sources of Power (1999), Klein found that experts under time pressure don’t compare multiple options. They recognize the first workable option, run a rapid mental simulation, and act if the simulation holds. The speed isn’t carelessness — it’s the product of thousands of prior OODA cycles that have trained the Orient phase to pattern-match quickly and accurately. Novices are slow because their Orient is thin. Experts are fast because their Orient is deep. Building Decision Velocity is, at bottom, building a deep Orient through high-repetition cycling.
The neuroscience of prefrontal cortex function under stress adds another layer. Research by Amy Arnsten at Yale, published in Nature Reviews Neuroscience, shows that acute, uncontrollable stress impairs prefrontal cortex function — specifically the deliberative, analytical processing that the classical decision model relies on. When you’re under genuine pressure, the careful analytical approach degrades first. What remains functional is the faster, more automatic processing of a well-trained Orient. This is why military training under stress matters: you’re not just building skills, you’re building a fast-loop Orient that functions when deliberate analysis has been taken offline by cortisol and adrenaline. The same principle applies in business, sport, and high-stakes personal decisions. Train the loop under conditions that approximate stress, and the loop will run when stress arrives uninvited.
Robin Hogarth at Pompeu Fabra University studied what he called “wicked learning environments” versus “kind learning environments” in Educating Intuition (2001). A kind learning environment gives you immediate, accurate feedback on your decisions. A wicked one gives you delayed, distorted, or absent feedback. Boyd’s insight about the loop applies directly: high Decision Velocity creates kind learning environments for yourself, because the fast action-observe cycle generates immediate feedback. Slow loops create wicked environments, because by the time you observe the result of your last decision, enough time has passed that you can no longer isolate which element of your action caused which part of the outcome. Looping fast isn’t just adaptive — it’s epistemologically superior. You learn more, faster, from tighter loops than from the same number of slow ones.
There’s also research specific to orientation quality. Philip Tetlock at the University of Pennsylvania spent two decades studying political forecasters and published the results in Superforecasting: The Art and Science of Prediction (2015, with Dan Gardner). His finding: the best forecasters — those whose Orient phase most reliably produces accurate assessments of ambiguous situations — share a consistent trait. They update their beliefs frequently and in small increments as new evidence arrives, rather than defending previous positions and updating rarely. They run a continuous OODA Loop on their own beliefs. The foxes, in Isaiah Berlin’s famous taxonomy, who know many small things, outperform the hedgehogs, who know one big thing — because the foxes are running faster loops on their mental models, discarding what stops working and building what fits.
This connects to the growth mindset research from Carol Dweck at Stanford: the defining feature of a growth mindset is the willingness to treat current performance as information rather than identity, which is another way of saying the willingness to loop — observe the gap, orient to what it means, decide on an adjustment, act on it. People with a fixed mindset are running slow loops on their self-concept, defending an orientation that experience has already contradicted. People with a growth mindset are running fast loops on the same data, updating continuously. The outcomes diverge predictably over time.
The Trap: When the Loop Breaks (And Why Analysis Paralysis Isn’t What You Think It Is)
Trap 1: The infinite Observe phase. You become a world-class information collector. You read everything, ask everyone, commission reports, pull data, request more data. Your observation is genuinely excellent. You never move to Orient. This is what analysis paralysis actually is — not a decision-making problem but a permission problem. You’re waiting for the observations to tell you what to do, which they will never do, because raw data has no inherent meaning. Meaning comes from orientation, and orientation requires you to commit to an interpretation. There’s a fix: set a hard deadline on observation. When the timer goes, you orient with what you have. The discipline of cutting off observation at a fixed point forces you into the rest of the loop, and the rest of the loop is where learning happens.
Trap 2: The corrupted Orient. You’re moving through the loop at reasonable speed, but your orientation is built on outdated mental models that no longer match reality. Your decisions produce systematically surprising results — not random surprises but a consistent pattern of “I don’t understand why this keeps happening.” That pattern is your Orient telling you it’s broken. Boyd called this the most dangerous trap: the person who is oriented to a world that no longer exists. The fix requires something cognitively expensive — deliberately entertaining the possibility that your interpretation of the situation is wrong, and actively looking for evidence that would confirm it. This is uncomfortable enough that most people avoid it, which is exactly why it’s the most common failure mode in experienced operators. The more successful you’ve been with a particular mental model, the harder it is to update it when reality changes. Beginners update easily because they have little investment in their models. Experts resist, which is how experience becomes liability.
Trap 3: The loop that never closes. You observe, orient, decide — and then loop back to observe before executing the decision. “I decided, but then I noticed something new, so I went back to check.” This feels like due diligence. It’s an avoidance behavior wearing due diligence’s clothing. The action is the thing you’re afraid of, and every loop back to Observe is a delay that you can justify to yourself and to anyone who asks. The fix is simple and uncomfortable: once you’ve decided, act before you check again. The action itself will generate better information than any additional observation of pre-action conditions could provide. You cannot think your way to certainty. Act your way to it.
Trap 4: Acting without looping back. The opposite failure. You’re decisive, you act fast, but you never complete the loop because you don’t observe the results of your actions with any rigor. You act on instinct and move to the next thing, and you’re mystified when patterns of failure repeat across different contexts because the feedback loop that would reveal the pattern is missing. This is the high-Decision-Velocity person’s version of the problem — and it’s more common in people who’ve been praised for decisiveness, because acting fast and getting praised for it trains away the observing-after-acting habit. The fix is building a deliberate debrief practice. Not a long one — fifteen minutes at the end of significant actions, running specifically the question “what did my action produce that I didn’t expect?”
The diagnostic for all four is the same: how long has it been since you completed a full loop on a significant decision? Observe-Orient-Decide-Act-Observe-the-result. If the answer is measured in weeks, find the break. Name it. Fix it this week, not after you’ve thought about it more. The Forge Protocol is useful here precisely because it creates a structured container where daily actions force daily loops, and the accumulated cycle repetition builds the OODA reflex faster than most other approaches manage.
The Contrarian Take: Why Slowing Down to Think More Clearly Is Usually Wrong
The conventional wisdom about high-stakes decisions is nearly universal: slow down. Take your time. Don’t rush. Think it through. This advice is reasonable enough in genuinely static situations — if nothing about the problem will change while you deliberate, then more deliberation produces better orientation and therefore better decisions. In static situations, the conventional wisdom is correct.
The problem is that static situations are far rarer than we treat them as being. Most important decisions exist in dynamic environments: careers, markets, relationships, health, organizations. In a dynamic environment, the cost of deliberation isn’t just the time you spent deliberating. It’s the state of the situation when you finally act, which is different from the state when you started deliberating — and the difference is paid entirely by you.
When Nokia spent two years studying the iPhone before deciding to respond, the situation changed faster than their deliberation cycle. When Blockbuster spent a year analyzing Netflix’s business model before commissioning their own streaming service, the market moved. When organizations spend months building consensus before acting on an obvious problem, the problem compounds. The deliberation wasn’t wasted — the orientation that emerged from it might even have been excellent. But the situation had moved, and excellent orientation of an outdated observation produces decisions optimized for a past that no longer exists.
The research backs the contrarian take. In a 2014 meta-analysis published in Psychological Bulletin, Ap Dijksterhuis at Radboud University reviewed studies of deliberation versus what he called “unconscious thought” in complex decisions. For decisions with many variables and uncertain tradeoffs — exactly the kind that matter most — deliberate analytical thinking often produces worse outcomes than faster, more intuition-driven decisions made by people with relevant experience. The analysis of this finding is still contested, but the practical implication aligns with Boyd: for complex, dynamic problems, a fast loop with a well-trained Orient outperforms a slow loop with exhaustive analysis. The quality of the orientation matters more than the length of the deliberation.
This isn’t an argument for recklessness. Loops that are too fast produce decisions before the Orient has enough input to function well. The 40-70 rule matters: don’t act at 20% information if 40% is achievable in a reasonable timeframe. The argument is against the reflexive assumption that more time always produces better decisions — and in favor of asking, specifically, whether the time you’re taking to deliberate is producing better orientation or simply producing the feeling of thoroughness while the situation moves.
The discipline required is counterintuitive: you have to be disciplined enough to act before you feel ready, and disciplined enough to observe the result honestly when you do. That combination — early action plus honest observation — is what builds the orient quality that eventually makes you genuinely fast. Not impulsive. Fast, with accurate calibration. That’s the goal. That’s what “Forty-Second Boyd” was actually doing in the briefing room at Nellis.
How the OODA Loop Connects to the Rest of the System
The OODA Loop isn’t just one tool in this system — it’s the cadence that gives every other tool its tempo.
Bias for Action is what closes the loop at the Act step. Without it, the loop reaches Orient and Decide and stalls — endlessly re-looping back to Observe while the action never happens. Boyd’s point about Decision Velocity is that the loop must close. Bias for Action is the psychological commitment that ensures it does. Together, they’re not just complementary — Bias for Action is the mechanism that makes the OODA Loop run at speed rather than theory.
Commanding Presence feeds the Observe step. You can’t observe what you’re not present for. If your Default Mode Network is running its usual highlight reel while you’re nominally paying attention, you’re collecting degraded data in the first step and every subsequent step compounds the error. Presence isn’t just a quality-of-life improvement — it’s a data-quality improvement for every observation you take.
Prioritize and Execute and Working the Problem operate inside the Act step. Complex problems with multiple moving parts require nested OODA Loops — a loop for each decomposed element, with the results feeding back into the orientation of the parent loop. Prioritize and Execute helps sequence which nested loop to run first. Working the Problem structures how to run each one. The OODA Loop is the rhythm; these tools are the choreography within each measure.
Deliberate Practice is the mechanism for building orient quality over time. The reason experts can run fast, accurate loops is that they’ve completed thousands of prior cycles in their domain, each one sharpening the pattern recognition that constitutes their orient. Deliberate Practice applied to your decision domain is how you build the deep orient that eventually makes fast decisions feel slow — because your pattern recognition is so well-trained that the orient happens before you’re consciously aware of it.
And Fault vs. Responsibility connects at the debrief step. After each loop, the observation of results will sometimes reveal that your action produced a problem. The question is whether you spend the next cycle in the Fault column (“I couldn’t have known; the circumstances were against me”) or the Responsibility column (“the loop produced this outcome; what does that tell me about my orient?”). Looping fast is only valuable if you’re honest about what the loops produce. The Fault-Responsibility distinction determines whether your loops compound into wisdom or just speed.
Sources & Further Reading
Common Questions About Move Fast Win About the OODA Loop
What does OODA loop stand for? Observe, Orient, Decide, Act. It’s a decision-making framework developed by Colonel John Boyd, a U.S. Air Force fighter pilot who became one of the most influential military strategists in American history. Boyd built it from his experience in Korean War aerial combat and refined it over two decades of post-military work. The framework describes how any person or organization processes information and makes decisions under uncertainty — and why cycling through the loop faster than an opponent confers a decisive advantage.
What is Decision Velocity and why does it matter more than decision quality? Decision Velocity is how fast you complete a full Observe-Orient-Decide-Act cycle. It matters more than individual decision quality because in dynamic environments, the situation changes between decisions. A fast loop with imperfect decisions outperforms a slow loop with excellent ones, because the fast loop generates enough feedback cycles to self-correct. The speed of the loop IS the advantage. Optimizing for Decision Velocity — rather than trying to make each individual decision perfect — produces better outcomes over time because it produces more learning opportunities per unit of time.
What is the most important step in the OODA loop? Orient. Not by a small margin — by a decisive one. Boyd himself spent more time analyzing the Orient phase than all the others combined. Observation is mechanical; anyone can collect data. Decide and Act are downstream of Orient — their quality is bounded by the quality of your orientation. The Orient phase is where your experience, training, mental models, and cultural context transform raw observation into meaning. Build a better Orient through deliberate experience and frequent mental model updates, and the entire loop accelerates automatically.
How do you apply the OODA loop in daily life? Start with the five practices in the Method section above. The core habit is: when anything changes in your environment, work, or relationships, immediately ask — what exactly did I observe? What does it mean given what I know? What’s the best available action with current information? Then act and immediately note what the action produced. Daily practice on small decisions builds the reflex that activates on large ones. The loop is trained through repetition, not understanding.
How is the OODA loop different from standard decision-making models? Most decision-making models treat a decision as an event: you gather information, evaluate options, select the best one. The OODA Loop treats it as a cycle: you act, observe the result, reorient, decide again. The standard model is designed for static situations with defined options. The OODA Loop is designed for dynamic situations where the options and the situation itself change as a result of your decisions. In real-world conditions of uncertainty and change — which is most situations that matter — the loop model produces systematically better outcomes because it’s built for how reality actually behaves.
Why did the F-86 beat the technically superior MiG-15? Two reasons, both traced directly to Boyd’s analysis. First, the F-86’s bubble canopy gave pilots near-360-degree visibility — a better Observe capability. Second, the F-86’s fully hydraulic flight controls allowed the pilot to transition between maneuvers faster than the MiG’s heavy manual controls permitted. Not fly faster — transition faster. This meant the F-86 pilot could cycle from one maneuver to another, completing one OODA loop and beginning the next, before the MiG pilot had finished processing the first move. The result was a 10-to-1 kill ratio in favor of a technically inferior aircraft. The machine’s specs mattered far less than the tempo of the human running it.
Can the OODA loop be used in team environments? Yes, and Boyd applied it explicitly at the organizational level in his “Patterns of Conflict” briefings. For teams, the loop’s speed is limited by its slowest phase — most commonly the Orient step, where shared mental models must be built and maintained across multiple people. Teams with high psychological safety (members can share observations without filtering for political safety) and high orientation alignment (shared understanding of what observations mean) run faster loops than teams where either is absent. The fastest teams have built shared Orient through accumulated experience and explicit after-action reviews, which is why high-performing military units, surgical teams, and trading desks all rely heavily on structured debriefs — they’re rebuilding and updating shared orientation after every loop.
What’s the relationship between the OODA loop and the 66-day habit formation research? Phillippa Lally’s research at UCL found that new automatic behaviors require roughly 66 days of repetition to become reflexive. The OODA Loop is most valuable when it runs automatically — when you observe a change and the subsequent Orient-Decide-Act sequence unfolds without deliberate effort. Building that automaticity requires running the loop consciously and repeatedly on small decisions for long enough that the sequence becomes a reflex. Sixty-six days of daily loop practice on low-stakes decisions is enough to make the pattern available under pressure. The reps on small loops build the reflex that runs on large ones.