2 Leaning into APIOps: Problem-solving and leading improvements

In chapter 1, I introduced APIOps and discussed its principles and benefits. In later chapters of this book, I dive into the details of specific software tools and practices you can use to improve your API development workflow. But before getting knee-deep in API workflow automation tools, there are a few big questions to answer: Although the API tools I talk about in this book may advertise many benefits, how can you be sure they will improve your API delivery workflow? Introducing automation is one thing, but how can you check that the automation actually improves your end-to-end API delivery performance? The key outcome you want for your customers is that any API workflow automation you introduce with APIOps helps you quickly deliver more valuable, high-quality APIs they can easily integrate with and use. It’s important for your company to see the automation reduce costs and, where possible, increase revenue. Along with these outcomes, you must consider the cultural aspect of embarking on a process improvement drive. How will it be received by your colleagues and other teams you work with?

2.1 Your company’s API quality and lead-time problem

2.2 The A3 approach to APIOps improvements

2.3 Theme and background

2.4 Current conditions and problem statement

2.4.1 Create the work process steps

2.4.2 Draw the information flow

2.4.3 Add performance metrics

2.4.4 Review your map

2.5 Goal statement

2.6 Root-cause analysis

2.7 Countermeasures and target conditions

2.8 Effect confirmation

2.9 Follow-up actions

2.10 Reviewing your A3

2.11 Identifying waste in your value stream

2.12 Benefits of using the A3

2.12.1 Think logically and objectively

2.12.2 Gain alignment, and increase collaboration

2.12.3 Apply a systems thinking approach

2.13 Leading your APIOps transformation

Summary