There is a version of being a helpful manager that gradually makes your team less capable: answering every question, solving every problem, making every call. It feels like support, but what it actually builds is dependency — a team that waits for direction rather than seeking solutions, and a manager who is too busy responding to everyone else's problems to do their own work. The distinction between giving useful direction and creating unhealthy dependency is one of the most practically important things new managers need to get right.
1 Answer questions with questions — sometimes
When a team member brings you a problem, the fastest path to a solution is often also the worst long-term choice: you tell them what to do, it gets done, everyone moves on. But over time, this pattern teaches people that bringing you problems is more efficient than thinking them through themselves. The queue outside your door grows, and their problem-solving capability atrophies.
The alternative is to respond to questions with a question of your own before providing an answer: "What options have you already considered?" or "What would you do if I weren't available?" This does not mean withholding guidance — there are situations where direct, efficient direction is exactly what is needed. It means distinguishing between problems that genuinely require your input and problems the person could work through themselves with a small amount of support.
A useful filter: before answering a question, ask yourself whether the person has the information and capability to reach a reasonable conclusion on their own. If yes, ask what they think the answer is before you offer yours. You will often find they already know — they just needed permission to act on it. If no, provide the guidance they need directly. Treating every question as an opportunity for coaching is as unhelpful as treating none of them that way.
2 Distinguish between directive and coaching conversations
Not all conversations with your team require the same approach. Some situations genuinely call for clear, direct instruction — a time-sensitive decision, significant risk of the wrong choice, onboarding a new team member to an unfamiliar process. Others call for a coaching approach that builds capability rather than just solving the immediate problem. Confusing the two creates friction and wastes the opportunity the conversation presents.
The practical difference: directive conversations are efficient and clear — here is what needs to happen and why. Coaching conversations are exploratory — what is your read of the situation, what have you tried, what do you think the options are? Neither is better. Each has its place, and recognising which one a given moment calls for is a skill worth developing deliberately.
At the start of a conversation where someone brings you a problem, take a moment to categorise it: does this require my judgement and instruction, or does my job here is to help this person develop their own thinking? Let that assessment shape how you engage. If you find yourself always defaulting to one mode, that is a signal worth paying attention to — both excessive directiveness and excessive coaching create problems for the people on the receiving end.
Building a team that thinks and acts independently is covered in depth in the LeadWise Emerging Leaders Program — with frameworks for delegation, coaching conversations and the kind of direction-setting that actually develops people.
Explore the program — €2993 Delegate decision-making authority, not just tasks
A common mistake in delegation is handing someone a task while keeping all the decision-making authority. The person is doing the work but checking in for approval at every step — which means they are not really autonomous, and you are not really delegating. Genuine delegation means being explicit about what decisions the person can make on their own, and which require your input. When people know the boundaries of their authority, they can operate confidently within them rather than defaulting to asking you before every choice.
This requires some thought about risk tolerance. Low-stakes, reversible decisions can almost always be delegated with full autonomy. Higher-stakes ones may warrant a check-in before action. Being explicit about this distinction — rather than leaving people to guess where the line is — removes a significant source of unnecessary dependency and enables people to move faster with more confidence.
When delegating a piece of work, explicitly state which decisions the person can make without consulting you and which ones they should run by you first. Something like: 'You have full authority to decide X and Y — just keep me in the loop. For Z, come to me before you commit.' This two-minute conversation at the outset eliminates a pattern of unnecessary check-ins and gives the person a clear operating mandate.
4 Build team norms for peer problem-solving
Dependency on the manager is sometimes less about the manager's behaviour and more about team structure: people have been trained, explicitly or implicitly, to route all questions through the manager rather than drawing on the knowledge of colleagues. Breaking this pattern means actively building the norm that team members can and should help each other — and visibly supporting that norm rather than always being the first point of contact.
This might mean redirecting questions: "Have you talked to Jamie about this? She dealt with something similar last quarter." It might mean creating space in team meetings for shared problem-solving rather than bilateral conversations with you. A team that can collectively problem-solve is more resilient and less dependent than one that waits for the manager's input on every significant question.
The next time someone brings you a question that another team member could answer as well as you, redirect them explicitly: tell them who to ask and why. Then follow up briefly to check that the question got answered. This models the peer-resource norm without abandoning the person, and over time it reshapes the assumption that the manager is the only useful source of guidance.
5 Make your reasoning visible, not just your conclusions
When managers only share what to do and not why, they create two problems: decisions feel arbitrary, and team members never develop the judgement to make similar calls themselves. The most effective direction is not just instructive — it is educational. When you explain the reasoning behind a decision — what you considered, what you weighed and why you concluded as you did — you are building the team's capacity to think similarly the next time a comparable situation arises.
This is especially valuable for the judgement calls that are genuinely hard: where reasonable people might disagree, where context matters significantly, where the answer depends on priorities that are not obvious from the outside. Making your thinking visible on these calls builds trust in your decisions and develops your team's ability to make better ones themselves.
Get into the habit of briefly narrating your reasoning when you make a call that affects the team: 'I went with option A rather than B because [reasoning]. The key factor for me was [X].' This takes an extra thirty seconds and does three things: it builds understanding, it gives the team a framework for similar decisions, and it models the kind of structured thinking you want to see from them. Over time, they start narrating their reasoning to you in the same way.
The bottom line
The dependency trap is insidious because the behaviours that create it — answering questions, solving problems, staying closely involved — look like good management from the outside and often feel like it from the inside. The signal that something has gone wrong is usually the manager's own experience: too busy, too reactive, too much time spent on other people's problems rather than the work they should be doing themselves.
Building genuine independence in a team requires deliberate choices about when to direct, when to coach, how much authority to delegate and how to encourage peer resources rather than defaulting to yourself. None of it is complicated, but it requires ongoing intentionality — especially from managers who are naturally capable problem-solvers and find it easier to answer than to step back.