Platform teams: Applying Lean practices to reduce their Operational workload
summary
Platform teams discover they spend roughly 70% of capacity on operational work (alerts, restarts, vendor and business support) leaving ~30% for roadmap work, and cut that load by applying Lean: build a value stream map, instrument pipelines in Grafana to show per-step failure rates and durations (DORA-like end-to-end metrics), track every channel (chat, desk visits, alerts) with tags, run monthly DMAIC cycles, run FMEA/Pareto to target the 20% causes that create 80% of incidents, and use Backstage as a self-service surface.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker intro
- 3:06Platform teams' operational workload problem
- 11:43Lean methodology fundamentals
- 17:07Mapping value streams in platforms
- 20:16Continuous improvement cycle DMAIC
- 27:36Root cause analysis techniques
- 31:10Why invest in reducing operational workload
- 34:06Summary and key takeaways
- 34:49Q&A session
related talks
30mHow DevOps is Enabling Lean Application Development
37mDevOps, 12 Factor and Platform Engineering
01h 04mDevOps Kaizen: Empowering Teams to find and fix their own Problems
44mEnhancing the Performance of Engineering Teams
22mThe challenges of Platform teams
27mHow platform teams create resilient organisations
22mLeading software teams with context (visibility)
43mEngineering Platforms Evolved