The Case for Notes That Outlive the Event

Every volunteer-run community I've spent time around has one person who "just knows." They remember who spoke at an event two years ago and how the talk landed with the room. They remember what a particular sponsor cared about beyond the invoice, and which topic the program committee flagged as missing from the agenda and never quite got fixed. None of it is written down anywhere. It sits in one person's memory until that person misses a few planning calls, or just stops showing up.

I've watched this happen a few times now. Someone runs the show for a couple of years without much fuss, then steps back, and a chunk of the group's memory leaves with them. Whoever takes over has to reconstruct decisions from old email threads, or repeat a mistake nobody warned them about, because the warning lived in a person instead of a place.

NOGnet started as event logistics software: registration and badge printing, the stuff that eats an organizer's weekend before a conference. The part I keep thinking matters more is a layer underneath it, a profile attached to each person and sponsor that carries forward from one event to the next, sometimes years apart. Less a contact card than a running set of notes.

Who spoke last time and how it went over. What a sponsor actually cared about two events ago, which was rarely "logo on a banner" and usually something more specific, like wanting more face time with the operator crowd than they got. What a program committee noticed was missing from the agenda after the fact. Small, unglamorous stuff that gets lost between one planning cycle and the next because nobody had anywhere durable to put it.

I know this isn't a new idea. Every CRM has been selling some version of "remember your customer" for decades. NOG communities aren't companies with a sales team, though. They're volunteers and rotating committees, people doing this alongside a day job because they like the technical content and the community around it. Nobody's buying a CRM seat for a volunteer program committee, and even if someone did, the odds of a tired organizer typing notes into it after a late speaker dinner are close to zero. The notes have to live inside whatever the organizer is already doing, reviewing a submission, glancing at a sponsor's history, or they don't get written at all.

Whether people actually write the notes down is the part I'm still unsure about. I can build the field. I can't build the habit. So far, what I've seen is organizers reaching for it during the next planning cycle, staring at a sponsor list and trying to remember why someone left, and that's usually when something finally gets typed in. A little late. Better than nothing.

There's an obvious hole in all this: I build and run NOGnet alone. If I step away for good, the platform has the same single point of failure I built it to fix for everyone else. I don't have a tidy answer for that yet. Backups, some documentation I keep meaning to finish, and a vague hope that nothing catastrophic happens before I get around to it.

For the organizers who do use it, though, remembering something two years later doesn't depend on one volunteer's memory holding up across a rotating committee anymore. It depends on a database, which is a lower bar, and one I can usually clear.