Look at last week's calendar for anyone on your team and you'll find the same shape: a morning fractured into thirty-minute pieces, an afternoon with one real block of focus time that got eaten by a "quick sync," and a standing invite nobody remembers accepting. On a ten-person team that's not a scheduling annoyance — it's the single largest tax on the work, and it compounds every time headcount grows.
The usual advice is to declare "no-meeting Wednesdays" and move everything to Slack. That helps for about two weeks, then the meetings creep back, because the reason they exist never went away. A meeting is almost always a symptom of missing context: someone couldn't find the state of the work, couldn't get a decision made, or couldn't trust that a written update would actually be read. Kill the meeting without fixing the context and you just move the confusion somewhere else.
So the real question isn't "how do we have fewer meetings." It's "which meetings are carrying information that has nowhere else to live, and how do we give it a better home." Here's how to sort them.
Every recurring meeting is one of three things
Before you cut anything, label each standing meeting on the calendar. In practice they all fall into one of three buckets, and each bucket has a different correct answer.
- Status meetings exist to answer "where is everything?" Standups, weekly check-ins, project syncs. These are the most common and the most replaceable — status is state, and state belongs on a board, not in a room.
- Decision meetings exist to resolve something that's genuinely contested or ambiguous. Architecture calls, prioritization arguments, "do we ship Friday or not." These are worth defending. A real decision with three stakeholders in disagreement is faster live than in a 40-comment thread.
- Connection meetings exist so people who work together actually know each other. 1:1s, retros, the occasional team call. Cutting these to save time is a false economy — they're cheap and they're what makes the async stuff work at all.
The mistake almost every overloaded team makes is running all three as if they were the same thing: a recurring 30-minute block on the calendar with a vague agenda. Once you've labelled them, the cuts get obvious.
Kill status meetings — move status onto the board
Most of what a daily standup delivers is already sitting in your tracker, or should be. "What I did yesterday, what I'm doing today, what's blocking me" is three columns of a board and a blocked flag. When the board is the source of truth, the meeting is just people reading it aloud.
The fix isn't to cancel the standup and hope — it's to make the written state good enough that nobody needs the readout. That means:
- The board reflects reality without anyone narrating it. If moving a card from "In Progress" to "In Review" is a single keystroke inside the tool people already work in, the state stays current for free. If it takes a context-switch to a separate app, it rots, and you're back to needing the meeting. This is the same reason WIP limits only work when the board enforces them — the tool has to hold the truth, not a wiki.
- Blockers are loud. A blocked item should page the person who can clear it, not wait for tomorrow's 9:15 to surface. Real-time notifications and @mentions turn "I'll mention it at standup" into "cleared in twenty minutes."
- Async updates are threaded, not spoken. If you genuinely want a daily heartbeat, post it as a comment on the sprint or the board where it lives next to the work, not in a chat channel that scrolls away by lunch.
Do this and the daily standup either disappears or shrinks to a two-minute optional call for the handful of people who actually have something to coordinate.
Defend decision meetings — but make them cheap to start
Decision meetings are the ones worth keeping, so the goal is to make them frictionless rather than rare. The failure mode here is the opposite of status meetings: a decision that needs five minutes and two people gets scheduled three days out because "let's find a slot," and the work stalls the whole time.
The trick is to collapse the distance between "we need to talk about this" and "we're talking about this." When a question surfaces on a specific issue, you want to jump straight from that issue into a call with the two people who own it — no calendar invite, no link-pasting, no hunting for context once you're in the room. That's the entire design idea behind in-context Meetings: you start the call from the issue or board you're already looking at, so everyone arrives with the same screen in front of them and the decision gets recorded back onto the work.
A good rule: if a thread hits its fifth back-and-forth reply without converging, stop typing and start a call. Text is great for broadcasting and terrible for negotiating.
A quick triage table
Run every recurring meeting through this once and you'll usually reclaim a third of the calendar.
| If the meeting is mostly… | It's a… | Do this |
|---|---|---|
| People reading their board status aloud | Status | Kill it; fix the board and notifications |
| One team's progress for another team | Status | Replace with a shared filter or dashboard |
| A contested call with 2–4 stakeholders | Decision | Keep it, but make it startable in one click |
| A design that needs a whiteboard | Decision | Keep it; timebox to 30 minutes |
| 1:1s, retros, team connection | Connection | Keep it; protect it |
| "We've always had this one" | Unknown | Cancel for two weeks and see who notices |
That last row is the highest-leverage experiment on the list. A recurring meeting nobody will fight to reinstate was never load-bearing.
Meetings are a feature of good async, not a replacement for it
The teams that feel calm aren't the ones that banned meetings. They're the ones where the written state is trustworthy enough that a meeting is a deliberate choice — "this specific thing is worth interrupting three people for" — instead of the default way information moves. Get the board, the filters, and the notifications right, and the meetings that survive are the ones that were always worth having.
You don't need a productivity framework for this. You need a place where status lives so it doesn't need a standup, and a way to turn a thread into a call the moment it's warranted.
Want meetings you can start from any issue, board or project — unlimited on every plan, free included? See what Meetings does, check the pricing, and start free. Your calendar will notice.
