The Insight Desk

3 Assumptions to Check Before an International Presentation

Clear English is only part of an international presentation. Check the context, language, and decision criteria your audience may not share.

A presenter reviewing audience notes beside a presentation screen before an international meeting.

You have already done a lot of the work.

The English is clear. The slides are tidy. You know the material well enough to explain it without staring at the screen like it owes you money.

And yet, in an international meeting, the audience can still look politely unconvinced.

That does not automatically mean your English is the problem. Often, the presentation assumes that the audience already shares three things: your context, your language, and your criteria for deciding what matters.

They may not.

Short answer: Before presenting internationally, check whether your audience shares your background context, understands your key terms, and will judge the proposal by the same criteria you expect. Clear English helps, but shared understanding needs to be designed.

This is not a call to make every presentation slower or simpler. It is a call to stop making the audience do invisible catch-up work.

Assumption #1: “They already know why this matters.”

You know the history. You know why the project became urgent, what happened last quarter, and why this one metric has everyone’s attention.

An audience outside that immediate context does not. If your first slide begins halfway through the story, they have to reconstruct the first half while you are already making the recommendation.

People can understand every sentence and still miss the stakes.

What to do instead

Give the audience the smallest useful amount of context before you ask them to care. One or two sentences is often enough.

For example:

Before: “We need approval for the next phase of the platform programme.”

After: “Our current platform cannot support the reporting requirements introduced for our overseas partners. Today, we are asking for approval to fund the next phase before the manual workaround becomes the default process.”

The second version does not drown the room in history. It gives people a reason to listen to the recommendation that follows.

A presenter adding a short context note to prepare an unfamiliar audience for a proposal.

Assumption #2: “This term means the same thing to everyone.”

Every organisation has its own private dialect. Acronyms. Project names. Familiar phrases that save time inside the team and cause mild confusion everywhere else.

Industry terms can create the same problem. A phrase may be technically correct, but still carry different meanings across markets, functions, or disciplines.

The aim is not to remove every specialist term. Experts should be allowed to sound like experts. The aim is to make sure the essential terms do not become locked doors.

What to do instead

For every key term, choose one of three moves:

  • Define it once in plain language.
  • Replace it with a more widely understood phrase.
  • Remove it if it does not carry its weight.

If you need a long explanation every time an acronym appears, it is not saving time. It is charging interest.

For example:

Before: “We need a decision on the RFP.”

After: “We need approval to issue the request for proposals: a formal invitation for suppliers to submit a bid.”

The second version keeps the professional term, but it does not make unfamiliar listeners guess what is actually being decided.

Assumption #3: “They will judge this by the same criteria we do.”

This is the one that can make a well-built deck feel strangely unpersuasive.

You may be leading with the evidence your team values most: technical detail, a detailed timeline, an impressive feature list, or the effort already invested. Your audience may first want to know something else: the commercial case, the risk, the implementation burden, the customer impact, or what happens if nothing changes.

Neither side is necessarily wrong. But if you answer questions the audience has not asked yet, your best evidence arrives too early—or feels irrelevant.

What to do instead

Before you finalise the order of the deck, ask:

  1. What decision do I need from this audience?
  2. What would make that decision feel risky to them?
  3. What evidence would reduce that risk first?

Then build the presentation in that order.

For example, a technical team may want to begin with architecture. A senior cross-functional audience may need the customer problem, the cost of delay, and the decision required before they need to see the architecture at all.

A presenter comparing audience questions with the evidence in a presentation deck.

A three-question check before you present

You do not need to rebuild the entire deck every time you present internationally. Run this short check first:

  1. What background does this audience not have? Add only the context they need to understand the stakes.
  2. Which terms need translation, not just English? Define the language that is obvious to you but not to them.
  3. What will this audience need to believe before they can decide? Put that evidence before the detail that supports it.

The goal is not to make your presentation generic. It is to make it usable by the people in the room.

Your audience should not have to reverse-engineer your point

An international audience is not one homogeneous group with one set of preferences. The people in the room may differ by market, role, technical knowledge, or decision authority. That is exactly why assumptions matter.

When a presentation makes context, language, and decision criteria visible, the audience can spend its attention on the idea instead of working out how to interpret it.

If you are unsure whether the friction is in the deck, script, message, or audience framing, get an outside view before the presentation. Send a deck, script, outline, or short practice video for a Free Presentation Diagnostic. You will get focused feedback on what is blocking clarity and a recommended next step.