Platform as a Product
summary
Argues that operations must adopt a platform-as-a-product mindset, building a Kubernetes platform with containerized runtimes, service mesh and middleware plus an automated build pipeline so teams can achieve weekly deployments. Recommends starting with one or two business-facing pilot projects, embedding platform engineers as consultants, seeding trained people into new teams, and running quarterly internal conferences. Cites real adopters (Discover, Rabobank, US Air Force, Home Depot, Comcast) and measures success by adoption and outcome metrics not just SLAs.
AI-written summary · about
chapters (5)
- 0:00Start
- 12:12Ops' roles and responsibilities are about developer productivity, platform creation
- 19:51Start small & steady, expand by seeding & winning trust
- 24:21Consulting, internal marketing, branding, etc.
- 27:41Use metrics to track value delivered, not (just) status
related talks
43mPlatform as a Product: Mindset, milestones, metrics
44mPlatform Engineering is All About Product
19mKeynote Talk: Platform as a Product: Are We Nearly There Yet
33mPlatform as a Product - Transforming from Service Delivery into Continuous Operations
27mConveying the Importance of Platform as a Product in the Cloud Native Ecosystem
26mLessons Learned from 7 years of Running Developer Platforms
35mPanel: Navigating the Path to Platform Engineering...
35mWhat the heck is Platform-as-a-Product? - How product thinking drives your platform maturity