Skip to main content

Most people come home from a conference with a tote bag, a stack of business cards they will never sort, a phone full of blurry slide photos and a vague feeling that it was “good”. Two weeks later, nothing has changed in how they work.

That is an expensive outcome. Conferences cost registration fees, travel, time away from patients and teams, and colleagues covering your work. The people who get real value from them are rarely the ones who attend the most sessions. They are the ones who treat the event as a project with a goal, a plan and a follow-up.

This is a practical checklist for health professionals attending any conference, large or small, clinical or policy-focused. Take what is useful and ignore the rest.

Before any of this: choose the right conference

The checklist assumes you are going to the right event. That is worth questioning first, because the most common waste is attending the wrong one well.

  • Match the conference to your question, not your specialty. If your problem is implementation, a policy or health services meeting may teach you more than a clinical congress in your own field.
  • Look at the programme from last year, not the marketing for this one. Were the sessions mostly original work, case studies from real systems, or sponsored showcases? The mix tells you what you will actually hear.
  • Check who attends, not just who speaks. If you want to meet commissioners, a meeting full of researchers will be frustrating, and the reverse is also true.
  • Compare the full cost, including cover for your absence, with what you expect to bring back. A smaller regional meeting close to home sometimes delivers more usable contacts than a large international one.

Four weeks before: decide why you are going

  • Write down one to three specific questions you want answered. Not “learn about digital health” but “find out how other hospitals have reduced discharge delays” or “understand what evidence exists for a specific intervention we are considering”.
  • Tell your manager or team what you are going to bring back. That turns the trip from a personal perk into a shared investment, and makes it easier to get time to act on what you learn.
  • Ask colleagues who cannot attend what they would want you to find out. You will be more useful to them and you will listen differently.
  • Read the programme properly and mark sessions by your questions, not by famous names. Big-name keynotes are often available online later; small panels and workshops usually are not.

Two weeks before: plan the people, not just the sessions

  • Identify five to ten people you would like to meet: speakers, authors of papers you have read, people working on the same problem in another system. Most conference value comes from conversations, and conversations need planning.
  • Send short, specific messages in advance. Say who you are, why you want to meet and what you can offer in return. A request for fifteen minutes over coffee is far more likely to be accepted than a vague “let’s connect”.
  • Prepare a thirty-second description of what you do and the problem you are working on. You will be asked many times. A clear answer leads to better conversations.
  • If you are presenting, rehearse to time and cut your slides by a third. Audiences at health conferences remember one clear idea far better than twenty dense slides.

Before you travel: the practical basics

  • Download the event app or programme, and check for room changes on the day.
  • Pack comfortable shoes, a refillable water bottle, a portable phone charger and a layer for over-air-conditioned rooms.
  • Set an out-of-office message that clearly names who to contact instead of you, and resist the urge to clear your inbox during sessions.
  • Block time in your calendar for the week after the conference to follow up. If you do not protect this time now, it will disappear.

During the conference: attend with intent

  • Do not try to attend everything. Leave gaps in your schedule for conversations, rest and thinking. Fatigue after the second day is real and it degrades judgement.
  • In sessions, take notes on what you would actually do differently, not a transcript of the talk. One useful format: what I heard, what it means for us, who I should tell.
  • Ask a question in at least one session. It makes you visible and often starts conversations afterwards.
  • Visit posters. Poster sessions are underrated; you can have a long conversation with the person who did the work, often about the problems that did not make it into the abstract.
  • Be sceptical. Conference presentations are frequently of unpublished or preliminary work. Ask about sample sizes, comparison groups, who funded the work and whether results have been replicated.
  • Note industry sponsorship of sessions and speakers. It does not make the content wrong, but it is relevant context.

Networking without the awkwardness

  • Talk to people standing alone. They are usually relieved.
  • Ask about the problem someone is working on rather than their job title. It leads to better conversations.
  • After each meaningful conversation, write two lines on the back of the business card or in your phone: what you discussed and what you promised to do.
  • Keep promises small and specific. “I’ll email you the protocol we used” is better than “let’s collaborate”.

The week after: where most value is lost

  • Send follow-up messages within a week, while you are both still remembered. Reference the conversation and deliver whatever you promised.
  • Write a one-page summary for your team: the three most useful things you learned, one change you propose to try, and who else should be involved.
  • Present back in a team meeting. Ten minutes is enough. It forces you to distil what mattered and spreads the value beyond you.
  • Pick one idea and test it. Not five. One small, measurable change you can try within a month.
  • Record what you spent and what you gained. Over time, this helps you choose which conferences are worth attending and makes a stronger case for funding future ones.

Reading conference evidence like a sceptic

Conferences are where findings are newest and least tested. That is their value and their risk.

An abstract is not a paper. Many studies presented at meetings are preliminary, and a meaningful share never make it into peer-reviewed publication, or change when they do. Results presented from a single site, a short follow-up or a subgroup deserve particular caution. So do dramatic before-and-after improvements with no comparison group, because many things change over time on their own.

A useful habit is to ask three questions of any finding you are tempted to take home. Compared with what? In whom, and would my patients look like them? What would it cost us to do this, in staff time as well as money? If a speaker cannot answer those, the idea may still be worth exploring, but it is not yet ready to be implemented.

It is also worth noticing what is missing. Conferences favour positive results and interesting stories. The pilot that failed rarely gets a slot. If you can find someone in the corridor who tried the same thing and it did not work, that conversation may be worth more than the session that inspired you.

If you are presenting a poster

Posters are often treated as a consolation prize for authors whose abstract did not become a talk. Used well, they are one of the best networking tools at any conference.

  • Lead with the question and the answer in large type at the top. Most people will read only the title and one sentence while walking past.
  • Put the one chart that matters in the middle. Cut the rest or move it to a handout.
  • Stand by it during the scheduled session and ask people what brought them over. You learn who is working on the same problem.
  • Bring something small to take away: a one-page summary, or a code linking to the full slides and your contact details.
  • Note who stopped and what they asked. Their questions are a preview of what reviewers will ask when you submit the paper.

For managers sending people

Much of the value of a conference is decided before anyone travels, by the person who approves the trip.

  • Ask for the questions in advance, not a report afterwards. A report written after the fact tends to describe the conference. A question written beforehand shapes what the person looks for.
  • Agree what will change if the trip is useful. That could be a small test of a new process, a contact who might become a partner, or a decision to stop pursuing something.
  • Protect time afterwards. Staff who return to a full inbox and a full clinic will have no room to act on anything they learned. Half a day of protected follow-up time is cheap compared with the cost of the trip.
  • Rotate who goes. Sending the same senior people every year concentrates learning and networks in a few heads. Sending a junior colleague with a clear question is often a better investment.
  • Ask the returning colleague to teach one thing, not summarise everything. Teaching forces clarity, and it multiplies the return on the budget.

The case for going at all

It is fair to ask whether in-person conferences are still worth it now that many sessions are streamed or recorded. For pure content, often they are not. If your only goal is to hear the keynotes, watching recordings at home is cheaper and lets you skip what is irrelevant.

The case for going rests on things that recordings do not capture: the corridor conversation with someone who has already solved your problem, the chance to ask a speaker the follow-up question that would not survive a chat box, and the relationships that make a later email get answered. If you are not planning to do those things, you may get more from the recording and a protected afternoon to watch it.

Measuring whether it was worth it

Three months after the conference, look back at your notes and ask three things.

  • What did we change, even slightly, because of something learned there?
  • Which contact from the event have I spoken to since?
  • Would I go again, and what would I do differently?

If the honest answer to the first two is nothing and nobody, it does not necessarily mean the conference was poor. It may mean the follow-up time was never protected. Either way, the answer should shape the next decision about where to spend the budget.

The one habit that matters most

If you take only one thing from this checklist, make it this: go with a question and come back with an action. Everything else, the sessions, the networking, the notes, is a means to that end.

Your tips

What is the best thing you have ever done at, or after, a conference? And what is the mistake you will never repeat? Share your tips in the comments. The most practical advice usually comes from people who learned it the hard way.

Abhishek Shankar

Abhishek Shankar is a three-time founder and CEO of MyBabyBridge, which uses AI and data to make IVF more accessible. He writes about the gap between what works in health pilots and what survives at scale, covering financing, workforce, digital health and equity. He writes more at abhishek-shankar.com.

Leave a Reply