Video summary

EP73 善於溝通的人，都是先從合理出發，而不是談道理。用多重合理性的視角，搞定難搞的客戶。 Feat. 許子謙Johs

Main summary

Key takeaways

Business

Business / Management Themes

  • Communication as “design”: Great marketing and great interpersonal communication both require a deliberate process—thinking about the audience’s psychology, constraints, and reactions before delivering messages.
  • Shift from “selling the product” to “selling identity/outcome”: Effective marketing reframes features into the person the customer becomes through using the product.
  • Coordination across layers: Real work (especially agencies) is mostly multi-layer coordination—client goals, internal teams, HQ/overseas, and end consumers—where communication failures compound.

Frameworks / Playbooks Mentioned

Multiple Valid Perspectives

  • Assumption: There’s no single absolute “right”; each side has rational motives based on their experiences.
  • Goal: Create a discussion space where parties can understand each other instead of attacking.

Five Whys (root-cause analysis)

  • Used to uncover why conflicts repeat.
  • Then translate “felt dissatisfaction” into specific comparators and decision criteria.

B = MAT

  • Original: Motivation (M) × Ability (A) × Trigger (T) → Behavior (B)
  • Reformulated by Johs: Behavior = (Motivation/Reason) × (Ability) × (Trigger/Context)
  • Key insight: If any one factor is near-zero, behavior won’t happen—small changes (e.g., clarifying what’s actually relevant) can “open the gate.”

Tactical Communication Pattern (praise-then-pointers + support)

  • Example tactic:
    • Spend most of the critique time praising first, then give pointers.
    • Offer a “warranty”/support channel for follow-up questions.

Key Examples / Case Studies (Actionable Takeaways)

1) Turning Conflict with a Client into Expansion (budget → 5x)

  • Situation: A difficult client kept pushing for revisions and was extremely particular/perfectionist.
  • Risk: A team member became overwhelmed (anger, threatened quitting), risking a relationship breakdown.

  • Approach used:

    • Step 1: Manage the person closest to you Understand emotions and what triggered them.

    • Step 2: Then address the client without blame Focus on understanding what “good enough” means to them.

    • Use Multiple Valid Perspectives Acknowledge both sides’ valid concerns (client wants quality; teammate needs a workable process).

    • Use Five Whys Identify the real underlying requirement: the client compared vendors on value (they had seen a vendor at ~70% of the current price).

  • Commercial solution (win-win negotiation):

    • Client pain: Difficulty justifying a higher price to their boss.
    • Provider constraint: Can’t discount freely (margin pressure).
    • Negotiation design:
      • Offer ~15% off (instead of a bigger cut) so the client can justify internally.
      • Repackage work requirements by priority:
        • Divide tasks into important / less important / minor nitpicks
        • Reduce pressure on the team for low-priority details.
      • Add a condition: the client must also give the “related project” to enable margin protection.

  • Outcome logic: Adjust incentives + scope + internal justification path → relationship preserved and business expanded.

2) “Made her cry” → Behavior Change + Leadership Lesson

  • Earlier work style: Blunt direct feedback (“this part needs changing… done… I’m busy”) led to emotional harm.
  • Aftermath: The colleague (star performer) resigned, later thrived elsewhere.
  • Reflection and change:
    • Later critiques used:
      • Praise first (8 min)
      • Pointers (2 min) for a ~10-minute critique
      • A 7-day “warranty” via email for follow-up
  • Leadership takeaway: Communication tone and perceived respect can determine retention and performance—even when the technical feedback is correct.

3) Marketing Insight: Ads vs Marketing, and Full-Screen “Annoyance”

  • People dislike ads; interruption triggers avoidance.
  • A “good ad” feels like:
    • “This is exactly what I want” (relevance beats interruption).
  • Implication: Design ad experiences based on user intent and relevance—not just persuasion.

4) Product Messaging Reframing (Body Wash / Soap / Perfume)

  • The product isn’t the “thing”; marketing sells:
    • the identity transformation and lifestyle outcome.
  • Examples:
    • Body wash / soap → relaxation, comfort, likelihood of sleep → “a calmer, healthier person.”
    • Fragrance → likability/personality signal → “social/romantic positioning.”

5) Threads / Algorithm Amplification as Persuasion Psychology

  • Negative/extreme takes get amplified by algorithms due to evolutionary neuroscience: humans are primed for danger/unusual threats.
  • Business takeaway (execution-focused): Platforms optimize for engagement drivers (emotion/novelty), so brand messaging must consider the risk of negativity loops.

6) B = MAT Example (Japanese restaurant on Threads)

  • Question: Would you go if it’s trending with good reviews?
  • People evaluate differently due to:
    • Motivation (e.g., wife doesn’t want raw food)
    • Ability (allergy/intolerance)
    • Trigger/context (e.g., only one dish out of ten changes the decision)
  • Practical implication: Tailor messaging to match audience barriers, not only present benefits.

Metrics / KPIs and Concrete Targets Mentioned

  • Negotiation / price:
    • Comparable vendor price: ~70% of current price
    • Proposed discount: ~15% off
    • Scope structured to reduce low-priority nitpicks
  • Support / retention mechanism:
    • 7-day email “warranty” after critique (support SLA-style concept)
  • Critique time allocation:
    • ~10-minute critique with ~8 minutes praise / ~2 minutes pointers

No revenue/CAC/LTV/churn targets were stated.

Actionable Recommendations (Distilled from the Talk)

  • Before communicating or persuading, run an “audience logic check”
    • What is motivating them? What ability do they have? What trigger/context will open them up to action? (B = MAT)
  • Use “priority-based scope” when negotiations get stuck
    • Split requests into important vs minor nitpicks; protect team workload and margin while still meeting the client’s definition of “quality.”
  • Debug conflict like a root-cause problem
    • Apply Five Whys when “they keep demanding changes”—often the real issue is internal justification or a hidden comparator.
  • Design communication tone as part of the process
    • Even correct critique can damage trust if delivered without psychological calibration; praise-first and follow-up support reduce defensiveness.
  • Market identities, not features
    • Convert product benefits into “the person the customer becomes,” making ads feel relevant rather than interruptive.

Presenters / Sources

  • Johs (許子謙) — primary guest and source of frameworks (Multiple Valid Perspectives, B=MAT, Five Whys usage).
  • Host / interviewer — referenced as “we” throughout; no name provided in the subtitles.

Original video