Meeting Management

Frameworks for running meetings that justify the time they take and eliminating the ones that do not.

The Real Cost of Bad Meetings

Atlassian’s research found that the average employee attends 62 meetings per month and considers roughly half of them a waste of time. At an average fully loaded cost of $50 per hour per employee, a 60 minute meeting with 8 people costs $400. Run that meeting weekly with no clear outcomes, and you are burning $20,800 per year on a single recurring calendar event.

The problem is rarely that meetings exist. It is that meetings run without structure default to discussion, which feels productive but often produces no commitments, no documented decisions, and no follow through. The solution is not fewer meetings. It is better meetings: ones with a clear purpose, a written agenda, defined roles, and documented action items.

Types of Business Meetings and When to Use Each

Different meetings serve different functions, and confusing them causes most meeting dysfunction.

Decision meetings exist to make a specific decision. They should be small (3 to 6 people), have a clear decision framed in advance, and end with a documented outcome. If you leave a decision meeting without a decision, the meeting failed.

Information sharing meetings exist to update a group on status, plans, or context. All hands meetings, project status updates, and sprint reviews fall into this category. The test for whether an information meeting should be a meeting or an email is simple: does the information require real time discussion or Q&A? If not, send a written update instead.

Problem solving meetings exist to work through a specific challenge. Retrospectives, brainstorming sessions, and incident reviews are problem solving meetings. They need a clear problem statement, the right people in the room (those with relevant context), and enough time for genuine discussion, typically 45 to 90 minutes.

One on one meetings exist to build trust, provide feedback, and remove blockers between a manager and a direct report. They should happen weekly or biweekly, last 25 to 30 minutes, and be driven by the direct report’s agenda. The manager’s job is to listen, coach, and clear obstacles, not to give status updates.

Anatomy of a Meeting That Earns Its Time

Three elements separate effective meetings from calendar filler.

First, a written agenda distributed at least 24 hours in advance. The agenda should state the meeting’s purpose in one sentence, list 3 to 5 specific topics with time allocations, and identify who is responsible for leading each topic. If you cannot write a clear agenda, you are not ready for a meeting.

Second, defined roles. Every meeting needs a facilitator (keeps discussion on track and manages time), a note taker (captures decisions and action items in real time), and a decision maker (has final authority if consensus is not reached). Without these roles, meetings drift into unstructured conversation.

Third, documented outcomes. The last 5 minutes of every meeting should be dedicated to reviewing what was decided, who is doing what by when, and what the next step is. Action items without owners and deadlines are suggestions, not commitments. Send the meeting notes within 1 hour while context is fresh.

Meeting Documentation That Actually Gets Used

Meeting minutes and meeting notes serve different purposes and are often confused.

Meeting minutes are formal records of decisions, votes, and official actions. They follow a structured format (attendees, agenda items, motions, votes, action items) and serve as a legal or organizational record. Board meetings, governance meetings, and formal committee meetings require minutes.

Meeting notes are informal records of discussion, insights, and next steps. They prioritize speed and usability over formality. A good meeting note captures the 3 to 5 most important takeaways, documents every action item with an owner and deadline, and notes any open questions for follow up.

The most effective teams store meeting notes in a shared workspace (not buried in individual notebooks or email threads) so that anyone who missed the meeting can find what was decided. Tag action items with the responsible person’s name and integrate them into your task management system within 24 hours.

Content for this section is being built. Check back soon.

← Back to Productivity

Common Questions About Meeting Management

What should be included in a meeting agenda?
A meeting agenda should include the meeting purpose in one sentence, a list of 3 to 5 topics with time allocations for each, the name of the person leading each topic, any pre reading or preparation required, and a final slot for reviewing action items. Distribute the agenda at least 24 hours before the meeting so attendees can prepare.
How long should a meeting be?
Most meetings should be 25 to 50 minutes. Short check ins and one on ones work well at 25 minutes. Working sessions and problem solving meetings may need 50 to 90 minutes. Default to the shorter option and extend only if the agenda genuinely requires it.
When should a meeting be an email instead?
A meeting should be an email when the information flows in one direction with no discussion needed, when there are no decisions to make, or when the update can be understood without real time Q&A. Status updates, FYI announcements, and simple approvals are almost always better as written communication.
What is the difference between meeting minutes and meeting notes?
Meeting minutes are formal records of decisions, votes, and official actions used in governance and legal contexts. Meeting notes are informal records that capture key takeaways, action items, and next steps. Most day to day business meetings need notes, not minutes. Save formal minutes for board meetings and committee proceedings.
Try It Free

One app for work management

Projects, docs, goals, and tasks in a single workspace. Free forever.

Get Started with ClickUp →