Psychology of Customer Success

The episode delivers several concrete frameworks (the consultative sequence, six whys of advice, question types) with clear reasoning tied to cognitive biases. However, significant portions are devoted to lengthy analogies (chess/chili, dinner ordering, barber examples) and conversational tangents that pad runtime without adding new insights. The core ideas are solid but could have been communicated more densely.

“the consultative sequence is this diagnosed before you prescribe, discover before you deliver”

“People don't argue with their own data. So as much as possible, they need to come to their own conclusions.”

The core advice - asking questions, building trust, helping before selling - is not novel and circulates widely in B2B advice (7 Habits, consultative selling canon). The cognitive bias framing (confirmation bias, affinity bias, Dunning-Kruger) is standard pop psychology. The contribution is organizing these ideas around a specific sequence and linking them to CS contexts, but the underlying thinking lacks true originality.

“helping sells, selling doesn't help”

“Build a relationship, find the need, meet the need. If you do enough of those two, you don't have to have the best solution”

Dan Smaida has 20+ years in sales coaching and consulting, which is relevant to the CS audience, and his book shows structured thinking. However, he is primarily a sales consultant without visible deep expertise in customer success operations, retention mechanics, or the specific structural challenges CS leaders face (health scores, lagging KPIs, expansion quotas). He operates at a general 'influence and behavioral science' level rather than CS-specific depth.

“He has spent this entire century helping people use behavioral science to improve communication and increase influence. His clients range from financial services to 3D printing, edtech.”

“I do primarily work with sellers. A large amount of work with sales managers and leaders adjacent to the sales function, sales ops, sales enablement, customer success.”

The episode relies heavily on conceptual frameworks and general examples (the wedding intervention, barber anecdotes, Macy's Santa, dinner ordering) rather than concrete data, named case studies, or quantified results. One exception: Rachel mentions a control group experiment showing 30% churn vs. 7% for managed cohorts. But Dan provides no specific client examples, metrics, or detailed case studies to demonstrate impact in real CS or sales scenarios.

“I had people in my course actually do that and had the C-suite see that, oh, you know, that cohort is churning at 30% versus, you know, 7% of the managed customers.”

“Availability bias is really a strong thing as a story or an anecdote. Anecdotal evidence completely outweighs statistics way more than it should.”

Rachel asks good clarifying follow-ups ('how do we avoid that bias?' 'how do we figure out what questions to ask?') and pushes back productively on Dan's frameworks when they don't fit CS reality (e.g., the concern about calls that don't close on outcomes). However, she also spends considerable time validating Dan's points, allowing tangential discussions (dinner ordering, personal anecdotes), and doesn't challenge his claims rigorously. The conversation feels collaborative but lacks the edge needed to pressure-test his ideas against CS-specific friction.

“That's a really good one, because what we're not saying there is, don't offer advice. We're saying, set the stage for useful advice.”

“But I personally, this fundamentally, and I still have trouble doing it sometimes. And it's because I want to help and because I want to speed it up.”