The IDE model once stands for Insights, Decisions, and Executions, but “execution” has increasingly proved too narrow to describe the flows that follow decisions. I am now retiring it in favor of “operation”, which captures ongoing, systemic, and scalable processes that sustain momentum and enterprise flow. This evolution expands IDE into IDO: Insights, Decisions, Operations. While older writings will retain the original term, future iterations of my research and papers will adopt this updated language.
When I first introduced the IDE model — Insights, Decisions, Executions — it served as a simple way to capture the essential sequence of work. You generate insights, make decisions, and then carry those decisions forward through execution. This framing has worked well in my research to date because it highlighted the chain of cause and effect that turns intelligence into progress.
But as my research and practice have evolved, the limits of “execution” have become clearer.
The Limits of Execution
The word execution suggests a narrow, almost mechanical act: the final step where a plan is carried out. It implies closure and a single burst of activity that follows a decision. In some contexts, this is accurate. But in the larger view of how enterprises actually function, it misses the continuity and complexity of what happens after decisions are made.
Execution marks an end point, but work rarely ends cleanly. Decisions ripple outward, creating cycles of coordination, monitoring, and adjustment.
Why “Operation” Fits Better
Over time, I have come to see that the third pillar of the IDE sequence must be broader. It must include not just one-off acts, but the sustained and systemic processes through which work unfolds. That is why I am retiring “Execution” and replacing it with Operation.
To make the distinction clear, here are the qualities that set Operation apart and make it the more fitting term:
- Operation is continuous. It captures the flows and cycles that keep work moving, not just isolated acts.
- Operation is systemic. It accounts for the interdependence of actors, tools, and processes, and how decisions ripple outward.
- Operation is scalable. It applies equally well to an individual task, a team workflow, or the functioning of an entire enterprise.
- Operation is organic. It reflects the reality of evolving systems, rather than a mechanical step at the end of a chain.
Taken together, these qualities show why Operation better captures the full range of activity that follows a decision. It is not a simple endpoint but an unfolding process that sustains momentum, integrates complexity, and keeps an enterprise in motion. Where Execution stops, Operation continues.
IDE as It Now Stands
The IDE model has always been a way to distill the essence of how progress happens. At its core, it describes the movement from recognition, to choice, to action. But as the framework has matured, the terminology must evolve to match the scope of what it represents. Moving from “Execution” to “Operation” is not cosmetic; it expands the model to capture the full system of activity that follows a decision.
The sequence is now:
- Insight — Recognition of patterns, opportunities, or problems.
- Decision — The commitments and choices that direct future action.
- Operation — The systemic unfolding of those decisions into sustained activity and enterprise flow.
This small shift in language reflects a deeper truth: organizations are not defined by isolated executions, but by their ability to operate. To evolve toward autonomy, they must be understood — and designed — in those terms.
A Natural Evolution
In some ways, this change is symbolic of the work itself. The Ragsdale Framework for Autonomous Organizations has always been about more than digitizing or automating tasks. It is about rethinking the very structures that sustain work. Just as I have evolved the Framework, the language that underpins it must evolve too.
Retiring “Execution” is not about discarding what came before, but about recognizing that our lens must expand. Operation better names the reality of how enterprises move forward and better prepares us for the horizon of autonomization. As I iterate through new editions of my existing papers, I will update the model to read IDA — Insights, Decisions, Operations. However, I will not retroactively revise older blogs or writings, which will continue to use the original terminology until they are replaced in the normal course of iteration.
…
