When to let a conference go

Nobody decides to keep attending a conference every year. It just happens: you went once, it was worth going, you went again the next year because you went the year before, and at some point the trip stopped being a decision and became a line item that renews itself. That's not automatically a problem — some annuals earn a permanent seat on the calendar. The problem is that almost nobody ever goes back and checks, and a habit that started as a good call three years ago can keep running on momentum long after the reasons that justified it have quietly changed.

The habit and the budget line are different questions

"We always send someone" is a description of what has happened, not a reason to keep doing it. It survives a first question — why do we go? — with an easy answer, usually pointing at something true three or four years ago: a regulator held a memorable session, a client relationship started in a hallway, the program used to be the best in the category. It rarely survives a second question: is that still true this year, for this edition, for the person we'd send? Sunk cost hides well inside a habit, because a habit doesn't feel like a decision at all — it feels like the calendar simply working the way it always has. The same discipline choosing a conference from scratch applies to a first-time pick applies just as hard to a conference you've already been attending for years; it's just easier to skip, because nobody's forcing the comparison.

What the last few trip reports actually say

The evidence for or against renewal is usually already sitting in a shared drive. A trip report worth reading names specific sessions, specific contacts, specific things that changed because of the trip — and read three or four of them from the same conference back to back, a pattern tends to surface fast. If each year's report names a different reason the trip mattered, that's an event still earning its keep. If the last three reports could be reordered without anyone noticing — same two sessions worth attending, same one contact worth the coffee, a paragraph of padding around them — that's not a failure of the person who went. It's the conference telling you, in writing, that it has settled into a smaller role than the budget line still assumes.

Sending someone else instead of dropping it

Letting a conference go doesn't have to mean cutting it from the calendar entirely, and treating it as all-or-nothing is usually what keeps a fading annual on the books past its useful life — nobody wants to be the one who "cancelled" a fixture. The lower-stakes move is rotation: hand the seat to someone who hasn't been, for reasons that have nothing to do with whether last year's version was worth repeating. Sending a colleague well is its own skill, and a conference you've outgrown yourself can be exactly the right one to hand to someone building their own first relationship with the room. You keep the door open, spend the same budget line differently, and get an honest new trip report instead of a fourth copy of your own.

When the real question isn't which edition

Choosing between a flagship and its regional counterpart assumes the answer is one of the two. Some years the more honest answer is neither — not because the organizer did anything wrong, but because your reasons for going changed faster than the habit did. That's a different failure mode than the conference changing on you through a postponement or a venue swap; this is the case where the event stayed exactly the same and your team simply outgrew what it offers. A flagship annual like RAPS Convergence or DIA's Global Annual Meeting can be worth attending for a decade straight for one team and worth one trip and no more for another — the program on the organizer's own page is the same either way. What changes is what you'd actually do with the seat this year, and that's worth checking honestly before the registration renews itself again.

Coming back later is fine

A skipped year rarely burns a bridge the way it feels like it might. Organizers run these events annually because most of the audience cycles in and out anyway; the room doesn't remember who sat it out one edition, and re-entering a conference after a gap costs nothing but the ordinary work of catching up on what changed — a program shift, a new venue, a schedule move, all worth confirming at the organizer's own page rather than assuming last year's rhythm still holds. An annual meeting you sit out for a year is still there the next one, if the reasons come back. What isn't worth doing is renewing on habit alone and finding out three trip reports later that nobody could say why.