A team with no initiative isn't a people problem. It's a conditions problem. And the conditions are usually closer than the leader thinks.
"They're senior. They're smart. But they show no initiative. They wait for me to tell them what to do."
A familiar complaint. What happens in their team meetings is just as familiar.
It looks productive. Things are moving. The leader is across everything - opening every agenda item, summarising, delegating. Statements, not questions.
A team member offers a half-formed idea in the moment. Why hasn't this been properly researched and costed? The idea gets parked.
Opinions are invited on a proposal. Two people offer a view. The leader nods, then proceeds with the original plan.
One of last week's decisions has been revised. The leader informs the team. No discussion invited.
The team is paying attention - they always are. And what they're learning - week by week - is what initiative costs here.
Somewhere in the middle of this, two team members catch each other's eyes.
Is this a team with no initiative - or a team that has learned it isn't worth it?
The leader isn't doing anything wrong. That's the problem.
Look at each moment in isolation and it's hard to argue with. A half-formed idea that hasn't been thought through probably shouldn't be actioned. A proposal the leader has already considered deserves a decision, not an endless discussion. A revised decision needs to be communicated. These aren't failures of leadership. They're what leadership looks like from the inside.
There's something else operating too. A coach once described it to me as the compulsion to add value in every situation - to have the answer, move things forward, demonstrate command of the brief. For many leaders, this isn't arrogance. It's anxiety. The belief that if they slow down, hold back, or let silence sit, they'll be seen as underprepared. Weak. Not across it.
So they fill the space. Every time.
The leader who never creates a vacuum is the leader whose team never learns to fill one.
The team, meanwhile, is doing something entirely rational. They're reading the conditions and adapting to them. Bring an unfinished idea and it gets parked. Offer a view and the original plan proceeds anyway. Make a decision and it gets quietly revised. The feedback loop is consistent and clear, even if nobody designed it that way.
This is what makes it hard to see from the inside. Nobody is behaving badly. The leader is leading. The team is responding to what the leader's behaviour actually rewards - not what the leader says they want. The complaint and the cause are sitting in the same room, in the same meeting, every week. They just aren't visible to each other.
A common pushback
"But my team expects this. If I start acting like I don't have the answers, I'll lose credibility."
It's a reasonable fear. And it points to a real tension - not a character flaw. Leaders who operate in complex, high-pressure environments often got there by being the person who knew what to do. The identity and the role got built together. Stepping back doesn't just feel uncomfortable. It can feel like a betrayal of what made them effective in the first place.
But the credibility argument contains a hidden assumption: that the team needs the leader to have the answers. In most senior teams, that stopped being true some time ago. The team has the capability. What they're missing is the signal that it's wanted.
There's also a harder version of this question worth sitting with. When a leader says "my team expects me to direct them" - are they describing the team's genuine expectation, or the pattern the team has learned to work within? These are not the same thing. One is a starting condition. The other is a consequence.
What actually shifts this
The change isn't a personality overhaul. It's a series of small, deliberate adjustments to the conditions - most of them in the meeting itself.
The most immediate is the question before the statement. Not asking for input after the leader has already signalled their view, but genuinely opening an agenda item without a position already visible. This is harder than it sounds. The impulse to frame, to set context, to show you've thought about it - all of that works against the gap that creates space for others to think.
The second is letting an idea be half-formed. Not every contribution needs to arrive fully costed and ready to action. Some of the most useful thinking in a team happens when someone puts something incomplete on the table and the group builds on it. The question "what would need to be true for this to work?" does more for a team's initiative than any amount of encouragement to speak up.
The third - and the most consequential - is what happens to decisions. If a decision the team made gets revised unilaterally, that's information about where authority actually sits. It doesn't matter what the org chart says. Teams locate power accurately, every time, and adjust their behaviour accordingly. If the leader wants the team to own decisions, the decisions need to stay owned.
None of this is about abdicating leadership. The best leaders in senior teams aren't the ones who know the most or speak the most. They're the ones who create the conditions for the best thinking to surface - and then know what to do with it. That's a different skill. And for many leaders, it's one nobody ever explicitly asked them to develop.
The team isn't waiting because they lack initiative. They're waiting because they've learned what happens when they don't. Change the conditions and you change what gets learned.
