By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.
Lenny's PodcastMoving fast and navigating uncertainty | Jeremy Henrickson (Rippling, Coinbase)
Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.
At a glance
WHAT IT’S REALLY ABOUT
Jeremy Henrickson on building fast, deep, globally scalable product organizations
- Jeremy Henrickson, SVP of Product at Rippling and former CPO at Coinbase, shares how he maintains product velocity in hyper-growth and high-uncertainty environments.
- He emphasizes small, founder-like product teams, deep domain immersion by product leaders, and a culture of extremely fast, high-quality decision-making.
- Henrickson argues against shallow MVPs in favor of designing for the most complex use cases first, especially when building on a shared platform or system of record.
- He also covers global expansion strategy, Rippling’s “compound startup” model, hiring and evaluating PMs, and how to effectively partner with a strongly opinionated, product-centric founder.
IDEAS WORTH REMEMBERING
5 ideasUse small, entrepreneurial teams with clear missions to preserve speed at scale.
Rippling repeatedly seeds new products with a ‘founder-type’ engineer plus a designer and a tiny team focused monomaniacally on one problem, enabling rapid learning, direct access to leadership, and minimized coordination overhead.
Design for the most complex use case first instead of a thin MVP.
Henrickson argues that optimizing for speed via simple MVPs often bakes in the wrong technical and product assumptions; instead, you should model for the hardest future scenarios (e.g., 10,000 global employees, multi-country payroll) even if you only ship simpler flows initially.
Invest in a real platform and single system of record to unlock compounding advantages.
Rippling’s core differentiation comes from one shared employee data store underlying many ‘vertical’ products, enabling capabilities like unified permissions, accurate reporting, and cross-product workflows that point solutions literally cannot match.
Cultivate a culture of very fast, high-quality decision-making.
Decisions are made “now,” not next week: leaders pull the right people into live conversations, operate on aggressive planning timelines, and actually move on if a team misses a decision deadline, which keeps organizational tempo high.
Product leaders must ‘go and see’ and become genuine domain experts.
Rather than delegating details to specialists, PMs are expected to deeply study tax codes, country regulations, or technical constraints themselves; that depth is what enables sound product judgment and scalable architectures.
WORDS WORTH SAVING
5 quotesYou have to go full speed toward one answer until you decide to go full speed toward a different answer.
— Jeremy Henrickson
A minimum viable product would do a disservice to both our customers and to the team building it.
— Jeremy Henrickson
We design for the most complex use case first, even if we don’t support it in version one.
— Jeremy Henrickson
No company I’ve been at, at any scale, has ever operated at the tempo this one does.
— Jeremy Henrickson (on Rippling)
What’s the point of writing a document if you don’t know what you’re talking about?
— Jeremy Henrickson
High quality AI-generated summary created from speaker-labeled transcript.
