Let me tell you about Raj.
Raj is a mid-level developer. Solid coder. Ships clean work. Never misses a deadline. But Raj has a secret fear. It keeps him up at night. It's not production bugs. It's not technical debt. It's not even the legacy PHP codebase that everyone pretends doesn't exist.
It's the calendar invite.
Specifically, the calendar invite that arrives at 4:47 PM on a Thursday, titled something vague like "Quick Chat: Next Steps on the Dashboard Refresh."
Raj stares at it. His cursor hovers over "Accept." His heart rate increases slightly. Who else is on this invite? He checks. There are 14 people. Fourteen! That's not a quick chat. That's a small wedding.
But here's the thing. Raj doesn't want to go. Raj has three PRs to review and a database migration that's slowly eating his afternoon. He knows, deep in his gut, that this meeting will be a 45-minute discussion about whether the "Refresh" button should say "Refresh" or "Update." A decision that could have been a Slack message. A decision that will probably be reversed next sprint anyway.
And yet, he clicks "Accept."
Why?
Because of Meeting FOMO.
The Disease We Don't Talk About
We joke about useless meetings. We share memes about "this could have been an email." We nod sagely when someone says "meetings are where work goes to die." But we still attend them. All of them. Religious. Like showing up late to a family function you didn't want to attend, but you go anyway because you're scared of what your aunt will say about you behind your back.
In tech, that aunt is your career.
Here's what actually runs through Raj's head when he sees that 14-person invite:
"If I decline, will people think I'm not a team player?"
"If I'm not in that room, will they make a decision about the dashboard that affects my work without my input?"
"Will someone mention my project while I'm not there? Will I lose ownership?"
"Will the Product Manager notice I'm absent and think I'm disengaged?"
"If I skip this, will I miss the one moment where the VP says something actually important? Like a reorg? A new tool? A free lunch?"
So he accepts. And at 2:00 PM the next day, he sits in a stuffy conference room (or a pixelated Zoom grid), silently dying inside while two senior engineers argue about button labels for the third time this quarter.
He contributes exactly one sentence: "Looks good to me."
And he leaves the meeting 47 minutes older, with no new information, three unread Slack messages, and the database migration still waiting for him.
The Real Cost of Showing Up
Here's what we rarely admit: the cost of Meeting FOMO isn't just wasted time. It's the mental load of recovery.
You don't just lose 47 minutes in that room. You lose another 20 minutes afterwards trying to remember what you were doing before you went in. You lose the flow state. You lose the deep focus that writing good code requires. You lose the will to live (slightly).
The meeting ends at 2:47 PM. By the time you've gone to the bathroom, refilled your water bottle, answered those three Slack messages, and opened your IDE again, it's 3:15 PM. You have maybe an hour and a half of decent work left before your brain starts feeling like scrambled eggs.
And for what? So Raj could say "Looks good to me" in front of 13 other people who also didn't want to be there?
The Magic Question
Here's what I've started doing. It's dangerous. It's radical. It might get me fired. But it works.
Before I accept any meeting invite with more than 6 people, I ask myself one question:
"If this meeting happened without me, would I care about the outcome?"
Not "would I be curious?" Not "would I have opinions?" But would I care?
If the answer is no, I decline.
Here's the script I use:
"Hey, thanks for the invite! I think this one might be better suited for [Project Lead] to weigh in on. I don't have much to add on this particular topic, but I'd love to see the notes afterwards. Let me know if there's anything specific you need from me."
That's it. That's the whole thing.
Nine times out of ten, the organizer replies with "No problem! I'll share the notes." And guess what? The notes never mention anything about the dashboard refresh. Because nothing was decided. Because it was a status update disguised as a decision meeting.
And Raj? Well, Raj still attends every meeting. He's still terrified. He still thinks showing up is the same as contributing.
But he's starting to notice something. The people who get promoted aren't the ones in every meeting. They're the ones who ship work between meetings. The ones who have time to think. The ones who protect their calendar like it's their last remaining brain cell.
And slowly, very slowly, Raj is learning to let go.
The Takeaway:
Your presence is not your contribution. Sitting in a room while other people talk doesn't make you valuable. It makes you furniture.
The next time a vague calendar invite shows up in your inbox, resist the urge to panic-accept. Ask yourself if you'd care about the outcome. Ask yourself if the meeting has an agenda. Ask yourself if the same information could be shared in a two-paragraph Slack message.
And then, if you're feeling brave, decline.
Your database migration will thank you.
Top comments (0)