Habit, Not Hack: Preparing For a Conference (Mentor)

Trainees don't come home from conferences empty-handed because they lack initiative. They come home empty-handed because conference skills are mentored skills — and most labs treat them as instincts.

Two trainees from two different labs attended the same conference.

The first, Naomi, got an email from her PI the week before: "Have fun, learn a lot, come find me if you need anything." She attended nineteen sessions in four days, ate lunch alone twice, stood three feet from the researcher whose papers shaped her dissertation, and let the moment pass. She came home with thirty-one pages of notes and no one to send them to.

The second, Marcus — years earlier, as a third-year himself — got fifteen minutes with his mentor before his first conference. One question: "What do you want out of this meeting, and who are the three people you should meet?" They built the list together. At the conference, his mentor walked him across a coffee break and said eleven words: "This is Marcus, my student — he's working on the problem you raised in your last paper."

That introduction became a conversation. The conversation became a follow-up email. The email, eventually, became a collaboration.

Naomi's PI was not a worse scientist than Marcus's mentor. She was not less invested in her student.

She just assumed the conference would teach itself.

The Story Mentors Tell About Conference Attendance

Most labs treat the conference as self-explanatory. The mentoring effort goes into the abstract, the poster, the slides — the artifacts. Then the trainee is put on a plane with a finished poster and an unspoken assumption: the rest is just showing up.

The story underneath this is that networking is a personality trait. Some people work a room; some don't. The trainee who comes home with new connections "has it." The one who comes home with a tote bag and a vague sense of overwhelm will hopefully develop it, the way everyone does — eventually, by repetition.

This story is not entirely wrong. Repetition does help. Some of conference skill really is accumulated mileage.

But the story confuses a teachable skill with an inherited temperament — and it quietly wastes the trainee's first several conferences as unguided trial and error. Goal-setting, choosing who to meet, opening a conversation, capturing what matters, following up within the window where follow-up works: every one of these is concrete, learnable, and fastest to learn when someone names it out loud.

Nobody expects a trainee to learn the lab's hardest technique by being handed the equipment and wished well. The conference is a technique.

The Habit: Mentor the Conference, Not Just the Abstract

This is not about scripting your trainee's week.

It is not about turning their first meeting into a performance review.

It is not about requiring an extrovert's itinerary from an introvert.

The habit is simpler:

Treat the conference as three mentoring conversations — one before, one brief moment during, one after.

Fifteen minutes before they leave. A few introductions while you're both there. One question the week they return.

That is the entire time cost. The return on it is the difference between Naomi's conference and Marcus's.

What This Looks Like in Practice

Before they go, sit down for fifteen minutes and ask three questions.

"What's your one goal for this meeting?" — and push past "network more." A real goal is falsifiable: feedback on the aim 2 design, three people from the lab they want to postdoc in, one person who has run this method on human samples.

"Who do you want to meet?" — and if they don't have names, this is where you earn your title. You know the field. You know who is generous with students and who is not. Help them build a list of three to five people, and have them look up one recent thing about each so the conversation has somewhere to start.

"What do you need from me?" — sometimes the answer is an introduction. Sometimes it's permission: to skip a session when they're depleted, to leave a social event early, to not attend everything. Say the permissions out loud. Trainees will not assume them.

If they are presenting, rehearse the human parts, not just the science: the three-minute poster walkthrough, the one-sentence answer to "so what do you work on?", the three questions they're most likely to get — and the one they're least prepared for.

During the conference, introduce them to your network.

This is the single highest-leverage thing you will do all week, and it costs you thirty seconds at a time.

Your name opens doors your trainee's cannot yet. A cold introduction from a third-year — "Hi, I'm a student in the Chen lab" — has to earn attention. A warm one from you — "This is my student; she's the one who solved the problem we talked about in March" — arrives with attention already attached. You are not just making an introduction. You are lending your credibility until they have their own.

So walk them over. At the coffee break, in the poster hall, after a session — when you see someone they should know, make the connection, say one specific sentence about their work, and then leave. The exit matters. If you stay, the conversation stays yours. If you go, it becomes theirs.

And let them see you work. Let them watch you ask a question after a talk, admit what you don't know, leave a session that isn't useful. You are modeling the norms they will carry for a career.

After they return, ask one question within the week:

"Who are you following up with — and have you sent it yet?"

The follow-up window is about 48 hours; after that, your trainee becomes a lanyard-shaped blur in someone's memory. Most trainees miss the window not from laziness but because nobody told them the window exists. Your question, asked once, installs the habit permanently — because it tells them what the conference report you actually care about is. Not how many sessions they survived. What they brought home that is still alive.

Then ask what they'd do differently next time, and write it down with them. That reflection is the compound interest. It is the reason their fourth conference will look nothing like their first.

A Note on What This Isn't

This is not doing the networking for them. The introduction is a door; they still have to walk through it, hold the conversation, and send the email. A mentor who manages every interaction has produced a trainee who can be escorted, not one who can navigate.

It is also not a uniform prescription. The introvert's plan and the extrovert's plan should not look alike. Two or three real conversations, followed up well, is a fully successful conference — for them and, frankly, for you. The mentoring is in helping them define their version of success before the meeting defines it for them.

And it is not only for first-timers. Your senior students and postdocs face a different failure mode: experience without intention, the same conference attended on autopilot every year. The questions change — "What do you need from this meeting at this stage? Who should you reconnect with? What conversation moves the next position forward?" — but the habit is the same.

The Reframe That Changes the Calculation

A trainee's conference is not a perk you sign off on. It is a training environment you are responsible for — the same as their bench work, their writing, their first peer review.

The funding is not the mentoring. The signature on the travel form is not the mentoring. The mentoring is the fifteen minutes before, the thirty-second introductions during, and the one question after.

Naomi's story has a second version. In it, her PI asks one question before the flight, walks her across one coffee break, and asks one question the week she returns. Total cost: under an hour. In that version, Naomi still eats one lunch alone, still feels overwhelmed on day one — and still comes home with three conversations worth continuing and the knowledge that conferences are prepared, not endured.

Every conference after that one, she prepares herself. That is what mentoring a skill means: you are present for the first repetition so you can be unnecessary for the rest.

That is not a hack.

That is a habit.

✨ Put the structure in your trainee's hands. The GLC Conference Prep Planner gives them the before-during-after scaffold — goals and a people list before they go, one-idea-one-action session notes, presenter prep for posters and talks, and the 48-hour follow-up tracker and reflection.