A delivery manager has a pricing query. The operations lead wants to extend a client deadline. A complaint has come in and someone needs guidance on how to respond. Taken individually, each one is a quick question. Together, they are how a founder ends up making forty decisions before lunch in a firm with twelve capable people on the payroll.
The pattern is common. And the cause is nearly always structural.
What does it mean when your team keeps coming to you?
Decision escalation happens when someone pushes a decision upward rather than resolving it at their own level. Early on, that is often appropriate: the owner holds the context and the authority. As a firm grows, the habit persists past the point where it serves a purpose. In many firms, the underlying cause is an absence of clear decision rights: who decides what, and where the boundary sits.
The pattern has two layers. The first is structural: as firms add people and complexity, ownership of day-to-day decisions becomes blurred. Nobody has explicitly defined who has authority over pricing, complaint resolution, or delivery scope. The second is behavioural: if the downside of making a wrong call feels bigger than the downside of interrupting the founder, staff will escalate.
UK risk management guidance makes this distinction clearly. The NCSC’s risk management collection assumes that escalation routes should be defined rather than improvised: you know who owns what, what triggers a genuine escalation, and where it goes. That discipline applies to any organisation handling operational complexity, not just large enterprises. A fifteen-person services firm operating without defined decision routes is improvising every time something unexpected comes up.
The NCSC also draws a line between informal escalation, where issues drift upward through habit, and structured escalation, where there is a defined route, a defined threshold, and a defined owner. Many service firms operate in the first mode. Moving to the second requires a set of decisions about who is trusted to decide what, not a governance overhaul.
Why does the pattern stick once it has started?
Every time a founder steps in to answer a question a manager should have resolved, the dependency deepens. The team learns that escalation is the fastest route to an answer, and that the downside of deciding for themselves outweighs the cost of interrupting the owner. Decisions that should take minutes stretch into hours as they queue at the top of the firm.
The reinforcement is subtle. If the founder regularly adjusts a manager’s pricing call after the fact, or steps in to resolve team disagreements that could have been settled at the delivery level, the team receives a consistent signal: escalation is safe, deciding is risky. Over time, even confident and capable people start framing things as questions when they already know the answer.
Commentary on UK management describes how diffuse accountability stretches decision timelines in growing firms, often turning calls that should take minutes into multi-hour waits as information bounces between levels. The authority structure around the team was simply never updated to match the scale of the business.
The problem feels to the founder like an interruption challenge. In structural terms, the operating model never specified who should carry the decisions that are now landing at the top. Changing the habit requires changing that structure, not managing people more assertively or asking the team to show more initiative.
Where does the escalation pattern show up in a service firm?
Service businesses have more grey areas than production businesses. Pricing a scope change, handling a complaint, deciding whether to extend a deadline: these are judgement calls. Staff in client-facing roles often seek a second opinion because the cost of getting it wrong falls on a real relationship. That combination of time pressure and high stakes is where escalation to the owner becomes the default move.
The categories that generate the highest volume of repeat queries tend to be consistent across service firms: pricing exceptions, complaint resolution, workload allocation, and decisions where a client relationship feels at risk. Founders often describe a similar pattern: they are rarely interrupted by genuinely novel questions. The interruptions are about the edges of familiar situations, the scenarios where the usual rule does not quite fit and someone wants confirmation before acting.
Those situations are predictable in aggregate. They are the scenarios a decision-rights document should cover first: what to do when a client asks for a discount outside the agreed band, what a manager can offer to resolve a complaint, what threshold triggers a formal escalation versus a brief call to a senior colleague. Documenting the common cases removes a significant share of repeat escalations without any change to headcount.
Analysis of why strategy stalls in growing firms identifies unclear accountability as a primary driver of operational friction, particularly in businesses where the founder has not yet separated strategic oversight from day-to-day delivery involvement. The escalation queue is often the visible symptom of that gap.
When is escalation the right call, and when is it a symptom?
Some issues should reach the founder or a specialist: anything touching personal data, a regulatory matter, or serious reputational risk genuinely sits beyond a manager’s authority. The problem arises when the same routing applies to routine pricing, standard complaints, and everyday delivery calls. When ordinary decisions queue alongside exceptional ones, the owner becomes the bottleneck for work the team is qualified to handle.
The ICO is clear that organisations are accountable for personal data handling. A suspected data breach, a complaint about how client information was used, or an access request outside normal processing are situations where structured escalation is appropriate and, in some cases, legally required. In 2020, the ICO fined British Airways £20 million following a data security failing. In 2023, Interserve Group received a £4.4 million penalty over a cyber security failing.
In both cases, the accountability frameworks behind the judgements examined whether appropriate governance and escalation had been in place. For service firms that handle client data, the implication is practical: certain escalations are obligatory. Firms with regulated activities face similar expectations. The FCA’s Consumer Duty rules reinforce that regulated firms are expected to have effective oversight structures, including the ability to identify and escalate issues that could affect customers.
The distinction that matters is between issues that genuinely sit outside delegated authority, such as data incidents, legal exposure, or regulated activity, and routine calls that have been treated as exceptional by habit. Defining the boundary clearly means the team knows what to escalate, and the founder knows what to send back down.
What does a decision system look like in a firm your size?
A decision system for a firm of five to fifty people does not require an org chart overhaul. It needs three things: a written list of what each manager can approve without asking, thresholds that trigger a genuine escalation (by value, by risk, or by external obligation), and a monthly review of repeat escalations to find the training or process gap behind them.
In practice, the decision-rights document can be a single page. A first column covers the decision type: pricing exception, complaint resolution, deadline extension, staff allocation. A second names who resolves it without checking in. A third sets the threshold: a fee above a stated value, a complaint with a legal dimension, a client relationship at formal risk. That document replaces the founder as the default reference point for the edge cases that currently take up the diary.
The monthly review of repeat escalations is the element many founders skip. When the same type of issue keeps arriving at the top of the firm, the process, the authority level, or the training is wrong somewhere. Reviewing for patterns once a month is usually enough to find the root cause and address it, rather than treating each occurrence as a one-off.
The goal is a firm where the operating model is visible enough that others can run it without asking permission for everything. A business structured that way is more resilient when the founder is away, easier to hand off in the future, and capable of making decisions at the pace the market requires. If the pattern feels too entrenched to shift with a document alone, Book a conversation to work through the decision-rights and governance gaps that are keeping you in the loop.
