We are becoming a digital platform business.

Some business units are building digital businesses.

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

We are not planning to become a digital business.

We think of APIs as products for software developers.

We use APIs primarily to expose assets internally or to partners.

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

We manage APIs as strategic assets for creating business value.

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 experiences.

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

Our business teams just define the products and experiences; IT designs and delivers them.

We are growing existing partnerships by adding a few new digital capabilities.

We are not actively expanding our ecosystem.

We are actively building ecosystems for strategic business advantage.

We are forming new partnerships and extending into adjacent markets.

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

Some IT teams have formally committed to APIs.

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

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

We have no funding for production API projects.

We have no explicit API funding and must convince individual projects to fund APIs.

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

We have funding mechanisms to build APIs only within specific projects.

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

We do not measure the impact of APIs.

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

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

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

We don’t follow modern API best practices.

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 of our software teams design and deliver APIs and API-first solutions.

All of our job descriptions require digital skills. API skills are required for all software development roles.

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

Our teams do not design and deliver APIs.

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

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

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

We have no self-service.