By Lenny Rachitsky · lennysnewsletter.com · @lennysan on X · YouTube · LinkedIn
Lenny Rachitsky's early newsletter answers three reader questions: how to motivate engineers to hit arbitrary deadlines, where to find real PM career ladders, and how to get executives to accept more actionable customer metrics. His core argument is that missed deadlines usually have explainable causes, so PMs should first listen and diagnose before pushing harder. He then offers practical levers for motivation, such as aligning incentives, buy-in, and sprint-sized estimates. For the exec-alignment problem he recommends grounding ideas in evidence, working backward from the ideal product, and tying work to a shared KPI. The advice is practical and grounded in common PM friction, which makes it useful for PMs managing delivery and stakeholders.
01Key takeaways
- Investigate why delivery is slow by asking engineers and comparing with other teams before assuming a motivation problem.
- Be upfront that a deadline is arbitrary when it is, and use hard and soft deadlines deliberately.
- Let teams set their own estimates, then lock in the plan and share it widely.
- Tie shipping to performance reviews, promotions, autonomy, and public recognition so incentives reinforce deadlines.
- When execs say an idea is not actionable, ask what would make it so, then back claims with data and user conversations.
- Agree on the target metric with execs first, then rank ideas by how much they move it.
02Key sections
- Diagnosing slow delivery
- Before blaming the team, ask engineers why work takes as long as it does and compare with other teams. Run blameless post-mortems to build a feedback loop.
- Using deadlines well
- Be transparent that deadlines may be arbitrary, but recognize they coordinate cross-functional work and create accountability. Distinguish hard deadlines from soft ones.
- Motivating the team
- Connect daily work to individual goals and the company mission, partner with managers, secure real buy-in on estimates, and align incentives, passions, and skills.
- Career ladders
- Lenny points to public PM career frameworks from companies such as Intercom, Oscar, Gusto, XO Group, and GitLab as useful references.
- Winning over executives
- When execs reject metrics as not actionable, gather evidence, treat feedback as useful input, design the ideal experience first, and test with real users tied to a shared KPI.
03From the post
“Hello and welcome to my humble newsletter, where I answer your questions and offer candid advice about building product, driving growth, working with other humans, and anything else that’s stressing you out at the office. I’ll tackle three reader questions each week (keeping your name and company anonymous) until you quit sending me questions. I definitely won’t have all of the answers, and it’s just my one perspective, but hey, it’s free! 🤝 If you’re returning from last week, thank you! If you’re new, nice to have you! Help spread the word by telling your friends to sign up here. 😎 New this week: Let’s experiment with comments 🤷♂️ If you have any of your own suggestions to share, on any of the topics we cover below, open up the newsletter in a browser, scroll to the bottom, and post a comment. 🤙 On to this week’s questions… [](https://substackcdn.com/image/fetch/$s!scV8!,fauto,qauto:good,flprogressive:steep/https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2Fb77fdc5c-b4db-43fb-ba63-dc5d80fe50c1220x145.gif) Q: The biggest question I'm dealing with is how to motivate my eng team to hit deadlines that aren't necessarily connected to anything specific. It feels like they've been dragging their…”
04Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.