Beyond Engineering: The Future of Platforms
summary
Argument: adopt platform-as-product beyond engineering so teams treat internal services as customers and remove cross-division friction. Cites data mesh and a prototype blocked because a rigid legal as a platform wouldn’t allow a bespoke NDA. Gives measurable frictions: an invoice approval that takes five hours and several weeks, a CTO blocked by a €150 quarterly limit against a €500 need, platform teams rebuilding a pager, and organizational trust limits like Dunbar’s ~150. Proposes compliance as a platform with searchable regs, checklists and facilitation.
AI-written summary · about
chapters (11)
- 0:00Future of platforms
- 1:04Beyond engineering
- 4:55Frictions outside teams
- 13:38Defining platforms
- 17:32State of platform engineering
- 23:32What teams miss
- 31:36Treating users as customers
- 37:16Platform examples
- 41:49Evolving platforms
- 45:25Encouraging platform mindset
- 46:28Q&A
related talks
34mPlatforms: Defying the laws of IT physics
44mPlatform Engineering is All About Product
31mHow Companies Evolve By Building Platforms
33mThe Platform Engineering Journey
27mThe Future of Platform Engineering
29mKeynote: Building Bridges with Platforms: The Role of the Platform Engineer
32mPlatform Engineering Is Not About Tech
30mPlatform as a Product