Who it's for
Designed around these roles
Product, business and technology leaders exploring API-enabled services, fintech partnerships and B2B platform propositions.
Purpose
Design the business relationships behind an API-enabled service.
Treat APIs as part of a product and operating model, not only an integration task. Explore who receives value, how partners participate and what the service needs to work reliably.
- Best for
- Product, business and technology leaders exploring API-enabled services, fintech partnerships and B2B platform propositions.
- Planned outputs
- 3 draft outputs for your team to review
- Topics
- 6 topics of learning and practice
- Formats
- Online, Onsite, Hybrid
- Engagement
- Standalone workshop or a module in a wider engagement
At a glance
Why teams take this workshop
Challenges this workshop addresses
Integrations without a clear value proposition
Unclear partner obligations
Product plans that omit service operations
How the workshop works
From your challenge to working material
Follow how the topics build towards each planned output. Select a stage or a topic to step through it.
Learning outcomes
What your team leaves with
The outputs below are proposed workshop deliverables: drafts and working tools for your team to review and develop. Final scope is agreed before an engagement. Business results depend on subsequent decisions, implementation and context.
- Output 1An API-enabled service proposition and stakeholder map.
- Output 2A partner dependency and responsibility map.
- Output 3A draft set of business requirements for onboarding, data permissions and service operations.
Workshop outline
Topics and the outputs they feed
The outline below shows the learning scope. Sequence, depth and timing are agreed during scoping.
| Session | Topic | Builds towards |
|---|---|---|
| 01 | API-enabled value propositions and business models | An API-enabled service proposition and stakeholder map. |
| 02 | Customers, partners and service boundaries | An API-enabled service proposition and stakeholder map. |
| 03 | Partner onboarding and commercial dependencies | A partner dependency and responsibility map. |
| 04 | Data permissions and responsibility allocation | A partner dependency and responsibility map. |
| 05 | Reliability, support and operational requirements | A draft set of business requirements for onboarding, data permissions and service operations. |
| 06 | Product measures and phased validation | A draft set of business requirements for onboarding, data permissions and service operations. |
01
- Topic
- API-enabled value propositions and business models
- Builds towards
- An API-enabled service proposition and stakeholder map.
02
- Topic
- Customers, partners and service boundaries
- Builds towards
- An API-enabled service proposition and stakeholder map.
03
- Topic
- Partner onboarding and commercial dependencies
- Builds towards
- A partner dependency and responsibility map.
04
- Topic
- Data permissions and responsibility allocation
- Builds towards
- A partner dependency and responsibility map.
05
- Topic
- Reliability, support and operational requirements
- Builds towards
- A draft set of business requirements for onboarding, data permissions and service operations.
06
- Topic
- Product measures and phased validation
- Builds towards
- A draft set of business requirements for onboarding, data permissions and service operations.
Engagement paths
Two ways to run this workshop
Our team will use public, fictional or authorised scenarios. This is business and product education, not developer certification or regulatory training.
Standalone workshop
Use a business-design workshop to map one API-enabled proposition and the questions it raises for product, partners and operations.
Related