WECS Community Operations
Community events direction for Women in Engineering & Computer Science at UVic. An operations pipeline for planning, running, and measuring events, with feedback loops that actually close.
The real deliverable
Student clubs run on goodwill and improvisation, which works beautifully right up until the person holding everything in their head graduates. As Community Events Director for WECS, my actual job isn’t any single event. It’s building an operations system that makes good events repeatable by whoever comes next.
Note 1The test I hold myself to: could someone run our next event from the documentation alone? If the answer is no, the documentation is the task.The pipeline
Every event runs through the same four steps.
Craft & budget
Pick the semester’s craft, source and purchase supplies against a fixed budget, and cap the spot count to what that budget actually covers.
NOTIONWednesday, day-of
Events run on a Wednesday. I build the playlist and personally assist attendees at their stations throughout, so nothing stalls waiting on one person.
IN PERSONPost-event survey
The same core questions every time, so results compare across events instead of floating alone.
FORMS → SHEETSApplied-learnings note
One written paragraph: what the data says the next event should do differently.
→ BACK TO STEP 01A finding I didn’t expect
One craft event per semester, always on a Wednesday, always capped by budget — and they still pull noticeably harder than most other WECS events.
I don’t run these through partnerships with other clubs or industry sponsors. The whole loop is mine: pick the craft, buy the supplies, build the playlist, and stand at the tables helping people finish theirs. Spots are capped by budget, not demand, which is exactly why the survey and the applied-learnings note matter: every semester’s craft has to earn its slot against a real constraint, not just against how fun it sounded in a meeting.
Why this one matters
This is the least visual project on this site and the most representative of the work I want to do: quiet systems, honest measures, and documentation good enough to hand to a stranger. It is also the kind of work whose value grows with scale, which is exactly why I intend to keep doing it.