Several years ago, after a long stretch where one institutional crisis ran into the next, a colleague described my leadership style as organized chaos. She did not mean it unkindly. Even so, I sat with the phrase for a while before deciding what to do with it.
The first move was to take her seriously. If a colleague who knows the work says you are creating uncertainty in the people around you, the right response is not to defend the pace. It is to ask whether the pace is the problem. So I asked. I considered whether I was holding too much in motion at once, whether I was leaving the team to interpret intent in the absence of clearer direction.
What I came to, after honest reflection, was that she had described something accurately, and that the description was not actually about me.
The conditions I was leading inside were chaotic in a way that was not going to settle. Faculty governance kept its own clock. State legislative sessions did not align with budget cycles. Compliance requests, donor concerns, and student crises showed up constantly, and rarely one at a time. The question was never how to make those conditions less chaotic. The conditions were the work. What I had to ask instead was whether the unit could function inside them without depending on me to personally hold every piece together.
That is the question the Organized Chaos Framework attempts to answer.
The Organized Chaos Framework, or OCF, is a leadership model designed for environments that do not stabilize. It begins from the assumption that the surface of the work, with its competing priorities and urgent requests and partial information, will not settle down into a predictable pattern, and it asks what disciplined leadership inside that environment actually looks like.
The shortest way to state the model is this: the OCF describes disciplined leadership in an undisciplined environment. It does not try to eliminate the chaos, because the chaos is part of the work and not going anywhere. What the model produces instead is enough internal coherence that the volatility outside does not turn into paralysis inside. A unit operating well under the OCF may look noisy from outside while remaining coherent within. People understand what they are working on, why it matters, who decides what, and where to find accurate information about what is happening. That coherence is the point.
Why this matters comes into focus once you compare the OCF to the alternative most leaders default to under pressure. Most leadership writing assumes that stability is achievable if the leader is competent enough, and treats disruption as something to be managed back to calm. Under that assumption, the leader’s job becomes a kind of personal heroics. Hold everything together until the storm passes, and the team can return to predictable rhythm. The trouble is that, in genuinely complex institutions, the storm does not pass. State legislative cycles, faculty governance processes, donor relations, accreditation reviews, federal compliance requirements, and the everyday needs of students all generate pressure that the leader cannot reliably anticipate or control. A leader who keeps trying to achieve calm in those conditions tends to end up in one of two places. One is exhaustion, where the leader has absorbed disruption personally for so long that there is no further capacity to absorb anything. The other is what the OCF calls controlled chaos, in which every decision routes through the leader, the team learns to wait before acting, and the unit slows down at exactly the moment it most needs to move.
The OCF is a different bet. Rather than trying to achieve calm, the leader develops a set of practices that allow the unit to operate without it. That shift matters because it changes what the leader is for. The leader is no longer the only source of coherence in the unit. The practices provide that coherence, and the leader is then available for the work that only the leader can do.
The model identifies six elements because each of them addresses a specific way that pressure causes a unit to break down. When pressure rises, the breakdowns are predictable. People stop knowing which priorities are real. Decisions stack up at the top because nobody else is sure they have the authority to close them. Rumor fills in for missing information. Quality slips because speed has become the goal. The same problems repeat because nobody stopped to capture the lesson. Work piles up without ever closing. Each of those breakdowns has a different cause, and each is addressed by a different element of the OCF.
The elements are also not independent of one another. They pair up, and the pairing is part of what makes the model work. Purpose and Boundaries together produce direction. Coordination comes out of Decision Rights and Communication operating in tandem. Learning Loops and Productivity, paired, support adaptation. Direction, coordination, and adaptation are the three things any complex unit has to keep producing in order to function, and the six elements are how the OCF produces them. Reading the six as a list of leadership ideas misses the point. They are a system, and the relationships among them are what give the system its hold.
The six are Purpose, Boundaries, Decision Rights, Communication, Learning Loops, and Productivity. What follows is what each one means and how it functions when it is working.
Take Purpose first. The element is operational, not aspirational. Purpose is not the language a unit uses to introduce itself on a website or in a strategic plan; it is the answer the team gives, out loud, when the work is hard and the calendar is overloaded and someone asks why we are doing this and not the other thing. The function it serves is producing criteria that the team can use to make trade-off decisions, the kind that come up constantly in complex work and rarely have an obvious right answer in advance. When operational purpose is absent, the criteria default to urgency. Whatever feels most urgent gets the next hour, and the year ends with a long list of things the unit responded to and a short list of things the unit actually advanced.
Where Purpose tells a unit what it is heading toward, Boundaries name what it will not give up to get there. Most leaders can articulate what they are trying to accomplish; far fewer can articulate, before pressure arrives, what they will refuse to sacrifice in the trying. Boundaries protect a few things in particular: quality of work product when speed becomes the priority, the dignity of how staff are treated when energy runs short, and ethical lines that are easy to cross when no one is watching closely. Each of those tends to be invisible until it is violated, at which point the cost of the violation typically exceeds whatever was gained by crossing the line. Articulating Boundaries before pressure arrives is what makes them hold under pressure, because the decision has already been made rather than being made under stress.
Together, Purpose and Boundaries produce a stable sense of direction. The unit knows what it is moving toward and what it will not trade in order to get there, and that combined clarity is what keeps direction from bending with every shift in circumstance.
The next pair addresses a different problem. Decision Rights exist because most units that are stuck are not stuck because the leader is incapable; they are stuck because every decision of any consequence routes through the leader, and the leader cannot read email and think strategically and answer the phone all at the same time. As a result, decisions queue. People wait for the leader to surface long enough to respond, and work that should have closed on Tuesday afternoon stays open until Friday morning, not because anyone is incompetent but because the right to close it was never clearly assigned to anyone other than the leader. Decision Rights, when they are clear, name who decides each kind of question, who gives input, and who needs to know after the decision is made. The work of setting them up is unglamorous. It is also the difference between a unit that moves and a unit that waits.
Of the six elements, Communication is probably the most misunderstood. In the OCF, Communication does not mean more email or more meetings. It refers to a working rhythm that produces a shared picture of reality on a predictable schedule. People in a unit need to know where to find decisions that have been made, what has changed since the last update, and when the next update will arrive. With that rhythm in place, the unit’s energy goes into the work itself. Without it, the same energy goes instead into reconstructing reality from fragments, and the gaps get filled with rumor. Rumor is not a failure of character. It is what happens when communication is unreliable and people still have to operate, so they manufacture certainty in the absence of accurate information. The manufactured version is rarely flattering.
Decision Rights and Communication together produce coordination, which is to say the unit moves without colliding with itself.
The third pair is about adaptation. Learning Loops are how a unit gets smarter without relying on the leader to personally remember every lesson. A Learning Loop is a deliberate practice of looking back at a recent stretch of work and naming three things: what worked, what did not, and what the unit will do differently next time. The practice is unsentimental and short, and it is not a retrospective in the project-management sense. The function it serves is converting friction into adjustment, so that the same problems do not arrive twice in slightly different forms. Without Learning Loops, friction tends to become resentment instead of intelligence, and the unit relives its mistakes on a roughly annual cycle.
Productivity is the element most leaders assume they understand, and most leaders get it wrong. In the OCF, Productivity does not mean output volume. It means closure. Open loops, half-finished decisions, and projects whose status no one is sure about drain a unit faster than overload does. A heavy workload is sustainable when it is clear; it becomes unsustainable when ambiguity is layered on top of it. Productivity in the OCF sense means the unit finishes what it starts and announces that it has finished, so people can move on rather than continuing to track unresolved work in the background. The relief that comes from closure is what makes the next round of work sustainable.
Learning Loops and Productivity together support adaptation. The unit captures what it has learned, closes what it has started, and is therefore positioned to take on what comes next without dragging the residue of the last cycle along with it.
That is the framework: six elements, three pairs, three functions. None of the six eliminates chaos, and that is not what they are designed to do. They make chaos navigable, which is a different and more honest goal than control.
One thing worth saying explicitly is that the elements rarely fail evenly. Chaos pools where the weakest element sits. A unit with strong Purpose but unclear Decision Rights will move with conviction toward several incompatible destinations at once. Compare that with a unit whose ownership is clear but whose communication rhythm is missing: it will make good decisions in private and discover later that no one else heard them. A third pattern shows up when Learning Loops are sharp but Productivity is weak; the unit knows exactly what is wrong and still cannot close anything. The diagnostic question is not whether the framework is working overall but where chaos is pooling, and which element is missing in that spot. That question almost always has a more specific answer than the leader expects.
The phrase my colleague used was right about the description and wrong about whose problem it was. It was a description of the conditions, not of me. Once I had the right name for what I was working with, the response stopped being personal effort and became a deliberate set of practices the unit could share. The framework is what those practices add up to.
DEB