Hum Rhetoric

Rhetoric: The Art of Persuasion

Overview

Aristotle identified three modes of persuasion: Ethos (credibility), Pathos (emotion), and Logos (logic). Effective persuasion uses all three in proportion appropriate to the audience and context.

Framework

IRON LAW: All Three Appeals, Calibrated to Audience

Logos alone convinces analysts but bores executives. Pathos alone moves
hearts but lacks substance. Ethos alone relies on reputation that may
not exist.

Every persuasive communication must use all three, weighted by audience:
- Technical audience: Lead with Logos, support with Ethos
- Executive audience: Lead with Pathos (vision), support with Logos (data)
- Public audience: Lead with Ethos (trust), amplify with Pathos

The Three Appeals

Ethos (Credibility) — Why should they trust YOU?

• Expertise, credentials, track record, shared values
• Established early — if the audience doesn't trust you, nothing else matters
• Techniques: cite credentials, reference shared experience, acknowledge limitations honestly

Pathos (Emotion) — Why should they CARE?

• Stories, vivid language, shared values, urgency, aspiration, fear
• Creates motivation to act — logic alone rarely moves people
• Techniques: personal anecdotes, concrete examples, sensory language, rhetorical questions

Logos (Logic) — Why should they BELIEVE?

• Data, evidence, logical reasoning, structure
• Provides the rational justification for the emotional response
• Techniques: statistics, case studies, cause-and-effect, comparison, analogy

Rhetorical Devices

Analysis Steps (for evaluating rhetoric)

1. Identify the rhetorical situation: Speaker, audience, purpose, context 2. Map the appeals: Where does the text use Ethos, Pathos, Logos? 3. Identify devices: Which rhetorical techniques amplify the message? 4. Assess effectiveness: Does the appeal balance match the audience? Are the appeals authentic? 5. Note weaknesses: Where is the rhetoric thin, manipulative, or mismatched?

Output Format

# Rhetorical Analysis: {Text/Speech}

## Rhetorical Situation
- Speaker: ...
- Audience: ...
- Purpose: ...
- Context: ...

## Appeal Analysis
| Section | Appeal | Technique | Effectiveness |
|---------|--------|-----------|--------------|
| {quote/section} | Ethos/Pathos/Logos | {specific technique} | H/M/L |

## Overall Balance
- Ethos: {strong/weak} — {evidence}
- Pathos: {strong/weak} — {evidence}
- Logos: {strong/weak} — {evidence}

## Verdict
{Overall effectiveness and recommendations for improvement}

Examples

Correct Application

Scenario: Analyzing a startup pitch

• Ethos (slide 2): "Our team has 15 years combined experience at Google and Meta" — establishes technical credibility ✓
• Pathos (slide 1): "Imagine waiting 3 weeks for a doctor's appointment while your child has a fever" — creates urgency through a relatable scenario ✓
• Logos (slide 5): "TAM of $4.2B growing at 18% CAGR (McKinsey, 2024)" — data-backed market opportunity ✓
• Balance: Well-calibrated for investor audience (Pathos hook → Ethos team → Logos market)

Incorrect Application

• A pitch deck with 20 slides of data and no story or emotional hook → All Logos, no Pathos. Investors decide emotionally first, then justify rationally. Violates Iron Law: all three appeals needed.

Gotchas

• Ethos is fragile: One dishonest claim destroys all credibility. Never overstate credentials or data.
• Pathos without Logos is manipulation: Pure emotional appeal without evidence is demagoguery. Always provide logical backing.
• Know your audience's Ethos threshold: In Taiwan, academic titles and institutional affiliations carry strong Ethos. In Silicon Valley, startup exits and portfolio companies matter more. Calibrate.
• Written vs spoken: Written rhetoric relies more on Logos (readers can re-read and verify). Spoken rhetoric relies more on Pathos and Ethos (listeners process in real-time).
• Counter-rhetoric: Understanding rhetoric helps you RESIST manipulation too. When someone appeals purely to emotion with no evidence, recognize it.

References

• For speech structure templates, see references/speech-structures.md

我直接建立檔案（不需要讀取，已有所有必要資訊）：

The file content is ready. Here it is — output only the markdown as requested:

---

Example: B2B SaaS Pitch to Traditional Manufacturer

Scenario

Jason Wu is CMO of CloudSync Taiwan（雲鏈科技）, a B2B SaaS platform for supply chain visibility. He has been pitching a three-year contract worth NT$18M to Longhua Precision（龍華精密）, a 40-year-old Taiwanese contract manufacturer with 800 employees and no prior SaaS adoption.

After two failed pitch meetings, Jason asks:

"I've delivered this deck six times. The data is solid — 23% inventory

reduction, 99.8% uptime, three Tier-1 reference clients. Why do they keep

saying 'we'll think about it'? How do I make this pitch actually land?"

He shares his current opening paragraph:

*"CloudSync is the leading supply chain visibility platform for mid-market

manufacturers in Taiwan. Our platform integrates with SAP and Oracle to

provide real-time inventory tracking. We serve 47 clients with an average

99.8% uptime SLA. Today I'd like to walk you through our ROI model."*

---

Analysis

Step 1 — Rhetorical Situation

---

Step 2 — Appeal Analysis of Current Opening

Diagnosis: The opening is all Logos with borrowed Ethos (industry jargon as proxy for credibility). It violates the Iron Law — zero Pathos. For a risk-averse traditional manufacturer burned by a past IT project, Pathos must come first to lower the defensive posture; Ethos must be earned through their reference points, not generic claims.

Appeal balance (current):

• Ethos: Weak — self-declared; no third-party validation; no shared experience
• Pathos: Absent — no story, no acknowledgment of their pain
• Logos: Over-weighted — ~80% of pitch is data the chairman cannot contextualize

---

Step 3 — Rhetorical Devices Audit

The current pitch uses no memorable devices. It reads like a spec sheet.

Missing opportunities:

• Rhetorical question — invite the audience into the problem before presenting the solution
• Analogy — abstract SaaS concepts need a concrete anchor for a 40-year manufacturer
• Specific detail as Ethos signal — naming "Taichung warehouse" instead of "your facilities" signals real research

---

Step 4 — Revised Opening

Calibration: Traditional executive audience in Taiwan → Lead with Pathos (shared pain), establish Ethos through peer references in their industry, deliver Logos as justification only after emotional buy-in.

*"Chairman Chen, in 2019 you implemented your current ERP system. I've spoken

with your operations team — the go-live ran eight months late and came in 40%

over budget. You were promised transformation and delivered a headache.*

>

*That story is not unusual. 67% of manufacturing IT projects in Taiwan run over

schedule (MIC, 2023). So when another vendor walks in with a big promise, I

understand why the answer is 'we'll think about it.'*

>

*I'm not here to give you another promise. I'm here because Formosa Plastics

used our platform for 14 months before they agreed to let us use their name —

they needed to be sure it worked first. Their procurement lead, David Lin, will

take your call this afternoon if you'd like to ask him directly.*

>

*What Formosa found: NT$23M in cash tied up in excess inventory they couldn't

see. Within six months they freed NT$8.4M of it. Chairman Chen — how much

inventory is sitting in your Taichung warehouse right now that you're not

certain you need?"*

---

Step 5 — Revised Opening Annotated

---

Result

Rhetorical Analysis: CloudSync Taiwan — Longhua Precision Pitch

Rhetorical Situation

• Speaker: Jason Wu, CMO — technical credibility, low relational capital with Longhua
• Audience: Risk-averse traditional manufacturer leadership; burned by prior IT project; relationship-driven decision culture
• Purpose: Close NT$18M contract; overcome persistent "we'll think about it" stall
• Context: Post-bad-ERP environment; vendor trust deficit; no prior SaaS adoption

Appeal Analysis

Overall Balance

• Ethos: Weak → Strong — shifted from self-declared to peer-verified, verifiable, specific
• Pathos: Absent → Strong — opens with acknowledged pain, closes with personalised question
• Logos: Over-weighted → Calibrated — data appears after emotional buy-in, grounded in named examples

Verdict

The original pitch failed because it assumed data persuades before trust is established. For a traditional Taiwanese manufacturer carrying recent IT trauma, the persuasion sequence must be:

Acknowledge pain → Earn trust through honesty and peer proof → Deliver data in a named-company frame → Close with a question that makes the problem personal.

No new facts were invented in the revision — only the rhetorical sequence changed. The same 23% inventory reduction and 99.8% uptime numbers appear later in the deck where the audience is now ready to receive them.

One remaining risk: Ethos is fragile. If the Formosa Plastics reference call doesn't happen, or goes badly, the entire credibility structure collapses. Never use a reference you haven't fully briefed and confirmed in advance.

Speech Structures

Five proven templates for structuring persuasive speeches and written arguments. Each template is matched to a specific rhetorical context, with the appeals (Ethos/Pathos/Logos) explicitly mapped to each section.

---

Template 1: Classic Aristotelian (General Persuasion)

Best for: formal speeches, proposals, academic arguments where the audience expects structured reasoning.

1. Exordium     — Hook + Ethos establishment
2. Narratio     — Context / background (Logos framing)
3. Propositio   — Thesis statement (what you're arguing)
4. Confirmatio  — Evidence for your position (Logos dominant)
5. Refutatio    — Acknowledge and rebut counterarguments (Ethos: fairness)
6. Peroratio    — Emotional close + call to action (Pathos dominant)

Why the order matters: Ethos must come before Logos. If the audience doesn't trust you by section 4, your evidence won't land. Refutatio before Peroratio is critical — addressing objections while you still have their analytical attention; trying to rebut after an emotional close feels defensive.

Worked example — pitch to a city council for a new cycling infrastructure budget:

---

Template 2: Monroe's Motivated Sequence (Call to Action)

Best for: sales presentations, fundraising asks, any speech where the explicit goal is to get the audience to DO something.

Developed by Alan Monroe at Purdue in the 1930s; widely used in persuasive speech training.

1. Attention    — Disrupt the audience's passive state (Pathos)
2. Need         — Establish a problem that must be solved (Logos + Pathos)
3. Satisfaction — Present your solution (Logos + Ethos)
4. Visualization — Paint the future state with/without your solution (Pathos)
5. Action       — Specific, concrete ask (clear call-to-action)

Critical distinction from Aristotelian: Monroe adds Visualization explicitly. Most speakers skip straight from solution to ask — this leaves the audience intellectually convinced but not emotionally ready to act. Visualization bridges that gap.

Worked example — internal pitch to adopt a new project management tool:

---

Template 3: Problem-Agitate-Solution (PAS)

Best for: short-form persuasion — emails, memos, one-page proposals, social media threads. Works in 3 paragraphs.

Problem     — Name the problem the audience already feels (Pathos recognition)
Agitate     — Deepen the pain: consequences, scale, urgency (Pathos + Logos)
Solution    — Your answer, with evidence (Logos + Ethos)

PAS is the minimum viable persuasion structure. If a message can't be reduced to these three moves, it isn't clear enough.

Worked example — email asking management to approve remote work policy:

Problem: Our current policy requires all staff to be in-office 5 days a week, but half our team commutes 90+ minutes each way.

>

Agitate: We've lost 3 senior engineers in 6 months — exit interviews cited commute as the primary factor. Replacing each costs approximately NT$800,000 in recruiting and onboarding. At current attrition rates, we're on track to spend NT$2.4M this year on preventable turnover.

>

Solution: I'm proposing a 3/2 hybrid model (3 in-office, 2 remote). Companies with similar profiles — including our direct competitor Appier — have used this model since 2022. I've drafted an implementation plan that maintains our collaboration norms. Happy to walk you through it this week.

What Agitate is doing: most writers go directly from Problem to Solution, which feels like a pitch. Agitate makes the problem visceral and urgent before you offer relief. The audience must feel the problem is worth solving before they care about your solution.

---

Template 4: The Sandwich (Diplomatic Feedback / Difficult Asks)

Best for: performance reviews, critiques, negotiation openings, any situation where the audience is likely to be defensive.

Positive     — Genuine acknowledgment of what is working (Ethos: good faith)
Core ask     — The challenge, critique, or request (Logos)
Forward path — Collaborative next step, not a demand (Pathos: shared future)

Warning: The Sandwich is widely misused as a manipulation technique where the positives are hollow filler. Audiences recognize this instantly and it destroys Ethos. The positive frame must be genuine. If you can't find something real to affirm, lead with shared context instead.

Worked example — telling a colleague their analysis has a critical flaw:

Positive: "The competitive landscape section is the strongest I've seen from anyone on the team — really sharp segmentation work."

>

Core ask: "The revenue projection on page 7 uses last year's FX rate. At current rates, the NPV drops by about 15%, which likely changes our recommendation. That needs to be corrected before we present to the board."

>

Forward path: "If you can update the model today, I can re-review by end of day and we can still hit tomorrow's deadline together."

---

Template 5: The Pyramid (Executive Communication)

Best for: briefings to senior executives, board presentations, situations where the audience may stop you at any moment and you need your conclusion first.

Developed by Barbara Minto (McKinsey) as the "Minto Pyramid Principle."

Conclusion    — State the answer/recommendation immediately (no buildup)
  Key point 1 — First supporting argument
    Evidence A
    Evidence B
  Key point 2 — Second supporting argument
    Evidence C
    Evidence D
  Key point 3 — Third supporting argument
    Evidence E

This inverts the Aristotelian structure deliberately. Executives operate under time pressure and high information density. They need to know if they agree with your conclusion before they'll invest attention in your evidence. If you bury the recommendation at the end, you've lost them.

Structure rule: Maximum 3 key points at any level. If you have 4, merge two or cut one.

Worked example — briefing the CEO on a vendor negotiation:

Conclusion: "I recommend we switch our cloud provider from AWS to GCP at renewal in Q3. Expected savings: NT$3.2M annually."

>

Key point 1 — Cost: "Our current AWS bill is NT$8.1M/year. GCP's committed use pricing brings equivalent workloads to NT$4.9M. We've modeled this against our actual usage for the past 12 months."

>

Key point 2 — Migration risk is manageable: "We already run 30% of workloads on GCP via our data pipeline. The remaining migration is estimated at 6 engineer-weeks — one-time cost of NT$600K, ROI in under 3 months."

>

Key point 3 — Strategic fit: "GCP's AI/ML tooling aligns with our roadmap. AWS has no equivalent to Vertex AI at our scale and budget."

What to do if the executive disagrees with the conclusion: Don't restructure to build-up. Instead, ask which key point they're skeptical of and go deeper on that branch. The pyramid makes it easy to navigate to the disputed sub-argument.

---

Choosing a Template: Decision Table

---

Mapping Templates to the Iron Law

Every template above uses all three appeals — they differ only in ordering and weighting:

No template suspends the Iron Law. Even the Pyramid — which appears all-Logos — relies on Ethos (the speaker's credibility that makes the conclusion worth hearing) and Pathos (the implied vision of what success looks like). If you find yourself writing a section with only one appeal, that section needs revision.

---

Common Structural Mistakes

Mistake 1: No explicit Refutatio Skipping counterarguments makes you look like you haven't considered them. Audiences generate objections mentally while listening; if you don't address them, those objections dominate their attention. Include at least one "Some might argue... however..." moment in any speech over 5 minutes.

Mistake 2: Call to action buried or vague "We hope you'll consider supporting this initiative" is not a call to action. Every persuasive communication ends with a specific, actionable ask: "Vote yes on resolution 14B today" / "Reply to this email with your approval by Friday" / "Sign up at the link in the chat."

Mistake 3: Visualization skipped in Monroe The jump from Satisfaction → Action leaves audiences intellectually convinced but emotionally flat. Visualization takes 60 seconds and dramatically increases follow-through. Never skip it.

Mistake 4: Using Pyramid for emotional audiences Leading with the conclusion requires the audience to trust you enough to hear it without context. If the audience is hostile, grieving, defensive, or in crisis, Aristotelian or Sandwich is safer — they need the relational groundwork before they can process your recommendation.

Mistake 5: PAS Agitate section using only one type of pain Effective Agitate stacks pain types: financial cost + emotional cost + opportunity cost. Using only data feels cold; using only emotion feels alarmist. A 2-3 sentence Agitate typically hits one Logos element (scale/cost) and one Pathos element (human consequence).