How to actually get value from a conference

The value of a conference is mostly decided before you leave the office. A specific goal, set before you look at the agenda, tells you which sessions to book, which to skip, and which conversations are worth chasing once you're there. Without one, you end up choosing sessions by name recognition and coming home with a notebook full of things that felt interesting for an hour and useful for none of them.

Write down a question, not a topic

"Attend the pricing track" is not a goal, because it doesn't tell you what to do once you're in the room. "Find out how two or three organisations our size are handling subscription pricing" is a goal, because you'll know within the first ten minutes of a session whether it's answering your question or not. Write the question down before you book anything. If you can't turn your reason for going into a single sentence with a question mark on the end, the goal isn't specific enough yet.

Choose sessions against the goal

A keynote speaker draws a room because people recognise the name from a book or a podcast. The material that moves your specific problem forward is more often in a narrower session, further down the programme, run by someone doing the work now. Go through the agenda and mark only the sessions that touch your question directly. Everything else is a maybe, to be filled in once you see how the day is actually running.

Decide what you'd count as a result

Before the first session starts, decide what you'd need to bring back for the trip to have been worth the time and the fee. That might be a specific answer, a comparison between two approaches, or the contact details of two people doing something you're trying to do. Naming it in advance is also the thing a manager will ask for if the conference needs signing off, and stating it clearly up front makes that conversation shorter. If you're still deciding whether a particular event is worth the ticket at all, that judgement is covered separately in Is This Conference Worth Going To?, and a template for setting the goal itself is in Worked Examples and Templates.

Where conversations actually start

Most of what you take from a conference happens in the gaps between sessions. The corridor track, the conversation that happens in the coffee queue or on the walk between rooms, is how people actually meet each other at these events. A session gives a room full of strangers a shared reference point for twenty minutes; the corridor track is where two of them use it.

Use the session as an opener

Approaching a stranger cold and asking what they do is hard work for both people. Approaching someone who sat through the same session and asking what they made of a specific point the speaker raised is not, because you already have something to talk about. That is the difference between working a room and having a conversation: one starts with a script, the other starts with a shared observation.

Who is worth talking to again

Job title is a weak signal of whether a conversation is worth continuing. The stronger signal is whether the other person is working on the same specific problem you are, or has already solved a version of it. A conversation with someone several grades below you who has just built the thing you are about to attempt is worth more than an introduction to someone senior with no direct overlap.

What actually gets exchanged

A business card or a new connection made in a corridor is not, by itself, worth anything. What makes a contact worth keeping is a specific piece of information exchanged during the conversation: a tool they used, a mistake they made, a name of someone else worth talking to. If you cannot recall a concrete thing the person told you an hour later, the conversation was pleasant but not useful, and it is fine to let it go rather than force a follow-up out of politeness.

When the format works against you

A loud plenary break with nowhere to sit and a single roaming microphone is not designed for conversation, whatever the organiser calls it. Structured formats built for this, a facilitated meetup, a smaller breakout, a quiet room away from the main hall, tend to produce better conversations than a crowded standing reception, because they lower the effort of starting one. If a conference's own programme makes this hard, that is a fair thing to factor into whether you go again; see Is This Conference Worth Going To? for how to weigh it before you book.

The notes you take mid-session feel useful at the time and useless by the following Tuesday, because they record what the speaker said. A page of bullet points from a talk on data strategy is not a decision, an action or a contact, so three months later it reads like someone else's meeting minutes. The fix is to change what you write down while you're in the room.

Write down decisions, not content

Capture four things and nothing else: the decision you've made because of what you heard, the name of the person or tool it came from, the action it implies, and a rough deadline. "Check whether our onboarding flow needs a re-audit against WCAG 2.1 AA, prompted by the accessibility talk, before Q3 planning" survives. A summary of the slide on accessibility principles does not, because nobody reads it again.

One document, not a stack of session notes

Keep a single running document for the whole event. Structure it under three headings: decisions and actions, people to follow up with and why, and things to check when you're back at your desk. This forces a choice at the moment you'd otherwise write a paragraph of summary: does this go under an action, or does it not go in at all. Most of what you hear does not go in, and that's the sorting mechanism doing its job.

Making it findable in three months

A note that lives only on the device you wrote it on effectively does not exist by the time you need it. Two habits make the difference:

• Name the file with the date and the event, not "notes" or "conference2", so a search for either turns it up.
• Move it into wherever your team already keeps shared documents within the first few days, not "when you get round to it", because a note that sits in a personal downloads folder for six weeks is a note nobody else can act on.

The worked examples and templates page has a structure you can adapt directly, so you're not designing a note-taking system from scratch on the train home.

The value of a conference gets decided in the week after it. A session that felt useful on the day is worth nothing if the notes sit unread and the people you met never hear from you again. What separates someone who got value from someone who just attended is what happens in the following five working days.

Write it up before the memory fades

Block an hour within two working days of getting back, ideally the first morning. Go through your notes and pull out three things: one idea you can act on immediately, one you need to raise with someone else, and one that needs more research before it's worth pursuing. Anything that doesn't fit one of those three categories was probably interesting but not useful, and that's fine. Most of what you hear at a conference is context, and the write-up is where you sort out what to act on.

What to share with your team

A verbal recap in the next team meeting works better than a written report nobody reads. Pick two or three concrete points: what you're going to change, what you think the team should look at, and what you'd want to check before recommending it further. If your employer paid for you to attend, this is also the moment that justifies the decision. If you're building the case for a future conference, the follow-up you produce this time is the evidence for next time.

Turning a business card into a contact

A LinkedIn connection sent the day you get home, with no message, is close to worthless. Anyone you had a conversation worth continuing is worth an email within the week that names the specific thing you discussed and proposes a next step, a call, a document, an introduction to someone else. That specificity is what makes the message worth answering. Conversations that don't get a follow-up within a week rarely get one at all, because the context that made them worth having fades for the other person as fast as it does for you.

What not to bother with

Not every contact needs to become a relationship, and treating a conference as a numbers exercise, collecting as many names as possible, produces a pile of connections you'll never use. A shorter list of people you actually follow up with is worth more than a long one you don't. The same discipline applies to notes: three actionable points beat forty pages of transcription nobody revisits.

For building the case to attend in the first place, see How to Get Your Employer to Pay for a Conference. For a template you can adapt for a write-up or a follow-up email, check Worked Examples and Templates.