Most weekly meetings transmit information that could be read. What to replace, what to keep, and how to do it without people feeling cut off.
Key takeaways
- Information is read faster than it is heard; decisions require talking.
- A meeting meant to update can be replaced by a report; one meant to decide cannot.
- Before cancelling, the information must genuinely be available elsewhere.
- The test: if no decision was made, that was a reading-aloud session.
A classic status meeting transmits information at the slowest rate available: one person talks while everyone else listens to something mostly irrelevant to them. What makes it unnecessary is not the time but the content - almost everything said in it could be read in two minutes.
What can be replaced and what cannot
| Meeting type | Its purpose | Replaceable? |
|---|---|---|
| Round of updates | Everyone says what they did | Yes - a report or a board |
| Project status update | Where things stand | Yes, provided status is recorded |
| Decision discussion | To decide | No |
| Problem solving | To think together | No |
| Coordination between people | Who does what | Partly - a board plus five minutes |
| Feedback conversation | To tell a person something | No, and do not batch it |
The first row consumes the most time in small businesses and is also the easiest to replace - provided something else genuinely holds the information.
What must exist before you cancel
Cancelling a meeting with no replacement creates a vacuum, and then information travels through private conversations - which is worse than the meeting. Three conditions first:
- Status exists in one place everybody can see - a board, a list, or a report.
- Somebody is responsible for keeping that information current.
- There is a channel for questions that is not a meeting - a message, a comment on a task.
Without the first, cancelling simply hides the problem: the team will not know what is happening, and it will surface accidentally when somebody does something twice. The logic of the report replacing the round is in a one-page weekly management report.
The format that replaces it
A board or list where each item shows four things: what it is, who owns it, what the status is, and what the next step is. That covers nearly everything said in a round of updates, and it is read in two minutes rather than forty.
What is worth keeping is a very short meeting - ten minutes, standing - covering only two things: what is unusual, and what is stuck. Everything else people read themselves. The difference from a status round is that here you only discuss what needs action.
Doing it without people feeling cut off
That is the real objection, and it is legitimate: a meeting also has a social role, and it is the moment people hear what is happening in the business. Abrupt cancellation feels like distance.
Three approaches that work: keep one monthly meeting that is genuinely a conversation rather than an update; include good news in the report and not only numbers; and explain the change explicitly - the aim is to return an hour a week to everyone, not to reduce communication. Said out loud, the resistance drops sharply.
What it is worth in practice
Five people in a 45-minute weekly meeting is close to four person-hours a week, around 190 hours a year. Even a partial replacement - shortening to 15 minutes - returns more than a hundred hours. The full method for costing this is in what manual work costs.
What matters in that calculation is not only the hours but the interruption: a meeting in the middle of the day splits it into two short halves, which costs more than the meeting itself. So when a meeting is kept, it is worth fixing it at the start or the end of the day.
What to do with the meetings that remain
- An agenda in advance - two lines is enough, but it must be sent.
- A defined outcome - what has to come out of it.
- Who must attend and who need not - default attendance is an expensive habit.
- Ending with decisions - what was decided, who does it, by when.
- A fixed length, not "until we finish".
The third returns the most hours in a small business: in most meetings two of five people are there because they always have been. One question - does this decision concern them - shortens the attendee list and the meeting itself.
How do you know which meeting to cut first?
Not by instinct but by a month of checking. After each meeting, record two lines: what was decided, and who needed to be there. By month end the picture is clear - some meetings produced no decision at all, and some produced a decision concerning two people out of five.
The first group gets cancelled; the second becomes a conversation between two people. What usually remains is one or two meetings a month that genuinely need everyone, and that is also the number most small businesses arrive at when they check.
Add a third column: how long the meeting actually took. The gap between planned and actual is almost always in one direction, and once it is recorded it starts shrinking on its own.
What happens to the information the meeting carried
That question needs an answer before cancelling, and it splits into three types. Status moves to a board or report. Context - why something happened, what the customer said - needs a place on the customer record or the task itself rather than in somebody's head. And social information, which is real and matters, stays for the monthly meeting or a conversation.
The second type is the hardest and is what makes teams miss the meeting. The practical fix is a small habit: whoever has a meaningful conversation with a customer writes two lines on their record. It takes less time than recounting it in a meeting, and it is still available in six months.
Sources
Frequently asked questions
What if the manager wants the round?
Propose trying it for a month: a written report on the morning of the meeting, and ten minutes covering exceptions only. In most cases the need for the round comes from having no orderly place to see status rather than from wanting to hear it - and once that place exists, the round makes itself redundant.
How do you know a meeting is necessary?
With a simple check after each one: was a decision made that would not have been made otherwise. Three consecutive meetings with no decision mean it is a reading-aloud session, and a report should replace it.
What about a remote team?
There it is worth keeping a regular short meeting, because the incidental interaction of an office is missing. The recommendation is the same - short, with an agenda - but the frequency can be higher, and that is fine as long as it does not become a round of updates.
How long until you see a change?
Usually a month. For the first fortnight people still recount what they did in the short meeting, then they adjust. What accelerates it is the report genuinely being current - when it is incomplete, the team goes back to asking verbally, and that reintroduces the round through the back door.
Keep reading
Related service
MVP Development
Turn an idea into a validated product in weeks, not months.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.