You are sitting at your desk at 7:30 in the morning, half an hour before anyone else arrives, and your calendar is already full. Not with your own priorities — with other people’s questions, approvals, check-ins, and decisions that somehow landed on your plate. Your inbox has fourteen items requiring action, and eleven of them are things your team could resolve themselves if anyone had clarity on who was supposed to decide. You do not remember choosing to become the central switching station for every operational question in the building. But here you are.
By lunchtime, you will have answered thirty questions, approved a dozen things that did not genuinely need your approval, and spent the better part of two hours solving problems that belong to other people. You will call this “being available.” You will tell yourself that the team needs you, that quality depends on your involvement, that this is what leadership requires. And you will be wrong on all three counts — not because you are a bad leader but because you have confused being essential with being a bottleneck.
Here is the uncomfortable truth: you did not become indispensable. You became a bottleneck. And the difference between those two things is the difference between a leader who scales an organisation and a leader who slowly drowns in it.
Monkey Hoarding: The Mechanism
A “monkey” is any problem, decision, or task that carries ownership. When someone brings you a monkey — a question, a dilemma, an approval request — and you accept it, the monkey has jumped from their back to yours. Monkey hoarding is the pattern of accepting ownership instead of returning it with structure. Every monkey you accept is an invisible meeting added to your week.
The concept comes from a classic management article by William Oncken Jr. and Donald Wass, and it is as precise today as it was when they first described it. The monkey is not the work itself. The monkey is the ownership of the next move. When a team member walks into your office and says “I’ve got a problem — what should I do?” and you answer the question, the monkey has moved. You now own the next step. They walk away lighter. You walk away heavier. And neither of you consciously chose this transfer.
This happens because of four reinforcing dynamics that make monkey hoarding feel completely rational in the moment:
- Solving is neurologically rewarding. When someone presents you with a problem and you resolve it quickly, your brain registers a genuine hit of satisfaction. You were competent. You were fast. You helped. The dopamine reward for solving is immediate and tangible — and it arrives much faster than the slow, invisible reward of developing someone else’s ability to solve it without you.
- Handing off is a relief for the team. When a team member transfers a problem to you, they experience genuine relief. The uncertainty is gone. The responsibility has shifted. They do not have to sit with the discomfort of making a decision that might be wrong. This is not laziness. It is the natural human tendency to seek resolution, and handing the problem to someone more senior is the fastest path to it.
- Decision rights are ambiguous. In most organisations, it is genuinely unclear who has the authority to make which decisions. When the boundaries are fuzzy, the default is to escalate — because escalation feels safer than deciding without permission. The ambiguity is not a personality problem. It is a structural one.
- Quality anxiety drives centralisation. You have seen what happens when things are done without your input. Sometimes it is fine. Sometimes it is not. The fear of quality issues — of something going out that does not meet the standard — creates a gravitational pull toward involvement in everything. The intention is quality control. The effect is that you become the single point of failure for every decision.
These four forces work together to create a system that reliably concentrates ownership at the top. The leader gets busier. The team gets more dependent. Deep work collapses. Strategic thinking starves. And the whole arrangement feels perfectly justified at every step, because each individual monkey transfer made sense in the moment.
Delegation is not a personality trait. It is system design. And the system most leaders have built is optimised for centralisation.
How Bottlenecks Form: Two Patterns
Step 1. A team member sends you a quick question: “Can you sign off on this before I send it?” It takes you two minutes. You reply. Done.
Step 2. Because you responded quickly, the team member learns that the fastest route to a decision is through you. They come back the next day with another question. Then another. Each one takes two minutes. Each one feels trivial.
Step 3. Other team members notice the pattern. If you are the fastest path to resolution, why would they struggle with uncertainty when they could just ask? The requests multiply. Your responsiveness has created a dependency.
Step 4. Within weeks, you are processing twenty to thirty micro-decisions per day that your team could make themselves. Each one is small. Collectively, they consume two to three hours of your day and fragment what remains.
Step 5. Your deep work collapses. The strategic thinking, the planning, the work that only you can do — it gets pushed to evenings and weekends, or it does not happen at all.
Step 6. Strategic work dies. You are now operating entirely in the reactive layer, solving everyone else’s problems while your own highest-value contributions wither. You are working harder than anyone on the team, producing less strategic value than anyone on the team, and wondering why everything feels stuck.
Step 1. You recognise the bottleneck. You decide to delegate. You hand a project to a team member with a vague brief: “Can you take care of this? Let me know if you need anything.”
Step 2. The team member does their best with limited context. They interpret the brief differently from how you meant it. The output comes back, and it is not wrong exactly — but it is not what you had in mind. It misses the nuance. It lacks the quality you expected.
Step 3. You redo the work yourself. It takes you longer than if you had just done it in the first place, because now you are editing someone else’s version instead of creating your own.
Step 4. You conclude, consciously or not, that “delegation does not work.” The evidence seems clear: you tried it, it produced inferior output, and you had to fix it. The lesson your brain draws is that doing it yourself is faster and better.
Step 5. You take everything back. The team member, who was never given proper guardrails or training, learns that their contribution is not trusted. They stop trying to take initiative. They start escalating earlier, not later.
Step 6. The bottleneck hardens. You are now more central than before, and the team is more dependent than before. The failed delegation attempt has reinforced the very pattern it was supposed to break.
This is not a delegation failure. It is a design failure. The outcome was delegated. The decision rights, the guardrails, and the capability were not.
What Not to Do
- Do not delegate outcomes without decision rights. If you hand someone a project but retain the authority to approve every step, you have not delegated. You have created a more complex version of the bottleneck, with extra steps and extra frustration on both sides. Delegation without authority is a performance of delegation. It changes nothing structurally.
- Do not micromanage while calling it delegation. Checking in daily, requesting updates on minor details, asking to see drafts before they are finished — this signals that you do not trust the person’s judgement. The result is that they stop exercising judgement. They wait for your input. They check before acting. You have trained them to be dependent while telling yourself you are empowering them.
- Do not accept monkeys “temporarily.” “I will just handle this one for now” is the sentence that keeps bottlenecks alive. Temporary monkey-holding becomes permanent monkey-hoarding with remarkable speed. If you accept it once, you have set the precedent. The next request will follow the same path, because the system now has a proven route through you.
If you are the only quality-control mechanism, you are not the safety net. You are the bottleneck wearing a safety net costume.
Three Levers That Actually Work
Fixing a monkey-hoarding problem is not about willpower or personality change. It is about redesigning the system that governs how decisions flow through your organisation. Three specific levers do this reliably.
Lever 1: Define Decision Rights
Most escalation happens because nobody knows who has the authority to decide. The fix is explicit: create a simple framework that categorises decisions by type and assigns clear ownership. Four levels are sufficient for most contexts:
- D1 — Team Decides, Informs Leader. The team member or team makes the call and lets you know afterward. You do not approve. You do not review. You receive information, not a request. This is the level for routine, reversible decisions where the cost of a suboptimal choice is low.
- D2 — Team Recommends, Leader Decides. The team does the analysis and presents a recommendation with reasoning. You make the final call. This is appropriate for higher-stakes decisions where the team’s input is essential but the risk warrants your judgement.
- D3 — Team Decides Within Guardrails. The team has full authority to decide, provided the decision falls within defined parameters. You set the guardrails once — budget limits, quality standards, timelines — and the team operates freely within them. This is the level where genuine autonomy lives.
- D4 — Leader Decides. You make the call. This should be rare — reserved for genuinely irreversible, high-stakes, or politically sensitive decisions. If more than ten percent of your decisions are D4, you have not delegated the system; you have delegated the paperwork.
The power of this framework is not in the categories themselves. It is in the act of making the invisible visible. Most teams operate with entirely unspoken decision rights, which means the default is always escalation. When you explicitly label which decisions belong where, escalation stops being the default and starts being the exception.
Lever 2: The Monkey-Return Script
When someone brings you a monkey — a problem, a question, a decision they want you to make — you need a consistent, respectful response that returns ownership without abandoning the person. One sentence does this:
“What do you recommend, and what trade-offs did you consider?”
This sentence does several things simultaneously. It communicates that you expect them to have thought about the problem before bringing it to you. It signals that their judgement matters. It returns the monkey — because now the next move is theirs, not yours. And it provides a development opportunity, because they have to articulate their reasoning rather than simply offloading the discomfort of deciding.
The first few times you use this, there will be resistance. People who are accustomed to handing you monkeys will be mildly uncomfortable with having them returned. That discomfort is diagnostic. It means the system is changing. Stay with it. Within two to three weeks, most team members stop bringing you monkeys and start bringing you recommendations. The quality of those recommendations improves rapidly once people know they will be asked for one.
Lever 3: Buy Back Your Time
Every leader has a set of recurring tasks that consume hours each week but do not require their specific expertise, judgement, or authority. Administrative work. Scheduling. Coordination. Reporting. Data entry. These tasks are real and necessary — but they are not your work. They are work that happens to be on your plate because no one else has been assigned to do it.
The calculation is straightforward. If you spend five hours a week on tasks that someone else could do — either by delegating internally or by paying for external help — that is roughly 250 hours per year. Two hundred and fifty hours of your highest-value time, consumed by work that does not require your highest-value thinking. The cost of not delegating this is not the five hours per week. It is the strategic and creative work that those five hours would have produced.
Two paths to buying back time:
- Internal delegation. Identify the administrative and coordination tasks on your calendar and explicitly reassign them to team members with the capacity and competence to handle them. This is not dumping. It is role clarity. Many of these tasks are development opportunities for the people who take them on.
- External support. When the cost of hiring help is less than the value of your reclaimed time, pay for it. A virtual assistant, a bookkeeper, a coordinator — the specific role depends on your context. The principle is the same: if someone else can do it well enough and freeing your time creates more value than it costs, the maths is clear.
The psychological barrier to buying back time is the feeling that you should be doing everything yourself. That feeling is not leadership. It is martyrdom dressed as dedication. Leaders who insist on doing everything themselves are not demonstrating commitment. They are demonstrating that they have not built a system that works without them.
Delegation Blueprint (45 Minutes)
- List your top 10 recurring decisions and tasks. Open your calendar and inbox from the past two weeks. Identify the decisions, approvals, and tasks that appear most frequently. Be specific: not “admin” but “approving expense reports,” not “team support” but “answering technical questions about the client database.”
- Label each one D1, D2, D3, or D4. For each item, ask: Does this genuinely require my judgement, or has it landed on my desk out of habit? Be honest. Most leaders discover that six or seven of their top ten items are D1 or D3 — decisions the team could make with clear guardrails.
- Choose 3 items to redesign this week. For each one, define: (a) who owns the decision going forward, (b) the guardrails — a simple “definition of done” that specifies what good looks like, and (c) the check-in cadence — how often you review, not through constant pings but through a scheduled rhythm (weekly, fortnightly, or at milestones).
- Write your monkey-return script. Decide on the exact words you will use when someone brings you a problem that belongs in the D1 or D3 category. “What do you recommend, and what trade-offs did you consider?” is a strong default, but adapt it to your natural language. The key is consistency — use the same response every time so the team learns the new pattern.
- Identify one time-buyback opportunity. Look at your recurring tasks and find one that does not require your expertise. Decide whether to delegate it internally or source external support. Calculate the hours per week it would free up. Multiply by fifty weeks. That number is your annual leverage gain.
- Set a 30-day review. Delegation redesign takes time to settle. After thirty days, revisit your list. Check which items have genuinely shifted, which are creeping back, and which need further adjustment. Adjust the guardrails if quality slipped. Tighten the script if monkeys are returning. This is iterative work, not a one-off exercise.
| Decision Level | Who Decides | Leader’s Role | Example |
|---|---|---|---|
| D1 | Team decides | Informed after | Scheduling, routine client follow-up |
| D2 | Team recommends | Final call | Budget reallocation, hiring shortlist |
| D3 | Team decides within guardrails | Sets parameters | Project scoping, vendor selection under limit |
| D4 | Leader decides | Owns decision | Strategic direction, irreversible commitments |
Most leaders discover that seventy percent or more of the decisions currently on their desk belong in D1 or D3. The first time you do this exercise, the number is usually confronting. That is normal. The point is to see the pattern and start shifting it deliberately.
The Real Cost of Not Delegating
The cost of monkey hoarding is not just your exhaustion — although that is real and compounding. The deeper cost is what your team never becomes. When you hold every decision, you deprive your team of the experience of deciding. They do not develop judgement, because they never exercise it. They do not build confidence, because they never carry the weight of ownership. They remain perpetually junior, perpetually dependent, perpetually waiting for you to tell them what to do — not because they lack capability but because the system you have built never requires them to use it.
This is the part that stings: the leader who does everything is not building a strong team. They are building a fragile one. One that cannot function without them. One that collapses the moment they are unavailable. The very indispensability the leader has cultivated is the thing that makes the team brittle.
If your team cannot function without you for two weeks, you have not built a team. You have built a dependency.
Delegation is how leaders scale themselves. Not by working longer hours, not by being more responsive, not by processing more monkeys faster — but by building a system in which decisions happen at the right level, ownership sits with the people closest to the work, and the leader’s time is freed for the things that genuinely require their attention: strategy, culture, the hard conversations, and the long-term bets that no one else in the organisation is positioned to make.
Key Takeaways
- Monkey hoarding is a system problem, not a character flaw. You did not choose to become the bottleneck. The system evolved to route everything through you because decision rights were unclear and solving felt rewarding. Fix the system, not yourself.
- Define decision rights explicitly. Label recurring decisions D1 through D4. Most of what sits on your desk belongs in D1 or D3 — decisions your team can and should make without you, given clear guardrails.
- Use the monkey-return script consistently. “What do you recommend, and what trade-offs did you consider?” returns ownership, develops your team’s judgement, and breaks the escalation habit in two to three weeks.
- Buy back your time ruthlessly. Five hours per week of delegated low-leverage work is 250 hours per year of reclaimed capacity for the work that only you can do.
This is the final piece of the puzzle. Across the ten posts in this series, we have moved from the foundational insight — that attention, not time, is the scarce resource — through the structural, interpersonal, and systemic levers that determine how your days actually unfold. Delegation is where it all converges: the point at which individual time management meets organisational design, and the leader stops trying to do everything and starts building a system that works.
The question was never whether you could work harder. You have already proven that. The question is whether you can build something that does not depend on you working harder. That is leadership. And it starts with giving the monkeys back.
If you want help redesigning your delegation system — defining decision rights, building the scripts, and buying back the hours that belong to your strategic work — that is the work I do.
Get in TouchFrequently Asked Questions
It is accepting ownership of other people’s problems. Every time you take the monkey, you become the bottleneck and the team becomes dependent. The monkey is not the work — it is the ownership of the next move.
Define decision rights and a “definition of done.” Delegate outcomes with guardrails, then review on a cadence — not through constant interruptions. Quality comes from structure, not surveillance.
“What do you recommend, and what trade-offs did you consider?” It returns ownership without abandoning the person, and it develops their judgement by requiring them to think before they escalate.
Remove low-leverage work from your calendar and fund it with support — internal delegation or paid assistance — so your hours go to leverage. Five hours per week reclaimed is 250 hours per year redirected to your highest-value work.