Shaking the Foundations: How to Move From a Corporate to an Open API Mindset

Transcript

1. Shaking the foundations: How to move from a Corporate to an Open API mindset Maria Garcia Luengo API Days Helsinki 2 June 2020
2. We’re doing ok so far We’ve always done it this way It’s not a good time We don’t have bandwidth It’s not in the budget We’re too busy! We have other priorities It’s not our job Let’s not reinvent the wheel! It’s too risky
3. Overcoming organizational resistance to your API initiative
4. Maria Garcia Luengo Innovation Strategist & Program Manager Building the future of travel!
5. 01 02 03 Competing priorities Organizational culture Fear of risk Key Challenges
6. Pitch your APIs value 01 02 03 Overcoming challenges Team & Governance Minimize risk How to successfully launch your API initiative
7. 01 Competing priorities Communicate value to stay ahead
8. Standing out in a jungle of projects Why APIs over something else?
9. Challenges to getting buy-in in the current context • Budget • Uncertainty • Short-term focus
10. Build a compelling case Importance in current context (digital transformation) Benefits of adopting APIs (value generation) ...and risks of NOT adopting APIs
11. 11 “Agility, scalability and automation will be the watchwords for this new era of business. Those that have these capabilities now will be the winners” World Economic Forum (April 2020)
12. Survival 20% Companies disappear Reinvention 10% Come out stronger “CHANGE has put many companies out of business and made other companies come out STRONGER and REINVENT themselves. The companies with a long- term mindset are the ones that will come out stronger. ” Simon Senek (May 2020) Source: Harvard Business Review
13. 31% revenues generated by APIs, according to IT leaders Source: Mulesoft 2020 Connectivity benchmark report
14. • Customer reach, adoption • New business models • Processes efficiency, automation • Time-to-market • Partnerships • Product improvements • New channels • Innovation, new use cases • Early trend detection • Brand perception APIs: value generation
15. Data is Power • Create a sense of urgency • Explain the risk of inaction • Provide proof: • Customer surveys • Competitive analysis
16. 02 Organizational culture & structure API Team & Governance
17. APIs at large, complex organizations Scattered initiatives Ownership & resistance Legacy systems
18. How to overcome structural challenges Ring-fenced API Team Common API Governance
19. Ring-fenced team (Business) Strategy Program Management Product Management & UX Developer Relations & Marketing Ring-fenced team (Tech) Business Units Corporate Functions Ring-fenced API Team
20. Program Platform Data API Design What: program strategy & coordination. How: ring-fenced team + representatives of all units and functions. Multiple hierarchy levels (e.g. Core, Steering...) What: common API platform maintenance & evolution (roadmap). How: Product Managers from all units and development teams. What: legal, commercial, security data risk analysis. APIs validation. How: central committee of data experts and representatives of all units (management). What: vision, guidelines, rules for API design. APIs review and approval. How: collaborative community of API experts across business units. Equal voting rights. Our approach to Governance
21. 03 Fear of risk Minimize risks, start small
22. Business Security Performance Cannibalization, legal risks. Attacks, data. Scale to accomodate volume. Opening APIs: most common concerns
23. 1 2 3 Security, Architecture. Business models, etc. Prepare, anticipate stakeholders’ concerns, communicate. Manage risk Transparency Start small, MVP Pick a basic use case. Test, learn, iterate, grow. Address the concerns
24. Quick wins: launching your first proof of concept Amadeus for Developers MVP (2018) • Limited set of APIs. • Low-risk data. • GET-only APIs. Continuous expansion & evolution • New APIs + categories (e.g. AI). • Core APIs, including POST. • New platform capabilities... developers.amadeus.com
25. Conclusions Your journey to launching your API initiative 25 Images: Amadeus at hackathons
26. 1 2 Competing priorities Organizational structure & culture Perceived risk (business, technical) 3 Let’s recap: Common roadbloacks to getting buy-in
27. Let’s recap: Tactics to overcome resistance Explain value Team & Governance Minimize risk Transformation enablers. Benefits of adoption. Risk of not doing so. Ring-fenced program team. Governance: program, platform, data, APIs. Risk management. Transparency, getting ahead. Start small, MVP.
28. Your API journey: An adventure worth taking
29. Ask the API Days community!
30. Thank you! developers.amadeus.com developers.amadeus.com/blog Follow us on: linkedin.com/in/mariagarcialuengo/ developers@amadeus.com Let’s talk!