How to design your team for scale
summary
Divides scaling into traffic, team, and territory and gives concrete fixes: use autoscaling, elastic DBs and offline workers for traffic; enforce tests, code review, a three‑month bootcamp and split services for team growth; and address GDPR, data residency and payment changes when expanding territories. Shares hard numbers and outcomes: systems moved from 200M to 20B events/day, a test suite bloated builds from 10 to 30 minutes, a MongoDB counter caused weekly failures, and an internal Cooper chatbot plus an automation index measurably reduced manual work.
AI-written summary · about
chapters (9)
- 0:00Introduction and purpose
- 3:14Why DevOps matters
- 9:19Three types of scaling
- 11:45Team scaling challenges
- 15:00Territory scaling challenges
- 17:27Analyzing scale needs
- 20:38Planning and execution
- 21:03Scaling at Lemonade
- 23:51Conclusion and Q&A
related talks
26mScaling engineering organizations
31mScaling Tech Organizations
16mEnlarge your team!
28mFrom Startup to Scale Up: How to Scale Engineering teams
31m5 Things I Wish I'd Known Sooner About Scaling Teams
50mScaling for Global Growth with Modern Cloud
28mMaking do: Scaling expertise on teams you can't grow
31mScaling