This presentation was given at API Days Global - Paris.
It often happened to me to work with organizations willing to establish an API strategy, as if such thing exists for real. In the luckiest cases this strategy is seen, at least, as part of a wider plan to embrace the opportunities of the networked age, in something that people often call a digital transformation plan.
But what’s an approach to APIs, microservices and service componentization that makes sense in an age of increasing complexity and interconnectedness? In the age of …Platforms?
My point here is that there’s no possibility — for an organization today — to define its role autonomously, but that the objective of a modern organization should be that of continuously discover its role dynamically, by interacting with the entities that populate its ecosystem.
This post gives you the context: https://stories.platformdesigntoolkit.com/design-apis-for-disobedience-7894f930e2cc
21. “When user needs are highly
heterogeneous, [monolithic products]
leave many seriously dissatisfied. One
solution is to enable users to modify
products on their own using
“innovation toolkits.”
Eric Von Hippel
@meedabyte #PDToolkit
22. Your APIs and Platforms are
Ecosystem Innovation Toolkits
@meedabyte #PDToolkit
31. “organizations which design systems
... are constrained to produce designs
which are copies of the
communication structures
of these organizations.”
Mel Conway
@meedabyte #PDToolkit