Grief-Test Your Calendar: Which Meetings Would Anyone Actually Mourn?

Every team has one. That recurring meeting nobody can quite explain. The Thursday sync that starts four minutes late, runs on fumes, and ends with 'okay, guess that's it.' Nobody schedules it anymore — it just is, like a load-bearing wall nobody wants to test.

We've written a lot on this site about meeting bloat, and the standard advice is always the same: audit your calendar, cancel ruthlessly, protect your maker time. Solid advice. But it skips a step that matters. Before you cut, you should figure out what your team would actually miss.

We call it the Grief Test, and it takes about an hour.

The Premise: Rank Meetings by Imaginary Loss

Here's the whole framework: go through every recurring meeting on your team's calendar and score it on one question — if this meeting vanished tomorrow, how upset would anyone be?

Not 'is this meeting useful?' That question invites everyone to defend their creations. 'Grief' is more honest. It measures attachment, and attachment is a surprisingly good proxy for value.

Score each meeting on a simple 0–3 scale:

• 0 — Nobody notices. The meeting dies and a week passes before someone mentions it in Slack.
• 1 — Mild relief. People quietly appreciate the reclaimed half hour. Nobody says anything, but morale ticks up.
• 2 — Real inconvenience. Work gets harder. Information stops flowing. Someone rebuilds a workaround within a week.
• 3 — Genuine mourning. Decisions stall, people feel disconnected, and the team demands it back.

Most teams that run this exercise discover something uncomfortable: the majority of their recurring meetings score a 0 or 1. The ones scoring a 3 are rarely the ones people complain about.

Running the Exercise in One Hour

Block one hour. Bring the whole team — remote folks included, cameras optional. Here's the worksheet:

Step 1 (10 minutes): List every recurring meeting. Pull them straight from your shared calendars. Include the ones without invites, like the 'quick huddle' that happens anyway. A 10-person startup typically surfaces 15–25 of these.

Step 2 (20 minutes): Grief-score each one, silently. Everyone scores independently first. This is critical — if you discuss before scoring, the loudest voice in the room sets the number. Use a shared doc or a polling tool so nobody sees anyone else's answers.

Step 3 (20 minutes): Compare and discuss the gaps. The gold is in the disagreement. If your weekly client pipeline review scores a 3 from sales and a 0 from engineering, that's not a problem — that's information about who the meeting is actually for. Meetings with a spread of two or more points get talked about. Meetings where everyone says 0 get a different conversation.

Step 4 (10 minutes): Decide the experiment. Nothing gets cancelled permanently on day one. Instead, each 0- or 1-scored meeting becomes a one-month pause. Async replacement if the score wasn't a flat zero; full deletion if it was. Put a calendar reminder at the end of the month to check grief levels for real.

That's it. One hour, one spreadsheet, one month of evidence.

What Teams Find When the Meetings Go Quiet

We've heard versions of the same story from enough small teams now that a pattern has emerged. A Denver-based agency ran the test and paused six of their eleven recurring meetings. Two came back within a month — the client kickoff and a biweekly design critique that people genuinely loved. Four never returned. Total meeting load dropped roughly 40%, and the most common reaction wasn't celebration. It was 'wait, we had a meeting there?'

That's the tell of a 0-score meeting: its absence is indistinguishable from its presence.

A five-person fintech startup in Chicago found their daily standup scored a 1 across the board. They replaced it with a written check-in posted in their team channel by 9:30 — three lines: what I did yesterday, what I'm doing today, what's blocking me. Six months later, the async thread has a longer institutional memory than the meeting ever did, because it's searchable.

The Meetings That Survive

It's worth saying: this isn't an anti-meeting manifesto. Teams that run the Grief Test don't come out the other side meeting-free. They come out with a shorter, denser calendar where the survivors mean something.

The meetings that reliably score a 3 share a few traits: someone makes a decision in them, someone feels seen in them, or something gets unstuck that would otherwise fester. One-on-ones almost always survive — not because they're efficient, but because they're where trust gets built, and trust doesn't async well. Brainstorms where everyone leaves with energy survive. Status updates never do, because status is a written artifact pretending to be a conversation.

The Deeper Point

The reason the Grief Test works where standard audits fail is that it reframes the question. Calendar audits ask 'what can we cut?' — a scarcity question that invites defensiveness. The Grief Test asks 'what do we actually value?' — a question teams can answer together without anyone feeling attacked.

And for smaller teams, the stakes are real. When you're ten people, a weekly hour-long meeting with eight attendees is 1% of your collective workweek, every week, forever. Multiply that across the calendar and you're paying a part-time salary for meetings nobody would mourn.

Run the test. Pause the zeros. And when the month ends, trust whatever grief shows up — or doesn't — to tell you the truth.