Cross-Team Meeting Phrasebook

Most of the difficulty you felt in that meeting was created the day before, by walking in cold. Two messages fix half of it.

The pre-read, sent 24 hours ahead

Why it works: people who have already seen the problem ask better questions and give you a quieter room. It also means your opening doesn't have to carry everything.

The pre-wire — one DM to one person on the other team

Why it works: walking into a room where one person already understands and agrees with you changes the whole dynamic — you are no longer alone, and they will often make your argument for you. This single habit is one of the clearest differences between senior and staff behaviour.

Write your first four sentences word for word

Not bullet points. Full sentences, in a doc, which you read aloud twice before joining. The opening is the moment your heart rate is highest and your English is weakest; it is the one part you should never improvise. Use the prep card below.

Greeting is a ritual, not a creative act. Use the same words every time.

Greeting — small meeting, people you know

Greeting — people you haven't met

Why it works: naming your system and team in the first ten seconds tells people how to interpret everything you say afterwards. Keep doing this for months; it never reads as unnecessary.

Set the shape and the time box

Why it works: it tells people how long you will be talking, so nobody is waiting for you to stop; it names the exit condition, so the meeting can be judged; and "does that work for everyone" gets a small yes early, which makes the bigger yes later easier.

If you're nervous

Why it works: a diagram moves attention off your face and onto an object, gives you something to point at instead of describe, and lets you recover your sentence while people read.

This is the part you said was hardest, and there is a fixed structure for it. Four sentences, in this order, every time. Learn the order and you never have to invent a structure again.

The same four sentences, filled in

Why it works: the ask arrives at second forty, not minute ten. The most common failure in cross-team meetings is explaining for ten minutes and asking in the final thirty seconds, once everyone has stopped listening and two people have opened Slack.

Give them the one-line version to hold on to

When they don't know your system at all

Why it works: it gives people permission not to know, and it bounds how much they have to hold in their head. "Everything else you can ignore today" is the most generous sentence in this document.

Analogy openers, when the mechanism is unfamiliar

Signposting phrases do two jobs at once: they tell listeners where they are, and they buy you the half-second you need to compose the next sentence. This is the single most direct fix for "I know it technically but I can't say it."

Signposts

Checkpoints — roughly every ninety seconds

Why it works: a checkpoint turns a monologue into a conversation and gives you a legitimate pause. Note that "am I explaining this clearly?" puts the burden on your explanation; "does that make sense?" repeated nervously puts it on their intelligence and makes you sound unsure. Ask it once, deliberately, not every thirty seconds.

Answer shapes

Why it works: "short answer / longer answer" gives you a complete, confident first sentence while your brain assembles the rest. It is the most reusable sentence in the phrasebook.

Clarifying

Why it works: restating is the highest-value habit for a non-native speaker in a fast room. It catches the sentence you half-heard, it slows the meeting to your pace without anyone minding, and it makes you look like a careful listener rather than a slow one.

Getting a commitment — the hard part

Why it works: "is that a no, or a not this quarter" is polite, completely unaggressive, and forces the one distinction you actually need. Vague agreement is what makes you look weak three weeks later, not the asking.

Asking for help without sounding lost

"Thanks for letting me know about this component" is a receipt, not a question. It's polite, it ends the exchange — and it leaves you exactly as lost as you were, while everyone moves on. Nobody expects you to know another team's internals. What they do notice is nodding along and then asking something ten minutes later that shows you didn't follow.

Anchor it to something you already know — the best single question

Why it works: you don't need to learn their system today — you need to place it on the map you already have. One of these three questions almost always gives you enough to follow the rest of the meeting, and they take four seconds to ask.

Ask for the one-line version, openly

Why it works: "the one-line version" and "two questions and then I'll stop" both bound the answer, so nobody fears a ten-minute detour. Saying plainly that something is new to you costs you nothing across team boundaries — it's expected. Pretending otherwise is what costs you.

Guess out loud — slightly wrong is efficient

Why it works: a wrong guess gets corrected with precision — people can't resist fixing an inaccurate summary, and you get a much better explanation than an open question would have produced. It also shows you were listening. Low risk: being approximately wrong about another team's component is not a thing anyone holds against you.

When it isn't needed for today's decision — defer cleanly

Why it works: "can you point me at the doc" is the move that converts a gap into homework instead of a silence. It's also a small, easy yes — people like being asked for the pointer.

Then actually close the loop, same day

Why it works: write the unfamiliar term down verbatim during the meeting, look it up within the hour, and send this. The pattern people remember is not "he knew everything" — it's "he said he'd come back, and he came back the same day, with a sharper question." That is the reputation you want, and it's entirely within your control.

Staff engineers are not people who never get pushed back on. They are people who stay calm and specific when it happens.

Disagreeing

Why it works: each of these separates the idea from the person, and each leaves you a way to be wrong without losing face. "I might be missing something" is not weakness — it is what lets you disagree hard in the next sentence.

When someone is dismissive

Why it works: taking the blame for the explanation costs you nothing and de-escalates instantly, and it gets you a second attempt with your strongest evidence.

When you don't know

Why it works: saying this plainly and then delivering the answer the same day raises your credibility. Guessing in the room and being corrected later lowers it. Senior people do this constantly; watch for it and you'll start noticing.

When the meeting drifts

This is two separate problems wearing one coat. There's the real-time problem — you lose your thread and the meeting loses time. And there's the underlying one — your teammate doesn't know what his job in this meeting is. Manage the first in the room; fix the second outside it. Never fight it in front of the other team: visible friction between the two of you reads to them as "these two aren't aligned", which quietly weakens whatever you're asking for.

Prevent it — say the split out loud at the start

Why it works: this is the highest-leverage move on the page and it takes six seconds. Most chronic interrupting is an ally with no assigned role trying to be useful. Give him a slot in public and he'll wait for it — he's no longer competing for one. It also makes you look generous rather than territorial, in front of the other team.

In the moment — hold the floor, warmly, without stopping

Why it works: say his name — that's what makes it register, and it's what stops the sentence without sounding sharp. Every one of these promises him the floor in a few seconds, so it reads as sequencing, not silencing. Don't pause before saying it; the pause is the opening he's been taking.

If he's already talking over you

Why it works: never abandon the sentence you were in. Repeating your last line before continuing is what makes the interruption visible without anyone having to name it, and it costs three seconds. If you drop the thread instead, the room learns that interrupting you works.

When it's eating the meeting

Why it works: "ours, not theirs" is a graceful way to move an internal argument out of a cross-team room without criticising anyone. It also signals to the other team that you're protecting their time, which they will notice.

The conversation to have once, privately, calmly

Why it works: no accusation and no count of offences — it's framed as a "we" problem, with the cost placed on how the other team experiences us, which is hard to argue with. It ends in a concrete mechanism rather than a request to behave better. Most people agree immediately and are a little embarrassed; don't press the point once they do.

If it continues after that, name it once, privately, plainly: "It happened again today — I got cut off three or four times. I want to fix it, because it's costing us time in the room." Say it within a day of it happening, not as a stored-up list. If it's persistent and affecting how visible your work is, it's a reasonable thing to raise with your manager — framed as a working arrangement you're already fixing, not as a complaint.

And check the mirror once. If you talk for four minutes without a checkpoint, people jump in — that's a vacuum, not rudeness. The ninety-second checkpoints from the explaining section cut interruptions on their own, because they create legitimate openings instead of forcing people to make one.

Write these four on a sticky note on your monitor. This week. You will need them, and in the moment you will not be able to invent them.

Why it works: two seconds of silence reads as thinking. Two seconds of "um, so, basically, like, yeah" reads as uncertainty. The gap is identical in length; only the filling differs. "I want to say this precisely" frames your pause as care about accuracy, which is exactly the thing you want to be known for.

One more, and it is the highest-leverage change available to you: speak about fifteen percent slower than feels right, and pause at the commas. Non-native speakers under stress speed up, which costs clarity and reads as nervousness. Slowing down buys composition time and reads as authority. Nobody has ever complained that a staff engineer spoke too deliberately.

Never let a meeting end by everyone drifting away. Whoever closes the meeting is running it.

When nothing was decided

Why it works: naming the non-decision keeps it from quietly becoming your problem alone, and "we can decide in the thread by Thursday" converts a stuck meeting into a dated commitment.

Why it works: whoever writes the summary owns the narrative of what happened, and quietly becomes the person the work routes through. It is the cheapest staff-level move available, it plays to your strength — you have time to choose your words — and over a year it is very visible to the people who decide promotions.

Fill this in before a meeting and read the result aloud twice. It's pre-loaded with the worked example — replace it with your own. Your draft is saved in this browser.

The left column isn't bad English. It's uncertain English — it hedges, apologises, or leaves out the number. The right column is the same thought with the uncertainty removed.

Twenty terms that let you say something precise in four words instead of three sentences. Precision is what makes you sound senior — not fluency.

Different etiquette, and mixing them up is what makes a meeting feel awkward.

One change per week, practised in meetings you're already in. Don't run two at once — the point is that each becomes automatic before you add the next.