##How does the dependency develop?
Managers can create this pattern without intending to. They redo a task instead of explaining their feedback, ask to review every detail, or reject an employee’s decision without explaining why.
The team gradually learns that asking the manager is the safest choice. Initiative declines, waiting becomes routine, and the manager feels an even greater need to step in because the team rarely acts independently.
Breaking this cycle starts with understanding why people hesitate. Do they know what outcome is expected? Do they have the information they need? Are the limits of their authority clear? Repeated questions may point to an unclear process rather than a lack of ability.
Delegate the outcome and the decision boundaries
“Take care of this” may sound clear to the person giving the instruction, but it can mean several things to the person receiving it. Effective delegation explains four points: the expected outcome, the deadline, the decisions the employee can make, and when they should come back to you.
Consider an employee who handles customer inquiries. They may be able to answer common questions using approved information, arrange a follow-up, and update the request’s status. Changing a price or the scope of a service, however, may require approval. Clear boundaries help the employee respond faster while keeping responsibility visible.
Review the decisions that reach your desk
For one week, note which requests stop while waiting for your decision. You will probably find that some appear repeatedly. For each type of request, ask: Does this truly need my approval every time? What information or guidelines would allow someone else to handle it?
It can help to place decisions in three groups:
Decisions an employee can make and carry out within agreed limits.
Decisions an employee can make and then report to the manager.
Decisions that require approval before action.
This gives the team practical clarity and leaves the manager more time for decisions with a greater impact.
Make your knowledge available to the team
If you keep answering the same question, the team may need a reference they can use on their own. It could be a checklist, a standard template, or a short page explaining the steps and what a good result looks like.
A useful process does not have to be long. For some tasks, a few examples are enough: How should we answer a common inquiry? When should a request be escalated? What should we check before submitting the work?
Once that knowledge is available, interruptions decrease, work becomes more consistent, and new employees can understand what is expected of them.
Use reviews to help people learn
An employee may approach a task differently from you. If they achieve the agreed outcome within the agreed boundaries, a different method does not automatically mean the work needs to be redone.
When a mistake happens, look at its cause before taking back the responsibility. Were the instructions clear? Was the necessary information available? Would additional training help? These questions lead to a more useful response and show the team how to improve next time.
Start with one decision
You do not need to change how the whole team works at once. Choose one recurring decision that reaches you and write down a simple rule: who can make it, what the limits are, and when it should be escalated. Try the rule for a short period, then review its effect on speed and quality.
Over time, you will see where the team needs more authority, training, or clearer procedures. The manager’s role can then shift from overseeing every detail to building a team that knows how to work, when to ask for support, and how to maintain quality.
One sign of good management is that work continues to a high standard when the manager is busy, because responsibilities are clear and decisions are made by the people equipped to make them.
I write about business, management, law, technology, and what I learn while building ventures.
Was this article useful?