Read the original at Lenny’s Newsletter ↗lennysnewsletter.com · subscriber post
By Lenny Rachitsky · lennysnewsletter.com · @lennysan on X · YouTube · LinkedIn
An interview-based deep dive into how Ramp's product org works, centered on a culture of velocity: planning only as far out as needed, anchoring strategy to the financial model, organizing teams around business outcomes, keeping teams small, and hiring high-slope, high-agency individual contributors. The core argument is that speed and ownership are a competitive advantage.
Subscriber post — summary only01Key takeaways
- Planning should be lightweight and timeboxed, since doing beats planning when direction is aligned.
- Anchor product strategy to the company's financial model so trade-offs between growth, margin, and monetization are explicit.
- Organize teams around big business outcomes with small, autonomous, single-threaded pods.
- Keep PM, design, engineering, and data reporting to the same leader so product stays a co-founder rather than a stakeholder.
- Have PMs find and close their first customers themselves, and hire high-slope individual contributors over managers.
“Any second you spend planning is a second you don’t spend doing.”Geoff Charles · Lenny’s Newsletter
“Speed is a competitive advantage.”Geoff Charles · Lenny’s Newsletter
02Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.