The bad default
Small teams often treat meetings as the safest way to move work.
Need alignment? Schedule a call. Need a decision? Put time on the calendar. Need a weekly update? Bring everyone into a room. Need to make sure something is real? Talk about it live.
This feels responsible because meetings create visible coordination. But visible coordination is not free. It interrupts work, forces context switching, and often turns one unclear issue into an hour of shared ambiguity.
The principle
Meetings are overhead.
That does not mean all meetings are bad. It means they should be treated like any other cost. A meeting has to earn its existence. If five people spend 45 minutes in a room, that is not a 45-minute event. It is 225 minutes of team capacity.
Small teams feel this tax faster than large ones because there is less spare capacity to hide inside.
Why the old default breaks down
There are fewer excuses for routine meetings.
AI can help draft updates, summarize documents, and turn notes into a clear first version. Shared docs are better. Async video is easier. Written status updates are trivial to publish. The cost of preparing clear context has dropped.
So when a team still defaults to live status calls, it is usually not because meetings are necessary. It is because the team has not built the habit of writing things down.
That matters because the downside of meetings has also increased. More tools, more notifications, and more digital overhead mean every calendar block breaks a larger number of active threads.
What small teams should do instead
1. Replace recurring status meetings with written updates
Status is the easiest category to move out of live conversation.
If the goal is simply to share progress, blockers, and next steps, a short written update is almost always cheaper and easier to revisit later. How to Replace Status Meetings With a Written Weekly Update is partly about this exact shift.
2. Require a written reason for every meeting
Before something goes on the calendar, answer three questions:
- What decision needs to happen?
- Why can it not happen in writing?
- What must be true by the end of the meeting?
If the organizer cannot answer those quickly, the meeting is probably early or unnecessary.
3. Use pre-reads instead of live context dumps
Many meetings are not decision meetings. They are document-reading sessions in disguise.
Send the context before the meeting. Let people show up already oriented. Then the live time can be used for disagreement, tradeoffs, and a crisp decision.
4. Keep live conversation for the work that actually benefits from it
A short live discussion is still useful for:
- resolving a hard disagreement
- handling something sensitive
- unblocking a stuck decision with multiple owners
But even then, the output should be written down immediately after.
A simple operating rule
If the desired outcome is information transfer, use writing first. Use a meeting only when live discussion clearly changes the quality of the decision.
A checklist or example
Try this meeting filter for one month:
- Cancel every recurring status meeting.
- Replace it with a shared written update.
- For every remaining meeting, add the decision to the invite title.
- Cap routine meetings at 25 or 50 minutes.
- End every meeting with a short written note: decision, owner, next step.
That one month usually reveals how many meetings were really serving as anxiety management rather than useful coordination.
Common failure modes
One failure mode is declaring "no more meetings" without giving the team a replacement system. That just creates confusion. Writing has to take the place of the meeting, not merely remove it.
Another failure mode is keeping the meeting and adding the document too. That doubles the work instead of simplifying it.
The last failure mode is leadership behavior again. If leaders keep asking for live reassurance, the calendar will refill no matter what the policy says.
Conclusion
Meetings are not progress. They are a coordination expense.
Small teams improve when they spend that expense carefully, write more by default, and reserve live time for the few conversations that genuinely need it.