A newly promoted manager is asked to settle a question that a capable specialist could probably answer. The manager knows the work well and gives a quick response. The next day, a similar question arrives. Soon, colleagues wait for the manager's view before taking steps they used to judge for themselves. Being available feels supportive, but the team's decisions now move at the pace of one person's attention.
This can happen when the manager was previously the strongest specialist. Direct problem-solving earned trust and may still be needed in some cases. The role now also requires you to make other people's judgement usable. That means deciding which questions must stay with you, which can be settled by colleagues, and what they need to act responsibly. The aim is not to push decisions away. It is to prevent your expertise from becoming the only route through which the team can work.
Find the decisions that keep returning
Look at the questions that repeatedly come back to you. Are colleagues asking for a decision because only you hold the authority? Do they lack a piece of information, a clear priority or confidence about how much discretion they have? Or have you created a habit of answering so quickly that they have little reason to practise their own judgement? The same visible pattern can have different causes, so “delegate more” is too blunt a diagnosis.
Notice what happens while a question waits. A routine choice may pause work that could have continued. A specialist may send a complete recommendation but receive no response because the manager is occupied elsewhere. Other colleagues may then treat the lack of an answer as uncertainty about the whole task. The bottleneck is more than a crowded inbox. It is a decision route that makes one person's availability a condition for progress.
Some returns are appropriate. A question with material consequences, a formal approval requirement or a conflict between teams may genuinely need the manager or another authorised person. Others point to an unclear boundary. If a team member can gather the evidence and make a sound choice within a defined range, requiring your approval for every instance adds little protection. Sorting these cases by the decision involved, rather than by how uncomfortable they feel, is the first step.
The pattern may also reveal a capability gap. A colleague who has not handled a type of issue before may need explanation, practice or close review. That need is real, but it does not automatically mean the manager must make the decision forever. Give the person a bounded opportunity to develop, with support matched to the stakes of the work.
Set the boundary before handing over a decision
A useful delegation begins with the purpose of the decision. What outcome is the person trying to protect or achieve? Which evidence should inform the choice? What can they decide without returning to you, and what must be referred to a specified decision holder? If those points remain implicit, the colleague may either send everything back or act beyond their remit.
Make the scope concrete. A team member might decide the order of ordinary fact-finding within an agreed investigation, but not approve a formal conclusion or commit another function's resources. A supervisor might adjust a routine allocation within an agreed limit, but need support when the change affects a protected control or a wider priority. These examples illustrate the distinction; actual roles and site procedures determine the real boundary.
Include the support the person can use. They may need access to previous cases, a colleague with relevant knowledge or a point at which to discuss uncertainty. A boundary is not an instruction to work alone. It gives room to exercise judgement while making help available before a small uncertainty becomes a larger problem.
Agree how the result will be reviewed. For an unfamiliar or consequential decision, you may want to discuss the reasoning before action. For a familiar decision within established limits, a later review may be enough. Match the review point to the risk and the person's experience. If every delegated decision still requires your informal sign-off, you have changed the language of ownership without changing the decision flow.
Let people decide within the boundary
Imagine a new Quality Manager who previously led most difficult investigations personally. A specialist on the team is ready to choose the order of a bounded fact-finding sequence. The manager explains what question the work must answer, which evidence should be gathered, when to ask for help and which conclusions or approvals remain with the authorised roles. The specialist then chooses the sequence and explains why it is suitable. This is a constructed illustration, not a rule for a real site.
If the evidence develops as expected, the specialist can complete the agreed part of the work and bring back a reasoned account. The manager can review the reasoning and help them see what worked, without quietly redesigning every step after the fact. The specialist has made a real choice within the boundary. Next time, the manager may be able to give similar work with less close support.
A second case might reveal a material uncertainty or a dependency on another function that was not anticipated. Here the specialist should pause at the agreed point and explain what changed. Escalation is not evidence that delegation failed. It shows that the boundary was understood and that a different decision or authority is now needed. The manager may need to decide, seek another role's approval or arrange a wider discussion, depending on the actual responsibility.
What matters is that the manager resists taking over merely because they could solve the problem faster. It may be quicker to give the answer in one instance, but repeating that choice keeps the team's capability narrow. A short discussion of the evidence, possible options and limit of authority can let the specialist make the next appropriate decision. The manager still intervenes where the risk or formal responsibility requires it.
Keep escalation useful
People need to know what should bring a decision back. Useful triggers are tied to the work: evidence that contradicts the expected picture, a consequence beyond the agreed scope, a decision that affects another team's capacity, or a formal authorisation that the person does not hold. “Come to me if it feels difficult” may be well meant, but it gives little guidance to someone learning where the real boundary lies.
The return should also arrive with enough context to support action. Ask for the question, the evidence, the options considered, the consequence of waiting and the authority needed. This is not a demand for an elaborate report before help is available. It helps distinguish a request for coaching from a request for an authorised decision. You can then respond at the right level instead of beginning the entire analysis again.
Escalation can expose a weakness in the original delegation. Perhaps the scope was unclear, the necessary information was unavailable or the team member was expected to influence a resource they did not control. Address that condition rather than simply telling them to be more confident. Where the decision truly belongs with you, make it and explain the reasoning that can help colleagues handle related questions later.
Some decisions belong to another function or a more senior role. Do not use delegation to bypass that route. Your job may be to help the team prepare a sound recommendation and reach the right decision holder in time. The fact that you are accountable for the team's work does not grant you every approval or allow you to pass a reserved decision to someone else informally.
Review the result without taking the work back
After a delegated decision, examine the quality of the reasoning and the result separately. A sound choice can have an unwelcome outcome because conditions changed; a fortunate outcome can hide weak reasoning. Discuss what the person knew, what they noticed, how they used the agreed boundary and what they would check differently next time. This gives feedback the person can apply beyond a single case.
Correct mistakes clearly. If an important step was missed, make the necessary work safe through the applicable route, then understand whether the cause was insufficient skill, missing information, an unclear limit or a poor decision. Different causes need different responses. A manager who simply takes all similar decisions back may restore short-term control but lose the opportunity to improve the team's judgement.
As evidence of capability grows, the boundary can change. A person may handle a wider range of routine choices, bring stronger recommendations on complex ones or need less frequent review. Equally, a new risk or changed responsibility may require closer oversight for a time. The aim is a deliberate match between discretion, capability, support and consequence, rather than a permanent label that someone is either trusted or not trusted.
Your own performance in a management role becomes visible in this pattern. A team that can make sound decisions within clear limits has more room to work, and you have more attention for the decisions only you can make. Expertise remains valuable, but its use changes. You apply it to set boundaries, develop judgement, recognise when escalation is needed and decide where your authority really matters. That is how a manager stops being the answer to every difficult question without leaving the team on its own.
