Your team agrees with you a lot. Meetings end in nodding. Plans you propose come back rubber-stamped. Your direct reports tell you the strategy makes sense, the timeline is realistic, the priorities are clear. You feel aligned. Productive. Like you've finally built the team you wanted.
You haven't. You've built a team that learned it's not worth disagreeing with you.
A recent survey from CNBC found that 61.3% of individual contributors say they often observe people staying silent when they have differing opinions. Half your team thinks you're wrong about something right now. They're just not telling you. And the more senior you get, the worse this gets — because nobody wants to be the one who pushed back on the VP's call and ended up on the wrong side of it when it didn't matter. CNBC
Here's the uncomfortable part: silence isn't a culture problem. It's a feedback loop you trained. Every time someone raised a concern and you defended your position instead of engaging it, you taught them what disagreement costs. Every time you said "good point" and then did exactly what you were going to do anyway, you taught them that pushback is performative. Every time a meeting ended with "any concerns?" and three seconds of silence and you moved on, you taught them the question was rhetorical.
You don't need a psychological safety workshop. You need to change three specific behaviors.
Stop asking "any concerns?" at the end of meetings. It's the worst possible time to invite disagreement — the decision feels made, the meeting is ending, and speaking up means extending a meeting nobody wants to extend. Move dissent to the beginning. Try: "Before I share where I'm leaning, what would you do here?" or "I want to argue against my own proposal for two minutes — then tell me where I'm weak." You're not soliciting concerns. You're forcing a structural moment where the path of least resistance is to engage, not nod.
Reward the disagreement publicly, even when you don't take the advice. If someone pushes back in a meeting and you say "great point, but here's why we're going to do it the other way" — and then you never mention it again — you've taught the room that pushback gets you politely overruled. Instead: "Priya pushed back hard on this last week, and I want to call out that her concern about timeline risk is the one I'm most worried about. We're proceeding anyway, and here's the bet I'm making." Now the cost of disagreement dropped. The reward went up. People watch this stuff.
Name your own bad calls out loud. If your team has never heard you say "I was wrong about that" or "the call I made last quarter didn't work, and here's why," they assume the role doesn't permit it. They will not be the first person in the room to admit a mistake if the manager never has. This isn't self-flagellation. It's a permission structure. Say it cleanly, once, and move on.
A note on what this isn't. You're not trying to create a team that argues about everything. Constant friction is just as bad as silence — it's silence in a different costume, because people stop saying what matters when everyone's saying everything. The signal you want is specific: when something important is on the table, the right people speak up. The rest of the time, they execute.
You'll know it's working when someone tells you, in a 1-on-1, that they think a decision you made last month was a mistake. Not in a polite, hedged way. Directly. Your job in that moment is not to defend the decision. It's to ask one question — "what would you have done?" — and actually listen to the answer.
Bottom line: if nobody on your team disagreed with you this quarter, that's not alignment. That's a data outage. And you caused it.