Decision Hoarding

Decision Hoarding: The Pattern That Turns a Leader into a Bottleneck

#TheExecutiveChallenge — Article #5

“Fourteen meetings a day just to say yes or no. And just like that, the quarter is gone.”

A quote from a VP of Operations, six months after their promotion. It wasn’t a workload problem. It was an architectural problem. The pattern has a name:

Decision Hoarding. The leader holds onto decisions that shouldn’t be on their desk.

Harvard Business Review, in “How to Stop Micromanaging and Start Empowering,” describes the phenomenon at its root: most micromanagers don’t choose to be one. They find themselves doing it out of inertia. Decision Hoarding is the executive version of this pattern. It’s not a lack of trust in the team—we addressed that two issues ago when talking about the Trust Tax. It’s not an inability to think big—we saw that in the last article; it’s the “expert mode” that blocks you. It’s something more subtle: the absence of decision-making architecture. The thing no one teaches you in forty years of leadership literature isn’t how to delegate more. It’s how to select better.

The Systemic Cost

McKinsey, in the research “Decision making: how leaders can get out of the way,” highlights that the vast majority of decisions reaching executive desks are reversible. They are Type 2 decisions, according to Jeff Bezos: doors that can be reopened, consequences that can be contained. Yet, the leader treats them as irreversible Type 1 decisions, weighing them down to the milligram.

The result is threefold, and it is felt within the company even when no one names it.

The decision cycle lengthens. A choice the team could have closed in two hours waits for three days. Multiply that by twelve decisions a week, and you’ve burned through a quarterly execution.

The team stops proposing. They realize every proposal becomes a wait, and they adapt. They start asking instead of suggesting. The quality of discussion progressively declines, and you don’t notice because you are inside the noise.

And you lose strategic altitude. You stop seeing the system from above because you are inside the system, approving the color of a button.

A 2017 HBR study on strategic delegation put it surgically: every decision a leader keeps beyond their zone is missed training, stolen from the system. You pay for it at the time of the next transition when you need a team that decides autonomously, only to find they were never trained.

Walk the Talk

At Citroën, in 2004, I found myself in exactly that position. I was personally approving every detail of the co-branding operations with Dolce & Gabbana. Every shoot, every claim, every page layout. I told myself I was safeguarding the quality of the positioning. In reality, I was strangling my team. One morning, the media manager told me: “Massimo, we have 10 minutes for your OK, otherwise we lose an editorial window in Vogue.”

That afternoon, I took an A4 sheet of paper. I drew three columns. What I decide. What I ratify. What the team closes and informs me of after the fact. I had redesigned the system. From that moment on, I started thinking again about the brand positioning—which was the job I had been hired for.

What Keeps You There

Before talking about concrete moves, here is a question I always ask in coaching: what gratifies you about being called for every “yes”? The answer that emerges, after a few minutes of silence, is almost always the same. There is a certain professional identity that feeds on the idea that “without me, no decision is made.” There is the dopamine of the message on the phone arriving on a Saturday morning. There is the confusion—built over a thirty-year career rising through technical merit—between being present and being useful. Decision Hoarding is not just an operational problem. It is a crystallized role identity that is now blocking the system. The first task of serious coaching is not to give you a delegation framework. It is to help you see what lies beneath the struggle of letting go.

Three Concrete Moves

Decision Audit, one week. For seven working days, track every decision that comes to you. Three questions, written alongside: was it reversible? could I have not been called? did the team learn something by bringing it to me? This is the first step of the awareness work that opens every path in the U.N.L.O.C.K. method: before changing the system, see it. At the end of the week, the pattern emerges on its own. In most cases, a very large portion of decisions falls into the “it shouldn’t have reached me” zone. That data changes the picture.

Three explicit decision zones.

Zone one: Type 1 decisions—irreversible, asymmetric, strategic. These stay on your desk.

Zone two: Decisions the team proposes and you ratify, typical of cross-functional contexts or those with reputational exposure.

Zone three: Decisions the team closes and informs you of post-facto—operational, reversible, below the risk threshold.

The critical point is the second half: communicating the three zones explicitly to the team. An implicit framework doesn’t work because no one knows where it stands. HBR, in “Should You Delegate That Decision? Ask These 4 Questions,” proposes four selection filters based on this logic: before deciding whether to delegate, map where the decision sits. A warning from the field: the first architecture will be imperfect. The three zones are calibrated in the first four to six weeks of application, not on the first try.

The 70 percent rule. Bezos formalized it years ago, and it still works: if you have seventy percent of the information you need, decide. Waiting for ninety percent costs more than a Type 2 error corrected on the fly. Apply the same threshold to the team: if they ask you for input and they have seventy percent of the necessary information, send the decision back to their desk. In this way, a request for approval transforms into an exercise in decision ownership. This is what David Marquet, in “Turn the Ship Around,” calls moving authority toward information: the person with the data at hand is the one who should decide.

A Note from the Field

The Institute of Coaching published a study with a significant title: “Two faces of empowering leadership.” Empowerment has two faces, the paper says: it is enabling when there is a clear framework; it is burdensome when the framework is missing. More autonomy without architecture is not mature leadership—it is abandonment. Your job is not to hand over decisions like you hand over tasks. It is to design the system within which they are made. The mature leader is not the decision-making center. They are the architect of the conditions in which others decide well.

The error I see most frequently in VPs during the first 90 days of a new role is confusing speed with impact. They arrive with solutions, messages, and priorities already defined, before having truly read the context. But those who enter well must not only explain where they want to go: they must see the dynamics, the alliances, the resistances, and the conversations that have not yet emerged.

That VP with the fourteen meetings, six months later, was doing six. Not because they had learned to delegate. Because they had stopped confusing their presence with their value.

Decision Hoarding is not cured by delegating more. It is cured by selecting better.

How many decisions did you make today that your team would have made better than you, if only you had told them how?

In the next article: Three decision zones work when people report to you hierarchically. But what happens when you have to exercise lateral leadership—over peers, over functions you don’t control, over external stakeholders? It’s the next pressure point: Influence without authority.

Domande Frequenti