Pete: Created page with "== General Info == * Functional Chair of the the Festival Committee (FestComm) * Core email: lead@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 == Responsibilities == * Plan and execute biweekly Festcomm meetings January-July (can be remote) * Collaborate with Cluster Leads to det..."

2026-02-23T18:20:22Z

Created page with "== General Info == * Functional Chair of the the Festival Committee (FestComm) * Core email: lead@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 == Responsibilities == * Plan and execute biweekly Festcomm meetings January-July (can be remote) * Collaborate with Cluster Leads to det..."

New page

== General Info ==

* Functional Chair of the the Festival Committee (FestComm)
* Core email: lead@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

== Responsibilities ==

* Plan and execute biweekly Festcomm meetings January-July (can be remote)
* Collaborate with Cluster Leads to determine scope of work for each year's event
* Direct the volunteer organization towards its established goals
* Mediate inter-org conflict towards a mutually beneficial outcome
* Oversee any process changes inside the volunteer organization
* Strengthen connections between decision-makers and community subject matter experts

== Who makes a good Event Lead? ==

=== Location ===
Most work can be done remotely, but benefits strongly from an in-person element.

=== Schedule ===
Biweekly meetings throughout Planning Season (January-July).
Conversations as needed, based on requests from Cluster and Core Leads
Work weekend attendance is helpful, although not mandatory.

=== Experience ===
Significant experience with Burn-type events will be essential, experience with Firefly will be very helpful.

=== Skills ===
* Ability to maintain trusting relationship is paramount
* Empathetic, curiosity-focused communication skills are very helpful
* Growth mindset strongly encouraged
* Planning and running productive meetings
* Working
* Asking people to do work
* Writing in a way that is concise, direct, and persuasive

== Motto ==
"Nothing is static, everything is evolving."

== Timeline ==

===Phase 1: Assess Resources Ends: 3/8===
* "What is at our disposal?"
** Define Core Leads
** Draft budget (early)
** Determine Scope

=== Phase 2: Early Planning Ends: 4/12, All-Hands Meeting===
* "How will each core handle the basics?"
** Each core should have its own broad plan
** Identify, describe, and discuss any change in services
** Finalize Scope, Budgets

=== Phase 3: Fine-Tuning Ends: First Work Weekend===
* "What details need to be worked out?"
** Cross-core coollaboration
** Core meetings held
** Communications to community

=== Phase 4: On Site Ends: Main Gate opening===
* "How do we make our plans a reality?"
** Minimal to no process changes at this point
** Adjustment for unanticipated issues

Event Lead - Revision history