You stay quiet in meetings when you know the answer. Let's fix that.
I spent nine years in the Marine Corps. I've been yelled at by people who were very good at yelling. And years later, as a data engineer on an Air Force computer vision project, I still caught myself sitting in a sprint meeting with the right answer in my head, saying nothing, and then listening to someone else say it five minutes later.
That stings. If you've done it, you know exactly the feeling.
Here's what I figured out, and what I actually do about it.
It's not that you lack confidence
I don't believe you build confidence. I believe you unhide it. The version of you that explains a bug fix clearly to a coworker at lunch is the same person who goes silent when the camera is on and the tech lead is listening. Nothing about your skill changed between those two rooms. Something about your filter did.
Your brain has a selective filter called the reticular activating system, the RAS. It decides what you notice out of the millions of things happening around you. It learns from what you feed it. If your past is full of moments where speaking up went badly (a senior dev tore apart your idea, a teacher laughed, a code review got brutal), your filter got trained to scan for threat. So in the meeting, it shows you every reason to stay quiet: the manager's neutral face, the silence after someone else spoke, the chance you're wrong.
The RAS also drives arousal, the physical side. That's the tight chest, the warm face, the voice that feels like it'll crack. That's not weakness. It's a filter doing the job it was trained to do.
The good news is filters can be retrained. You retrain it with new experiences, in small doses, on purpose.
The rep that does the most work: compliment a stranger
This sounds unrelated to standups. It isn't.
Once a day, give one genuine, specific compliment to someone you don't know. The barista, the person in line, the guy at the gym with a good deadlift. "That's a great jacket." Done. Walk away.
Why this works: it's the smallest possible version of the exact thing you freeze on in meetings. You're putting your voice into a space where nobody asked for it. Your body will react the first few times. Then it stops reacting, because your filter keeps collecting evidence that speaking up unprompted is fine, and usually goes well.
That's the first rung of the ladder:
- Quick compliments to strangers
- Light conversation
- Deeper conversation
You move up when the current rung stops spiking your heart rate. Not before.
Bringing it into the meeting
Once the daily reps are going, do these at work.
Speak in the first five minutes. The longer you wait, the bigger the moment gets in your head. Say anything early. "Morning." "I can take notes." "Quick question on the ticket." Your voice is now in the room, and the next thing is easier.
Lower the stakes of what you say. You don't need a perfect answer. Try "I might be off, but I think the timeout is coming from the retry logic." Hedged, useful, and it gets the idea on the table. Being wrong in a meeting costs almost nothing. Being silent costs you the credit, every time.
Write one sentence before the meeting. Look at the agenda and write one thing you'll say. When the topic comes up, read it. Prepared beats brave.
Count reps, not outcomes. Your win is that you spoke. Not that everyone loved it. Track it like a workout. Three meetings this week where you said something is a good week.
What changed for me
On the Athena project, our edge sensors ran a local model. When it flagged something significant, it shipped the context from before, during, and after the event to AWS so the models could keep learning. The system got better because it kept getting fed new examples.
That's the whole idea. Your brain is the model. Every time you stay quiet, you feed it another example that silence is safe and speaking is dangerous. Every time you speak, even badly, you feed it the opposite. Enough examples and the filter flips. The meeting stops feeling like a threat and starts feeling like a place where you have something to add.
You already have the answers. You already have the voice. It's just been hidden under old training.
Your mission this week
- Compliment one stranger a day for seven days.
- In your next three meetings, say something in the first five minutes.
- Write down each rep. Look at the list on Friday.
Then come back and tell me in the comments how it went. Which part was hardest for you?
Top comments (2)
@christopher_jakob_acda8fa Scuba Buba, you strayed too far from the school playground.
It is lunch money time.
Where's your code, Navy-blue Eyes? GH, GL, Berg?
If you give me the repos, I'll let you go.
You'll be able to go back to Castle Chairforce and the My Little Zoomie calls.
When did cadets "cheer" for Navy at an Army-Navy football game?
In 1943, Wartime travel restrictions kept the Brigade at Annapolis when the game was at West Point. As a result of a coin toss, the First Regiment learned Navy songs and cheers, wore white caps to the game, and "helped" Navy beat Army.
I ain't even from the Thirteen Colonies, so I'm not gonna do that favor for you, Scuby Zoom.
Na toir orm a bhith nam Rita Vrataski.
@highflyer910 now imagine, doing this for 2 years, and even after that I get Scuba Gooding Junior from USS Love Cruiser.
What can I even say to this:
And if you think, this is just Chairforce playing Air Cavalry Pony Tales at Fort Pillow...
Then just think about Infantry...
Infantry derives from the Latin word infans, which means a "young child" or "one unable to speak" .
Here's an excerpt from official training materials, United States Military Academy at West Point:
Zero Dark Flirty?! Operation Romantic Sunset?! Shock and Awww Doctrine?!
...
What can I even say?!
...