A few years ago I was sitting in on a team meeting — not my team, I was there as an observer — and the manager was doing something I've watched hundreds of managers do.
Every time someone started to speak, he'd wait about four seconds and then finish their sentence. Sometimes he'd jump in with a yeah, exactly, and pivot to his own point. Sometimes he'd just start talking over them — not rudely, just confidently. Like he already knew where they were going and didn't see the need to wait.
Afterwards I asked him how he thought the meeting went.
"Really productive," he said. "Good energy."
I've thought about that conversation a lot since.
Interrupting isn't just rude. It's painful.
Here's something most managers don't know. Being interrupted — or simply being ignored when you're speaking — activates the anterior cingulate cortex. That's the same region of the brain that processes physical pain. The same circuitry that fires when you touch a hot stove.
Your team members aren't just mildly annoyed when you cut them off. Their brains register it as hurt.
Now — before you feel terrible: most managers who interrupt aren't doing it maliciously. In my experience, they're doing it because they're engaged, they think quickly, and they genuinely believe they're helping the conversation along. It comes from confidence, not contempt.
But good intentions don't change the neurological outcome.
The problem with silent interrupting
What makes this even more interesting is what I call silent interrupting.
You're in a meeting. Someone is explaining a problem. And instead of actually listening, you're doing something else entirely — you're preparing your response. Composing the solution, forming the question you want to ask, or quietly disagreeing before they've finished speaking.
Your mouth is closed. But you've left the building.
The person speaking can feel this. It's not mystical. Humans are wired to read faces, eye movement, micro-expressions. When the person across from you is no longer tracking what you're saying — even if they're silent — you notice. The anterior cingulate cortex activates anyway.
Silence, it turns out, isn't the same as listening.
What listening actually does to the brain
When a manager actually listens — fully, without the preparation loop running — they engage the theory-of-mind network: the superior temporal sulcus and right temporoparietal junction. These are the regions responsible for perspective-taking. For understanding what another person actually means, not just what they said.
A manager who practises genuine listening isn't just being polite. They're literally upgrading their own ability to read their people.
Teams whose leaders listen consistently show measurably higher psychological safety — fewer problems get buried, more dissent surfaces before it becomes expensive, people bring the real issue rather than the safe version of it.
The open-door manager who had a closed-door brain
I worked with a team leader who told me, with genuine pride, that he had an open-door policy. Anyone could come to him with anything.
When I spoke to his team separately, the picture was different. People didn't come to him because when they did, he'd solve the problem in the first ninety seconds and the conversation was over. He was efficient. He was helpful. And he had no idea his team had quietly stopped bringing him the complicated things.
He wasn't a bad leader. He just hadn't learned to wait.
The behaviour he worked on was simple — uncomfortable, but simple. Before offering anything: ask one clarifying question. Not rhetorical. A real one. Then actually listen to the answer before doing anything else.
Within a month, his team was having different conversations with him.
None of this means you have to become someone who sits in meetings nodding slowly and saying tell me more every forty-five seconds. That's not listening either. That's performing listening, which is its own problem.
It just means slowing down enough to let the other person's thinking land before yours takes over.
The manager I observed at the start of this piece ran a team that was performing well by most measures. But when I looked more carefully, I noticed something: his team never surprised him. They gave him what they thought he wanted. They'd learned, over time, that the conversation went faster if they arrived at his conclusion quickly.
That's not high performance. That's compliance with good optics. The two look similar from the outside. They feel completely different from the inside — and eventually, they produce very different outcomes.