Do you need regular team meetings at all
Recurring meetings aren't always useful: which rituals earn their place, which to cancel, and how to replace them with an async format.
Weekly sync, Friday retro, daily standup. Most recurring meetings appear by inertia: they once helped, settled into the calendar, and stopped being questioned.
When a recurring meeting is needed
- The team is distributed and shared decisions need synchronization. Otherwise people drift apart on priorities.
- There are real forks. A choice must be made and depends on several people at once.
- Personal contact matters. Once a week or two people should see each other, or ties fray. That is a value in itself.
When to cancel
- The meeting became reading statuses aloud.
- Half the attendees are silent and decisions are made outside it.
- The agenda appears at the meeting itself.
- You can’t remember what was decided last time.
A good test: cancel the meeting for a month. If work didn’t suffer, it wasn’t needed. If people started coordinating in chat on their own, you found a real need and can bring the meeting back in a narrower format.
What to replace it with
Async status. Everyone writes what they did and what blocks them in a shared channel. Read in five minutes, written whenever convenient. A project channel works for this.
A transparent board. If the state of work is visible on the task board, “who is working on what” needs no meeting.
Meet on a trigger. Not “every Monday at 10:00” but “when there is a question that can’t be solved in writing”.
What to keep
A short recurring meeting with clear structure (problems and decisions, not statuses), capped at 25 minutes, usually pays off. The rest — as needed. More on what meetings cost in How much does one team meeting cost.