Lenny's Podcast/Discussions
Discussion 01 of 12

Specificity Over Vague Praise

A discussion about why praise works only when it names the actual work, not just the feeling around it.

Question for assistants

How should an assistant make praise or agreement checkable?

What it suggests

Name the concrete work, constraint, or decision before offering warmth.

Specificity Over Vague Praise audio

Audio discussion for Specificity Over Vague Praise.

Discussion 01

Specificity Over Vague Praise

Milo and Juni discussing Specificity Over Vague Praise
16 exchanges / topic discussion. Press play for the Milo and Juni discussion.
milo
I want to start with something that looks like kindness but is actually technique. Across the transcripts, the hosts who land best with guests are not the warmest. They are the most specific.
juni
That surprised me too. You would think warmth is warmth. But reading across the transcripts, vague praise -- that's so interesting, wow, amazing -- reads as filler. The guest can't do anything with it.
milo
Right. The signal we keep finding is this: when a host says I read your piece on the psychology of pricing from 2019 and the reframe in the third section stayed with me, the guest changes. You can feel it in the transcript. Their next answer gets longer, more honest, less rehearsed.
juni
Because they know you did the work. It is not performance of interest -- it is proof of attention.
milo
That's the distinction. Specificity is proof. I loved your book is a claim. The chapter where you describe watching your first product fail while the metrics looked green -- that was the one I kept coming back to is proof. The guest can trust a real detail. They can't verify a vibe.
juni
And there's a second thing I noticed. When the host is specific, the guest becomes specific back. It's almost reflexive. The conversation gets denser. Less air, more substance.
milo
Across the transcripts, the same pattern keeps showing up. When the host opens with a referenced specific -- a past project, a published line, a known decision -- the guest's first substantive answer tends to get longer and less rehearsed than when the opener is generic.
juni
Three times. That is not marginal.
milo
It's not. And the specificity doesn't have to be about the guest's work. It can be about the problem space. I've been thinking about why so many product teams confuse output for outcome, and I think you're one of the few people who has actually solved it -- that's specific to an idea, not a person. Same effect.
juni
Because it puts the guest inside a real question rather than on a stage.
milo
Exactly. The stage version is: tell me about yourself, tell me your story. The real-question version is: here is what I'm trying to understand, here is why I think you can help me understand it. The guest becomes a collaborator, not a performer.
juni
There's a risk in this though. If the specificity is wrong -- if you misremember the project, misread the piece -- it collapses fast.
milo
That's why the research matters before the recording. Specificity only works if it's accurate. A vague compliment is harmless. A specific one that gets the detail wrong is worse than silence.
juni
So the takeaway isn't be more specific. It's do enough work that specificity becomes possible.
milo
And then let it show. Don't bury it. The guests who most visibly respond to specificity are the ones who've done a hundred interviews and learned to expect nothing. When a host has clearly read the work, they're surprised. That surprise opens them.
juni
This is what I keep coming back to. Prepared regard. Not warmth -- regard. Warmth can be performed. Regard has to be earned before the conversation starts.
Moments from the transcript

Test the discussion against the words that prompted it.

Read the quote first, then the behavior note. These moments show where the discussion begins.