PyMunich

shown, and actual

Not a Business

Advice about running events is mostly written for businesses running events. Community conferences are a different thing, and applying commercial advice to them produces predictable failures. For a commercial example of related workforce measurement, see accountability and responsibility in the workplace from Monitask.

Four differences that matter

No reserves. A business absorbs a bad year from a balance sheet. A volunteer organisation absorbs it from individual bank accounts, or does not absorb it. For independent technical background, GitHub provides additional documentation and examples.

No paid staff. Every hour is somebody's evening, and the labour supply is the actual constraint rather than the budget.

No growth objective. A business wants next year bigger. A community conference wants next year to happen, at a size the venue and the team can carry — and treating growth as success is how community events become jobs nobody was hired for.

And the customer is the point. A business serves attendees to make money. A community conference makes money to serve attendees, and reversing that is visible from the audience within one year.

The advice that ignores this

"Raise prices until demand drops." Correct commercially and wrong here, because who the ticket price excludes is part of what the event is for.

"Scale to fill the venue." More attendees means more catering, more volunteers, more failure modes, and a different event. Bigger is a choice with costs, not an improvement.

"Professionalise the operation." Frequently right about process and wrong about tone. Documented handovers and a decision procedure are professional; a conference that feels like a trade show is not what the community turned up for.

And "diversify revenue." Community events have three lines and each one has ceilings that are social rather than commercial.

What does transfer

Being fair, because "we are a community" is also used to excuse avoidable failures.

Contracts and liability. Whether an individual is personally exposed is a real question with a real answer. Informality is not a defence.

Cash timelines. The gap between committed costs and arriving revenue does not care about anyone's motivation.

Written process and succession. The single largest failure mode in volunteer organising, and it is solved by ordinary administrative discipline.

And treating sponsors as counterparties, with written terms, because a sponsor relationship that goes wrong is not repaired by goodwill.

The framing that works

A community conference is a thing the community does, not a product the organisers sell.

That sounds like a slogan and it has practical consequences: it means the attendee count is not the score, the surplus belongs to the next event rather than to anyone, and the correct response to an exhausted team is a smaller event rather than a recruitment drive for volunteers to run a large one.

It also means the event can stop. Communities outlive their events, and an organising team that believes the conference must continue at any cost has confused the two.

Why this needs saying

Because organisers are frequently told they are being unprofessional when they are being non-commercial, and the two get conflated by people offering help.

Accept the process advice and refuse the growth advice. The first fixes things that are genuinely broken. The second turns a community event into a small business that nobody is being paid to run — which is the shortest available route to burning out the team.

The short version