Continuous Deprovement will eat your product for breakfast
summary
Growth eats engineering unless lead times are measured and governed: the claim is that rapid headcount and product proliferation produces slow, siloed delivery unless teams track change lead time and cycle time. Practical fixes shown are value‑stream metrics, limiting batch size, use of feature toggles (only ~12% reported doing this) and an internal currency to surface platform vs product value. Audience polls split roughly 50/50 on knowing fix times, exposing the coordination problem.
AI-written summary · about
chapters (10)
- 0:00Start
- 7:58THE START-UP
- 14:17THE ENTERPRISE DILEMMA
- 15:48THE FIRST PRODUCT
- 22:23THE INVENTORY
- 35:28THE TIME KPI'S
- 38:54THE HUMANS
- 40:26ONE DASHBOARD
- 42:01PLATFORMS ARE PRODUCTS
- 45:16KEY TAKEAWAYS
related talks
22mOptimizing Product Development: Balancing Speed, Quality, and Process
52mBeyond Features
30mDelivering Features VS Delivering Impact
15mOptimizing the engineering value stream
29mEconomies of Speed
51mThe astonishing value of speed
31mEngineering Effectiveness: Achieving your goals with less
30mTransforming to a Culture of Continuous Improvement