How to Design & Publish API Products Your Customers & Partners Want
summary
Argues that APIs must be API as product not one-off projects, recommends hiring an API product manager and using a product vision board and lean/venture tools to map mission → customers → business goals. Describes co-creation work with airports and Airbus, discovers escalators are more critical than elevators for passenger flow, and shows that building owners or facility managers — not developers — are often the paying customers, so portals should present product value first then transition to developer details.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:47Digitalisation
- 1:36Digital Transformation
- 3:06What Can You Do
- 4:03Use a Product as a Vehicle
- 4:42Project Mentality
- 6:26API Product Manager
- 7:29Product Vision Board
- 8:12API Popsicles
- 8:55Killer API
- 9:30Mission
- 10:02People Flow
- 10:43Connected Equipment
- 11:30Elevators as iPhones
- 11:51Getting out there
- 13:55Exercise
- 14:08Hands Up
- 14:32The Developer
- 14:59Questions Going Forward
- 15:14Developer Experience
- 16:56API Portal
- 17:27Who is your customer
related talks
29mTransform Your Business with Strategic API Management
26mRevolutionizing Business with API-First Strategy: Key Insights
28mAPI Productisation - shift RIGHT to Better Product Resilience
23mContinuous API Product Management
26mMastering API Strategies for Digital Transformation
39mSorry Developer, Your API Just Became a Product
26mUsing APIs for Better Business Partnerships
16mMaster API Product Design with APIOps Cycles Method