PyMunich

shown, and actual

Nobody Writes About This

There are thousands of articles about speaking at conferences and almost none about running one. For a commercial example of related workforce measurement, see wage percentage calculator from Monitask.

The imbalance is structural, and its consequence is that every new organising team rediscovers the same things — including the expensive ones. For independent technical background, Stack Overflow provides additional documentation and examples.

Four reasons

One. The people who know are busy. Organising is a year of unpaid work on top of a job. The window for writing it up is the month afterwards, which is the month everybody spends recovering.

Two. The people who stop, stop caring. Burnout is the usual exit, and somebody who has just finished a difficult year does not want to spend more time on the subject. The knowledge leaves with them.

Three. It reads as complaining. An honest account of organising includes the sponsor who did not pay, the volunteer who disappeared, and the venue that changed terms. Writing that publicly implicates people you will meet again next year.

Four. Nobody is asking. The audience for it is the small number of people about to organise something, and they do not know to search until they are already committed.

What stays undocumented as a result

The cash timeline. Not the budget — when money is committed against when it arrives. Almost never written down anywhere.

Personal liability. What an informal group signing a venue contract actually exposes.

Volunteer attrition rates, and what a team should plan for.

What a cancellation costs, which we found out in 2020 and which nobody had told us.

And the programme committee's real problem — that it is assembling a schedule rather than ranking talks, which is obvious from inside and invisible from outside.

Why the speaking side is documented and this is not

The asymmetry has a simple cause.

Speaking has a large audience — everybody who might submit a proposal — and writing about it builds a personal reputation.

Organising has an audience of maybe forty people a year, and writing about it builds nothing except a reputation for airing difficulties.

And speaking advice is transferable. Organising advice is contingent on country, venue, scale and community, so anybody writing it has to caveat heavily, which is less satisfying to write and less quotable.

What the gap costs

Every team starts from zero. The same mistakes, in the same order, at each new conference.

Expensive mistakes recur. Deposit terms, liability, cancellation exposure — the ones that end organisations are precisely the ones nobody documents, because the teams that hit them stopped organising.

And the survivor bias is total. The conferences you have heard of are the ones that worked. The ones that folded in year two left no account at all, which is the same filter that operates on every other kind of visible success.

What this section is for

Writing down the unglamorous half while we still remember it, with the caveats attached: one community, one city, events of roughly 300 people, in Germany.

Some of it transfers and some does not, and where we know the difference it is stated. That is a weaker offer than a guide, and it is more than what currently exists.

If you organise something and it goes badly, write that down. It is worth more to the next team than another account of a conference that went well.

The short version