A keynote or conference talk is not a longer version of a business presentation. The audience is different — they came to be informed or inspired, not to make a decision. The format is different — you're usually alone on a stage, often without the safety net of slides to carry the argument. And the standard is different: a keynote that merely conveys information correctly is considered a failure.
For non-native English speakers, the challenges multiply. Performing at this level in your second language requires control over your material, your delivery, and your language that is substantially harder to achieve under the pressure of a live audience.
This post is a practical guide to doing it well.
The Architecture of a Talk That Works
The structure of a keynote is not the structure of a report. A report is organised by category. A keynote is organised by experience — by what you want the audience to think and feel at each moment.
The most reliable architecture:
Opening (first 90 seconds): Don't introduce yourself. Don't thank the organisers. Start with the thing that earns attention — a specific claim, a surprising statistic, a question that makes the audience aware of a gap they hadn't noticed. You have about ninety seconds before the audience decides whether this is worth their full attention. Use them.
The problem or tension: Every good talk is organised around something that is broken, unresolved, or not widely understood. Name it. Make the audience feel the problem before you offer the solution.
Your answer: This is the body of the talk. One central idea, explored from multiple angles, illustrated with specific examples. Not three points with sub-bullets. One idea, thoroughly explored.
The implication: What should the audience do or think differently because of this? Land the takeaway explicitly. Don't leave it implicit.
Close: Return to what you opened with, or take it somewhere new. End with a sentence you wrote before you built the talk — a line you're proud of, that closes the loop.
| Section | Common mistake | What works instead |
|---|---|---|
| Opening | "Good morning everyone, I'm delighted to be here..." | Start with a claim or a question — earn attention before introducing yourself |
| Body | Three parallel points, each with equal weight | One driving argument, with sub-points as evidence, not additions |
| Close | "So in conclusion, as I've talked about today..." | Return to the opening image or statement — create a closed loop |
The Language of Authoritative Delivery
What makes a speaker sound authoritative is not sophistication of vocabulary — it is command of pace, deliberate pausing, and declarative structure.
Declarative sentences over hedged ones. Compare:
- "It seems that one of the things that might be contributing to this problem could be..."
- "The root cause is this."
The second sentence is more authoritative because it commits. Audiences give authority to speakers who commit to their claims, even provisionally.
Short sentences for emphasis. Long, complex sentences are harder to follow when spoken. When you want something to land:
- "This is the insight most companies miss."
- "That number is wrong. It has always been wrong. And the consequences of treating it as right are what I want to talk about today."
Signpost language helps an audience track where they are in your argument:
- "The first thing I want to say about this is..."
- "Here's where it gets interesting."
- "This is the thing that changed my mind."
- "Let me come back to that — but first."
These phrases don't slow the talk down. They orient the audience and give them a moment to catch up.
Handling Nerves and English Under Live Pressure
The specific failure mode under live speaking pressure: speed. When anxious, speakers accelerate — sentence length grows, breathing shallows, and pace increases. For non-native English speakers this compounds: fast speech in a second language means more errors, less control, and harder comprehension for the audience.
The intervention is simple and uncomfortable: deliberate slowing. The pace that feels slightly too slow from the stage sounds approximately right to the audience. Practise at this pace before you go on. You will feel like you're going too slowly. You won't sound that way.
The deliberate pause is your most powerful tool. A two-second pause after a strong statement doesn't create dead air — it creates emphasis. It gives the audience time to feel the weight of the thing you just said. Most speakers use almost no silence. The ones who use it well are the ones that audiences remember.
If you lose your place or stumble:
- Don't apologise in the moment — it draws attention to something the audience may not have noticed.
- Pause, breathe, find the thread. Ten seconds of silence on stage feels like ten minutes to the speaker. To the audience, it looks like thinking.
- Summarise back to yourself: "Let me come back to the core point" — this both gives you a moment and returns the audience to the through-line.
Working With Slides
Slides are a support structure, not a script. If your slides contain the talk, you will read them. Reading slides to an audience is the single most common public speaking mistake, and it destroys the speaker's authority completely.
The rule: your slide should contain only what cannot be spoken. A striking image. A key statistic. A framework or diagram. A single, bolded claim.
Language for transitioning slides without the transition being the thing the audience notices:
- "Which brings me to the question of..." (slide advances)
- "Here's the data that makes that argument." (slide advances)
- "Let me show you what I mean." (slide advances)
The slide should feel like it's appearing to support what you're saying, not like you're waiting for the slide to tell you what to say next.
Q&A at the End of a Keynote
Q&A at a conference or keynote is different from Q&A in a meeting. The audience is larger, the questions are less predictable, and the social dynamics are more visible. Some specific language for the most common situations:
Buying time on a hard question: "That's a question I want to answer properly. Let me think for a moment."
Handling a question that's really an argument: "I hear a challenge in that. Let me engage with the strongest version of it."
Deflecting a question that's outside your scope: "That's genuinely outside what I know well — I'd rather give you a useful answer than a confident one. I don't have that one."
Redirecting a rambling question: "I want to make sure I've understood what you're asking — is the core question X?" (State X, then answer X.)
When you don't know: "I don't have a reliable answer to that — my instinct is X, but I'd want to verify before I commit to it publicly."
Practising for a Non-Native English Standard
The preparation required for a keynote in your second language is substantially more than the preparation for the same talk in your first language. The rule is simple: the talk should be at the edge of automatic before you go on stage.
"Automatic" means you can deliver the main through-line even if you're distracted, nervous, or disoriented — which you will be. The specific content of each section can vary on the day; the spine of the talk should be so familiar that it runs without much conscious effort.
How to get there:
- Record yourself on video and watch it. This is uncomfortable and necessary.
- Present to a small, live audience at least once before the main event. The physical experience of being watched is not replicable by practising alone.
- Time yourself on every run-through. Talks that run over time are a signal of under-preparation.
- Prepare for the questions you don't want to get, not just the ones you expect.
Frequently Asked Questions
How long should I plan for per slide?
In a standard talk, two minutes per slide is a useful planning figure — but this should not be mechanical. Some slides are visual support that you spend thirty seconds on. Some are data-heavy and need longer. The rule is: no slide should be on screen for so long that the audience has read everything on it and moved on before you have.
My accent has been commented on in past talks. Should I address it?
Only if it serves the audience. A brief, confident acknowledgement can build rapport: "My first language is X, so I'll ask you to tell me if I lose you." But this only works if it's genuinely brief and you don't return to it. Prolonged or anxious apology for your accent draws attention to it as a problem — which it isn't.
Is it better to memorise the talk or work from notes?
Neither pure memorisation nor heavy note-reading works well. The effective approach is a memorised structure with a loose script — you know the shape and the key lines, but you're not reconstructing exact sentences. This gives you flexibility when the unexpected happens while keeping the talk coherent.
How do I handle a panel discussion in English, rather than a solo talk?
Panels are a different skill. The main challenges are: getting enough space to make your point, being heard over stronger speakers, and bridging back to your core message. Use phrases like: "I want to build on what X said and add one thing..." or "That's the framing I'd challenge, actually — here's why..." Panels reward people who say fewer things more memorably, not more things more quietly.
If any of this resonates, I run weekly sessions with founders and senior professionals on exactly this kind of thing. Free 10 minute fit call to see if it's a fit. Book here.