An organisation can have capable people, clear roles and sophisticated processes, but still find important decisions returning to the same desk.
The usual explanation is that the team needs more experience, stronger managers or tighter oversight. Sometimes it does. But delegation can fail even when the person receiving it is fully capable.
The problem may be that responsibility has travelled further through the organisation than the reasoning required to exercise it.
A founder or senior executive hands over a decision with an objective, deadline, and expected outcome. The work comes back technically sound, but somehow misses the point. The leader corrects it and becomes more involved the next time. The team senses that autonomy is conditional; the leader becomes less comfortable letting go.
And with time, delegation becomes formal rather than real.
What leaders carry in their heads
Important decisions rarely depend on an instruction alone. They carry a body of reasoning around them: which trade-off matters most, which risks are tolerable, where flexibility exists, what cannot be compromised, when “good enough” is sufficient and when it is not.
Founders carry this knowledge almost unconsciously.
They remember the negotiation that shaped a commercial position, the regulatory issue that changed how the business approaches a risk, the customer relationship that requires care, or the compromise that was acceptable once but should never become precedent.
Those experiences become judgment.
The task, however, can be transferred without the reasoning behind it. The person receiving the decision then has to fill in the gaps.
That is where interpretation becomes important.
An instruction can be clear enough to execute and still leave considerable room for interpretation. “Close this issue this week” establishes an outcome and timeframe, but says little about how to weigh speed against regulatory risk, commercial flexibility against precedent, or immediate resolution against a longer-term relationship.
The person acting on the instruction may make a defensible decision. It may simply differ from the one the leader had in mind.
The delegation loop
A familiar cycle can follow. A leader delegates a task. The result comes back technically correct but directionally different from what was expected. The leader intervenes. The team learns that delegated authority still comes with close correction, while the leader becomes less confident about handing over the next decision.
More supervision, approvals, or senior involvement follow.
If the underlying issue was an untransferred decision logic rather than capability, the pattern survives. A new hire may face the same ambiguity. Another approval layer may add control without adding judgment.
Delegation is therefore usually treated as the transfer of work, when the more consequential transfer is judgment.
The objective is not to explain every decision in exhaustive detail. It is to give people enough understanding of the reasoning behind important decisions to exercise discretion when the next situation is unfamiliar.
What needs to travel with authority
People need to understand the context in which a decision sits, the trade-offs that matter, the outcomes that are non-negotiable and the boundaries within which they can act. They also need to know what warrants escalation and what should be resolved without returning upwards.
Without that clarity, people can respond in opposite ways. One escalates decisions that should have been made independently; another exercises discretion beyond what the leader intended.
Neither behaviour necessarily demonstrates a lack of capability. Both can result from uncertainty about how the decision will be judged.
This is why adding approval stages does not necessarily solve the problem. Governance can establish who has authority. It cannot supply the judgment required to use that authority well.
The energy sector exposes the problem quickly
The distinction becomes particularly important in businesses where decisions extend across long project cycles and multiple institutional interfaces.
An energy project rarely remains confined to the function in which a decision originated. Commercial assumptions can affect financing. Technical choices can create regulatory implications. Contractual decisions can shape future claims or stakeholder relationships. A project team may implement a decision months after it was taken, under materially different circumstances.
The person who made the original decision cannot remain present throughout that chain.
What needs to survive is the intent and reasoning that gave the decision its direction.
This is also why experienced leaders can become reluctant to delegate. They understand how many consequences can sit behind an apparently ordinary decision. Retaining every consequential decision, however, leaves the organisation dependent on access to the person carrying that context.
The more sustainable approach is to make that context usable by others.
Communication determines whether intent travels
Communication therefore has a more consequential role than transmitting instructions.
Leaders who delegate effectively tend to make the reasoning around a decision visible before handing over the responsibility. They explain why the work matters, what pressures are shaping the decision and which trade-offs genuinely matter. They make their standards clearer too: what a good outcome looks like, which risks can be accepted and which outcomes cannot be compromised.
Just as important are the boundaries. People need to know where they have discretion, when a decision should come back to the leader and where speed matters more than achieving a perfect outcome. These boundaries give authority practical meaning.
The final piece is often overlooked. Delegated work is usually reviewed through the outcome: Was it right? Was it delivered? A stronger conversation also examines the interpretation behind it. What did the person believe mattered most? Which trade-off did they consider decisive? Why did they act independently? What made them escalate one issue and resolve another?
That conversation does two things at once. It helps the team understand the reasoning behind the decision, while showing the leader where assumptions have remained implicit. This allows experience that once existed primarily in one person’s head to become available to others. Organisational memory begins to form.
This is the deeper function of communication in delegation. It carries enough context, reasoning, and boundaries for someone else to exercise judgment when the next situation does not resemble the last one.
Delegation then moves beyond transferring a task. It begins to transfer the judgment required to carry responsibility well.
The real test of delegation
When a delegated decision goes wrong, a more useful question may be:
What did they reasonably believe I was asking them to do?
The answer may reveal a capability gap, poor judgment or an interpretation gap created by the way the decision was communicated. Each requires a different response.
For founders, the knowledge being transferred is often knowledge they have never consciously articulated. They know where the organisation should compromise, what it should protect, how much risk it should accept and when an attractive opportunity is inconsistent with the business they are building.
The leadership task is therefore not simply to become better at letting go. It is to make enough of that reasoning visible for others to use it without the founder being present. This is what allows intent to travel.
The real measure of delegation is not how much work a leader has handed over. It is how little interpretation has to be reclaimed afterwards.
When people can make decisions consistent with the organisation’s priorities and standards, even when circumstances change, delegation has become more than task transfer. Personal judgment has acquired an organisational form, and communication is one of the means through which that transformation takes place.
When a delegated decision goes wrong, do you first examine the person’s judgment or the context they were given to make the decision?
_________________________
Want more insights like this?
Click here to join our WhatsApp Channel for strategic communications insights, leadership perspectives, industry observations, in-depth analysis, and practical communications tips.
_________________________
Also read: Does Flexible Operation Damage Thermal Plants?
When Does a Stakeholder Argument Influence Regulation?
When Priorities Collide, What Should Win?
Do Lawyers Realise They Communicate Even When They Aren’t Speaking?