Practical Solutions · Save time · Illustrative example

How to stop being the bottleneck in your business

By Geoff Greenwood FCCA, MBA, MSc · 6 min read

Aqua pathways pass through a narrow central opening and separate into clear lanes, illustrating a shared approval bottleneck.

When every ordinary decision returns to the owner, the answer is rarely better time management. Make authority clear enough for work to move without removing the controls that matter.

Illustrative business scenario—not a reported client result.

Late on a Thursday, a routine client appointment needs to move. One person wants to protect the technician’s route. Another wants to keep the client informed. Both know the owner can decide in two minutes, so both wait.

The owner sees the message between a supplier call and a recruitment issue. A routine decision joins the queue. By the time it is made, the appointment has moved twice and the client has been asked for the same information by two people.

This need not be a problem with commitment or confidence. The business has not made clear who can decide what, and on what basis.

The owner becomes the default answer

Centralising decisions makes sense early on. It becomes a problem when the business grows but the arrangement does not.

Waiting becomes normal. People keep unresolved questions in mind, interrupt one another for updates or proceed without enough information. Asking the owner feels safer than acting. These are conditions around the work, not simply a lack of initiative.

Every unanswered decision creates return traffic to the owner. This is also a collective-execution problem; see Alignment Is Not an Offsite: The Conditions for Collective Execution.

Why “take ownership” does not settle authority

Delegation training can help. So can an email asking people to take ownership. Neither answers the questions that slow work down: Which decision is mine? What limits apply? When must I involve someone else? What happens if two priorities conflict?

“Take ownership” can leave someone carrying responsibility without authority. Escalation is then rational, not a failure of initiative. The owner reads the question as dependency; the employee experiences it as risk.

A task says what work to complete. A decision right says someone may choose between defined options, within stated limits, without another approval.

Define decision rights before you delegate

Decision rights specify who may decide what, within what limits and when an issue must be escalated. They preserve control by making it visible rather than keeping it inside the owner’s head.

For a recurring decision, state the decision, the decision-maker, the outcome it protects, the limits that cannot be crossed and the escalation triggers. Keep it short enough to use while work is happening.

This is not unrestricted autonomy. The HSE describes control as the degree of say a person has in how they do their work, while its guidance on role emphasises clear responsibilities and a way to raise uncertainty or conflict.[1] Clear decision rights hold both: enough authority to act and an explicit route for cases that do not safely fit the boundary.

A meta-analysis—a study that combines findings from earlier studies—found positive relationships between empowering leadership and several work outcomes. It does not prove that this approach will improve profit in a particular business.[2]

Give bounded authority in an ordinary situation

Take routine appointment changes. An operations coordinator might move a client appointment between already available slots in the next fortnight, confirm the new time using the agreed message and update the scheduling system.

They cannot change service scope, override a safety requirement, make a priority promise affecting another client or commit a colleague whose availability is unconfirmed. A complaint, no viable slot, or a conflict between client commitments goes to the team lead.

The owner still sets service commitments and limits. They do not need to resolve each ordinary rearrangement.

Start where work comes back

Do not map every decision. Start with one recurring point where work returns to the owner, a manager or a shared inbox. This is a pragmatic starting sequence, not a scientifically validated protocol.

  1. Choose one decision type and collect a few recent examples.
  2. Identify the legitimate outcome, usual options and boundaries that have mattered.
  3. Name the decision-maker and escalation triggers in plain language.
  4. Test the rule in the next few cases, then revise it if the boundary is unclear or too broad.

The test is not that nobody escalates. It is that routine cases move without repeated clarification, while exceptional or higher-risk cases surface early enough for the right person to decide.

Measure flow, not optimism

Take a four-week baseline and compare it with a similar four-week period after the decision right is used. Keep the context comparable where possible: a seasonal peak or new system rollout can distort the picture.

Track three things: the median time from a decision being needed to it being made; cases returning to the owner after a decision-maker is named, tagged as an unclear boundary, genuine exception or reversal; and repeat clarification on the same case.

The business opportunity is less repeated handling and more reliable delivery. If that avoids overtime or prevents an appointment being lost, measure the actual spending or contribution protected. If the owner simply spends fewer hours on approvals, that is released capacity—not automatically cash saved.

Preserve the escalation route

Some escalation is necessary. It protects customers, people and the business when a commitment, safety requirement, role boundary or conflict of priorities is at stake. Role safety matters too: people need permission to raise uncertainty without being treated as evasive.

If the same decisions still return after boundaries are clear, the constraint may sit elsewhere: workload, missing information, a manager’s span of control or competing service commitments. The question is not simply whether to delegate more. It is which part of the operating system is causing work to wait.

A Workforce Capacity Audit can examine that context, including workload, role clarity and decision rights, without reducing the issue to employee scores. It is finite and scoped only where that diagnosis would be useful. To clarify whether this is the business constraint you are facing, Request a Workforce Performance Conversation.

Sources

  1. [1]
    HSE Management Standards overview

    Supports describing control and role clarity as work-design conditions, including clear responsibilities and routes to raise uncertainty or conflict.

    Limitation: Regulatory guidance on work-related stress and work design; it does not test this article’s specific decision-rights sequence or commercial outcomes.

  2. [2]
    Empowering leadership: A meta-analytic examination of incremental contribution, mediation, and moderation

    Provides a review-level directional rationale: the meta-analysis drew on 105 samples and reported positive relationships between empowering leadership and several work outcomes.

    Limitation: The evidence does not establish that a decision-rights intervention will cause a specified outcome in an individual growing UK business.