When your organization sends a delegation, not just you

Splitting a conference with colleagues to cover more tracks is an internal efficiency problem — nobody outside your own company particularly cares whether you divided the agenda well. Attending the same event as your organization's formal delegation is a different job wearing similar clothes. Counterparts from other organizations are watching whether your three or four people say the same thing, in the same meeting, in front of them. A visible disagreement between two of your own colleagues reads, from the other side of the table, as your organization not actually knowing its own position — which is a worse outcome than either colleague being individually wrong.

This is not the same problem as splitting the tracks

It's worth being explicit with your own team about which problem you're actually solving, because the two look similar on a travel approval form and require nearly opposite habits in the room. Dividing coverage well means colleagues can safely disagree with each other afterward, in the debrief, about what a session actually meant — that disagreement is the point of sending more than one person. A formal delegation to a body like the HMA/EMA Multistakeholder AI and Data Forum can't afford the same visible disagreement live, because the audience isn't your own management, it's a counterpart organization deciding how much weight to put on what your organization just said. Decide out loud, before you travel, which mode this particular trip actually is — a badge count alone won't tell your team which habits to bring.

Name a lead before you land

Someone needs the actual authority to make a live call when two colleagues' read of the room diverges mid-meeting, and that person needs to be named before the first session, not improvised in a hallway once a disagreement has already become visible to the other side. The lead doesn't need to be the most senior person in the delegation — seniority and situational judgment in a live multi-party negotiation aren't the same skill — but everyone in your group needs to already know who it is, and be genuinely willing to defer to that call in the moment rather than relitigating it in front of counterparts. Settling this on the flight over is late but survivable; settling it after the first awkward cross-talk in the room is not.

Assign territory, and defend it under pressure

Divide who owns which topic the same way you'd divide a co-presented talk's material — by who actually knows it best, not by rank — and then hold that assignment even when a more talkative colleague is itching to jump in on someone else's question. The discipline that's easy to state and hard to practice live is staying quiet on a topic that isn't yours, especially when you have a sharper answer than the colleague it belongs to. Interrupting your own delegate to correct or improve their answer in front of a counterpart reads worse than a slightly weaker answer delivered cleanly by the person who was actually assigned it; save the correction for the huddle afterward, not the room.

The five-minute huddle between sessions

Build in a short check-in between sessions or over the coffee break — not at the end of the day, when a drift in position has already had hours to become visible to the other side. Each person reports anything that changed their read of a topic since the delegation last synced, and the lead decides, in that five minutes, whether it changes what anyone says next. This is the same daily-sync habit a track-splitting team already uses to fold notes into one report, run at a tighter interval because the cost of staying silent about a drifting position is paid immediately, in the room, rather than discovered later in someone else's trip report. Confirming the return trip and any follow-on paperwork — entry requirements for every member of the delegation, not just the lead — belongs on the same pre-trip checklist; a delegation that arrives short one person at the border has already lost some of the coordination it spent weeks building.