Build a Better PyCon My Annual Reflection
summary
Three co-organizers run nine teams (program, ops, design, web, marketing, sponsor, engagement, AV, HR) and scale from 11 to 40 organizers to move a single-day event into a four-track conference with ~300–400 attendees; repeated failures come from unclear task ownership, upstream/downstream dependencies and burnout. Remedies that worked: regular meetings with action items and deadlines, a single repository for docs, 11 practice meetups, shadowing and office hours (2 hrs/week), genAI as a productivity filler with a no PII rule and red/amber/green status tracking.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:11Volunteer journey
- 3:40HK teams structure
- 4:48PyCon HK 2025 goals
- 5:10Conference retrospective
- 7:17Clear roles
- 8:24Team tasks breakdown
- 10:51Volunteer management styles
- 11:34Project management
- 13:26AI for planning
- 14:51Meetups as training
- 15:52Transparency and communication
- 17:16One-on-one meetings
- 18:23Handling urgent issues
- 20:31Humble leadership
- 21:34Negotiation timing
- 22:18Project management techniques
- 23:44Career growth
- 25:33Organizer challenges summary
- 26:01Q&A
related talks
39mLocal Community Building
34mBecoming a team, one pixel at a time
15mGrowing at Work with Community-oriented Development
46mRunning with Scissors: Open Source Team Dynamics
52mToo many cooks! Supporting augmented teams without getting salty
31mProductionalizing a Data Science Team
23mManaging diverse engineers for high-impact deliveries
46mLeading Distributed Teams