Don’t Do Team Meetings

Regular team meetings are often treated as a default part of work. They are seen as a sign of coordination, alignment, and healthy communication. In practice, they often reveal the opposite.

A recurring team meeting where everyone goes around the room to explain what they did last week is usually not a good use of time. It turns communication into a performance instead of a real exchange of useful information. If the team needs a formal meeting just to learn what people have been doing, that is often a sign that day-to-day communication is already failing.

The problem with “what did you do last week?” meetings

They happen too late

Work should not become visible only once a week in a meeting. If something matters, it should already have been shared when it happened: when a task was completed, when a blocker appeared, when a useful idea emerged, or when help was needed.

Waiting for a meeting to report progress means information is delayed, and delayed information is usually less useful.

They expose a communication issue

If a team depends on a weekly meeting to know what others are achieving, the issue is not a lack of meetings. The issue is a lack of continuous communication.

People should not discover completed work, current priorities, or open questions only during a scheduled call. A healthy team communicates continuously, in context, and in writing when possible. If this is not happening, adding more meetings does not solve the underlying problem.

They are often boring

Most of these meetings are passive. One person speaks, others wait for their turn, and very little real discussion happens. In many cases, people are not truly listening. They are replying to emails, reading messages, or working on something else while the meeting continues in the background.

That is usually a sign that the meeting is not useful enough to deserve full attention.

They scale badly

The more people you add, the worse the meeting becomes.

Each additional participant increases the duration, reduces relevance, and lowers attention. What may be tolerable with three people becomes a waste of time with ten. A long status meeting with many participants often creates very little value for most of them.

A meeting that costs one hour for ten people is not a one-hour meeting. It is a ten-hour cost for the team.

A better model: continuous sharing

The alternative is simple: share continuously in chat, in the right place, as the work happens.

This is the model we use in our team.

Instead of relying on status meetings, communication happens across several chat rooms:

• one global room for the whole team
• one fun room for informal exchanges
• multiple project-specific rooms

The rule is simple: use the project room first when something is related to a specific project. This keeps information close to the people who need it, while still making it visible to others who want to follow along.

Everyone can join all rooms. The only mandatory ones are the global room and the fun room.

This model has several advantages:

Communication becomes timely

Updates are shared when they matter, not days later. People can react sooner, help sooner, and stay informed without waiting for a calendar slot.

Communication becomes contextual

Project-related discussions stay in project rooms. Team-wide information goes to the global room. Casual conversation has its own place. This reduces noise and makes it easier to find relevant information later.

Communication becomes inclusive without being interruptive

People can read when they have time. They do not need to stop their work for a meeting that may not concern them. They can stay informed asynchronously and still participate when relevant.

There is no need to force reactions. Sharing is enough.

Communication becomes searchable and durable

A chat message leaves a trace. It can be read later, linked, searched, or revisited. A spoken status update in a meeting often disappears as soon as the call ends.

Meetings should be the exception

This does not mean that all meetings are bad. Some meetings are necessary:

• to make a decision that requires live discussion
• to resolve a conflict or a misunderstanding quickly
• to work through a complex topic together
• to handle urgent coordination in real time

But a recurring status meeting is rarely the best tool for those cases.

Conclusion

If your team has a weekly meeting just to explain what everyone did last week, the problem is probably not that you need a better meeting. The problem is that you need better communication during the week.

A team that shares continuously in chat is usually more informed, more efficient, and less dependent on rituals that consume time without creating much value.

Do not default to team meetings.

Communicate continuously. Share in context. Keep meetings for the moments when real synchronous discussion is actually needed.