Talking more in a meeting gets you noticed. It does not reliably get you credit for what you said.
Most advice written for quiet individual contributors, the engineers, analysts and designers who are not naturally the loudest voice in a room, treats those as one problem and gives one answer: talk more. Sometimes that’s the right fix. Often it isn’t, because being heard in the room and having your name still attached to the idea a week later run on different mechanics. The first happens live and fades. The second happens after everyone has logged off.
This piece is about the second one.
Why the loudest person in the room gets remembered as the smartest one
The finding has a name and a paper. In 2020, Neil MacLaren, Francis Yammarino and colleagues at Binghamton University published Testing the babble hypothesis in The Leadership Quarterly. They measured how long each person spoke in small groups, then asked the group who its leader was. Speaking time predicted the answer, and it kept predicting it after they controlled for intelligence, personality, gender, and the fact that people who already look like leaders tend to talk more in the first place. Quantity of speech, not quality of it.
A more recent study moved the test onto video calls. Michael Johnson at LSU put 198 students into 38 teams running a Mount Everest simulation over Zoom, recorded the calls, and measured the exact proportion of time each person spoke. Objective speaking time had a direct positive effect on who got nominated as leader. That work re-examines the older finding rather than originating it, and the university’s write-up names no journal for it.
How lopsided does airtime get? Psychology Today reports a figure from status research: in a three-person group the highest-status member controls about 47 percent of the talking time, the second about 30 percent, and the third about 23. The underlying source is Correll and Ridgeway’s 2006 chapter on expectation states theory.
What we see when quiet ICs first try to fix this
When quiet ICs first try to be heard in meetings, we see the same pattern: they speak up more, but they don’t write any of it down.
They come out of a planning call having said three useful things, and by Thursday the doc has someone else’s name on the section they described out loud on Tuesday. The advice worked. They were audible. Nobody wrote the audible part down, including them.
Speaking is the half of this that feels like it takes courage, so it’s the half that gets the effort.
The rest of this post assumes you already talk in meetings. If getting the first sentence out is your harder problem, this isn’t the piece for that; why people freeze or ramble out loud is.
Five ways to convert airtime into credit while you’re still in the room
Each of these is about placement rather than volume. These are placement moves for an ordinary meeting; if the problem is a person talking over you or repeating your idea as their own, the word-for-word replies are in assertive communication scripts.
1. Let the strongest voice open, then name what it left out
“That covers the API contract. It doesn’t cover what happens if the vendor changes the rate limit mid-migration.”
Dana said that about nineteen minutes into a planning meeting, after a staff engineer had spent eight of them laying out an approach. (Dana is illustrative, a composite of people we’ve coached.) She had said almost nothing before it. What she said was the single condition his framing didn’t cover, and it was the sentence the room argued about for the next ten minutes.
This is the cheapest move on the list because it costs the fewest words. The senior voice does the work of building the frame. You do the work of finding its edge. The edge is usually a dependency someone outside the room controls, a failure case nobody priced, or a date that only holds if something else lands first.
Dana had been trying to be more visible for two months before this, mostly by agreeing loudly and early, which did nothing at all. Her hit rate on the move is not high. It doesn’t need to be.
2. Say the decision back, once, before the meeting moves on
“So we’re going with the phased rollout, EU region first. Is that the call?”
Nineteen words. Somebody in every meeting has to convert a discussion into a decision, and in most meetings nobody volunteers, so the thread just stops and everyone leaves holding a slightly different version of what was agreed.
Be the person whose sentence becomes the record. That takes having tracked the conversation, and it takes saying it before the room moves to the next agenda item, which is the harder half. Ninety seconds later the same sentence reads as re-litigating.
3. Attach your name when you first say the idea, not after someone repeats it
Two openings for the same idea.
Ownerless: “What if we tried batching the writes?”
Owned: “I want to flag batching the writes. Here’s the case for it.”
Neither is louder. The owned one is harder to pick up and carry off without the name attached.
There’s evidence for how far apart contribution and credit can drift, though it comes from scientific authorship rather than meetings. Ross and colleagues, publishing in Nature in 2022, analyzed research teams and found women were 13 percent less likely than men to be credited as authors on the resulting papers, and 58 percent less likely to be named on patents, after accounting for role, research experience and time spent on the project.
4. Ask the question that reframes, not the one that agrees
Don’t: “Does that make sense to everyone?”
Do: “Are we optimizing for speed to launch or accuracy of the numbers? The last two decisions point in different directions.”
The first asks the room to confirm it was paying attention. The second tells the room what it just did without noticing. Only one of those gets repeated by somebody else later.
The reframing question only works if you were tracking the whole conversation instead of waiting for your turn, which is active listening rather than confidence. It’s also the move most likely to go badly in a tense room, because “the last two decisions point in different directions” is an accusation when the person who made both is sitting there. Say it about the decisions. Never about the person who made them.
5. Ask for the floor, but only when it’s earned
It worked once like this. A product analyst waits until a scoping call is thirty seconds from ending on the wrong assumption, says “Can I jump in, thirty seconds,” and spends them on one sentence about a data dependency. The call ran four minutes over and the scope changed.
Then it stopped working. Over the following weeks she opened with “can I jump in” in nearly every meeting, including standups, including ones where the point could have waited until Slack. By the third week people expected it, and one manager started calling on her last on purpose.
The move runs on scarcity and on pacing. A one-sentence interruption at a genuine decision point reads as a contribution. The same words delivered fast, or without a clear finish, or at a moment when nothing is being decided, read as an interruption and get filed that way. The distance between those two outcomes is mostly oral communication, the pacing and the landing, rather than nerve.
Use it more than once or twice a month and it stops being a move. It’s just how you talk in meetings.
When speaking up more in meetings is the wrong move
Three cases where the five moves above are the wrong thing to be working on.
Some ICs already talk plenty. Airtime was never their constraint, and their credit problem sits somewhere else, usually with whoever runs the meeting or writes the notes. Nothing above touches that.
Some teams run on writing. Design docs, RFCs, decision records, review comments. On those teams meeting airtime was never the lever, and the person who reads every RFC properly and comments on Thursday is more visible than the person who talked for six minutes on Tuesday. If that’s your team, written collaboration is where the effort pays, and most of the five are close to irrelevant to you.
And some rooms have one dominant senior voice. Competing for airtime there from a first- or second-year seat starts a status contest a first- or second-year IC does not win, and losing it in front of everyone costs more than staying quiet did. Skipping three of the five is a fair read of that room.
What happens to all five in the twenty minutes after the meeting ends
Everything above happens out loud, and out loud has a shelf life of about a day.
Nobody reconstructs a meeting accurately from memory. Whoever writes the recap writes it from their own notes, and their notes over-record the people they were already watching. So the gap you named, the decision you closed, the reframe you offered, all of it passes through one person’s memory before it reaches anybody who wasn’t in the room, and it arrives attributed to whoever was already visible. It’s just how note-taking works.
Written airtime behaves the other way around. A message with your name on the timestamp, a comment on the doc, a two-line recap posted in the channel twenty minutes after the call. It’s searchable in November. It gets quoted by people who weren’t in the meeting. It survives your manager changing.
Each of the five has a written version.
The gap you named goes on the planning doc as a threaded reply, not just into the air.
The decision you said back goes into the channel as a line with your name on the timestamp.
The idea you attached your name to gets a written trace, a ticket or a comment, that outlives a transcript nobody rereads.
The reframing question, written down, gets quoted. Said aloud, it gets paraphrased into somebody else’s words inside a week, usually by a person who sincerely believes they thought of it.
And the interruption you spent your credibility on becomes one line: “Decision: phased rollout, EU first, because of the vendor rate limit. Flagged by Dana.”
Dana’s line got quoted back at her in a planning review six weeks later. The engineer who usually took notes had left the company, and hers was the only written record of why the sequence was chosen.
Start with the meeting you just left
The fastest thing available to you today isn’t the next meeting. It’s the three minutes after the last one: open the doc, post the line, put your name on the timestamp.
If your visibility problem is wider than meetings, ten ways to be more visible at work covers the rest of it. If the person who needs to see the written trail is your own manager, that’s managing up. Kept up, it’s also part of what gets an IC read as leadership material before there’s a title. And if you want to rehearse one of these before you try it live, Merlin will run the conversation with you first.