Platforms: Defying the laws of IT physics
summary
Argues platforms must deliver guardrails plus low‑friction lane assist, not monolithic pyramids that try to anticipate every need. Recommends treating platforms as products (not consulting), actively commoditizing redundant layers, and using a simple 2x2 (value × fit) to avoid feature creep. Notes agents shift consumption patterns, raising cognitive load and making orchestration, compliance and platform cohesion the real bottlenecks; cites a 28‑year‑old architecture definition and human exhaustion after about 3–4 hours of intense pair‑work as concrete evidence.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:18Platforms are not pyramids of false assumptions
- 4:47Platform adoption failures
- 7:16Wrong benefits to customers
- 9:20Submarine effect in platforms
- 11:50Commoditizing platforms
- 13:19Infrastructure to product mindset
- 16:10Avoiding consulting trap
- 18:17Roadmap fit and business value
- 20:24Guardrails vs lane assist
- 22:47Platform adoption growth
- 24:36Architecture guidance to capabilities
- 26:00Platforms in AI age
- 29:49Reducing cognitive load
- 32:19Platforms as productivity amplifiers
related talks
51mThe Magic of Platforms
46mPlatforms: Build abstractions, not illusions
49mBeyond Engineering: The Future of Platforms
58mPlatforms: Build abstractions, not illusions
31mHow Companies Evolve By Building Platforms
29mPlatforms, Architecture and Sustainability
23mPlatform Engineering for Architects - Crafting Platforms as a Product
46mPlatforms: Build Abstractions, not Illusions