User Tools

Site Tools


programmingops

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
programmingops [2014/05/08 16:07] – Added additional improvement for revisiting warnings. maraprogrammingops [2017/01/14 14:24] (current) – external edit 127.0.0.1
Line 6: Line 6:
  
 ==== Areas for Improvement / 2015 Recommendations ==== ==== Areas for Improvement / 2015 Recommendations ====
 +  - Replace printed name tents with dry erase name tents (Example: http://www.trainerswarehouse.com/Original-Reusable-Name-Card-dry-erase-tents-LARGE/productinfo/TCLA/) that are left in each room for the duration of the weekend.  ROI would be greater than 1 year based upon 2014 printing costs.  A method for securing in each room, or collecting following the last scheduled event each day would need to be put in place.
   - Have ProgramOps do room scheduling in advance of the convention rather than Programming.  This would create more accountability for issues during convention, and ensure that the people receiving complaints would be able to prevent them recurring in future conventions.  Example: Numerous complaints received during convention due to proximity of musical performances and panels, and multiple requests for projectors.  ProgramOps received complaints, but could not do anything about it at that point.\\    - Have ProgramOps do room scheduling in advance of the convention rather than Programming.  This would create more accountability for issues during convention, and ensure that the people receiving complaints would be able to prevent them recurring in future conventions.  Example: Numerous complaints received during convention due to proximity of musical performances and panels, and multiple requests for projectors.  ProgramOps received complaints, but could not do anything about it at that point.\\ 
   - Standardize A/V available in each room.  Ideal would be to have a projector and microphone in each room, but this is likely cost prohibitive. Have groups of rooms designated for panels (which typically don't need a projector), and group of rooms that are for individual speakers (which typically do need a projector).  Grouping rooms together by location simplifies the rescheduling process, and facilitates answering questions from speakers who are trying to confirm they will have the expected A/V equipment.\\   - Standardize A/V available in each room.  Ideal would be to have a projector and microphone in each room, but this is likely cost prohibitive. Have groups of rooms designated for panels (which typically don't need a projector), and group of rooms that are for individual speakers (which typically do need a projector).  Grouping rooms together by location simplifies the rescheduling process, and facilitates answering questions from speakers who are trying to confirm they will have the expected A/V equipment.\\
Line 29: Line 30:
    
 ====== Program Ops Responsibilities  ====== ====== Program Ops Responsibilities  ======
-The Program Ops person is a staff member on the Operations (Ops) team who handles the direct operational running of the convention. Program Ops responsibilities include ensuring all convention events start & finish on time, providing real time updates to the schedule during the convention if event times or locations are changed, counting attendance at all scheduled events, and publishing the same immediately after the convention.  Prior to the convention, the Program Ops person is responsible for printing and assembling speaker/presenter packets, room schedules, and all materials needed by Program Ops during the convention.\\ +The Program Ops person is a staff member on the Operations (Ops) team who handles the direct operational running of the convention programming. Program Ops responsibilities include ensuring all convention events start & finish on time, providing real time updates to the schedule during the convention if event times or locations are changed, counting attendance at all scheduled events, and publishing the resulting data immediately after the convention.  Prior to the convention, the Program Ops person is responsible for printing and assembling speaker/presenter packets, room schedules, and all materials needed by Program Ops during the convention.\\ 
  
 ===== Required Skills & Availability ===== ===== Required Skills & Availability =====
Line 90: Line 91:
   - Request green room information from the head of Hospitality for inclusion in GoH welcome letters.\\    - Request green room information from the head of Hospitality for inclusion in GoH welcome letters.\\ 
   - Request a list of GoH liaisons from the appropriate department head.\\    - Request a list of GoH liaisons from the appropriate department head.\\ 
-  - Request a copy of the official map to be put in the scheduling book from the person responsible for the program book.\\+  - Request a copy of the official map to be put in the scheduling book from the person responsible for the program book. Modify as needed to use for individual participant maps.\\
   - Update the welcome letters to reflect current green room & liaison information.\\    - Update the welcome letters to reflect current green room & liaison information.\\ 
   - Generate samples of the information that will be provided in each packet and provide to the heads of Ops, Programming, and Hospitality for review.  This should include a sample of each of the following:\\    - Generate samples of the information that will be provided in each packet and provide to the heads of Ops, Programming, and Hospitality for review.  This should include a sample of each of the following:\\ 
programmingops.1399565270.txt.gz · Last modified: 2017/01/14 14:24 (external edit)