Speaking for your organization, not for yourself

There is a particular kind of room — a working group, a standards committee, a multi-stakeholder forum with a name plate and a desk mic in front of you — where the physical setup does something to a sentence that a conference panel or a hallway conversation never does. Say something in that seat and the room hears it as your organization's position, not your own read of the topic, regardless of how you meant it. Nobody hands you a script for the difference. Most people learn where the line sits the first time they cross it by accident, in front of the people least forgiving of the mistake.

The room can’t hear the asterisk in your head

On a conference panel, the audience already expects a personal take — that’s the format's whole premise, and being invited onto one comes with an implicit license to say what you actually think. A working-group seat with your organization's name on the placard carries the opposite default. Say “personally, I’d go further than this,” and the minute-taker across the table writes down your organization's name next to a position nobody there cleared. The sentence felt like an aside when you said it; on the record, it reads as a stance. This is a different risk than an informal hallway conversation with a regulator, where the setting itself signals that nothing said is being minuted — a seated committee session with a name plate in front of you signals the opposite, whether or not anyone announces it out loud.

Get it cleared before the mic is live, not during

The discipline that actually prevents this is boring and happens well before the meeting: know the two or three positions your organization has already taken a formal view on, and know which topics on the agenda you genuinely don't have cover to speak to yet. That second category is not a failure to prepare — multi-stakeholder agendas routinely raise items faster than any one organization's internal process can clear a position on all of them. The honest move in that case is a version of “we don't have a settled view on this yet and will follow up in writing,” which costs you nothing and commits your organization to nothing it hasn't actually decided. Freelancing a plausible-sounding answer in the room because silence feels worse than an answer is how organizations end up bound to positions nobody upstream ever approved.

The phrase that flags a personal opinion

Genuine divergence between your own read and your organization's cleared position does happen, and it's worth having one clean way to say so rather than improvising it live. “Speaking personally rather than for [organization]” is a plain, working version — not because the phrase is magic, but because saying it consistently trains the room to actually hear the distinction instead of assuming every sentence from your seat carries equal institutional weight. Use it sparingly enough that it still means something when you reach for it; a habit of prefacing everything with the disclaimer teaches the room to stop listening for it, which defeats the entire point of having it available.

When new information changes the position mid-meeting

The harder version of this problem shows up live: a fact surfaces in the discussion that would plainly change your organization's cleared position if the right person back at the office knew it right now. The instinct is to update the position on the spot, in the room, because that's what a good-faith participant in the conversation would seem to do. Resist it. The honest answer is to flag the new information as exactly that — “that changes something for us; let us take it back and follow up” — the same discipline a silent observer at a public meeting already has to practice by default, applied here to a seat where you do have a voice but not the unilateral authority to spend it on a position nobody cleared. A follow-up email a day later, with the position actually confirmed, does more for your organization's credibility than a confident-sounding answer given live and quietly walked back afterward.