For the team behind a recurring tech event, between editions
Crew ChartIf that person disappeared tomorrow, who runs their area?
List every role with its lead and backup, and every organizer with how they are doing. Free in your browser: the bus-factor map, lead first, who is doing the job of several people, who no longer enjoys it, undisclosed business interests, whether you need a legal entity, how decisions should split, how leaders hand over, and whether it is time for a first paid hire. A run writes the standing-team design, or the role cards for your charter.
1 The event and its team free
2 The team, as it operates free
What the page flags
The bus-factor map
Each organizer - load, answer, return
Entity, decision rights, succession, paid hire
3 Team design or role cards metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
How the team operates
Bus-factor map
Entity, decisions, succession, hire
Burnout
Conflict of interest
Checks
Record
Caveats
The page's check of this reply
4 Saved designs
How it works
The question behind every recurring event: if a person disappeared tomorrow, who could run their area next edition? Every role gets a named backup, the lead first. A person leading three roles, or running far over a few hours a month, is doing the job of several people - split the role rather than ask for more. Ask each organizer every year whether organizing is still pleasant; a no gets a structural answer this edition, and every organizer names what they get back - including business, as long as it is disclosed.
The first signed contract makes "no entity" a personal liability; a fiscal sponsor is the usual step for a conference, an own non-profit for an event meant to outlive its founders. Once there is money, a standing layer keeps contracts and finances while the operational team keeps the program. Rotating leaders only works over that layer, and the first paid hire, when the gate says so, is an event coordinator - never a community manager.