Lenny's PodcastMoving fast and navigating uncertainty | Jeremy Henrickson (Rippling, Coinbase)
CHAPTERS
- 0:00 – 0:32
Go deep as a leader: learning in the trenches
Jeremy opens with a core leadership habit: resisting the urge to “float” above the work and instead joining teams where problems are hardest. He explains why firsthand exposure reveals real constraints, tradeoffs, and opportunities that dashboards and updates can’t.
- •Leaders learn fastest by working alongside teams on the hardest problems
- •Being close to implementation surfaces true bottlenecks and risks
- •Deep dives create better context for prioritization and decision-making
- 0:32 – 3:46
Jeremy’s path and what this episode will cover (velocity, decisions, expertise)
Lenny introduces Jeremy’s background—SVP Product at Rippling, formerly CPO at Coinbase—and frames the episode around moving fast in uncertain environments. The preview emphasizes scaling velocity, fast decision-making culture, and the importance of deep domain expertise.
- •Jeremy scaled product/engineering orgs through hypergrowth at Coinbase
- •Episode themes: velocity at scale, decision speed, domain mastery
- •Also teased: MVP skepticism, complex-use-case-first design, hiring PMs
- 3:46 – 5:25
Coinbase during the 2017 crypto boom: 40x growth and constant breakpoints
Jeremy recounts what it felt like to run product through Coinbase’s massive 2017 demand surge. The growth was exhilarating but operationally punishing, with reliability and incident response becoming a recurring weekend reality.
- •Coinbase saw ~40x usage growth over 2017
- •Hypergrowth creates “dream and nightmare” dynamics simultaneously
- •Systems break at the edges; incident response becomes routine
- •Trustworthy teammates are essential under sustained pressure
- 5:25 – 7:32
Staying focused amid chaos: security first and aligning on a point of view
Lenny asks how Jeremy kept teams focused while everything was changing. Jeremy describes security as the non-negotiable constraint and explains how leaders must emerge from debates with a clear company stance—even when uncertainty remains.
- •Reframe “people getting rich” into customer trust and safeguarding money
- •Security is the top priority and shapes what “moving fast” can mean
- •Balance immediate firefighting with a 6-month directional plan
- •Create clarity: debate hard, then align and execute at full speed
- 7:32 – 8:52
Surviving intense work periods: learning rate as the silver lining
Jeremy reflects on the personal strain of extreme work intensity (including having a newborn at home). He shares a mindset for enduring these periods: stepping back to see the accelerated learning and long-term meaning that often comes from the “crucible.”
- •Intensity is hard—especially with major life events at home
- •High-pressure periods often accelerate growth the most
- •Use reflection and friends to contextualize the experience
- •The takeaway later is usually: we built something meaningful and learned a lot
- 8:52 – 12:10
Maintaining velocity at scale: small teams, platforms, deep dives, and right staffing mix
Jeremy lays out a practical playbook for staying fast as organizations grow. He emphasizes small teams with clear missions, investing in platform interfaces to reduce decision complexity, leaders going deep, and continually adjusting team seniority/skills to match the product phase.
- •Optimize for small teams with clear missions; minimize horizontal comms
- •Platform investment reduces repeated decision-making and accelerates shipping
- •Leaders must periodically dive deep on the hardest areas
- •Rebalance teams as work shifts from 0→1 to scaling (fit, interest, capability)
- 12:10 – 14:29
Rippling’s “small founding team” pattern: time & attendance as a case study
Jeremy describes Rippling’s repeatable approach to spinning up new products: start with a tiny, highly focused team and iterate fast with direct leadership access. The time & attendance product illustrates how four people built quickly by staying monomaniacally focused and integrating only where necessary.
- •Time & attendance started with ~4 people focused on a single mission
- •CEO involvement helps, but the key is focus and a replicable pattern
- •Teams integrate with the suite intentionally, not by default
- •Direct exposure to senior leadership increases feedback tempo
- 14:29 – 18:03
A model for launching new products: entrepreneurial lead + designer + fast build cycle
Jeremy details Rippling’s product incubation model: identify the need, assign an entrepreneurial “founder-type” engineer, pair with a designer, and recruit a small 0→1 team. New leaders first absorb platform and cultural patterns, then build to internal dogfooding or launch within ~6–9 months and scale as needed.
- •New product starts with a one-page definition and an entrepreneurial lead
- •Leads first learn the platform by embedding on existing teams
- •Pair with an experienced designer familiar with Rippling’s components
- •Typical path: blank slate → dogfood/launch in ~6–9 months; team scales based on needs
- 18:03 – 20:39
Why Jeremy isn’t a big MVP fan here: design for the hardest case to avoid rewrites
Jeremy explains why “minimum viable product” can be counterproductive at Rippling: optimizing too hard for speed can constrain creativity and lock in fragile technical assumptions. Instead, teams should model the most complex use case early so architecture can grow without painful unwinding later.
- •MVPs can limit differentiated thinking when the market is already validated
- •Simplistic early assumptions create compounding architectural constraints
- •Design for the hardest/most complex case first, even if not shipped initially
- •Slightly slower upfront work often saves significant time later
- 20:39 – 23:17
Global payroll example: building a platform that makes adding countries easier
A concrete illustration of complex-first design: Rippling’s global payroll. Rather than cloning U.S. payroll country-by-country, the team launched with multiple very different countries to force a generalized architecture, keeping most of the system common and making local differences configurable by non-engineers.
- •Avoid “copy US payroll and tweak” as the default approach
- •Launch with multiple diverse countries to force a generalized system
- •Aim for ~80% shared platform + ~20% country-specific layers
- •Push configuration to compliance/legal workflows instead of engineering changes
- 23:17 – 27:09
Compound startup strategy: one system of record enabling cross-product differentiation
Jeremy defines Rippling’s “compound startup” idea: many large standalone businesses unified on one platform. The single system of record eliminates duplicated data and unlocks capabilities (permissions, workflows, reporting) that are difficult or impossible when products are stitched together via integrations.
- •Rippling combines multiple verticals (payroll, benefits, IT, time, etc.)
- •Core differentiator: one system of record (single source of truth)
- •Enables platform primitives like permissioning, analytics, workflows
- •High activation energy upfront yields compounding advantages for new products
- 27:09 – 40:31
Culture of speed: fast decisions, firm deadlines, and “go and see” domain mastery
Jeremy describes Rippling’s distinctive operating tempo: decisions happen immediately when possible, not “next week.” He ties speed to leadership modeling, tight planning timelines, expectations that PMs become world experts in their domains, and the “go and see” principle—walking all the way to ground to understand reality.
- •Decision-making happens in the moment; pull in needed people via Slack calls
- •Deadlines are real—if you miss the date, the org moves on
- •PMs are expected to be foremost experts in their domain to answer quickly
- •“Go and see” means leaders personally verify details at the source
- 40:31 – 45:32
Global expansion strategy: picking markets, starting earlier, and respecting local reality
Jeremy explains how Rippling prioritized countries using customer demand signals, build difficulty, strategic value, and risk/lead times—then continually re-ranked as they learned. He argues companies should expand internationally earlier than they think because every country’s norms, expectations, and compliance details are uniquely demanding.
- •Assume global needs eventually; prioritize with real customer footprint data
- •Rank by demand, build complexity, strategic value, and approval lead times
- •Start international expansion earlier than feels comfortable
- •Localization and cultural credibility details can make or break trust
- 45:32 – 1:02:16
Frameworks vs deep thinking, plus hiring and developing PMs (case studies, questions, humility)
Jeremy clarifies he’s not anti-framework—he’s against process replacing thinking. He then shifts into how Rippling evaluates PMs: complex case studies to test agility, strong signals from candidate questions, and advice for junior PMs centered on humility, curiosity, and updating beliefs—especially when working with an opinionated founder.
- •Use “just enough process” to enable decisions; avoid process-as-substitute for thinking
- •Framework choice should match team context and lifecycle; unify mainly planning and tooling hygiene
- •Hiring signals: mental agility during complex case study; quality of candidate questions
- •Career advice: humility, curiosity, and willingness to change your mind; success with strong-opinion founders requires adaptability and respectful challenge
- 1:02:16 – 1:08:31
Lightning round and wrap: books, media, favorite products, and “imperatives” for focus
In the lightning round, Jeremy shares book and entertainment recommendations, products he’s enjoyed, and a tactical change at Rippling: “imperatives,” a short list of cross-org priorities that create clarity by defining what matters—and what doesn’t. The episode closes with where to find Jeremy and Rippling hiring notes.
- •Recommendations: Neal Stephenson’s Baroque Cycle; Iain Banks’ Culture series
- •Favorite show/movie mentions: The Last of Us; Tenet
- •“Imperatives” create focus across product/engineering by force-ranking shared priorities
- •Closing: LinkedIn contact and Rippling careers for entrepreneurial senior PMs
