Automating an API delivery workflow does not, by itself, make delivery better. Lean thinking asks whether the workflow creates more value for API consumers while using fewer resources and producing less waste. The aim is continuous improvement, not automation for its own sake. section 2.0
Five principles guide the work:
- Specify the value created by each product. section 2.11
- Identify its value stream—the work that creates and delivers that value. section 2.11
- Make value-creating steps flow by reducing large batches and queues. section 2.11
- Let customer demand pull value from the producer. section 2.11
- Pursue perfection through continued improvement. section 2.11
For API delivery, start with a current-condition process map and distinguish activities that add value from those that do not. Value stream mapping helps show the flow of work and time taken. An A3 problem-solving sheet provides an iterative way to examine improvements, build alignment with colleagues, and capture what is learned. section 2.0 section 2.11
Judge a proposed APIOps change by its end-to-end results: can customers integrate with and use valuable, high-quality APIs sooner? Also consider costs, possible revenue gains, and how affected teams receive the change. These questions help determine which automation is worth introducing and sustaining. section 2.0
