Opening Panel
summary
Conversation lays out concrete playbook: treat platform as platform as a product, curate off‑the‑shelf (EKS, GitHub Actions, Terraform, HashiCorp Vault) and build only unique, reusable services, aim for ~80% coverage, avoid forced mandates, and expect adoption to climb from MVP to 50% then 90% in successful cases. Start with a low‑maturity pilot team, focus on fleet management/day‑two operations, invest in product/design skills, and ship an MVP in 4–8 weeks to learn. Documentation, discoverability and ADRs decide success.
AI-written summary · about
chapters (16)
- 0:00Event introduction
- 1:48Panelist introductions
- 3:54Audience experience levels
- 5:37Starting platform journey
- 7:22Developer questions
- 10:11Building through failure
- 13:47Platform as product
- 16:57Team size feasibility
- 18:22First customer team
- 22:16Build vs buy components
- 24:24Platform patterns
- 28:57Industry similarities
- 31:44Cloud Foundry lessons
- 35:14Design patterns
- 37:41Fleet management
- 38:25Closing remarks
related talks
33mWhy You Should Treat Your Platform as a Product
50mWhy is it so Hard to Create a Great Platform-as-a-product?
43mEverything You Need, Nothing You Don't: How Do You Actually Build a Lean Platform
40mInternal platforms in practice
43mEngineering Platforms Evolved
31mPanel Discussion: Platform and Developer Productivity - Trends and Challenges
32mHow Might You Platform: Avoiding Traps Before It's Too Late
46mWork It Smarter, Dev It Better, Ship It Faster, Test It Stronger