Tuesday, 14 December 2010 11:05

How Do You Get Team Members to Come Prepared to the Meeting?

Written by 
Rate this item
(1 Vote)

The Problem:

We've all attended meetings where participants were asked to read a document, do some research, or conduct some other "homework" prior to the meeting but very few people actually did it. Obviously, the intent of assigning the pre-work is to ensure that all attendees are prepared which should result in a quick, efficient meeting... right???? Wrong!!! Too often some attendees don't complete the assignment as requested which drags down the entire group. Before you lead your next meeting, consider these tips about assigning pre-work.

Consider these suggestions....

  • Give the group a choice about how to complete the prep (either outside or within the meeting). You might say, "Everyone will need to review the requirements document prior to our review discussion. We can either do it as a group and plan to meet for a full day or everyone can review it offline, and the group will meet for 2-3 hours to discuss changes. Which approach does the group prefer?" Most groups will opt for the shorter meeting. This technique tends to work because the group was given the option to review the document during the meeting and they chose not to do that.
  • Assign specific team members to lead certain sections of the meeting (which would require them to have completed the pre-work). When they know they will be asked to lead discussion, attendees are much more likely to have done their homework. No one wants to appear unprepared!
  • Try to keep the pre-work brief. The more complicated it is, the less likely attendees are to complete it.
  • Ask team members to email you either a list of questions or comments on the pre-work several days prior to the meeting. This acts as a confirmation to let you know that they have indeed reviewed the document. If you don't get feedback from someone on the team, place a call to them asap to request their feedback.
  • Give attendees ample time to complete the pre-work. If you ask them to review a lengthy document 3 days prior to the meeting, it may not provide ample notice. Ideally, let the team select the due date for completion of the pre-work. This buy in significantly increases the likelihood of compliance.
  • Discuss the issue of attendees not being prepared during the meeting debrief, and encourage the team to identify approaches to address the issue (e.g. incentives, "punishments", etc.)

Don't forget to leave your comments below


Dana Brownlee is President of Professionalism Matters, Inc. a boutique professional development corporate training firm. Her firm operates www.professionalismmatters.com and www.meetinggenie.com, an online resource for meeting facilitation tips, training, and instructional DVDs. Her latest publications are "Are You Running a Meeting or Drowning in Chaos?" and "5 Secrets to Virtually Cut Your Meeting Time in Half!" She can be reached at This email address is being protected from spambots. You need JavaScript enabled to view it. .

Read 4126 times Last modified on Tuesday, 27 March 2012 13:46

Comments  

 
0 # Paul Genuario 2010-12-16 00:18
Dana, The only issue I have with your recommendations is that often projects are executed at Mach 5 and requirements development time is squeezed (wrongly so, but reality none the less). I completely agree with your suggestions “when you have the time”. I would like to add a recommendation that I have found of use in the more adrenaline rushed organization. That is many frequent small meetings. For some reason the one hour meeting is easier to schedule, especially when the project team consists of many partial heads that have other project commitments they are multi-tasking between. Secondly, action item status can be reviewed frequently in a public meeting forum where the “assignee” must convey his tardy rational before their peers… I find this quite motivational in and of itself (also provides more timely options to the BA; i.e. re-assigning, escalation). And thirdly; agenda’s can be tailored to not require all project stakeholders (greater chance of scheduling meetings with all attendees). Th is requires BA’s to be savvy at partitioning his meetings, send out more frequent requirements updates and more dynamic action status. But it works.
Reply | Reply with quote | Quote
 
 
0 # Christine Haggarty 2011-02-09 03:35
People are busy and your meeting prep may have slid down on their priority list. Don't forget the old-fashioned but highly effective tactic of dropping by their workstation for an informal "how's it going" prompt. If they have questions or concerns, it gives them an off-line opportunity to talk to you about them. The good-will you generate may be enough to spur them to move their prep work up in their list of priorities!
Reply | Reply with quote | Quote
 

Add comment