Five minutes after the all-hands, someone asks me in the hallway, "What did he mean by that?" Then another person: "So what are we actually supposed to do?" I didn't have a great answer either. We'd all sat through twenty minutes of a strategy change presentation. We all nodded. None of us was in the conversation.

This isn't a one-off. I see this pattern everywhere – across teams, across functions, across seniority levels. People show up to meetings. They sit. They nod. They leave without having processed what was said. Full attendance, zero presence.

Most advice on listening tells you to add behaviors – nod more, paraphrase, ask clarifying questions. I think the fix is the opposite. Presence isn't something you perform. It's what remains when you stop doing everything else.

This isn't a listening guide. What follows are patterns – ways presence breaks down in rooms I've been in, including when I was the one not present. Once you start recognizing them, they're hard to unsee.

How presence breaks down

I see this play out in a few distinct ways. Sometimes it's obvious – a room full of silent nods. Sometimes it's subtler.

Silent nods, two flavors

This is the one that does the most damage, and it's invisible in the moment.

Flavor one: don't understand, won't say so. That all-hands I described at the top – this was exactly it. A room full of people nodding along to something they hadn't actually processed. Nobody asked a clarifying question. Nobody said, "I don't follow." The meeting felt smooth. The hallway afterward told the real story.

Flavor two: understand fine, disagree, won't surface it. A manager assigned a direction. The team silently accepted. Later, over coffee, one of the engineers told me directly: he disagreed, saw no value in it, and was going to do the minimum to get it off his plate.

The disagreement never entered the room where it could have changed something. It lived in the hallway, in the coffee chat, in the Slack DM. By the time it surfaced – slow execution, low quality, quiet attrition – nobody connected it back to that meeting where everyone nodded.

Both flavors look identical in the room. Silent nods. But one is a comprehension gap, and the other is a trust gap. A speaker who's actually paying attention to the room – not just broadcasting – can sometimes tell the difference. Yet most speakers don't, because they're focused on getting through their material. They're not listening either.

Solving before hearing

Engineers are trained to decompose problems. It's the job. But that instinct kicks in too early in conversations. Someone starts describing a situation. Ten seconds in, your brain is already pattern-matching and mapping it to something you've seen before, composing a solution.

The problem: you're now building your response in parallel with the other person still talking. You're not tracking their reasoning – you're constructing your own. By the time they finish, you've got an answer to a question they didn't ask, because you stopped listening after the first thirty seconds.

Listening for your turn

This one I catch myself doing. Someone is talking, and I'm holding my argument in my head, waiting for a gap. The physical tell is real – I lean forward, I nod faster. Not because I agree, but because I want them to finish so I can say my thing.

People who are vocal and not shy do this without thinking. They fire their thoughts at every opening. The quieter person's point never fully lands because the room has already moved on to the next response.

The worst part: you don't realize you're doing it until someone's point slides past you and you can't recall what they actually said. And when it happens to me – when I'm the one not being heard – I push through. Force the idea through anyway. It works, but it's not solving the listening problem. It's bulldozing past it.

It happens in 1:1s too

You might think this is a group-meeting problem – too many people, too many laptops, too much noise. But it happens in the most intimate format we have: the 1:1.

I've caught myself doing it. Someone is talking to me one-on-one, and my eyes drift to the screen. I'm scanning something – a notification, a message, a tab I forgot to close. Tracking something that isn't the person in front of me. Not because I don't care. Because the pull of the inbox is stronger than any of us wants to admit.

This is the version of the problem that's hardest to name, because it feels personal.

What being present actually looks like

Closing the lid

I was in a meeting with my team. Everyone had laptops open – the usual. Someone was presenting an idea, and the room had that familiar energy: half-listening, half-typing.

I closed my laptop lid. Started looking at the speaker. Actually tracking what they were saying.

I saw something shift in their eyes – a kind of recognition that someone was paying attention. Then one of my teammates closed their lid too. Then another. Not everyone, but enough. The conversation changed. Suddenly, there were real questions. Pushback. Ideas building on each other. Before the lids closed, it was a broadcast. After, it was a dialogue.

That small act – closing a laptop – did more for the conversation than any "great question" could have. Because the question only works if you've been listening long enough to know what to ask.

Dropping performance

Here's the thing about active listening that most advice gets wrong: it's not a technique. If you try to perform it – the nodding, the eye contact, the clarification question every twenty seconds – people notice. They feel the gap between your body language and your attention.

It only works when you actually stop thinking about everything else. You look at the person. Not staring – eye contact from time to time. You let them flesh out their thoughts. You can be completely silent. That's fine. Nobody needs you to nod on a timer.

The real skill is subtraction, not addition. Remove the distractions. Remove the urge to respond. Remove the performance. What's left is just… focus. You're in this conversation and nowhere else. That's simpler than any framework, and harder than all of them.

Holding back

Before a recent vacation, I was handing over a project I'd been leading – research done, core team assembled, draft plan written. My teammate needed to pick it up and run with it.

In our 1:1 handover meeting, she started asking questions and sharing her own vision for how to approach it. I remember the tension in my own head – I knew the answers. I had my understanding, my vision, my plan. Every instinct said: jump in, push the knowledge, save time.

I didn't say a word. I just listened. Looked at her screen when she showed me things. Nodded – naturally, not performatively.

She covered the whole story. Answered the majority of her own questions just by working through the plan and my notes. And then she proposed a couple of insights I had missed in the planning – things she added as follow-up topics for the project team.

I'm fairly sure that wouldn't have happened if I'd started in expert mode. The handover would have been faster, but worse. She would have received my understanding instead of building her own. And those insights she caught? Buried under my monologue.

Pulling the rope

Here's how I think about it. When someone is explaining a hard problem – the kind that doesn't have clean edges – they're pulling a heavy rock up from the bottom on a rope.

You can stand there and watch them pull. Or you can step closer, grab the rope, and help.

Active listening is the grabbing. Resist the urge to decompose immediately. Follow the other person's thread before you start your own. That's the rope-pulling: making the effort to understand what they're actually saying before you decide whether you agree.

Key takeaways

The next time you're in a room, you'll probably catch one of these – in yourself or someone else. That's the point. Once you see the pattern, you can't run it on autopilot anymore. You don't need a technique for what happens next. You just stop doing the thing you caught yourself doing.

1. Presence is not attendance. Being in the room and being in the conversation are different things.
2. Engineers default to problem-solving mode, which means they start constructing responses before they've finished hearing the problem. Resist the decomposition reflex.
3. Silent nods hide two different problems: people who don't understand and people who disagree. Both look the same. Both break things differently.
4. Listening is labor, not passivity. You're helping the speaker articulate something hard, not waiting for them to finish so you can talk.
5. Listening isn't a skill to add to your toolkit. It's setting down reflexes you already have – the solving, the responding, the performing.

Further reading

• Steve Huynh — on how the questions you ask communicate how you think: 5 Questions That Make People Take You Seriously
• Wes Kao — on detecting and addressing the Question behind the question