Organizers To Do List

This is the current list of tasks for the IPG organizers.

Travel

• Send travel and accommodations email to participants. Include a note to remind participants that some limited amount of sponsorship is available, if needed. (Zak)
• Organize travel and acc. for participants that MoFo is sponsoring (Zak)

• Catch up with those who don't respond to our organization emails

Agenda and Activities

• Finalize schedule (Zak)
  • Send draft to rest of team (Zak)

• Draft guidelines for presenting an edge case. (Zak)

• Solicit edge case presenters (after schedule is finalized) (Team)

Orientation

• Write participants to encourage them to get an early start on the symposium. Drop them a mail that encourages them to:
  • write up a few brief notes on their interest in the symposium
  • adopt a session as coordinator
  • present an edge case

• Send out an orientation email for participants. Include:
  • schedule and a list of activities at the symposium
  • a set of questions to get people thinking about the issues at the symposium
  • maps and travel directions
  • the outcomes we hope to have from the event
  • a request for ideas on what tangible things the event could lead to
  • a request to blog about the event before they attend
  • suggestions on how to get the best from the event
  • notes which parts of the event are public and which are private private aspects of the event. In other words, let people know to what extent their comments, presentations, etc., will be made public, and to what extent they can engage in more private off-the-record discussions.

General Logistics

• Get all participants wiki accounts
• Find delivery joints
• Decide if the evening breakouts are at the HBS or at the Charles
• Find out what room(s) we will have at HBS
• Organize coffee breaks and lunch
• Catalogue A/V resources at HBS
  • Can we easily record sessions?

Event Materials

• Badges
  • Create draft badges (Zak)
  • Discuss with group (Zak)
  • Get attendee info for badges
  • Make/print final badges

Followup

• we should draft a followup message for the event