The Approval Chokehold
We were asked to look at why a mid-sized services firm had gone from winning work to missing deadlines on work it had already won. The answer was not in the delivery team. It was in a queue. On the day we visited, forty one items sat waiting for one signature. Two were urgent. One had been waiting nineteen days. The person who was supposed to sign them all was in meetings for six hours a day.
This is the approval chokehold. It is rarely a person being difficult. It is a structure in which one desk has been handed the power to say yes to everything, and no power to say no to anything.
How the chokehold forms
Nobody designs it. It grows. A purchase limit starts at a sensible number. Then a bad decision somewhere makes the leadership nervous, so the limit comes down. A discount authority gets pulled up a level after one deal went wrong. A hiring decision moves from the manager to the department head, and then to the head of the department head, because a bad hire was expensive once. Each move is reasonable in isolation. Together they move the traffic of the whole company onto a smaller and smaller number of desks.
By the time anyone notices, the founder or the director or the plant head is the single point through which every non-trivial decision must pass. Approvals for a laptop, a leave request, a client proposal, a replacement part and a new hire all land in the same inbox, and they all wait in the same order.
What the queue actually costs
The obvious cost is time. The hidden costs are worse.
- Momentum dies. A decision that needed a yes on Tuesday gets a yes on Friday. The client has already gone quiet. The candidate has already accepted elsewhere.
- People stop deciding. When every call is escalated, managers learn that deciding is risky and escalating is safe. The skill of judgement, which is what you actually pay managers for, slowly leaves the building.
- The queue becomes a hiding place. A stalled project has a ready excuse: it is with the boss. Nobody is accountable because everyone is waiting.
- The approver becomes a bottleneck and a single point of failure at once. If they are unwell, on leave, or travelling, the company pauses.
We have seen teams measure this without meaning to. One operations head kept a private note of how long her own requests took. The average was eight working days for anything above a modest sum. She had started building the delay into her plans. When you plan around your own company's slowness, the slowness has become a permanent tax.
Why the approver does not see it
The person at the top of the chokehold usually believes they are being careful. From their desk, each item looks like a small, sensible check. They do not see the queue, because a queue looks like a full inbox, and a full inbox looks like being important.
They also cannot feel the cost, because the cost is paid downstream. The delay is absorbed by the team that had to redo the plan, the client who waited, the candidate who left. None of that lands back on the approver's desk. They see a clean, controlled process. The floor sees a company that cannot move.
There is a second blindness. The approver is often the person who understands the business best, which is why the authority was concentrated there in the first place. The very competence that made them the bottleneck is the reason nobody wants to take the decisions away.
The signs to look for
The chokehold is easy to confirm once you know what to look for.
- One name appears on almost every approval trail, whatever the category.
- Managers can quote the current approval thresholds from memory, because they hit them constantly.
- There is a standing joke about how long the boss takes to reply, and it is not really a joke.
- Urgent items and routine items share the same queue and the same order.
- Decisions are re-opened after they were made, because the approval came with conditions attached at the last minute.
If you can draw the flow of decisions as arrows, and one desk has more arrows entering it than any other, you have found the chokehold. It is usually visible on a single sheet of paper.
What actually fixes it
The fix is not to tell the leader to let go. That advice never survives contact with a bad decision. The fix is to move authority deliberately, in writing, with limits that are clear and consequences that are understood.
Set thresholds that mean something. A manager who can approve up to a real number, not a token one, will use the authority and learn from it. Give a small number of people the power to say yes within a stated range and the duty to explain any decision that turns out badly. Most will make good calls, because most people make good calls when they own the outcome.
Route by category, not by seniority. A leave request, a software licence and a client discount are different kinds of risk and do not belong in the same queue. Give each a home closer to where the work happens. Keep only the genuinely large or irreversible decisions at the top.
Then watch the queue, not the person. Measure how long items wait, by category, every week. The number will tell you whether authority has actually moved. If the wait time does not fall, the thresholds were raised on paper but not in practice.
Why this is worth doing now
A chokehold feels like control and behaves like paralysis. The company looks disciplined from the top and feels stuck from everywhere else. The people who can tolerate the waiting stay. The people who cannot, leave, and they are usually the ones who were comfortable making a call.
Authority is not a fixed quantity you must guard. It is a tool you place where the work is. When you move it deliberately, you get faster decisions and better ones, because the person closest to the problem is the person making the call. When you leave it stacked on one desk, you get a queue, and a queue is just a slow way of saying no.
We do not guess. We investigate. Before we advise on structure, we map the real approval trail, the one people actually follow, and we count the days. The map usually explains more than any org chart.