Watch the room next time, not the meeting.
Watch what happens in the two seconds after someone asks a hard question. Not the answer — the two seconds before it. Watch where the eyes go.
If you're the CEO, in a lot of rooms, the eyes go to you. Not because anyone was told to look at you. Because it's simply become the fastest, safest route to an answer.
That's not a leadership team failing to lead. That's a leadership team that has learned, through hundreds of small repetitions, that waiting works.
The thing that makes this hard to see
If your team were failing loudly, you'd know. Missed deadlines, obvious mistakes — those get noticed and named quickly.
Waiting doesn't look like failure. It looks like diligence. It looks like a VP being thoughtful, gathering input, "wanting to make sure we're aligned" before moving. It looks, on the surface, like exactly the behavior you'd want from someone senior.
The tell isn't in any single instance. It's in the pattern. Ask yourself: how many initiatives on your team's plate right now are actually stalled, waiting on you — not because they need your specific judgment, but because nobody wanted to be the one who moved without it?
Most CEOs, when they actually count, are surprised by the number.
What waiting looks like in practice
A leader who used to make a call now brings you three options instead of a recommendation.
A leader who used to push back in the room now goes quiet in the meeting and finds you afterward, privately, to say what they actually think.
A leader who used to own a full project end-to-end now owns the parts of it that are easy to defend, and quietly routes the ambiguous parts back to you — sometimes as a question, sometimes just by moving slowly enough that you eventually step in.
None of these people think of themselves as passive. Most of them think of themselves as careful, or respectful of your time, or simply doing things "the way that works here." That phrase is worth sitting with: the way that works here. Every team develops one. The question is whether anyone ever chose it on purpose.
Why this is easy to miss from the inside
If you're the CEO, waiting can feel like respect. People deferring to you can feel like the team functioning well — like alignment, like everyone rowing the same direction.
It's genuinely hard to tell the difference, in the moment, between a team that's aligned with you and a team that's simply outsourced its judgment to you. Both look calm. Both look cooperative. Only one of them can run without you in the room.
There's a rougher way to test it. Think about the last time someone on your leadership team disagreed with you — not diplomatically hedged, actually disagreed — and held that position after you pushed back once. If you're struggling to remember a recent example, that's not proof of a strong team. That's usually proof of a team that has learned disagreement doesn't survive contact with you, whether or not that was ever your intention.
Something to watch
The next three leadership meetings — the pause before someone answers a hard question, where the eyes go, how many decisions get framed as options-for-you rather than plans-already-made.
And one blunt question worth sitting with: if you took a two-week vacation with no phone, how many of the decisions on your team's desks right now would actually get made without you?
Whatever that number is, it isn't an indictment of your team. It's information about how the system currently runs — and next week, we'll look at exactly how a capable, well-intentioned CEO builds that system without ever meaning to.
This is the second in a series on why companies that are doing everything right can still become harder to run. Next week: the specific, almost invisible ways a good leader accidentally trains their team to wait.
.png){kind=small}