Prioritising comfy seats but not the engine - Things product owners need to know...
summary
Dyson moves from a round 360i through a 360 Heurist to a new D-shaped vacuum, discovering major technical debt where code and assumptions expect a circular chassis; rebuilding some subsystems and refactoring others lets navigation and corner-cleaning work within weeks after months of low-level rebuild. Continuous delivery with weekly internal releases, heavy automated tests, logs → Elasticsearch/Splunk, metrics → CloudWatch/Prometheus/Grafana, simulated 3D home trials and Tableau dashboards drive fast learning across 20 teams in four countries. Built-for-change, not just features.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:41Andrews background
- 2:06Technical debt
- 5:25Spotting technical debt
- 6:51Paying off technical debt
- 9:48Problems with rebuilding
- 13:40Software architecture
- 18:18What does continuous delivery mean
- 21:35Building new capabilities
- 23:28Testability and observability
- 26:54Embedded metrics
- 28:22Team topologies
- 29:15Team responsibilities
- 30:37Wrapping up
- 32:55Questions
related talks
47mBumpy 12 Months Road to Transform Team of Mercenaries Into Product Minded Team
45mFrom 5 to 100 in Product Development team in just 5 years
31mHow Great Tech Teams Build a Productivity Culture that Scales
11mDesign team of one
21mNeed for speed - Moving fast as a software engineer
56mSmarter, Not Harder: Scaling without burning out in an always more landscape
42mThe subtle art of supporting mature products
48mHow to Build and Maintain Engineering Teams Focused on Product through Culture and Values