← Research/Opinion · Short/3 min read

Against the status meeting.

Published: ·Last reviewed: Current

Status is a report, not a conversation. If your calendar disagrees, your calendar is wrong.

Quick answer
Should I have a recurring status meeting?
Almost never. Status is a read operation — it belongs in a document, where it can be batched, searched, and skipped. A recurring status meeting is a slow and expensive email, read out loud.
AS
Adam Stead
Mar 15 · MeetingCost Research

If you have ever sat in a thirty-minute meeting where six people took two minutes each to say what they did last week, you have attended a very expensive, very slow email.

Status meetings are the default because they’re the easiest thing to book. They require no preparation, no artifact, no decision. The cost is invisible, which is different from being zero. The cost is, in fact, enormous.

Status is a read operation. It belongs in a document. Writing it forces clarity; reading it lets people batch; skipping it, when nothing’s new, is allowed. None of these things are available in a meeting. You can’t skip a meeting you’re in.

“If the purpose of your meeting is to hear what happened, you did not need a meeting. You needed a paragraph.”

The counter-argument is always the same: but it’s how we stay connected.Fine — keep one. A fifteen-minute shared coffee. No agenda. Nothing to report. Just people. Call it what it is and let everyone decline without guilt on the weeks they don’t want it.

Everything else — the pipeline review, the ops standup, the team sync that somehow starts with a round of updates — those aren’t meetings. Those are memos that somebody didn’t want to write.

Price a status meeting →
— then imagine that number on the invoice.

Frequently asked

FAQPage schema
  • Keep one short, agenda-less fifteen minutes a week if cohesion is the goal — and call it that. Don't dress it up as a status sync. Make it declinable without apology.
AS
About the author

Adam Stead

Founder & editor, MeetingCost

CTO, founder and operations coach. Has built and run multiple companies across tech and marketing. Writes MeetingCost from the vantage point of someone who has sat through — and called — too many of the meetings he now advises people to cut.

CTO & founderOperations coachTech + marketing operator

Sources

  1. 01GitLab Handbook — Meetings · GitLab2024
  2. 02The Art of Async · Amir Salihefendic · Doist2022
  3. 03Stop the Meeting Madness · Perlow, Hadley & Eun · HBR2017
Keep reading
All research →