Your team won't challenge your ideas (that's the problem)
Why teams won't challenge you and how to fix it
The architecture review is almost done. Lead engineer walks through the new microservices design. Solid work. Clean boundaries. Yes! Everyone’s nodding.
Then someone raises their hand. Someone who doesn’t usually speak up in these meetings.
“Why are we splitting this service? The load is low. We don’t have the team size to maintain multiple deployments. This adds complexity we don’t need yet.”
The room goes quiet.
Lead engineer’s face shifts. Not angry, exactly. Just... tight. “We’re planning for scale. This is how you design systems properly.”
The questioner backs down. “Yeah, makes sense. Just wanted to understand.”
Meeting continues. Decision stands.
Later, the same lead engineer complains to you: “Nobody on this team challenges anything. They just agree with whatever I propose.”
The performance of openness
You’ve seen this movie before. I know I have.
Leader asks if there are any concerns in a meeting where everyone knows the answer is supposed to be no. Engineering manager invites pushback on a timeline they’ve already promised to stakeholders. It’s not openness. It’s theater.
Real challenge doesn’t feel like a smooth meeting where everyone nods thoughtfully and agrees all around. Real challenge creates friction. It slows things down, makes people uncomfortable, and almost always makes them defensive.
This is especially important now. Speed matters more than ever. We’re making decisions faster and faster. And when speed is the priority, we’re tempted to skip the challenge phase. Why slow things down with questions when we could just move forward?
Challenging slows things down temporarily, but it speeds them up in the longer run. You either spend an hour now finding the holes in the plan, or you spend three months later fixing what you built on a broken foundation. The question isn’t whether to challenge. It’s whether people are willing to make the short-term sacrifice of slowing down to get it right.
When someone objects that challenging is a waste of time, the response is simple: challenging things now is cheap. Changing the course of action later is very expensive.
If your open-to-feedback culture never produces tension, nobody’s actually challenging anything.
They’re performing agreement while privately thinking you’re wrong.
This cost me. I used to end meetings feeling great because everyone was aligned. Then I’d get Slack messages an hour later about concerns people didn’t raise in the room. Four messages from four people. None of whom said anything when it mattered.
Turns out I was running a very efficient pipeline: meeting to Slack to nowhere.
The meeting wasn’t open. It was a performance. And I was the director demanding everyone stick to the script.
Real dissent isn’t polite
Real challenge doesn’t sound like interesting perspective, let me play devil’s advocate for a moment. It sounds like this assumption is wrong or we’re solving the wrong problem or this timeline is unrealistic and we’re setting ourselves up to fail. Not polite or hedged. Direct.
It questions core assumptions, not implementation details. It doesn’t ask whether to use Postgres or MySQL. It asks whether we even need a database for this. It proposes alternatives - instead of microservices, here’s why a modular monolith solves this better right now. Sometimes it questions whether the problem is worth solving at all. Users aren’t asking for this, so why are we building it?
This is uncomfortable because challenge implies the person making the decision might be wrong. And most of us don’t handle that well, even when we claim we do. Especially when we claim we do.
The tension is the point
Challenge creates tension because it threatens three things leaders care about: momentum, authority, and certainty.
You’re ready to move forward. Someone challenging the decision means stopping, reconsidering, maybe changing course. That feels like going backwards when you were so close to checking this off your list. When someone questions your decision, it can feel like they’re questioning your competence. Especially if they’re doing it in front of others. You’ve already decided this is the right path. Challenge introduces doubt. And doubt is uncomfortable when you’re trying to project confidence.
So we shut it down. Not explicitly. We’re too sophisticated for that.
We say let’s take that offline or good points, we’ll consider that, then proceed exactly as planned. We say we need to move forward as if momentum is more important than being right.
The challenge goes away. So does the thinking.
If someone challenges your idea and you feel defensive, that’s the signal it’s working. That discomfort means they’re questioning something you haven’t fully examined. The defensive feeling is your ego protecting a decision that might not be as solid as you thought.
Most of my best decisions came from challenges that made me uncomfortable first.
The “not like that” problem
Leaders say they want dissent. Then someone actually disagrees and the response is not like that.
You wanted pushback, just... gentler and more collaborative. Perhaps phrased as a question instead of a statement? Definitely raised privately instead of in the meeting. Better yet, framed as curiosity instead of disagreement.
You wanted dissent that doesn’t actually dissent.
I watched a PM get blindsided by this. They asked the team whether users actually want this feature. Important question. But the product lead heard it as you don’t know what you’re doing.
PM got feedback later: “You need to be more supportive of the team’s direction.”
The message was clear. Agree or stay quiet.
The gap between we want people to challenge ideas and not like that is where groupthink lives. People learn what kinds of challenge are actually safe. They learn which questions are allowed, and to phrase disagreement so carefully it stops being disagreement.
Then we wonder why nobody challenges anything. They tried once. It didn’t go well. They’re not making that mistake again.
When pushback is just Steve being Steve
But here’s the thing: not all challenge is valuable. Some people challenge everything, all the time, without offering alternatives. That’s not helpful dissent. That’s just Steve from team X who hasn’t liked an idea since 2019.
Good challenge is specific. It names what’s wrong and why. It proposes what to do instead. It’s aimed at making the decision better, not at proving the challenger is smart. Obstruction is vague - I don’t think this will work - with no specifics and alternative, just blocking.
Good challenge accepts when it’s overruled. The person made their case, the team considered it, the decision went another way, they move forward even if they disagreed. On the other hand, obstruction refuses to let go. Brings it up again next meeting. Undermines the decision after it’s made. Tells everyone privately it’s going to fail.
The hard part? Sometimes these look the same in the moment. Someone pushing back on your decision could be offering valuable perspective or being obstinate. You have to distinguish between the two without defaulting to anyone who disagrees is being difficult.
Ask yourself: are they questioning the decision or questioning whether you have the right to make it? Are they offering alternatives or just pointing out problems? Are they willing to commit after being overruled or still arguing two meetings later?
This is important: you don’t have to accept every challenge. Some are valid and improve the decision. Some are just people wanting to be against something. Acknowledge it, consider it, take what makes sense. Sometimes you’ll realize it’s important. Sometimes you’ll understand it but decide the tradeoff isn’t worth it. Both are fine. The key is actually considering it instead of dismissing it reflexively.
Worth asking yourself: do I want the right answer or do I just want to be right?
The other thing about timing: if everything is already laid out and things are in motion, if teams have already started implementing, pushback gets exponentially harder. This is why the right discussions need to happen at the right time - early, when the decision is still being made, not after everyone’s already committed resources.
Sometimes it takes one or two failed projects for people to understand this. When you’re three months into something that’s clearly not working, that’s when explaining sunk cost fallacy helps. The time and money already spent is gone whether you stop now or keep going. The only question is whether you want to spend more time and money on something that won’t work. Once people see this pattern play out, they get more comfortable challenging things earlier, before the costs pile up.
Making it safe to disagree
If you want real challenge, you have to make it safe. Not comfortable - safe. There’s a difference.
Start by making challenge explicit. I usually invest in the relationships with people before meetings, then at the beginning prompt them: “Please keep an open mind and open your chakras for a different point of view.” It’s a light way of saying we’re here to challenge each other’s thinking, not to agree.
Don’t ask if there are any concerns. That invites performance. Ask who’s willing to argue against this. Give the dissent a role - your job in this meeting is to find the holes in this proposal. Now challenging isn’t being negative. It’s doing the job.
If nobody wants to challenge because they don’t feel they have permission, use the devil’s advocate framing. “Let’s just entertain the thought - what if we’re looking at this wrong?” You’re giving people permission to explore different angles without feeling like they’re being negative or disloyal. It’s not disagreement. It’s thinking out loud together.
When you’re the one proposing something, invite the dissent yourself. Tell people you’re not married to the idea. You want to look at it from different angles, find any cracks and gaps in the plan.
When someone challenges you and they’re wrong, thank them anyway. Tell them you disagree but you’re glad they raised it. When they’re right? Say it publicly - you were right, I was wrong, this is better because you pushed back. People watch what gets rewarded. If challenge only gets thanked when it’s quiet and private, that’s what you’ll get.
The reality: there’s no guarantee you’ll be successful when you challenge something. Your point of view might not be the right one. But being quiet when things aren’t clear is definitely wrong. The cost of speaking up and being wrong is temporary embarrassment. The cost of staying quiet when you see a problem is watching the whole thing fail while knowing you could have said something.
What this looks like in real meetings
The best thing I ever did for my team’s willingness to disagree was changing my mind in a meeting after someone challenged my thinking. Not saying I’d consider it. Actually changing the decision right there. You’re right, this doesn’t make sense. Let’s do your version instead. Did it feel uncomfortable? Yes. Did it make me look less certain? Probably. Did it make the team more willing to challenge me in the future? Absolutely.
I worked with a tech lead where we became sparring partners. Complex problems - not just technical, but process, teams, infrastructure, how everything fit in the platform we were building. Sometimes it took us hours, sometimes multiple sessions, to get to a solution that finally ticked all the boxes. We’d give ourselves a pat on the back for solving it.
Then he’d say: “Okay, now that we have the perfect solution, let’s find three ways why this won’t work.”
We became our own worst enemies by poking holes in the plan and finding reasons why things could fail. This helped us identify risks we’d missed in the excitement of solving it. We succeeded every time. Not by throwing away the plan - by identifying the gaps, addressing them, or documenting the risks and accepting the reality. That’s what good challenge looks like. You make the solution better by trying to break it first.
When someone questions a design, don’t make it about who they are or what their role is. Make it about the idea. Is the question valid? Then it doesn’t matter who asked it. I’ve seen engineers dismiss questions from people they don’t consider technical enough, questions they would have seriously considered if they came from someone with more credibility. The question was good. The dismissal was ego protection. If you want real challenge, judge the argument, not the person making it.
Something else that helps: build relationships with people before you challenge them. They need to know you’re not attacking them as people, you’re challenging the problem and the solution. When you have that foundation, you can push harder without it feeling personal. When someone gets animated and raises their voice explaining something, that’s often passion, not aggression. They care. But if you have a relationship with them, you can point out when they’re getting defensive and they’ll actually hear it. Without that relationship, the same comment feels like an attack.
Catch yourself mid-response when someone challenges you. You felt defensive. You’re about to explain why they’re wrong. That’s the moment to pause. Ask yourself: Is this a bad challenge or am I just uncomfortable? Is the question invalid or does it threaten something I haven’t thought through?
The defensive feeling is information. I’ve ignored it enough times to know: three months later, they were usually right.
Sometimes I’ll just say it out loud: “I’m being defensive right now. I need to think this through. Thank you for pushing back, bear with me while I work through this.” Naming the defensiveness doesn’t make you look weak. It makes the challenge land better because you’re not pretending to be open while mentally building your counterargument.
Building this kind of culture isn’t quick. It takes time and courage. It means showing people that you don’t need to be the smartest person in the room, that you don’t need to be right all the time. People will start accepting and valuing that you look at things from different perspectives. And they’ll start doing it themselves. The key is that these discussions happen at meetings, not in Slack an hour later.
In your next team meeting
You’re in your next decision-making meeting. Someone’s proposing something. You’re about to agree.
Stop for ten seconds.
Ask yourself: what would the opposing argument be? If someone challenged this, what would they say? Is anyone in the room thinking it but not saying it?
If nobody’s challenging it, someone should. Maybe that someone is you.
Or you’re the one making the proposal. You’re about to ask if there are any questions. Try this instead: ask what you’re missing, what’s wrong with this. Then wait. Actually wait. Count to ten if you have to. Let the silence be uncomfortable.
Someone will fill it. If they don’t, that tells you something about the room. When someone does challenge you, notice your reaction. Defensive? Annoyed? If you say grateful, I won’t believe you (and neither should you). That feeling tells you whether you actually want challenge or just the appearance of it.
The alternative is comfortable groupthink
The alternative to uncomfortable challenge is comfortable groupthink. Meetings where everyone agrees and decisions that go unopposed.
Then reality hits. The timeline was unrealistic or the users don’t want the feature. The architecture doesn’t scale and oh my, the strategy was based on a wrong assumption. And everyone says they had concerns but didn’t think it was the right time to bring them up.
Someone probably tried to raise this earlier. We called it staying positive or moving forward or being a team player. When being agreeable matters more than being right, you end up living with decisions that nobody actually believed in.
Real challenge is uncomfortable. That’s not a bug. That’s the whole point.
If it doesn’t create at least a little tension, it’s not challenging anything that matters.