Lenny’s Newsletter · Subscriber post · Execution, roadmaps & process · Metrics, data & experimentation

Setting goals

If you find this newsletter valuable, consider sharing it with friends

Lenny RachitskyApr 28, 20207 min♥ 33
SourceLenny’s Newsletter
KindSubscriber post
PublishedApr 28, 2020
Readers♥ 33
Originallennysnewsletter.com ↗
N:

Lenny Rachitsky lays out a framework for setting team and company goals, placing goals between strategy and roadmap as the way to measure whether strategy is working. He covers the traits of a good goal, how to pick a metric through a growth model and bottleneck, how to set an ambitious but reachable threshold, and how to operationalize goals once set.

Subscriber post — summary only

01Key takeaways

  • Goals sit between strategy and roadmap; they show whether the strategy is actually being executed.
  • Make sure the whole team shares one picture of success, since people often imagine different goals.
  • A good goal is simple, concrete, worthwhile, stable, and gives quick feedback.
  • Find the growth model's biggest bottleneck, then choose a concrete metric that tracks it.
  • Set thresholds using both top-down needs and bottom-up capacity, aiming for uncomfortable but not impossible.
“A product leader's job is to unwrap the burrito and make sure everyone is seeing the same thing.”Lenny Rachitsky · Lenny’s Newsletter
“goals should feel "uncomfortable, but not impossible.”Brian Chesky · Lenny’s Newsletter

02Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.