I know how to disagree. But do I actually allow disagreement when I have the power?

Years ago, one of my bosses said something to me that has stayed with me.

He told me that before a decision was made, he expected me to give the discussion everything I had. Challenge the team. Challenge my peers. Challenge him. Make the case. Say when I disagreed. Don't hold back just because someone else had more authority or saw it differently.

But once the decision was made, even if the organization chose the exact opposite of what I had recommended, he expected me to support it fully.

At the time, I thought he was teaching me about commitment. Over the years, I've come to see something else in it. He was asking me to develop two very different leadership muscles: the courage to disagree, and the ability to let go when disagreement didn't produce the outcome I wanted.

Years later, I came across a name for what he was asking of me: disagree and commit. Debate needs dissent. Execution needs alignment. Run both phases the same way and you weaken one of them.

Most senior leaders I work with say they're comfortable with disagreement. I believe them. But the harder question is whether they can let someone disagree with them without needing to change that person's mind.

A lot of leaders are comfortable with disagreement at the beginning of a conversation. What's harder is disagreement at the end.

You've explained your thinking. They understand it. They still don't agree.

Not every disagreement needs a decision. Sometimes there's nothing to commit to except continuing to work well together while seeing things differently.

That moment tells you much more about how comfortable you really are with disagreement than whether you invited it in the first place.

Sometimes we keep talking because we need agreement

I was reminded of this in a coaching conversation. The conversation moved almost immediately toward influence: how to make the case, how to bring the other person around.

I stopped it.

Influencing someone and disagreeing with someone are not the same thing. Sometimes the conversation has already done what it needed to do. You understand my reasoning, you still see it differently, and we can leave it there.

That sounds simple. It often isn't.

Sometimes what's underneath is this: I need you to agree with me so I can feel that you understood me.

That's a different need.

And people can feel it.

Over-explaining can be a clue

There's a difference between explaining for clarity and explaining for validation. Clarity helps someone understand your position. Validation keeps going until their response gives you what you need: agreement, reassurance, confirmation you were right.

The behavior looks the same. The motive doesn't.

If disagreeing with you means having to defend the point over and over, people learn disagreement has a cost. They still challenge you on the big things, but they get selective, hold back on the smaller ones, or agree because it's easier.

Disagreement is welcome, as long as it eventually becomes agreement.

Influence doesn't guarantee the outcome

Senior leaders are often rewarded for the quality of their judgment, which creates a quiet assumption: if you really understood what I understand, you'd reach the same conclusion.

But two smart, well-informed people can look at the same situation and reach different conclusions.

Understanding does not require agreement.

My former boss's lesson lives here. Before the decision, give the organization your best thinking: say what you see, say what you disagree with, don't hold back because you might not win the argument.

Once it's made, help it succeed instead of proving you were right.

That commitment shouldn't mean permanent silence. If a decision starts causing real harm, raising it again isn't relitigating, it's responsible. You can still say, "I would have made a different call," and move forward fully committed.

There is another side to psychological safety

Many organizations say they want healthy conflict. I'm more interested in what happens after it.

The real debate moves into the hallway. People leave the meeting saying, "I guess we decided," while privately still lobbying for their position. Someone who lost the argument quietly pulls back.

Amy Edmondson's research on psychological safety established the importance of people feeling safe enough to take interpersonal risks at work. But I'm interested in what happens after someone takes that risk.

We ask whether people feel safe enough to speak up. The harder question is whether they're safe enough to remain in disagreement.

Can they tell me they still see it differently after I've made my case, without managing my reaction, softening their position, or agreeing just to end the conversation?

If they can't, the team may have permission to challenge, but it doesn't yet have the conditions for independent thinking.

Research on minority dissent supports this. Psychologist Charlan Nemeth found that genuine dissent can stimulate divergent thinking, pushing people to consider more perspectives and generate more original ideas. The value of disagreement, in other words, isn't necessarily that one side persuades the other.

It can change the quality of the thinking itself.

Watch what happens the next time someone disagrees with you after you've made your case.

Notice the urge to explain it one more time.

Ask yourself whether you're adding something the conversation still needs, or trying to get something you need from the conversation.

The real test happens after the conversation ends: whether people can still see it differently, still trust each other, and still commit fully when a decision calls for it.