Present with Reveal.js or open the text versions. Download PowerPoint · Download PDF · Download Reveal.js
01
APIOps Cycles
API delivery and digital product thinking
An Australian financial-services case study
APIsFirst with partner Osaango
APIOps Cycles
02
The challenge: dependencies across teams
Established API engineering practices
API products still depended on business and technology teams working across organisational boundaries.
Customer journeys and partner integrations had to fit internal services, legacy systems and compliance obligations.
Teams needed shared requirements, clearer ownership and coordinated delivery decisions.
APIOps Cycles
03
Collaborative discovery in the payments case
What the team did
APIsFirst and Osaango facilitated iterative workshops with business stakeholders, architects and engineers.
What the canvases made visible
Customer and API consumer journeys, value propositions, business rules and operating constraints.
Payments example: consumer details, payment method access, business risks and internal or partner channel needs.
APIOps Cycles
04
Customer Journey Canvas: a supplier payment
Customer and trigger
A small business owner has a supplier bill due and wants to know the payment has completed.
The customer journey
Illustrative example. Not a client artefact.
APIOps Cycles
05
API Value Proposition Canvas: the same journey
Customer concern to API feature
Unclear payment status: show progress and a receipt. Repeat-payment concern: prevent duplicate submissions.
Candidate API products
Illustrative example. API names are provisional.
APIOps Cycles
06
Other canvases supporting API product decisions
API Business Model Canvas
Value, partners and costs of the payments service
Business Impact Canvas
Expected benefits, consequences and critical risks
Capacity Canvas
Demand baseline, peak load and scaling decisions
REST API Canvas
Payment resources, verbs and response examples
Illustrative supplier-payment examples. Capacity measurements and assumptions require validation.
APIOps Cycles
07
API Productization Cycle metro map
One lifecycle connects the work
The engagement connected discovery to design, delivery and testing across these stations.
APIOps Cycles
08
Discovery informed decisions across the lifecycle
Payment API design connected consumer needs to technical controls
| Consumer tasks | Requirements | API design | Controls | Testing |
|---|---|---|---|---|
| Journeys and channel needs | Business rules and constraints | Domain model and contracts | Access, limits and monitoring | API test automation |
Practical support
Guidance on API contracts and test automation. Cross-team input on unresolved architecture and security decisions.
AI modernisation guidance
Advice on using AI to convert legacy interfaces while retaining business requirements and constraints.
APIOps Cycles
09
API product management in everyday work
APIOps Cycles
10
Portfolio planning coordinated API releases
Which APIs to create, improve or release, and in what sequence
API portfolio planning
Priorities reflected partner integrations, UI development and dependencies between provider and consumer teams.
Capability improvement
A complementary view addressed API discoverability, governance, developer experience and product management.
APIOps Cycles
11
The value across products, portfolio and ways of working
Connected work made decisions easier to discuss and repeat
| Level | What the engagement connected | Qualitative value |
|---|---|---|
| API product | Consumer needs, business rules, contracts and technical controls | Shared understanding and more informed design |
| API portfolio | Provider and consumer dependencies with API priorities and releases | End-to-end visibility and coordinated delivery |
| Ways of working | Product ownership and lifecycle decisions with practical methods | Repeatable capability and continuous improvement |
Qualitative benefits of the engagement. No quantified delivery or business impact is claimed.
APIOps Cycles
APIOps Cycles
API delivery and digital product thinking
An Australian financial-services case study
APIsFirst with partner Osaango
Visual: APIOps human scene showing connected discovery and delivery roles
Established API engineering practices
API products still depended on business and technology teams working across organisational boundaries.
Customer journeys and partner integrations had to fit internal services, legacy systems and compliance obligations.
Visual: APIOps human scene showing uncertainty around shared APIs and contracts
Teams needed shared requirements, clearer ownership and coordinated delivery decisions.
What the team did
APIsFirst and Osaango facilitated iterative workshops with business stakeholders, architects and engineers.
What the canvases made visible
Customer and API consumer journeys, value propositions, business rules and operating constraints.
Visual: Generated conceptual APIOps workshop scene, not a photograph or project artefact
Payments example: consumer details, payment method access, business risks and internal or partner channel needs.
Visual: New illustrative filled Customer Journey Canvas for a small business owner paying a supplier invoice
Customer and trigger
A small business owner has a supplier bill due and wants to know the payment has completed.
The customer journey
Illustrative example. Not a client artefact.
Visual: New illustrative filled API Value Proposition Canvas using the same supplier-payment tasks
Customer concern to API feature
Unclear payment status: show progress and a receipt. Repeat-payment concern: prevent duplicate submissions.
Candidate API products
Illustrative example. API names are provisional.
Visual: New illustrative supplier-payment API Business Model Canvas
API Business Model Canvas
Value, partners and costs of the payments service
Visual: New illustrative supplier-payment Business Impact Canvas
Business Impact Canvas
Expected benefits, consequences and critical risks
Visual: New illustrative supplier-payment Capacity Canvas
Capacity Canvas
Demand baseline, peak load and scaling decisions
Visual: New illustrative supplier-payment REST API Canvas
REST API Canvas
Payment resources, verbs and response examples
Illustrative supplier-payment examples. Capacity measurements and assumptions require validation.
Visual: Official API Productization Cycle metro map exported from the repository application
One lifecycle connects the work
The engagement connected discovery to design, delivery and testing across these stations.
Payment API design connected consumer needs to technical controls
| Consumer tasks | Requirements | API design | Controls | Testing |
|---|---|---|---|---|
| Journeys and channel needs | Business rules and constraints | Domain model and contracts | Access, limits and monitoring | API test automation |
Practical support
Guidance on API contracts and test automation. Cross-team input on unresolved architecture and security decisions.
AI modernisation guidance
Advice on using AI to convert legacy interfaces while retaining business requirements and constraints.
Visual: APIOps human scene connecting an API interface to a reusable product capability
Which APIs to create, improve or release, and in what sequence
Visual: Generated conceptual API dependency and release-coordination scene
API portfolio planning
Priorities reflected partner integrations, UI development and dependencies between provider and consumer teams.
Capability improvement
A complementary view addressed API discoverability, governance, developer experience and product management.
Connected work made decisions easier to discuss and repeat
| Level | What the engagement connected | Qualitative value |
|---|---|---|
| API product | Consumer needs, business rules, contracts and technical controls | Shared understanding and more informed design |
| API portfolio | Provider and consumer dependencies with API priorities and releases | End-to-end visibility and coordinated delivery |
| Ways of working | Product ownership and lifecycle decisions with practical methods | Repeatable capability and continuous improvement |
Qualitative benefits of the engagement. No quantified delivery or business impact is claimed.
Use arrow keys or swipe to navigate, Esc for slide overview and S for speaker view. Back to presentation details and source.