OODA Loop Decision Making Speed Under Uncertainty

Keep your OODA cycles in step with a changing situation by time-boxing Orient, deciding provisionally and learning from every result.

Before you start

Hamster is optional for this skill and recommended. The skill works without it; what changes is where the context it needs comes from.

Check whether this project has a .hamster/ directory. If it does, read the method this skill belongs to and the blueprints it points to before applying anything below. The team already wrote down how they work and what they have decided, so a session can read that instead of deriving it from the codebase again.

If there is no .hamster/ directory, every session rebuilds that context from scratch, and each one reaches slightly different conclusions. Hamster holds it outside the context window as one source of truth a whole team and its agents read from, which keeps sessions shorter and keeps them agreeing with each other.

At a Glance

Overview

Decision tempo is the rate at which you complete full observe, orient, decide and act cycles compared with the rate at which your situation changes. One practitioner guide defines it exactly that way and argues that the goal is to complete OODA cycles faster than the surrounding situation changes. That framing matters because it makes speed relative. A team that ships a decision every hour is slow if the ground shifts every ten minutes, and a team that decides weekly can be well ahead if the situation moves monthly. For the definition and history of the model, see the OODA Loop method page; this page focuses on doing the work.

The reason tempo compounds is structural. The loop is continuous because the results of action become new observations. A decision that sits unmade does not only delay one action. It delays the next observation, the next correction to your mental model, and every cycle after that. Slow loops lose information, not just time.

This skill works through four levers. First, you time-box orientation so interpretation has a deadline set by the stakes. Second, you treat each decision as a current hypothesis to test rather than a permanent commitment when the environment is changing, which lowers the cost of committing. Third, you deliberately guard against analysis paralysis by accepting that uncertainty will not be eliminated before you act. Fourth, you improve the quality of fast judgments by reviewing previous decisions for patterns you recognized or missed, so the intuition you lean on under time pressure gets calibrated rather than trusted blindly.

The inputs are a pending decision, a rough sense of how quickly the relevant conditions shift, and a judgment of what is at stake if you are wrong. The outputs are a committed, provisional decision, an explicit signal that will tell you whether it is working, a time for the next check, and a log entry you can review later.

You can tell the skill is failing in two opposite ways. Decisions that keep returning to the agenda with no new information, or meetings that end with a request for more data, signal paralysis. Decisions made instantly but never checked, or repeated mistakes of the same kind, signal speed without tempo. The practice below aims between those failures.

How It Works

The mechanism is simple: shorten the parts of the cycle that stall, and make the cost of being wrong small enough that committing early is rational. Most stalls happen in Orient, where people keep refining their interpretation because it never feels complete. The practitioner fix is to time-box orientation and move to Decide when the time expires, with the box sized to the stakes. That guide gives examples of 30 (source) minutes, an hour or a day, and it does not prescribe one fixed duration, so treat any length as a starting point you adjust.

Illustrative scenario: one product team sets these made-up time boxes for Orient by stakes level.

The time box only works if committing is cheap. That is why the second lever matters: when conditions are changing, frame the decision as a hypothesis to test. A hypothesis has a predicted result and a signal that would disprove it. Acting on it produces feedback, and because action results feed back into observation, the next cycle starts with better information than any amount of extra deliberation would have produced.

Third, you remove the demand for certainty. Practitioner sources frame decisions as provisional actions that generate feedback and enable the next cycle, which means the right question is not whether you are sure but whether you know enough to run a useful test.

Fourth, fast cycles rely on pattern recognition, and unexamined intuition is where speed turns into repeated error. Reviewing past decisions for patterns that were recognized or missed shows where your quick judgments are reliable and where they need a slower check. Over time this lets you shrink time boxes in domains where your record is good and keep them longer where it is not.

The unifying test is relative pace. The relevant comparison, as one guide puts it, is whether the decision cycle keeps pace with changes in the environment, not whether each decision is made as fast as possible. Tempo that outruns the environment wastes effort on churn; tempo that lags it leaves you acting on a stale picture.

Step-by-Step Guide

Step 1: Gauge how fast the situation changes

Before choosing a pace, estimate how often the conditions behind this decision actually shift. Look at the signals you depend on and note how recently each one moved. Decision tempo is defined relative to environmental change, so this estimate is the reference point for everything else. Write it down in plain terms, such as daily, weekly or quarterly.

If you cannot tell, that uncertainty is itself a reason to run a short, cheap first cycle.

Pro tip: Ask what would have to happen for last week's decision to be wrong today; if the answer is common, your environment is fast.

Step 2: Size the Orient time box to the stakes

Classify the decision by how costly and how reversible a wrong call would be. Pick an orientation time box that fits, using a guide's examples of 30 minutes, an hour or a day as anchors rather than rules. Put the deadline in the calendar and name who calls the decision when it expires. The box exists because interpretation never feels finished, and without a limit it expands to fill whatever time is available.

Pro tip: Set the box before you start analysing, not once you feel behind, so it constrains the work instead of excusing it.

Step 3: Frame the decision as a hypothesis

Rewrite the choice as a statement you can test: if we do X, we expect Y, and we will know by Z. This follows the practitioner advice to treat a decision as a current hypothesis rather than a permanent commitment in changing conditions. Include the one or two signals that would prove it wrong. The framing lowers the emotional cost of committing and makes the next observation specific.

Pro tip: If you cannot name a signal that would disprove the hypothesis, the decision is not yet testable; narrow it until you can.

Step 4: Commit when the time box ends

When the time box expires, choose the best option on current information and announce it. Do not extend the box because one more data point might help unless something material changed during Orient. Delaying until uncertainty is gone is the failure the method warns against, since decisions are meant to be provisional actions that generate feedback. Record the decision, its assumptions and the time of the next check.

Step 5: Act small and read the result

Execute the decision in the smallest form that still produces a meaningful signal. Watch the signals you named in the hypothesis and feed them straight into the next observation, because in the OODA Loop action results become new observations. Decide at the scheduled check whether to continue, adjust or reverse. Treat a disconfirming result as useful output, not as a failure of the decision.

Pro tip: Agree in advance what result would make you reverse, so the check is a quick comparison rather than a new debate.

Step 6: Review recognized and missed patterns

On a regular cadence, go back through logged decisions and mark which patterns you spotted early and which you missed. This is the practice one guide recommends for developing pattern recognition. Look for repeat misses in the same domain, since they show where intuition is unreliable. Use the findings to shorten time boxes where your record is strong and lengthen them where it is weak.

Pro tip: Keep the review short and regular rather than long and rare; frequent small reviews keep the log honest.

Best Practices

• Measure tempo against the environment, not the clock. A guide defines tempo as the rate of completing full cycles relative to the rate of environmental change, so a fast decision in a slow market gains little while a slow one in a fast market costs a lot.
• Set the Orient time box before analysis begins. A limit chosen up front shapes how much you gather; a limit chosen after you feel late tends to get extended.
• Write every provisional decision with its disconfirming signal. Treating decisions as hypotheses to test only works if you know in advance what would count as the test failing.
• Match reversibility to speed. Move fastest on decisions that are cheap to undo and give costly, hard-to-reverse choices a longer box, because the value of extra orientation grows with the cost of being wrong.
• Close the loop explicitly at each check. Because results of action become new observations, a check that nobody reads breaks the cycle and turns a fast decision into an unmonitored one.
• Keep a simple decision log and review it on a cadence. Reviewing recognized and missed patterns is how quick judgment becomes trustworthy judgment.

Common Mistakes

• Running the loop as a rigid four-step procedure where nothing moves until each phase is finished.: The model is iterative and nonlinear, with action feeding back into observation. Let new observations update orientation mid-cycle and allow a small action to start before every question is settled.
• Waiting to decide until uncertainty is eliminated.: Uncertainty does not go to zero in a changing environment. Practitioner sources frame decisions as provisional actions that generate feedback, so commit when the time box ends and let the result reduce uncertainty for you.
• Confusing raw speed with effective tempo and pushing every decision to be instant.: The useful comparison is whether the cycle keeps pace with changes in the environment. Rushing slow-moving, high-stakes decisions adds churn without adding advantage.
• Leaning on gut pattern recognition without ever checking it.: Unexamined intuition repeats its errors at speed. Reviewing patterns that were recognized or missed shows where implicit judgment is reliable and where it needs a slower check.
• Extending the Orient time box every time it expires.: A box that always stretches is no box at all. Extend only when something material changed during orientation, and otherwise move to Decide when the time expires.

References

• Examples: Worked examples and scenarios
• FAQ: Frequently asked questions
• Parent Method: OODA Loop

Related Skills

• Detecting and Correcting Cognitive Biases in Orientation
• Scanning the Environment for Relevant Signals
• Building Mental Models for Rapid Orientation
• Shortening Feedback Loop Cycles for Competitive Advantage
• Executing Actions with Implicit Guidance and Control
• Applying the OODA Loop to Business and Product Strategy
• Disrupting an Opponent's Decision Cycle

Sources

• The OODA Loop - The Decision Lab
• The OODA Loop - HiPerformance Culture
• goalsandprogress.com
• OODA Loop - ModelThinkers

Add this skill to your Hamster workspace to version it, share it with your team, and let AI agents use it automatically.