Your team is pushing back. Here's what they're not saying.

A CEO we work with was ready to restructure. He planned to bring a new leader into his executive team, at the same level as several heads of function. He took the plan to them, and the objections came fast. 

Was this person ready? Did they have enough experience? Had they been here long enough? 

They were fair questions. They just weren't what the room was really worried about. 

Each of those leaders was about to lose part of their team and part of their role. Nobody said that out loud, but it drove every question asked. 

We see this a lot. A CEO brings a change they've thought through carefully. The team pushes back. So the CEO explains it again, a bit louder. Then comes the question that gives it away... "Does this make sense?" 

Usually it makes perfect sense. That's rarely the problem. 

Explaining it again won't fix it 

When people push back, most CEOs assume the team hasn't understood. So they reach for a clearer slide or a better explanation. 

But the logic is often fine. Under the objection sits something people find harder to say. They might be losing status. They might not know why the work matters. They might not trust the people involved. 

In that restructure, capability was a fair question and losing scope was a fair feeling. They needed two different conversations, and you can't have the second one while pretending you're only having the first. 

Sometimes "no" means "tell me why" 

In another business, a team member flatly refused a task. The founder started to wonder about his attitude, and whether he fitted the culture. 

When they talked it through, he hadn't refused at all. He wasn't willing to start until he understood why the work mattered, and he'd explained himself badly. 

The behaviour still needed dealing with. But the problem was completely different from the one the founder thought he had. 

The loudest voices aren't the whole room 

A third leadership team came out of a tough session sure their senior managers had rejected a new way of setting priorities. They spent hours explaining the framework again. 

Then we went through the group one person at a time. Most of them were positive. The strongest concerns sat with a few people, and some of those concerns had little to do with the framework. It had simply become the safest place to argue about trust and authority. 

So the plan changed. Instead of redesigning everything around the loudest voices, the leaders sat down one-on-one with the people who actually had concerns. 

Good logic still has a cost 

A fourth CEO was merging teams for sound business reasons. He was right about the logic. He was also right that some good people would feel worse off for a while. 

Both things were true. The risk was treating their discomfort as proof he was wrong, or treating his logic as proof they had no reason to feel it. 

What to do next time your team pushes back 

Hold off on the better explanation and ask questions instead. What's worrying you about this? What would you lose? What are we not seeing? 

Listen to find out what you might have missed. If someone raises something you hadn't considered, treat it as information, not as a challenge to win. 

If the meeting isn't the place for it, take it outside. A one-on-one is often where people tell you what's really going on. 

Then make the call. Understanding the resistance doesn't mean you have to give in to it. It means you decide with the whole picture in front of you. 

A little challenge for you and your team. Think of the change you're pushing hardest on right now. Who's pushing back, and what might they be worried about losing?