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.

Here's the deeper version of what's happening, and it's not the popular "his emotional brain hijacked his rational brain" story. There aren't two brains fighting. On Lisa Feldman Barrett's account of constructed emotion, Frank's brain is constantly running predictions and budgeting resources, and a big part of that is heading off social and reputational threats before they land. "Admitting we're underwater" gets predicted as a threat to his standing, and the brain doesn't process that threat in some lower region and then hand it up to be reasoned about. It builds the whole experience at once, including the felt conviction that the feature is genuinely bad. The reasons aren't a cover story bolted on after the feeling. They are the prediction made experiential. That's why they feel completely sincere to Frank, because to his brain they are not a rationalization. They are what the threat prediction looks like from the inside.

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.

Why the Surface Argument Resists Evidence

This is why piling on more evidence tends to make these arguments worse, not better. If Frank's "the feature is bad" conviction is what a reputational-threat prediction feels like from the inside, then better data about the feature isn't aimed at the thing actually generating his position. It's answering a question he isn't really asking. The conviction will keep regenerating reasons as fast as you knock them down, because the prediction underneath hasn't changed.

What does change it is lowering the threat the prediction is tracking. The reason "Frank, is this a capacity issue, or do you genuinely think the feature is wrong?" can work where an hour of evidence didn't is that it changes what his brain is predicting, from "I'm about to be exposed as the manager who fell behind" to "naming the constraint is safe here." Once that prediction shifts, the manufactured reasons usually lose their urgency, because they were never the real load-bearing thing. The argument on the surface is rarely the actual argument, and the actual argument is a prediction about what it costs to tell the truth.