The subtle art of supporting mature products
summary
A company discovers the standard rotation causes 900 engineer days of unaccounted work in a year and shifts from six‑week Shape Up experiments to a dedicated, central support team that keeps primary/secondary rotation, builds runbooks and dashboards, and automates repetitive recoveries. The team uses logs, metrics, tracing and deployment pipelines, enforces rollbacks and team objectives, reduces incident rates over the following year, and turns recurring tickets into product fixes and proactive reliability work.
AI-written summary · about
chapters (12)
- 0:00Supporting mature products
- 4:59Success in support growth
- 10:41Support responsibilities and goals
- 13:30Support rotation methods
- 17:21Breaking knowledge silos
- 21:43Rapid team restructuring
- 24:57PowerP girls support team
- 26:20Team objectives for support
- 29:12Moderation in support practices
- 33:53Support progress and goals
- 37:44Support orchestra as you grow
- 40:15Support as legacy-building art
related talks
51mThe subtle art of supporting mature products
25mWhat I Learned
23mMake Your and Other People's Life Easier: Do Support!
47mBumpy 12 Months Road to Transform Team of Mercenaries Into Product Minded Team
32mTransitioning from developing software to developing people
51mTaking Care of Business - for 10 000 hours
33mBuilding Sustainable Teams to Handle Uncertainty
43mMaking support the backbone of your business