When the Argument Isn't Really About the Argument

You've probably been in a meeting like this one. Frank, an engineering manager, is pushing back hard on a feature Susan, the product manager, wants to ship. He's got reasons: the feature doesn't make sense, users won't use it, the value isn't there. Susan fires back with user research, usage data, customer quotes. Frank counters. Susan counters. Round and round.

What Susan doesn't know is that Frank's team is already buried. They're behind on three other projects, and there is absolutely no way they can take on anything new right now. Frank knows this. But instead of saying it, he's building a case for why the feature is a bad idea.

This is more common than you think, and there's a real psychological reason it happens.

The Ego Under Threat

Admitting your team is behind schedule is painful. It means owning failure, even if the reasons are complicated. It means looking like the person who let their colleagues down. For Frank, saying "we can't do this because we're underwater" feels like walking into a room and announcing that he's incompetent.

So his brain does something clever: it finds another reason. Psychologists call this motivated reasoning. You start with a conclusion you need to be true (we can't do this feature) and then work backward to construct arguments that support it. The arguments feel completely genuine to Frank; he believes them. But they're downstream of an emotional need, not an objective assessment.

Neuroscientifically, what's happening is that Frank's threat detection system (the amygdala and related circuitry) has flagged "admitting failure" as dangerous. His prefrontal cortex, which handles rational thinking, gets recruited not to find the truth, but to rationalize his way out of an uncomfortable situation. Lisa Feldman Barrett's work on constructed emotion is useful here: our brains are constantly making predictions and managing resources, and a big part of that is managing social and reputational threats. Frank isn't lying exactly; he's protecting himself in a way that feels very natural.

What Susan Could Have Done Differently

Here's the counter-intuitive part. Susan kept bringing better facts and arguments, thinking that would crack it. But she was playing a game of logic when Frank was playing a game of emotion. More evidence doesn't fix that.

If Susan had paused and asked herself, "Why would a reasonable person argue this hard against a feature with decent evidence behind it?", she might have landed somewhere more useful. What's at stake for Frank, beyond being right about the feature? What would he be giving up if he agreed?

This is basically what Buddhist psychology calls "right view": seeing things as they actually are, not as we want them to be. Susan was so focused on her own position that she wasn't really seeing Frank's situation clearly.

A simple question could have changed everything: "Frank, I know your team has a lot going on. Is this a capacity issue, or do you genuinely think the feature is wrong?" That kind of question gives Frank an off-ramp. It signals that admitting a constraint is safe, that no one is going to attack him for it.

The Practical Takeaway

When a colleague argues unusually hard against something with good evidence behind it, stop treating it as a debate to win. Start asking what they might be protecting. The argument you're having on the surface is rarely the actual argument.

Understanding what's really at stake for the other person isn't just kinder; it's faster. Susan spent an hour fighting the wrong battle. One curious, low-threat question could have gotten to the real problem in five minutes.