Why is it so Hard to Create a Great Platform-as-a-product?
summary
Argues that a platform must be treated with product thinking and shows concrete remedies: build self‑service managed Kubernetes with Vault and Argo CD for secrets and deployments, offer one‑click deployment paths and RFC roadmaps, measure impact (platform users deploy ~10x faster), embed enablement teams for feedback, avoid making the platform mandatory or a mono‑platform, and staff teams with product management plus mixed infrastructure and developer skills to prevent the cost‑center and false‑consensus traps.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:42Agenda
- 1:09What is platform engineering?
- 10:47What is so significant about this concept?
- 15:47Stumbling blocks to watch out for
- 44:02Good user centric platform-as-a-product characteristics
- 48:56Conclusion
- 49:39Outro
related talks
33mWhy You Should Treat Your Platform as a Product
39mOpening Panel
12mUnveiling the Future: Navigating Cloud Strategy, Platform Engineering, and Architectural Evolution
32mHow Might You Platform: Avoiding Traps Before It's Too Late
32mFrom Kubernetes to PaaS to … Err, What’s Next?
25mWho Built This Platform? Alternative Viewpoints on Platform Design - Diana Todea & Elif Samedin
46mPlatforms: Build abstractions, not illusions
44mIs Platform Engineering a hype? Let's build a platform together!