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:
- Plan. Objective, audience, budget, and partner obligations captured in one template before anything gets booked.
- Run. A day-of runbook with an owner for every task, so nothing lives only in someone’s memory.
- Measure. A short post-event survey with the same core questions every time, so results compare across events instead of floating alone.
- Apply. One written paragraph: what the data says the next event should do differently. The loop only counts if it closes.
A finding I didn’t expect
Collaboration requests from other clubs and industry partners got dramatically easier to evaluate once each one was scored against member interest data instead of enthusiasm in the meeting. Some genuinely exciting proposals scored poorly and were declined. Attendance didn’t suffer at all, which was itself a finding worth writing down.
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.