Zimbo Meetings and the Ghost Work Tax
A 30-minute meeting costs 2.5 hours of actual work. That’s not a metaphor. That’s the math when you account for prep, context switching, and follow-up. Most organizations track the 30 minutes. None track the 2 hours of ghost work that surrounds it.
I’m calling these Zimbo meetings—not zombie meetings, because they’re not dead. They’re worse. They’re undead. They shamble forward, consuming resources, generating more meetings, but producing no decisions and no clarity.
The Ghost Work Tax
The Ghost Work Tax is the hidden labor that meetings extract from teams: calendar coordination, pre-reads, note-taking, summary distribution, action item tracking, and the mental overhead of managing all of it. It doesn’t show up in calendars. It doesn’t show up in time tracking. But it shows up in missed deadlines and burnt-out teams.
At Pragmatic Leaders, I ask PMs to track their actual meeting preparation time for one week. The median ratio is 1:3. For every hour in meetings, they spend three hours on ghost work. Senior PMs hit 1:4 because they’re expected to “come prepared” to everything.
The tax compounds with team size. A 30-minute meeting with 8 people isn’t 4 person-hours. It’s 20 person-hours when you include the ghost work. Most companies would require VP approval for a 20-hour project. They let anyone schedule a 30-minute meeting.
Where the Ghost Work Hides
Here’s the falsifiable claim: If you eliminate meetings with no pre-defined decision or deliverable, you reduce total coordination overhead by 40-60%, not 20-30%.
The standard advice is “have better meetings.” That’s useless. The problem isn’t meeting quality. It’s meeting existence.
Zimbo meetings have three characteristics:
- No exit condition. The meeting ends when the calendar says it ends, not when a decision is made.
- Recursive ghost work. The meeting generates action items that require more meetings to resolve.
- Ambient participants. Half the attendees are there “just in case” or “for visibility.”
The ghost work tax hits hardest in three places:
Pre-meeting: Reading the deck someone sent 10 minutes before the call. Digging up the context from three Slack threads. Finding the doc that was “shared last week.” The calendar says the meeting starts at 2pm. The actual work starts at 1:30pm.
During-meeting: One person talks. Three people take notes in three different tools. Two people are on mute doing other work. One person is “capturing action items” in a format no one will read. The official output is a 30-minute meeting. The actual output is 90 minutes of fragmented attention.
Post-meeting: Writing the summary email. Clarifying what was actually decided in the back-channel Slack thread. Scheduling the follow-up meeting because this one ran out of time. Updating the three places where meeting notes live. The meeting ended at 2:30pm. The ghost work ends at 4pm.
I’ve seen teams where 60% of “execution time” is actually meeting overhead. They’re not slow because they can’t build. They’re slow because they can’t stop coordinating.
What We Measured
We tracked this at Zopdev for one quarter. Every meeting required a one-line purpose statement and a binary decision: “Is this to make a decision or share information?” If information, it defaulted to async unless someone could articulate why it needed to be synchronous.
Meeting count dropped 40%. Ghost work dropped 55%. The delta—that extra 15%—came from eliminating the recursive meetings. The meetings that existed to clarify the meetings that came before them.
Here’s what we learned:
Most “syncs” are status theater. The information being shared already exists in Slack, Linear, or Notion. The meeting exists because someone doesn’t trust the async system or because “we’ve always done it this way.”
Most “brainstorms” are pre-cooked. One person has already decided. The meeting exists to build consensus or distribute blame. The actual decision-making happened in a 1:1 three days earlier.
Most “check-ins” are anxiety management. The manager feels out of the loop. The meeting exists to make them feel better, not to unblock the team.
The pattern I see across thousands of PMs: junior PMs schedule meetings because they don’t know how to make decisions. Senior PMs schedule meetings because they know exactly what decision they want and need organizational buy-in to de-risk it.
Neither is wrong. But only one is honest about what the meeting is for.
The Framework: Decide, Deliver, or Die
Every meeting should have a decision, a deliverable, or die.
Decision meetings need: a clear choice to be made, pre-circulated options with tradeoffs, and a DRI who owns the call. If you can’t name the decision, it’s not a decision meeting.
Deliverable meetings need: a thing that will exist at the end that didn’t exist at the beginning. A design, a plan, a document. If the output is “alignment,” it’s not a deliverable meeting.
Everything else is async. Updates go in Slack. Brainstorms start in docs. Status lives in project management tools.
The Ghost Work Tax doesn’t show up in your P&L. It shows up in your execution speed. In your team’s ability to do deep work. In the gap between your roadmap and your delivery.
Track it for one week. For every meeting on your calendar, log the prep time, the meeting time, and the follow-up time. Add it up. Then ask: what could we have built with those hours?
Most organizations won’t do this. They’ll keep scheduling 30-minute meetings and wondering why quarters take six months.
The ones that do will discover something uncomfortable: half their meetings exist to compensate for broken async communication. Fix the async system, kill the meetings, reclaim the ghost work hours.
What I don’t know yet: how to build organizational trust in async-first decision-making when the executive layer still equates “presence in meetings” with “doing the work.” The ghost work tax is a technical problem with a political solution.
More on this as I work through it.