Are There Opportunities to Use OODA Loops in Your Software Project?

The world is full of good ideas misapplied, so I want to be careful when discussing OODA loops. The OODA loop was created as an idea in the study of war. War is endemic to the way humans are (at least, so far), but it is always, in part or in whole, a tragedy. And characterizing software engineering, business operations or entrepreneurship as a conflict in that vein can create an overly aggressive view of the world. But, I belive, this concept can be adapted to a more civilian setting. The key difference is that, in war, the main conflict is with some adversary, and it is brutal. But in a software project, the conflict is mostly with ourselves and our environment. And if it feels brutal, that’s certainly a red flag! Observe, Orient, Decide, and Act OODA stands for Observe, Orient, Decide, and Act. It’s a model of how individuals and organizations take in the world (Observe), form an understanding of it (Orient), pick a strategy to pursue (Decide), and affect their environment (Act). ... Read full article.