What does it mean that organizations can become self-directing?

With the right infrastructure, organizations can govern themselves without constant top-down control. Self-direction is not the absence of structure — it is the presence of a different kind of structure. Hierarchical organizations coordinate through command: a small number of people at the top decide, and a large number of people below execute. Self-directing organizations coordinate through infrastructure: shared purpose, transparent information, clear decision rights, and feedback mechanisms that enable every member to make good decisions without waiting for instructions. The shift from command to infrastructure is not a reduction in organizational intelligence — it is a multiplication of it.

Example: A digital product studio, Meridian, grew from 15 to 120 people in three years. At 15, the founder made every significant decision — project selection, staffing, technical approach, client communication. This worked because the founder could hold the entire operation in their head. At 50, it was breaking: decisions queued behind the founder, good people left because they had no autonomy, and the founder was working 80-hour weeks on decisions that any experienced team lead could have made. The founder faced a choice: add management layers (the conventional solution) or build self-directing infrastructure (the sovereignty solution). They chose infrastructure. They codified the company's purpose into a decision framework — 'Does this serve our mission of making complex technology accessible?' — that any team could apply. They made all financial data transparent so teams could evaluate the economic impact of their decisions. They established clear boundaries: teams had full autonomy within their project scope, with defined escalation criteria for decisions that affected other teams or the company's strategic direction. They created weekly cross-team syncs where teams shared what they were learning, not for approval but for coordination. Within a year, 90% of decisions that had previously required the founder were being made by teams — faster, with more context, and with better outcomes. The founder's role shifted from decision-maker to infrastructure maintainer: refining the decision frameworks, improving information transparency, and coaching teams on self-direction skills.

Try this: Map the decision flow in your organization for one week. For every decision you encounter — whether you make it, request it, or wait for it — record: (1) What was the decision? (2) Who made it? (3) Who had the information needed to make it? (4) Were the decision-maker and the information-holder the same person? If not, how much delay did the information transfer add? (5) Could this decision have been made at a lower level with the right infrastructure (information access, decision criteria, authority)? At the end of the week, calculate the percentage of decisions where the decision-maker was not the person closest to the relevant information. This percentage represents the self-direction opportunity — the decisions that could be faster and better if the right infrastructure existed.