Set one time-sensitive decision with an observation window, room to act, and guardrails.
OODA Loop
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
Prerequisite
What needs to be finished first
Decision horizon, signal sources, assumption log, action options, effect signals, and timestamps
Preparation
What needs to be ready before start
Decision horizon, signal sources, assumption log, action options, effect signals, and timestamps
Decision owner · people with situational knowledge · execution owners · scribe for signals and assumptions
Set one time-sensitive decision with an observation window, room to act, and guardrails.
30–90 minutes for the first cycle; further cycles follow the cadence of observable effects.
Divide the workspace into Observe · Orient · Decide · Act · Feed back; keep sources, assumptions, and decisions separate.
Core question
The one question this method answers
Which action will we test from the current situation, and which feedback starts the next OODA cycle?
Flow
Phases with goal, actions, output and pitfall
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.
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.
- 1
Observe
Source-bound situation picture

Goal
Source-bound situation picture: Collect raw signals from the system, environment, and unfolding interaction with source and timestamp; separate observation from interpretation.
Inputs for this step
- 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
Actions
- Collect raw signals from the system, environment, and unfolding interaction with source and timestamp; separate observation from interpretation.
Output
Source-bound situation picture
Collect raw signals from the system, environment, and unfolding interaction with source and timestamp; separate observation from interpretation.
Quality check
Are signal, source, time, and uncertainty visible without already claiming a cause?
Pitfall
The situation picture says the warehouse is overloaded but contains no measurable signals. Split claims into observed values, source, timestamp, and open uncertainty.
Timing: 10–20 minutes
- 2
Orient
Orientation with alternatives

Goal
Orientation with alternatives: Connect signals to the goal, capacity, experience, new information, and assumptions; test at least one alternative interpretation.
Inputs for this step
- Source-bound situation picture
Actions
- Connect signals to the goal, capacity, experience, new information, and assumptions; test at least one alternative interpretation.
Output
Orientation with alternatives
Connect signals to the goal, capacity, experience, new information, and assumptions; test at least one alternative interpretation.
Quality check
Are context, assumptions, and at least two plausible interpretations separated?
Pitfall
The first familiar explanation is treated as fact. Expose formative experience and assumptions, then formulate a competing interpretation.
Timing: 15–25 minutes
- 3
Decide
Decision hypothesis

Goal
Decision hypothesis: Choose one option as a testable hypothesis; record expected effect, guardrail, owner, and review time.
Inputs for this step
- Orientation with alternatives
Actions
- Choose one option as a testable hypothesis; record expected effect, guardrail, owner, and review time.
Output
Decision hypothesis
Choose one option as a testable hypothesis; record expected effect, guardrail, owner, and review time.
Quality check
Does the decision state action, expected signal, guardrail, and review time?
Pitfall
The decision only says optimise slots and omits effect and boundary. Add one concrete change, measure, stop rule, owner, and date.
Timing: 10–15 minutes
- 4
Act
Executed test

Goal
Executed test: Execute the chosen action within scope and log deviations, side effects, and new signals.
Inputs for this step
- Decision hypothesis
Actions
- Execute the chosen action within scope and log deviations, side effects, and new signals.
Output
Executed test
Execute the chosen action within scope and log deviations, side effects, and new signals.
Quality check
Does execution match the decision, with deviations and timestamps recorded?
Pitfall
Additional variables change during execution without being logged. Preserve the original decision and stop or explicitly record extra changes and their effect.
Timing: One or two operating cycles
- 5
Feed back
Next OODA cycle

Goal
Next OODA cycle: Compare effect and guardrails with the hypothesis; feed surprises into the next cycle as new observations.
Inputs for this step
- Executed test
Actions
- Compare effect and guardrails with the hypothesis; feed surprises into the next cycle as new observations.
Output
Next OODA cycle
Compare effect and guardrails with the hypothesis; feed surprises into the next cycle as new observations.
Quality check
Are result, deviation, and open signals fed back into Observe?
Pitfall
The action is closed as a success although a relevant signal is unchanged. Check all signals and phrase the main residual uncertainty as the next observation.
Timing: 15–20 minutes
Artifact
What comes out at the end
Sketch: what the artifact looks like
Versioned OODA log containing observations, orientation, decision hypothesis, action, and feedback.
Record date, owner, evidence state, decision, and review; preserve earlier cycles.
- Signal and event log
- Assumption and option map
- Decision log with effect signals
ooda-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
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
ooda-loop-beispiel.md
Concrete filled scenario, fictional example
Fictional teaching example: OODA Loop · working structure
Source-bound situation picture
Saturday 09:00–12:00: p80 wait 18 minutes; 12 bookings from 10 to 11; inventory sync 22 minutes old.
Orientation with alternatives
Interpretation A: booking cluster exceeds eight handoffs per hour. B: stale inventory extends every search.
Decision hypothesis
Cap at eight slots per hour for two Saturdays; expect p80 below 15 minutes; stop above 10% rejection.
Executed test
Lea applies the cap on 9 and 16 Nov; Support marks rejected bookings; Warehouse measures wait.
Next OODA cycle
p80 drops to 12 minutes, rejection is 7%; warehouse calls remain high. Next cycle observes sync and search time.
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- Source-bound situation pictureThe situation picture says the warehouse is overloaded but contains no measurable signals.View in phase
- Orientation with alternativesThe first familiar explanation is treated as fact.View in phase
- Decision hypothesisThe decision only says optimise slots and omits effect and boundary.View in phase
- Executed testAdditional variables change during execution without being logged.View in phase
- Next OODA cycleThe action is closed as a success although a relevant signal is unchanged.View in phase
Source-bound situation picture
The situation picture says the warehouse is overloaded but contains no measurable signals.
Split claims into observed values, source, timestamp, and open uncertainty.
Orientation with alternatives
The first familiar explanation is treated as fact.
Expose formative experience and assumptions, then formulate a competing interpretation.
Decision hypothesis
The decision only says optimise slots and omits effect and boundary.
Add one concrete change, measure, stop rule, owner, and date.
Executed test
Additional variables change during execution without being logged.
Preserve the original decision and stop or explicitly record extra changes and their effect.
Next OODA cycle
The action is closed as a success although a relevant signal is unchanged.
Check all signals and phrase the main residual uncertainty as the next observation.
Stop criteria
When to pause, resolve prerequisites, or choose another approach
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

