Starting a DevSoc chapter felt like standing at the bottom of a hill with a very loud committee. We had the energy. We had the Discord server. What we didn’t have as at then was a plan for turning enthusiasm into something that survived a semester and even multiple semesters. These are the lessons I’d pass to anyone about to run one.
The first event sets the pattern
We treated the first meetup like an exam we had to pass. We over-prepared, over-rehearsed, and worried about attendance numbers. Then a handful of people showed up and we ran the session anyway.
That small, honest session did more than a packed one would have. The people who came felt like they were part of something because we talked to them instead of at them. The trust we built in that room carried through the term. A chapter’s reputation forms in the first event, and consistency after that matters more than size.
People stay for the community, not the slides
The topics we taught got forgotten. The connections stuck. Members who came for a Python workshop kept coming because they found people to build with, to ask dumb questions without judgment and to share wins with.
We started measuring the wrong thing. Attendance numbers, event count, engagement metrics. What actually grew the chapter was the quieter stuff. The person who stayed late to help a beginner debug, the group that kept building together after a session ended. Feed that and the numbers could follow but what really mattered was the impact regardless of the numbers. Those who care deeply will definitely show up, this does not negate the fact that we should not follow up those who aren’t in line already, it just simply means taking the initative to do what needs to be done is super important.
You’ll burn out on planning events alone
For the first few months it plausible to be tempted with running everything, choosing the topics, booking the rooms(where applicable), chasing the speakers(where applicab,le) and making the slides. It could work until it won’t. Nobody can sustain that, and the chapter suffers when one person becomes the bottleneck.
The fix is delegation with trust. Every committee member got an area to own, including the freedom to run it their way. Topics got worse and then much better, because different people brought different strengths. A chapter run by a team outlasts one run by a leader.
Small and regular beats big and rare
We tried a grand hackathon before we were ready. Months of planning, and it took a toll on everyone. In hindsight the regular two-hour sessions did the heavy lifting. They built habit, familiarity and the community we needed before we could pull off the big thing.
Do the small thing weekly. The big event becomes possible when the small thing has already made the community.
What I’d do differently
Say yes to help sooner. Ask members what they want to learn, and let them shape the schedule. Keep a simple record of what we ran and what landed because hindsight is generous when you write it down and celebrate the small milestones out loud. The first member who got a contribution merged, the first workshop taught by a member, the first week where you didn’t plan the session and a member did.
Running a chapter is leadership through service. You’re not the star of the show. You’re the person who sets the table so others can shine. Do that well and the chapter grows itself.
If you’re thinking about starting a chapter in your city or institution, we’d love to help you get going. Find us on Discord or check out our start a chapter page.