Vertically Integrated in Platform Engineering
summary
Argues platform engineering should act like a vertically integrated product company that actually builds a developer platform (not the end application), tracks capacity and interrupt-driven work, and uses DORA metrics plus NPS and utilization graphs to make cases. Shows how to translate outcomes into dollars — using an example of $1,000 per minute of downtime, estimating 1,000 prevented minutes → ~$1M saved versus a ~$100k project cost to claim a ~$900k ROI — and uses a road-mapped cutline to prioritize funding.
AI-written summary · about
chapters (9)
- 0:00Introduction and Audience Engagement
- 1:00Common Challenges in DevOps and SRE
- 1:39Understanding Vertical Integration
- 3:55Who Are You Building For?
- 4:28Navigating Customer and User Dynamics
- 8:18Tools for Effective Communication
- 10:24Data-Driven Decision Making
- 12:48Speaking the Language of Business
- 16:07Conclusion and Final Thoughts
related talks
27mTurning Platform Engineering Work Into Business Value Leadership Understands
43mEngineering Platforms Evolved
44mPlatform Engineering is All About Product
31mNavigating the Platform Revolution: From Bottom-Up Innovation To Product Thinking
29mKeynote: Building Bridges with Platforms: The Role of the Platform Engineer
33mMeasuring the Impact of Platform Engineering
33mBeyond developer productivity: what's next?
22mDevOps vs Platform Engineering: Navigating the Path Ahead