The
adoption of new technology initiates change, and the impact of that change may
be easily digested or resisted with all one’s might. Where does the change
represented by the adoption of API management fit into the spectrum? And how
does one overcome the risk that is imposed by resistance?
At Apigee we have been able to see many organizations
address the cultural impact of this change. At one level, it is an IT
organizational change that involves now using API management tools instead of
using older approaches and the comfort they offer as @Kristopher Kleva has noted. At a business level it is a
transformation of business that elevates the importance of digital business
with perhaps even new business models that may bring uncertainty to those
familiar with the way business has always been done.
Particularly intriguing to me are the older companies, the
decades old or 100 year olds that by the nature of their existence have
navigated cultural change many times before. What is their secret?
This thread is an attempt to begin a discussion of how to
best address the challenge of cultural change as a result of the adoption of
APIs, API management, digital transformation or anywhere along that spectrum.
It’s long been my view that technology driven success is 20% technology and 80%
the people and their approach to managing the change associated with technology.
What’s your experience? How have you mitigated the risk
associated with people part of the success equation?
LinkedIn
Twitter