One does not simply... rebuild a product
summary
Culture Amp is rebuilding its second‑largest product (performance) from scratch to reach a $3b market, after thousands of customers and 850–1,500 review cycles per month exposed an outdated domain model and tangled monoliths. The team pivots from Hanami to Rails, ships a first slice: self‑reflections, and enforces a for‑like principle with a new design system. Results show LCP improvements, frontend deploys drop to under 10 minutes and backend to under 5 minutes, the slice ships successfully, and the rebuild allows rapid innovation (AI features next).
AI-written summary · about
chapters (8)
- 0:00Product rebuild journey
- 3:34Need for full rebuild
- 7:48Stakeholder buy-in
- 11:57First slice execution
- 17:32Success metrics beyond customers
- 19:37Scaling remaining domains
- 22:24Rolling out rebuilt product
- 24:28When to rebuild
related talks
38mOne does not simply... rebuild a product
51mMicroservices and Microfrontends: Scaling, Learning, Growing
42mHow Rails fosters a diverse and competitive tech ecosystem in the era of big tech
21mTaming Monoliths Without Microservices
13mSpeed at Scale: Optimizing The Largest CX Platform Out There
32mHot Swapping Our Rails Front End In Secret - A Rebrand Story
51mCompleting the Rewrite from Hell: Five Years of Technical Debt and How We Escaped
28mBreaking Rules to Ship Products: A Beginner's Rails Journey