The manager who will not delegate

The problem it solves

Failure to delegate almost never presents itself as such. It presents as an owner working Saturdays, a team waiting on answers, and small decisions taking days because only one person can make them. It shows up in smaller things too: approvals that stack up whenever the owner travels, or the supervisor who knows what to do and asks anyway, because the last time they decided alone they were overruled in front of their team.

The usual diagnosis — "you need to delegate more" — is correct and completely useless, because delegation is not a character trait. It is a structure: defined levels of authority, written criteria, indicators that let you let go without losing visibility, and supervisors prepared to receive what gets released.

Without that structure, the bill arrives from several directions. The organization moves at the speed of one calendar, so growth mostly produces longer waits. Middle managers never build judgment because they never get to use it, and the best of them leave for places where they can. And there is a risk nobody has written down: if that one person falls ill or burns out, decisions are not made worse. They stop being made. Left alone, the pattern feeds itself: the less the team decides, the less ready it is to decide, and the more reasons the owner finds to hold on.

What it covers

The workshop treats delegation as a problem of organizational design rather than willpower. The choice of angle matters. Advice about trusting the team more or learning to let go leaves untouched the structure that caused the problem, and before long everything is running across the same desk again.

It starts from a real inventory of decisions — who makes them today, who should, and what is missing for that to happen — and builds an authority matrix by level: what each role decides on its own, what it decides and reports afterwards, what it consults on first, and what stays with leadership. Along the way it draws distinctions that rarely get said out loud. Delegating is not offloading: handing over a task without the authority or the criteria to resolve it moves the problem, not the decision. And follow-through is not micromanagement: follow-through watches a few indicators agreed in advance, while micromanagement checks every step because nobody agreed what to watch.

It also works the uncomfortable side: what the owner needs in order to trust, what evidence he needs to see, and what happens when somebody decides differently from how he would have decided. A business that only tolerates decisions matching the owner's has not delegated anything; it has added a step. That is why part of the session belongs to the people on the receiving end: what they need to know, where their limits sit, and who they turn to when a decision goes beyond their level.

The work in the room is done on each participant's own company. Everyone completes their inventory, tests it against the group to find the decisions held back out of habit, and puts the matrix under pressure with a concrete scenario: a supervisor makes a call within their level that the owner would have made differently. When owners and their teams attend together, they run that exercise with each other, which is where it earns its keep.

The close is an operational succession plan: what would break tomorrow if the key person did not show up, and what has to move so it stops breaking. Participants leave with each decision assigned to its rightful owner, an authority matrix by level, the handful of indicators that make letting go possible without flying blind, and a map of the places where continuity hangs on a single person. Deciding which of the current managers can take on the authority being released, and what they still lack, belongs to People, one of the engines of ALUD's consulting practice.

What participants learn

• Inventory the decisions that currently pass through a single person.
• Define levels of authority with written criteria and clear limits.
• Distinguish delegating from offloading, and micromanagement from follow-through.
• Choose the minimum indicators that allow letting go without losing visibility.
• Prepare the supervisors who will receive the delegated authority.

Agenda

1. 01Delegation as structure, not as a personal trait
2. 02Levels of authority and decision limits
3. 03Accountability without micromanagement
4. 04Organizational structure and bottlenecks
5. 05Developing supervisors who can receive authority
6. 06Minimum indicators for letting go with visibility
7. 07Operational succession and continuity

What the organization leaves with

• An inventory of decisions with their current owner and their correct owner.
• An authority matrix for the organization.
• The minimum set of indicators that sustains delegation.
• A continuity risk map by key person.