Meetings rarely have a good reputation. They're often seen as time-consuming, obligatory, and inherently inefficient. Almost every organization I've had the opportunity to observe closely has tried to improve its meeting culture. The discussion usually focuses on shorter agendas, better timekeeping, or reducing the number of participants.
The basics are well established. A good meeting needs a clear purpose, a structured agenda, the right people in the room, and agreed outcomes that are documented afterwards.
Determining who the right people are, however, is often more difficult than it appears. When organizers deliberately keep the participant list small, they sometimes leave out exactly those people whose perspective or responsibility is essential. Meeting owners rarely have a complete overview of all adjacent processes and dependencies. One simple practice can help: include a short note in the invitation asking participants to speak up if they believe an important stakeholder is missing. That way, the collective knowledge of the team is used without unnecessarily expanding the invitation list.
An even more fundamental question comes first: Does this need to be a meeting at all? Information sharing and status updates can often happen asynchronously, for example through a narrated PowerPoint presentation. Face-to-face meeting time is most valuable when people need to ask questions, align perspectives, solve problems, or make decisions together.
Yet even a well-prepared meeting can become unproductive. Some people dive too deeply into operational detail. Others provide too little context. Some repeat information everyone already knows. At times, meetings even become a stage for micromanagement, when topic owners are asked to justify details that fall squarely within their own area of expertise—even though those details are neither required for understanding nor relevant to the decision at hand. All of this makes meetings longer than they need to be.
These dynamics are not always easy to prevent, but a few simple principles can make a significant difference.
A meeting needs a clear purpose, but so does every agenda item. Is the goal to inform? Gather feedback? Make a decision? Ask for support? Grant approval? Adding a dedicated column to the agenda template—“What do you need from the group?”—creates clarity before the meeting even begins.
When the purpose is simply to inform, the level of detail matters. If presenting a topic is likely to take more than ten minutes while several other agenda items still need attention, consider using an asynchronous format or scheduling a separate session with the people who actually need the information.
Another useful practice is the 60-second rule. Every agenda item begins with a concise one-minute summary covering the essential context, why it matters, and what the presenter is asking from the group. The maximum time allocated to the topic is defined in advance in the agenda. Only then does the team decide whether the discussion deserves a deeper dive within that time frame. If additional time is required, the topic can be moved to a dedicated follow-up discussion.
Micromanagement can also be addressed with a simple rule: details should only be explored in the larger group when they are necessary for a shared decision, a significant risk assessment, or an important dependency. Otherwise, the responsibility stays with the topic owner. A moderator can redirect the discussion simply by asking: "Do we actually need this level of detail to make today's decision?"
Regular team meetings also offer opportunities to improve collaboration. If everyone brings their own agenda items, rotating the role of meeting host can work remarkably well. Responsibility for preparation, facilitation, and documenting outcomes no longer rests with one person but becomes a shared team capability. With the possible exception of the team lead, everyone should take a turn.
Rotating the order of agenda items is equally valuable. When meetings always start with the same people, those whose topics appear later on the agenda are far more likely to run out of time whenever earlier discussions overrun. Even the order of an agenda influences visibility and priorities.
If certain topics repeatedly need more time than planned, consider reserving a dedicated deep-dive slot at the end of the meeting. Before moving into that session, decide who actually needs to stay. This prevents one topic from consuming the entire agenda while avoiding unnecessary time commitments for colleagues who have nothing to contribute to the discussion.
When agendas are consistently overloaded, extending the meeting is rarely the best answer. Teams with a high demand for ongoing coordination may benefit more from short, 15-minute sync meetings several times a week. Whoever is working and available joins. The higher frequency compensates for the fact that not everyone will attend every session.
Time tracking is just as important in these meetings. The tight time frame naturally encourages everyone to focus on what matters most. At the same time, it creates visibility into who is working on what, where dependencies exist, and where further conversations are needed. The goal is not to resolve every issue during the sync meeting. It is to share information efficiently and identify coordination needs early, so they can be addressed in dedicated follow-up discussions.
What all of these approaches have in common is that they go far beyond improving meetings. They shape how responsibility is shared, how information flows, how expertise is respected, and how teams work together.
That is why improving meeting culture is, in many ways, organizational development at its smallest scale.