The question, and the damage done in good faith
There is a management conviction that has done real damage in the past decade without anyone quite naming the mechanism. It starts from a premise that is correct: people do their best work when they genuinely own it. From that premise, an inference is drawn that is wrong: that the opposite of micromanagement is the removal of all constraints. Organizations act on this inference with the best intentions, call it autonomy, and produce a failure mode that looks - from the outside - like empowerment, and feels - from the inside - like abandonment.
The teams with the most stated autonomy are often the ones that ask the most questions, seek the most validation, and take the least initiative. This is not a talent problem. It is a design problem.
Two conditions that feel similar from the outside
Autonomy is the authority to make real decisions within a defined perimeter. It requires genuine decision-making power, and a clear boundary within which that power operates. Without the power, it is delegation without authority. Without the boundary, it is something else entirely.
Absence of framework is the state in which the perimeter is undefined - where objectives are vague, resources are ambiguous, and the rules of escalation are unspoken. Then someone makes a real decision and the invisible boundary becomes visible through contact. The cost is not the decision itself. It is what it teaches the team about what autonomy actually means in this organization.
Formless trust is not actually trust.
It is ambiguity with good intentions.
Defining the frame is an act of respect, not of control.
What genuine autonomy actually requires
A specific objective, not a general direction. "Do what you think is best" is not an empowerment. It is an abdication. Genuine autonomy requires an objective specific enough that the team can tell, at any decision point, whether they are moving toward it or away from it - without asking.
Explicit resources and constraints. The framework is not bureaucracy. It is the minimum set of explicit rules that makes real delegation possible: what budget is controlled, what headcount can be deployed, what commitments can be made, and what requires sign-off. These rules should be co-built where possible.
Clear rules of escalation. The most paralyzing ambiguity is not about what the team can decide - it is about what they must escalate. Without a clear answer, every significant decision carries the risk of having overstepped. Explicit escalation rules are the precondition for trusting without monitoring.
The co-construction principle
There is a difference between a framework that is handed down and a framework that is built together. The first is received as a constraint. The second is owned as an operating system. Teams that participated in building the framework navigate its edges with judgment rather than with rule-following, because they understand what the edges are protecting.
The leader's real job: architect of the perimeter, not guard at the gate
A guard controls movement - checks, approves, and restricts at the boundary. An architect designs a space within which movement is genuinely free. Their work is front-loaded and mostly invisible once it is done. The team that operates in a well-designed space does not feel the architecture. They feel the freedom. The architecture is what makes the freedom real.
The bottom line
Autonomy and absence of framework are not points on the same spectrum. They are different conditions that produce different behaviors and different quality of decision-making. The question is not: have we given our teams autonomy? It is: have we built the framework that makes autonomy real? Defining a perimeter is not a failure of trust. It is the thing that makes trust operational.
Chapter 6 - Performance Indicators