"Sometimes deciding not to hold a meeting may be the best use of everyone's valuable time."
Few managers would disagree with that statement, which we found on the website of PPD Consultants. The engineering-services organization asks four questions to address the perpetual "to meet or not to meet" dilemma:
Strong examples: (a) to reach a decision; (b) to brainstorm for solutions to a problem; and (c) to promote a sense of accountability (by creating a public forum where one's work is on display for all to see, so people push harder to deliver).
Weak example: to gather status-only reports for areas of little activity.
It may be logical to postpone the meeting if required information is missing or a critical team member is unavailable. Don't be too quick on this trigger, however; you don't want to cancel necessary meetings.
Information-only debriefs, such as status updates, can be done through e-mail or other means. If the topics only involve two or three members, then an informal subgroup session may be wiser than an all-hands-on-deck meeting.
Before postponing a meeting, consider: What would not be accomplished? How would team members react? How would senior managers react? If people are telling you that nothing would be missed (or implying as much by their absence or lack of interest), then you have your answer, which should lead you to either cancel the meeting or find ways to improve it.