1. Strategy & Objectives for APIs: This is the core glue between the Business Canvas and the API Adoption Canvas. Based on the output from the Business Canvas the strategy and objectives should be defined and can stream through all other aspects. This should capture key objectives both short and long term and include important milestones.
- Infrastructure required to support the API Platform
- Installation and configuration¬†
- Skills required for API Platform
3. Key Resources / Dependencies: what are the IT, people and financial resources and dependencies required to make the project a success such as:
- Sponsor users
- Line of Business dependencies
- IT Resources¬†
4. Key Roles & Partners: within an API Project many roles exist, such as:
- API Developer
- App Developer
- API Deployer
- API Product Owner
- System of Record owners
- Operations Team (monitoring API availability)
- Infrastructure Team (building the API Platform and planning for the required capacity)
It is important to identify these roles early on and map them to who within the organization, partner community will fulfill these roles for your project. Different API projects within the same organization may have different answers to the above questions.
5. Early Adopters / Customer Segments: who will be the first users of these APIs, will they initially be internal and partners, and then over time grow to include the public.¬†
6. API Products/Descriptions: discover and define the APIs or types of APIs, that will be built to realize the strategy. While defining these, the team should consider the short, medium and long term nature, and attempt to flesh out the short term APIs in most detail. Identify business and consumer requirements for the API and then identify potential back end systems that can fulfill this requirement.
7. Socializing APIs: depending on the overall API strategy, an API may be exposed to internal, partner or public developer communities. Each of these commonly have a different mechanism for consumption, for instance an internal API may be available to everyone within the organization that registers, however the public developers need to pay for access.¬†
8. Cost Structures:¬† where the business objective is to define a API driven revenue channel, the cost of implementing API infrastructure and exposing APIs needs to be ascertained. This is required to define and measure the business success. For reference, a study by Forrester Consulting on the Total Economic Impact of APIs enabled by IBM API Connect can found .¬†
9. Revenue Streams & Pricing model:¬† APIs can be Monetized to create a new revenue stream. APIs can be viewed as products that require a pricing model to be defined based on the business resource that are exposed and the value of those resources. There are many possible Monetization business models including direct payment for usage, paying someone to use your API as well as Indirect models. You can find more information on API Monetization models .¬†