👋 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 minute twelve of a fifty-minute meeting and you've got the thing. It's good. It's actually the thing nobody in the room has said yet. You just want to tidy it up a bit so it comes out right.
Minute nineteen: someone else says about two-thirds of it, worse, and everyone nods.
Minute fifty: you're making tea, delivering the full polished version to yourself, and it is genuinely better than what they said, and it does not matter even slightly.
What's actually going on
You've probably decided this is a confidence problem. I don't think it is, mostly.
Watch what the people who talk a lot are actually doing. They're not delivering finished thoughts. They're thinking out loud — starting a sentence before they know how it ends and steering it while it's already moving. A decent chunk of what they say is wrong, and they correct it themselves three sentences later, and nobody holds it against them, because that's what the room is for.
You're doing a different thing. You're drafting. Writing the sentence in your head, checking it, cutting the weak clause, checking again that it doesn't sound stupid — and then submitting it.
Those are two different activities, and only one of them fits inside a meeting.
That's the whole gap. It isn't that they're sharper. It's latency. They're running at conversation speed because they've offloaded the thinking into the talking; you're running at writing speed because you're doing the thinking first, in private, to a higher standard than the format requires.
And here's the mean part. A good thought delivered late arrives worse than a rough one delivered on time. At minute twelve, your half-formed version steers the discussion — it's cheap, it's part of the flow, someone builds on it. At minute thirty, the exact same words are a rewind. You're asking eight people to go back. So now it does have to be brilliant, because you're spending everyone's time to say it. Which makes you edit harder. Which makes it later.
The other thing, and I think this is the one people genuinely don't notice: you're waiting for a gap, and there is no gap. Silence in a meeting isn't an invitation. It's someone breathing in. The people who get to speak aren't luckier with timing — they start on the in-breath, before it's fully quiet. If you're waiting for a clean, unambiguous, obviously-yours window, you can sit through an entire hour without getting one and conclude afterwards that nobody let you in.
So what do you actually say?
Claim the floor before the thought is finished.
The move is to spend your thinking time out loud instead of before. Which sounds horrifying, so you buy the first few seconds with a phrase that requires no content at all:
"Can I jump in on that one?"
That's four seconds of runway, and in those four seconds you form the sentence you were going to form anyway. You never needed to be finished. You needed to not be silent while you finished.
Label it half-formed and it stops having to be right.
"Half-formed thought — is this the same problem as the thing with the billing sync?"
Two things happen there. The label sets the terms: you've told the room this is a draft, so nobody's grading it as a conclusion. And it's a question, which is a complete contribution even when your opinion isn't ready — it moves the discussion without requiring you to be correct about anything.
That second part matters more than it sounds, because most of the reason people stay quiet is that they're waiting to have an answer. You almost never need an answer. Naming the thing everyone is circling is a contribution: "Are we deciding this now, or are we working out who decides it?" has saved more meeting-hours than any opinion I've seen delivered.
Say something in the first ten minutes. Anything.
Not a good thing. Any thing. "Can we go back one slide?" counts.
The mechanic is that the room builds a model of you early — participant or audience — and every minute of silence after that raises the price of your first sentence. At minute three, speaking is nothing. At minute forty, speaking means visibly changing category in front of everyone, which is a far bigger move than the one you were avoiding. People read your first contribution as your register for the meeting. Nobody notices the second one at all.
And the one that does the most work: get in before the meeting.
One line to whoever's running it, the day before: "I've got a thing about the migration — want me to raise it, or is that not this meeting?"
Now you're expected. Being expected is most of being able to speak, because the hard part was never the sentence — it was granting yourself permission to take the room's time, and someone else has now granted it for you. And maybe a third of the time you'll get back "oh, we actually settled that on Friday," which saves you the entire ordeal.
One thing that's new this year
If your company runs an AI notetaker — and most do now — something is true that wasn't a few years ago. The summary lists decisions, owners, and who raised what. It gets skimmed by people who weren't there. It is the version that survives.
Which means the mediocre thing you said out loud at minute twelve is in the record, and the excellent version you sent in a DM afterwards isn't. I'm not thrilled about that either. But it's an argument for the cheap early sentence, not against it.
Worth knowing the other half: those summaries get attribution wrong reasonably often, and there's no appeals process. So if something genuinely needs to be yours, a comment on the doc beforehand is more durable than a spoken line — it's timestamped, it's written down, and it's still there when the transcript decides someone else said it.
Where this backfires
If you're the most senior person in the room, invert all of it. Speaking early doesn't make you a participant, it closes the question — you'll get agreement instead of opinions and you won't be able to tell which one you got. Your version of this is to go last, and to leave a silence long enough to be uncomfortable, and then to hold it, because the useful thing in that room isn't coming from you.
Second: don't do it to be seen doing it. Talking to appear engaged is one of the most legible things a person can do — nobody can prove it, everybody clocks it. If you speak early and it's filler, you've just spent the credibility you were trying to build. "Any thing" means any real thing. "Can we go back a slide" is real. Confidently restating what the last person just said is not.
Third, and this one depends entirely on the room: in some teams, and in some cultures, jumping in is straightforwardly rude, and the actual protocol is the raised hand, or the chat, or waiting to be asked by name. Advice about interrupting is mostly written by people who work in rooms where interrupting is free. Spend one meeting watching how contributions actually get in — that's a real thing to do with a meeting — then use that door instead of this one.
The part that isn't fair
Interrupting is not equally priced.
The same jump-in reads as decisive from one person and rude from another, and it has very little to do with the sentence. If you're the only junior in there, if you're dialled in while five people share a room, if you're the only woman at the table, if you're working in your second language — you are paying more per interruption than the person next to you. Every article that says "just speak up more" is quietly assuming your price is the same as the author's.
The remote one is partly literal, which I find weirdly comforting. A few hundred milliseconds each way means you physically cannot land in a pause — by the time the silence reaches you and your voice gets back, the room has moved. You're not being hesitant. You're behind by a measurable amount of time.
Two honest responses to that. The first is that whoever runs the meeting can fix it in one sentence — "let's go round" or "hang on, Sam had something" — and most of them will, if you ask once, privately, in plain words: "I keep getting talked over on the call. Could you come to me by name?" That's not a complaint, it's a request with a mechanism, and it's much easier to say yes to.
The second is that writing is a legitimate route and not the consolation prize. A comment on the doc lands in the room whether you speak or not. Some people are simply better in writing, and building your influence around that is a strategy rather than a surrender. The trap is that it only works before. The same paragraph posted after the meeting is a note. Posted the night before, it's the agenda.
And the last uncomfortable thing, which took me a long time to see: a lot of decisions weren't made in the meeting at all. Two people talked on Tuesday, and the meeting is where it gets said out loud with everyone present. If you keep bringing good arguments that don't move anything, you may not be bad at meetings — you may be arriving at the ratification. The room to change it was the conversation before it, and getting into that conversation is a different skill entirely. One for another week.
Monday
Next meeting you're in, say something in the first five minutes.
It does not have to be good. A question counts. "Can we go back one slide" counts. You're not trying to contribute yet — you're changing category from audience to participant while it's still cheap.
Then for the meeting after that one, send the line the day before: "I've got a thing about X — want me to raise it, or is that not this meeting?"
That's the whole practice. You don't need to become more confident. You need to stop editing and start talking at the same speed as everyone else in the room.
🚀 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:
- ⭐ GitHub — follow me and star the projects: github.com/parsajiravand
- 💬 Discord — join the frontend best-practices community: discord.gg/d9KRhuAwQ
- 📸 Instagram — frontend best practices, daily: @bestpractice___
🤝 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.
Top comments (0)