Read the original at Lenny’s Newsletter ↗lennysnewsletter.com · subscriber post
By Lenny Rachitsky · lennysnewsletter.com · @lennysan on X · YouTube · LinkedIn
Lenny Rachitsky offers a three-step process for a product person to say no to a manager while keeping their trust: listen and ask questions, form an independent point of view, then respond constructively using one of five response paths. The core argument is that saying no is part of the job, and it should be done with curiosity, evidence, and clear next steps.
Subscriber post — summary only01Key takeaways
- Saying no is a core part of a PM's job in creating focus and stability for the team.
- Start by listening and asking several probing questions before reacting to a manager's idea.
- Form your own independent view by weighing downside, upside, timing, and strategic fit.
- Choose from five response paths: yes with trade-offs, yes but not now, no with an alternative, no but explore further, or a clear no with reasons.
- When rejecting an idea, lead with unbiased facts and evidence rather than opinions.
“Originality is fragile. And, in its first moments, it's often far from pretty.”Ed Catmull · Lenny’s Newsletter
“Dig as far as you can, in the time you have, both to understand where your manager is coming from and to make sure they…”Lenny Rachitsky · Lenny’s Newsletter
02Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.