A VP I worked with stepped into a COO role after 18 years of being the person with answers. Week one, someone on his team brought him a supply chain problem. He solved it in about twelve minutes. The person thanked him and walked out. He felt useful. Over the following months that pattern kept repeating: problems arriving, him resolving them quickly, everyone leaving satisfied.

About eight months in, he noticed something. His calendar was full. His team looked busy. The organization was hitting its numbers. But the problems being brought to him had gotten simpler. The hard, unresolved, genuinely ambiguous ones had stopped appearing on his calendar. At first he assumed things were going well. Then he started paying closer attention to what his directs were discussing in meetings he wasn't in.

He hadn't gotten worse at his job. His team had gotten better at filtering what they brought him. Without being told, without a memo, without any explicit instruction, they had learned which problems he would receive openly and which he would redirect with a quick answer. So they curated accordingly.

What the Research Actually Shows

HBR published research in April identifying this pattern with some precision. The behaviors that build executive presence early in a career are the same behaviors that degrade decision quality at senior levels. Having the answer, projecting confidence, adding value to whatever idea a team member brings: these are the habits that earned respect on the way up, and they are also what closes the room at the top. The mechanism is straightforward, even if the implications are uncomfortable.

When a leader takes a team member's idea and improves it, even slightly and helpfully, the member's ownership of that idea drops by roughly half. Marshall Goldsmith documented this in his research on leadership habits. The executive thinks they made the idea better. Technically they did. But the person who brought the idea no longer fights for it the way they would have if they'd built it themselves. And at senior levels, execution depends almost entirely on whether the people doing the work actually believe in what they're doing.

The smoothest meeting you'll ever run is also the most dangerous one. Smooth means the room has learned what not to bring you.

The Closed Loop You Don't See Forming

The problem compounds over time in a specific way. Teams do not stop bringing problems altogether. They keep bringing them. What changes is the category. The problems that surface are the ones the team has already partially solved, the ones with a clear ask, the ones they already know the leader will find tractable. The genuinely complex ones stay in the hallway conversations and the Slack threads that senior leaders never see: the problems with no clean ask, no obvious solution, no good option worth surfacing to someone likely to want a quick answer.

This is how executives end up with excellent situational awareness about the things that are going fine and almost no visibility into the things that are about to fail. The 70% transformation failure rate that HBR identified in March is partly a strategy problem, partly a structural problem, and partly this: the people closest to execution stopped bringing the real signals to the people with authority to act on them, because experience taught them that doing so would result in a quick answer rather than a genuine conversation.

The leader doesn't notice because the signal of the closed loop is the absence of something. Absence is hard to read. Everything looks orderly. The retrospectives run cleanly. The status updates are positive. The meeting ends on time.

The Discipline the Best Senior Leaders Build

The counterhabit is not complicated, but it requires something most high-performing leaders find genuinely difficult: sitting with a problem a beat longer than feels productive. Asking the second question instead of offering the first answer. Getting comfortable with the silence that follows "I'm not sure. What do you think?"

Not because they don't have views. Senior leaders have views. The discipline is about sequencing. When a leader's answer comes too early, it forecloses the room. Their opinion has weight, more weight than they often realize, and weight deployed before the room has had a chance to generate its own thinking tends to collapse the conversation toward the leader's frame rather than expand it.

The most effective senior leaders I've worked with have developed a specific habit around this. They ask what they're not hearing. Directly, sometimes out loud: "What's the problem you almost didn't bring to this meeting?" It feels unusual the first time. The second time it starts working. Over months, it rebuilds the kind of information flow that organizational layers naturally erode.

The COO eventually named the pattern to his team explicitly. He told them he'd noticed the problems had gotten simpler. He asked them to bring the ones they'd been holding back. That conversation was uncomfortable. The ones that followed were the most useful he'd had in months.