The leader cannot be the bottleneck

If every significant decision comes back to the leader, a team may look well controlled, but it is not independent. People wait, the leader works longer hours, and the organisation slows down precisely when it should respond faster. Independence does not emerge from telling people to ‘get on with it’. It must be built through clear boundaries, feedback and consistently handing over responsibility.

A bottleneck often starts with good intentions

Leaders rarely become bottlenecks because they want to control everything. More often, they start by helping. They know the subject, find a solution faster and take responsibility when things get difficult. The problem begins when that help becomes the team's default way of working.

Every answer given too quickly teaches people that asking is the safest option. Every decision taken over by a manager removes an opportunity for someone to develop judgement. Eventually, the leader complains that the team lacks independence, while the team reasonably assumes the leader will decide anyway.

I have seen different models of command and management in the military and in business. In both, a leader's responsibility is similar: create conditions in which people can act even when the manager is not beside them. That takes trust, but trust alone is not enough. Work needs a clear structure.

Delegating a task is not the same as delegating a decision

You can hand over a task and still control every step. The employee follows instructions without developing ownership. Independence begins when someone understands the goal, knows the limits of their authority and can choose how to achieve the result.

Before delegating, I establish three things. First, the required outcome. Second, the non-negotiable constraints, such as safety, budget, timing or compliance with a standard. Third, which decisions the person can make alone and which require a discussion. Without this, both sides are working in the dark.

A leader may say ‘take responsibility’ while keeping every decision. That is a contradiction. We cannot expect ownership without genuine influence over how the work is done.

Not everyone needs the same degree of freedom

Independence is not handed over once, in equal measure to everyone. A newcomer needs more frequent checkpoints. An experienced specialist can have broader authority, but still needs to know when to escalate. I match freedom to the area of work, competence and risk, not just a job title.

Someone may manage daily operations independently while still needing consultation on a process change or an expense. That is not a lack of trust. It is deliberate risk management. The problem arises when rules are unspoken and change with the manager's mood.

Develop thinking instead of supplying the answer

When someone brings a problem, giving them a solution is easiest. It is quick, but expensive in the long run. More often I ask: how do you assess the situation, what options do you see, which do you recommend, and what risks have you considered? I support the person without taking away their thinking.

This does not mean turning every conversation into a series of questions. If safety or business continuity is at risk, or an immediate decision is needed, the leader should take control. Afterwards, return to the conversation and explain the reasoning. Otherwise, the team only learns to wait for the boss whenever things get difficult.

Feedback must address the decision, not just the result

A good decision can lead to a poor outcome, while a bad one may work out by chance. In a review, I therefore look beyond the result. I examine what information was available, what assumptions were made, what options were considered and whether the person responded to warning signs.

This builds judgement. If we assess only results, people soon learn to avoid risk, hide doubts or copy the manager's decisions. Discussing the thinking makes it easier to distinguish a learning mistake from disregard for a standard.

A leader should be available, but not always needed

A mature team is not one whose leader is absent. It is one whose daily work does not depend on the leader being present. People know the priorities, make decisions within their authority and escalate when agreed boundaries are crossed.

This does not make the leader less important. It frees time for work no one else can do: setting direction, developing people, removing barriers between functions and preparing for future challenges. The leader stops being a central approval desk and starts raising the quality of decisions across the team.

Five practical takeaways

Delegate the outcome and decision authority, not just a list of activities.

Agree what the person decides alone, what they consult on and what they escalate.

Before offering a solution, ask for an assessment, options and a recommendation.

Match freedom to competence, the area of work and the consequences of an error.

Review the quality of the thinking, not just the final result.

Tool: an autonomy agreement

Choose one recurring area where decisions regularly come back to you. Complete these fields with the person who will take greater responsibility. Keep the agreement to one page and review it after the first few decisions.

At the agreed review, do not ask only whether everything was completed. Find out which decisions the person now makes confidently, where support is still needed and whether their authority can safely expand.

Independence reflects the way we manage

You cannot build an independent team while keeping every decision with the leader. You need to hand over influence deliberately, accept reasonable differences in approach and keep reviewing decision quality. It takes patience, but reduces dependence on one person.

If your team waits too often for approval, or leaders are overloaded with everyday decisions, at Mentavia we can translate that problem into practical rules for delegation, escalation and growing ownership. We work on real situations, without adding more slogans to the corporate vocabulary.