Scaling
summary
Scaled an engineering org from 2 to 20 and another from ~20 to 40–50 in 2.5 years, and the hard lessons are concrete: prioritize product–market fit over hiring velocity, expect process to trail headcount, and stop repeat work caused by Conway's Law. Operational fixes include formal post-incident postmortem + five whys, dedicated on‑call and onboarding rotations, adopting team topologies, and keeping a 30% technical‑debt floor so growth doesn’t force a multi‑month rewrite. External partners like Lohika accelerate safely if treated as long‑term collaborators.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:54Dave Burgess
- 1:10Derrick Knudsen
- 13:06Scaling Culture
- 26:33What Lessons Have You Learned in Terms of Scaling via External Engineering Partners
