Is this conference worth going to?

The programme is the conference's own account of what it will contain, and it usually gives away more than the organisers intend. A session title, a speaker bio and a track label are marketing copy in miniature, written by people who know that most attendees decide from the programme alone. Reading them as evidence tells you whether the content was curated for the audience or sold to whoever paid for a slot.

What a session title tells you

A title built around a specific question or a named problem, such as "why our migration to microservices took eighteen months longer than planned", signals a speaker with a particular thing to report. A title built around a category or a trend, such as "the future of AI in retail", signals a slot that could be filled by almost anyone willing to talk about the subject in general terms, and often was. Sponsorship does not make a session worthless, but a title that reads like a product category rather than a claim is worth checking against the speaker's employer.

What a speaker bio does and does not tell you

A bio that names a specific role, a specific project or a piece of published work gives you something to check, because you can look up whether that person actually did what the bio says. A bio built entirely from job titles and company names, with nothing you could verify, tells you the organiser had a name for the page and little else. Bios that only appear after you have bought a ticket, or that are missing altogether, are worth noting: it usually means the speaker was confirmed late or was never really the point of the session.

How the track structure gives away the funding model

Programmes are usually organised into tracks, parallel strands of sessions running at the same time so attendees choose which to follow. A track named after a sponsor, or one where every speaker works for the same handful of companies, is a pay-to-speak track: the sponsor bought the slot. That is a legitimate way to fund a conference and most events run at least one such track, but it is not curated content, and treating it as equivalent to a peer-selected session misreads what you are looking at.

The ratio worth checking is how many sessions sit inside sponsor-named tracks against how many came through open submission. A programme with one clearly labelled sponsor track among six independent ones is a different proposition from a programme where sponsor logos sit against half the sessions and the rest carry no label at all.

Where to check the claims

None of this needs special access. A speaker's employer, their previous talks where recorded, and the project named in their bio are all checkable in a few minutes online. If the programme resists that kind of checking, because titles are generic, bios are vague and speakers are listed only by first name and company, that resistance is itself worth noting.

For how organisers are meant to build a programme, and where the pay-to-speak line is usually drawn, see Designing a Conference Programme and Finding, Choosing and Looking After Speakers.

A conference ticket is the smallest number on the invoice. The full cost is the ticket, travel, accommodation for however many nights the programme runs, and the days you are out of the office, which is a cost even if your employer is paying your salary regardless. A two-day conference in a UK city typically runs to £800 to £2,000 all in once travel and accommodation are added to a mid-range ticket, as of 2024, and that band moves with location, hotel rates during the conference dates, and whether you book travel early or late.

What the money and the days are not being spent on

Every pound and every day committed to a conference is a pound and a day not spent on something else: a training course with a defined syllabus, a smaller specialist workshop, or simply two days of uninterrupted work on something that is currently slipping. The comparison worth making is not "is this conference good" but "is this the best use of this specific budget and these specific days, compared with the next best alternative available to me right now". If the honest answer is that a half-day webinar would cover the same ground, the conference is not worth it regardless of how well it is run.

Ignore what you have already paid

If the ticket is already booked, the money is spent whether or not you go, so it should not feature in the decision about whether to attend. What still matters is the cost still ahead of you: the travel, the accommodation if not yet booked, and the days out of the office. Weighing those against a registration fee you cannot get back is the sunk-cost trap, and it pushes people to attend events that no longer make sense simply because pulling out feels like a waste. The question to ask is always forward-looking: given what it will now cost me to go, from here, is that worth it.

Making the case if someone else is paying

Where an employer is covering the cost, the same arithmetic still applies, because days out of the office are a cost to the business even when the ticket is not. How to Get Your Employer to Pay for a Conference covers how to frame that case with a specific return. Once you have decided to go, How to Actually Get Value From a Conference covers how to make sure the days you have committed are not wasted once you are there.

The session on stage is not always where a conference earns its ticket price. For a lot of attendees the return comes from the queue for coffee, the person you sit next to at lunch who turns out to work on the same problem, or the five minutes after a talk where you ask the speaker the question you didn't want to raise in front of two hundred people. This is sometimes called the corridor track: the informal, unscheduled part of the event that runs alongside the printed programme.

Why the break in the schedule can matter more than the session

A talk teaches you something one person already knows. A conversation in the corridor can point you to a person, a tool or a decision you didn't know to look for. Organisers who understand this build time for it into the design: they lengthen breaks, seat people at shared tables, and resist the urge to fill every slot because an empty one on the printed agenda looks like wasted budget.

What a packed agenda tells you

Check the timings before you check the speakers. A programme with fifteen-minute breaks between every session and a single hour for lunch is built for content volume: you will spend the day moving between rooms. A programme with forty-five-minute breaks, a seated lunch or an explicit unstructured slot is telling you the organisers expect value to happen off the stage as well as on it. Neither approach is wrong on its own. The mismatch worth watching for is a conference that markets itself on networking while scheduling none.

Meals are a schedule decision.

How lunch is served says more about a conference's priorities than the menu does. A boxed lunch eaten standing, or carried back to a desk, removes the one guaranteed moment when a room full of strangers sits down together. A seated lunch, even a plain one, forces the mixing that a coffee break only offers to the confident. If accessibility has been thought through properly, dietary requirements and step-free access to the eating area will have been asked about at booking; if the conference hasn't asked, that tells you something too.

Read Designing a Conference Programme for what organisers weigh when they decide how much of the day to leave open, and How to Actually Get Value From a Conference for how to use that unscheduled time once you're there.