Note: These are my personal views and even though the title may sound exaggerated, the truth in the post will resonate if you are willing to reflect deep enough.
Background
Often times organizations which care to some extent about APIs think that they have an API problem if:
-
They don’t have API governance / processes / practices / standards in place.
-
They don’t have API infrastructure like gateways, portals in place or if its not being utilized properly.
-
The APIs are not actively used by developers / not perceived as valuable / not generating value for business
All of these are valid. However if you dig deeper there could be more fundamental issues from which the above manifestations may be stemming. The fundamental caused need to be understood and addressed if one wants a effective and lasting solution to the problem at hand.
And that’s exactly what we look at in this post.
So what are the fundamental problems?
Business is not talking APIs
APIs make a difference to business - sometimes explicitly, sometimes implicitly and sometimes strategically. More details can be found in this post. That being the case business needs to actively engage with APIs. If you see any or all of these following signs, know that there is a fundamental issue:
-
There is no business ask for APIs.
-
Business folks are not aware of APIs or don’t talk about APIs in any forum - internal or external.
-
Words like API strategy, API portfolio, API roadmap, API monetization are not part of the business vocabulary.
-
There is not a single person in the business org who has API in his/her title or role.
-
Spanner / cold water is thrown on any attempt to get focus on/for APIs.
The point here is not that the only thing the business does is focus on APIs. The point here is that business can’t be indifferent to and detached from APIs. Business needs to have skin in APIs.
No API stories to tell
If you are not doing anything with APIs you will obviously not have anything to tell about it. But if you are playing on, there will be stories to tell. Some may be success stories, others may be lessons learnt but there will be something to say. Regardless of whether you succeed or learn, you will grow and mature when you play on. The only way to stay stuck and not make any progress is to not play at all.
And when you start playing, stories will emerge naturally.
“If silence is the only (API) story you have, then either you are asleep or your are dead.”
-S-
Ignorance and indifference as a strategy
Not taking APIs seriously till it becomes a serious issue.
The most common example is not paying enough attention to API inventory, auditing and security thereby not even being aware of the attack surface and consequences of an attack. The only thing worse than not having APIs at all is having APIs which are insecure and can be a potential threat. You need a minimum viable commitment for APIs. If you are doing APIs do it with a certain level of quality and care.
Conclusion
While it may seem that doing APIs is only about the governance (standards, design, compliance etc.) and infrastructure (API gateway, portals etc.) aspects but there is something more to it.
-
Business needs to actively involve in APIs.
-
APIs translate to stories.
-
APIs need a minimum viable commitment (read care and quality).