The Single Point of Failure Is a Volunteer
NOG communities run on volunteers stacking event work on top of day jobs, and the warning signs of burnout are almost always quiet until someone is gone. A reflection on why handoff so rarely works, and why the community rarely says so out loud.
Every NOG I've been part of runs on the same fuel: people doing unpaid work on top of a day job, because nobody else will and the thing needs to exist. The mailing list needs a moderator. The registration system needs someone to keep it from breaking two weeks before the event. The program committee needs someone chasing speakers who haven't confirmed. Sponsors need someone answering emails at 11pm because that's when the reply came in. None of this is glamorous. It doesn't pay, and most of the people doing it wouldn't call themselves burned out even when they clearly are.
The warning signs are almost never dramatic. Nobody quits in a public blowup. What actually happens is quieter and slower. A task that used to get done within a day starts taking a week, then two. Replies on the mailing list get shorter. Someone who used to speak up on planning calls starts just listening, then stops showing up to the calls, then stops showing up anywhere. By the time anyone names it out loud, the person is already most of the way out the door. Usually nobody said anything while it was happening, because saying it out loud felt presumptuous, or like making someone's private struggle into a group problem they hadn't asked to share.
Underneath that pattern is a structural one. The same handful of people end up doing five jobs instead of one. Control freaks aren't usually the reason. Nobody else stepped up when the ask went out, and eventually it's faster to do it yourself than to keep asking. That's how you get a treasurer who's also the registration admin who's also the person who knows which sponsor contact actually responds. It works right up until the person doing it can't keep doing it anymore, and there's rarely a clean point where someone else picks up the slack.
Where the knowledge lives
Handoff is the part nobody wants to deal with, and I think that's because so much of what keeps a NOG running lives only in one person's head. The public stuff is usually fine. I mean the actual operational memory: which vendor needs a purchase order two months out instead of one, which sponsor got annoyed last year and why, which part of the registration flow silently breaks if you touch it in the wrong order, who to call when the venue contract needs a signature nobody else is authorized to give. None of that is written down. Writing it down takes time nobody has, and the person holding it usually doesn't realize how much they're holding until they try to hand it off and discover there's no clean edge to hand off along.
I don't think this gets talked about openly for a fairly ordinary reason. Everyone who's been around long enough has watched it happen to someone, and most of them have felt an early version of it in themselves at some point too. Naming it out loud means admitting the community's continuity depends on people quietly absorbing costs that nobody's tracking, and that's an uncomfortable thing to say to volunteers you're currently asking to do more.
I've spent a chunk of the last while building NOGnet, tooling aimed at some of the operational load that tends to pile up on one or two people during event season, things like registration and the logistics that usually live in someone's inbox and nowhere else. I want to be honest about what that is and isn't. It doesn't fix burnout. It doesn't replace the judgment calls that only exist in someone's head after years of doing this, and it doesn't make the emotional weight of being the one everyone defaults to any lighter. What it can do is take some of the repetitive, undocumented busywork off a single person's plate, so the knowledge that has to live in one head is at least smaller than it used to be. I'm making a modest claim on purpose. I've watched enough tooling get pitched as a fix for a people problem to be wary of doing that myself.
The actual fix, if there is one, probably has less to do with software and more to do with communities getting comfortable asking an awkward question earlier: who else knows how to do this, and if the answer is nobody, what happens before that becomes urgent instead of after.