Your calendar is full. You know this. That is not news. What you maybe have not named is that most of what fills it did not need to be a meeting in the first place.
The status update that three people sit through and two half-listen to. The "quick sync" that takes thirty minutes and could have been a message. The decision call where everyone already knew their position before the call started. These are the meetings you could move to async without losing anything important, and your week would feel different by Friday.
What actually needs real time
Before we talk about what to cut, let us be fair to meetings. Some conversations genuinely need everyone in the same room at the same time.
Complex problem-solving where people build on each other's thinking. Relationship work where the point is connection, not information transfer. Hard decisions that require debate to surface real objections. New hire onboarding. Hiring interviews. Clients who need to see your face.
Those are the meetings worth protecting. Everything else is on the table.
What async handles well
Status updates are the biggest one. Nobody needs to block fifteen minutes to hear what three other people worked on yesterday. A short written message in Slack or a shared doc covers it, and the people who care can read it when they have a minute.
Information sharing. "Here is the new policy." "Here is what the client said." "Here is the plan for next week." These are broadcasts, not conversations. Write them down once, let people read when they can.
Simple questions. The "can I do X?" or "where do we keep Y?" type. You were going to answer with a sentence anyway. Do not put it on a calendar.
Most status meetings with your team. You can replace a weekly standup with a short Monday written update where each person posts three lines: what they are working on, what they are blocked on, what they need. You glance through in five minutes, respond to what needs a response. You reclaim the meeting slot.
Most reviews. Share the doc, ask for comments by a deadline, summarize the feedback, make the call. Synchronous review meetings tend to be people reading out loud what everyone could have read silently in a third of the time.
The tools are ones you already have
You do not need new software. Slack, Teams, email, Google Docs, Notion, Loom. That is the list. Most teams own more than enough software for this. What they lack is shared expectations about when to use which.
A reasonable default stack for a small business:
Slack or similar, for fast questions and quick updates. Default to a channel, not a DM, so other people can learn from the answer.
A shared doc tool, Google Docs or Notion, for anything that needs to be referenced later. Status updates, project plans, decisions that got made.
Loom or a quick video recording, for the things that are easier to show than type. New process walkthroughs, client updates, anything with your face on it.
Email, for anything outside the team, and for long-form internal updates.
Calendar, for the meetings you genuinely need. And nothing else.
The hard part is setting expectations
The tool is not the problem. The norm is. If your team has not agreed on response times, async communication feels worse than meetings. Someone sends a question at 2pm. The other person sees it at 5pm. They answer at 9am the next day. The sender has been stuck for 19 hours.
Write the norms down. Keep it short. Something like: messages in Slack are answered within a business day, urgent stuff goes to phone, everyone has the right to two heads-down blocks per day where they do not respond to anything. That is a real agreement. It does not need a policy document.
The other piece is getting comfortable with answers not being instant. A lot of owners send a message and then wait by the screen. That is not async. That is impatient sync with extra steps. Send the message, close the tab, come back later.
How to make the shift
The simplest move: pick one recurring meeting this week and try replacing it with a written update for four weeks. Just one. Not all of them.
Write the first couple of updates yourself so the format is clear. Two or three short sections. What happened, what is next, what is blocked. Keep it tight on purpose. If people feel like they are writing essays, they will stop doing it.
Watch what happens. Does the team feel less informed? Less aligned? Or do they feel like they got their Monday morning back? Sometimes the meeting was doing work you did not realize, and you need to bring it back. Usually the work it was doing can be covered in a well-structured written update in a fifth of the time.
This is a Kaizen move. Small change, honest look at the result, keep it or throw it away. You are not trying to redesign your whole communication system. You are trying one thing.
When to push back on your own impulse
There is a moment, a few weeks in, when something feels slightly off and the instinctive move is to schedule a meeting to fix it. Resist it once. Try to name the actual problem first. Is it information not getting shared? Write it down where people can see it. Is it disagreement on a decision? Put the decision in a doc and name the people who need to weigh in. Is it a team member feeling isolated? That one might actually need a meeting, a one-on-one, not a group call.
The discipline is to match the format to the problem. Most "communication problems" in small teams are not fixed by adding meetings. They are fixed by writing things down where the right people can find them.
If your calendar is the problem
When I run a Flow Check for a small business, the calendar audit is often the first thing that surfaces real friction. Meetings that exist because they always have. Meetings where the actual decision gets made after the meeting, in a side channel. Meetings someone inherited from a previous role and never canceled.
If that is where your friction lives, two weeks of honest observation can map it. Then you decide what to cut.
Also worth a read if you have been meaning to think about this more broadly: the meeting problem and communication norms nobody wrote down. They pair with this one.