In this article
- Strategic delegation starts with your decision queue
- Separate the decision from the task around it
- Use reversibility and information as questions
- A hypothetical decision map
- Check willingness and workload
- Review the pattern, then adjust the boundary
- Protect time for the decisions only you can make
- Keep a decision record proportionate
Research discussed in Harvard Business Review notes that delegated decisions can feel burdensome. More authority is not automatically a better assignment.
The decision map below is a practical management tool, not a reproduction of that research or a validated scoring model.
Strategic delegation starts with your decision queue
List the decisions that repeatedly wait for you. Include small approvals, exception requests, prioritisation choices and recommendations that arrive already complete but still require your signature.
For each, ask why it remains with you. The answer may be a legitimate policy requirement, a risk you need to own, missing capability elsewhere or simply habit.
Record how often the decision occurs and who holds the most relevant information. You do not need precise time estimates to notice a queue of routine choices blocking work.
Do not assume every slow decision should be delegated. Sometimes the approval step itself is unnecessary and should be removed through the proper process.
Separate the decision from the task around it
A colleague can prepare a report without having authority to act on its findings. Another can choose a supplier within an approved framework without having authority to sign the contract.
Name the exact decision. “Handle purchasing” is broad. “Select among approved suppliers for orders below the agreed limit” is clearer.
Then distinguish three roles: who recommends, who decides and who must be consulted. One person may occupy more than one role, but the relationship should be explicit.
If two managers believe they hold the final decision, delegation will not resolve the conflict. Agree the authority before handing the work to an employee caught between them.
The University of Michigan's delegation checklist explicitly includes defining authority; use that distinction when naming the decision you intend to transfer.
Use reversibility and information as questions
Ask how difficult the decision would be to undo and how close the proposed owner is to the relevant information. These questions reveal where a small experiment may be appropriate.
A reversible internal scheduling choice is different from a binding customer commitment. A frontline supervisor may know the staffing constraint better than a distant manager, while the manager knows the wider contractual risk.
Avoid pretending these questions generate an objective score. They support judgement; they do not replace policy, expertise or legal requirements.
For a decision with substantial consequences, consider delegating the recommendation first. The employee can develop reasoning and exposure while the formal decision remains at the required level.
A hypothetical decision map
Imagine an operations manager approving every minor rota change, every supplier exception and every customer-service adjustment.
She identifies that routine rota changes within agreed staffing rules can be decided by supervisors. Supplier exceptions require consultation with procurement. Customer compensation outside the authorised range remains with the designated approver.
She publishes the boundaries and makes sure supervisors can access the relevant staffing information. She also clarifies that conflicting requests should return for a decision.
The manager has not simply moved a larger task list to the team. She has changed which decisions need her involvement.
This hypothetical illustrates allocation, not an estimate of time saved or proof that the same boundaries fit another organisation.
Check willingness and workload
Ask the employee how the authority fits their current responsibilities. A stretch opportunity may be welcome, but it can also add difficult decisions without removing any existing work.
Discuss what support they need and what will stop. Where the assignment changes the role materially, use the appropriate organisational process.
Explain how disagreement will be handled. If you routinely reverse decisions because you prefer another option, the authority exists only on paper.
Agree what would justify intervention: a boundary exceeded, material new information or an unacceptable risk. A different reasonable preference is not enough by itself.
Review the pattern, then adjust the boundary
After a suitable number of decisions, examine the quality of reasoning, the exceptions raised and the information that was missing. Do not judge only whether every outcome was favourable.
Ask whether the boundary was clear enough for ordinary decisions. If every case becomes an exception, the rule may be too narrow or the work more variable than expected.
You may expand authority, provide training or retain a particular class of decision. Explain the reason so that an adjustment does not feel like an unexplained withdrawal of trust.
Keep the review proportionate. A process designed to reduce bottlenecks should not create a new approval ritual for every routine choice.
Protect time for the decisions only you can make
Decide how you will use the capacity released. If it is immediately filled by low-value meetings, strategic delegation has not improved your attention.
Reserve time for the decisions that require your scope, relationships or accountability. Make the connection explicit: the team owns the routine choice; you own resolving the broader constraint.
For related guidance, see Peak Belt’s articles on decisions under pressure and team accountability, plus TrueNorth.
Keep a decision record proportionate
For consequential choices, record the option selected, the main assumption and the review trigger. This helps the next discussion examine the reasoning available at the time. Routine, low-risk decisions may need much less documentation. Avoid turning a useful record into a new permission system that recreates the bottleneck delegation was intended to remove.
Choose one recurring decision this week. Name the owner, permitted range and escalation trigger, then remove the unnecessary permission step only when those conditions are real.
AI-assisted researched guidance from PeakBelt. Hypothetical examples are labelled in the text. See our editorial approach.