Platforms MUST Be Small, Regardless of Their Size
summary
Claims that platforms must be small no matter company size and that most enterprise platforms have become monoliths through tool sprawl. Evidence: examples of dozens of tools and automation paths, Conway’s-law-driven growth, and the shift to a platform of platforms architecture. Practical fixes: carve out multiple platform teams, deliver a thinnest viable platform (TVP) as a minimal API/docs/toolset, measure adoption, open inner-source, and treat each subplatform as a product so teams can adopt without changing workflows.
AI-written summary · about
chapters (7)
- 0:00intro
- 0:14defining platforms
- 3:15the disruptive nature of platforms
- 5:14challenges with current platforms
- 8:07breaking down the monolithic platform
- 10:40strategies for platform improvement
- 12:06conclusion and call to connect
related talks
38mPlatform Engineering in the Age of AI Teammates
31mThe Evolution to Platform Engineering 2.0
18mBeyond Bits and Bytes: The Strategic Role of Digital Platform Leaders
44mBeyond Metrics: Orchestrating Developer Delight with AI driven Platform Engineering
21mImproving your Developer Experience Through Platforms and Generative AI
46mWhen Software Becomes Everyone's Job
05mThe Evolving Role of Platform Teams in the AI Era
31mClosing panel: The future of platform engineering and what to build next