Entering the Platform Age: How to create genuine value for internal and external API consumers
Download as PPTX, PDF3 likes3,421 views
The document discusses the importance of creating value for API consumers within the context of modern platforms, emphasizing a co-creation approach between providers and users. It outlines three key strategies for success, focusing on delivering value, optimizing accessibility, and managing API governance effectively. The author stresses the need for a committed platform strategy to empower API creation and usage for business success.
Entering the Platform Age: How to create genuine value for internal and external API consumers
- 1. Entering the Platform Age How to create genuine value for internal and external API consumers Steven Willmott, [email protected] @njyx
- 2. Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)
- 6. THE VALUE OF PLATFORMS
- 8. Agility
- 9. Deliver more value, faster, with less resource
- 10. Platforms power the core of your business
- 11. EXAMPLE: UBER
- 12. EXAMPLE: “APPLE TV-OS READY” IN 2 WEEKS
- 14. PLATFORMS & BI-MODAL IT
- 15. “Gartner's Recipe For Disaster” - Jason Bloomberg / Forbes “This is akin to adding lipstick to the pig.” - Simon Wardley, CSC “Gartner’s bimodal IT considered Harmful” - Phil Wainewright / Diginomica
- 16. True if you are doing it wrong…
- 17. But this is not about separation It’s about going from 1-1 to 1-N (and N-N)
- 18. 1-1 IT Need for software innovation drives deep integrations InternalSystems Applications
- 19. 1-N IT Governance and APIs create reusable anchor points
- 20. N-N IT Common governance rules can apply to APIs from anywhere
- 21. Platform value is “co-creation” of value between providers and consumers (buyers & sellers) (you & partners / customers) (mode 1 & mode 2)
- 23. SO: HOW DO WE SUCCEED?
- 24. THREE KEYS
- 25. “Jeff Bezos Moment” (thank you @frankarr) )
- 26. CHAPTER 1: AUSPICIOUS BEGINNINGS
- 28. But ... adoption is slow …
- 29. #1: FOCUS ON VALUE
- 30. EXAMPLE: MAPS CREDIT UNION Loren Paulson, APIStrat, 2015
- 32. A Map of Expectations Expected Unexpected DesirableUndesirable Thor Mitchel, 2014
- 33. Questions to Ask • Who is the customer? • Where is their value? • If we create this, will you use it? • What is the complete use case?
- 34. Key Strategy Deliver value one API and one use-case at a time
- 35. CHAPTER 2: FOCUSING ON THE CHOSEN
- 37. More adoption … but still 50% off target
- 38. #2: OPTIMIZE FOR ACCESSIBILITY AND UTILITY
- 39. We have great developer experience … what happened?
- 42. Questions to Ask • When Developer Experience is not enough • How do the APIs need to be consumed? • Who else might consume them? • Where do their effects propagate to? • What additional value can we add?
- 43. EXAMPLE: SIMILAR WEB Noahm Schwartz, APIStrat, 2015
- 44. EXAMPLE: FITBIT Jeremiah Lee, San Francisco, 2016
- 45. EXAMPLE: CRUNCHBASE Nicolas Greenie, San Francisco, 2015
- 46. Key Strategy The API is not the key thing – the value is the key thing
- 47. CHAPTER 3: IN FULL FLIGHT
- 48. API Demand is up – multiple teams are using them: powering core business Woho!!
- 49. But...
- 50. Hairy Panic!
- 51. #3: DIVIDE AND CONQUER
- 52. Questions to Ask • How to split Dev, Ops, Management? • What do we automate? • What do we monitor? • Which APIs do we focus on first? • How will we manage change?
- 54. Key Strategy N-N >>>>> 1-N
- 55. Governance + Support e.g. tools, platforms, guides, design sages
- 57. • Very hard work • Unglamorous • It is not a big bang (big bet) • People get upset at rules and restrictions • But … hugely rewarding
- 58. Recommendation: Focus on Business(es) enabled (number, revenue)
- 59. TAKE AWAYS
- 60. Your company NEEDS your platform strategy to succeed
- 61. Even if you have a “Bezos Moment” – Keep focused on the value you are delivering piece by piece
- 62. Try to empower both API creation and usage
- 63. BACK AT THE OFFICE…
- 64. A commitment…
- 65. 1. Talk to ONE key API consumer in depth: nail their use case 2. Write that value down and articulate it for your whole API team 3. Assess the objectives for the API Platform program in terms of business supported
- 66. API Owners Manual http://www.3scale.net @njyx @3scale http://bit.ly/APIOwners
- 67. Images (Copyright Authors) • Apple TV Image, Apple.com: https://support.apple.com/library/content/dam/edam/applecare/images/en_US/appletv/apple- tv-3gen-home-screen.jpg • Amazon Echo: Amazon stock marketing image • Bay Bridge: https://unsplash.com/photos/0iAzHzjeYRk • Jeff Sheldon https://unsplash.com/photos/o6Y9E-DdG6w • Taras Perevarukha https://500px.com/photo/215416/-by-taras-perevarukha • Richard Bland https://500px.com/photo/89775589/coming-for-you-by-richard- bland?ctx_page=2&from=search&ctx_q=platform&ctx_type=photos&ctx_sort=relevance • Kaleb Nimz: https://unsplash.com/photos/-5rA4DRrEXU • Seabags Creative: https://unsplash.com/photos/U3m4_cKbUfc • Todd Quankenbush https://unsplash.com/photos/IClZBVw5W5A • Hairy Panic http://theconversation.com/what-is-the-hairy-panic-tumbleweed-that-has-buried- a-small-australian-city-55074
Editor's Notes
- #25: Three Keys
- #28: Finely crafted! There is a lot of excitement! Fan fare and they get intreset – some very enthusiastic hard core users, but there isn’t huge take up… the project that needed the API is basically happy but it’s hard to deliver. Expectations Met?
- #36: (incredibly hard to do when you have platform dreams!)
- #37: Obvious and easily stated
- #48: (incredibly hard to do when you have platform dreams!)
- #49: Obvious and easily stated
- #53: This is a no-brainer right?
- #56: (incredibly hard to do when you have platform dreams!)
- #58: Obvious and easily stated