OODA Loop: The Observe, Orient, Decide, Act Decision Model

By Tara Minh · Updated Oct 10, 2026

The OODA loop is a decision model created by U.S. Air Force Colonel John Boyd. It describes how people and organizations Observe what's happening, Orient themselves to it, Decide on a course of action, and Act, then repeat. The goal isn't raw speed. It's adapting to change faster and more accurately than the situation around you.

Most business articles flatten it into a four-box circle and tell you to "move quickly." That misses what Boyd actually drew. This article covers the original model, why Orient is the part that matters, what "getting inside the loop" means, and how it compares with PDCA, Cynefin, and Vroom-Yetton.

What is the OODA loop?

OODA stands for Observe, Orient, Decide, Act. Boyd developed it as a way to explain how fighter pilots, commanders, and organizations win or lose when conditions keep shifting. Its main argument is that whoever cycles through sensing, making sense, choosing, and acting more effectively than the other side gains an advantage the other side can't easily recover from.

The four steps in plain terms:

• Observe: take in information from the environment, including outside information, unfolding circumstances, and the results of your last action.
• Orient: interpret what you've observed using your experience, culture, and mental models. This is where raw data becomes meaning.
• Decide: pick a course of action. Boyd treats the decision as a hypothesis.
• Act: carry it out. Boyd treats the action as the test of that hypothesis.

The action then changes the situation, which produces new observations, and the cycle continues. In a competitive setting, your opponent is running the same cycle against you.

The loop most people draw is not the loop Boyd drew

The popular diagram is a tidy circle of four arrows. Boyd's own sketch, in his final briefing The Essence of Winning and Losing (first dated 28 June 1995, last revised January 1996), looks quite different. It shows Observe, Orient, Decide, and Act with orientation at the centre, fed by several inputs: genetic heritage, cultural traditions, previous experience, new information, and analyses and synthesis. Feedback runs back from the decision and the action into observation. And two lines labelled "implicit guidance and control" run from Orient directly into Action and back to Observation.

Those lines are the important detail. They mean experienced people often skip a deliberate Decide step. A seasoned operator sees a familiar pattern and acts, because their orientation already carries the answer. Boyd's note on the sketch says that orientation shapes observation, shapes decision, shapes action, and is in turn shaped by the feedback coming back in.

So the model isn't a linear checklist where you finish one box and move to the next. It's closer to a continuous process where all four activities overlap, and where the quality of your orientation determines everything else.

Why Orient is the centre of the model

If you remember one thing, remember this: Orient is where the loop is won or lost. The same observations produce different decisions depending on who is looking. A sales director who has lived through three price wars reads a competitor's discount differently from someone who hasn't.

Boyd's key statements in the same briefing make the dependency explicit. They argue that without prior experience, cultural background, and a repertoire of skills built through earlier encounters, we can't handle unfamiliar situations. Without analysis and synthesis across several domains, we can't build new repertoires for unfamiliar change. In his own words, the whole loop is "an ongoing many-sided implicit cross-referencing process of projection, empathy, correlation, and rejection" (that wording is Boyd's, and it's dense).

For a leader, that translates into some practical points:

• Your orientation can be wrong. Outdated mental models make you misread good data. If your market changed and your picture of it didn't, you'll decide quickly and incorrectly.
• Orientation can be built. Diverse teams, varied experience, and regular exposure to new domains widen the set of patterns you can recognize.
• Orientation can be destroyed. Boyd's wider work was about creating confusion and disorder in an opponent so they can't make sense of events. The business version is a competitor shipping, pricing, and changing direction faster than you can interpret.

What does "getting inside the opponent's loop" mean?

The phrase comes from Boyd's earlier briefing, Patterns of Conflict. There he proposes operating at a faster tempo or rhythm than an adversary, or, in his words, getting "inside" the adversary's observation-orientation-decision-action cycle. The reason he gives is that this makes you appear ambiguous and unpredictable, which generates confusion and disorder on the other side.

Notice that the mechanism isn't "do the same thing faster." It's creating a mismatch between what the other party expects and what actually happens, so that their orientation stops matching reality. In the briefing, Boyd uses historical examples, including German blitzkrieg operations, as cases where one side repeatedly operated inside the other's loop.

In business terms, getting inside a competitor's loop looks like this:

• You release a pricing change, a partnership, or a product update before they've finished interpreting your last move.
• Your customer feedback reaches your product team in days, while theirs takes a quarter.
• You make small, reversible bets, so you learn from the market while a larger rival is still waiting for a committee decision.

It's worth being honest about the limits. Boyd was writing about military conflict. Business isn't war, and treating customers or colleagues as "opponents" is a poor fit for most leadership work. The transferable idea is tempo plus orientation: learn from reality faster and more accurately than the other organizations in your space.

How the OODA loop compares with other decision frameworks

OODA doesn't replace the other models leaders use. It answers a different question. This table puts the common ones side by side.

OODA vs. PDCA

PDCA starts with a plan. You decide what you expect, run a change, check the result, and standardize or adjust. It suits situations where you can plan ahead and measure the effect, such as reducing defects on a production line.

OODA starts with observation and orientation, because in fast-changing conditions a detailed plan goes stale quickly. A common simplification says PDCA is for improving a process and OODA is for responding to a moving situation. That's a fair rule of thumb, though in practice the two can coexist: a team may run OODA to respond to market events and PDCA to improve the internal process that handles them.

OODA and Cynefin

Cynefin, introduced for managers by David Snowden and Mary Boone in A Leader's Framework for Decision Making (Harvard Business Review, November 2007), sorts situations by how much cause and effect can be known. OODA is useful mostly in the parts of that map where answers can't be looked up and you have to probe, sense, and adjust. If the problem is straightforward, a standard procedure beats looping. If it's genuinely complex, a loop of small tests fits. Cynefin helps you decide whether OODA is the right tool in the first place.

OODA and Vroom-Yetton

Vroom-Yetton is about who decides: you alone, after consulting, or as a group. OODA is about how fast and how well the organization cycles. They combine well. A leader can use Vroom-Yetton to choose the right level of participation and OODA thinking to keep the decision from outliving the situation it was meant for.

How leaders use the OODA loop: a step-by-step method

Here's a practical way to apply the model in a leadership team. It's an adaptation of the idea, not a procedure Boyd prescribed.

1. Set a shared picture of "what normal looks like." Agree on the few signals that tell you something is changing: churn, win rate, response time, competitor moves.
2. Observe from more than one place. Pull in frontline reports, customer conversations, and outside information, not just the dashboard that reached your desk.
3. Orient on purpose. In a short meeting, ask what's changed, what we assumed that may now be wrong, and which past situation this resembles. Invite someone who disagrees.
4. Decide at the lowest competent level. Give teams clear intent and boundaries so they can act without waiting for approval. This is the practical version of acting on implicit guidance.
5. Act in small, reversible steps. Treat the action as a test, in line with Boyd's own framing of action as the test of a hypothesis.
6. Close the loop fast. Review the result, update the shared picture, and go round again.
7. Audit your orientation regularly. Once a quarter, ask which beliefs about customers, competitors, or your own capabilities have gone stale.

OODA loop template

Copy this table into a doc and fill it in for any live situation. Rerun it each time something material changes.

Examples by business function

These are illustrations of how the model might work, not documented cases.

For crisis conditions, where the loop has to run in hours, see crisis leadership.

Do's and don'ts

Limits of the OODA loop

Boyd's model was built for competition between adversaries, and it carries that bias. A few cautions:

• Speed without accuracy backfires. A fast loop built on a poor orientation produces fast mistakes.
• It's not a step-by-step process. The popular four-box circle is a simplification of Boyd's diagram, so rigid "stage gates" run against his point.
• It doesn't tell you what to value. It describes how to adapt, not which goals are worth pursuing. Ethics, long-term strategy, and stakeholder trust sit outside the loop.
• It needs organizational support. Fast cycles depend on people who are trusted to act on intent, which connects to agile leadership and adaptive leadership. Building the underlying skill is covered in the decision-making competency.

Key Facts

Key Facts

• The OODA loop was developed by U.S. Air Force Colonel John Boyd. Its fullest statement is his briefing The Essence of Winning and Losing, first dated 28 June 1995 and last revised in January 1996.
• In Boyd's sketch, Orient sits at the centre. Boyd notes that orientation shapes observation, decision, and action, and is shaped in turn by feedback.
• Two "implicit guidance and control" links run from Orient straight to Action and to Observation, which lets experienced people act without a separate, deliberate decision step.
• "Getting inside" an adversary's observation-orientation-decision-action loop appears in Boyd's earlier briefing Patterns of Conflict, where he links faster, more irregular tempo to confusion and disorder in the other side.
• The Cynefin framework for managers was published by Snowden and Boone in Harvard Business Review, November 2007.

Learn more

• Cynefin framework
• Vroom-Yetton decision model
• Risk-based decision-making
• Crisis leadership