>I also don't agree with your claim that you can't "practice" the loop on an individual level.
To further agree with what you are saying...
In many sports: people put work in to run their OODA loop faster even they don't call it that. People watch videos of their opponents to learn how to more quickly orient their opponents actions with the context of the sport.
In engineering: unittests, debuggers and IDEs are all designed to provide information that allows a faster OODA loop.
The idea of rapid iteration is based on the idea in exploratory settings with low information a faster OODA loop is often better than a smarter but slower OODA loop.
One of the best ways to slow down an opponents OODA loop in soccer is to choose inconsistent actions from play to play. As a forward receiving the ball from defense: dribble (with speed changes), pass back, pass across, etc.
It was pretty awesome hearing my son's team making this type of observation on the field as the opposition repeated the same offensive play, and adapt their response.
To further agree with what you are saying...
In many sports: people put work in to run their OODA loop faster even they don't call it that. People watch videos of their opponents to learn how to more quickly orient their opponents actions with the context of the sport.
In engineering: unittests, debuggers and IDEs are all designed to provide information that allows a faster OODA loop.
The idea of rapid iteration is based on the idea in exploratory settings with low information a faster OODA loop is often better than a smarter but slower OODA loop.