Services Cluster: Difference between revisions
Filled out from previously submitted form |
Tab's updates |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
== Contact Info == | |||
* Core email: service@fireflyartscollective.org | |||
* Included in the planning@fireflyartscollective.org mailing list with all cluster and core leads | |||
* Included in the festival@fireflyartscollective.org mailing list with all of Exec cluster and all cluster leads | |||
== Service Cluster Lead Responsibilities == | == Service Cluster Lead Responsibilities == | ||
The Service Cluster coordinates the cores that support our participants! | The Service Cluster coordinates the cores that support our participants! | ||
* Gnome Core | * Gnome Core <gnomes@fireflyartscollective.org> | ||
* Coffee Core | * Coffee Core <coffee@fireflyartscollective.org> | ||
* Sanctuary Core | * Sanctuary Core <sanctuary@fireflyartscollective.org> | ||
* Accessibility Core | * Accessibility Core <accessibility@fireflyartscollective.org> | ||
Lead responsibilities: | Lead responsibilities: | ||
* Attend biweekly Festcomm meetings January-July (can be remote) | |||
* Identify and fill any key vacancies in the above-listed cores prior to event, working with Volunteer Coordinator as needed | * Identify and fill any key vacancies in the above-listed cores prior to event, working with Volunteer Coordinator as needed | ||
* Communicate with core leads throughout planning; ensure they are empowered to successfully lead their cores. | * Communicate with core leads throughout planning; ensure they are empowered to successfully lead their cores. | ||
| Line 14: | Line 21: | ||
* Check in with cores & provide updates at daily meeting during the event. | * Check in with cores & provide updates at daily meeting during the event. | ||
* Participate in after-burn activities/planning for next year. | * Participate in after-burn activities/planning for next year. | ||
* Field and direct questions and communication as needed between and around cores | |||
* Print volunteer instructions for all cores to take to the event and have at Gnomes | |||
== Who makes a good Service Cluster Lead? == | == Who makes a good Service Cluster Lead? == | ||
=== Location === | === Location === | ||
Can be done from anywhere, though it's useful to attend a Work Weekend to take inventory. | |||
=== Schedule === | === Schedule === | ||
Biweekly meetings throughout Planning Season (January-July), plus occasional follow-up for after-burn activities. | |||
Most responsibilities are asynchronous communication that can be done whenever you want, as long as you hit deadlines. Hitting deadlines requires lead time because the work is always about getting other people to do things, not just staying up late to do it yourself. | |||
=== Experience === | === Experience === | ||
Some familiarity with the relevant cores is helpful, but not required. | |||
=== Skills === | === Skills === | ||
* Strong interpersonal communication | |||
** The majority of our work is asking people to accomplish tasks and communicating between different groups of people which requires some ability to work with different personalities, communication styles. | |||
* Clear, concise, persuasive writing | |||
** We need to be able to stay on top of email as there is significant email communication with core leads and with the rest of festcomm and be able to directly and kindly state tasks that need to be done. | |||
* Time management | |||
** As a cluster lead, we're responsible for ensuring our cores have their budgets, resources, and communications delivered on time. | |||
== Timeline == | |||
=== January === | |||
* Reach out to core leads to determine who is returning and solicit potential replacements | |||
* Start attending Festcomm meetings | |||
=== February === | |||
* Work with [https://wiki.fireflyartscollective.org/wiki/Volunteer_Coordinator volunteer coordinator] to recruit new leads for any cores that need them | |||
* Conduct core or cluster specific onboarding | |||
* Cluster budget template shared- notify cores of March 15 deadline | |||
=== March === | |||
* '''Budget submissions due: March 15''' | |||
* All-hands planning meeting late March/beginning of April | |||
* Finalize core recruitments and onboarding | |||
=== April === | |||
* Ticket lottery opens | |||
=== May === | |||
* Cores begin work on updating volunteer shifts | |||
=== June === | |||
* Glowbe announcement to recruit volunteers for cores, volunteer portal opens | |||
* Cores begin recruitment for volunteers | |||
=== July === | |||
* Gear/supply staging for cores | |||
* Last volunteer signup (close Sunday before event for printing) | |||
* Event: July 4th weekend | |||
* Teardown: immediately post-event | |||