The phrase has become its own meme: "This meeting could have been an email." Every developer has thought it. Most have said it in Slack. A few have screamed it directly into a Zoom call by accident (unmute button failure). But where did this universal frustration come from, and is there actual data behind it, or is it just developer grumbling? Turns out, the data is worse than the meme, and April Fools' Day might be the perfect time to acknowledge it.
The Meme's Real Origin: Productivity Theater Gone Wrong
The phrase emerged as a meme around 2018-2020, right as remote work was exploding. Before that, developers complained about meetings, but the complaint lived in cubicles and conference rooms. When Slack and Zoom enabled remote work, the frustration became visible, quotable, and spreadable across the internet.
The first documented usage appears across Slack communities, Reddit's r/ProgrammerHumor, and Twitter around 2018-2019. As the pandemic shifted everyone to remote in 2020, the meme exploded. Suddenly, your calendar could be packed with back-to-back Zooms, and you had no face-to-face reasons to break them up. Status updates that should have been a Slack post became 30-minute video calls. "Let's sync up" became code for "let's waste 45 minutes on camera."
By April 1, 2020 (coincidentally, the peak of pandemic lockdown), Noota and other meeting analytics platforms started tracking the phenomenon: too many meetings, not enough focus time, and a productivity crisis that no one was measuring until Zoom was measuring it for them. The data they collected would later justify the meme with hard numbers.
What's remarkable is how quickly the phrase became universal. By 2021, every tech company, every Slack workspace, every developer knew the phrase and felt its truth. It transcended being a joke—it became a legitimate business complaint, supported by research and backed by changing work patterns.
The Data: The Frustration Is Real (And Growing)
Here's where the meme shifts from complaint to indictment: 71% of managers admit that meetings are unproductive. That's not developers being cynical—that's managers saying their own meetings don't work. If managers think their meetings are bad, imagine what the people forced to attend them think.
More specifically: 32% of workers attend meetings they think could have been emails. That's roughly a third of your team sitting in a call they actively resent. For knowledge workers and developers, the number is likely higher. Dev.to surveys consistently show that developers cite "too many meetings" and "interruptions" as the top productivity killers, ranked above insufficient tooling, poor documentation, or bad code.
And the math gets worse: if you have an organization of 100 people and 32 are in meetings they think are unnecessary, and that meeting is 30 minutes, and you're doing this three times a week—that's 1,440 hours per year of meetings that shouldn't exist. That's 360 eight-hour workdays. That's the productivity cost of not writing the email instead. For a company with 1,000 employees, it's 14,400 hours per year. That's 6 full-time engineers' worth of lost productivity, just from unnecessary meetings.
Studies from FlowtRace's collaboration research show that synchronous meetings (even quick ones) destroy deep work. A developer interrupted from focus needs 15-23 minutes to regain concentration. A 30-minute meeting isn't 30 minutes of lost time—it's 30 minutes plus context-switch tax on both sides of the call. So that "quick sync" is actually costing 90 minutes of developer time. If you multiply that across an organization, you're watching productivity collapse in real time.
Why Developers Hate Meetings (It's Not Just Grumpy Introverts)
The stereotype is that developers hate meetings because they're anti-social or anxious. False. Developers hate meetings because they require synchronous time, destroy flow state, and rarely produce more clarity than an async email would. It's not personal—it's mathematical.
Here's what developers actually need to do their best work:
- Deep focus blocks: Interruptions during code work are expensive (literal bugs, lost context, security vulnerabilities). A developer in flow can catch subtle logic errors. A developer interrupted and re-focused might miss them.
- Async-friendly decisions: Most decisions can wait for an email thread and still be made correctly. "Should we use library X?" "Do we need to refactor module Y?" "When should we deploy?" All of these benefit from written, searchable context.
- Optional attendance: A meeting where only half the people need to be there doesn't need all of them there. But calendar invites imply obligation. Email threads are opt-in.
- Clear agendas: Meetings without agendas are just socializing with obligations. Email threads self-organize around the question that needs answering.
- Time zone flexibility: Synchronous meetings assume everyone is awake and available. Email works at 3 AM for night owls, in the early morning for early risers, on weekends for people with split schedules.
Remote work made this visible. In an office, a quick status meeting feels efficient (walk to the conference room, 15 minutes, back to work). On Zoom, that same 15 minutes requires: login, wait for people to join, technical glitches, camera anxiety, and actual recovery time. It's no longer 15 minutes—it's 30 minutes of your day gone, plus the mental fatigue of being on camera.
The meme persists because developers live this calculus every day, and they've learned (correctly) that an email with a clear update, a Slack thread for Q&A, and optional async participation produces better outcomes than a synchronous meeting. They've also learned that saying "this should be async" in a Zoom call is political suicide, so the meme does the complaining for them.
When Meetings Are Actually Necessary (And When They're Not)
Not all meetings are email crimes. Some genuinely need synchronous time:
- Live problem-solving: When you need whiteboard thinking and real-time collaboration (debugging a critical issue, architecting a new system, troubleshooting production).
- Relationship building: One-on-ones with direct reports, team retrospectives, new hire onboarding. Some of this needs face-time (metaphorically, even on Zoom).
- Decision-making with conflict: When people disagree and need to reach consensus through dialogue. Email threads can get heated and circular.
- Brainstorming: When ideas need to build on each other in real time. Though honestly, even this works in Discord or Slack for async teams.
- Sensitive conversations: Feedback, performance reviews, layoffs. Some conversations require tone and presence.
But the meme calls out the meetings that aren't in that list: status updates (which could be a Slack thread or email), information dumps (which could be a document), read-aheads that are just being read aloud (which defeats the purpose of a document), and meetings scheduled for "the sake of regular syncs" (which kill momentum). These are the 32% that could be emails.
Smart teams now run what Dev.to's engineering communities call "meeting audits": asking for each recurring meeting, "Could this be async?" If the answer is yes, it becomes an email or Slack doc. If no one misses it after a month, it stays dead. Suddenly, teams find 3-5 hours per week back in their calendar. That's a full day of productive work, recovered by asking hard questions about synchronous time. Programmer Humor communities document the collective relief when an unnecessary meeting gets cancelled.
The Evolution of the Meme in 2026
In 2026, the meme hasn't died—it's evolved into institutional critique. Remote work is no longer new, but meeting bloat is worse. The average developer in 2026 attends more meetings than in 2020, despite the pandemic normalizing async work. The industry learned the wrong lesson: instead of replacing meetings with emails, we just added more meetings and called them "sync-ups" and "check-ins" and "touch bases."
Companies that have solved this (GitLab, Automattic, Zapier) are known as "the best places to work." They do this by:
- Setting "no-meeting days" (Fridays or Wednesday afternoons are common). Full days without calendar blocks.
- Using Slack-first communication for status updates and decisions. If it's not urgent, it's async.
- Making meetings optional unless marked "attendance required." Presence is requested, not assumed.
- Recording meetings and posting summaries, not requiring live attendance. You can watch it later.
- Banning recurring meetings that never change. If the content is the same every week, it becomes a document.
- Celebrating async wins publicly. Showing that decisions got made, work got done, without synchronous time.
The meme endures because the problem endures. Until your organization treats developer focus time as seriously as it treats meeting attendance, someone's going to think (or say), "This meeting could have been an email."
Wearing Your Philosophy
If you've nodded along to this entire post, you understand why our This Meeting Could Have Been An Email Shirt exists. It's not anti-social. It's pro-productivity. It's a statement that your time and focus are valuable, and they should be guarded like production systems (because your work IS a production system). The philosophy of protecting focus time is backed by research across agile and DevOps communities. Wear it in your next unnecessary meeting. Someone will get it. Some manager somewhere might even rethink their calendar.
Frequently Asked Questions
Where did the "this meeting could have been an email" meme come from?
The phrase emerged as a meme around 2018-2019 in developer communities, but exploded during the 2020 pandemic shift to remote work. As Zoom became omnipresent and managers equated "camera time" with "productivity," developers realized that synchronous video calls were replacing asynchronous communication, killing deep work and focus time. The meme was born from collective frustration with meetings that should have been Slack messages or emails.
Do developers really hate meetings?
Developers hate interruptions and lost focus time, not meetings themselves. Research shows 71% of managers admit meetings are unproductive. The problem isn't the concept—it's that too many meetings are scheduled for status updates, information delivery, and routine syncs that work better as async communication. A well-run, time-boxed problem-solving meeting? Developers are fine with that. A 45-minute status call that could have been a Slack doc? That's the complaint.
How many meetings could actually be emails?
Studies show that roughly 32% of meetings could be emails or async communication instead. That translates to thousands of wasted hours per year in an average organization. When teams audit their recurring meetings and replace unnecessary ones with async updates, they typically recover 3-5 hours per week per person. For an engineering team of 20 people, that's 300-500 hours per year—roughly a full developer worth of recovered time, just from better communication practices.