Bringing someone to their first flagship

A first regulatory conference has its own checklist — badge, hotel, agenda, the logistics nobody puts in writing until someone else has already learned them the hard way. Bringing a junior colleague to their first flagship week is a different job, and it belongs to the senior person, not the newcomer. Registering them and handing over the agenda covers the logistics. It doesn't cover the fact that a flagship conference runs partly on standing — who someone is vouched for by, which rooms they have a reason to be in — and a first-timer has none of it yet. Transferring some of that standing is the part of the trip that's actually the senior colleague's to do.

What you're actually giving them

A first-time attendee at a large flagship event is, socially, nobody yet — not because of anything about them, but because nobody in the room has a reason to know that yet. The fastest way past that isn't more preparation on their part; it's a senior colleague willing to spend some of their own accumulated standing introducing them around. That transfer is real and finite — it works because the senior person's name means something in that room — which is exactly why it's worth doing deliberately in the first hour rather than assuming it'll happen naturally over the course of the week.

The introduction that does the real work

A useful introduction names what the person actually does and gives the other party a real reason to keep talking after you walk away — "this is our device-submissions lead, she's been digging into the same combination-product questions you raised this morning" does more work than a name and a handshake ever will. This is the same instinct behind a junior colleague's own request for someone senior's time, run from the other direction: instead of the newcomer having to earn an opening on their own, the senior colleague manufactures one for them, at a flagship the size of the ISPE Annual Meeting or DIA's Global Annual Meeting where a name alone rarely opens a conversation on its own.

Stepping back without disappearing

The introduction is the easy part. The harder discipline is what happens next: stepping back and letting the new conversation run without hovering nearby to rescue it. A junior colleague who's never worked a room this size will make small mistakes — an awkward pause, a question that lands wrong — and that's a normal, necessary part of how they learn to do it themselves next year. Staying visibly attached the whole week reads as a lack of trust as much as it looks like support. Being reachable if something genuinely goes sideways is different from staying within arm's reach the entire time, and the junior colleague usually knows the difference even if they'd never say so.

The debrief that actually helps

At the end of each day, the useful question isn't "which sessions did you get to" — that's a scheduling report, and it's the least interesting thing that happened. Ask who they talked to, what surprised them, and whether any conversation left them with a follow-up they're not sure how to handle alone. That's a smaller, private version of the formal readout a team runs once everyone's home, and it does more to make the second day better than the first than any amount of pre-trip preparation could have. A first flagship week that a junior colleague remembers as genuinely useful, rather than merely survived, is usually the result of a senior colleague who treated this part of the trip as their own job to do well.