← Essays Essay · Authority

Leadership Authority Structures

By Stan Tscherenkow · Published August 2025 · 11 min read

Quick Answers

What does authority actually mean in an organizational context? Authority has a precise meaning that most companies blur: it is the right to make a decision that others are obligated to act on, without requiring their personal agreement. This is different from influence, expertise, seniority, or respect. A senior engineer may be the most technically knowledgeable person in the room, but if the company has not granted them authority over architecture decisions, they have influence, not authority. Influence requires building consensus. Authority does not. Companies routinely confuse these things, promote people to senior titles, assume authority follows, and then wonder why decisions stall. The title changed. The authority structure did not.

What are the four types of leadership authority? Decision authority: the right to make a binding decision unilaterally within a defined domain. Approval authority: the right to block or approve a decision made by someone else, often confused with decision authority but it is a veto, not ownership. Recommendation authority: the right to advise on a decision without binding outcome, the default for most senior roles in companies that have not structured authority explicitly. Execution authority: the right to determine how a decision is implemented, even if someone else made the decision itself. This is often the most practically important authority for operational leaders, and the most commonly withheld by founders who have delegated the decision but not the execution.

How do authority gaps form in growing companies? In most growing companies, authority gaps are not designed. They accumulate. Three common formation patterns. Inherited ambiguity: new hires join into roles that were never defined against the existing authority structure. Job descriptions cover responsibilities, not authority. Founder retention: founders who have stopped making operational decisions day-to-day but have not formally transferred authority. Decisions get escalated out of habit. Committee erosion: companies that adopt consensus-based decision processes without realizing this transfers authority from individuals to groups. Groups move slowly and cannot be held accountable for outcomes in any meaningful sense. Authority gaps persist because naming them explicitly feels like a demotion even when it is just a clarification.

Why are authority and accountability inseparable? The most consequential mistake companies make is holding people accountable for outcomes they did not have the authority to produce. This is not a management problem, it is a logical impossibility. If a COO is accountable for operational efficiency but does not have authority over hiring decisions, they cannot be held accountable for efficiency problems caused by the wrong people in the wrong roles. If a CFO is accountable for cash position but does not have authority over the terms of customer contracts, they cannot be held accountable for the cash flow consequences. The alignment test is simple: for every metric a person is accountable for, trace back the decisions that determine that metric. If those decisions are made by someone else, the accountability is nominal. It produces blame without the possibility of genuine ownership.

Authority is not the same as seniority, title, or tenure. It is the specific right to make a binding decision in a defined domain. And its absence is the single most reliable predictor of organizational dysfunction in growing businesses.

What authority actually means

Authority in an organizational context has a precise meaning that most companies blur. It is the right to make a decision that others are obligated to act on, without requiring their personal agreement.

This is different from influence, expertise, seniority, or respect. A senior engineer may be the most technically knowledgeable person in the room, but if the company has not granted them authority over architecture decisions, they do not have authority over architecture decisions. They have influence. Which requires building consensus, which takes time and may not succeed.

The distinction matters because companies routinely confuse these things. They promote people to senior titles, assume authority follows, and then wonder why decisions stall. The title changed. The authority structure did not. The related essay on what this looks like in daily operation is the price of unclear authority.

In a $34M distribution business I worked with, the VP of Operations had been in the role for four years. The founder had never formally transferred authority over supplier contracts. It was assumed. When the VP tried to renegotiate a major contract, the supplier escalated to the founder, who reversed the decision. The VP resigned within sixty days. The authority structure had never been tested until it failed.

The four types of leadership authority

Not all authority is the same. Growing companies need to distinguish between four types and assign each explicitly.

Four types of authority

Decision authority. The right to make a binding decision unilaterally within a defined domain. The clearest form. The rarest on the ground.
Approval authority. The right to block or approve a decision made by someone else. Often confused with decision authority. But it is a veto, not ownership.
Recommendation authority. The right to advise on a decision without binding outcome. The default for most senior roles in companies that have not structured authority explicitly.
Execution authority. The right to determine how a decision is implemented, even if someone else made the decision itself. Often the most practically important authority for operational leaders, and the most commonly withheld by founders who have delegated the decision but not the execution.

You cannot hold someone accountable for an outcome they did not have the authority to produce.

How authority gaps form and how to test for them

In most growing companies, authority gaps are not designed. They accumulate. The founding structure had implicit authority because the founder made everything. As the company grew and people were added, authority was neither formally transferred nor explicitly retained. It became ambiguous.

Three formation patterns

Inherited ambiguity. New hires join into roles that were never defined against the existing authority structure. Their job description covers responsibilities. It does not cover authority. Both parties assume the other will clarify it. Neither does.
Founder retention. Founders who have stopped making operational decisions day-to-day but have not formally transferred authority. Decisions get escalated out of habit, and founders respond out of habit. The authority structure calcifies around the founder even as the org chart shows something different.
Committee erosion. Companies that adopt consensus-based decision processes without realizing this transfers authority from individuals to groups. Groups move slowly, produce compromise decisions, and cannot be held accountable for outcomes in any meaningful sense.

Authority gaps persist because they are uncomfortable to address. Naming them explicitly requires someone to say to a senior person: "You do not have authority over this." That conversation feels like a demotion even when it is just a clarification. So it is avoided. The gap remains.

An authority structure that exists only on paper is not functional. The test is behavioral. When a consequential decision is made in a domain, does the person with nominal authority make it, and does it hold?

Four diagnostic questions

When a significant decision is made in a domain, who actually makes it, and does the answer match the org chart? If not, the authority structure is nominal, not functional.
When the person nominally in charge of a domain makes a decision, how often is it reversed, modified, or re-examined by someone senior to them? Every reversal is a signal that authority has not been transferred, only delegated conditionally.
When two senior people disagree on a decision in a shared domain, what happens? If the answer is "it escalates to the founder," the authority structure has a gap. If the answer is "it stalls," the authority structure has a different problem.
Can every senior leader in your company name three decisions they made in the last ninety days without seeking approval from anyone above them? If not, they do not have decision authority. They have recommendation authority dressed in a title.

Decision latency is a proxy for authority clarity. In companies with clear authority structures, decisions move quickly because there is one person who can make them. In companies with ambiguous authority, decisions stall because everyone is waiting for someone else to commit. If your decision speed has slowed as you have scaled, this is usually the reason.

Redesign, and why authority and accountability are inseparable

Redesigning authority structures is sensitive work. Done badly, it reads as demotion, political maneuvering, or loss of trust in the people affected. Done well, it is clarifying. It removes ambiguity that has been causing friction and replaces it with explicit structure that people can operate within.

Principles that make redesigns hold

Start with domains, not people. Define the decision domains first. What categories of decision exist, and what their boundaries are. Then assign authority to roles, not to individuals. This makes the conversation structural rather than personal.
Be explicit about what is being transferred and what is being retained. If the founder is retaining approval authority over capital decisions above a threshold, say so. The retained authority is not a problem. The ambiguity about what is retained is.
Document it and test it within ninety days. Write down what was agreed. Then create a situation where the new authority structure is actually used, a real decision in the new domain. If the structure holds, it is functional. If it gets overridden, the redesign did not take.
Separate authority from compensation. Authority changes should not automatically carry compensation changes. Conflating the two makes every authority discussion also a pay discussion, which prevents clarity on either front.

The most consequential mistake companies make with authority structures is holding people accountable for outcomes they did not have the authority to produce. This is not a management problem. It is a logical impossibility. If a COO is accountable for operational efficiency but does not have authority over hiring decisions, they cannot be held accountable for efficiency problems caused by the wrong people being in the wrong roles. If a CFO is accountable for cash position but does not have authority over the terms of customer contracts, they cannot be held accountable for the cash flow consequences of those contracts.

The accountability-authority alignment test is simple: for every metric a person is accountable for, trace back the decisions that determine that metric. If those decisions are made by someone else, the accountability is nominal. It produces blame without the possibility of genuine ownership. The operational guide for founders facing this is how do you build leadership authority without losing control.

Stan Tscherenkow Private Business Advisor Two decades operating across Europe, Russia, Asia, and the United States.

About Stan →