Apr. 30, 2026 · 6 min read
OODA Loop
Colonel John Boyd developed the OODA Loop (Observe, Orient, Decide, Act) while studying aerial combat in the 1950s and 1960s. Boyd observed that pilots who could cycle through observation, orientation, decision, and action faster than their opponents consistently won engagements, regardless of aircraft superiority (Boyd, 1976).
Same story in business and technology. Loop faster than your competition and compound your advantage.
The Four Phases Explained
The OODA Loop consists of four interconnected phases forming a continuous cycle (Boyd, 1987). Observe gathers data from system telemetry, customer feedback, and market research. Orient synthesizes this data through organizational culture and domain expertise, transforming information into clear insight. Decide selects a course of action, balancing analysis with acceptable risk. Act executes decisions and feeds results back into observation.
These phases form a continuous loop, not a sequential checklist (Boyd, 1987). While you act on one decision, you simultaneously observe its effects, orient to new information, and prepare subsequent decisions.
Why Speed Matters
Boyd’s central insight was that faster OODA cycles create disorientation in opponents (Boyd, 1976). When you complete your loop faster than competitors, you act on current information while they respond to outdated conditions. Each iteration compounds this advantage.
The Lean Startup demonstrates that companies with faster build-measure-learn cycles consistently outperform slower competitors (Ries, 2011). Google’s DORA research confirms that elite performers deploy code 973x more frequently than low performers, with direct business impact (Forsgren et al., 2018).
Organizations that iterate weekly learn 52 times per year. Those that iterate quarterly learn four times. Over multiple years, this difference becomes insurmountable (Ries, 2011).
Impediments to Fast Loops
Observation bottlenecks emerge from poor instrumentation and siloed data. When teams lack visibility into production behavior, orientation suffers (Forsgren et al., 2018).
Orientation failures come from cognitive biases and outdated mental models. Companies orient based on past success rather than current reality, creating blind spots (Argyris, 1977). Team Topologies demonstrates that cognitive load and communication structures impact how organizations orient to technical challenges (Skelton & Pais, 2019).
Decision paralysis shows up in committee-driven processes and excessive risk aversion. Decision velocity correlates strongly with competitive advantage (Forsgren et al., 2018).
Action delays result from deployment friction and technical debt. The DevOps Handbook shows how reducing batch sizes and automating pipelines directly impacts throughput (Kim et al., 2016).
Each impediment multiplies cycle time. An organization that observes infrequently, orients poorly, decides cautiously, and acts slowly operates at a fraction of its potential velocity.
Practical Applications for Tech Leadership
Incident response maps directly to OODA. Effective incident management observes anomalies quickly, orients to root causes through runbooks, decides on remediation, and acts through automated procedures. Agentic AI is beginning to compress the observe-orient phases from minutes to seconds, keeping humans in the decision and action loop. Mean time to recovery depends more on loop speed than preventing all failures (Beyer et al., 2016).
Product development accelerates through continuous deployment. Feature flags enable observation, A/B testing provides orientation, and rapid deployment enables quick action. Organizations practicing continuous delivery deploy 46x more frequently with 440x faster lead times (Forsgren et al., 2018).
Strategic planning benefits from continuous adjustment rather than annual cycles (Ries, 2011). Observe market dynamics continuously, orient strategy quarterly, decide on tactical adjustments monthly, and act on opportunities as they emerge.
Common Mistakes
Neglecting the Orientation phase. Observation and Action are the visible parts of the loop. Orientation is where the loop is won or lost. Boyd spent more time on Orientation than the other three phases combined (Boyd, 1987). It filters incoming data through experience, mental models, and cultural assumptions. Teams that rush from Observe to Decide skip the phase that determines whether their speed is applied to the right problem.
Confusing OODA with a REPL. Engineers sometimes treat the Read-Eval-Print Loop as a metaphor for fast iteration. The loop resembles OODA but lacks Orientation. Each cycle reacts without building a mental model. Geoffrey Huntley calls the agentic AI version the Ralph Wiggum Loop. It describes an agent that iterates on its own outputs until it stumbles onto a correct result, with no orientation between cycles (Huntley, 2025).
Sustaining high-velocity indefinitely. Constant high-velocity mode exhausts teams, decreasing productivity and degrading decision quality (Forsgren et al., 2018). Not all competitive advantages derive from speed. Some require patient investment in research that cannot be rushed. Decisions that demand methodical, effortful reasoning cannot be compressed without degrading their quality (Kahneman, 2011).
Put It Into Practice
The goal is not maximum speed but optimal tempo. Fast enough to stay ahead, disciplined enough to sustain it.
Audit your organization’s loop. Where do observations get delayed? What distorts orientation? What causes decision paralysis? What impedes action? Each impediment is an opportunity. Eliminate them, one cycle at a time.
References
Argyris, C. (1977). Double loop learning in organizations. Harvard Business Review, 55(5), 115-125. https://hbr.org/1977/09/double-loop-learning-in-organizations
Beyer, B., Jones, C., Petoff, J., & Murphy, N. R. (2016). Site Reliability Engineering: How Google Runs Production Systems. O’Reilly Media. https://sre.google/sre-book/table-of-contents/
Boyd, J. R. (1976). Destruction and Creation. U.S. Army Command and General Staff College. https://www.coljohnboyd.com/static/documents/1976-09-03__Boyd_John_R__Destruction_and_Creation.pdf
Boyd, J. R. (1987). Organic Design for Command and Control. Unpublished briefing. https://www.coljohnboyd.com/static/documents/1987-05__Boyd_John_R__Organic_Design_for_Command_and_Control__PPT-PDF.pdf
Forsgren, N., Humble, J., & Kim, G. (2018). Accelerate: The Science of Lean Software and DevOps. IT Revolution Press. https://itrevolution.com/product/accelerate/
Huntley, Geoffrey (2025). “Ralph Wiggum as a ‘software engineer’.” ghuntley.com. https://ghuntley.com/ralph/
Kahneman, D. (2011). Thinking, Fast and Slow. New York: Farrar, Straus and Giroux. https://us.macmillan.com/books/9780374533557/thinkingfastandslow/
Kim, G., Humble, J., Debois, P., & Willis, J. (2016). The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations. IT Revolution Press. https://itrevolution.com/product/the-devops-handbook/
Ries, E. (2011). The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses. Crown Business. https://theleanstartup.com/book
Skelton, M., & Pais, M. (2019). Team Topologies: Organizing Business and Technology Teams for Fast Flow. IT Revolution Press. https://itrevolution.com/product/team-topologies/
Thumbnail: Canadair Sabre Mk. 1 cockpit at the Alberta Aviation Museum. Photo by CambridgeBayWeather (CC BY-SA 3.0). Wikimedia Commons
Outtakes
The kill ratio. Boyd’s original insight came from a puzzle. U.S. pilots in F-86 Sabres were shooting down MiGs 10:1 despite the MiG-15 being the superior aircraft (on paper). His explanation wasn’t pilot skill. The F-86’s bubble canopy gave better situational awareness. Its hydraulic controls gave faster stick response. Pilots who could see more and react faster completed their loops first.
Napoleon’s corps system. A century and a half before Boyd, Napoleon restructured the French army into semi-autonomous corps that could act independently without waiting for central command. Each corps completed its own loop without needing permission.
The Fighter Mafia. Boyd pushed for a lightweight, maneuverable fighter using his Energy-Maneuverability theory. The Air Force establishment wanted the opposite, the F-15, a large, twin-engine fighter with advanced radar and a growing price tag. Boyd launched a parallel competition. The winning design, the YF-16, became the F-16. By the time it entered service, the Air Force had added radar, avionics, and weight until it had drifted back toward the aircraft Boyd fought against.
Changelog
2026-05-16 Added Outtakes section. Removed Senior IC section.
2026-05-04 Consolidated “When Speed Becomes a Liability” into Common Mistakes.
2026-05-02 Updated Boyd reference links to direct PDFs via the Colonel John Boyd Digital Archive.