Turning Platform Engineering Work Into Business Value Leadership Understands
summary
Shows exact framing and numbers used to win funding: adopt a lightweight centralized platform in six weeks with two engineers to reduce churn from 10% to under 5% by cut release time from two days to one day, citing a 50% release-time cut tied to faster feature delivery. Uses CNCF platform and maturity models and mentions tools like Argo. Reframes capabilities as risk offsets—target 99.95% uptime with multi-region clusters, notes $100k HA build vs $1M/hour downtime and $3M/year infra with $500k/yr savings potential.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 1:14Defining platform engineering
- 3:38The investment dilemma
- 5:56Cloud-native maturity model
- 8:10Business case for churn
- 12:33Reliability and risk
- 16:47Financial modernization
- 20:23Platform as a product
- 24:37Conclusion and takeaways
related talks
17mVertically Integrated in Platform Engineering
43mEngineering Platforms Evolved
25mFrom Ops to Impact: Scaling Engineering Velocity
29mKeynote: Building Bridges with Platforms: The Role of the Platform Engineer
33mWhy You Should Treat Your Platform as a Product
43mPlatform as a Product: Mindset, milestones, metrics
37mPlatform Engineering's Inferno
29mSuccessful Cloud Native Platform Engineering – Hype vs Reality