Getting the numbers for API-driven transformation to add up
summary
Argues that API spend often fails to show value because teams focus on tooling and vendor options while neglecting measurable benefits, with costs clustered in platforms and governance, training and people, project delivery and business enablement. Reports common surprises: higher operating costs, slower change, and funding squeeze. Successful programs treat engineers as customers and APIs as products, link API work to direct metrics (completion, onboarding time, revenue per API) and avoid the evaporating business case.
AI-written summary · about
chapters (6)
- 0:00API-driven transformation value
- 2:39API investments shortfalls
- 7:18Direct vs indirect API benefits
- 11:12Successful API programs themes
- 18:03Customer, product, process, team, culture
- 20:32Key takeaways for API success
related talks
27mGetting the numbers for API-driven transformation to add up.
01h 01mThe Business Value of a Good API
26mRevolutionizing Business with API-First Strategy: Key Insights
23mLeverage APIs to Transform Your Business Landscape
30m6 Reasons Why APIs are Reshaping your Business
26mAPIs are the new skin of your organisation
53mFor Want of a Nail: Industry Analyst Lessons Learned on the State of Software Dev...
28mDigital Transformation in Governance