Apidays Virtual Helsinki - Alan Glickenhouse, IBM
summary
Outlines a concrete API strategy that compresses business drivers into four claims—speed to market, reach, innovation at low risk, and cross‑domain reuse—illustrates governance that makes it easy to do the right thing and hard to do the wrong thing, and warns that monetization usually means driving revenue not just charging for APIs. Emphasizes the critical role of the API product manager, gives an anecdote about coordinating 46 lines of business, recommends principle‑based API security, and urges measuring the why (revenue, consumers) not just API calls.
AI-written summary · about
chapters (15)
- 0:00Intro
- 3:11What goes into creating a Business Strategy? i.e. the Age
- 6:11Digital Transformation Business Drivers
- 8:43The Business of APIs - Monetization
- 9:48Defining Use Cases
- 11:39Domain Ownership
- 12:58API Success Requires Addressing Needs of Multiple Stakeholders
- 15:32Organization Structure
- 17:19API Initiative Governance - Business Considerations
- 19:30API Initiative Governance - Technical Considerations
- 20:27Architecture and Technical Implications
- 21:57Communication
- 23:12Measuring Success - Analytics Establish meaningful measurable goals for "success" and gain executive agreement
- 24:56API Economy Journey Map Charting the evolution of Digital Transformation
- 26:15Getting Started 1. Executive and Business Backing
related talks
26mMastering API Strategies for Digital Transformation
40mUnlocking the secret to success in the API Economy
26mRevolutionizing Business with API-First Strategy: Key Insights
25mBeyond API Governance: Run your API org like a lean startup
01mWelcome to – Alan Glickenhouse
27mAPI Economy and Ecosystem
19mSolutions Architect. EMEA
40mThe API mindset: tech, product, business and legal
