In short
To reduce meetings, list every recurring meeting and ask what each decides, cancel or replace the ones that only share status with a written update, shorten the rest and give each an agenda, and keep a written record so people can skip meetings without losing track.
To reduce meetings, start with the recurring ones: list them, write down what each one decides, replace the ones that only share status with a written update, shorten the rest, and give every meeting that survives an agenda. Then keep a short written record of each, so the people who skip it do not lose track. That last part is what makes the rest stick.
This guide goes through a meeting audit step by step, then covers the habits that stop the calendar filling up again. It is the index for this section; each step links to a guide that goes deeper.
How to reduce meetings: a meeting audit
- List every recurring meeting. Go through your calendar for the next four weeks and write down each recurring meeting: its name, how often it happens, how long it lasts and how many people attend. One-off meetings can wait; the recurring ones repeat whatever you do.
- Write down what each meeting decides. For each, write one line: "This meeting exists to …". If the honest answer is "to hear updates", mark it. If nobody can say, mark it too.
- Work out what each one costs. Multiply attendees by hours per month. Add a loaded hourly cost if you want a money figure; what a meeting costs gives the formula and a worked example.
- Decide: keep, change, replace or cancel. Use the table below. Most teams find at least one meeting that can go and several that can be shorter.
- Tell people what changed and why. Send one message with the decisions, the new format for anything replaced, and a date to review it. A meeting cancelled without explanation tends to come back.
- Review in four to six weeks. Ask what was lost. If something important stopped happening, bring back a smaller version of the meeting rather than the whole thing.
Keep, change, replace or cancel
| If the meeting… | Then |
|---|---|
| Only shares status or updates | Replace it with a written update |
| Makes decisions, but runs long | Keep it, shorten it, add an agenda |
| Has people who rarely speak | Make them optional and send them the notes |
| Overlaps with another meeting | Merge the two |
| Nobody can say what it is for | Cancel it for a month and see who asks |
| Handles conflict, feedback or hard problems | Keep it; these need a conversation |
The last row matters. Fewer meetings help only if the work they did still gets done. Reporting moves well to writing. Deciding, disagreeing and helping someone who is stuck usually still need people talking.
Replace status meetings with writing
Status meetings are the easiest to cut, because reading is faster than listening and does not need everyone free at the same time. A short written format (done, next, blocked) posted in one place by a fixed time replaces most of them. The blockers still get a conversation, just a small one with the people involved.
Async status updates has a template and covers where updates should live and how to stop blockers getting lost. If your team keeps a daily standup instead, keep it short and write down only the blockers; see standup meeting notes.
Make the meetings you keep shorter
A meeting expands to fill its slot. Three changes shrink it:
- Default to a shorter slot. 25 or 50 minutes instead of 30 or 60 leaves a gap between back-to-back meetings. Google Calendar and Outlook both have settings that do this for every new meeting; how long a meeting should be has the steps and suggested lengths by type.
- Write an agenda as questions. "Do we launch Harbour on 3 November?" ends when it is answered. "Launch" does not. The meeting agenda template shows the format, with owners and time boxes.
- Invite fewer people. Everyone who needs to decide, plus anyone whose input is needed for an item. Everyone else gets the notes.
If you want to know whether you personally are the reason a meeting runs long, talk-to-listen ratio explains how to measure how much you spoke.
Protect whole days
Cutting individual meetings frees scattered half-hours. A day with no meetings at all is different: it is time for work that needs several hours without interruption. Many teams pick one day a week, block it in everyone's calendar and agree on the exceptions. No-meeting days covers choosing the day and making it last beyond the first month.
Keep a record so people can skip
The main reason people attend meetings they do not need is the fear of missing something. A short written record removes it. After each meeting, write down:
- What was decided, and by whom.
- Action items, each with one owner and a date.
- Open questions, and who is finding the answer.
Put the record where the team already looks: the project page, the channel, the ticket. The meeting notes template has this format in copyable Markdown.
Then make it normal to skip. When someone misses a meeting, they read the notes and ask a question if something is unclear. Catching up on a meeting you missed covers what a good catch-up note contains and what to ask the people who were there.
Match the format to the type of meeting
Different kinds of meeting reduce in different ways. Status meetings go to writing. Planning meetings get shorter when the preparation happens beforehand. One-to-ones and retrospectives usually should stay, because they are where problems come up that nobody writes down. Types of meetings lists the common kinds, what each is for and what its record needs.
Where a notetaker helps, and where it does not
A recording does not reduce meetings by itself. A transcript of an hour nobody needed is still an hour, now with a file attached. Where it helps is in the record: the person taking notes can listen instead of typing, and the notes can be checked against what was actually said before they go out.
Notey records meetings on your Mac, with your microphone and the call as two separate tracks, and transcribes them on the device. If you ask for a summary with action items, only the transcript's text is sent, and the result is labelled as AI-generated; it says so when nobody committed to anything, which is itself worth knowing about a meeting. Notey has no shared workspace, so you export the notes and post them where the team reads them. Everyone in the meeting should know it is being recorded; say so at the start.
Common mistakes
- Cancelling meetings without replacing what they did. The information stops flowing and the meeting comes back, usually longer.
- Cutting the one-to-ones first. They are cheap and they are where problems surface early.
- Replacing a meeting with a longer document nobody reads. A written update should take two minutes to read.
- Never reviewing. Calendars refill. Repeat the audit every few months.
Frequently asked questions
How do I reduce the number of meetings on my team?
Start with the recurring meetings, because they repeat. For each, write down what it decides and who needs to be there. Replace the ones that only share information with a written update, and shorten or merge the rest.
How do you politely decline a meeting?
Say what you can offer instead - "I can't make it, but I'll send my update in writing by 10 and read the notes afterwards." Declining is easier when the meeting has an agenda and notes, because you can see whether you are needed.
Are fewer meetings actually better?
Fewer meetings help only if the work they did still gets done. Status can move to writing; decisions and hard conversations usually still need people talking. Cut the reporting, not the discussion.
What is a meeting audit?
A list of every recurring meeting with its purpose, attendees, length and cost, reviewed to decide which to keep, change or cancel. It takes an hour or two and is worth repeating every few months.
How can people skip a meeting and still know what happened?
Write down the decisions, action items and open questions, and put them where the team already looks. A short written record is what makes skipping safe.