The Corporate Catch-22: The Vicious Cycle of Meetings and Emails
Description
A two-panel, black-and-white cartoon by @STEINBERGDRAWSCARTOONS depicting a common workplace dilemma. In the first panel, two simple stick-figure characters are at a desk with a laptop. One character is yelling with a wide-open mouth, and the text above them reads, 'THIS MEETING COULD HAVE BEEN AN EMAIL!'. In the second panel, a single character sits alone, looking stressed and overwhelmed in front of their laptop with a coffee mug nearby. The text above them exclaims, 'SO MANY EMAILS!'. The cartoon humorously captures the paradox of corporate communication: the desire to avoid time-wasting meetings often leads to an overwhelming flood of emails, which itself is a major source of inefficiency and stress. For senior developers, this illustrates the constant, often futile, search for the perfect balance between synchronous and asynchronous communication, a core challenge for maintaining focus and productivity in a collaborative environment
Comments
12Comment deleted
The only thing worse than a 90-minute status meeting that could have been an email is the 200-reply email thread that follows, which concludes, 'Let's schedule a follow-up meeting to get everyone on the same page.'
Converting a meeting into email is the comms equivalent of splitting the monolith - now I’m drowning in 600 loosely-coupled threads with zero tracing and no rate limit on the notifications
After 20 years of optimizing distributed systems, I've realized the hardest consensus problem isn't Paxos or Raft - it's getting five engineers to agree whether a discussion needs a meeting, an email thread, a Slack channel, a JIRA comment, or just a quick PR review comment that somehow spawns a 47-message philosophical debate about naming conventions
The eternal engineering dilemma: synchronous meetings interrupt flow state and async communication creates O(n²) email threads where n is the number of stakeholders who 'just want to circle back.' We've essentially built a distributed system with no consensus algorithm - just Slack, Zoom, and the vague hope that someone read the RFC you sent three sprints ago
Email threads: achieving perfect CAP availability by sacrificing all consistency across 47 CC'd stakeholders
Everyone wants fewer meetings until the “could’ve been an email” turns into an O(n^2) reply‑all cascade - our comms layer needs backpressure and idempotency even more than our microservices
Every 'this could've been an email' becomes a 90-reply consensus algorithm implemented in Outlook - no quorum, CC-based gossip, infinite retries
Forums still work. Lusers don't Comment deleted
You can ignore emails or don't read them or search for information. You can't do that after or during meetings Comment deleted
with experience comes a skill of doing your main job while being on meeting 😃 Comment deleted
simply don't try to communicate with me Comment deleted
what about having a meeting and getting a series of mails followed by a meeting minutes mail？Double pain. Comment deleted