How to Clarify Decision Rights So Everything Stops Coming Back to the Founder
If every significant decision in your business routes through you, the business hasn’t been structured — it has been personalised around you. That is not a delegation problem. It is an architecture problem. Here is how to fix it.
At a glance
- Decision rights are the formal assignment of authority to make specific decisions at specific levels — without them, everything defaults upward
- Task delegation without decision authority doesn’t decentralise anything — the founder retains all the judgment calls within the work
- Three dimensions of decision authority: financial thresholds, risk categories, and strategic scope
- The escalation rule: define precisely when and why something should come to the founder — and hold the team to it both ways
- Clear decision rights are one of the three structural foundations a fractional COO installs
Why everything keeps coming back to you
Most founders who are experiencing the bottleneck problem have already tried to fix it. They have told the team to take more ownership. They have delegated tasks they used to do themselves. They have stepped back from meetings they used to chair. And yet the decisions keep arriving — by message, by phone call, in the corridor before a client call, at the end of a meeting that should have resolved things without them.
The reason the problem persists is that the fix was applied at the wrong level. Delegating tasks moves work outward. It does not move decision authority with it. When a team member is given responsibility for a piece of work but not the authority to make the consequential decisions within it, those decisions have nowhere to go except back to the founder. The work moves. The accountability doesn’t.
Decision authority is a structural element, not a behavioural one. It needs to be explicitly designed and formally assigned — not assumed to follow from a conversation about “taking more ownership.” Ownership without authority is not ownership. It is responsibility without power, which produces deference rather than initiative.
What decision rights actually are
Decision rights are the formal mapping of who can decide what, under what conditions, and at what level. They are not a bureaucratic exercise — they are the foundational design element that determines how authority flows through a business.
In a business without decision rights, authority flows to whoever is willing to exercise it — which in a founder-led business is almost always the founder, because they have the clearest context, the highest stakes investment, and the longest track record of having made the calls. That is how the bottleneck forms. The founder isn’t taking decisions away from the team — the team is handing them up because there is no structural alternative.
In a business with clear decision rights, authority flows to the role that owns the outcome. The sales director decides what to include in a proposal up to a defined commercial value. The operations manager decides which suppliers to use for defined categories of spend. The account lead decides how to handle a client service request within defined parameters. Each decision happens at the appropriate level because the structure says it should — not because the individual chose to be courageous.
Three dimensions of decision authority
Decision rights are typically defined across three dimensions, each of which captures a different type of consequential decision.
Financial thresholds. The most straightforward dimension to define. A role can commit the business to spend, discount, or contractual terms up to a defined value independently. Above that value, sign-off is required. The specific thresholds depend on the business’s size and risk appetite — a £2M business will set different thresholds from a £500k one — but the principle is consistent: define the number, communicate it clearly, and hold it.
Risk categories. Some decisions carry risk that is not purely financial — reputational risk, legal risk, client relationship risk, or risk to the business’s operational continuity. These need a separate framework. A client-facing team member might be able to make a service recovery gesture up to a financial threshold, but any decision that involves accepting liability, changing contract terms, or committing to a performance guarantee above a certain level should require sign-off regardless of the financial value.
Strategic scope. Some decisions are consequential not because of their immediate cost or risk but because of what they commit the business to. Hiring decisions. Supplier relationships that create dependency. Pricing changes that affect the market positioning. Process changes that affect how the business operates. These decisions have a strategic dimension that financial and risk thresholds don’t fully capture — they belong at a level where the full commercial context is understood.
A practical decision authority map
The following table illustrates the structure for a professional services business with a founding director, a senior operations lead, and account or project managers. The specific thresholds are illustrative — the right values for your business depend on its size, structure, and risk tolerance.
| Decision category | Project / Account Manager | Operations Lead | Founder / Director |
|---|---|---|---|
| Supplier spend | Decides <£500 | Decides <£5,000 | Approves >£5,000 |
| Client service recovery | Decides <£200 | Decides <£1,000 | Approves >£1,000 |
| Scope change (client work) | Consults ops lead | Decides if <10% of contract | Approves >10% of contract |
| Hiring decision | Consulted | Recommends | Decides |
| Contract terms change | Flags to ops lead | Reviews and recommends | Decides |
| Day-to-day client communication | Decides independently | Oversees | Not involved |
| Team performance conversations | Owns for their team | Owns for their reports | Not involved unless formal HR |
The table is a starting point, not a template. The categories and thresholds should be built for the specific business. What matters is that the result is written down, communicated to the team, and enforced — both in the sense that the team is held to making decisions within their authority, and in the sense that the founder is held to not making decisions that belong to someone else.
The escalation rule — and why it cuts both ways
A decision rights framework is only as useful as the escalation rule that governs when to invoke it. The rule should be specific: escalate when the decision falls outside your financial threshold, when it carries risk in a category that requires sign-off, or when it has a strategic dimension that affects how the business operates or positions itself. Not when you are uncertain. Not when you want cover. Not when it feels important.
The part founders most often miss: the escalation rule cuts both ways. The team needs to stop escalating decisions that fall within their authority. And the founder needs to stop accepting escalations that shouldn’t have arrived. Every time a founder answers a question that was within someone else’s decision authority, they reinforce the pattern they are trying to break. The structure has to be enforced from both sides.
When a team member escalates a decision that falls within their authority, the right response from the founder is not to make the decision — it is to redirect it. “That’s within your authority to decide. What do you think you should do?” That is uncomfortable for both parties initially. It becomes the norm when it happens consistently.
What changes when decision rights are clear
Without decision rights
- Decisions default to founder by habit
- Team defers rather than decides
- Founder receives escalations that shouldn’t arrive
- Leadership development stunted — team never exercises real judgment
- Capable people disengage when they cannot act autonomously
- Business can only move at the founder’s processing speed
With decision rights
- Decisions made at the appropriate level by default
- Team leads with judgment, escalates with reason
- Founder receives only decisions that genuinely require them
- Leaders develop faster — exercising real authority with real consequences
- Capable people stay — they have genuine scope to lead
- Business scales at the team’s collective capacity, not the founder’s alone
The connection to leadership development
One of the less discussed consequences of absent decision rights is its effect on leadership capability. A team that is never given the structural permission to exercise judgment doesn’t develop judgment. They develop the skill of presenting options to the founder and implementing the founder’s choice — which is a very different thing.
Leadership capability in a founder-led business is often significantly underdeveloped relative to what the team is capable of — not because of lack of potential, but because the structural condition for development is missing. People develop as leaders by making consequential decisions, owning the outcomes, and adjusting their approach based on what those outcomes teach them. That process is unavailable to a team that always defers upward.
Clear decision rights fix the structural condition. They create the environment in which leadership development can actually happen — not through training programmes or coaching conversations, but through the daily exercise of genuine authority within a defined and governed framework.
This is directly connected to the broader founder bottleneck problem, which the post on why founders become the bottleneck covers in full. And if the decision-routing problem is one of several structural issues in the business, the ten signs your business needs a fractional COO provides a diagnostic that covers the full picture.
If decisions keep routing back to you
The Operational Clarity Call is a 45-minute diagnostic that establishes what is specifically broken in your decision architecture — and whether the right intervention is a decision rights design, a structural engagement, or something else entirely.
Book the call →Frequently asked questions
Decision rights are the formal assignment of authority to make specific categories of decision at specific levels of the organisation. They define who can decide what independently, what requires consultation, and what requires sign-off from a senior leader or the founder. When decision rights are clear, the team operates with genuine authority at the appropriate level. When they are absent or ambiguous, decisions default upward to whoever is willing to make them — usually the founder.
Approval thresholds define the boundary between what a role can commit to independently and what requires sign-off. They are typically set across three dimensions: financial (any spend or commitment above a specific value requires approval), risk (any decision that creates a legal, reputational, or client relationship risk above a defined level requires approval), and strategic (any decision that changes how the business operates or positions itself requires approval). The specific values depend on the business’s size and risk tolerance, but the principle is that thresholds should be set high enough to give the team genuine autonomy and low enough to protect the business from consequential unilateral decisions.
Task delegation moves work outward but does not move decision authority with it. When a team member is delegated a task but not the authority to make the decisions that task requires, every consequential choice within the task still routes back to the founder. True decentralisation requires delegating outcomes and the authority to make the decisions that affect those outcomes — not just the work of executing a defined brief.
When decision rights are clear and enforced, leaders develop faster. They are required to make decisions, own the consequences, and develop judgment through the exercise of real authority rather than through the observation of the founder making decisions on their behalf. Leadership capability in a founder-led business is often stunted not because the team lacks potential but because they are never given the structural permission to exercise judgment. Clear decision rights fix the structural condition that prevents development.
Related: the one-page tool that turns decision rights into an operating fact — What is a Threshold-Based Authority Map?
