![]() How do we track success against the business goals that have been set?Īn API team is most closely related to a “product” team-whether your customers are internal or external, you are in charge of building, deploying, operating, and optimizing the infrastructure others depend on.How are the APIs promoted inside the organization or marketed to the outside world?.What technology is used to build the APIs?.The final question, “How do we design our API program to achieve what we want?” is all about implementation and execution. Internal directions about the value of an asset may change, which could also affect what should be achieved with an API. In concrete terms, while the why is unlikely to change often, the what may vary significantly based on external factors-such as markets, technical considerations, or economic conditions. The decision about the what is then usually a combination of the 2 views. When deciding what an API should do for a business, both internal and external views The more valuable and unique the services and resources offered the more suitable they are for an API program.Īn organization that has unique data could take advantage of this resource by allowing access to the data via API. Unique content, data, and services can make access to the API extremely valuable. The internal view refers to specific, valuable assets an organization possesses. The second question should be “What concrete outcomes do we want to achieve with these APIs?” In other words, “What do the APIs actually do and what impact do they have on the wider business strategy?”īoth the concepts of the internal view and the external view of an organization can help to define the what of the API. The benefits to the organization need to be strong enough to make the decision to invest in the APIs an obvious choice for the organization. The top technology drivers are to improve application integration, improve mobile integration, and support the connection to more devices. ![]() The most common business drivers for establishing an API program, according to a survey of 152 organizations conducted by the Cutter Consortium and Wipro, are to develop new partnerships, to increase revenue, to exploit new business models, to improve time to market, and to develop new distribution channels. The value of the API to users is the result of an API call (service request and response), rather than the call itself. APIs are usually driving some other metric-sales, affiliate referrals, brand awareness, etc. This is true only if the API itself is the product. An API is valuable when it becomes a channel that provides new types of access to the existing value an organization delivers.Īnother common misconception is believing that for an API to be valuable users must be prepared to pay for it. Remember, it’s the organization’s core business that’s valuable, not necessarily the API. Firstly, rather than focus on the value of the API, it’s helpful to think of the value of the effect of the API. People often misinterpret this question in different ways. How do we plan to execute the API program to achieve that?.What concrete outcomes do we want to achieve with these APIs?.You’ll know you have the makings of a great strategy when you can answer the following 3 questions in a clear way: It’s no longer a stretch to say that most organizations don’t ask whether to engage in API programs, but how to do so.Īn effective API program has to build on an organization’s overarching corporate strategy and contribute to its objectives. APIs are important to modern organizations, adding new capabilities to everything from their operations and products to their partnership strategies. API design refers to the process of developing application programming interfaces (APIs) that expose data and application functionality for use by developers and users.
0 Comments
Leave a Reply. |