What separates organizations that truly improve from those that stay busy but stagnant is simple: some are built for action, while others are built for learning.
Most organizations prioritize speed. They decide, execute, and move on. But without structured reflection, they never really understand the consequences of their actions. Improvement becomes guesswork. It may work occasionally, but it rarely compounds. That’s why many organizations end up in cycles of firefighting, often relying on a few high performers to carry results.
Real learning, as described by John Dewey, comes from reflecting on experience. It requires observing outcomes and updating your understanding of how things actually work. In most organizations, though, action outpaces interpretation. Insights are informal, quickly forgotten, or never fully developed.
This becomes even more problematic in complex systems. As Buckminster Fuller emphasized, problems cannot be understood in isolation. Organizations often make changes that improve one area while unintentionally creating issues elsewhere because they don’t see the full system.
That’s where structured learning cycles come in. W. Edwards Deming’s PDSA cycle is not just about improvement, but about building knowledge. In practice, however, the “Study” phase is often rushed or skipped. Organizations assume that if a metric moved, their action caused it. Over time, this leads to “best practices” that are never fully understood. The result is a fragile system where knowledge lives in individuals instead of the organization. When those individuals leave, the insight leaves with them.
Stronger organizations take a different approach. They treat learning as the unit of progress. They run disciplined experiments, study results carefully, and capture what they learn so it persists over time. Frameworks like Lean Startup follow this same principle.
The result is a shift from reactive change to compounding understanding. Instead of relying on heroic effort, the system itself becomes more capable. That is the real distinction. Improvement can happen without understanding, but learning changes the system so that each step forward builds on the last.
Strong article. I would add one layer: organizational learning does not fail only because people skip reflection. It often fails because the system is not designed to protect what was learned.
Insights remain informal. Causal assumptions go untested. Knowledge stays trapped in individuals. And the next decision starts almost from zero again.
So the real challenge is not just creating learning cycles, but building a decision architecture where learning survives beyond the people, the project, and the moment.
There is an important truth in this article. Compounding understanding is the father of responding, vs reacting and being lucky. In Fighter Aviation you cannot rely on luck, but on continuous learning to be able to respond. A System that chases flawless