Purpose
In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.
Decision Making Process model
OODA Loop
Connects observation, orientation, action, and feedback in a fast decision cycle.
Beobachtungen werden laufend mit Kontext und möglichem Gegenwind abgeglichen, bevor die nächste Aktion gewählt wird. Der kurze Zyklus erzeugt einen Lernrhythmus, der Anpassung in unsicheren oder wettbewerbsintensiven Lagen beschleunigt. Entscheidend ist die Geschwindigkeit des Nachjustierens.
Which action will we test from the current situation, and which feedback starts the next OODA cycle?
- Participants
- 1-8
- Time
- 30–90 minutes for the first cycle; further cycles follow the cadence of observable effects.
The steps express the method mechanics; feedback may reopen an earlier step.
Observe
Source-bound situation picture
Collect raw signals from the system, environment, and unfolding interaction with source and timestamp; separate observation from interpretation.
Orient
Orientation with alternatives
Connect signals to the goal, capacity, experience, new information, and assumptions; test at least one alternative interpretation.
Decide
Decision hypothesis
Choose one option as a testable hypothesis; record expected effect, guardrail, owner, and review time.
Act
Executed test
Execute the chosen action within scope and log deviations, side effects, and new signals.
Feed back
Next OODA cycle
Compare effect and guardrails with the hypothesis; feed surprises into the next cycle as new observations.
At review, add evidence, update assumptions, and version the next cycle.
A good fit when
In dynamischen Situationen veralten Entscheidungen schneller, als sie vorbereitet wurden. Der OODA Loop hält Wahrnehmen, Einordnen, Entscheiden und Handeln als wiederkehrenden Takt zusammen, damit Reaktion nicht in Trägheit kippt.
Ideal for
- Incident response
- Strategic uncertainty
- Fast learning loops
Not good for
- Stable routine processes
- Decisions without feedback
Outputs
Next OODA cycle
Versioned OODA log containing observations, orientation, decision hypothesis, action, and feedback.
OODA Loop · working structure
Fictional example
Fictional values demonstrate the method-specific fields.
Source-bound situation picture
Collect raw signals from the system, environment, and unfolding interaction with source and timestamp; separate observation from interpretation.
Saturday 09:00–12:00: p80 wait 18 minutes; 12 bookings from 10 to 11; inventory sync 22 minutes old.
Orientation with alternatives
Connect signals to the goal, capacity, experience, new information, and assumptions; test at least one alternative interpretation.
Interpretation A: booking cluster exceeds eight handoffs per hour. B: stale inventory extends every search.
Decision hypothesis
Choose one option as a testable hypothesis; record expected effect, guardrail, owner, and review time.
Cap at eight slots per hour for two Saturdays; expect p80 below 15 minutes; stop above 10% rejection.
Executed test
Execute the chosen action within scope and log deviations, side effects, and new signals.
Lea applies the cap on 9 and 16 Nov; Support marks rejected bookings; Warehouse measures wait.
Next OODA cycle
Compare effect and guardrails with the hypothesis; feed surprises into the next cycle as new observations.
p80 drops to 12 minutes, rejection is 7%; warehouse calls remain high. Next cycle observes sync and search time.
All values are fictional.
First step
Set one time-sensitive decision with an observation window, room to act, and guardrails.
Deep dive
How it works
Observations are continuously matched against context and possible headwinds before the next action is chosen. The short cycle creates a learning rhythm that speeds up adaptation in uncertain or highly competitive situations. What matters most is the speed of readjusting.
In detail
The OODA Loop makes decision-making visible as a repeated learning cycle. Observations are not translated directly into action but first into orientation: Which patterns, assumptions, experiences, or constraints shape the situation? That is followed by a decision, whose action creates new observations. The strength lies in the speed and quality of orientation, not only in fast execution.
Facilitation
Prepare a visible loop with current signals, assumptions, the decision, and the action. Timebox each cycle and record which observation triggered which decision. After several cycles, run a short review to check whether the orientation still fits.
The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Artifact templates
OODA Loop: WorksheetSet subject, evidence, roles, flow, and review.markdown
OODA Loop: WorksheetSet subject, evidence, roles, flow, and review.
markdownooda-loop-working-template.md
Set subject, evidence, roles, flow, and review.
OODA Loop: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Complete run Time: 30–90 minutes for the first cycle; further cycles follow the cadence of observable effects.
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Decision horizon, signal sources, assumption log, action options, effect signals, and timestamps
- Roles: Decision owner · people with situational knowledge · execution owners · scribe for signals and assumptions
- Advance information: Set one time-sensitive decision with an observation window, room to act, and guardrails.
- Overall time needed: 30–90 minutes for the first cycle; further cycles follow the cadence of observable effects.
- Setup: Divide the workspace into Observe · Orient · Decide · Act · Feed back; keep sources, assumptions, and decisions separate.
Prepare for the work steps
Observe: Source-bound situation picture
- Set one time-sensitive decision with an observation window, room to act, and guardrails.
- Decision horizon, signal sources, assumption log, action options, effect signals, and timestamps
Orient: Orientation with alternatives
- Source-bound situation picture
Decide: Decision hypothesis
- Orientation with alternatives
Act: Executed test
- Decision hypothesis
Feed back: Next OODA cycle
- Executed test
OODA Loop · working structure
Source-bound situation picture
Collect raw signals from the system, environment, and unfolding interaction with source and timestamp; separate observation from interpretation.
...
Orientation with alternatives
Connect signals to the goal, capacity, experience, new information, and assumptions; test at least one alternative interpretation.
...
Decision hypothesis
Choose one option as a testable hypothesis; record expected effect, guardrail, owner, and review time.
...
Executed test
Execute the chosen action within scope and log deviations, side effects, and new signals.
...
Next OODA cycle
Compare effect and guardrails with the hypothesis; feed surprises into the next cycle as new observations.
...
The blank worksheet contains prompts only.
Reference · original teaching example
Observe: Source-bound situation picture
Expected artifact: Source-bound situation picture
Collect raw signals from the system, environment, and unfolding interaction with source and timestamp; separate observation from interpretation.
Entry:
...
- Are signal, source, time, and uncertainty visible without already claiming a cause?
Orient: Orientation with alternatives
Expected artifact: Orientation with alternatives
Connect signals to the goal, capacity, experience, new information, and assumptions; test at least one alternative interpretation.
Entry:
...
- Are context, assumptions, and at least two plausible interpretations separated?
Decide: Decision hypothesis
Expected artifact: Decision hypothesis
Choose one option as a testable hypothesis; record expected effect, guardrail, owner, and review time.
Entry:
...
- Does the decision state action, expected signal, guardrail, and review time?
Act: Executed test
Expected artifact: Executed test
Execute the chosen action within scope and log deviations, side effects, and new signals.
Entry:
...
- Does execution match the decision, with deviations and timestamps recorded?
Feed back: Next OODA cycle
Expected artifact: Next OODA cycle
Compare effect and guardrails with the hypothesis; feed surprises into the next cycle as new observations.
Entry:
...
- Are result, deviation, and open signals fed back into Observe?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/ooda-loop/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
Decision Making
Decision Tree
Instead of OODA Loop, choose Decision Tree when a decision should be prepared and documented through branched if-then paths.
Decision Making
Cynefin Workshop
Sorts cases into the fitting domain and derives actions that match the degree of clarity or complexity.
Decision Making
Force Field Analysis
Pits driving and restraining forces against each other to deliberately derive change levers and interventions.
Decision Making
Assumption Surfacing
Clarifies options, criteria, and risks by framing the initiative or decision, collecting implicit assumptions, and planning tests or research.
Decision Making
Impact Filter
Sharpens a planned step through impact, success criteria, and risks down to the smallest sensible move.
Decision Making
Red Teaming
Examines an initiative from an opposing perspective, collects weaknesses, and derives prioritized mitigations.
Constraints and origin
MediumWorkshop + async15-60 min je Zyklus
Profile
- Method form
- Process model
- Participants
- 1-8
- Time
- 15-60 min je Zyklus
- Maturity
- Established
- Origin
- John Boyd
Next up: After-Action Review