The document discusses how to define an API business strategy. It outlines key considerations such as understanding stakeholder needs, defining business models, developing communication and marketing plans, addressing legal and security concerns, and establishing teams for product management, development, operations, and more. It emphasizes the importance of treating APIs as products and having tools to help all stakeholders be successful.
Hello everyone thank you for joining the call today. I am laura heritage. I am a principal solution architect for Enterprise API Platforms. I have been working with companies all over the world for the past 10 years establishing AP and SOA strategies. Today I am going to share my experiences on API Management Adoption Patterns.
You can follow me on twitter @heritagelaura
This is a dramatization of a typical scenario happening at large enterprises when it comes to APIs.
The Enterprise Architects gets some nice presentation explain what APIs are to the business but they still shake their heads. Executives are still scratching their head as they think, well we already have a mobile app? We do really need to be in a refrigerator as I can’t really see the demand in that.
For the Enterprise Architect, the writing is on the wall. They understand the technical business benefits. Starting with the for adoptions patterns. The EAs see the most benefit from Internal use to stream line and improve efficiency. They understand the architecture benefits in Mobile, they understand and want to make partner on boarding easier for themselves and they are intrigued by the notion of external innovation but don’t feel they are mature enough yet in most cases.