Orchestrating your organisation for digital transformation
summary
Argues that companies need four core roles—API developer, operations, API product manager and initiative leader—to scale ecosystems; gives concrete examples (car purchase that needs manufacturers banks and insurers, and a “hot toy” supply chain) and says technical onboarding that used to take weeks or months can drop to days, but business agreements still block speed. Recommends a developer portal that combines API docs and business onboarding, cites a February white paper “Recommendations for an API Economy Center of Excellence.”
AI-written summary · about
chapters (15)
- 0:00Start
- 6:12Digital Ecosystems - Past, Present, and Future
- 8:49Who are these people?
- 9:01Introduction to API Roles and Responsibilities
- 9:42API Roles and Responsibilities-API Developer
- 10:15API Roles and Responsibilities - Operations
- 10:58API Roles and Responsibilities - API Product Manager
- 12:15API Roles and Responsibilities - API Initiative Leader
- 13:10API Roles and Responsibilities - Related Stakeholders-IT
- 13:24Organization Structure
- 14:04Digital Ecosystem Orchestration - An Optimistic Scenario...
- 16:10Digital Ecosystem Orchestration - In an Ideal World...
- 17:30Digital Ecosystem Orchestration - In a Less Than Ideal World...
- 20:35Summary
- 22:50Alan's Articles, Blogs, Papers, and Videos...
related talks
26mMastering API Strategies for Digital Transformation
54mAPI team characteristics and best practices
22mDigital Leadership and Digital Ecosystem
28mAPI Productisation - shift RIGHT to Better Product Resilience
40mUnlocking the secret to success in the API Economy
25mBeyond API Governance: Run your API org like a lean startup
19mSolutions Architect. EMEA
29mWhy APIs Call for 2xs the DevOps