Unlocking API Success: Bridging Business & Engineering
summary
Argues that treating APIs as core products prevents wasteful duplication — for example a single email capability can otherwise become 50–200 duplicate email APIs across teams — and shows how an API-first approach yields a reusable catalog, governance group, and observability/analytics to prove usage. Demonstrates concrete tools: OpenAPI specs for contracts, Postman tests exported into CI, and claims a simple API can go from design to production in half-day to production when standardized.
AI-written summary · about
chapters (7)
- 0:00Welcome
- 3:40APIs misunderstood across teams
- 10:27APIs as core products
- 13:12API-first development
- 17:08OpenAPI governance
- 19:55Business meets engineering
- 26:20Q&A
related talks
26mRevolutionizing Business with API-First Strategy: Key Insights
19mUnlocking API Opportunities: Best Practices for Corporations
40mUnlocking the secret to success in the API Economy
40mThe API mindset: tech, product, business and legal
29mUnlock the strategic value of APIs in digital transformation
28mAPI Productisation - shift RIGHT to Better Product Resilience
54mAPI team characteristics and best practices
26mUsing APIs for Better Business Partnerships