Skip to content

By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.

Tim FerrissTim Ferriss

How to say no | The Tim Ferriss Show (Podcast)

This is a special episode of the podcast. When I wrote Tribe of Mentors, I reached out to many different experts, leaders, athletes, and entrepreneurs who are the best in the world at what they do.

Tim Ferrisshost
Dec 14, 201727mWatch on YouTube

Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.

Great conversations run long. Their best ideas don't have to.

uListen is free on iPhone, iPad, Android, Chrome, and Claude.

See how

CHAPTERS

Chapter summaries

  1. Tim’s direct ask: launching Tribe of Mentors and why to check it out

    Tim Ferriss opens with a rare direct request to support his newly released book, Tribe of Mentors. He frames it as an easy-to-read, “choose-your-own-adventure” collection of short advice from many high performers and notes that he puts out a large volume of free content.

    • •Tim announces the release of Tribe of Mentors: Short Life Advice from the Best in the World
    • •He describes the book as broadly useful across business and personal life, with something “for everybody”
    • •He emphasizes the scale of contributors and variety of disciplines covered
    • •He asks listeners to support the book as an occasional paid offering alongside his free podcast and blog content
    • •He points listeners to tribementors.com and general booksellers
  2. Show bumper and sponsor block: ConvertKit and Audible offers

    A brief show bumper leads into sponsor messages. Tim explains why he uses ConvertKit for email and then shares an Audible deal along with a few audiobook picks.

    • •A short show intro bumper precedes advertising
    • •Tim describes ConvertKit as his chosen email service provider and highlights deliverability, automation, and integrations
    • •He mentions a free first month offer via a specific link
    • •Tim describes how Audible fits into his routine and what he likes about audiobooks
    • •He gives an introductory pricing deal and explains how to redeem it via URL or text message
  3. Why this episode exists: rejection, saying no, and needing real phrases

    Tim sets the topic as rejecting requests—specifically, how to say no in a way that protects time and attention. He contrasts broad heuristics (like “hell yes or no”) with the practical need for specific wording people can use in real-life declines.

    • •Tim frames the core challenge as separating “noise” from “signal” and avoiding over-commitment
    • •He cites the “hell yes or no” heuristic as one way people decide quickly
    • •He argues that decision rules aren’t enough without concrete language to decline requests
    • •He explains that while writing Tribe of Mentors, many people declined his invitation
    • •He introduces the idea of reading standout rejection letters as practical templates
  4. How the ‘rejection letters’ feature came about (and why personality matters)

    Tim explains that some decline emails were so well-crafted he asked permission to publish them in the book. He emphasizes that saying no doesn’t require being cold or impersonal and can still reflect the sender’s personality.

    • •Tim says some declines were “expertly crafted,” prompting him to request permission to reprint them
    • •He positions these examples as tools listeners can adapt into reusable ‘set language’
    • •He highlights that a thoughtful ‘no’ can still sound human and personal
    • •He introduces the first example contributor, illustrator and graphic journalist Wendy MacNaughton
    • •He notes his recurring interview question about what people have become better at saying no to
  5. Example #1: Wendy MacNaughton’s thoughtful ‘I gotta pass’ email

    Tim reads Wendy MacNaughton’s decline, which explains her need to step back after an intense stretch of output and promotion. The email models a clear no while conveying respect, gratitude, and personal authenticity.

    • •Wendy describes stepping back after years of heavy creative output, promotion, and interviews
    • •She explains canceling contracts and saying no to new projects to create space to explore and rest
    • •She explicitly communicates appreciation and respect while still declining
    • •She acknowledges the professional cost of saying no, but prioritizes her current needs
    • •She expresses hope to connect later and suggests other people who could fill the gap
  6. Example #2: Danny Meyer’s brief decline that still lands warmly

    Tim introduces restaurateur Danny Meyer and reads a concise email decline sent through a mutual connection. The message is short, clear, and appreciative, using gratitude and confidence in the project to soften the refusal.

    • •Tim explains the request was routed through a friend acting as a go-between
    • •Danny cites current time constraints and other commitments, including his own writing projects
    • •He signals deliberation with “I thought carefully about this” before declining
    • •He declines “with gratitude,” keeping tone positive while making the answer unambiguous
    • •He closes by expressing confidence the book will succeed
  7. Example #3: Neal Stephenson’s ‘blanket policy’ and the Hydra to-do list

    Tim introduces Neal Stephenson and reads his decline, which explains an experiment to avoid adding anything to an already expanding to-do list. Neal frames the refusal as a blanket policy, making it clearly not personal while wishing the project well.

    • •Neal apologizes for a slow response and thanks Tim for considering him
    • •He describes trying to stop adding to his to-do list because it keeps growing—“like fighting a Hydra”
    • •He says being ‘ruthlessly efficient’ requires turning down requests like this as a blanket policy
    • •The policy framing communicates it’s not about the requester, but about constraints and rules
    • •He ends with encouragement and good luck for the project
  8. What these great ‘no’s have in common—and why your default may need to be no

    Tim extracts common patterns from the declines and explains how he applies similar language in his own rejections. He argues that even well-crafted no’s aren’t a panacea, but they can increase clarity and preserve respect over time.

    • •Tim says that with even modest success, the default answer to most requests should often be no
    • •He highlights explaining the predicament/context briefly as a key ingredient
    • •He emphasizes using ‘policy’ language (blanket/across-the-board) to make refusals non-personal
    • •He notes the goal is a clear no—not a vague ‘maybe later’ that keeps hope alive
    • •He closes by acknowledging you can’t control others’ reactions, then wraps up the episode and transitions toward the book plug and outro sponsor reads

Get more out of YouTube videos.

Read along on your phone, search it beside the video, or ask your favorite AI app what was said.