Week 30 Day 4: Building People Up Without Creating Dependency

Coaching that creates dependency is not coaching -- it is control dressed up as support. The test is simple: if you were unavailable for a month, would the people you have been developing continue to improve, or would they stall? If they would stall, you have created dependency, not capability.

Here are the three traps that create dependency instead of independence. Trap one: the open door that never closes. You tell the team 'my door is always open.' They take you literally. Every question, every decision, every uncertainty comes to you. You feel valued and needed. The team feels supported. But they are not developing their own judgment because they never have to -- you are always available to provide yours. The fix: create graduated availability. For the first month of a new person's tenure, your door is wide open. Month two, you start redirecting: 'What do you think you should do?' Month three, you set boundaries: 'Try your approach first, and if you get stuck, come find me.' Month six, you are the escalation path, not the first resort. Trap two: the feedback loop that only loops through you. You review every deliverable, provide detailed feedback, and the work improves. But the improvement is dependent on your review. Without your feedback, the work quality drops. The fix: transfer the review standard. Instead of just providing feedback, explain the criteria you use to evaluate the work. Eventually, the person can self-review against your criteria. Then pair them with a peer reviewer. Your direct feedback becomes the exception, not the norm. Trap three: the emotional support that replaces resilience. You are empathetic and supportive when people struggle. They feel safe coming to you with their frustrations. But if the support becomes a coping mechanism rather than a development tool, you are helping them feel better without helping them get stronger. The fix: combine empathy with challenge. 'I hear that this is frustrating. What would you do differently next time?' Validate the feeling, then redirect to learning.

The dependency-versus-independence framework maps to what Kegan and Lahey (2009) call the 'immunity to change' phenomenon -- the unconscious dynamics that prevent leaders from releasing control even when they intellectually support independence. Their research found that leaders who created dependency often had a hidden competing commitment: the desire to be needed conflicting with the goal of developing independence. This conflict produces what Argyris (1991) calls a 'defensive routine' -- a pattern of behavior that protects the leader's self-image (as essential and valuable) at the cost of organizational effectiveness. The graduated availability model is supported by research on 'scaffolding' (Wood, Bruner, and Ross, 1976), which originated in educational psychology and describes the process of providing temporary support that is systematically removed as the learner develops competence. Their research found that effective scaffolding follows a predictable trajectory: initial high support, intermediate fading (gradually removing support as competence increases), and eventual withdrawal (the learner operates independently). The emotional support trap connects to research by Neff (2003) on 'self-compassion,' which distinguishes between 'self-kindness' (acknowledging difficulty, which supports resilience) and 'over-identification' (dwelling in the difficulty, which undermines resilience). Leaders who combine empathy with challenge promote self-kindness in their teams, while leaders who provide empathy without challenge promote over-identification -- a pattern that feels supportive but produces learned helplessness over time (Seligman, 1975).