Economies of Speed
summary
Argues that speed plus discipline reduces risk and improves quality citing 2,600x frequency gaps between high and low performers and high performers spending 44% more time on new features. Recommends shrinking cycles toward daily releasability using deployment pipelines, trunk‑based and test‑driven development. Gives concrete proofs: SpaceX uploads software 40 minutes before launch, Tesla changed max charge from 200 to 250 kW with a software change and production line update within three hours. Cites a 4,000‑project study where teams of five produce fewer defects and nearly the same throughput as larger teams.
AI-written summary · about
chapters (12)
- 0:00Intro
- 4:20Efficiency
- 7:01The nature of the problem
- 10:03Best way to reduce gaps
- 11:08What does your Org. think of "IT"?
- 16:55How do we achieve "Economies of Speed"?
- 21:43Technical performance
- 22:15Cultural performance
- 24:34Organizational performance
- 25:37How to move fast
- 27:06What does "Going Fast" mean?
- 28:39Outro
related talks
51mThe astonishing value of speed
23mThe Cost of Speed: Rethinking "Move Fast" in DevOps
45mThe astonishing value of speed
45m"Moving Fast at Scale"
42mSpeeding Up Innovation
45mAccelerating Software Delivery: Why Your Team Is Slowing Down
59mSlowdown to Grain Speed: Technical practices that take time but save time.
01h 21mTradeoffs in the Software Workflow