I got this wrong in a client meeting recently and it's worth showing the whole thing, because the failure is more useful than the principle.

Someone I've worked with for a while pushed back on a set of changes. Too hard. Won't work operationally. We'd have to change too much. I listened to all of it, and then I said something close to: it sounds like you're trying to do as little as possible here.

He didn't have an answer. I was right about the behavior and wrong about everything else, and I knew it within about a minute of the call ending.

What I actually did

I took the objection at face value.

That's the whole error. Not rudeness, not impatience. I heard "that won't work operationally" and processed it as a claim about operations, which is what the words say and almost never what the words mean.

What it meant was: the things you want changed are things I built, and I committed to them in front of my team, and agreeing with you costs me something you're not counting.

I know that. I've written it down. I teach it. And in the moment I didn't apply it, which is the part worth examining, because I wasn't distracted in the way that word usually means. I was on the call. I was paying attention. I could have repeated back everything he said.

Being present is not the same as listening

Here's the distinction I'd been fuzzy about.

Active listening gets described as a posture. You're engaged. You're not planning your reply while they talk. You mirror, you paraphrase, you reflect it back so they know they were heard. All of that is real and all of it has its place.

None of it is the thing.

Actively listening means passing what's being said through a framework. It's an act, not a state. You have filters running, and the filters are what let you hear the difference between what someone is saying and what they're conveying. Without them you're a very attentive recording device.

Said: that won't work operationally. Conveyed: I'd have to change something I made, in front of the people I made it for.

Mirroring gets you an accurate copy of the first one. Only a filter gets you the second.

The filter that would have caught it

There are several worth running. This is the one I should have had loaded and didn't.

Listen for objections that work against the person's own stated goal.

Somebody tells you what they want. You tell them what getting there requires. They hand you a list of reasons it won't work. Stop there, because those two things can't both be true. If the objections are counter to the outcome they told you they need, something else is driving them, and continuing to debate the objections on their merits is a way of not finding out what.

It's a cheap filter. It fires on a contradiction you can hear in real time, and it doesn't require you to be clever, only to be checking.

The reason it's worth naming specifically is that face-value objections are plausible. Capacity really is finite. Operational difficulty is real. Nothing about "we don't have the bandwidth" sounds like evasion, which is exactly why it works as one.

Why I lost it

Two reasons, and neither is interesting, which is the point.

I was stressed and distracted in general, and I brought that into a call where I thought presence would be enough. It wasn't. Presence without a framework is just attendance.

And I'd mistaken the relationship. Everything with this person had been good for months. What I hadn't noticed is that nothing had tested it. We'd been agreeing about things that cost him nothing. The moment I proposed changes that touched what he'd built, the relationship got tested for the first time, and I read the resistance as a change in him rather than a change in what I was asking.

That matters if you carry accounts. A relationship that's never been tested isn't strong. It's untested, and those look identical right up until they don't.

The fix is preparation, not talent

You need a buffer before a meeting. Five to fifteen minutes, and not for the thing everyone uses it for.

Reviewing notes and action items is preparing for the content of the call. That's necessary and it is not this. You also have to prepare to be present, which means loading the frameworks you intend to listen through, so they're running when something arrives that needs them rather than arriving as a realization on the drive home.

I skipped that. I did the notes and I thought that was preparation.

And when you do catch it, call up

One more thing, because I got this wrong in the same sentence.

When I told him it sounded like they were trying to do as little as possible, I called him out. In front of a member of his team, which made it worse.

The behavior did need naming. But you call out the behavior and call the person up. Something closer to: I understand where this is coming from, and I think we need to move past it, because I know how much you want this to work and you're going to be the one living in whether it does.

Same observation. Completely different thing to be on the receiving end of. One of them makes agreeing with me an admission, and the other makes it the obvious next move.

Separating the person from their process is the same discipline as separating them from the thing they built, and I'd argue it's the whole job once you're past the easy part of a relationship.

One caveat I left out, and it turns out to be the part that decides whether any of this works: calling somebody up requires knowing what is being defended, and if you do not have that, the correct move is silence rather than a gentler version of the same question.

The part that's genuinely good news

More resistance has surfaced with this client the longer we've worked together, and my first read was that things were going badly.

They're going deeper. Early on I was proposing things that cost nobody anything. Now I'm proposing things that touch what people built and committed to, and that's where the actual value is. Resistance showing up late isn't a relationship degrading. It's usually the first evidence you've stopped working on the surface.

Frustrating in the moment. But if you're never meeting resistance, it's worth asking whether you're proposing anything that matters.