👋 I'm Parsa Jiravand — I work in IT, and this is Best Practice. One article every day, one soft-skills episode every week. It all lives at bestpractic.org — come join us.

It's your second week owning the Tuesday planning sync, and forty minutes in, you notice the same two people have already agreed on the answer — you can see it in how they're not really asking each other questions anymore, just confirming — and everyone else is still taking turns giving their opinion like it's a vote that hasn't happened yet. You called this meeting. You're supposed to be running it. And you have absolutely no idea what to do with what you just noticed.

That's the actual job, and nobody tells you it's the job, because the invite just says "owner."

It's not the same skill as talking in one

You can be the person who speaks up well in a meeting — lands a point, asks the sharp question at the right moment — and still have no idea how to run one, because they're not the same muscle. Speaking in a meeting is about contributing to a conversation that's already happening. Running one is about deciding when the conversation is actually over, which is a much weirder thing to have to call.

Most meetings get decided before they start. Not maliciously — just structurally. Two people talk in a thread, or in the hallway, or on a call that wasn't this one, and by the time the room convenes, there's already an answer; the meeting itself is where that answer gets performed back as if it's being discovered live. Everyone plays along, partly out of politeness and partly because nobody wants to be the one who says "didn't we already decide this."

Your job, once you're the one running it, is to notice that moment and do something about it instead of letting the room keep performing.

The second audience nobody mentioned

There's a newer wrinkle on top of the old one. A lot of these meetings now have something else in the room besides people — a note-taker that's actually a model, quietly producing a transcript and a summary afterward. More people are skipping the meeting entirely and reading that summary instead, trusting it to carry the parts that matter. Which means the thing you're running isn't just for the people in the call anymore. It's also, increasingly, for whoever reads the write-up tomorrow and never heard the tone, the hesitation, the "well, I guess" that told you someone wasn't actually on board.

That changes what's worth saying out loud. A decision that only lives in the room's collective memory doesn't survive contact with a transcript built by something that can't hear hesitation. If it matters, it has to get said plainly enough to survive being summarized by a machine that wasn't paying attention to anything except words.

So what do you actually say?

Three moves, and all three are just different ways of naming the gap between what's being performed and what's actually true.

When you notice the room has converged and is still going through the motions: "I think we've converged — can I read that back as the decision?" Say the decision in one sentence. If nobody corrects it, the meeting is over, whatever's left on the agenda. If someone does correct it, good — you just found out it wasn't actually settled, which is useful information you didn't have thirty seconds ago.

When you suspect the question isn't really live anymore, and you want to check before you cut it off: "What would change your mind right now?" If the answer is a real thing — a number, a person's opinion, a test result — it's still open, keep going. If the answer is a shrug or a restatement of the same position, it was decided before you walked in, and you can say so without it being a jab at anyone.

When there's a side conversation happening in the room that's really a two-person problem wearing a group meeting as a costume: "Let's take that offline, the two of you, and bring back a recommendation." This does two things at once — it stops the rest of the room from sitting through a negotiation that isn't theirs, and it gives the two people involved somewhere to actually finish the thing instead of circling it in front of an audience.

And for the transcript problem specifically: "I'm going to say the decision out loud so it's actually in the notes, not just in our heads." It sounds almost silly to announce, but it's the sentence that turns a vague paragraph in tomorrow's AI summary into an actual decision someone can point back to in a month.

Where this goes wrong

Naming "I think we've converged" works when you have some standing to call it — when you're the one who convened the meeting, or you're a peer to the room. It does not work the same way when your manager, or your manager's manager, is in that room and the thing you'd be naming is that they've already decided something and are letting everyone else perform catching up to it. Say that sentence in that room and you're not running the meeting anymore, you're correcting someone with more leverage than you, in front of witnesses, and that's a different and much riskier act than the same sentence said to a group of peers. If you're junior and the decision-makers outrank you, the honest move is usually to ask the "what would change your mind" question privately, afterward, not to call the room out in it.

The transcript sentence has its own failure mode too — it can read as performing for the record rather than talking to the people in front of you, especially if you say it every single time. Use it when the decision is actually the kind that gets argued about later, not as a tic.

The part that isn't about skill

The person who ends up running these meetings is very often not the most senior person in the room — it's whoever's most organized, or whoever volunteered once and it stuck. That's worth saying plainly, because running a meeting well functions as leadership — you're the one deciding what counts as decided — but it doesn't always get recognized or compensated as leadership, especially if you came into the role sideways instead of through a title. You can do this job extremely well for a long time and have it read as "good at logistics" rather than "good at judgment," which is the same skill wearing a less flattering name.

And there's a quieter politics now too, with the note-taker in the room: who gets to see the raw transcript, whether it gets cleaned up before it's shared, whether someone's half-finished sentence becomes part of the permanent record of what they think. Nobody puts that in the meeting invite, but if you're the one running it, you're also, a little bit, the one deciding what gets to count as having been said.

Monday

Before your next recurring meeting, write down — just for yourself, two minutes, before anyone joins — which items on the agenda are actually open questions and which ones you already suspect are decided. Then say that split out loud at the top: "I think the first two are real decisions, the third one I suspect is already settled — tell me if I'm wrong." You're not performing authority. You're just telling the room what kind of meeting it's about to be, instead of making everyone find out the slow way.

📚 Read next

🚀 Want more like this? Every guide, playground, and quiz lives on bestpractic.org — open it and sign up free so the next one finds you.

Thanks for reading! Let's stay connected:

🤝 Want to make something with us? Write a piece, come on the podcast, or bring an idea that should exist — bestpractic.org/collaborate.

And if this one helped, send it to the person you know who needs it this week. That's what keeps these coming.