Reduce API Delivery Time from Weeks to Days: Here's How
summary
Claims a real drop in API design review time From 2.5 weeks to 1 day by applying A3 problem solving and automating API workflows. Uses OpenAPI-first definitions stored in Git, CI/CD pipelines, declarative gateway config and software agents (Flux/Argo or pipeline runners) to push changes. Adds automated linting and breaking-change checks, contract tests and small scoped rollouts. Reports much higher standards compliance, far less rework, and a measured improvement (example: ~200% gain vs target) after validating countermeasures.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:00About the company
- 1:15Platform architecture
- 2:50Problem solving
- 4:16Outline
- 4:49Thinking
- 6:45API Ops
- 7:25API Ops principles
- 8:32Example problem
- 9:04Problem owner
- 9:37Theme
- 10:11Background
- 10:39API Compliance
- 11:02Current Conditions Problems Statements
- 12:30Process Charts
- 13:04Goal Statement
- 14:32Root Cause Analysis
- 15:08Capacity Issue
- 15:33Counter Measures
- 16:42Effect Confirmation
- 17:45Followup Actions
- 18:23More tips
- 19:07The Plan Do Study Act Cycle
- 19:58Challenges with A3s
- 20:49Recommended books
related talks
25mAPIOps: automating API operations for speed and quality at scale
29mWhy APIs Call for 2xs the DevOps
01h 01mUnlocking Agile Efficiency: From Days to Minutes
01h 26mOptimising Continuous Delivery
20mAutomated Processes for Even Better APIs
49mOptimizing QA Flow to Minimize Time to Release While Meeting Quality Standards
51mThe astonishing value of speed
27mOptimizing CI/CD Pipelines for Faster Time to Market