The Permission Tax is the cost an organization pays when decisions route upward for approval instead of closing where the context already lives. It is charged in the asking, not in the answer, and nobody has to say no for the organization to pay it.
The Definition
The Permission Tax is the cumulative cost an organization pays when decisions route upward for approval instead of closing at the point where the relevant context already lives.
Three things make the term useful. It names a cost rather than a personality, which moves the conversation away from who is at fault. It locates that cost in a specific mechanism, the round trip a decision makes before it can move. And it is observable, because a leader can look at which decisions reach them and ask whether those decisions belonged somewhere else.
What the term does not cover matters as much. It says nothing about whether the leader is difficult, controlling, or unwilling to let go. Plenty of organizations pay a heavy Permission Tax under leaders who want nothing more than for people to decide without them. The tax describes a routing pattern, and routing patterns survive the intentions of everyone inside them.
Where the Pattern Comes From
Many founder-led organizations build the pattern for good reason, during a period when the founder actually was the only person with enough context to decide.
In the first years, centralized decisions are correct. One person holds the customer relationships, the economics, the technical judgment, and the history of what has already failed. Routing decisions to that person is not a bottleneck; it is the fastest available path. The organization learns this and rewards it, because the answers keep turning out to be good ones and the alternative would have been slower.
Then the condition that justified the pattern expires. The company hires people with better information than the founder has about their own domains. The context spreads out. What does not spread is the routing, because nothing in the organization ever announced that the reason for it had ended. The pattern outlives its justification, often by years, and it looks like culture rather than like the leftover of a decision nobody revisited.
How the Tax Gets Charged
A capable person facing a decision they could make asks anyway, because asking is cheap for them and deciding alone carries a personal downside they cannot size.
Follow one decision. A director knows the answer, has the data, and could close the matter in an afternoon. She also cannot say with certainty whether this particular call sits inside her authority, and the cost of guessing wrong is a difficult conversation and a small dent in how she is regarded. Sending an email costs her nothing. So she sends the email, and her choice is entirely rational at the individual level.
Repeat that across a quarter’s decisions and the organizational picture inverts. Speed goes first, since each round trip adds days to work that could have closed in hours. Initiative goes next, as people learn that proposing something reliably costs them a wait. Confidence goes last, and it goes quietly. Someone who has asked permission again and again gradually stops experiencing herself as a person who decides things.
The mechanism also compounds. Every answer a leader gives is evidence that asking was correct, which raises the probability of the next ask, which produces another answer. Nobody in the loop is doing anything unreasonable. The leader is being helpful and the director is being careful, and the organization pays for both.
The Permission Tax is charged in the asking, not in the answer. Nobody has to say no for the organization to pay it.
How the Tax Gets Charged
What the Permission Tax Is Not
Four adjacent ideas get confused with it, and each confusion sends leaders toward a fix that does not work.
| Often mistaken for | The actual difference |
|---|---|
| Micromanagement | Micromanagement is a leader intruding. The Permission Tax is people volunteering to be intruded upon, often under a leader who wishes they would stop. |
| A delegation gap | Delegation moves the task. The Permission Tax concerns decisions, and a leader can delegate flawlessly while holding every call. |
| Bureaucracy | Bureaucracy is written down and visible. The asks that make up this tax are usually required by no policy at all. |
| A talent problem | It presents as passivity, which points at the people. Replace them and the routing is still there for the next person to learn. |
Each of these points at a person or a policy. The Permission Tax points at a drawing: who is authorized to decide what, and whether anyone ever said so out loud.
What Changes When a Leader Names It
Naming the tax converts a people problem into a design problem, which is the only version of it a leader can actually solve.
The first thing that changes is where attention goes. A leader who believes the team is passive works on the team. A leader who sees a routing pattern works on the routing. That is where our Decision Rights paper starts: the escalation bottleneck is a design gap, not a character flaw, and the leader who “can’t let go” is usually looking at authority that was never actually assigned. As the paper puts it, “If they keep flowing back to you, you are still the mechanism.”
The second thing that changes is what kind of fix gets tried. We change beliefs to change behaviors. A leader who redirects every question for a month, by effort alone, will find the asking returns under pressure, because the belief that makes asking sensible is still intact: nobody has said whose call it is. Decision rights are not a chart you publish; they’re agreements you build out loud. The work is to build that agreement, with the people who live inside it, so the belief changes and the behavior follows.
The third thing is that the tax gets located. The Permission Tax lives in what we call the Business Operating System (BOS), the layer of the TRIAD Operating Architecture™ that answers who is authorized to decide what, and how authority becomes execution. It is one layer of three. If the routing persists after the authority is drawn, the cause may sit in how the team coordinates or in what the leader believes about their own role. Diagnose before you intervene.
Frequently Asked Questions
How do I know whether my organization pays a Permission Tax?
Look at where decisions land. If choices that someone closer to the work could have closed with what they already know keep arriving at your desk, the routing is the signal. The question underneath is this: when one reaches you, could you have said beforehand whose it was? Often nobody has ever said it out loud, which is a design gap rather than evidence of a weak team.
Is some Permission Tax appropriate?
Some decisions belong at the top, and an organization where nothing gets escalated has a different problem. The tax is the routing nobody chose: decisions that climb because the authority was never drawn, not because someone decided they should. Can you name which decisions are yours, and why, without reaching for the answer in the moment?
Who pays the tax, the leader or the organization?
Both, in different currencies. The organization pays in speed and in the gradual flattening of people who could be deciding. The leader pays in calendar and in the peculiar exhaustion of being needed for things that do not need them. Leaders usually feel their own version first and read it as workload rather than as a design signal.
What reduces the Permission Tax?
Redirecting questions helps only when the belief behind the asking changes. People ask because nobody has said whose call it is. Decision rights are not a chart you publish; they’re agreements you build out loud, with the people who live inside them. Until that agreement exists, a redirect is a request rather than a design.
If decisions keep flowing back to you, where was the authority never drawn?
Reach your next peak.
Related reading: the Permission Tax during a leadership transition, accountability and permission-seeking culture, and where authority lives in your company.
