Are You Ready for Platform Adoption, or Are You Setting Yourself up for Failure?
Panelat Platform Engineering Day 2025 - Europe · on Tuesday, 2025-04-01· at 12:45· Level 1 | Hall Entrance N10 | Room F·
summary
Argues that confusing a portal with a platform dooms adoption and that an API-first platform (examples: Crossplane, Cratics) with onboardable, on‑demand APIs prevents recentralised ops bottlenecks; contrasts ready‑made tradeoffs (Verscell style convenience vs lost policy control) and time vs money costs; recommends cluster-level policy (ValidatingAdmissionPolicy, OPA), observability (Grafana, Data Dog, Honeycomb), testable docs, measurable business outcomes, iterative feedback loops, and a platform product owner to drive adoption and track whether the golden path actually works.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:03Platform vs portal confusion
- 2:07Centralizing ops without APIs
- 3:10Lack of business buy-in
- 4:13Developer sandwich alignment
- 4:35Ready-made solutions costs
- 6:41Solutions outgrowing needs
- 7:43Build vs buy costs
- 8:24Platforms as APIs
- 10:11Mission control policies
- 11:13Observability tools
- 12:16Documentation for adoption
- 13:19Four adoption mistakes
- 15:09Measuring adoption outcomes
- 15:50Platform enables business
- 16:34Building developer needs
- 17:18Feedback flaws
- 19:43Feedback collection methods
- 21:49Platform product owner role
- 24:38Product thinking beyond PO
- 25:21Platform iceberg work
- 27:09Platform empathy quiz
- 30:44Quiz results and advice
related talks
29mTales from the Platform Adoption Mines
30mPlatform as a Product
27mPlatform Adoption Strategies: Critical Roles When Investing...
40mPlatform Wars: The Battle Between Golden Paths and Spaghetti Pipelines
25mCommon platform team mistakes and how to avoid them
33mThe Platform Engineering Journey
34mPlatforms: Defying the laws of IT physics
27mThe Future of Platform Engineering