Platform as a Product - Transforming from Service Delivery into Continuous Operations
summary
Ops groups shift from ticket-based service delivery to product-managed platforms that prioritize developer productivity: eliminate developer toil (automation and self-service), enforce compliance via one centralized platform, and involve developers through 90-day POC cycles tied to real apps. Case studies include Discover Financial Services, Rabobank, and the US Air Force. Start small with several pilot apps, then scale — teams typically ramp to material usage in ~1 year — and run quarterly internal events to teach, market and iterate on platform features.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:13Platform as a Product
- 2:48How are things different this time
- 6:05Im always unhealthy
- 7:36Operations in DevOps
- 9:06Roles in DevOps
- 11:31Product Management
- 13:50Application in Operations
- 15:55Key Areas of Focus
- 16:56Waiting for resources
- 17:52Developer problems
- 19:18Finding toil
- 21:05Standardization
- 21:34Involve Developers
- 23:09Advantages of a Platform
- 25:40Starting Small
- 28:00Quarterly Events
related talks
30mPlatform as a Product
43mPlatform as a Product: Mindset, milestones, metrics
26mLessons Learned from 7 years of Running Developer Platforms
38mHow to Empower your DevOps Initiatives with a PlatformOps Approach
42mPlatform Engineering in practice — Why and How to start
41mPlatform as a Product
37mPlatform as a Product for modern IT needs
33mThe Platform Engineering Journey