# Integration Capability Strategy — Integration Productization Cycle

Canonical page: https://apiopscycles.com/cycles/integration-productization-cycle/stations/api-product-strategy

Language: en

Entity ID: api-product-strategy

Cycle: [Integration Productization Cycle](https://apiopscycles.com/cycles/integration-productization-cycle.md)

Read [shared station guidance](https://apiopscycles.com/stations/api-product-strategy.md) first. The sections below supplement or replace the corresponding shared sections for this cycle. Sections not repeated here retain the shared guidance.

## Journey entry criteria

- Business goals are defined. (ID: business-goals-defined)
- Capability opportunity is identified and documented. — Individual API opportunities are identified and documented. (ID: api-opportunity-documented)

## Journey exit criteria

- Relevant market signals, feedback, or operational insights are available to guide this capability opportunity. — Relevant market signals, feedback, or operational insights are available to guide this API opportunity. (ID: metrics-feedback-available)
- Business goals are defined. (ID: business-goals-defined)
- Market research identifies capability opportunities. — Market research identifies API opportunities. (ID: market-research-done)
- Relevant stakeholders agree this capability opportunity is worth exploring and prioritizing. — Relevant stakeholders agree this API opportunity is worth exploring and prioritizing. (ID: stakeholder-approval)

## Description

Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable integration capability should proceed.

## Role participation and responsibilities

- [Integration Architect](https://apiopscycles.com/roles/integration-architect.md) (lead): Designs integration approaches and implementation styles that connect the capability or API with other systems.; suggested-answer-owner: [Integration Capability Validation Canvas](https://apiopscycles.com/resources/integration-capability-hypothesis-canvas.md)
- [Business Owner](https://apiopscycles.com/roles/business-owner.md) (core): Represents business goals, funding, and expected outcomes for the capability, API, or automation initiative.
- [Capability Owner](https://apiopscycles.com/roles/capability-owner.md) (core): Owns the capability vision, value, priorities, lifecycle, and reuse across consumers.
- [Domain Expert](https://apiopscycles.com/roles/domain-specialist.md) (core): Brings deep knowledge of the business domain, concepts, rules, and constraints the capability or interface must reflect.
- [Platform Owner](https://apiopscycles.com/roles/platform-owner.md) (core): Owns platform capabilities, roadmap, operational model, and service expectations.
- [API Product Owner](https://apiopscycles.com/roles/api-product-owner.md) (consulted): Drives the API opportunity, prioritization, and product-level decisions across the lifecycle.
- [Partner or Vendor Manager](https://apiopscycles.com/roles/partner-specialist.md) (consulted): Coordinates external partner, supplier, or vendor relationships that influence capability or API strategy and delivery.

## Resources

- [Customer Journey Canvas](https://apiopscycles.com/resources/customer-journey-canvas.md)
- [Capability Value Proposition Canvas](https://apiopscycles.com/resources/capability-value-proposition-canvas.md)
- [Capability Business Model Canvas](https://apiopscycles.com/resources/capability-business-model-canvas.md)
- [Integration Capability Validation Canvas](https://apiopscycles.com/resources/integration-capability-hypothesis-canvas.md)