Avoiding the 8 Wastes of Lean API Development with OpenAPI & APIOps.
summary
Claims that using OpenAPI plus APIOps and the API Cycles method cuts waste and speeds delivery: one team using API Cycles finishes eight customer journeys and finds five reusable APIs in three months versus months of rework for code-first teams. Specific fixes include linting OpenAPI specs, providing runnable examples, automating tests, and using AI to generate specs and tests. Concrete data: 50% of registrants never made calls and 25% contacted support; canvas creator exports canvases as JSON/SVG for tooling and version control.
AI-written summary · about
chapters (11)
- 0:00Lean API Development intro
- 1:10Eight wastes of Lean
- 5:04OpenAPI as a Solution but Not a Silver Bullet
- 6:34Code-centric API failure
- 9:09Poor docs support issues
- 10:59Overprocessing in API design
- 12:24API Cycles overview
- 13:49API Cycles success
- 15:39Canvas Creator tool
- 17:24API lifecycle roadmap
- 18:28Call to action
related talks
22mAPIOps Cycles, how to develop business & software together
23mOpen method for Lean & Business-oriented API design APIOPs Cycles
24mFixing API Chaos: A Practical, Open Method to Structure API Work
16mMaster API Product Design with APIOps Cycles Method
24mPractical API Strategy with APIOps Cycles
49mBuilding Software Better: API Lifecycle Management for Developers
13mFrom Chaos to Clarity: Designing (AI-Ready) APIs with APIOps Cycles
20mAutomated Processes for Even Better APIs