liveBook · Manning

Job to be done

As explained in Automating API Delivery

Jobs to Be Done is a framework for identifying the goals and underlying needs that motivate customers to use or purchase a product or service.

Jobs to Be Done identifies the goal, triggering situation, motivation, and expected outcome behind a customer’s use of a product or API. In API design reviews, expressing that job clarifies the API’s business purpose and the consumer task it must support. section 5.2.3

Translate a job into API design inputs:

  • Describe the triggering situation and user goal. section 5.2.3
  • State the outcome the user expects. section 5.2.3
  • Derive the high-level tasks or digital capabilities the API needs to provide. section 5.2.3

Product Catalog API

When I need a product to care for my pet, I want to discover products in the relevant category with quality reviews so I can choose one. This job leads to capabilities for browsing the catalog by category and, later, searching for particular products. section 5.2.3

Table 5.1 Example of an API profile
Item
Description
API name
Product Catalog API
API value proposition
An API to discover Acme’s great range of products so users can find products to care for their pets
API consumer
The end user is a customer browsing Acme Pet Supplies products to make a purchase. Client API developers will use this API to build three end-user channels: the Acme mobile app, the Acme web store, and an affiliate’s store.
Job stories
Story 1:
When exploring what products Acme has available, I want to browse the Acme catalog by category so I can find new and exciting pet products that interest me.
Story 2:
When exploring what products Acme has available, I want to search for particular pet products in the Acme catalog so I can view details of the product and decide if I want to buy.
Note: Search catalog capability will be in phase 2.
Access level
Public API, made available for use by both Acme-owned digital channels and registered affiliates
Usage plans
Acme mobile app: 10 requests a minute
Acme web store: 10 requests a minute
Affiliate stores: 8 requests a minute
Security model
API requests should be authorized using OAuth2. We’ll start with the read permission scope for the MVP but will add more scopes as the API functionality is expanded.

Use the API profile to inspect the consumer, value proposition, job stories, access level, and planned capability scope. section 5.2.3

How Automating API Delivery covers it

How deep it goes
Defines job stories and derives high-level digital capabilities, but stops short of detailed implementation.
Examples
Uses a pet-supplies Product Catalog API with category browsing, product search, and quality reviews.
What it assumes
Assumes familiarity with API consumers and design reviews while explaining the job-story approach from its basic elements.
What you can do after
Apply it to clarify API requirements, scope, boundaries, and consumer-facing digital capabilities.
How it connects
Connects user stories, user journeys, digital capabilities, API profiles, and value proposition canvases.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Automating API Delivery. The section links point to the parts of the book it draws on.