You floated an idea in the team meeting. A few heads nodded, nobody pushed back, and you left assuming you had buy-in. A week later you learned that half the room had quietly decided it wouldn’t work and said nothing at the time. The nods weren’t agreement. They were people waiting for the meeting to end.
Most of us call this reading the room at work, and most of us treat it as a gift you either have or you don’t. That’s a convenient story, and a wrong one. Reading the room is a skill, and like any skill it runs on a loop you can practice. The catch is that almost every guide teaches the easy half, notice the cues, then stops right before the part that actually makes you better. This guide walks the whole loop, including the step nearly nobody takes.
Reading the room isn’t a talent, it’s a loop you can practice
Before anything else, name the four steps, because the loop is the whole method:
- Catch a cue. Something shifts: a posture, a tone, a word, a silence.
- Hold two or three readings. Resist the first meaning that jumps to mind and ask what else the same cue could be.
- Make one small move. Something low-risk that tests a reading without putting anyone on the spot.
- Check afterward. Find out whether you read it right, then carry that into the next meeting.
Steps one through three happen live. Step four happens after, and it’s the one almost everyone skips.
None of this requires a sixth sense. Reading the room is emotional intelligence applied in real time, and Daniel Goleman’s research on what makes a leader frames social awareness as a learnable competency, not a gift some people are simply born with. If you’ve read our piece on social perceptiveness, treat that as the trait deciding which cues reach you at all. This post is about the ten seconds after one does.
The visual cues, and what to do when you spot one
Bodies say things before people do, but a body never says only one thing. The mistake is jumping from a posture to a conclusion. The fix is to hold the alternatives and let a small move settle it.
| Cue | Could mean | Your move |
|---|---|---|
| Crossed arms, closed posture | Disagreement they’re holding back, or feeling cold, or just how they sit comfortably | Ask an open question that invites the objection: “What’s the strongest case against this?” |
| Leaning back, out of the conversation | Checked out, or thinking hard, or deferring because it isn’t their call | Bring them in with a low-stakes question tied to their area |
| Laptop open, eyes down, no eye contact | Multitasking, or taking notes on exactly what you said, or avoiding being called on | Offer to send the summary so they can close the laptop, or ask if now’s a good time |
| Fidgeting, glancing at the clock | Bored, or anxious about a hard stop, or just physically restless | Name the clock: “We’ve got ten minutes, anything we’re missing?” |
Notice that not one of those readings is certain. Crossed arms in a cold conference room mean the person is cold. The same posture from someone who’s argued with you twice this month means something else. Personality and culture move the baseline too, so the read is always a starting hypothesis, never a verdict.
That’s why the move in every row is a question, not an accusation. For the background on why these signals carry so much weight, see our piece on why nonverbal communication matters at work, and if you’re the one sending confusing signals, the body language mistakes managers should avoid is the other half of the same skill.
The vocal cues: what tone and pace signal
Tone carries what words hide. A flat, monotone “sounds good” might be genuine ease, or quiet resignation, or someone who mentally left three topics ago. You won’t know from the words, so ask them to say the plan back in their own terms and listen for whether the energy matches the answer.
Rising pitch and a quickening pace can read as excitement. It can just as easily be nerves about being challenged, or someone talking themselves into a position they don’t fully hold. Slow the tempo yourself and ask one concrete question. Real conviction answers it without speeding up.
A long pause after you ask something is the most misread cue of all. It could be careful thinking, or reluctance, or diplomacy while they pick words that won’t start a fight. Don’t rush to fill it. Count to five in your head, and if it still feels heavy, make it safe to answer: “Take your time. I’d rather hear the real answer than a quick one.”
The verbal cues: what word choice gives away
Word choice leaks the things people won’t say outright.
Hedging is the first tell. “I guess that works,” “maybe,” and “if that makes sense” can mean genuine uncertainty, or a disagreement they don’t feel safe stating plainly, or just a verbal habit with no weight behind it. Ask what would turn their “I guess” into a firm yes, and you’ll find out which one you’re dealing with.
Over-qualified agreement is the opposite tell. When a minor point gets “yeah, totally, great point, love it,” the enthusiasm might be real, or it might be a polite way to close the topic and move on. A quick “what would you change if it were yours?” separates the two.
Then there’s the pronoun shift, when “we” quietly becomes “you.” “We should ship this” turning into “when you ship this” can be a clean handoff, or it can be someone stepping back from a decision they no longer stand behind. Name it lightly: “Sounds like this became mine somewhere. Are we still on the same page?” Word choice often carries unspoken conflict, which is why our guide on emotional intelligence in conflict resolution pairs well with this one.
The silence cues: what an unequal conversation is telling you
Who talks and who doesn’t is data most people ignore. If two voices run eighty percent of the meeting, the quiet majority isn’t automatically on board. Silence could mean consent, or it could mean they gave up trying to get a word in, or it could mean they disagree and decided the fight wasn’t worth it.
The tempting move is to call out the quiet, and it’s the wrong one. “You’ve been quiet, what do you think?” puts someone on the spot in front of the room and usually gets you a safe non-answer. Give them a real opening instead: a specific, easy question inside their lane. “Nora, you ran the last migration. What broke that we should watch for here?” That hands the quiet person something concrete to say and signals you actually want the answer, which is active listening in practice rather than a spotlight.
Reading the room on a video call is a different skill
A video call strips out most of what you’d normally read. The glance between two people, the person who shifts in their seat when a topic lands, the energy in the corner of the room, all gone. You get a grid of faces and a lot of missing signal, and the cues that survive are easy to misread.
Three things break specifically on video:
- Audio lag looks like hesitation. A half-second delay before someone answers can read as doubt when it’s just the connection. Don’t score a laggy “yes” as a reluctant one.
- Camera off is a multi-reading cue. It could mean disengagement, or back-to-back-meeting fatigue, or a noisy kitchen, or a bad-hair morning. On its own it’s evidence of nothing.
- Everyone’s looking slightly away. The camera sits above the faces, so genuine eye contact is impossible by design. The usual “they won’t look at me” read means nothing here.
Bailenson’s Stanford research on the four causes of Zoom fatigue explains part of the problem: a close-up grid of faces and a constant view of yourself tax attention in ways an in-person meeting doesn’t. A team that looks flat on video may just be worn down by the medium, not by your idea.
The move that works remotely is different too. In a room you might pull a quiet person in live. On video, a cold call-out often lands harder because everyone is watching one spotlighted rectangle. A low-stakes async check-in afterward beats it: a short direct message like “you seemed a bit quiet on the pricing thread, anything on your mind?” gives them room to answer honestly without an audience.
The step nobody takes: checking whether your read was right
The step that separates people who actually get better from people who just accumulate meetings is checking whether your read was right. Almost every guide ends at “notice the cues,” and noticing without feedback is just rehearsing your guesses. You have to close the loop.
Three ways to check:
- Ask, directly and specifically. Not “was that okay?” but “I read the room as lukewarm on the timeline, did I get that right?” Specific questions get honest, specific answers.
- Check with a trusted peer who was there. “Did Sam seem on board to you, or was that just me?” A second set of eyes catches the blind spots you can’t see from inside your own head.
- Write your read down and compare later. Jot “I think Dana disagreed but didn’t say it” right after the meeting. Two weeks later you’ll know whether you were right, and your calibration sharpens either way.
This is where self-awareness does the heavy lifting, because the pattern you most need to catch is your own tendency to hear what you hoped for. Our piece on self-awareness at work covers that wider habit. And it’s well-founded: Judith Hall’s decades of research on nonverbal accuracy show that reading cues accurately is measurable and trainable, though her full review sits behind a journal paywall.
This is also where Merlin fits, and it’s worth being precise about how. Merlin is Risely’s AI coach, and it lives inside Slack and Microsoft Teams as an after-meeting debrief partner. To be clear about what it does not do: Merlin does not watch, join, or analyze your meetings live. Nothing listens in. What it does is help you replay a moment cue by cue once the meeting is over, so you can see the reading you jumped to and the pattern in your own misreads. Over a few weeks, that replay is how guessing turns into a real read.
For ICs it’s about when to push; for managers it’s team temperature
The same read points you toward different decisions depending on your seat.
If you’re an individual contributor, reading the room is mostly about timing your own voice. You catch that the room has cooled on your proposal. The question is whether to push now, while you still have the floor, or let it go and follow up in a 1:1 where the real objection is easier to surface. Choosing between those is exactly the kind of decision that emotional intelligence sharpens, and our guide for individual contributors goes deeper on making your read count without formal authority.
If you’re a manager, the read is about team temperature, and your misreads compound. Take a quiet nod as agreement and move on, and you don’t just misjudge one moment. You build a plan on a decision half the room never actually made. Probing a lukewarm room costs you two minutes. Skipping it can cost you a quarter.
Debrief the moment you’re least sure about
Reading the room gets better the way any skill does, through reps with feedback. After your next meeting, pick the one moment you’re least sure about, the nod you couldn’t read or the pause that felt heavy, and debrief it before you decide what it meant. Talk it through with Merlin in Slack, Teams, or the web app: replay the cue, lay out the two or three things it could have meant, and choose your next move on purpose instead of on instinct.
Want to go wider first? Assess your emotional intelligence to see where your read of people already lands, or work through the active listening toolkit for the drills that sharpen the live half of the loop. The cues were always there. This is how you stop finding out a week too late.