A business meeting only works when its format fits its goal. A brainstorm run like a status update kills ideas, and a decision meeting run like a brainstorm never reaches a decision. This guide covers the 10 types of meeting most businesses run, what each is for, how long it should take and how to keep it useful.
For scale, Harvard Business Review reports that executives spend nearly 23 hours a week in meetings, up from less than 10 hours in the 1960s. Choosing the right type, and running it well, gives a lot of that time back.
What is a business meeting?
A business meeting is a gathering of people who come together to share information, solve problems or make decisions about work. It can be in person, virtual or hybrid, and formal or informal, from a 10-minute daily stand-up to a full-day planning session. What every good one shares is a purpose: something should move forward by the end.
Quick guide: which meeting type do you need?
| If you need to... | Run a... | Typical length |
|---|---|---|
| Keep a team aligned on priorities | Monthly team meeting | 30 to 60 minutes |
| Surface blockers fast | Stand-up | Up to 15 minutes |
| Track progress against goals | Status update meeting | 30 minutes |
| Fix something that has gone wrong | Problem-solving meeting | 45 to 60 minutes |
| Reach one clear decision | Decision-making meeting | 30 to 60 minutes |
| Generate options | Brainstorming meeting | 45 to 60 minutes |
| Set long-term direction | Strategic management meeting | Half a day or more |
| Start a project well | Project kickoff meeting | 60 to 90 minutes |
| Help people get to know each other | Introductory meeting | 30 minutes |
| Let leaders answer employee questions | Town hall meeting | 45 to 60 minutes |
The lengths are common starting points rather than rules. Shorten any meeting that finishes early.
The 10 types of meetings in business
1. Monthly team meetings
A monthly team meeting is a recurring check-in where a team reviews progress, assigns upcoming work and agrees priorities. It earns its place when there is more to cover than a quick stand-up allows. The usual failure is turning it into an information dump: if everything shared could have been an email, send the email and keep the meeting for blockers, decisions that affect several people and changes of direction.
Do not confuse it with an all-hands meeting, which brings the whole company together, usually led by senior leadership, rather than a single team.
2. Stand-up meetings
A stand-up, also called a daily scrum, is a short daily check-in held in under 15 minutes. Atlassian describes it as a quick round-robin where each person answers three questions: what did I accomplish yesterday, what will I do today, and what is blocking me. The time limit keeps it a coordination tool rather than a status report. Stand-ups suit teams working on a shared project day to day. For distributed teams, a written stand-up in a shared channel can do the same job without the scheduling.
3. Status update meetings
Status updates usually happen weekly and track progress against specific goals. Unlike a stand-up, the question is whether the project is on track, where it is ahead or behind and what that means for the next milestone. Keep it structured: everyone reports in the same format, and anything that needs real discussion gets its own meeting so a 30-minute update does not become an unplanned hour.
4. Problem-solving meetings
These are called when something has gone wrong, or is about to, and a group needs to diagnose it and agree a fix. They are often unplanned and may pull in people from several departments. Focus on the problem, not on blame, and finish with an agreed solution, a named owner and a deadline. Send the relevant data beforehand so that everyone starts from the same picture of what the problem actually is.
5. Decision-making meetings
A decision-making meeting exists to reach one decision that needs input or authority from several people. Invite everyone whose sign-off is required, and nobody else. Write the decision as a single question before you schedule it: "Should we move the launch from Q3 to Q4?" is a decision meeting, while "What do we think about the launch timeline?" is not. Afterwards, record the decision and the reasoning so that it is not reopened months later.
6. Brainstorming meetings
Brainstorming meetings generate ideas; evaluating them comes later. When both happen at once, the instinct to judge suppresses the ideas, and you are left with a short list of safe suggestions. Spend the first part producing ideas without comment and the second part grouping and ranking them. A live word cloud or open-ended slide lets quieter people contribute at the same moment as everyone else, instead of waiting for a gap in the conversation.
7. Strategic management meetings
Strategic meetings are where senior leaders review long-term direction, assess performance against strategic goals and set priorities for the coming quarter or year. They are typically quarterly or annual and need real preparation: share pre-reading at least 48 hours ahead so the discussion is not superficial. The output should be a clear list of priorities and decisions, not a list of things to "explore further". There is more detail in our guide to the strategic management meeting.
8. Project kickoff meetings
A project kickoff meeting marks the official start of a project. It brings together the project manager, the team and the stakeholders to cover what the project must achieve, who is responsible for what, how the team will communicate and what success looks like. It is also the cheapest moment to surface assumptions and risks, before work has built momentum in one direction.
9. Introductory meetings
An introductory meeting happens when someone joins a team, when two groups begin working together or when a person moves into a new role. The aim is to build the relationship: backgrounds, working styles and expectations. Open-ended chat tends to fizzle, so give people something concrete to talk about, such as a short question or a small shared task.
10. Town hall meetings
A town hall meeting is a planned company-wide or department-wide session in which leaders share updates and answer questions from employees. Wikipedia notes that the format is modelled on the New England town meeting, which dates from the 17th century, but that attendees of a town hall do not vote on binding decisions. The value is transparency and two-way communication, and that depends on the Q&A being real. Pre-screened softball questions defeat the purpose, so give employees an anonymous way to submit questions before and during the session.
How to run any type of meeting well
The format changes across the 10 types, but the habits that make a meeting worth attending stay the same.
- Define the purpose before you schedule. Can you say what decision will be made, what information will be shared or what problem will be solved? If not, the meeting is probably not needed yet.
- Share an agenda. A meeting agenda keeps the discussion on track and lets people prepare. A list of topics with a time against each is enough.
- Invite the right people. Include those whose input or authority is needed and send everyone else the notes.
- Give each topic its time. Allow longer for complex items, stick to the schedule, and add a short break in anything over an hour.
- Make it interactive. A meeting where one person talks and everyone else listens loses attention quickly. Live polls, quick Q&A and open-ended questions keep people taking part. The free AhaSlides plan supports up to 50 participants, which covers most team meetings.
- Record decisions and follow up. Minutes need only capture the decisions made, the actions assigned, who owns each and by when. Send them within 24 hours, then ask for feedback so the next meeting improves.
Common mistakes to avoid
- Using the wrong type for the goal. Decide what output you need, then pick the format that produces it.
- Inviting too many people. Large rooms slow decisions and reduce how much each person engages.
- Skipping the follow-up. A decision that is not written down has the same effect as no decision.
- Letting recurring meetings run on autopilot. Every few months, ask whether the meeting still serves its original purpose. If not, cancel it or change the format.
Frequently asked questions
Why are meetings important in business?
Meetings let information, ideas and feedback travel up and down an organisation, and they are the quickest place to align people on a decision.
What meetings should a business have?
Most businesses run a mix of all-hands meetings, leadership meetings, team meetings, project meetings and one-to-ones, plus function-specific sessions such as sales, marketing, finance and hiring reviews, training sessions and client meetings. Start with the 10 types above and add others only where a clear purpose calls for them.
How long should a business meeting be?
As short as the purpose allows. Stand-ups should stay under 15 minutes, status updates and decisions around 30 minutes, and only strategic or planning sessions should run to half a day or more.
What is the difference between a stand-up and a status update meeting?
A stand-up is a daily, very short check-in on individual tasks and blockers. A status update is usually weekly and looks at whether a whole project is on track against its goals.
