API capabilities
The visible part of the design of an API product is what users interact with. API capabilities are what users simply call “the API.” Without capabilities, you wouldn’t have an API to offer in the first place. That’s why identifying and validating an API design starts by defining and testing capabilities. As you’ve seen earlier in this book, capabilities are derived from potential users’ challenges. Let’s learn how to structure the work of identifying capabilities by understanding use cases.
Use case analysis
Since not all potential users are alike, earlier in this book, you learned how to identify, define, and document user personas. If each user persona is an abstract representation of a group of people, then you can compile the things that the group of people does regularly. Among those things are the jobs to be done (JTBDs). I find the information about each JTBD particularly interesting because it lets you...
