methodatlas
Method guideDecision Making

OODA Loop

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium
Time15-60 min je Zyklus
Participants1-8
FormatWorkshop + async
MaturityEstablished
Plan OODA Loop
01

Prerequisite

What needs to be finished first

Complete firstDecision subject

Set one time-sensitive decision with an observation window, room to act, and guardrails.

Without a clear boundary, cases and signals become mixed.
Complete firstEvidence access

Decision horizon, signal sources, assumption log, action options, effect signals, and timestamps

Missing sources are marked as open assumptions.
02

Preparation

What needs to be ready before start

Materials

Decision horizon, signal sources, assumption log, action options, effect signals, and timestamps

People / roles

Decision owner · people with situational knowledge · execution owners · scribe for signals and assumptions

Pre-read

Set one time-sensitive decision with an observation window, room to act, and guardrails.

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.

03

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?

04

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.

Reference · original teaching example

  1. 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. 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. 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. 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. 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

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

OODA Loop · John BoydObserve signals, translate through orientation into decision, act, and feed feedback back into the situation
OODA LoopThe visual shows Observe, Orient, Decide, and Act as an adaptive decision loop with feedback returning to observation.Learn, decide, and act faster in dynamic situationsDo not translate observation directly into action: orientation makes assumptions, patterns, and options explicit.capture situationmake sensechoice of actionfeedbackclose loopObservesignals, changes, feedbackOrientpatterns, assumptions, mental modelsorientation determines loop qualityDecidechoose optionActact, test, create impactEffectnew observation
Form

Versioned OODA log containing observations, orientation, decision hypothesis, action, and feedback.

Versioning / ownership

Record date, owner, evidence state, decision, and review; preserve earlier cycles.

Tool alternatives
  • 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

06

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.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Source-bound situation pictureThe situation picture says the warehouse is overloaded but contains no measurable signals.View in phase
  2. Orientation with alternativesThe first familiar explanation is treated as fact.View in phase
  3. Decision hypothesisThe decision only says optimise slots and omits effect and boundary.View in phase
  4. Executed testAdditional variables change during execution without being logged.View in phase
  5. Next OODA cycleThe action is closed as a success although a relevant signal is unchanged.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Stop Observe: Are signal, source, time, and uncertainty visible without already claiming a cause?
Stop Orient: Are context, assumptions, and at least two plausible interpretations separated?
Stop Decide: Does the decision state action, expected signal, guardrail, and review time?
Stop Act: Does execution match the decision, with deviations and timestamps recorded?
Stop Feed back: Are result, deviation, and open signals fed back into Observe?

Method after John Boyd. Curated with 1 sources.

Sources: OODA Loop

Flow, timeboxes, and pitfalls are editorially curated practice recommendations based on the listed sources.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.