The Building Blocks for a Successful API Strategy
Many companies have launched API programs, and many more will in 2011. Some have used their API to become unstoppable market forces by empowering a new indirect channel. Others have seen minimal API adoption, and are unclear on why they havent succeeded. Even more are in the mushy middle between success and failure.
At Apigee, we observe common patterns in API programs that succeed in planning, management, and organization. Those that fail hit common pitfalls in these categories as well. So we have developed a nine-box model for API program management that helps track how both strategy and execution must come together to build a successful API effort.
Strategy: Know your market segment and channel partners (developers)
Execution: Plan, Manage, Organize
This results in the following nine-box model for executing an API program. This assumes that the channel is developers but should be modified to match the way that your business needs to define the channel.
PlanningManagementOrganizationTarget Segment(s)Define market segment in detail including size and user persona; specify API profile needed to satisfy top use cases for each target segmentEstablish key performance indicator targets, traceability and dashboardBusiness-ledSegment-oriented workstreamsEngage ChannelSpecify business model and marketing driver for the channel that will reach each target segmentEstablish developer adoption targets, developer marketing and channel actions (community site, events, and communication)Channel-led
Community, developer, and business development workstreamsIndustry GoalSpecify roadmap of API deliverables, mechanics, integration, and business process to meet target segment needsImplement API roadmap, adjust and report on iteration cycle, and establish alpha developer teamEngineering-led
API, infrastructure, and developer support workstreams
The top-left box should pull all of the others. And API programs key performance indicators should align with existing corporate business key performance indicators. With this framework in mind, the most common pitfalls in API programs we observe are a lack of a business goal and a lack of a channel leader.
Without a business goal and attendant core performance indicators the program will fail because its not seen as a business or an ongoing program, but as a side project, solely led by engineering. But! APIs ar e in fact lines of business in their own right and companies have to manage them as such. Without this alignment the team will get pulled in different directions, or company focus, funding, and commitment will falter.
Similarly, the lack of a channel leader ensures that the program will fail because the channel itself is not understood. An effective leader for the developer channel understands both developers and business and is a full peer to the engineering and business leader. In many cases the de facto leader for a developer channel is a community manager, developer advocate, or API evangelist. Sometimes this person doesnt exist as a full-time role, and in other failure cases the position is not granted the right level of authority. We will see this role become more understood in the coming year especially among companies that have successful API programs.
Good luck in your API program, and let me know in the comments if you have questions based on the model above, or want to suggest further articles on API strategy and execution.
Sam Ramji is Vice President of Strategy at Apigee, a company that manages APIs. Prior to Apigee, Ramji led open source strategy across Microsoft.
Related content from GigaOM Pro (subscription reqd):
- VMwares Cloudy Ambitions: Can It Repeat HypervisorSuccess?
- Infrastructure Overview, Q22010
- Defining Internal Cloud Options: From Appistry toVMware
Comments