Stratrix

Quick reference

Key formula / structure

Observe, orient, decide, act, and round again. Check the picture before you speed up.

Memory aid

Speed only helps when your picture of events is right. Boyd's weight was on orient.

TL;DR

The OODA loop is John Boyd's four-step cycle: observe what is happening, orient (build a picture of what it means), decide, and act, then observe the results and go round again. Boyd wanted to be quicker than an adversary so as to get inside its loop and hold the initiative, but he located errors in orientation: a picture that does not match the ground. Write the team's picture down, test it against the front line, decide from it, act, and redraw it as the facts change.

What Is OODA Loop?

The OODA loop is a cycle of four steps: observe what is happening, orient (build a picture of what it means), decide what to do, and act. The results of the action are observed in turn, so the cycle repeats. John Boyd taught it in his lectures, most fully in "Discourse on Winning and Losing" in 1989. OODA stands for observe, orient, decide, act.

People have to observe. They have to orient. They have to decide. And they have to act. And if you’re getting inside that, you’re getting inside that guy’s rhythm, his tempo, his natural way of doing business. He can’t play.

— John R. Boyd, "Discourse on Winning and Losing," lecture at the USMC Command and Staff College (1989)

The popular version says the side that cycles fastest wins. Boyd did want to be quicker than an adversary, but his reason was to get inside the other side's loop: to act in ways its picture of events cannot keep up with, so that, as he put it, "he can’t play." The step he treated as decisive was orientation, the images, views and impressions a person forms from what they observe. Orientation can be false. Boyd's example was a commander whose picture was the one "you get at a rear headquarters," which did not match what was happening at the front. A team that decides quickly on that kind of picture is not ahead; it is wrong sooner. He also corrected a shorthand: reading a German general's call for a rapid, concise assessment, a quick decision and quick execution, Boyd said it named orientation, decision and execution. "He just left out the word “observation.”" The loop is not a checklist to run once in order. It is a feedback loop: the consequences of each action are observed, and the picture is redrawn.

The OODA loop

Four steps that repeat. The second one decides whether the other three help.

Observe

What is happening, including the results of your last move

→

Orient

The picture: what it means. Where errors live

→

Decide

A course of action from that picture

→

Act

Do it, then observe what it changed

↻

Origin & context

The best-documented statement of the loop is Boyd's own lecture, "Discourse on Winning and Losing," given on 25 April, 2 May and 3 May 1989 at the US Marine Corps Command and Staff College in Quantico, Virginia, and preserved in a transcript. Boyd taught it to officers as a way to think about conflict: each side observes, orients, decides and acts, and the side that gets inside the other's loop holds the initiative.

Builds on: John R. Boyd (1989), Discourse on Winning and Losing, lecture at the USMC Command and Staff College, Marine Corps University, Quantico (25 April, 2 May and 3 May 1989).
What we changed: Nothing in the loop. The page puts the weight where Boyd's own lecture does, on orientation, rather than on the popular reading of the loop as a race.

OODA Loop in action

Boyd's own example

The commander whose picture came from the rear

In his 1989 lecture, Boyd answered a comment from the class about one commander's conduct. The popular reading of the loop would look for a slow decision.

Boyd's answer pointed somewhere else. "It’s a false orientation," he said. The commander "had an orientation, but his orientation was the orientation you get at a rear headquarters, period. That’s a rear headquarters orientation. Unfortunately, it doesn’t map to what was going on up there."

The lesson is the one the slogan loses. Every step after orientation inherits its errors. A commander who decided twice as fast from the same rear-headquarters picture would only have been wrong twice as often.

Boyd used the case to locate failure in the picture, not the pace: a false orientation, however quickly acted on, does not match what is happening at the front.

Norsk Hydro

Three decisions in one meeting, and a picture redrawn for months

In March 2019, ransomware hit Norsk Hydro, the Norwegian manufacturer. At the emergency meeting, as Microsoft later told the story, "Norsk Hydro executives made three swift decisions": they would pay no ransom, they would summon Microsoft's cybersecurity team to help restore operations, and they would be open about what had happened. Executives then held daily press conferences at their Oslo headquarters.

The speed rested on a picture the company already held. At a press conference the day after the attack, finance chief Eivind Kallevik called it "quite severe" but said the company had no plans to pay, and pointed to its good backup systems as the route to recovery. The decide-and-act step was fast because the orientation was settled: the way back ran through the backups, not the attackers.

Then the loop kept turning. Hydro's estimate of the cost was redrawn as the facts came in: $41 million at first, $52 million in April, $69 million in early June. The case does not show Hydro using Boyd's loop, and its adversary was an attacker, not a rival. It shows the loop's question answered well: what do we believe is happening, and what follows from it?

In July 2019, Hydro put the total financial impact of the attack for the first half of the year at up to $75 million (NOK 650 million), up from the initial estimate of $41 million. It never paid the ransom.

Read the full story: Norsk Hydro's ransomware refusal →

Using it in the room

Use it when the situation is moving while you act on it: the first days of a crisis, a rival's surprise move, a launch in a market you do not know. Set it up in the first meeting, and redraw the picture at every meeting after.

Questions to ask

  • ?What do we believe is happening, in three sentences?
  • ?What fact would prove that picture wrong, and who would see it first?
  • ?Does our picture match what the people at the front line are seeing?
  • ?What result do we expect from this decision if our picture is right?
  • ?When did we last change our picture, and what changed it?

The 30-minute version

Five minutes: everyone reports what they have seen since the last meeting. Ten minutes: the owner reads the current picture aloud and the room tests it against those reports, then rewrites it. Ten minutes: decide the next actions and the result each should produce. Five minutes: set the time of the next redraw.

Core Components

1

Observe

Take in what is happening, including the results of your own last action and the information at the edges that nobody asked for.

Example

A plant manager reports that machines on one line have stopped responding, and a customer calls about a missed shipment.

2

Orient

Turn what you see into a picture of what it means. Boyd called this generating images, views and impressions. It is the step where errors live: a picture that does not match the ground makes every later step wrong, however fast.

Example

Is this a broken machine, a supplier problem or an attack on the network? Each picture leads to a different decision.

3

Decide

Choose a course of action from the picture you hold. A decision is only as good as the orientation it rests on.

Example

Shut the network down and run the plants by hand until the picture is clear.

4

Act

Carry out the decision, then watch what it does. The action changes the situation, which is why the loop starts again.

Example

The network goes down, and the team watches which plants can keep producing.

5

The loop itself

Boyd called it a loop because "you do it more than once" and because it is a feedback loop. The side that gets inside the other's loop, he said, holds the initiative.

Example

Each new cost estimate in a crisis is the loop going round: new facts, a redrawn picture, a new decision.

Boyd defined initiative through the loop: "I get inside my adversary’s OODA loops, I got the initiative. If he gets inside my OODA loops, he’s got the initiative."

When to Use OODA Loop

Scenario 1

A crisis in the first hours

Problem it solves: Facts arrive faster than meetings can absorb them, and the first picture of what happened is often wrong.

Real-world application

A company hit by a cyberattack names a small team to keep one running picture of what is known, and redraws it at every update.

Scenario 2

A rival's surprise move

Problem it solves: The temptation is to answer at once, on the old picture of the market.

Real-world application

A retailer's rival cuts prices in one region; before matching, the team asks what the cut tells it about the rival's costs and plans.

Scenario 3

A launch in an unfamiliar market

Problem it solves: The team's picture of customers comes from its home market and has not been tested.

Real-world application

Each week's sales data is used to rewrite the team's picture of the customer, not only to adjust the sales forecast.

Scenario 4

A negotiation that is moving fast

Problem it solves: One side keeps reacting to the other's offers without asking what the offers reveal.

Real-world application

Between rounds, the deal team writes down what it now believes the other side needs, and checks whether its next offer follows from that.

Fast on a false picture is not fast

A team that shortens its decision time without checking its orientation gets to the wrong answer sooner. Ask what the team believes is happening before you ask how quickly it can act.

How to Apply OODA Loop: Step by Step

Before you start

  • →A situation that is changing while you act on it
  • →Someone responsible for the team's running picture of what is happening
  • →A way to get fresh observations quickly, including from people at the front line
Tools:A shared page for the running picture, with timesA short, regular meeting rhythmDirect lines to people at the front line
1

Observe widely

Gather what is happening, including the results of your own last action and information from the edges that nobody asked for.

Tips

  • ✓Ask people closest to the problem, not only the people closest to you

Common mistakes

  • ✗Observing only what the current plan expects to see
2

Write the picture

State in a few sentences what the team believes is happening and why. This is the orientation, and it is the step to slow down on.

Tips

  • ✓Name the one fact that would prove the picture wrong

Common mistakes

  • ✗Leaving the picture unspoken, so each person decides from a different one
3

Test the picture against the ground

Check whether the picture matches what the people at the front are seeing. Boyd's warning was about a rear-headquarters picture that did not map to the front.

Tips

  • ✓Ask someone outside the core team to argue for a different picture

Common mistakes

  • ✗Treating the first report as the truth because it came first
4

Decide

Choose the action that follows from the picture, and say what result you expect to see if the picture is right.

Tips

  • ✓Prefer decisions you can see the effect of quickly

Common mistakes

  • ✗Deciding fast to look decisive, on a picture nobody has checked
5

Act and watch

Carry out the decision and watch what it changes. The results are the next round's observations.

Tips

  • ✓Agree in advance when the team will next redraw the picture

Common mistakes

  • ✗Moving on to the next decision without looking at what the last one did
6

Go round again

Redraw the picture with what the action revealed, and repeat. In a fast situation, the loop may turn several times a day.

Tips

  • ✓Keep each version of the picture, with its time, so the team can see how its view changed

Common mistakes

  • ✗Running the loop once, as a checklist, and calling it done

Showing the result

One slide: the team's current picture of the situation in three sentences, with the time it was written; the facts that changed it since the last version; the decisions that follow from it; and the one fact that would prove it wrong.

On the slide

  • ✓The current picture, in plain words, with a time stamp
  • ✓What changed since the last version
  • ✓The decisions it leads to, and the result each should produce

Left off

  • ✕A diagram of the four steps (the board knows the loop; it needs the picture)
  • ✕Every observation gathered (keep them in the log)
  • ✕Claims about speed that the picture does not support

Value & Outcomes

Primary benefit

It makes a team say what it believes is happening, and change that belief as the facts change, before it races to act.

Additional benefits

  • ✓Gives a crisis team a shared rhythm: observe, redraw the picture, decide, act
  • ✓Puts attention on the step where most errors start
  • ✓Turns speed into an advantage only when the picture is sound

What you'll learn

  • →What each of the four steps asks of a team
  • →Why Boyd put the weight on orientation, not raw speed
  • →How to keep a running picture that changes with the facts

Typical outcomes

A written picture of the situation, with the time it was last changedDecisions tied to the picture they rest onFewer fast moves made on a stale view

Best Practices

📋 Preparation

  • •Name who owns the team's running picture before a crisis starts
  • •Agree how front-line observations reach the people who decide
  • •Decide in advance how often the picture will be redrawn

🚀 Execution

  • •State the picture in writing before each major decision
  • •Ask what fact would prove the picture wrong
  • •Watch the results of every action and feed them back

🔄 Follow-Up

  • •Compare each version of the picture with what turned out to be true
  • •Note where the picture lagged the facts, and why
  • •Change who is consulted if the front line was heard too late

💎 Pro Tips

  • •If the picture has not changed in days while the facts have, the loop has stopped
  • •Speed is a result of a clear picture, not a substitute for one
  • •Ask what your rival's picture of you is, and what would surprise it
Write the picture down

In a fast-moving situation, keep a one-paragraph statement of what the team believes is happening, with the time it was written. When a new fact does not fit it, rewrite the paragraph before making the next decision.

Limitations & Pitfalls

⚡

It is easy to reduce to a slogan about speed, which drops the step Boyd cared most about.

Mitigation: Spend most of the time on orientation, and treat speed as a result of it

⚡

It names the steps but says little about how to build a good picture.

Mitigation: Pair it with tools that build orientation, such as scenario planning before the crisis and a pre-mortem before the commitment

⚡

It was taught for conflict between adversaries. In business, the other side is often a market or an event, not a mind to get inside.

Mitigation: Use the loop's discipline of redrawing the picture, and use the idea of getting inside a loop only where there is a real rival

⚡

Two sides cycling at the same pace can trade moves with no edge. Boyd described that as a stalemate.

Mitigation: Look for the move the other side's picture cannot explain, not only the faster version of the same move

What comes before and after

Run first

Scenario planning →

Builds pictures of possible futures before the crisis, so orientation starts from more than the first report.

The decision-making framework →

Frames who decides what, so the loop's decisions do not stall on authority.

Run next

A decision log →

Records each version of the picture and the decisions it led to, so the team can see later where its view lagged the facts.

Pre-mortem →

Once the situation steadies and a plan is drawn, test that plan's picture before committing to it.

Where this comes fromJohn R. Boyd introduced this.

Sources & further reading

More Management Frameworks

Other frameworks in the Stratrix library.

Strategy Development

Core Competency Analysis

A framework for identifying an organization's unique bundle of skills and technologies that provide access to multiple markets, contribute significantly to customer value, and are difficult for competitors to imitate.

Strategy Development

Strategy Map

A strategy map, from Robert Kaplan and David Norton (2000), draws a strategy as four layers of objectives joined by cause-and-effect arrows. The boxes are easy; the arrows are the strategy, and each one is a bet you can price and own.

Strategy Development

Real Options

Real options treats a strategy as a series of options rather than a single forecast: pay a little now for the right, but not the obligation, to invest more later, once you know more. The protection covers only the money that can still wait.

Strategy Development

Blue Ocean Strategy

Blue Ocean Strategy creates new demand instead of fighting rivals for existing demand, by eliminating, reducing, raising and creating what an industry competes on. A blue ocean is a move, not a place: it fills, and the grid must be run again.

Strategy Development

Hoshin Kanri

Hoshin Kanri, or policy deployment, carries a few breakthrough goals through every level of a company and reviews them in plan-do-check-act cycles. Its distinctive step runs upward: in catchball, each level says what a goal will take before anyone commits to it.

Strategy Development

Business Model Canvas

A visual strategic management tool that describes, designs, challenges, and pivots a business model through nine interconnected building blocks covering value creation, delivery, and capture.

Tools to try

More from Stratrix

Ask Stratrix

Three questions a month are free.

Stratrix Team

Every Casebook, three Strategy Packs a seat each year and Ask Stratrix, for teams that face these decisions all year.

$1,999 a year · $499 a seatWhat is included →

New analyses, by email

The defining moves in business, and what they teach, as they publish.

We'll email you a link to confirm. Unsubscribe anytime. Privacy policy.

See OODA Loop in the wild.

Follow OODA Loop across the companies and lenses where it actually shaped the strategy — the decision, the rationale, and how it played out.