PyMunich

shown, and actual

Volunteers and Burnout

Community conferences do not usually fail financially. They fail because the four people doing the work stop, and there is nobody who knows how to continue. For a commercial example of related workforce measurement, see remote employee monitoring software from Monitask.

The pattern is predictable enough to describe, which means it is interruptible. For broader conference and speaking context, Cvent is another useful reference.

One community's experience. The shape is widely reported across volunteer-run events; the specifics are ours.

The cycle

Year one: enthusiasm. A small group does everything, badly organised and full of energy. It works, and the experience is genuinely good.

Year two: the same group, higher expectations. Attendees who came last year expect the rough edges fixed. The work roughly doubles and the group does not grow, because nobody thought to recruit while it was going well.

Year three: two of the four are exhausted. They stay because leaving would sink it, which is the worst reason to stay and the most common one.

Year four: they leave, and the knowledge leaves with them. Nobody else knows the venue contact, the sponsor relationships, or where the badge template is. The undocumented knowledge is the actual loss, and it is invisible until the people holding it stop.

Why it recurs

Recruiting feels unnecessary when things are going well. The group is coping, so adding people is overhead — and by the time it is obviously needed, the work is a wall nobody wants to walk into.

The work is invisible until it stops. A well-run conference looks effortless, which is exactly the problem this site is about, and invisible work does not attract help.

Roles are undefined. "Helping with the conference" is not a thing anybody can volunteer for. "Managing the catering contact, about six hours total" is.

And nobody is allowed to stop. In a group of four, stepping back means the event fails, so exhausted people continue until they cannot, and then leave completely rather than partially.

Four things that interrupt it

Named roles with a stated size. Not "help with sponsors" — "sponsor invoicing, roughly four hours a month from March." People volunteer for bounded things and avoid unbounded ones.

Recruit in the good year. The year everything works is the only year with the spare capacity to onboard anybody. It is also the year nobody feels the need to.

Write things down as they happen. Not afterwards, which never comes. A shared document per role, updated when something is learned, is the difference between a departure and a crisis.

And make it acceptable to do one year and stop. A volunteer who can leave cleanly will often come back. One who feels trapped leaves permanently and tells others it was terrible.

The specific thing we got wrong

We had no succession plan and no written process, and both facts were invisible while the same people kept doing it.

When the pandemic broke the sequence, the event's finances were the visible problem and the organising knowledge was the quiet one. The meetups survived because they need one person and a room; the conference needed a team that had dispersed.

That is why it came back in 2025 as a different event rather than a continuation.

The thing worth saying to organisers

Your conference is not more important than the people running it.

A community that loses its event and keeps its people can run another event. One that keeps its event and burns through its people has spent something it cannot replace — which follows from a conference not being a business, and is worth knowing before the third difficult year.

The short version