Approaching Conferences

Am I getting the most our of time at conferences? This post was a way for me to think through that question and come up with strategies.

Am I getting the most out of the time I put into conferences? This year NAACL and ACL ran mentoring programs to help newer members of the community and in the process of giving advice I started to question whether my own approach to conferences was effective. Most online advice is aimed at students attending for the first time. What about a more experienced researcher? I’ve fallen into certain patterns without stepping back to think about whether they are effective and what could be better.

During sessions

There are four main options during a session in the main conference:

  1. Attend a talk. Pro: Typically the most exciting work is presented in talks. Con: Most talks are poorly presented. Even in a good talk, it is easy to sit and listen but not take it in.
  2. Attend the poster session. Pro: Easy to spend more or less time on each poster. Con: Easy to start skimming titles and figures without learning much (particularly when tired).
  3. Talk to people. Pro: A great way to (1) learn about what other people are doing / thinking about right now, (2) make connections / network, (3) make specific people aware of your own work. Con: Sometimes conversations become just small talk, which is not always worthwhile (Edit: see clarification in the postscript). It can also be hard to approach new people.
  4. Relax. Pro: Being focused and engaged is tiring, a break can be rejuvenating. Con: Missing out on work being presented.

There is no perfect fixed combination of these. The strategy I want to try next time is:

  • Over breakfast, choose 2-3 talks from each session that cover must-see work for my interests. Look through posters for the topics I have an interest in and flag must-see items. If the conference provides breakfast, eat elsewhere to do this and then show up for the last 30 minutes to chat.

  • When a session starts, if I’m in an interesting conversation, keep talking. Otherwise, go to the talks selected that morning and drop by posters in between.

  • Take notes in the conference handbook on every talk I attend and every poster I do more than read the title of.

This minimises the number of decisions during the day and focuses on the work I am most interested in. Of the options above, taking a break isn’t included. I’m hoping this approach (and more below) will make that unnecessary in general.

During breaks

At the first few conferences I went to, I was constantly meeting new people because I didn’t know anyone. Now, I tend to talk to the same people at every conference. I do want to catch up with those people, but it means I’m not making the most of the diverse group the conference brings together.

Who should I be trying to meet? As a student, I was most interested in meeting faculty working in my area. Now, I want to look for (1) the students doing work I am excited about and (2) faculty at places I intend to apply to. My reasoning on the students is that (1) they will have more to say about their work than their advisor, (2) they are the future of the field, and (3) if there is scope for collaboration then it will be easier to get their advisor on board if they are excited than vice versa.

How should I try to meet people? Conferences are so big these days that simply hoping to bump into someone won’t work. One solution is to contact people ahead of time and plan to meet during a specific break. The same idea can apply to lunch. Usually I have just joined lunch groups in an ad hoc way, but having a plan for the nucleus of a group and then picking up more people on the day would be more effective.

In the evening

I always go to the conference receptions (ie. Welcome / Social) and plan to continue. The key questions in my mind are about industry hosted events and when to go to sleep.

I usually don’t get invited to industry events these days. One thing I could do differently is be more proactive in talking to people from the companies hosting events to tell them I am interested. When I am invited, I think it is worth going as it’s another chance to meet people in a setting where it is easy to join and leave conversations (like conference breaks).

Sleep is crucial for conferences. I’ve held that opinion for a while, but on reflection I have not gone far enough. It’s easy to keep hanging out and stay up late then set an alarm to make the morning session. Almost all people need 7-8 hours of sleep, not counting the time before we fall asleep, and the specific sleep hours need to be consistent (see “Why We Sleep” by Matthew Walker). There are two options here: either plan to go back to the hotel at 10pm to be up at 7am, or plan to miss the morning session, staying out till 12am, waking up at 9am. On the topic of sleep, I’m noticing jet lag more as I get older and while the university won’t pay for lodging before the conference, I should seriously consider it anyway (but not tire myself out by doing in a million tourist activities).

Workshop days

Previously I’ve jumped between workshops, trying to squeeze in every keynote talk from someone whose work I am interested in. In future, I plan to take go to a single workshop all day. Reflecting on the keynotes I’ve seen, most are just conference talks stitched together. I’m not learning a lot that is new. In contrast, being at a single workshop means engaging with a sub-community.


In many ways, the plans outlined above are very similar to what I do already. I am eager to see how the changes work out and also hope that having stepped back like this I will feel less uncertain about my choices at the next conference.

While putting this together I found this series of tweets from Chinmay Kulkarni interesting. Our opinions differ on certain points, so check them out:

Postscript: Responses

After sharing this on Twitter, there was some interesting discussion. For posterity, I’m summarising that and other comments I got here:


  • Be willing to leave a poster, talk, or conversation. It may feel polite to stay, but time is valuable, so once something no longer seems interesting, move on to something else. This is one reason to sit on the aisle in a talk.

  • Note taking is important because there is simply too much happening to remember. One suggestion was to track who you talked to and what it was about.

  • Consider going to random things and trying to understand them. This can lead to unexpected links to your own work and may be more interesting (as everything is new).

  • I clarified my small talk point above. I definitely see it is valuable, but if every conversation is small talk then you are missing an opportunity to have a conversation you couldn’t have outside of a conference.

  • People vary in their preferences regarding staying up late or not. Some see it is valuable time to connect. Others get the same from morning activities like running groups.

Talks vs. Posters

  • Talks can give a lot of content in a brief period and convey the presenter’s view of the most important idea.

  • Staying for a complete talk session can expose you to work that is relevant to your interests, but you might have otherwise missed.

  • Talks are often recorded now, so you can watch them later instead (but be honest with yourself about whether you will).

  • Demos and Industry track presentations may have content not in the paper.

  • Attending a talk is a nice way to connect with someone. It means you are guaranteed to find them and there is a starting place for conversation.

  • Interactions at posters can make you feel part of the community in a way talks don’t.

  • As the community grows we may need to explore other structures. For example, at RSS, work is presented as both a four minute talk and a poster session (NAACL tried a 1-minute-madness at least once, which is a similar idea).