Meeting Management · Meeting Rules
Meeting Management
What is meeting management?
- Each type of meeting needs a different design
- Five elements: purpose, attendees, pre-reads, rules, and outputs
- Meeting minutes should record decisions and next actions
The first thing that changes when you fix how meetings run is not their length but the sentence the organizer writes. When 'Let's get together tomorrow at 3 about marketing' becomes 'By 3 tomorrow, we will finalize the second-half ad budget allocation,' who needs to attend and what to read beforehand follow naturally. Start from the deliverable, not the agenda. That is how this practice works. When a meeting has only an agenda, no one can say what was decided once it ends; with the deliverable written down first, failure becomes visible the moment it isn't produced.
In practice, teams start by sorting meetings into four types. Information sharing is the first candidate to move to documents and asynchronous channels. Decision-making requires a decision-maker and someone who holds a dissenting view. Idea generation works better with more people but must defer judgment. Problem solving centers on the practitioners who hold the data. Mixing two types in one meeting makes the formats clash. If you move from brainstorming to deciding, the loudest voice's proposal wins; if brainstorming starts in a session meant for deciding, the time just drains away. Once a decision meeting goes beyond 7 people, it tends to end in a show of consensus rather than a real decision, so it's better to make the extra attendees recipients of the results instead.
The nature of the minutes matters too. Verbatim transcripts get reread by no one; what should remain is three columns: decision, owner, and deadline. 'Agreed to look into it' is not a decision. Only when the minutes state who will review what by when, and where the result will be posted, does the next meeting avoid restarting the same agenda item from scratch. Count the number of re-raised agenda items, and you can see right away whether an organization's meetings are producing decisions or postponing them.
The most common misconception is treating meeting improvement as 'cutting time.' Trim 60 minutes to 30 and the meeting gets shorter, but decisions scatter into hallways and chat threads, and a shadow meeting appears, where someone has to brief the people who were left out, so total time actually goes up. Even when you cut attendees, if a decision summary doesn't go out the same day, the team lead who was dropped will overturn the decision next week. If you eliminate meetings without building a channel for information to flow through documents, the same meeting comes back to the calendar two months later under a new name.
Ara LimExpert in global leadership, AI, and business communication
John KimInstructor John Kim, author of B2B Marketing Design and CEO of Nanum ConsultingMeeting management has been studied in facilitation and organizational productivity research, and defining the purpose, attendees, and outputs in advance has become a standard approach in project management and Agile practice.
Consider a hypothetical case. Company A is an industrial parts manufacturer with 240 employees. When we pulled the calendars of its 20 team leaders and above, weekly meeting time averaged 11.4 hours per person, and HR interviews kept turning up comments like 'I only get 20 minutes between meetings to write reports.' The management support division then spent three months overhauling its regular meetings.
- When Kim, a team lead in corporate administration, downloaded the company calendar and sorted 37 recurring meetings by purpose, attendees, frequency, and annual hours, the figure that came out was KRW 380 million (≈ US$284,300) a year in labor cost.
- The CEO asked each organizer of the 37 meetings, 'What would immediately become a problem if this meeting disappeared?' No one could answer for 12 of them, and those were cancelled on the spot.
- The 9 information-sharing meetings moved to a shared document on Friday mornings, where team leaders write up progress, issues, and requests in 3 lines or fewer each, and the division head replies in comments.
- When the weekly production meeting was cut from 11 attendees to 6, Park from quality objected that 'we'll be left in the dark,' so the team set a rule to send a decision summary email by 6 p.m. the same day and opened 2 observer seats.
- They standardized the meeting-minutes template into three columns: decision, owner, and deadline, and had the division head send back any minutes that only said 'discussed.' "If the deadline column is empty, you didn't really hold a meeting" became the standard line.
- Three months later, weekly meeting time per team leader fell from 11.4 hours to 6.2 hours, and the number of agenda items raised more than once dropped from 18 to 5 per quarter.