Avoiding MVPs for Complex Designs

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

Topic 5 of 10

Published Jun 4, 2023 · Clip 18:06–22:27 (4:20)

Jeremy prefers avoiding MVPs at Rippling to prevent suboptimal architecture; instead, design for complex cases first (e.g., 10k global users) even if simplified initially, saving long-term rework. MVPs optimize speed over deep thinking, risking wrong technical foundations. Example: Global payroll launched for six diverse countries, creating extensible platform (80% shared, 20% configurable) vs. replicating per-country, easing future additions.