Season Hosting Team Guidelines
Team purpose
To understand the needs of the community forming around a season and support the participants to design and run a peer-to-peer programme of education, support, inspiration, mutual aid, accountability, and getting things done.
A season is successful if
- Participants receive tangible support for working on stuff that matters
- Participants deepen skills and habits of helping other people in the node succeed
- Participation is high and a wide number of people host sessions and activities
- Most folks are keen to participate in another season
Role
The role of the hosting team is to host the season — they don’t need to run everything. They are here to:
- Understand the needs of the individuals and community as a whole
- Help people orient themselves in the community
- Facilitate key sessions and activities of the season
- Pay attention to the vibes
The workload should be light, with the season for the hosting team starting a few weeks earlier and finishing a week later. Additional work during the season should be no more than 1–2 hours per week.
Key tasks
Pre-season
- Send out season invite
- Collect and share applications with node members
- Curate invitation process for new members
In-season
Done by hosting team:
- Facilitate key sessions (Opening, Closing)
- Maintain a schedule of sessions and activities
- Attend bi-weekly hosting team sensemaking calls
- Participate in season hosting async chat
Ensure it happens (don’t necessarily have to do it yourself):
- Onboarding programme for new members is delivered
- Documenting, harvesting and storytelling (both retrospective and prospective, internal and external)
Post-season
- Gather feedback from season participants
- Recruit next season hosting team
- Liaise with Enspiral Ops to onboard new members to the node
- Coordinate necessary updates to this handbook (but not responsible for making the updates themselves)
Last updated on