# Capability Strategy — Capability Productization Cycle

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

Language: en

Entity ID: api-product-strategy

Cycle: [Capability Productization Cycle](https://apiopscycles.com/cycles/capability-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)
- 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)

## 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 digital capability should proceed.

## Role participation and responsibilities

- [Capability Owner](https://apiopscycles.com/roles/capability-owner.md) (lead): Owns the capability vision, value, priorities, lifecycle, and reuse across consumers.; suggested-answer-owner: [Capability Validation Canvas](https://apiopscycles.com/resources/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.
- [Customer or Partner Representative](https://apiopscycles.com/roles/customer-specialist.md) (core): Contributes the business customer or partner perspective for the journey, value, and collaboration model.
- [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.
- API Program Owner (consulted): Coordinates API portfolio practices, organizational alignment, and long-term API capability development.
- [Compliance and Legal Specialist](https://apiopscycles.com/roles/compliance-specialist.md) (consulted): Clarifies legal, privacy, regulatory, and contractual requirements that affect the capability, API, interface, or automation.
- [Platform Architect](https://apiopscycles.com/roles/platform-architect.md) (consulted): Guides platform, integration, scalability, and architecture decisions that shape how the capability or API is built and operated.

## 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)
- [Capability Validation Canvas](https://apiopscycles.com/resources/capability-hypothesis-canvas.md)