When Capable Teams Don't Step Up
The dependency you didn't mean to create
During a recent session, a CMO shared her frustration, with barely concealed exhaustion. “I have brilliant people on my team. Seriously capable. But I still feel like the person everything lands with.”
She’d just come from back-to-back meetings where three different leaders had brought her issues - issues and decisions that in her mind, they should have resolved themselves. Not because the problems were particularly complex. Not because they lacked the capability. But because, as one of them lightly put it, “I wanted to make sure you were on board.”
“I trust them to sort it,” she said. “I’ve told them that. But they still bring it all to me.”
This pattern shows up repeatedly with the leaders I work with. Capable teams who keep escalating. Experienced managers who won’t commit without sign-off. Leaders who say they want their people to step up, but can’t work out why they don’t.
What’s particularly interesting is how rarely these leaders recognise their own role in creating the dynamic they’re now trapped in.
Because dependency doesn’t emerge from nowhere. It gets built, decision by decision, interaction by interaction. And often, the person building it is the one most frustrated by it.
The challenge is that most leaders don’t see themselves as creating dependency. They see themselves as maintaining standards. Staying on top of things. Being available. Making sure nothing falls through the cracks.
But those same behaviours - the quick response, the detailed follow-up, the willingness to jump in - can inadvertently signal that escalation is expected. That the leader wants to stay close to decisions. That taking something to the boss is the smart, safe move.
Your team learns what you reward. Not what you say you want, but what actually gets reinforced through your actions. And if checking in with you before committing means avoiding potential criticism later, they’ll check in. Every time.
The irony is that this dynamic tends to intensify precisely when leaders are most overstretched. When you’re already carrying too much, the temptation to give a quick answer rather than push back can feel like the faster option. But that quick answer becomes tomorrow’s precedent for escalation.
What makes this particularly difficult is that the behaviours creating dependency often come from good instincts. You care about quality. You want to support your team. You’re trying to move things forward efficiently. The problem isn’t the intent - it’s the unintended consequence.
Breaking this pattern requires something uncomfortable: recognising that your team’s reluctance to step up might not just be about them. It might be about the environment you’ve created, perhaps without realising it.
Because if your team won’t make decisions without you, the question isn’t just “why won’t they step up?” It’s “what am I doing that makes escalation feel like the right move?”
Notice: The patterns you’re most frustrated by in your team often have roots in your own behaviour, even if that’s not immediately obvious.
When someone escalates to you, what do you typically do?
What could be the unintended consequences?
Where might there be a gap between what you say you want and what your behaviour actually reinforces?
Examine: Dependency gets built through repeated interactions that signal what’s safe, what’s risky, and what the leader actually wants - regardless of what they say.
How does your team experience the difference between decisions you agree with and decisions you don’t?
What might change if you responded to escalation with questions rather than answers?
How might your team describe the authority they feel they can actually use versus the authority you think you’ve given them?
Shift: Breaking dependency patterns requires consistency over time - your team will test whether you genuinely mean it, or whether escalating remains the safer choice.
How might you respond when your team makes a decision that makes you uncomfortable but isn’t actually problematic?
What would tell you that you’re slipping back into giving answers when you should be asking questions?
Who on your team already demonstrates genuine ownership - and what specifically do you do that reinforces that?
If you’ve found this week’s issue thought provoking please hit the ❤️ button at the top of this email so that more leaders can find it.
Meantime if you haven’t already, you can subscribe to receive the next issue straight to your inbox.
