Chairing a meeting

From apppm
Revision as of 21:54, 14 February 2021 by Asbkru (Talk | contribs)

Jump to: navigation, search

Contents

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. Having to many meetings can disrupt the flow of the project, and having to few meetings can make people uncertain of what to do. 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 project manager has to assign a person to take the minutes, so that it is possible later to review the minutes and see what were decided on the meeting. 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.

Big Idea

Application

Limitations

Annotated bibliography

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox