Fostering an Obligation to Dissent

When my team does not tell me I am making a mistake, they are being dishonest with me by omission. That is how I think about silence in the room. It is not
neutrality, but a failure of honesty. Obligation to dissent is a fancy way of saying: If you disagree with something, you have the responsibility to speak up, even you don't want to. Regardless of your seniority in the team.

The problem is that most teams (that I've worked in) are systematically silent by default. Not because the people in them are passive, but because at some point, speaking up didn't go so hot. Maybe they worked for a leader who said they wanted folks to raise their concerns, but wasn't really open to candid feedback. It takes just one time of a dissenter being dismissed, talked over, or made to feel foolish for the rest of the team to draw a quiet conclusion: it's not worth it. The discussion over semantics or small things: Not worth it.

I watched this play out in a previous team. One engineer was technically strong but dominated every discussion. He just had very strong opinions and the confidence to hold the floor. Over time the rest of the team stopped pushing back. Not because they had nothing to say (and not because this engineer was always right - quite the opposite), but because engaging with him meant a guaranteed long-winded discussion where this engineer spoke 80% of the time. We all started choosing silence and imperfect solutions over a daunting conversation.

Skewing the conditions

Telling the team they have an obligation to speak up would have changed nothing. The dynamic was structural, not motivational. What actually ended up working was giving the engineer a different role. I asked him to be the designated devil's advocate. Nitpicking, challenging, stress-testing assumptions. That was now explicitly his job. The small reframe changed the entire dynamic and the rest of the team no longer felt they were picking a fight with him. He was doing his
role. They were doing theirs.

You cannot just declare an "obligation to dissent" and expect it to happen. You have to engineer the conditions that make it possible. Psychological safety is the prerequisite, and psychological safety is not built by announcing it. It is built through consistent behavior. And it also a very fragile thing and can be destroyed in a single moment.

An honest caveat

In my case, the devil's advocate role solved the silence problem, but it raises an obvious question: if you've now given everyone permission to challenge, haven't you just traded one dysfunction for another?

Dissent is a tiresome time sink if you let it run unchecked. I also know the allure of hoping everyone will nod their heads in a decision to quickly jam it through, especially when you are strapped for time. A team where everyone feels entitled to re-litigate every decision is not a high-functioning team. The goal is not maximum debate. It is surfacing the right objections at the right moment, and then moving. The obligation is to speak up when you genuinely see a flaw, a blind spot, or a better path. This is a challenging line to draw, and even more challenging to moderate and enforce. But the dissenters who ask the uncomfortable question that reframes the whole problem are the ones I am quietly grateful for, even when it costs us an hour.

The broader principle is this: dissent needs to know when it's open and when it's closed. A few things that actually enforce this:

Decision rights are clear before the discussion starts. Everyone knows who is making the final call. Dissent is input, not veto. It's your role as a leader to suffocate the discussion when there are diminishing returns, and take the call.

The challenge phase and the decision are separated explicitly. The devil's advocate role works because it signals: this is the moment we stress-test this. Once
that phase is done, you move. You do not relitigate in execution.

Write down the objections and why you proceeded anyway. On this point I could write an article in itself. It does two things: it signals the dissenter was genuinely heard, and it holds you accountable later. If the objection turns out to be right, you own it. That accountability is what makes the next round of dissent feel worth raising. But there are two further benefits.

Frequently reviewing decisions

The first is circumventing malicious compliance. When a team doesn't genuinely feel heard, they don't actually commit, but they perform commitment. They execute the decision minimally, wait for it to fail, and feel vindicated when it does. You asked them to disagree and commit, but what you got was disagree and watch. The decision log is partly a defense against this: it signals that the objection was real, was considered, and has a named owner. That changes the psychological contract.

The second is the general need for decision review. Most decisions never get revisited honestly. When things go wrong, the decision is mostly reframed as a collective "we agreed on this together" decision, which conveniently distributes accountability and lets you off the hook. That is an own form of dishonesty.

If you make the call, you own the outcome. Reviewing decisions and saying out loud "I was wrong, the objection was right" is what makes the whole system credible. Without that, the obligation to dissent is just theater. People speak
up, the leader decides, nothing is ever examined, and eventually the team concludes that the challenge phase is decorative.

When your team stops telling you when you are wrong, you have already lost something important. Getting it back is much harder than not losing it in the first place.