Types of Meetings and When to Use Each
Published on 25 June 2026
The Taxonomy of Meetings
Organizations run dozens of different meeting types without ever naming them. When you cannot name the type of meeting you are in, you cannot run it well, attend it well, or know when it should have been an email instead.
Here are the most common meeting types, what they are for, and how to run each one effectively.
1. Decision Meetings
Purpose: Reach a decision. Walk in with options, walk out with a choice.
Who should attend: Only the decision-makers and the people whose input is essential. Everyone else gets the output.
How to run it: State the decision to be made at the start. Review the options. Make the call. Document who decided what and why. This last part — the reasoning — is what prevents the same debate from resurfacing six months later.
TymitHub logs every decision with its timestamp and the speakers who contributed, so the institutional memory is automatic.
2. Problem-Solving Meetings
Purpose: Diagnose a problem and generate solutions. The output is a shortlist of options, not necessarily a final decision.
Who should attend: People with different angles on the problem — not just the people most affected by it.
How to run it: State the problem precisely. Separate diagnosis from solution (spend more time on the first). Time-box the ideation phase. End with next steps, not just ideas.
3. Status Update Meetings
Purpose: Share progress across a group. Useful when the updates are interdependent and people need to hear each other's news to make sense of their own.
Warning: This is the meeting type most likely to be replaced by an async tool. Before scheduling a status meeting, ask whether a shared document or a brief video update would serve the same purpose with less time cost.
4. Brainstorm Meetings
Purpose: Generate ideas without judgment. The goal is quantity and diversity, not evaluation.
How to run it: Establish the "yes, and" norm explicitly. Defer judgment. A facilitator helps. Capture everything — even the ideas that seem weak — because the best ideas often emerge from combinations.
5. Onboarding and Training Meetings
Purpose: Transfer knowledge from those who have it to those who need it.
How to run it: Structure matters more here than in any other meeting type. Use examples. Allow questions. Follow up with written documentation.
6. Formal Sessions (Board, Council, Committee)
Purpose: Fulfill a governance or legal obligation, make binding decisions, and produce an official record.
Who should attend: The formal members of the body, plus any required observers or presenters.
How to run it: Follow the agenda strictly. Record votes. Produce minutes that are accurate, complete, and issued promptly.
This is where TymitHub was built to help most. Every word spoken is transcribed, every decision timestamped, and the first draft of the minutes is ready the moment the gavel falls. See how it works for councils and boards.
Choosing the Right Format
Before scheduling any meeting, identify which type it is. Then ask: does this type of meeting actually need to be synchronous? Could a shared document replace it? Could an async video?
If you do need the meeting, let the type determine the structure — the right attendees, the right agenda, the right output.
