ROI Of Platform Engineering
summary
Claims a new ROI method that grades platform capabilities by quality and attaches price tags to golden path templates, so business can fund incremental value. Uses examples: migrating three apps to Kubernetes stalls for 12 months, leaving zero ROI while teams chase perfection. Recommends building right-to-left from developer needs, treating platforms as products, leveraging promise theory and a taxonomy to quantify autonomy vs. cost, and proposes a working group to produce a practical qualitative ROI framework.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:06Platform product owners
- 2:35Calculating platform ROI
- 4:22Culture impacts ROI
- 6:13Developer experience design
- 9:00Silos versus collaboration
- 10:26Building platforms right to left
- 13:49Measuring platform adoption
- 16:46Quantifying engineering decisions
- 19:51Autonomy versus ROI
- 21:21Call to action
related talks
27mTurning Platform Engineering Work Into Business Value Leadership Understands
43mEngineering Platforms Evolved
33mWhy You Should Treat Your Platform as a Product
23mPutting a Price Tag on Open Source ROI in Enterprise Japan
40mInternal platforms in practice
33mBeyond developer productivity: what's next?
01h 17mRefactoring the ROI of Software
27mWhy Developer Platforms and a curated Dev Experience are a must have when scaling