SOHEYL
GHAEMIAN

ENDGAME / Blog

Delegation Without Decision Rights Is Just a Busier Inbox

Delegation only changes work when authority, limits, and escalation paths are explicit; otherwise it adds another reporting layer.

· Soheyl Ghaemian · Deutsch

Curved concrete staircase in the Blavatnik Building at Tate Modern, London.
Adrian Boliston · Image source · CC BY 2.0 · Resized / verkleinert (1280 px).

Authority is the real unit of delegation

Delegation is often described as handing work to someone else, but that description hides the central question: who can actually decide? If the person receiving the task can only collect updates, ask for approval, and pass the issue back up, then the work has not really been delegated. It has been forwarded. The visible activity changes, but the decision rights remain where they were.

ENDGAME starts from the owner’s objective and then maps the route around it. That means delegation should be tested against the actual goal, the accepted trade-offs, the interests already in play, and the decision rights that cannot be silently overridden. A useful delegation statement is not just who does what. It is who decides what, under which limits, and what happens when the limits are reached.

A bounded delegation test

A practical test is to ask five questions before treating delegation as real. What decision is being moved? What limits remain with the owner? What dependencies still require coordination? What early signal would show the arrangement is failing? What is the alternative if the delegated route breaks down? These questions matter because authority without boundaries becomes vague, while boundaries without authority become theatre.

Consider a hypothetical example. An owner asks a manager to “own” customer communication, but every unusual message still needs sign-off, every priority change still needs permission, and every escalation returns immediately to the owner. In that case, the manager is not owning communication. The manager is preparing drafts for a higher layer of approval. The business now has one more reporting point, but not one more decision-maker.

Why the false version persists

The false version of delegation survives because it feels orderly. The owner still sees everything. The team still produces updates. The hierarchy appears intact. But a busy reporting rhythm can disguise a missing decision structure. People may work harder while becoming less responsible, because responsibility without judgment is only partial ownership.

This is where the downside test becomes useful. Any important move should ask what is gained, what control or flexibility is given up, what new commitments arise, and what adverse outcome is plausible. If the owner is unwilling to give up any real discretion, then the arrangement should be described honestly as oversight, not delegation. Clear language matters because a pretence of delegation can create confusion about accountability later.

Decision rights need an exit condition

A bounded delegation test is strongest when it includes an exit condition. Delegation should not depend on optimism that things will go well. It should include the signal that would change the decision. If the signal appears, the owner can tighten the boundary, revise the route, or bring the issue back into direct control. That is not failure. It is disciplined adjustment to evidence.

This also fits the ENDGAME method of separating internal and external factors around an explicit objective. Internally, the owner may have a strength in speed or judgment. Externally, the business may face a dependency on another person’s approval or another unit’s timing. Crossed together, these factors show whether delegation is genuinely executable or only attractive in theory. A route that depends on hidden permission is not a route. It is a hope.

What real delegation changes

Real delegation changes the structure of work. It reduces the need for constant translation at the top. It gives the person closer to the issue a defined space to act. It also makes the owner’s remaining role more precise: setting the objective, naming the limits, tracking the conditions, and intervening only when the agreed boundary is crossed.

That precision matters because the owner cannot silently override others’ rights while still claiming a clean division of responsibility. If the business wants delegated authority, it must accept that some decisions will move away from the center. If it is not willing to accept that, then the better label is supervision. Delegation without decision rights is not empowerment. It is another reporting layer with a nicer title.

GOAL → POSITION → MOVE → OUTCOME ↗