Our digital initiatives focus on modernizing IT while business proceeds as usual.

We are not digitally transforming the business.

Some business units are building digital business models.

Our whole company is transforming to become a digital platform business.

We use APIs to build digital experiences and products.

We think of APIs as a way to do systems integration.

We manage APIs as strategic assets for creating business value.

We use APIs for open innovation and to expose assets to partners.

Our business teams just define the experience; IT designs and builds products and APIs that deliver it.

We relentlessly use data to improve our products and customer experiences.

Our business and IT are converged into teams that work together to make products and services.

We build experiences based on the services that IT tells us are already available.

We are actively developing our capabilities to build ecosystems for strategic business advantage.

We want to augment existing partnerships with a few new digital capabilities.

We are not actively expanding our ecosystem beyond existing technologies and integrations.

We are investing in new partnerships and want to extend into adjacent markets.

Many business leaders are driving their products and services with an API-first approach.

We have champions and some IT teams have formally committed to API-first.

We have a few API evangelists with some following, but no explicit executive support.

Our CIO/CTO has mandated an API-first digital transformation.

We have a funded, company-wide initiative to build the API platform.

We have no funding for production API projects.

We have funding mechanisms to build APIs within individual projects.

We have to convince individual projects to use APIs in order to get something built.

We use traditional IT-centric numbers, such as APIs produced or cost of producing them.

We use metrics focused on consumption of APIs, such as number of developers and number of apps.

We measure the impact that our APIs have on the business in terms of revenue, NPS, and speed to market.

We do not measure the impact of APIs.

Less than half of our software development teams follow modern best practices.

All of our software development teams follow modern best practices.

More than half, but not all, of our software development teams follow modern best practices.

We don’t follow modern API best practices.

All of our software teams design and deliver APIs.

Fewer than half our teams design and deliver APIs, typically for special projects.

More than half our software teams design and deliver APIs.

Our teams do not design and deliver APIs.

We have no self-service.

Our self-service processes are manual, with access provided in a week or more.

We have a basic online self-service process, and a few of our APIs are ready to use within a day.

App developers can get to “Time to First Hello World“ with many of our APIs in less than five minutes.