Mapping out your API Strategy - 4.20.11 Webinar slides

10,289 views
10,143 views

Published on

These are the slides for Apigee's API Workshop webinar "Mapping out your API strategy" by @sramji and @landlessness

Published in: Technology
1 Comment
6 Likes
Statistics
Notes
No Downloads
Views
Total views
10,289
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
168
Comments
1
Likes
6
Embeds 0
No embeds

No notes for slide
  • Creative Commons Attribution-Share Alike 3.0 United States License
  • Superset of API best practices and lessons learnedFocus: strategy, technology, design and adoption Considerations for your roadmapAmmunition to help you evangelize APIsRule: no product pitchCreative Commons – please take and use
  • You
  • Mapping out your API Strategy - 4.20.11 Webinar slides

    1. 1. Mapping out your API Strategy<br />4.20.11 @ 11:05 PST<br />VOIP or Dial-in (see chat)<br />Brian Mulloy@landlessness<br />Sam Ramji@sramji<br />
    2. 2. Welcome to our first webinar.<br />
    3. 3. @landlessness<br />@sramji<br />
    4. 4. “Rapid API” Workshop Webinar Series <br />Today: Mapping out your API Strategy <br />10 Patterns in Successful API Programs<br />Pragmatic REST: API Design Fu<br />API Tech & Roadmap Considerations<br />Driving API Adoption<br />
    5. 5. Part 1: Mapping out your API Strategy<br />
    6. 6.
    7. 7. You need a strategy for the explosion in consumption. <br />
    8. 8.
    9. 9.
    10. 10. Do business in the customer’s full context.<br />
    11. 11.
    12. 12. Align your investments with your customers.<br />
    13. 13. Example iPadapp<br />
    14. 14. What About Android?<br />
    15. 15. And LinkedIn?<br />
    16. 16. And Another Partner?<br />
    17. 17. And Another Product?<br />
    18. 18. Resources Required<br />
    19. 19. The Big Bet of Yesterday<br />
    20. 20. Many Bets of Today<br />
    21. 21. How to Do It All?<br />
    22. 22. API Initiatives<br />
    23. 23. Internal<br />
    24. 24. Partners<br />
    25. 25. Open<br />
    26. 26. Enterprise API Engine<br />
    27. 27. API Value Chain<br />App<br />User<br />API<br />Team<br />World of<br />APIs<br />App<br />Store<br />Internal<br />Systems<br />App<br />Developer<br />API<br />App<br />
    28. 28. “<br />John Musser<br />Programmable Web<br />
    29. 29. But how?<br />
    30. 30. Let’s break it down<br />
    31. 31. Establish Target Segments<br />Engage Developer Channel<br />Set Industry Goal<br />
    32. 32. target segments<br />An API should extend your core business<br />into a new part of the market<br />
    33. 33. target segments<br />Your core business already has <br />key performance indicators<br />
    34. 34. target segments<br />So apply your KPIs to the new market segment you’re targeting with your APIs<br />
    35. 35. target segments<br />What is the market impact you need to create in order to succeed as a business?<br />
    36. 36. target segments<br />What does the targetsegment need that it is not getting from you today?<br />
    37. 37. target segments<br />The answer will be the foundation of your API strategy.<br />
    38. 38. developer channel<br />In most cases the channel for your API will be developers, but what do they need?<br />
    39. 39. developer channel<br />A profit motive.<br />
    40. 40. developer channel<br />Here are the leading profit models for developers today<br />
    41. 41. developer channel<br />App sales<br />
    42. 42. developer channel<br />In-app purchases<br />
    43. 43. developer channel<br />Affiliate royalty<br />
    44. 44. developer channel<br />Your advertising spend<br />
    45. 45. developer channel<br />Market awareness of their offering<br />
    46. 46. industry goal<br />If you don’t know where you’re going, you definitely won’t get there<br />
    47. 47. industry goal<br />Partnerships and platform businesses are very different things.<br />
    48. 48. industry goal<br />Partnerships are formed to serve a known set of entities<br />
    49. 49. industry goal<br />A partner API should be traceable to each partner’s relationship<br />
    50. 50. industry goal<br />And support end-to-end business processes<br />
    51. 51. industry goal<br />A platform exists to create massive and unpredictable opportunities<br />
    52. 52. industry goal<br />All your technology, support, and community decisions will be about surviving the scale of adoption<br />
    53. 53. That’s the strategy dimension.<br />
    54. 54. The execution dimension is what you already know.<br />
    55. 55. Planning.<br />Management.<br />Organization.<br />
    56. 56. Putting all this in context gives us a map for our API strategy <br />
    57. 57.
    58. 58. In summary<br />Open, Partner, or Internal?<br />Align Execution with Strategy (try 9 boxing)<br />
    59. 59. Next Time<br />Mapping out your API Strategy<br />10 Patterns in Successful API Programs<br />Pragmatic REST: API Design Fu<br />API Tech & Roadmap Considerations<br />Driving API Adoption<br />
    60. 60. THANK YOU<br />Questions and ideas to:<br />@landlessness<br />@sramji<br />@apigee<br />

    ×