# Strategy

Canonical page: https://apiopscycles.com/stations/api-product-strategy

Language: en

Entity ID: api-product-strategy

## Description

Prioritize a reusable integration capability hypothesis before choosing the implementation style.

## Why it matters

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.

## Apply in work

Use shared journey, domain, value proposition, and business model canvases to gather technology-agnostic requirements and decide whether the capability should be reusable.

## Outcomes

- A testable integration capability hypothesis
- Consumers, reuse scope, provider, owner, and supporting evidence clarified
- Critical assumptions, validation step, and proceed-or-stop decision documented

## Steps

1. State the reusable integration capability hypothesis and intended outcome.
2. Identify intended consumers, reuse scope, provider, owner, and optional supporting evidence.
3. Record the initial implementation-style hypothesis without treating it as an architecture decision.
4. Define critical assumptions, smallest validation experiment, and proceed-or-stop decision.

## Questions

- State the reusable integration capability hypothesis and intended outcome.
- Identify intended consumers, reuse scope, provider, owner, and optional supporting evidence.
- Record the initial implementation-style hypothesis without treating it as an architecture decision.
- Define critical assumptions, smallest validation experiment, and proceed-or-stop decision.
- Use shared journey, domain, value proposition, and business model canvases to gather technology-agnostic requirements and decide whether the capability should be reusable.
- 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.

## Evidence

- design-artifact
- documentation
- research
- roadmap

## Completion 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)

## Role participation and responsibilities

- [API Product Owner](https://apiopscycles.com/roles/api-product-owner.md) (lead): Drives the API opportunity, prioritization, and product-level decisions across the lifecycle.; suggested-answer-owner: [API Value Proposition Canvas](https://apiopscycles.com/resources/api-value-proposition-canvas.md); suggested-answer-owner: [API Business Model Canvas](https://apiopscycles.com/resources/api-business-model-canvas.md)
- [Automation Owner](https://apiopscycles.com/roles/automation-owner.md) (lead): Owns automation goals, business value, priorities, controls, and lifecycle outcomes.; suggested-answer-owner: [Automation Hypothesis & Validation Canvas](https://apiopscycles.com/resources/automation-hypothesis-canvas.md)
- [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)
- [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.
- [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.
- [Platform Owner](https://apiopscycles.com/roles/platform-owner.md) (core): Owns platform capabilities, roadmap, operational model, and service expectations.
- [Process Owner](https://apiopscycles.com/roles/process-owner.md) (core): Owns the business process being automated, including objectives, rules, outcomes, and improvement priorities.; suggested-answer-owner: [Automation Hypothesis & Validation Canvas](https://apiopscycles.com/resources/automation-hypothesis-canvas.md)
- [API Consumer Representative](https://apiopscycles.com/roles/api-consumer-specialist.md) (consulted): Represents the needs of developers, integrators, or other API consumers who use the API directly.
- API Program Owner (consulted): Coordinates API portfolio practices, organizational alignment, and long-term API capability development.
- [Automation Engineer](https://apiopscycles.com/roles/automation-engineer.md) (consulted): Implements, tests, integrates, and maintains automation solutions and supporting workflows.
- [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.
- [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.
- [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.
- [Security Specialist](https://apiopscycles.com/roles/security-specialist.md) (consulted): Ensures security risks, controls, and trust boundaries are addressed throughout the API lifecycle.

## Cycle-specific guidance

- [Capability Productization Cycle](https://apiopscycles.com/cycles/capability-productization-cycle/stations/api-product-strategy.md)
- [API Productization Cycle](https://apiopscycles.com/cycles/api-productization-cycle/stations/api-product-strategy.md)
- [Integration Productization Cycle](https://apiopscycles.com/cycles/integration-productization-cycle/stations/api-product-strategy.md)
- [Automation Cycle](https://apiopscycles.com/cycles/automation-cycle/stations/api-product-strategy.md)