Airtime

In a meeting, silence doesn't read as depth. It reads as absence. The person who said nothing was functionally not there.

The misconception: silence = rigor

Technically strong engineers are often the quietest people in the room, and they have principled-sounding reasons for it. They only speak when they have something rigorous to add. Talking to be seen feels like performing. The people who talk the most seem to be optimizing optics over substance, and nobody wants to become that person.

Every one of those instincts is individually reasonable, and the aggregate result is a career problem. Because here is what actually happened in that meeting, from the organization's point of view: you weren't there. You had the correct analysis in your head — you'd spotted the flaw in the migration plan before the presenter finished slide two — and it influenced nobody. Unspoken analysis has zero organizational weight. It is exactly as useful to the meeting as the analysis of someone who skipped it.

The mistake is treating a meeting like a code review, where the artifact speaks for itself. In a meeting there is no artifact. There is only what got said, and who said it.

The mechanics: meetings are where judgment is observed

Why does airtime matter so much? Because meetings are the org's primary instrument for observing judgment.

Your judgment displayed in a code review is visible to three peers. Your judgment displayed in a cross-org design review is visible to the people who decide promotions, staffing, and who leads the next big thing (see Be In The Room — but being in the room is only step one; you also have to be audible in the room). Managers and senior leaders spend most of their day in meetings. That is their sample of you. If your sample is silence, their model of you is built entirely from other people's descriptions of your work — which means your reputation is being written by whoever does speak.

Speaking also stakes your claim on ideas. If someone says the thing you'd already concluded and you nod silently, the idea is now theirs. Provenance in meetings is assigned by utterance, not by who thought of it first — a close cousin of Cookie Licking: Claiming Work Without Doing It, except here the claim is legitimate: whoever voices the idea in front of the deciders owns it. Silent agreement is a donation.

This is the same mechanism as legibility-beats-reality: the org can only act on what it can see. A meeting is a legibility device. Opting out of speaking is opting out of being legible.

The compounding cost

The damage isn't per-meeting; it compounds through labels.

Calibration and talent-review discussions run on compressed labels, not transcripts. "Quiet in meetings" gets compressed — over dozens of meetings and a couple of review cycles — into "not strategic," "not leadership material," "solid but heads-down." Notice what happened: a label about thinking style got applied as a verdict on thinking quality. Nobody in the room can counter it with "actually, his silent analyses are excellent," because nobody has ever seen them.

Once attached, reputation labels are sticky and self-reinforcing: the "not strategic" engineer stops getting invited to strategic meetings, which removes the only venue where the label could be disproven. The cost of silence isn't the meeting you were quiet in. It's the meetings you stop being invited to.

How to get airtime with substance

The good news: you don't have to become the person you dislike. The goal is a high signal-per-word ratio, not volume. Five specific moves:

Speak early. The first few minutes of a meeting establish who is "in" the conversation. An early, small contribution — a clarifying question, a framing observation ("before we dive in, is the constraint here latency or cost?") — costs almost nothing and buys you a seat. Breaking in at minute 40 against established momentum costs ten times more, which is why people who don't speak early usually don't speak at all.
Ask the sharp question. A well-aimed question is high-signal airtime that doesn't require having the answer — which removes the perfectionist's usual excuse. "What happens to in-flight requests during the cutover?" can reshape a whole design discussion in one sentence. Questions are the cheapest rigorous contribution that exists.
Summarize and name the decision. "So we're choosing X over Y because Z — is that right?" The summarizer is remembered as the person who drove convergence, even though they added no new content. This move is almost always available, almost always valuable, and mysteriously unclaimed in most meetings.
Prepare one substantive point. For any meeting that matters, if you know the agenda you can pre-think one point worth making — and walk in already knowing what you'll say instead of hoping rigor strikes live. This is the lightweight version of the meeting-before-the-meeting: the work happened before the room, the room is where it becomes visible.
Claim your idea when it's restated. When someone re-voices the thing you proposed earlier, respond immediately and politely: "Right — that's the approach I proposed earlier; to build on it..." Immediately matters. Provenance resets fast, and a correction two days later reads as pettiness while a correction in the moment reads as continuity.

Remote and hybrid nuances

Remote meetings raise the price of silence: there's no body language to signal engagement, so a silent square is even more absent than a silent chair. Camera on is baseline. Chat contributions count and are better than nothing — a sharp question typed into chat still registers — but spoken beats typed, because chat scrolls away and voices don't. If you dropped a good point in chat and it got skipped, unmute and say it.

And the guardrail on all of this: airtime without substance is discounted fast. People keep a running signal-per-word estimate on everyone, and the engineer who talks constantly with nothing to say burns credibility every time they unmute. You are not trying to match the loudest person's word count. You are trying to make sure your actual judgment enters the room, out loud, attributed to you.

Diagnostic test

If someone who only attends meetings with you were asked to describe your judgment, could they — or would they have to admit they've never heard it?