Platform Engineering for Architects - Crafting Platforms as a Product
Talkat Platform Engineering Day 2025 - Europe · on Tuesday, 2025-04-01· at 15:55· Level 1 | Hall Entrance N10 | Room F·
summary
Internal Developer Platforms fail because teams build infrastructure projects not products; adoption, not tech, is the failure mode. The talk claims many orgs start infrastructure-first, extend cognitive load, and neglect user research and feedback loops; it cites developers spending ~40% of time coding and says only about one third of teams set timelines/budgets. Concrete practices: run user interviews, measure door/space metrics, set deprecation criteria, favor a thinest viable platform, and treat Backstage/GitOps as tools not the platform itself.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:47Internal platform failures
- 3:56Infrastructure pitfalls
- 5:41Extending left and cognitive load
- 7:10Shared platform journey
- 8:37Business value alignment
- 10:24Data-driven design
- 11:52Challenging Conway's law
- 13:19Cultural shift and iteration
- 14:45User research and feedback
- 16:30Technical debt criteria
- 17:55Beyond technology
- 19:41Enabling efficiency and developer experience
- 21:06Feedback and evolution
- 22:10Product mindset
- 22:31Q&A
related talks
47mPlatform Engineering is Domain-Driven Design
48mSome Principles From Real World Internal Developer Platform Engineering
34mPlatforms: Defying the laws of IT physics
01mPlatform Engineering is Domain Driven Design
32mPlatform Engineering for Software Developers and Architects (Redux)
29mLeading With The Platform: A Platform Engineering Approach To Tech Debt
46mPlatforms: Build abstractions, not illusions
48mPlatform Engineering is Domain Driven Design