Chairing a meeting

Revision as of 14:11, 21 February 2021

Abstract

In project management, an important but often neglected skill, is chairing an effective meeting. Having ineffective meetings is a waste of organizational resources and can also lead to the wrong decisions being made. As a project manager, or the person chairing the meeting, it is important to note that doing a good job starts before the meeting itself. This starts with determining the 5 W's: who (should be a the meeting), what (should be discussed at the meeting), when (should be meeting be), where (is the meeting held) and why (are we having this meeting). During the meeting the focus is on making sure the meeting proceeds as expected. This includes following the agenda, making sure that sufficient discussion is allowed for each item, without also spending too much time either. It is also important that every person at the meeting gets a chance to state their opinion, so no person feels they are left outside the decisions. The work of the project manager is not done when the meeting concludes. After the meeting the project manager has to make sure that the decisions taken in the meeting are actually carried out after the meeting. This also includes following up on tasks given to specific persons in the meeting and ensuring they are done as planned.

Contents of article:

- Short explanation of the relevancy

- What to do before the meeting

- What to do during the meeting

- What to do after the meeting

- Mistakes to avoid

Key references:

https://www-emerald-com.proxy.findit.dtu.dk/insight/content/doi/10.1108/00197850310463751/full/pdf?title=chairing-developing-a-key-skill

https://emj-bmj-com.proxy.findit.dtu.dk/content/14/2/119

https://www-tandfonline-com.proxy.findit.dtu.dk/doi/pdf/10.3109/01421598909146275?needAccess=true

https://www.targettraining.eu/the-why-when-where-who-what-and-how-of-the-meeting-agenda/

The Essential Managers Handbook

https://www.lifesize.com/en/video-conferencing-blog/types-of-business-meetings

No More Muddling Through Mastering Complex Projects in Engineering and Management

Portfolio Management: The standard for portfolio management

Program Management: The standard for program management

PMI Standard for Risk Management

Big Idea

When managing a project, portfolio or program, an essential requirement is communicating with relevant people. As a project manager it is important to make sure the projects become a succes through effective and efficient management. In order to make sure that the project is moving forward according to the planned schedule it is necessary for the people executing the project to know when and what they have to do. To do this many project managers use meetings as a tool to inform multiple members of the team at once, while also getting updates from the same members if things are not going to plan. However, if the meetings are not used properly by the project manager, they can be a waste of time and company resources and ultimately delay the project finish date as well as exceeding the expenses. While a project manager might have a focus on the larger aspects of the project, small things like having timely meetings and also not wasting time on meetings are essential for the big time schedules to go as planned. According to a 2012 survey done by the site salary.com, the number one reason for employees wasting time on work, was ineffective meetings. ^[1]. The same result was found in the 2013 study. ^[2]

While it might seem obvious that having good meeting practices will help the project forward, it is not always the case that companies follow that. Most people working have at some point or another complained that they are having too many meetings, that interrupt their work, while also complaining if they don't have enough information through meetings and feeling left in the dark. Good meeting practices is also something that is often not noticed when it works as it is supposed to, but when it does not work it creates a variety of problems.

This article will examine some of the good practices associated with chairing a meeting, but also the tasks to be done ahead of a meeting as well as how to proceed after the meeting has concluded. Most of the focus will though be on the things to do before and during the meeting since it has the most direct effect on the meeting. But without doing the proper work after the meeting, the meeting can become less valuable so that part will also be covered.

For this specific wiki article the perspective of a project manager is used, however many of the things explained here can also be attributed to managing a portfolio or a program.

Application

As outlined in the prior section, there is a lot of productivity to be saved by being able to conduct efficient meetings. This section will go through the best practices associated with productive meetings, while also discussing why it different meeting practices might be good for increasing the productivity. The section below this one will go through the limitations and downsides to the different meeting practices in order to give an allround view of the meeting practices.

Before meeting

In order to have a productive meeting, a lot of the work starts before the meeting is actually held. There are several things a project manager has to do and think about before the meeting is held. The first part is deciding on the basics of the meeting why is this meeting being held, who should attend the meeting, when and where should the meeting be held and what should be discussed in the meeting. These questions are based on the method five W's ^[3] which is used in problem solving, but here makes the project manager consider the practicalities of the meeting.

1. Why: "Why is this meeting necessary?" is the essential question to ask before planning a meeting, since if the meeting is not necessary the other practicalities does not matter. When considering if a meeting is necessary the project manager should consider the work hours that goes into the meeting. If there is an hour long meeting with 5 employees that is 5 work hours going into the meeting, which means the result of the meeting should be worth more than those 5 work hours.

When asking why the meeting is necessary, it should also be considered what type of meeting it is ^[4]. The type of the meeting also has influence on which employees should be invited, and therefore it should be decided early in the process. For status meetings especially the project manager should think whether it is necessary with a meeting, or if it could be accomplished by e-mail.

2. Who: In order to have a productive meeting, it is important to have the correct people as well as the correct amount of people at the meeting. If there is too many attending the meeting it might be less productive, and based on the work hours mentioned above, it might also be a waste of time for some of the people attending the meeting. If too few people are attending the meeting, there might be key information that is missing in order to make the correct decisions, while also possibly missing people who should be involved in making those decisions. So having the right number of key employees attending the meeting is imperative.

3. When: The meeting has to take place at a certain time, and this is also necessary to have decided before the meeting, so the attendees now when they have to attend the meeting. When deciding on the meeting start time, the project manager should also consider how long the meeting should be, and adjust accordingly, so a two or three hour long meeting is not put one hour before lunch.

4. Where: In line with "When" the place that the meeting is taking place is also important to communicate out to the attendees so they know where to attend the meeting at the specified time.

5. What: If the previous questions have been answered, the topic of the meeting should seem clear now. Nonetheless it is still useful to formally describe what the meeting should be about. This makes it easier to make the agenda for the meeting, while also ensuring that the meeting participants are on the same page regarding the topic of the meeting.

After answering the 5 W's, the project manager should have an idea of why the meeting is necessary, who should attend, where and when the meeting is as well as what the meeting is about. This leads to the next part which is setting the agenda for the meeting. Writing down the agenda makes it clear to the participants what they should expect for the meeting, the agenda should preferably be sent out before the meeting it self so the attendees has a chance to familiarize themselves with the agenda ^[5].

- Call the meeting

During the meeting

- Pick a secretary to write minutes

- Make sure that proper time is allocated for each item

- Make sure everyone are heard

After the meeting

- Make sure that the responsibilities and duties assigned during the meeting is carried out

- Consider when the next meeting should be

Limitations

- Every organisation is different

- Different fields require different meeting type

- Sometimes meetings doesn't go as planned

Annotated bibliography

References

1. ↑ https://www.salary.com/passages/why-how-your-employees-are-wasting-time-at-work/3/
2. ↑ https://www.salary.com/chronicles/2013-wasting-time-at-work-survey/
3. ↑ https://en.wikipedia.org/wiki/Five_Ws
4. ↑ https://www.lifesize.com/en/video-conferencing-blog/types-of-business-meetings
5. ↑ John S. G. Biggs (1989) Meetings: Twelve tips for chairing a new committee