API Economy growth predictions are looking great.Â Â Â A search on â€śAPI Economy Growthâ€ť finds an endless supply of reports and articles showing excellent growth projections â€“ and we are still in the initial stages.Â Industry standards are starting to form which will drive further use.Â With this, it seems odd to think that there is something impeding growth, but I think there is – the three-letter acronym: API.
Most companies that have API initiatives are driving the initiative from IT, often with little involvement from the business.Â The subset of companies that do involve the business obtain higher value.Â So, why is the business often uninvolved if this would drive higher value?
We all know that API stands for Application Programming Interface.Â But, you knew this before the
recent API Economy excitement â€“ and that is the problem.Â API as a term has been around for decades.Â Any program calls another program through its API.Â The problem is we are not talking about all these APIs.Â If I tell you I want to talk to you about an elephant, you already have a picture in your mind as to what this is.Â Even if I tell you I want to talk about a new and different elephant, you are going to point me to the people in your organization that deal with elephants to discuss this topic.
That is the problem with the term â€śAPIâ€ť.Â We already have a definition for this term which everyone knows and now we are reusing it for a different meaning.Â We should be saying â€śBusiness APIâ€ť or â€śWeb APIâ€ť to distinguish it, but nobody does that.Â When talking about API Economy APIs, we are talking about business recognizable assets that are simple and easy to consume.Â This is not the traditional technical API interfaces we have been using.
Lesson 1 â€“ be careful of terminology.Â Do not assume the people you are talking to about APIs understand the differentiated definition of a Business API.
Lesson 2 â€“ do not say â€śAPIâ€ť to the business people.Â They will send you back to IT.Â Use terms such as â€śdigital business assetsâ€ť.
Having versus Using
â€śI already have APIsâ€ť.Â I cannot count how many times I have heard this phrase.Â Yes, everyone has APIs.Â And, with the growth in popularity of the API Economy, more back-end systems and middleware are supplying APIs for their functions.Â The API Economy facilitated by API Management software is not about having APIs, it is about driving consumption of your APIs.Â Yes, part of this is to enable the creation of an API, but beyond this it is about, governance, management, security, socialization and simplified consumption of the APIs (see my prior blog on this topic).
Lesson â€“ acknowledge that APIs already exist but explain what is new and different.
Cost Savings versus Revenue Generation
The term â€śAPIâ€ť having a technical heritage has landed API initiatives in the domain of IT.Â Historically similar solutions (i.e. middleware) have been put in place to drive cost savings for IT.Â And, APIs do drive IT cost savings.Â However, this is like measuring an iceberg by counting only the part you can see above the water.
By far the larger value from API initiatives is revenue generation.Â Several of the API business drivers (blog) – speed to market, reaching new customers and new markets, and innovation â€“ are about driving business revenue.Â The challenge is that IT has difficulty predicting revenue which is outside their domain and falls back to measuring only the cost savings.Â A second and more critical issue is that by not involving the business early, the revenue generating projects are delayed â€“ giving competitors a chance to jump ahead.
Lesson â€“ recognize that API initiatives are about revenue and involve the business early.
When you boil it down to what the â€śBusiness APIâ€ť technically is, it is an Application Programming Interface.Â But, describing what it is doing does not communicate the value it is providing.
â€śBecoming a Digital businessâ€ť, â€śCloud computingâ€ť, â€śArtificial Intelligenceâ€ť are all extremely popular topics of discussion both for the business and IT.Â There are no scary TLAs* in these names that have the business people telling you to talk to IT.Â Unfortunately, I am not going to be able to drive the industry to rename API Economy.
Lesson â€“ Understand your audience and how they will react if you discuss â€śAPI Economyâ€ť.Â If necessary, avoid the term and talk about the value to the business â€“ speed to market, reaching new customers and markets, and innovation.Â You will find much greater acceptance in creating a partnership with the business to drive a successful initiative if you discuss values delivered.
A few years ago I was co-author of the API Economy Journey Map, which in simple terms is a view of the maturity of the API Economy as it moves from IT led, to IT/Business partnership, to Business led, to Ecosystem, and then beyond.Â I continue to believe this will be the progression, but we are still in the early phases.Â In my opinion the term â€śAPIâ€ť is holding this discussion in the IT domain and impeding the progress.Â Your business can break down this barrier inside your company by using the appropriate terminology for each audience and communicating value.Â As more companies recognize the value, the growth rates for the API Economy shown today will look small.
To understand more about IBMâ€™s thoughts on the API Economy visit the IBM API Economy website.Â IBM API Connect is IBMâ€™s complete foundation to Create, Run, Manage, and Secure APIs.Â You can find more information about IBM API Connect at the API Connect website.Â And you can also experience a trial version of API Connect.
If you have questions, please let me know.Â Connect with me through comments here or via twitter @Arglick to continue the discussion.
* TLA = Three Letter Acronym