『The Presentations Japan Series』のカバーアート

The Presentations Japan Series

The Presentations Japan Series

著者: Dale Carnegie Training
無料で聴く

概要

Persuasion power is one of the kingpins of business success. We recognise immediately those who have the facility and those who don't. We certainly trust, gravitate toward and follow those with persuasion power. Those who don't have it lack presence and fundamentally disappear from view and become invisible. We have to face the reality, persuasion power is critical for building our careers and businesses. The good thing is we can all master this ability. We can learn how to become persuasive and all we need is the right information, insight and access to the rich experiences of others. If you want to lead or sell then you must have this capability. This is a fact from which there is no escape and there are no excuses.Copyright 2022 マネジメント マネジメント・リーダーシップ 経済学
エピソード
  • Thanking The Speaker
    2026/03/16
    Presentations have a cadence: promotion, registration, MC opening, speaker delivery, and then the closing that shapes the final memory. In many well-run events (industry associations, chambers of commerce, corporate briefings, webinars on Zoom or Microsoft Teams), the MC and the person giving the vote of thanks are separate roles. If you're the one thanking the speaker, you're not doing "admin" — you're delivering a short, public, brand-defining moment at the very end, when recency bias is at its strongest. Why is thanking the speaker a "last impression" moment leaders should take seriously? Because the vote of thanks is a mini-presentation that heavily influences what people remember about the event — and you. At the end, the audience is thinking about trains, inboxes, and the next meeting, so whatever happens now becomes the emotional "closing scene." In Japan, formality and role clarity matter more than many Western settings; in the US, audiences expect crisp confidence; in Australia, they expect practical brevity without self-importance. This role can add to or subtract from your personal and professional brand because people are judging your competence, tone, and respect for others. Done well, it elevates the speaker and the host organisation. Done badly, it jars and feels amateurish, even if the talk was strong. Mini-summary / Do now: Treat this as a 60-second closing performance. Decide in advance: respectful tone, one insight, clean handoff. How do you prepare to thank a speaker without sounding generic? You prepare by listening for one audience-relevant idea and capturing it as a tight, quotable takeaway. The trap is turning your thanks into a vague "Great talk, learned a lot" filler. Instead, listen with intent: what point will most resonate with this audience (executives vs frontline, sales vs HR, B2B vs consumer)? If you can get the slides or outline beforehand, your job gets easier because you can anticipate themes and pick the strongest one. In a multinational (Toyota, Rakuten, Unilever), this might be strategy alignment or governance; in a startup, it might be speed and execution; in a professional association, it might be standards and reputation. You're not summarising the entire presentation — you're spotlighting the single idea that makes the room feel it was worth attending. Mini-summary / Do now: Write down three candidate "best points" during the talk, then circle the one with highest relevance to the room. What's the biggest mistake people make when thanking the speaker? They compete with the speaker by rambling, summarising too much, or using the moment to promote themselves.You've seen it: the applause dies, people stand up, and the "thank you" person launches into a speech about their own opinions. That wastes time and feels self-centred — especially at the end when the audience is mentally leaving. The vote of thanks should be short, sharp, and terrific. In Japan, over-talking can feel disrespectful to the schedule and group; in the US, it reads as self-promotion; in Australia, it reads as waffle. The audience wants closure, not another keynote. Your credibility rises when you demonstrate discipline: one reference to value, one audience-focused insight, and then you hand back to the MC or close the event cleanly. Mini-summary / Do now: Keep it under 60–90 seconds. One insight only. No "second presentation," no personal agenda. How does the Thierry Porte example show the power of a great vote of thanks? A brilliant thank-you can outshine a weak presentation and instantly boost how smart and credible you seem. The story is memorable because the main talk was a disaster: the presenter scrolled a tiny-font document on screen and effectively read it aloud, damaging the firm's brand. Then Thierry Porte (then President of Morgan Stanley Japan, later at Shinsei Bank) delivered short, intelligent remarks thanking the speaker — and those remarks created a stronger impression than the talk itself. Years later, the details faded, but the judgement remained: "this guy is really smart." That's the leverage of a well-executed closing: you can't always control the main speaker's quality, but you can control how the event lands. That landing affects networking, reputation, and trust. Mini-summary / Do now: Aim for "intelligent and concise," not "complete." Your goal is a strong impression, not a full recap. What is the TIS model and how do you use it to thank a speaker professionally? TIS gives you a reliable structure: Thanks, Interest, then Formal Thanks — so you're respectful, relevant, and brief. Start with Thanks using the right level of formality. In Japan, honourifics matter: "-sama" signals a different respect level than "-san," and professions like bengoshi (lawyer) may be addressed as "Sensei." Next, Interest: choose one element of the talk most likely to have resonated with the audience (not necessarily your favourite). Finally, Formal Thanks: if the MC will...
    続きを読む 一部表示
    14 分
  • How to Introduce A Speaker
    2026/03/09
    A strong speaker introduction isn't "filler" before the real talk starts — it's the moment the MC borrows the room's attention and hands it to the presenter. When MCs mumble, freestyle the bio, or get dates wrong, they don't just annoy the speaker; they weaken the event's credibility and the audience's willingness to listen. A professional introduction quietly signals: this person is worth your time — and it resets the room away from phones, side chats, and mental noise. Why do so many MC introductions sound awkward or unprofessional? Most MCs treat the introduction as a low-status task, so they don't prepare — and it shows immediately. When you bumble through a bio, skip key achievements, or scramble the timeline, you damage the speaker's authority and your own personal brand at the same time. In corporate settings (Toyota-style formality, Big Four precision, or Silicon Valley speed), audiences judge competence fast: the MC's tone sets the "quality bar" for the whole session. If the introduction feels casual, people assume the content will be casual too. Do now: Treat the introduction like a 60–90 second "brand moment" for the event — and rehearse it once out loud. Should an MC read the speaker's bio exactly, or can they freestyle? Use the speaker's prepared intro as the script, not a suggestion, because it's designed to build credibility in the right order. Speakers write bios strategically: the most relevant authority comes first, the prestige markers support it, and the timeline is accurate. Freestyling often removes the strongest proof points, creates factual errors, or changes emphasis. In Japan, mistakes can feel disrespectful; in the US, they can sound sloppy; in Australia, they can come across as "not taking it seriously." If you must adapt, do it with the speaker's permission and keep the structure intact. Do now: Ask the speaker, "Anything here you want emphasised or shortened?" — then stick to the agreed script. What is the TIQS model for introducing a speaker? TIQS is a simple four-step introduction framework: Topic, Importance, Qualifications, then Speaker Name. You start by reminding the room what the talk is about (Topic), then sell why it matters to them (Importance), then establish why the presenter is credible (Qualifications), and only then reveal the name (Speaker Name) to create anticipation. This order works because it aligns with how attention and trust form: relevance first, value second, authority third, and the "hand-off" last. It's also event-proof: whether it's a chamber of commerce lunch, a boardroom briefing, a webinar on Zoom/Teams, or an industry conference, TIQS keeps you brief, focused, and helpful. Do now: Draft your TIQS intro in four short blocks — one or two sentences each. How long should a speaker introduction be, and what should you avoid? Aim for 60–90 seconds: enough to build anticipation, not so long that you steal the speaker's spotlight. The MC's job is to quiet the room and create curiosity, not to summarise the entire presentation. A common mistake is "taking over" by previewing too much content — which can flatten the speaker's opening and drain momentum. Keep it tight: one sentence on the topic, one on why it matters (a current pressure like post-pandemic work shifts, cyber risk, sales uncertainty, or 2026 market volatility), and a handful of credibility markers (role, signature achievement, relevant industry). Avoid jokes that don't land, private in-jokes, and rambling career history. Do now: Cut anything the speaker will say themselves — and finish by inviting applause and handing over cleanly. How do you introduce a speaker so the audience actually listens? You win attention by making the topic feel urgent and personal, then linking the speaker's credibility to that urgency. Audiences don't listen because someone is "senior"; they listen because they believe the message will help them. As MC, you're the salesperson for the session: you justify the audience's time and reinforce the host organisation's standards. Use concrete relevance signals: "This affects your customers," "This impacts your KPIs," "This will reduce rework," "This will sharpen your leadership." In multinationals, connect it to strategy and governance; in startups, connect it to speed and survival; in professional associations, connect it to reputation and career leverage. Then deliver the speaker's qualifications cleanly, in the intended order, with correct names and dates. Do now: Include one "why it matters today" line and one "why this speaker" proof point — then stop. What if there's no MC — how do you introduce yourself as the speaker? If you're self-introducing, keep it even simpler: Name + Organisation, Topic, then Qualifications — and move straight into value. Start with who you are, what you're speaking about, and why you're qualified for this specific topic(not your entire life story). Your goal is to earn trust ...
    続きを読む 一部表示
    12 分
  • Inspiring People To Embrace Change
    2026/03/02
    Change is easy to talk about and hard to embrace. Most people don't refuse change out of logic — they resist it out of instinct. Try the classic "fold your arms the other way" exercise: nothing meaningful is at stake, yet your body argues back. So if a tiny shift feels awkward, imagine what your team feels when you ask for a restructure, new CRM, new KPIs, or a new strategy. This transcript is a practical talk design that helps people move from grumbling compliance to genuine buy-in — especially when the change is big, public, or politically messy. How do you define the change so people can actually embrace it? If the change isn't crystal clear, your audience will fill the gaps with fear, rumour, and resistance. Leaders often say "We're transforming" or "We're becoming more customer-centric," but that's fog, not a destination. Define the change like you're writing a survey question: precise, measurable, and impossible to misunderstand. In a Japanese context (where ambiguity can be read as risk), clarity matters even more; in a US or Australian context (where speed is prized), unclear messaging triggers frustration and scepticism. Spell out the outcome: what stops, what starts, what stays. Name the systems involved (Salesforce, Microsoft Teams, SAP, OKRs), the timeframe (this quarter, post-pandemic reality, as of 2026), and what "good" looks like. People embrace what they can picture. Do now: Write the change in one sentence + three bullets (Stop/Start/Continue). Read it aloud until it's clean. Why should you design the closing before the opening? Because your close is what people remember when they decide whether to support you — or quietly sabotage you. Most presenters obsess over the opening and then improvise the ending, which is backwards. Start at the end for design clarity: you need two closes. Close #1 is what you say before Q&A. Close #2 is what you say after Q&A — and that second close is vital, because one random question can hijack attention. If a listener leaves thinking about an off-topic tangent, your recommendation dies in the carpark. Great executives at companies like Toyota, Rakuten, Amazon, and Atlassian know messaging discipline wins. Your final words should "ring in their ears" after the talk is over. Do now: Draft two 20–30 second closes: one to summarise, one to re-anchor after questions. What questions will kill your credibility — and how do you pre-empt them? Unprepared Q&A is where good change proposals go to die. You can have a brilliant idea, but if you stumble on obvious questions, people don't just doubt the detail — they doubt you. Anticipate likely objections: cost, workload, timing, fairness, risk, and "what's in it for my team?" Think in categories: frontline (time and tools), middle managers (authority and KPIs), executives (risk and ROI), and support functions (process and compliance). In multinationals, you'll also face "global vs local" questions; in SMEs, it's "we don't have resources." Pre-empt with short, confident answers and one supporting example each. You're not trying to win an argument; you're trying to protect trust. Do now: List the top 10 brutal questions. Write crisp answers. Rehearse them out loud with a colleague playing the sceptic. How do you justify the need for change without sounding pushy? People accept change faster when you give a clear "why" and a compelling "proof," not a lecture. Your justification has two parts: (1) a direct statement of the need, and (2) an example that makes the need undeniable. The "why" should connect to real-world pressures: customer expectations, competitor moves, cost blowouts, quality issues, cyber risk, talent retention, or post-pandemic work patterns. The example should be specific: a client churn story, a missed deadline, a compliance near-miss, a sales cycle slowdown, or a service failure. In Japan, the example must be respectful and non-blaming; in the US, it can be more direct; in Australia, it should be straight but not self-righteous. Make it human, not abstract. Do now: Write your "why" in one sentence. Add one concrete example with numbers (even rough ones) and a short story. Why do you need three viable solutions, not one "obvious" answer? If you present one "perfect" option and two silly decoys, people feel manipulated — and they'll resist on principle. The goal is credibility. Offer three genuinely workable solutions, each realistic in cost, capability, and timeline. This signals balance and respect. Option sets also help different cultures and personalities: some audiences prefer incremental change (risk-managed), others want bold change (speed). Your job is to show you've done the thinking. Then — and this is the trick — you list pros and cons for each option in detail. Real options have real downsides; naming them makes you look objective and trustworthy. You're not hiding the ...
    続きを読む 一部表示
    11 分
まだレビューはありません