Keynote: Why are you making a new platform?
summary
Claim: huge centralized platforms mostly serve buyers and IT layers, not end users, and they routinely fail. Examples: national health IT projects cost ~10 billion in Norway/UK and ~50 billion in the US and produce protests and unusable systems. Tools mentioned: Kafka, REST, GraphQL, Office365/Slack, Epic and SAP integrations. Recommendation: build a small working product first, evolve it, and prefer a collection of opt‑in toolkit components over a monolith; empirical failures show that large designed‑from‑scratch platforms don’t work.
AI-written summary · about
chapters (12)
- 0:00Platform obsession intro
- 1:29True purpose of platforms
- 4:59Who benefits from platforms
- 10:12Cost of misaligned incentives
- 17:11Success and empathy
- 22:09Platforms vs user needs
- 27:47Platforms as toolkits
- 34:28Billions wasted on platforms
- 40:27Platform trap and user focus
- 47:28Team autonomy beats bloat
- 57:17Cloud migration reconsidered
- 1:00:25User-centric call to action
related talks
20mKeynote: Software Delivery and Developer Experience in the Age of Platform E...
23mPlatform Engineering for Architects - Crafting Platforms as a Product
58mPlatforms: Build abstractions, not illusions
23mBeyond the Buzz Building Developer Platforms That Drive Business Success
34mPlatforms: Defying the laws of IT physics
24mSignificance of Platforms in Product Development
33mWhy You Should Treat Your Platform as a Product
46mPlatforms: Build abstractions, not illusions