4 Gathering your people
This chapter covers
- Assembling your team of organizers
- Deciding on who your participants should be
- Revisiting access and where you want to store extra information
- Sending a bug bash announcement
Bug bash is an event for people, by people. You’ll need to gather your organizing team to support you, and also think more strategically about your participants. Once you know this, you’ll be able to prepare promotional materials and send out a well-organized announcement to invite people in.
4.1 People behind the bug bash
A significant part of the bug bash event’s success is having active, enthusiastic, and caring individuals in two roles: organizers and participants. Let’s explore how to identify your supporters and participants and get them involved.
4.1.1 Get your organizer team together
Even if you are the main organizer of the bug bash and can handle many tasks alone, you don’t have to. Learning what to delegate, to whom, and how will make it a smoother, better-planned event.
You know your stakeholders and have leadership’s approval for organizing a bug bash; it’s time to get to know your allies. How do you recognize them? What’s the difference between stakeholders and allies?
Allies
are individuals who support your idea and are willing to provide backing, hands-on help with preparing and/or running the event, or simply advocating for it.