Keynote Engineering Success The Blueprint for Effective Platform Adoption
summary
Claims a concrete five-point blueprint: treat the platform as a product, secure clear stakeholder funding and billing, structure teams per Team Topologies, build rapid automated feedback and analytics, and actively incentivize adoption. Shows concrete failures and metrics: a VM that used to take two weeks then later six weeks because of governance and arrived without internet so the POC fails. Mentions Kubernetes, Terraform, CNCF platform white paper, self-service onboarding and measurable usage over NPS.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 2:50What Platform Engineering does
- 3:33Platform Engineering as a strategic business enabler
- 5:05Platform Engineering as a Launchpad
- 7:35Key Takeaways
related talks
19mKeynote Talk: Platform as a Product: Are We Nearly There Yet
29mKeynote: Building Bridges with Platforms: The Role of the Platform Engineer
35mPanel: Navigating the Path to Platform Engineering...
27mConveying the Importance of Platform as a Product in the Cloud Native Ecosystem
01h 02mKeynote: The Socio-technical Elements that Make Good Platforms
43mPlatform as a Product: Mindset, milestones, metrics
29mNon-Technical Challenges of Platform Engineering
27mThe Future of Platform Engineering