A cycle for defining and productizing reusable integration capabilities without assuming the implementation style in advance.
Guide reusable integration capability design before choosing an API, event, file, stream, data product, direct integration, or hybrid implementation style.
Method map
Navigate the method
Select a station, cycle, or stakeholder perspective to explore the method.
Capability opportunity is identified and documented.
Exit criteria
The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.
Integration contracts, schemas, mappings, test evidence, environments, permissions, credentials, monitoring, support, replay, reconciliation, fallback, recovery, risks, and ownership have been reviewed for release readiness.
The integration capability is discoverable with published ownership, lifecycle status, contracts, schemas, service expectations, access and onboarding paths, support, versioning, and feedback channels.
Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable integration capability should proceed.
Integration work often jumps too quickly to a technical pattern. This station keeps the team focused on consumer need, value, domain meaning, ownership, reuse potential, viability, assumptions, and validation before selecting APIs, events, files, streams, data products, direct integration, or hybrids.
Agree provider and consumer commitments for access, validation, service, failure handling, recovery, compatibility, and lifecycle.
The right architecture depends on consumer goals, onboarding expectations, service levels, data quality needs, change tolerance, observability, support, and producer constraints.
Select the integration architecture, implementation style, and platform capabilities, taking account of constraints and the governance model.
Architecture choices should follow from evidence about business impact, locations, trust boundaries, capacity, latency, data ownership, consistency, operability, security, privacy, governance, and cost.
Design the integration solution, contracts, schemas, data structures, mappings, and interaction or delivery patterns for the selected style.
Once the architecture pattern is known, the design must turn capability requirements into clear interface contracts, interactions, schemas, data rules, lifecycle expectations, and consumer obligations.
Build, test, deploy, and operate the integration capability using its selected implementation style and validated contract.
A reusable integration capability needs reliable delivery and operations regardless of whether it uses APIs, events, messages, files, streams, data products, connectors, or direct integration.
Assure integration readiness, governance, quality, security, compliance, and operational evidence before release.
A formal readiness decision prevents automation solutions from being released without clear evidence, accepted risks, remediation actions, and business and operational ownership.
Publish the integration capability so teams can discover it, evaluate it, request access, complete onboarding, reuse it, and get support.
Automation solutions only create value after rollout when affected people and consuming systems understand what changes, how access and operation work, where to get support, and when rollout should pause, expand, or roll back.
Released solutions need evidence to show whether expected outcomes are being achieved, where manual intervention or recovery is still needed, and what lifecycle decision should be made next.
Publish this cycle
Export the page-specific template after reviewing the entity summary and supporting details above.
Publishing
Markdown and Confluence export
Use Markdown for repositories and static sites, or Confluence-wiki markup for compatible Confluence pages.
Markdown
# Integration Productization Cycle question template
A cycle for defining and productizing reusable integration capabilities without assuming the implementation style in advance.
Use this template to gather answers and evidence station by station. Canvas section prompts are listed first, followed by other related resources.
## 1. Integration Capability Strategy
Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable integration capability should proceed.
### Canvas questions
#### Customer Journey Canvas
What journey does the most external meaningful customer experience, and what should improve?
- **Persona**: Who is the typical customer experiencing this journey?
- **Customer Discovers Need**: How does the customer recognize their need or problem?
- **Customer Need Is Resolved**: How is the customer's need ultimately resolved?
- **Journey Steps**: What are the steps the customer takes in their journey?
- **Pains**: What are the customer's pain points or challenges?
- **Gains**: What are the customer's gains or benefits?
- **Inputs & Outputs**: What are the inputs and outputs at each step?
- **Interaction & Processing Rules**: What are the interaction and processing rules at each step?
- **Improvement opportunities**: Which journey steps indicate that an underlying capability or process should be created, improved, automated, or removed?
#### Capability Value Proposition Canvas
Which reusable capability would create value for consumers without deciding yet whether it should be delivered as an API, event, file, stream, data product, or another implementation style?
- **Consumer tasks and outcomes**: What are consumers, partners, users, systems, or teams trying to achieve?
- **Gain-enabling capability features**: What capability features would help consumers achieve better outcomes, speed, automation, insight, reach, or compliance?
- **Pain-relieving capability features**: What capability features would remove friction, manual work, errors, delays, risk, or uncertainty for consumers?
- **Reusable capabilities**: What reusable business or data capabilities could serve these tasks, gains, and pains across more than one consumer or use case?
#### Capability Business Model Canvas
How viable, reusable, funded, owned, supported, and discoverable should this capability be?
- **Capability value proposition**: What value does this reusable capability provide to consumers and to the organization or ecosystem?
- **Capability consumer segments**: Who are the current and potential consumers of the capability, including teams, partners, systems, products, or data users?
- **Consumer engagement**: How will consumers discover, evaluate, request, onboard, get support for, and provide feedback on the capability?
- **Channels**: Through which catalogs, portals, marketplaces, documentation sites, support paths, or governance processes will consumers interact with the capability?
- **Key resources**: Which systems, data assets, platforms, people, standards, funding, and operational capabilities are required?
- **Key activities**: What must the capability owner and producers do to design, deliver, govern, support, and improve the capability?
- **Key partners**: Which business, technology, data, security, legal, platform, or external partners are needed to make the capability work?
- **Benefits**: What business, operational, ecosystem, reuse, compliance, or cost benefits justify the capability?
- **Costs**: What are the significant costs of building, operating, governing, supporting, and evolving the capability?
#### Integration Capability Validation Canvas
Validate whether a proposed reusable integration capability should proceed.
- **Capability to validate**: Which proposed integration capability and reuse scope are being tested?
- **Reused evidence**: Which earlier canvas outputs support the proposal?
- **Critical assumptions**: What could invalidate value, reuse, ownership, feasibility, or adoption?
- **Validation step**: What is the smallest useful validation and success threshold?
- **Decision**: Proceed, narrow, revise and retest, or stop?
### Before this station
- [ ] Business goals are defined.
- [ ] Capability opportunity is identified and documented.
### Ready to leave when
- [ ] Relevant market signals, feedback, or operational insights are available to guide this capability opportunity.
- [ ] Business goals are defined.
- [ ] Market research identifies capability opportunities.
- [ ] Relevant stakeholders agree this capability opportunity is worth exploring and prioritizing.
## 2. Integration Consumer & Provider Commitments
Agree provider and consumer commitments for access, validation, service, failure handling, recovery, compatibility, and lifecycle.
### Canvas questions
#### Integration Consumer & Provider Commitments Canvas
Agree the responsibilities needed to use and provide a reusable integration capability.
- **Selected parties and use cases**: Which producers, providers, consumers, and use cases are covered?
- **Provider commitments**: What will providers deliver, maintain, monitor, and support?
- **Consumer commitments**: What must consumers test, protect, operate, and communicate?
- **Access and validation**: How will access, environments, credentials, and conformance be handled?
- **Failure and recovery**: Who handles failures, replay, duplicates, reconciliation, and recovery?
- **Change and lifecycle**: How will compatibility, migration, notice, deprecation, and retirement work?
### Before this station
- [ ] Relevant market signals, feedback, or operational insights are available to guide this capability opportunity.
- [ ] Business goals are defined.
- [ ] Market research identifies capability opportunities.
- [ ] Relevant stakeholders agree this capability opportunity is worth exploring and prioritizing.
### Ready to leave when
- [ ] Capability opportunity is identified and documented.
- [ ] The capability addresses a clear business need and is reusable by its intended consumers.
- [ ] The selected interface provides an appropriate abstraction for consumers.
- [ ] The capability value proposition has been validated with business and consumer stakeholders.
- [ ] Consumer segments are identified.
- [ ] A high-level implementation roadmap is defined.
### Other related resources
- **Integration Consumer Onboarding Guide**: Guidance for helping consumer teams discover, request access to, test, validate, and start using an integration capability.
- **Integration Access and Environment Checklist**: A checklist for access requests, identities, credentials, certificates, sandbox, test, staging, production, partner, and recovery environments.
## 3. Integration Architecture & Platform Decisions
Select the integration architecture, implementation style, and platform capabilities, taking account of constraints and the governance model.
### Canvas questions
#### Business Impact Canvas
What value, risk, operational, financial, customer, employee, compliance, and strategic impact is expected or at stake?
- **Expected benefits**: What business, customer, employee, quality, speed, risk, compliance, or strategic benefits are expected?
- **Operational efficiency impact**: How could work effort, waiting time, rework, throughput, reliability, support load, or operational cost change?
- **Customer and employee impact**: How will customers, employees, partners, operators, or support teams experience the change?
- **Financial impact**: What revenue, cost, investment, savings, loss avoidance, or funding impact is expected?
- **Compliance and strategic impact**: What regulatory, contractual, policy, reputation, market, ecosystem, or strategic consequences matter?
- **Impact of not proceeding**: What happens if the capability, automation, integration, or service is not improved or delivered?
- **Risks and criticality**: What availability, security, data, safety, process, adoption, or business continuity risks could affect the outcome?
- **Mitigations and decision impact**: Which mitigations, constraints, trade-offs, or residual risks should influence prioritization, architecture, rollout, or readiness decisions?
#### Location Canvas
What geopolitical, regulatory, network, and trust boundaries affect this capability or integration?
- **Location / Trust Groups**: What are the relevant geopolitical, regulatory, network, or trust groups?
- **Group Characteristics**: What are the characteristics of those groups, such as residency, trust level, or network exposure?
- **Relevant Locations / Zones**: What are the relevant locations, zones, or environments within each group?
- **Location / Zone Characteristics**: What are the characteristics of those locations or zones, such as ownership, region, or exposure?
- **Network / Regulatory Distances**: What latency, trust, regulatory, or connectivity distances exist between the locations?
- **Distance Characteristics**: What are the characteristics of those distances, such as latency sensitivity, residency constraints, or trust boundaries?
- **Connectivity Endpoints**: What connectivity endpoints or interfaces are associated with the locations?
- **Endpoint Access Characteristics**: What are the characteristics of those endpoints, such as exposure, protocol, security, or access restrictions?
#### Capacity Canvas
How much demand, load, timing, and scaling capacity must be understood for the capability, automation, integration, or service?
- **Current Business Volumes**: What are the current business volumes and transaction rates?
- **Future Consumption Trends**: What are the anticipated future consumption trends?
- **Peak Load and Availability Requirements**: What are the peak load and availability requirements?
- **Caching Strategies**: What caching strategies can be used to optimize performance?
- **Rate Limiting Strategies**: What rate limiting strategies can be used to manage consumption?
- **Scaling Strategies**: What scaling strategies can be used to accommodate growth?
#### Integration Architecture Decision Canvas
Choose the integration style and platform using evidence already gathered.
- **Reused inputs**: Which commitments, capacity, location, impact, and domain decisions constrain the choice?
- **Viable options**: Which API, event, messaging, file, stream, data, connector, platform, or custom options remain viable?
- **Selected approach**: Which integration style, platform, or hybrid is selected?
- **Decision rationale**: Why does the selected approach fit best?
- **Rejected alternatives**: Which serious alternatives were rejected, and why?
- **Open risks**: What still needs validation before delivery or release?
### Before this station
- [ ] Capability opportunity is identified and documented.
- [ ] The capability addresses a clear business need and is reusable by its intended consumers.
- [ ] The selected interface provides an appropriate abstraction for consumers.
- [ ] The capability value proposition has been validated with business and consumer stakeholders.
- [ ] Consumer segments are identified.
- [ ] A high-level implementation roadmap is defined.
### Ready to leave when
- [ ] The capability addresses a clear business need and is reusable by its intended consumers.
- [ ] The selected interface provides an appropriate abstraction for consumers.
- [ ] The capability value proposition has been validated with business and consumer stakeholders.
- [ ] Consumer segments are identified.
- [ ] A high-level implementation roadmap is defined.
## 4. Integration Solution Design
Design the integration solution, contracts, schemas, data structures, mappings, and interaction or delivery patterns for the selected style.
### Canvas questions
#### Domain Canvas
What are the core entities and business rules related to this capability or domain?
- **Selected Customer Journey Steps**: Which customer journey steps are relevant to this domain?
- **Core Entities & Business Meaning**: What are the core entities and their business meaning?
- **Attributes & Business Importance**: What are the key attributes of each entity and their business importance?
- **Relationships Between Entities**: What are the relationships between the entities?
- **Business, Compliance & Integrity Rules**: What are the business, compliance, and integrity rules related to the entities?
- **Security & Privacy Considerations**: What are the security and privacy considerations related to the entities?
#### Integration Solution Design Canvas
Refine the selected architecture into an implementable integration design.
- **Selected inputs**: Which architecture, domain, interaction, and commitment decisions are reused?
- **Contract and model**: What contract, schema, data model, and version define the integration?
- **Mapping and delivery**: What transformations, delivery pattern, and metadata are required?
- **Errors and recovery**: How are failures, retries, replay, duplicates, and reconciliation handled?
- **Security and trust**: What identity, access, privacy, and trust controls apply?
- **Observability and evolution**: How will the integration be monitored, changed, migrated, and deprecated?
#### Interaction Canvas
What kinds of interactions should this capability support before choosing a protocol-specific design?
- **CRUD Interactions**: Are CRUD (Create, Read, Update, Delete) interactions needed here?
- **CRUD Input & Output Models**: What are the input and output models for the CRUD interactions, if this style is needed?
- **CRUD Processing & Validation**: What are the processing and validation rules for the CRUD interactions, if this style is needed?
- **Query-Driven Interactions**: What read or query interactions are needed to answer consumer questions?
- **Query-Driven Input & Output Models**: What are the input and output models for the query-driven interactions?
- **Query-Driven Processing & Validation**: What are the processing and validation rules for the query-driven interactions?
- **Command-Driven Interactions**: What state-changing commands are needed, if any?
- **Command-Driven Input & Output Models**: What are the input and output models for the command-driven interactions, if this style is needed?
- **Command-Driven Processing & Validation**: What are the processing and validation rules for the command-driven interactions, if this style is needed?
- **Event-Driven Interactions**: What events need to be published or consumed, if any?
- **Event-Driven Input & Output Models**: What are the input and output models for the event-driven interactions, if this style is needed?
- **Event-Driven Processing & Validation**: What are the processing and validation rules for the event-driven interactions, if this style is needed?
### Before this station
- [ ] The capability addresses a clear business need and is reusable by its intended consumers.
- [ ] The selected interface provides an appropriate abstraction for consumers.
- [ ] The capability value proposition has been validated with business and consumer stakeholders.
- [ ] Consumer segments are identified.
- [ ] A high-level implementation roadmap is defined.
### Ready to leave when
- [ ] The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.
- [ ] The selected interface provides an appropriate abstraction for consumers.
- [ ] The interface design and exposed capabilities trace back to business value and consumer needs.
- [ ] The interface design follows agreed design standards and conventions.
### Other related resources
- **Contract-First Capability Design**: Guidance for validating capability contracts before delivery, including API contracts, event schemas, file schemas, data contracts, service agreements, workflow inputs and outputs, and user-facing service promises.
- **Integration Style-Specific Design Guide**: Guidance for selecting design resources after the architecture decision, including REST, GraphQL, events, messaging, files, streams, data products, direct integration, connectors, and hybrids.
## 5. Integration Delivery & Operations
Build, test, deploy, and operate the integration capability using its selected implementation style and validated contract.
### Canvas questions
#### Integration Readiness & Operations Canvas
Prepare the minimum operating evidence needed before integration readiness review.
- **Ownership**: Who owns business, integration, producer, consumer, platform, and incident responsibilities?
- **Environments and access**: Are environments, credentials, connectivity, permissions, and sequencing ready?
- **Test evidence**: What proves contract, mapping, compatibility, quality, resilience, and recovery?
- **Monitoring and support**: How will producers, consumers, platforms, incidents, and service questions be supported?
- **Failure and recovery**: How will retry, replay, duplicates, reconciliation, fallback, and compensation work?
- **Readiness status**: Are contracts, runbooks, dependencies, risks, conditions, and blocking gaps clear?
### Before this station
- [ ] The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.
- [ ] The selected interface provides an appropriate abstraction for consumers.
- [ ] The interface design and exposed capabilities trace back to business value and consumer needs.
- [ ] The interface design follows agreed design standards and conventions.
### Ready to leave when
- [ ] The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.
- [ ] The selected interface provides an appropriate abstraction for consumers.
- [ ] The interface design and exposed capabilities trace back to business value and consumer needs.
- [ ] The interface design follows agreed design standards and conventions.
### Other related resources
- **Integration Development Best Practices**: Implementation guidance for building integration capabilities from validated contracts using maintainable code, configuration, connectors, mappings, and platform patterns.
- **Integration Testing Guide**: Guidance for testing integration contracts, schemas, mappings, compatibility, data quality, security, performance, resilience, replay, reconciliation, and recovery.
- **Integration CI/CD and Deployment Guide**: Guidance for automating build, validation, deployment, configuration, migration, release, rollback, and traceability for integration capabilities.
- **Integration Security Guide**: Guidance for protecting integration identities, credentials, data, trust boundaries, access, privacy, auditability, and platform controls.
- **Integration Recovery and Reconciliation Guide**: Guidance for retry, replay, duplicate handling, ordering, dead-lettering, restartability, reconciliation, fallback, compensation, and rollback.
## 6. Integration Readiness Assurance
Assure integration readiness, governance, quality, security, compliance, and operational evidence before release.
### Station questions
- Review the completed design, test evidence, operating model, permissions, credentials, monitoring, support, fallback, and rollback arrangements.
- Verify that known risks, exceptions, unsafe actions, human oversight, compliance requirements, and unresolved assumptions have been addressed or explicitly accepted.
- Record blocking findings, accepted residual risks, release conditions, and required remediation actions.
- Decide whether the release is ready, ready with conditions, requires remediation, or is not approved.
- Record the decision owner, decision date, and evidence used.
- Confirm that nothing proceeds to release without clear business and operational ownership.
- Use readiness evidence to make an explicit go, conditional-go, or no-go decision before production use.
- A formal readiness decision prevents automation solutions from being released without clear evidence, accepted risks, remediation actions, and business and operational ownership.
### Before this station
- [ ] The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.
- [ ] The selected interface provides an appropriate abstraction for consumers.
- [ ] The interface design and exposed capabilities trace back to business value and consumer needs.
- [ ] The interface design follows agreed design standards and conventions.
### Ready to leave when
- [ ] The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.
- [ ] The interface design and exposed capabilities trace back to business value and consumer needs.
- [ ] The interface and its capabilities are documented clearly enough for review, audit, and onboarding.
- [ ] The interface design follows agreed design standards and conventions.
- [ ] The interface contract has been validated and tested against functional and non-functional requirements.
### Other related resources
- **Integration Readiness Checklist**: A checklist for release readiness across contracts, schemas, mappings, test evidence, environments, permissions, credentials, monitoring, support, replay, reconciliation, fallback, recovery, risks, and ownership.
- **Integration Compliance and Data Governance Guide**: Guidance for privacy, retention, residency, consent, lineage, ownership, data contracts, auditability, regulatory obligations, and policy controls in integrations.
## 7. Integration Publishing & Enablement
Publish the integration capability so teams can discover it, evaluate it, request access, complete onboarding, reuse it, and get support.
### Station questions
- Affected people and changed work: Who will use, operate, support, approve, consume, or be affected by the release, and what responsibilities, decisions, handoffs, or working practices will change?
- Activation and rollout approach: How will access, permissions, pilot use, phased rollout, restricted groups, parallel operation, and rollout expansion be managed?
- Enablement and support: What communication, training, operating instructions, and support paths are required?
- Feedback and control: How will adoption, trust, actual use, issues, and unexpected behavior be monitored, and what conditions trigger pause, rollback, or return to manual operation?
- Plan rollout, enablement, support, feedback, and rollback so released solutions can be adopted safely.
- Automation solutions only create value after rollout when affected people and consuming systems understand what changes, how access and operation work, where to get support, and when rollout should pause, expand, or roll back.
### Before this station
- [ ] The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.
- [ ] The interface design and exposed capabilities trace back to business value and consumer needs.
- [ ] The interface and its capabilities are documented clearly enough for review, audit, and onboarding.
- [ ] The interface design follows agreed design standards and conventions.
- [ ] The interface contract has been validated and tested against functional and non-functional requirements.
### Ready to leave when
- [ ] The solution passes quality, security, compliance, and readiness checks.
- [ ] Audit findings and remediation decisions are shared with the relevant stakeholders.
- [ ] The capability is ready to be published or released through the selected delivery mechanism.
- [ ] Consumer-facing documentation and onboarding materials are ready.
### Other related resources
- **Integration Publishing and Discovery Guide**: Guidance for publishing integration purpose, ownership, lifecycle status, contracts, schemas, service expectations, dependencies, examples, limitations, access paths, and support information.
- **Integration Consumer Onboarding Guide**: Guidance for helping consumer teams discover, request access to, test, validate, and start using an integration capability.
- **Integration Service Agreement Template**: A template for documenting service expectations, ownership, support, incident communication, availability, latency, throughput, data quality, change, and recovery commitments.
- **Integration Versioning and Deprecation Guide**: Guidance for compatibility, versioning, migration, deprecation, retirement, change notice, consumer impact, and lifecycle communication.
## 8. Integration Monitoring & Improvement
Monitor integration reliability, reuse, incidents, performance, consumer outcomes, and improvement needs.
### Station questions
- Outcomes and value: Are the expected process, user, and business outcomes being achieved?
- Operational performance: What do successful runs, failures, partial completions, exceptions, retries, timeouts, interventions, processing time, waiting time, and cost show?
- User, risk, and recovery signals: What errors, corrections, unsafe actions, bypassing, mistrust, support needs, fallback events, or recovery failures are occurring?
- Learning and lifecycle decision: Which hypothesis assumptions were supported or rejected, and should the solution be improved, expanded, restricted, redesigned, paused, or retired?
- Use operational, user, risk, and value evidence to decide what to improve, expand, restrict, pause, or retire.
- Released solutions need evidence to show whether expected outcomes are being achieved, where manual intervention or recovery is still needed, and what lifecycle decision should be made next.
### Before this station
- [ ] The solution passes quality, security, compliance, and readiness checks.
- [ ] Audit findings and remediation decisions are shared with the relevant stakeholders.
- [ ] The capability is ready to be published or released through the selected delivery mechanism.
- [ ] Consumer-facing documentation and onboarding materials are ready.
### Ready to leave when
- [ ] Consumer-facing documentation and onboarding materials are ready.
- [ ] Consumer onboarding, support, and communication processes are ready.
- [ ] Legal, privacy, and compliance requirements for publishing or release are defined and understood.
### Other related resources
- **Integration Monitoring and Value Metrics**: Guidance for monitoring reliability, performance, capacity, data quality, consumer experience, reuse, cost, operability, value, learning, and lifecycle decisions.
- **Integration Consumer Feedback and Adoption Guide**: Guidance for collecting consumer feedback, onboarding friction, support needs, adoption evidence, reuse patterns, and improvement requests.
- **Integration Reliability and Data Quality Metrics**: Guidance for measuring availability, success rate, failure rate, retries, dead-lettering, replay, duplication, ordering, latency, throughput, queue depth, stream lag, batch duration, file delivery, schema violations, mapping errors, missing data, and reconciliation differences.
- **Integration Lifecycle Management Guide**: Guidance for lifecycle decisions such as improve, scale, standardize, consolidate, version, deprecate, replace, retire, or split an integration capability.
Confluence-wiki
h1. Integration Productization Cycle question template
A cycle for defining and productizing reusable integration capabilities without assuming the implementation style in advance.
Use this template to gather answers and evidence station by station. Canvas section prompts are listed first, followed by other related resources.
h2. 1. Integration Capability Strategy
Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable integration capability should proceed.
h3. Canvas questions
h4. Customer Journey Canvas
What journey does the most external meaningful customer experience, and what should improve?
* *Persona*: Who is the typical customer experiencing this journey?
* *Customer Discovers Need*: How does the customer recognize their need or problem?
* *Customer Need Is Resolved*: How is the customer's need ultimately resolved?
* *Journey Steps*: What are the steps the customer takes in their journey?
* *Pains*: What are the customer's pain points or challenges?
* *Gains*: What are the customer's gains or benefits?
* *Inputs & Outputs*: What are the inputs and outputs at each step?
* *Interaction & Processing Rules*: What are the interaction and processing rules at each step?
* *Improvement opportunities*: Which journey steps indicate that an underlying capability or process should be created, improved, automated, or removed?
h4. Capability Value Proposition Canvas
Which reusable capability would create value for consumers without deciding yet whether it should be delivered as an API, event, file, stream, data product, or another implementation style?
* *Consumer tasks and outcomes*: What are consumers, partners, users, systems, or teams trying to achieve?
* *Gain-enabling capability features*: What capability features would help consumers achieve better outcomes, speed, automation, insight, reach, or compliance?
* *Pain-relieving capability features*: What capability features would remove friction, manual work, errors, delays, risk, or uncertainty for consumers?
* *Reusable capabilities*: What reusable business or data capabilities could serve these tasks, gains, and pains across more than one consumer or use case?
h4. Capability Business Model Canvas
How viable, reusable, funded, owned, supported, and discoverable should this capability be?
* *Capability value proposition*: What value does this reusable capability provide to consumers and to the organization or ecosystem?
* *Capability consumer segments*: Who are the current and potential consumers of the capability, including teams, partners, systems, products, or data users?
* *Consumer engagement*: How will consumers discover, evaluate, request, onboard, get support for, and provide feedback on the capability?
* *Channels*: Through which catalogs, portals, marketplaces, documentation sites, support paths, or governance processes will consumers interact with the capability?
* *Key resources*: Which systems, data assets, platforms, people, standards, funding, and operational capabilities are required?
* *Key activities*: What must the capability owner and producers do to design, deliver, govern, support, and improve the capability?
* *Key partners*: Which business, technology, data, security, legal, platform, or external partners are needed to make the capability work?
* *Benefits*: What business, operational, ecosystem, reuse, compliance, or cost benefits justify the capability?
* *Costs*: What are the significant costs of building, operating, governing, supporting, and evolving the capability?
h4. Integration Capability Validation Canvas
Validate whether a proposed reusable integration capability should proceed.
* *Capability to validate*: Which proposed integration capability and reuse scope are being tested?
* *Reused evidence*: Which earlier canvas outputs support the proposal?
* *Critical assumptions*: What could invalidate value, reuse, ownership, feasibility, or adoption?
* *Validation step*: What is the smallest useful validation and success threshold?
* *Decision*: Proceed, narrow, revise and retest, or stop?
h3. Before this station
* [ ] Business goals are defined.
* [ ] Capability opportunity is identified and documented.
h3. Ready to leave when
* [ ] Relevant market signals, feedback, or operational insights are available to guide this capability opportunity.
* [ ] Business goals are defined.
* [ ] Market research identifies capability opportunities.
* [ ] Relevant stakeholders agree this capability opportunity is worth exploring and prioritizing.
h2. 2. Integration Consumer & Provider Commitments
Agree provider and consumer commitments for access, validation, service, failure handling, recovery, compatibility, and lifecycle.
h3. Canvas questions
h4. Integration Consumer & Provider Commitments Canvas
Agree the responsibilities needed to use and provide a reusable integration capability.
* *Selected parties and use cases*: Which producers, providers, consumers, and use cases are covered?
* *Provider commitments*: What will providers deliver, maintain, monitor, and support?
* *Consumer commitments*: What must consumers test, protect, operate, and communicate?
* *Access and validation*: How will access, environments, credentials, and conformance be handled?
* *Failure and recovery*: Who handles failures, replay, duplicates, reconciliation, and recovery?
* *Change and lifecycle*: How will compatibility, migration, notice, deprecation, and retirement work?
h3. Before this station
* [ ] Relevant market signals, feedback, or operational insights are available to guide this capability opportunity.
* [ ] Business goals are defined.
* [ ] Market research identifies capability opportunities.
* [ ] Relevant stakeholders agree this capability opportunity is worth exploring and prioritizing.
h3. Ready to leave when
* [ ] Capability opportunity is identified and documented.
* [ ] The capability addresses a clear business need and is reusable by its intended consumers.
* [ ] The selected interface provides an appropriate abstraction for consumers.
* [ ] The capability value proposition has been validated with business and consumer stakeholders.
* [ ] Consumer segments are identified.
* [ ] A high-level implementation roadmap is defined.
h3. Other related resources
* *Integration Consumer Onboarding Guide*: Guidance for helping consumer teams discover, request access to, test, validate, and start using an integration capability.
* *Integration Access and Environment Checklist*: A checklist for access requests, identities, credentials, certificates, sandbox, test, staging, production, partner, and recovery environments.
h2. 3. Integration Architecture & Platform Decisions
Select the integration architecture, implementation style, and platform capabilities, taking account of constraints and the governance model.
h3. Canvas questions
h4. Business Impact Canvas
What value, risk, operational, financial, customer, employee, compliance, and strategic impact is expected or at stake?
* *Expected benefits*: What business, customer, employee, quality, speed, risk, compliance, or strategic benefits are expected?
* *Operational efficiency impact*: How could work effort, waiting time, rework, throughput, reliability, support load, or operational cost change?
* *Customer and employee impact*: How will customers, employees, partners, operators, or support teams experience the change?
* *Financial impact*: What revenue, cost, investment, savings, loss avoidance, or funding impact is expected?
* *Compliance and strategic impact*: What regulatory, contractual, policy, reputation, market, ecosystem, or strategic consequences matter?
* *Impact of not proceeding*: What happens if the capability, automation, integration, or service is not improved or delivered?
* *Risks and criticality*: What availability, security, data, safety, process, adoption, or business continuity risks could affect the outcome?
* *Mitigations and decision impact*: Which mitigations, constraints, trade-offs, or residual risks should influence prioritization, architecture, rollout, or readiness decisions?
h4. Location Canvas
What geopolitical, regulatory, network, and trust boundaries affect this capability or integration?
* *Location / Trust Groups*: What are the relevant geopolitical, regulatory, network, or trust groups?
* *Group Characteristics*: What are the characteristics of those groups, such as residency, trust level, or network exposure?
* *Relevant Locations / Zones*: What are the relevant locations, zones, or environments within each group?
* *Location / Zone Characteristics*: What are the characteristics of those locations or zones, such as ownership, region, or exposure?
* *Network / Regulatory Distances*: What latency, trust, regulatory, or connectivity distances exist between the locations?
* *Distance Characteristics*: What are the characteristics of those distances, such as latency sensitivity, residency constraints, or trust boundaries?
* *Connectivity Endpoints*: What connectivity endpoints or interfaces are associated with the locations?
* *Endpoint Access Characteristics*: What are the characteristics of those endpoints, such as exposure, protocol, security, or access restrictions?
h4. Capacity Canvas
How much demand, load, timing, and scaling capacity must be understood for the capability, automation, integration, or service?
* *Current Business Volumes*: What are the current business volumes and transaction rates?
* *Future Consumption Trends*: What are the anticipated future consumption trends?
* *Peak Load and Availability Requirements*: What are the peak load and availability requirements?
* *Caching Strategies*: What caching strategies can be used to optimize performance?
* *Rate Limiting Strategies*: What rate limiting strategies can be used to manage consumption?
* *Scaling Strategies*: What scaling strategies can be used to accommodate growth?
h4. Integration Architecture Decision Canvas
Choose the integration style and platform using evidence already gathered.
* *Reused inputs*: Which commitments, capacity, location, impact, and domain decisions constrain the choice?
* *Viable options*: Which API, event, messaging, file, stream, data, connector, platform, or custom options remain viable?
* *Selected approach*: Which integration style, platform, or hybrid is selected?
* *Decision rationale*: Why does the selected approach fit best?
* *Rejected alternatives*: Which serious alternatives were rejected, and why?
* *Open risks*: What still needs validation before delivery or release?
h3. Before this station
* [ ] Capability opportunity is identified and documented.
* [ ] The capability addresses a clear business need and is reusable by its intended consumers.
* [ ] The selected interface provides an appropriate abstraction for consumers.
* [ ] The capability value proposition has been validated with business and consumer stakeholders.
* [ ] Consumer segments are identified.
* [ ] A high-level implementation roadmap is defined.
h3. Ready to leave when
* [ ] The capability addresses a clear business need and is reusable by its intended consumers.
* [ ] The selected interface provides an appropriate abstraction for consumers.
* [ ] The capability value proposition has been validated with business and consumer stakeholders.
* [ ] Consumer segments are identified.
* [ ] A high-level implementation roadmap is defined.
h2. 4. Integration Solution Design
Design the integration solution, contracts, schemas, data structures, mappings, and interaction or delivery patterns for the selected style.
h3. Canvas questions
h4. Domain Canvas
What are the core entities and business rules related to this capability or domain?
* *Selected Customer Journey Steps*: Which customer journey steps are relevant to this domain?
* *Core Entities & Business Meaning*: What are the core entities and their business meaning?
* *Attributes & Business Importance*: What are the key attributes of each entity and their business importance?
* *Relationships Between Entities*: What are the relationships between the entities?
* *Business, Compliance & Integrity Rules*: What are the business, compliance, and integrity rules related to the entities?
* *Security & Privacy Considerations*: What are the security and privacy considerations related to the entities?
h4. Integration Solution Design Canvas
Refine the selected architecture into an implementable integration design.
* *Selected inputs*: Which architecture, domain, interaction, and commitment decisions are reused?
* *Contract and model*: What contract, schema, data model, and version define the integration?
* *Mapping and delivery*: What transformations, delivery pattern, and metadata are required?
* *Errors and recovery*: How are failures, retries, replay, duplicates, and reconciliation handled?
* *Security and trust*: What identity, access, privacy, and trust controls apply?
* *Observability and evolution*: How will the integration be monitored, changed, migrated, and deprecated?
h4. Interaction Canvas
What kinds of interactions should this capability support before choosing a protocol-specific design?
* *CRUD Interactions*: Are CRUD (Create, Read, Update, Delete) interactions needed here?
* *CRUD Input & Output Models*: What are the input and output models for the CRUD interactions, if this style is needed?
* *CRUD Processing & Validation*: What are the processing and validation rules for the CRUD interactions, if this style is needed?
* *Query-Driven Interactions*: What read or query interactions are needed to answer consumer questions?
* *Query-Driven Input & Output Models*: What are the input and output models for the query-driven interactions?
* *Query-Driven Processing & Validation*: What are the processing and validation rules for the query-driven interactions?
* *Command-Driven Interactions*: What state-changing commands are needed, if any?
* *Command-Driven Input & Output Models*: What are the input and output models for the command-driven interactions, if this style is needed?
* *Command-Driven Processing & Validation*: What are the processing and validation rules for the command-driven interactions, if this style is needed?
* *Event-Driven Interactions*: What events need to be published or consumed, if any?
* *Event-Driven Input & Output Models*: What are the input and output models for the event-driven interactions, if this style is needed?
* *Event-Driven Processing & Validation*: What are the processing and validation rules for the event-driven interactions, if this style is needed?
h3. Before this station
* [ ] The capability addresses a clear business need and is reusable by its intended consumers.
* [ ] The selected interface provides an appropriate abstraction for consumers.
* [ ] The capability value proposition has been validated with business and consumer stakeholders.
* [ ] Consumer segments are identified.
* [ ] A high-level implementation roadmap is defined.
h3. Ready to leave when
* [ ] The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.
* [ ] The selected interface provides an appropriate abstraction for consumers.
* [ ] The interface design and exposed capabilities trace back to business value and consumer needs.
* [ ] The interface design follows agreed design standards and conventions.
h3. Other related resources
* *Contract-First Capability Design*: Guidance for validating capability contracts before delivery, including API contracts, event schemas, file schemas, data contracts, service agreements, workflow inputs and outputs, and user-facing service promises.
* *Integration Style-Specific Design Guide*: Guidance for selecting design resources after the architecture decision, including REST, GraphQL, events, messaging, files, streams, data products, direct integration, connectors, and hybrids.
h2. 5. Integration Delivery & Operations
Build, test, deploy, and operate the integration capability using its selected implementation style and validated contract.
h3. Canvas questions
h4. Integration Readiness & Operations Canvas
Prepare the minimum operating evidence needed before integration readiness review.
* *Ownership*: Who owns business, integration, producer, consumer, platform, and incident responsibilities?
* *Environments and access*: Are environments, credentials, connectivity, permissions, and sequencing ready?
* *Test evidence*: What proves contract, mapping, compatibility, quality, resilience, and recovery?
* *Monitoring and support*: How will producers, consumers, platforms, incidents, and service questions be supported?
* *Failure and recovery*: How will retry, replay, duplicates, reconciliation, fallback, and compensation work?
* *Readiness status*: Are contracts, runbooks, dependencies, risks, conditions, and blocking gaps clear?
h3. Before this station
* [ ] The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.
* [ ] The selected interface provides an appropriate abstraction for consumers.
* [ ] The interface design and exposed capabilities trace back to business value and consumer needs.
* [ ] The interface design follows agreed design standards and conventions.
h3. Ready to leave when
* [ ] The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.
* [ ] The selected interface provides an appropriate abstraction for consumers.
* [ ] The interface design and exposed capabilities trace back to business value and consumer needs.
* [ ] The interface design follows agreed design standards and conventions.
h3. Other related resources
* *Integration Development Best Practices*: Implementation guidance for building integration capabilities from validated contracts using maintainable code, configuration, connectors, mappings, and platform patterns.
* *Integration Testing Guide*: Guidance for testing integration contracts, schemas, mappings, compatibility, data quality, security, performance, resilience, replay, reconciliation, and recovery.
* *Integration CI/CD and Deployment Guide*: Guidance for automating build, validation, deployment, configuration, migration, release, rollback, and traceability for integration capabilities.
* *Integration Security Guide*: Guidance for protecting integration identities, credentials, data, trust boundaries, access, privacy, auditability, and platform controls.
* *Integration Recovery and Reconciliation Guide*: Guidance for retry, replay, duplicate handling, ordering, dead-lettering, restartability, reconciliation, fallback, compensation, and rollback.
h2. 6. Integration Readiness Assurance
Assure integration readiness, governance, quality, security, compliance, and operational evidence before release.
h3. Station questions
* Review the completed design, test evidence, operating model, permissions, credentials, monitoring, support, fallback, and rollback arrangements.
* Verify that known risks, exceptions, unsafe actions, human oversight, compliance requirements, and unresolved assumptions have been addressed or explicitly accepted.
* Record blocking findings, accepted residual risks, release conditions, and required remediation actions.
* Decide whether the release is ready, ready with conditions, requires remediation, or is not approved.
* Record the decision owner, decision date, and evidence used.
* Confirm that nothing proceeds to release without clear business and operational ownership.
* Use readiness evidence to make an explicit go, conditional-go, or no-go decision before production use.
* A formal readiness decision prevents automation solutions from being released without clear evidence, accepted risks, remediation actions, and business and operational ownership.
h3. Before this station
* [ ] The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.
* [ ] The selected interface provides an appropriate abstraction for consumers.
* [ ] The interface design and exposed capabilities trace back to business value and consumer needs.
* [ ] The interface design follows agreed design standards and conventions.
h3. Ready to leave when
* [ ] The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.
* [ ] The interface design and exposed capabilities trace back to business value and consumer needs.
* [ ] The interface and its capabilities are documented clearly enough for review, audit, and onboarding.
* [ ] The interface design follows agreed design standards and conventions.
* [ ] The interface contract has been validated and tested against functional and non-functional requirements.
h3. Other related resources
* *Integration Readiness Checklist*: A checklist for release readiness across contracts, schemas, mappings, test evidence, environments, permissions, credentials, monitoring, support, replay, reconciliation, fallback, recovery, risks, and ownership.
* *Integration Compliance and Data Governance Guide*: Guidance for privacy, retention, residency, consent, lineage, ownership, data contracts, auditability, regulatory obligations, and policy controls in integrations.
h2. 7. Integration Publishing & Enablement
Publish the integration capability so teams can discover it, evaluate it, request access, complete onboarding, reuse it, and get support.
h3. Station questions
* Affected people and changed work: Who will use, operate, support, approve, consume, or be affected by the release, and what responsibilities, decisions, handoffs, or working practices will change?
* Activation and rollout approach: How will access, permissions, pilot use, phased rollout, restricted groups, parallel operation, and rollout expansion be managed?
* Enablement and support: What communication, training, operating instructions, and support paths are required?
* Feedback and control: How will adoption, trust, actual use, issues, and unexpected behavior be monitored, and what conditions trigger pause, rollback, or return to manual operation?
* Plan rollout, enablement, support, feedback, and rollback so released solutions can be adopted safely.
* Automation solutions only create value after rollout when affected people and consuming systems understand what changes, how access and operation work, where to get support, and when rollout should pause, expand, or roll back.
h3. Before this station
* [ ] The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.
* [ ] The interface design and exposed capabilities trace back to business value and consumer needs.
* [ ] The interface and its capabilities are documented clearly enough for review, audit, and onboarding.
* [ ] The interface design follows agreed design standards and conventions.
* [ ] The interface contract has been validated and tested against functional and non-functional requirements.
h3. Ready to leave when
* [ ] The solution passes quality, security, compliance, and readiness checks.
* [ ] Audit findings and remediation decisions are shared with the relevant stakeholders.
* [ ] The capability is ready to be published or released through the selected delivery mechanism.
* [ ] Consumer-facing documentation and onboarding materials are ready.
h3. Other related resources
* *Integration Publishing and Discovery Guide*: Guidance for publishing integration purpose, ownership, lifecycle status, contracts, schemas, service expectations, dependencies, examples, limitations, access paths, and support information.
* *Integration Consumer Onboarding Guide*: Guidance for helping consumer teams discover, request access to, test, validate, and start using an integration capability.
* *Integration Service Agreement Template*: A template for documenting service expectations, ownership, support, incident communication, availability, latency, throughput, data quality, change, and recovery commitments.
* *Integration Versioning and Deprecation Guide*: Guidance for compatibility, versioning, migration, deprecation, retirement, change notice, consumer impact, and lifecycle communication.
h2. 8. Integration Monitoring & Improvement
Monitor integration reliability, reuse, incidents, performance, consumer outcomes, and improvement needs.
h3. Station questions
* Outcomes and value: Are the expected process, user, and business outcomes being achieved?
* Operational performance: What do successful runs, failures, partial completions, exceptions, retries, timeouts, interventions, processing time, waiting time, and cost show?
* User, risk, and recovery signals: What errors, corrections, unsafe actions, bypassing, mistrust, support needs, fallback events, or recovery failures are occurring?
* Learning and lifecycle decision: Which hypothesis assumptions were supported or rejected, and should the solution be improved, expanded, restricted, redesigned, paused, or retired?
* Use operational, user, risk, and value evidence to decide what to improve, expand, restrict, pause, or retire.
* Released solutions need evidence to show whether expected outcomes are being achieved, where manual intervention or recovery is still needed, and what lifecycle decision should be made next.
h3. Before this station
* [ ] The solution passes quality, security, compliance, and readiness checks.
* [ ] Audit findings and remediation decisions are shared with the relevant stakeholders.
* [ ] The capability is ready to be published or released through the selected delivery mechanism.
* [ ] Consumer-facing documentation and onboarding materials are ready.
h3. Ready to leave when
* [ ] Consumer-facing documentation and onboarding materials are ready.
* [ ] Consumer onboarding, support, and communication processes are ready.
* [ ] Legal, privacy, and compliance requirements for publishing or release are defined and understood.
h3. Other related resources
* *Integration Monitoring and Value Metrics*: Guidance for monitoring reliability, performance, capacity, data quality, consumer experience, reuse, cost, operability, value, learning, and lifecycle decisions.
* *Integration Consumer Feedback and Adoption Guide*: Guidance for collecting consumer feedback, onboarding friction, support needs, adoption evidence, reuse patterns, and improvement requests.
* *Integration Reliability and Data Quality Metrics*: Guidance for measuring availability, success rate, failure rate, retries, dead-lettering, replay, duplication, ordering, latency, throughput, queue depth, stream lag, batch duration, file delivery, schema violations, mapping errors, missing data, and reconciliation differences.
* *Integration Lifecycle Management Guide*: Guidance for lifecycle decisions such as improve, scale, standardize, consolidate, version, deprecate, replace, retire, or split an integration capability.