Organizations often talk about authority as if it were a personal attribute: a founder has it, a manager has it, a team has been “given” it. But everyday coordination depends on something more concrete. Who can decide? Within what domain? What can they commit? What resources can they move? Who carries the consequence? When is the decision reviewed?
Seen this way, authority is infrastructure. It is part of the operating environment that lets people act without continuously asking for permission or reconstructing the social order around each decision.
From title to relationship
A role title can suggest authority without telling us how it actually moves. The useful unit is the relationship between a decision, the people affected by it, the resources involved, and the person or role responsible for the outcome.
Authority becomes legible when a person can tell what they may decide, what they may commit, and where their authority ends.
This also makes mismatch visible. Someone can carry high responsibility with very little authority. Someone else can hold broad informal veto power without being accountable for the result. A team can look decentralized while every consequential choice still routes upward.
Infrastructure can be redesigned
If authority is infrastructure, the response to a bottleneck is not only “trust people more.” The system itself can change: decision domains can be clarified, resource thresholds can move, review conditions can be defined, and approval loops can be removed.
The question shifts from “who is in charge?” to “what arrangement of authority lets this work move with enough clarity, accountability, and freedom?”