The success or failure of an English presentation isn't determined by clever phrasing. Everything depends on a structure designed from the starting point of 'Who are you trying to move, for what purpose, and how?' Proposing a strategy to a CxO, presenting a solution to a client, explaining an architecture to a technical team—when the audience changes, the fundamental framework of the presentation must also change.
In this article, we will focus not on collections of phrases, but on 'the structure of the presentation itself.' Based on ELT's experience coaching over 10,000 individuals, we will explain three structural patterns and how to use them for different audiences.
The Real Reason 'English Presentation Phrasebooks' Don't Work
"Good morning, I'm here today to talk about..." "In conclusion, I'd like to summarize..."—These phrases are correct, and there's no harm in remembering them.
However, the most common feedback we receive from ELT students is, 'After my presentation, I was asked, "So what?" and "What's the ask?"' The phrases were perfect, but the audience wasn't moved to action.
The problem isn't the phrasing; it's the structure.
The typical Japanese presentation style is often built in the order of 'Background → Analysis → Consideration → Conclusion.' The audience only reaches the conclusion after listening to the very end. If you simply translate this structure into English, an English-speaking audience will lose focus by the third minute, wondering, 'So, what's your point?'
English presentations are the opposite. 'Conclusion → Rationale → Specific Examples → Call to Action'—it's a structure where you state what you want them to do in the first 30 seconds and use the remaining time to prove its validity.
Adapting Your Structure to Your Audience—Three Frameworks
Trying to get through every presentation with a single 'Introduction → Body → Conclusion' template won't work in a business setting. The optimal structure changes fundamentally depending on 'who you need to move.'
① The Pyramid Structure — For Moving CxOs and Decision-Makers
When to use it: Proposing strategy to management, reporting to the board, requesting budget approval
CxOs have limited time. It's not uncommon to have only 10 effective minutes to get a decision in a 15-minute slot. Conclusion first, limit your supporting points to three, and clearly state 'what you want them to do'—these are the ironclad rules of the pyramid structure.
Structure (for a 15-minute presentation):
Part | Time | Content |
|---|---|---|
Ask | 1 min | Conclusion and call to action. "Today, I am requesting your approval for [X]." |
Key Message | 1 min | "There are three reasons for this." |
Evidence ①②③ | 2-3 min each | Support your rationale with data, case studies, and comparisons. |
Call to Action | 1 min | "As a next step, I would like to proceed with [X]." |
Q&A | Remaining time | Question & Answer |
Example Phrases:
- "I'm here to request your approval for [X]. Let me walk you through the rationale."
- "There are three reasons why this is the right move."
- "The projected ROI is 3.2x over 18 months."
- "Based on this analysis, I recommend we proceed with [action] by [date]."
What to avoid: Starting with background information. Begin with 'what the conclusion is,' not 'why this analysis was done.' CxOs want to know the 'So what?' in the first 30 seconds.
② The Storytelling Framework — For Gaining Empathy from Clients and Internal Teams
When to use it: Proposing a solution to a client's problem, internal project kick-offs, sharing a team vision
If the pyramid structure is about 'moving with logic,' the storytelling framework is about 'moving with empathy.' The first goal is to make the audience feel 'this is my problem.'
Structure (for a 15-minute presentation):
Part | Time | Content |
|---|---|---|
Hook | 1 min | A question or anecdote that makes the audience feel personally involved. |
Problem | 3 min | Describe the current problem in detail, supported by data. |
Turning Point | 1 min | "But, things can change if we do this." |
Solution | 5 min | Details of the proposed solution. |
Vision | 2 min | A picture of the future after implementing the solution. |
Q&A | Remaining time | Question & Answer |
Example Phrases:
- "Imagine this scenario: [describe a specific situation]"
- "The core challenge we're facing is..."
- "Here's where the opportunity lies."
- "If we implement this, the impact would be..."
What to avoid: Talking about the solution right at the beginning. The client first needs to feel that you have correctly understood their problem. Presenting a solution without first establishing empathy for the problem will just sound like a sales pitch.
③ The Data-Driven Framework — For Convincing Technical Teams and Analysts
When to use it: Proposing a technology choice, reporting on data analysis, presenting an ROI analysis
What technical teams and analysts want isn't a moving story, but reproducible evidence. A scientific structure of Hypothesis → Verification → Conclusion builds trust.
Structure (for a 15-minute presentation):
Part | Time | Content |
|---|---|---|
Hypothesis | 1 min | "Our hypothesis is [X]." |
Methodology | 2 min | How you verified the hypothesis. |
Data / Findings | 6 min | Data and analysis results. Graphs and charts take center stage. |
Implications | 3 min | What the data means. |
Recommendation | 1 min | Recommendation based on the data. |
Q&A | Remaining time | Question & Answer |
Example Phrases:
- "Our hypothesis was that [X] would lead to [Y]."
- "We tested this across [N] data points over [period]."
- "The data shows a clear correlation between [A] and [B]."
- "Based on these findings, we recommend [action]."
What to avoid: Subjective claims without data. A technical team will always ask, 'What's the evidence?' Make "The data shows..." and "The evidence suggests..." your default, not "I feel..." or "I believe..."
The Opening—Make Them Believe It's Worth Listening in the First 30 Seconds
There is a principle common to all three frameworks: the battle for an English presentation is won or lost in the first 30 seconds.
The typical Japanese-style opening, 'Thank you for taking time out of your busy schedules to be here today. My name is [Name] from the [Department]...' is unnecessary in an English presentation. The audience is thinking, 'So, what's this about?'
Here's how to design an opening tailored to your audience.
For CxOs: Start with the conclusion.
- "I'm requesting approval for a ¥50M investment in [X]. Here's why it makes sense."
State what you want in a single sentence. You can provide background if they ask for it.
For Clients: Start with a question.
- "How much revenue are you leaving on the table due to [problem]?"
Dive into the client's problem to make it personal for them.
For Technical Teams: Start with a conclusion + a number.
- "We've identified a 40% performance improvement by migrating to [architecture]. Let me show you the data."
Grab their interest with a number and lead into the main body with data.
The Body—Does Every Slide Answer 'So What?'
The most important thing in the body of your presentation is that for every single slide, you can answer the question 'What is the point of this slide?' in one sentence. A slide for which you can't answer this question may contain information, but it doesn't contribute to the story of your presentation.
How to Create Slide Headlines (Titles)
Your slide titles should be 'messages,' not 'labels for information.'
NG | OK |
|---|---|
Q3 Sales Data | Q3 Sales Exceeded Target by 12% |
Market Analysis | Japan Market Represents 20% Untapped Growth Opportunity |
Competitive Landscape | We Have a 6-Month Head Start Over Competitors |
Can you read just the slide titles from top to bottom and follow the story of the presentation?—This is the most reliable way to self-check. If you can't, you need to revise your structure.
Transition Phrases (Bridging the Gaps Between Slides)
Phrases that smoothly connect one slide to the next are essential for maintaining the flow of your presentation.
- "Now that we've established [A], let's look at [B]."
- "This leads us to the key question: ..."
- "Building on this data, the implication is..."
- "So far we've covered [X]. Now let's turn to [Y]."
If you switch slides without a transition, the audience will lose the context of 'why are we talking about this now?'
The Closing—End by Answering 'So, What Should I Do Now?'
Ending a presentation with the Japanese equivalent of 'That is all. Thank you for your attention,' is the biggest missed opportunity in an English presentation.
The end of an English presentation should be a three-part package: 'Reiterate Conclusion' + 'Call to Action' + 'Transition to Q&A.'
Call to Action Phrases
- "Based on what I've presented, I'd like to request [specific action]."
- "The next step I'm proposing is [action] by [deadline]."
- "I'd welcome your feedback on the approach before we proceed."
The key to a call to action is to 'be specific.' A vague 'Please consider it' won't lead to action. Specify who needs to do what by when, such as 'approval for X' or 'a response by Y.'
Transitioning to the Q&A
- "I'd like to open the floor for questions."
- "I've kept some time for discussion. What questions do you have?"
One point to note: "Do you have any questions?" is a closed question that can easily be answered with "No." You are more likely to get questions if you ask, "What questions do you have?"
For more on handling the Q&A session, please see this article.
Mastering the Q&A in English Presentations: 'Aikido' Techniques to Deflect Tough Questions
3 Steps to Convert a Japanese-Style Presentation to an English-Style Framework
Many business professionals simply translate their Japanese-language presentation materials into English and present them as is. However, even if the language is translated, if the structure remains Japanese-style, feedback like 'The conclusion comes too late' or 'I don't get the "so what?"' is inevitable.
You can convert a Japanese-style structure to an English-style one in these three steps.
Step 1: Move the last slide (the conclusion) to the beginning. The final slide of a presentation created in a Japanese style is often the 'Conclusion' or 'Proposal.' Move this slide to become the very first one.
Step 2: For each slide, add a one-sentence 'So what?'. For each slide, check if you can state 'what this slide is ultimately trying to say' in a single sentence. A slide you can't summarize has information but no message. Be bold and delete it.
Step 3: Rearrange the remaining slides in the order of 'Conclusion → Rationale → Specific Examples.'
Example of Conversion:
Japanese Style (Before) | English Style (After) |
|---|---|
① Background / Market Environment | ① Conclusion + Ask (Moved from the end) |
② Competitor Analysis | ② Rationale 1 (Data Summary) |
③ Internal Analysis | ③ Rationale 2 (Competitor Comparison) |
④ Problem Identification | ④ Rationale 3 (Feasibility) |
⑤ Proposed Measures | ⑤ Next Steps + Call to Action |
⑥ Schedule | |
⑦ Conclusion |
A 12-slide presentation becomes 7 slides, and though the content is the same, the impact on the audience is completely different. Reducing the number of slides isn't about 'cutting corners'; it's about 'sharpening your message.'
Is Your English Presentation Structure Ready for the Real World?
The three structural patterns and conversion techniques introduced in this article can be used immediately in your next presentation preparation.
However, there is a huge gap between 'understanding the structure intellectually' and 'actually delivering a 15-minute presentation in English that moves the audience.' Designing the slides with the right structure, delivering the entire presentation in English, and responding instantly to Q&A—this entire process cannot be polished without rehearsal and feedback.
At ELT, for those at an intermediate level or higher in business English, we offer one-on-one counseling and trial lessons with native instructors who hold professional qualifications in English language education.
- Presentation Structure Diagnosis: Bring your actual presentation materials for professional feedback on both structure and delivery.
- Mock Presentation + Q&A: The instructor will play the role of a CxO or client, allowing you to rehearse under realistic pressure.
- 'Japanese-style → English-style' Conversion Support: Receive concrete advice on how to restructure your existing Japanese presentation materials into an English-style framework.





