Working with a manager who hoards decision-making, you may sense a message that is never spoken. You feel it in the decisions they take back, the work they redo, and the approvals that keep returning to their desk: No one can do this as well as I can.
Sometimes that belief is justified. They know the supplier, remember why the last agreement failed, and recognize a problem before anyone else sees it. Their competence is real. That is what makes the trap difficult to recognize.
Early in a career, being the person who can solve the difficult problem creates opportunity. People bring you more responsibility, and the experience makes you better. But as the organization grows, it needs something more from you: other people who can make good decisions, including when you are unavailable.
A leader’s expertise can remain valuable long after the organization’s dependence on it becomes expensive.
The Leader Who Won’t Let Go
The trap begins with a reasonable decision: I’m better at this, so I should do it. Repeat that decision often enough and the supplier relationships, difficult questions, and authority gather around the same person. The leader becomes more experienced while everyone else gets fewer opportunities to learn.
There is a related idea in organizational learning research. Barbara Levitt and James March describe how success with an established approach can keep an organization from gaining enough experience with a better alternative. Their discussion of competency traps concerns organizational routines; the leadership pattern here follows a similar logic. Doing the work yourself keeps proving useful while developing someone else keeps looking inefficient.
From the outside, this can look like a leader carrying the business. Every important question reaches the same desk, and everyone knows whom to call when something goes wrong. Yet the business is also becoming dependent on one person’s attention.
Decisions that once benefited from the leader’s involvement eventually begin waiting for it.
How Dependence Becomes Self-Fulfilling
Eventually, the leader looks around and notices that nobody else knows how to do the work. That seems to confirm the original belief: I have to stay involved. But the leader retains responsibility because others lack experience, and others lack experience because the leader retains responsibility.
People adapt. When a purchasing manager’s decisions are repeatedly overridden, checking first becomes safer than taking ownership. When supplier conversations happen without them, they have less context for the next negotiation. What looks like hesitation may be a sensible response to the way the work is managed.
The leader then sees that hesitation as another reason to hold on. The system keeps producing evidence in its own defense, even when the people inside it are capable of more.
The organization may have trained capable people to be dependent.
When Delegation Feels Like Risk
Once that dependence exists, delegation does carry risk. Someone making a decision for the first time will not have the judgment of someone who has made it for fifteen years. The experience gap needs attention, especially when a mistake could affect customers, cash, or production.
But keeping every consequential decision also carries a cost. The leader stays overloaded, the team stays inexperienced, and the next attempt to delegate feels just as difficult. At some point, people need the opportunity to exercise judgment while someone experienced is still available to help them develop it.
That requires more than handing over a task. A purchasing manager needs the supplier history, the reasoning behind acceptable terms, access to the people involved, and clear authority to place an order. Assigning the work while retaining every decision leaves the dependence intact.
Delegation becomes more workable when the leader defines what the person can decide, what needs review, and how they will learn from the results. Authority can expand as capability grows. The leader’s job includes creating the conditions that make that growth possible.
Working With a Bottleneck Leader
If you work for a leader caught in this pattern, begin with the outcome they are trying to protect. A purchase approval may be about cash exposure. A supplier relationship may carry a history of quality problems. A proposal review may be about margin or a promise the business will struggle to keep.
Those concerns deserve a clear answer. Ask, “What would you need to know to be comfortable with me making this decision?” Then help translate the answer into a usable boundary: an approved supplier, a spending limit, a minimum margin, or a condition that requires escalation.
The aim is to move the conversation from permission to parameters.
Make the proposal small enough to evaluate. You might ask to handle routine orders from an approved supplier for the next month, within an agreed budget, with a short weekly review. Put the agreement somewhere both of you can refer to it. The review should show what you decided, why, and what happened—not quietly become another approval queue.
It also helps to make the waiting visible. Track the time between a purchase request and a decision, then connect the delay to the work it holds up. “These orders waited for approval while the production window narrowed” gives you a concrete process to improve together. Keep delayed revenue, lost orders, and additional costs distinct; they tell different stories about the consequence.
This is the practical work behind boundaries that create better decisions: agree on what you can do, what information should guide you, and when you need help. If the leader will not agree to those boundaries, make the unresolved decision and its consequence visible. You can propose a better arrangement; the authority to establish it still belongs to the leader.
From Bottleneck to Scaffolding
I have watched this play out in the sourcing of a critical raw material. A senior leader retained control of purchasing and brought years of supplier knowledge and pricing experience to the decision. People closer to production could see demand developing and inventory tightening, but they did not have sufficiently clear authority to act.
Eventually, there was not enough material. Production was constrained, orders could not be fulfilled as quickly as they otherwise could have been, and revenue was lost.
We had demand. We didn’t have material.
A purchasing error alone does not tell us whether a leader should retain a decision. Forecasts change, suppliers miss commitments, and experienced people make mistakes. What matters here is that the organization could see the need developing without having a dependable way to respond.
Consider what a different arrangement could have looked like. This is a proposed redesign of the situation, not a claim about what the company later implemented.
Think of the leader’s support as scaffolding around a building under construction. It helps the work rise in the right direction while the structure gains strength. As the building becomes able to stand on its own, the scaffolding comes away. Developing a decision-maker calls for the same intention: provide enough support to keep growth moving, then reduce that support as the person becomes capable of carrying the responsibility.
The leader, purchasing manager, production team, and finance lead would agree on an inventory floor and an earlier reorder trigger. The trigger would account for expected consumption during supplier lead time, confirmed incoming stock, and a safety allowance. Waiting until the material reached its minimum level could already be too late.
Changes in booked orders, the production schedule, or supplier lead time would trigger a fresh look at the projected balance. The purchasing manager would own that check and the resulting action. A forecast would then have a defined consequence, rather than depend on whether someone noticed it in a report.
Purchasing authority would sit inside an agreed dollar range, with approved suppliers, acceptable terms, and limits on total commitments. Orders within those boundaries could proceed without another approval. A price increase beyond the agreed tolerance, a new supplier, a quality concern, or a commitment outside the budget would go to the leader, with a response deadline and a named backup when the leader was unavailable.
At first, the leader and purchasing manager might work through orders together, comparing the reasoning behind each decision. A shared view of inventory, incoming orders, spending, and exceptions would give those conversations something concrete to work from. The manager would make the decision with support, gaining experience while the leader remained available to help.
They would also agree on when that support should change. As the manager consistently recognized risks, stayed within the budget, and escalated the right exceptions, joint reviews could become occasional check-ins. The manager could take on larger commitments and more complex supplier conversations. Each step would remove a piece of scaffolding rather than add another layer of approval.
The role would still carry financial limits and accountability. What would come away is the extra supervision needed while someone learns. The leader’s experience would have done its job when the purchasing manager could explain the decision, act on it, and recognize when to ask for help.
That would not guarantee a shortage-free operation. It would give the organization a way to act on what it knew before a shortage became unavoidable.
Turn Judgment Into Infrastructure
The useful work begins with asking an experienced leader how they decide. What makes you order sooner? Which supplier terms worry you? What changed your mind the last time we faced this? Walk through a real decision together and record the reasoning, including the exceptions.
Some of that judgment can become a threshold or an operating rule. Some needs to be learned through shared decisions, supplier conversations, and review. A checklist cannot hold fifteen years of experience, but it can make the recurring parts visible and leave more room to teach the difficult ones.
Economists Michael Jensen and William Meckling make a useful distinction in Specific and General Knowledge, and Organizational Structure: communicating information is not the same as transferring knowledge someone can act on. Their analysis also connects the placement of decision authority to the cost of moving knowledge, alongside the controls that delegation requires.
That gives the practical task its shape: turn judgment into infrastructure. Document the decision rights, teach the reasoning, establish the review, and keep the rules current. The test is whether another person can use what has been shared to make a sound decision.
This is also where succession begins. Knowledge becomes useful beyond its original owner while that person is still present to explain it, challenge its application, and help someone improve. The leader’s experience starts building capability instead of accumulating requests.
Decision Architecture Is Revenue Architecture
Budgets, forecasts, and sales plans assume the organization can act. Underneath those plans sits a question with commercial consequences: who is allowed to decide what, with which information, and by when?
If every consequential decision must climb the hierarchy, the hierarchy becomes part of the organization’s lead time. A production slot can disappear while an order awaits approval. A customer can find another supplier while the business decides whether it can commit. The decision process shapes how much of the opportunity the organization can actually deliver.
That is why decision architecture is revenue architecture.
A leader can make excellent decisions all day and still constrain the business. The next question is whether the organization can make good decisions without requiring that leader to make all of them. Answering it means giving people the context, authority, and practice to carry more of the work.
Expertise creates more value when it helps the organization move.