How to actually get value from a conference

Most of the value from a conference is decided before you leave the office. A goal set in advance changes which sessions you book, who you seek out in the breaks, and what you write down. Turn up without one and you will fill a notebook with things that seemed interesting at the time and mean nothing three weeks later.

Set a goal specific enough to fail

"Learn about the industry" is not a goal, because there is no version of the day that fails to meet it. A goal worth setting names a decision you need to make or a problem you need to solve: which vendor to shortlist, how another team structured a process you're stuck on, whether a change to your pricing model holds up against how other people are thinking about it. If you can imagine coming home having not achieved it, it's specific enough to be useful.

Write the goal down before you look at the programme. A goal chosen to fit the sessions on offer isn't a goal, it's a rationalisation for the ticket you've already bought.

Choose sessions against the goal

A programme built around what attendees came to learn shows up when you compare a session's title against your goal. A well-known speaker giving a talk that has nothing to do with your goal is an hour you won't get back. A session with an unfamiliar speaker but a title that answers your actual question is the better bet, most of the time.

Where two sessions clash, pick the one closer to your goal and plan to catch the other later: many conferences record main-stage sessions, and asking the organiser about recordings before the day saves you from a bad trade-off on the schedule.

Decide what you're there to find out

Separate what you already know from what you're going to find out, because the two need different kinds of attention. If a session covers ground you already have, your job there is to test it against your own experience and note where it disagrees with what you do. If a session covers ground you don't have, your job is to capture the mechanism.

If your employer is paying for the trip, the goal you set here is also the thing you'll report back on, so it's worth writing in terms someone else in the business would recognise as useful. How to Get Your Employer to Pay for a Conference covers how to frame that case before you book, and Is This Conference Worth Going To? covers how to judge a programme against your goal before you commit the ticket price at all.

Conversations that produce something useful rarely happen in the room set aside for networking. They happen in the queue for coffee, in the gap after a session when people are still thinking about what they just heard, and in the seats nobody wants at the back where the people who left early end up sitting together. If you spend the whole conference in the main hall and leave the moment each session ends, you will meet almost nobody worth remembering.

The corridor track is where most of the value sits

Conference organisers sometimes call the informal conversation that happens between sessions the corridor track, distinct from whatever is printed in the programme. It is not a separate event and nobody schedules it, but it is where people compare notes on the talk they just watched, admit which parts they didn't follow, and mention the problem they're actually trying to solve back at work. That last part is the useful bit: people say more honestly what they need when they aren't being asked a question by someone holding a name badge and a plan.

This is also why the break in the schedule matters more than the size of the room. A programme with no gap between sessions, or one where the only break is a rushed ten minutes before the next talk starts, removes the corridor track entirely. If you're choosing which sessions to attend, a longer break after a session that interests you is often worth more than a slightly better-known speaker in the next slot.

Starting a conversation without the performance

The networking session with a name badge, a drink, and an instruction to mingle produces very few conversations anyone remembers a week later, because it asks two strangers to manufacture a reason to talk. A shared reference point does that work for you. Standing near someone who was in the same session and asking what they made of one specific point the speaker raised is a far easier opening.

• Ask about a specific claim or slide from a session you both just watched.
• Mention the problem you came to solve. Titles invite small talk; problems invite the other person to say whether they've hit the same one.
• Stay in a conversation past the first exchange. Most useful conversations only get interesting on the second or third question, and the person who moves on after thirty seconds rarely finds out.

What makes someone worth talking to again

Not everyone you talk to is worth following up with, and treating every business card as equally valuable is how a contacts list turns into a pile of names nobody can place three months later. The people worth a follow-up email are the ones who named a specific problem, disagreed with something in a way that made you think, or offered to send you something concrete: a document, an introduction, a link. A pleasant five-minute chat that produced nothing specific is fine on the day but rarely survives the trip home.

Write down what the conversation was actually about while it's still fresh. A note that says "struggling to get budget sign-off for the same tool we use, wants to compare notes" is something you can act on later. A note that says only a name and a job title is not, and it's the difference between a contact and a line in an address book. The guide to attending a conference covers what to capture during the day so that this note-taking doesn't depend on memory alone.

A page of notes taken in the room rarely gets opened again. What survives is notes written to answer a question you'll actually have later: what did I decide to do, who did I meet, and what did I say I'd send them. Capture those three things separately from the general scribble, because they are the part anyone goes looking for afterwards.

What to write down, and what to skip

Skip transcribing the slides. Most speakers share slides afterwards, or the organiser posts them, so copying bullet points in real time is effort spent on something you can get for free later. What you cannot get later is your own reaction: the point where you thought we do this wrong, or the question you wanted to ask but didn't. Write those down as they happen, because they are the only record of your own thinking that will exist.

• Decisions: anything you resolve to try, stop doing, or ask someone about back at work
• Names and context: who you spoke to, what they do, and the one thing that made the conversation worth having
• Open questions: things you meant to look up or ask and didn't get to
• Quotable specifics: a number, a method, or a phrase worth repeating to your team.

One format, not four notebooks

Scattered notes across a paper pad, your phone and a slide deck you annotated are notes you will not find again. Pick a single document for the whole event, even a plain one, and add a line to it after every session. A simple structure works better than a clever one: session name, one line on what it was about, one line on what you're taking from it.

Making it findable later

A note is only useful if you can find it when the question comes up, which is usually weeks later and triggered by something unrelated at work. Tag or file notes by the problem they answer. If you took a business card or a contact detail, put it in the same document next to the note about the conversation.

The follow-up habits that turn these notes into something a team actually uses are covered in the section on the first week back. For deciding what to capture in the first place, it helps to have set a goal before you arrived, which the preparation section in this guide covers in more detail.

The week you get back decides whether the trip paid off

Notes go stale fast, and conference contacts go cold faster. The person you spoke to at the drinks reception on day two will have been to two more events within a fortnight, so a follow-up sent five days later starts from a weaker position than one sent the next morning. Set aside an hour on your first day back, before the rest of your inbox absorbs your attention, to work through what you wrote down and act on it while it still means something to you.

What to send your team, and why nobody reading it is worse than nothing

A trip report that gets filed and never opened teaches whoever approved the ticket that sending you produces paperwork. The useful version is short: what you learned that applies to a live piece of work, what you would do differently next time, and whether the cost was justified against what you brought back. That is the document a colleague weighing up the same event next year will actually read.

• A short written summary to your manager and the colleagues covering the same ground, sent within the first week
• A ten-minute slot at the next team meeting to talk through the two or three points worth discussing
• One concrete change to how you or your team work, proposed while the reasoning is still fresh

Turning a conversation into a contact you can actually use later

A connection request with no message attached is not a follow-up. It is a digital business card exchange that neither of you will remember making. What works is a short message within a few days that refers to the specific thing you discussed. If someone offered to send a document, make an introduction, or look at a problem you both have, ask for it while your conversation is still the most recent thing they associate with your name. A contact worth keeping is one where you both know what the next exchange would be about.

A sample follow-up email and a one-page trip report you can adapt are in Worked Examples and Templates. For the case you made to get sent in the first place, and what to carry into next year's request, see How to Get Your Employer to Pay for a Conference.