Platform-as-a-product from the trenches
summary
Gartner prediction of 80% by 2026 and Accelerate’s finding of an 8% decrease in throughput frame a cautionary case for internal platforms. Real projects include a multi‑year insurance cloud migration that missed milestones while untangling 15 years of on‑prem config, a crypto‑bank platform scoped to deliver virtual cards that succeeded by focusing on a narrow customer value, and a finance org using Centaso’s Cratics where a team self‑hosted the golden‑path to get S3 buckets faster. Key failures: wrong scope, building pipelines no one uses, and weak business alignment.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 5:44Why platform as a product matters now
- 7:50What is a platform and why use one
- 12:48Platform engineering origins
- 17:21Hype cycle and pitfalls
- 19:26Platform as a product solution
- 24:20Challenges of platform PM
- 27:10Defining platform value
- 34:08Usability for platform PMs
- 41:52Feasibility is not your job
- 42:56Business viability for platforms
- 46:24Key takeaways
- 47:08Q&A
related talks
40mPlatform Wars: The Battle Between Golden Paths and Spaghetti Pipelines
37mPlatform as a Product for modern IT needs
24mSignificance of Platforms in Product Development
27mTurning Platform Engineering Work Into Business Value Leadership Understands
33mWhy You Should Treat Your Platform as a Product
44mPlatform Engineering is All About Product
20mPlatform-First Cloud Transformation
43mEngineering Platforms Evolved