Moving fast and navigating uncertainty | Jeremy Henrickson (Rippling, Coinbase)

Brought to you by Miro—A collaborative visual platform where your best work comes to life | Mixpanel—Product analytics that everyone can trust, use, and afford | Lenny’s Job Board—Hire the best product people. Find the best product gigs—Jeremy Henrickson is Rippling’s SVP of Product, responsible for scaling their product and design team across three continents. Previously, as Chief Product Officer at Coinbase, he oversaw 10x growth of the product and engineering organization and transformed a scrappy startup into a global cryptocurrency platform with tens of millions of users. He began his career at Apple in the 1990s and holds a BS and MS in computer science from Stanford. In today’s episode, we discuss:• Strategies for sustaining focus and momentum at scale• The case against MVPs• The problem with frameworks• “Compound startups” and how this influences Rippling’s product development process• Advice for founders wanting to move faster• Why you don’t understand your product unless you’re “in the weeds”• Hiring practices at Rippling and how young PMs can build fruitful careers—Find the transcript at: https://www.lennysnewsletter.com/p/moving-fast-and-navigating-uncertainty—Where to find Jeremy Henrickson:• Twitter: https://twitter.com/jeremyhenricks• LinkedIn: https://www.linkedin.com/in/jeremyhenrickson/—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• Twitter: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Jeremy’s background(03:24) What it was like leading product teams at Coinbase during the crypto boom(05:25) How Jeremy kept teams focused and the biggest challenges he faced at Coinbase(07:35) Advice for going through intense periods at work(08:52) Maintaining velocity at scale(12:07) An example of small teams with clear missions(14:29) A model for building products(18:03) Jeremy’s thoughts on MVPs (minimum viable products)(22:26) Designing for the most complex use case firs