Jeremy Henrickson on Velocity at Scale, the Compound Startup Model, and Why MVPs Can Be Harmful

Jeremy Henrickson is Senior Vice President of Product at Rippling, where he leads product and design teams across a portfolio of interconnected HR, payroll, and IT products. Previously Chief Product Officer at Coinbase during its 40× growth period in 2017, he argues that the most important product decisions are structural — platform investment, team design, and the instinct to design for complexity rather than simplicity first.

Key ideas

• Design for the most complex use case first. MVPs are useful when product–market fit is genuinely unknown. For a compound startup building on a shared platform, optimising for the simple case embeds architectural assumptions that are almost impossible to unwind. Design the system that handles the hardest cases; then decide which cases to support in V1.
• The compound startup model. Rippling is many businesses — payroll, benefits, IT, device management, time and attendance — sharing one system of record. The activation energy to build this was enormous, but the payoff is that each new product inherits infrastructure no competitor can replicate: a single source of truth for every employee attribute, always current.
• Small teams with clear missions preserve velocity. As organisations scale, horizontal communication becomes the primary drag on speed. The antidote is small groups with narrowly defined missions, insulated from everything except the platform interfaces they depend on. Rippling repeatedly launches new product lines with four to six people.
• “Go and see.” Henrickson’s leadership principle: product leaders must descend all the way to ground on the hardest problems in their domain. Understanding global payroll means reading tax law, not just reading summaries from a compliance team. That depth is what allows authoritative, fast decisions.
• Product leaders are right a lot. Rippling explicitly hires for this. The product decisions PMs make multiply across entire engineering organisations. The rare skill is the ability to look at an ambiguous situation with incomplete information and call the right direction — and to be right most of the time.

Topics covered

• Coinbase’s 40× growth in 2017 and what it taught about focus under pressure
• Small teams with clear missions: how Rippling launches new product lines
• Platform investment as velocity multiplier
• Anti-MVP argument: designing for the most complex use case first
• Rippling’s global payroll as a case study in architectural foresight
• Compound startup model: many businesses, one system of record
• “Go and see” as a leadership principle
• Quarterly planning and the culture of moving on
• What Rippling looks for in product managers: insightful questions, right-a-lot instinct
• “Imperatives” system: cross-cutting priorities for the entire product org
• Working with a strongly opinionated product founder

See also

• Deep notes — Adler frame, glossary, claims by section
• Compound Startup Model — the episode’s novel concept
• Compounding — platform capability that compounds over time
• Jeremy Henrickson — speaker
• 7 Powers — the system-of-record decision as a durable moat
• Jeff Weinstein — adjacent long-term-structure lens