Break the advice-dependency loop

When people come to you for every decision, it signals advice-giving is making them less capable, not more.

Why it works

Over-advising creates dependency through a learned helplessness mechanism: when people consistently receive answers from above rather than developing their own, they stop investing in their own problem-solving capacity and start routing problems upward as a default. The manager who always has the answer trains their team to bring them every problem. Breaking the loop requires the manager to refuse to solve problems that the other person is capable of solving — which feels unhelpful but is the most helpful move.

How to do it

1. When someone brings a decision that is within their authority, reflect it back: "What would you decide if I weren’t available to ask?"
2. Distinguish genuinely escalated decisions from questions people ask out of habit or safety-seeking.
3. Make explicit that you are not available as a decision router: "My job is to help you develop your judgment, not to be your judgment."
4. Track how often the same type of question comes to you — recurrence signals a training opportunity, not a decision to make.

Evidence

Self-efficacy theory (Bandura) establishes that confidence in one’s capabilities is built through mastery experiences — successful independent performance. Over-advising denies those experiences. Learned helplessness research (Seligman) describes the opposite effect. (mechanistic)

Self-efficacy and learned helplessness are well-studied constructs; the application to advice-dependency in management is a mechanistic inference rather than a separately studied phenomenon.

Sources

• Bandura (1977), Self-efficacy: toward a unifying theory of behavioral change, Psychological Review

Common mistake

Recognizing advice-dependency in your team and then solving it by withdrawing support abruptly — the transition needs to be gradual and made explicit, or people experience the change as abandonment rather than development.