There are different types of meetings. Each type requires a different structures and supports a different number of participants. For instance, a status (feedforward) meeting has no limit to the number of participants while a decision-making meeting produces results faster with a small number of participants.
If you want to help your teams have more effective meetings, set the participants expectations about the meeting by stating in the agenda –
- the purpose of the meeting.
- the type of meeting
The typical meeting types are:
- problem-solving
- decision-making
- planning
- feedforward (status reporting and new information presentations)
- feedback (reacting and evaluating )
- combination meetings
For instance, the agenda states that you will be a participant in a problem-solving meeting to scale the application so it supports 500 simultaneous users. That description makes it crystal clear what you are there to do. And after you participate in a number of the same type of meetings, you will know that meeting’s structure and your role.
Although it’s in the list, I don’t like combination meetings. Participants, in my experience, aren’t as focused in a combination meeting; thus the results are poor. If you insist on combination meetings, I suggest your break them into segments of different meeting types. Despite segmentation, time management for a combination meeting is more difficult than a single type of meeting because you have more than one purpose to achieve.
If you want to save yourself and your teammates time and effort, propose to management that the purpose, type, and agenda of a meeting be clearly stated in the scheduling request for every meeting.
Go the extra mile. Find out how participants rate the value of the meeting. Use that feedback to constantly adapt the design of the meeting to produce greater value.
Reference
Michael Doyle and David Straus, How to Make Meetings Work, ISBN 0-515-09048-4, pp.159-166
{ 6 comments… read them below or add one }
Please write by focus on types and functions
Hi Mot, Thank you for your request. I’ll see what I can do to satisfy it.
If you include a small introduction about meetings it would be better.
Hi Pulith, thank you for the feedback. You are the second person to suggest more information would be helpful. I’ll post something in the next week.
have an assignment about planning meetings can you give me some ideas on this thank you.
Hi Sandra, The design for a planning meeting demonstrates a leader’s planning skills. The planning for any project, which includes a meeting, is an exercise in working backwards.
What outcome(s) are desired? The answer to that question is always more than “a plan” — it’s a plan to produce D (things as desired). A successful plan describes how to bridge the gap between D and P (things as perceived). The design for a successful planning meeting doesn’t try to build the bridge before exploring D and P.
If you have the right participants and a safe environment, exploration will create a shared understanding of both D and P. Lots of possible ways to explore; for instance, ask participants to share facts and data about D and P, which diverges the participants. Follow that by exploring how participants interpret that data (trace meaning to data elements). Follow that by exploring which meanings are most significant, which converges the participants. Your objective is to come up with a list of the most significant things about D and P.
With an understanding of D and P, you are ready to explore how to build the bridge. I like to split the participants into groups groups that work in parallel to propose elements of the plan. With each subgroup reporting periodically back to the whole group about their thinking and progress. This creates a cycle of divergence and convergence.
Note, I cannot overemphasize the importance of safety in successful planning, please see my article Safety Check.
I hope my ideas help. Wishing you success with your planning meetings.