Labs tend to handle conference social media one of two ways: total silence, or a flood of posts documenting every session attended, every poster walked past, every coffee-break conversation. Neither gets much engagement. The silent approach wastes a genuinely good content opportunity — a conference is one of the few times a lab has something happening in real time. The flood approach buries the one or two posts anyone actually wanted to see under a dozen that read as note-taking rather than sharing.
Pick the moments, don’t document the whole trip
A conference post works best when it captures a specific moment: a striking result from someone else’s talk, a good question from the audience during the lab’s own presentation, an unexpected connection made in a hallway conversation. These are the posts people actually stop to read, because they carry a real reaction rather than a log entry. A useful filter before posting is whether the moment would be worth mentioning to a colleague back home in person — if yes, it’s probably worth a post; if it’s just “attended talk X,” it usually isn’t.
The lab’s own talk or poster deserves its own post
If the lab is presenting, that’s the one moment worth planning in advance rather than improvising. A photo of the poster or the speaker mid-talk, with a one-line summary of the finding in plain language, works on LinkedIn or X and gives people who couldn’t attend a reason to ask questions or reach out. This is also a natural moment to link back to the paper itself if one exists, since conference attention is one of the few times a broader audience is actively paying attention to the lab’s work.
Ask before posting other people’s slides
It’s common to see a striking slide from someone else’s talk shared as a photo, and just as common for that speaker to not have wanted it shared. A quick check — “mind if I post this?” — takes ten seconds and avoids the occasional awkward request to take a post down. When permission is unclear or the speaker isn’t nearby, a text description of the finding without the photo is a safe default.
Real time beats a recap written afterward
Conference content loses most of its relevance once the conference is over. A thread posted the following week, after everyone’s attention has moved on, gets a fraction of the engagement a same-day post would have gotten. This is part of why it’s usually better for a student actually attending sessions to post in the moment, phone in hand between talks, rather than routing everything through a PI who’ll write it up after getting home — by then the moment for it has largely passed.
It’s fine to skip a day
Not every conference day produces something worth posting, and a low-effort post written just to keep a streak going tends to read as exactly that — thin and obligatory. Skipping a day costs nothing. This connects to a broader point about posting consistency: the goal is posting real material regularly, not posting on a fixed schedule regardless of whether there’s anything to say.
After the conference, one wrap-up is enough
A single short post after returning — a highlight or two, a thank-you to organizers, maybe a mention of a new collaboration that came out of it — closes the loop well. It doesn’t need to recap every session; anyone who wanted the day-by-day version already saw it posted live. This closing post is also a natural moment to link to a fuller writeup if the lab keeps one, without needing the social post itself to carry all the detail.
Common questions
How many posts is reasonable for a multi-day conference?
One or two a day is plenty for most accounts. A live-tweet thread of every session is fine if that's genuinely the account's format, but for a lab account it usually reads as noise that buries the one or two posts people actually wanted to see.
Should we post the talk slides?
Only with the speaker's permission, and a photo of a single striking slide usually works better than a dump of the whole deck. Many speakers explicitly don't want their slides posted, so it's worth a quick check before sharing rather than assuming it's fine.
What if nothing exciting happened that day?
Skip the post. A conference doesn't require a daily update, and a low-effort post written just to maintain a streak reads as exactly that. Silence for a day is less costly than a post with nothing to say.
Should the PI or a student handle conference posting?
Whoever is actually attending and has a phone free between sessions, which is often a student rather than the PI. It matters less who posts than that the posts happen in the moment, since conference content loses most of its value if it goes out a week later.