For three months — 13 weeks, 62 working days — I tracked every meeting I attended. Not just the count, but the type, the actual outcome, the number of attendees, and whether the meeting could have been replaced by an async alternative. I built a spreadsheet. I made charts. I did this because I am an engineer and when something annoys me enough, I quantify it until I can prove the annoyance is justified.
The results: 247 meetings in 13 weeks. That's 19 meetings per week, averaging 34 minutes each. Total time in meetings: approximately 10.8 hours per week, or 27% of my working hours. Now here's the kicker — I classified each meeting into one of four categories: "necessary and productive," "necessary but unproductive," "unnecessary but harmless," and "a complete waste of everyone's time." The breakdown: 23% were necessary and productive. 31% were necessary but could have been half the length. 26% could have been a Slack message, an email, or a shared doc. And 20% — one in five — had no clear purpose, no agenda, and produced no action items. They existed because someone had a recurring calendar invite and lacked the courage to delete it.
The worst offenders were "status update" meetings where eight people sit in a room (or a Zoom) and take turns reading things that are already written in Jira. If your standup takes 25 minutes for a team of six, that's not a standup — it's a sitdown. The second worst: "alignment" meetings, which is corporate for "we don't trust Slack to convey nuance, so let's waste an hour making eye contact about it." Third place: the "quick sync" that was neither quick nor synced.
The fix isn't "no meetings" — some conversations genuinely need real-time, face-to-face interaction. Architecture decisions, conflict resolution, brainstorming sessions where ideas build on each other — these benefit from synchronous communication. But status updates don't. FYI announcements don't. Decisions that one person has the authority to make don't. The math is simple: if your meeting has 8 people and lasts 30 minutes, that's 4 person-hours. If the outcome could have been achieved with a 3-paragraph Slack message that took 10 minutes to write, you just burned 3 hours and 50 minutes of human life. Multiply that across every unnecessary meeting in your company and the number will make your CFO physically ill.