The season that stopped paying for itself

Every conference on your calendar can pass its own individual test — worth attending, worth the budget, worth the days away — and the season can still be too full. That's the part the per-event test misses: it was never built to catch a problem that only shows up in the aggregate, where five reasonable yeses add up to a quarter with no slack left in it. The signal isn't any one bad event. It's a specific feeling that shows up around the third or fourth trip of a busy stretch, and it's worth learning to recognize on its own terms instead of waiting for it to resolve itself.

The tell is sameness, not any particular bad trip

A single disappointing conference is just a disappointing conference — it happens, and it doesn't mean anything about the rest of the calendar. The more useful signal is quieter and shows up over several trips: your own trip reports start reading like the same document with the city changed, the sessions you pick start repeating last year's agenda, and the people you catch up with in the hallway are the identical five people from the last three events. None of that is a reason to skip any one of them. It's a reason to look at the stretch as a whole rather than event by event, which is exactly the view the per-event test was never designed to give you.

Count what the budget line doesn't show

The approval process tracks registration fees and travel costs, because that's what a manager has to sign off on. It doesn't track the two days of prep before a talk, the backlog waiting at your desk when you land, or the number of nights in a row you've slept somewhere other than home this quarter. A quick tally at mid-year or year-end — total days on the road, total prep hours, not just total dollars — usually tells a more honest story than the budget does about whether the season still has room in it, or whether the next invitation should get a harder look than the last one did.

Trim the portfolio, not the next event on the calendar

The decision that actually works is made once, looking at the whole list, not reactively at whichever registration deadline happens to land next. Sequencing the year's events against their submission dates is the planning side of this; the evidence for whether any one of them still earns its seat is the per-event side. The season-level question sits above both: given everything already sequenced and already earning its place individually, is the total still something you can sustain without the desk work and the sleep both quietly going into debt.

What usually survives a real trim is the flagship — the one event in the year that reliably produces something none of the others do — and what usually goes is the comfortable regional repeat that's become a habit more than a decision. That's a harder cut than it sounds, precisely because the comfortable one still passes its own individual test. It just doesn't need to pass it every single year.