Station

API Product Strategy

Before building anything, define your API's value, users, and business goals from day one.

Many organizations think of APIs as tech projects, not products. The result? Confused consumers, poor adoption, and wasted effort. This station helps you define your API’s purpose, target audience, and success criteria, so teams can deliver APIs that solve real problems.

Method map

Metro map

Select a cycle, station, or stakeholder to open its permanent method page.

StrategicGovernanceConsumerTechnicalUser ExperienceUser ExperienceMarket InsightsMarket InsightsBusiness GoalsBusiness GoalsCompetitive AnalysisCompetitive AnalysisEcosystem VisionEcosystem VisionScalable InfrastructureScalable InfrastructureLegal and ComplianceLegal and ComplianceSecurity and PrivacySecurity and PrivacyDesign StandardsDesign StandardsVendor ManagementVendor ManagementContract DesignContract DesignDevelopmentDevelopmentCI/CDCI/CDTest AutomationTest AutomationRelease ManagementRelease ManagementService AgreementsService AgreementsConsumer AdoptionConsumer AdoptionPromotionPromotionPartner IntegrationPartner IntegrationAPI MindsetAPI MindsetRoles and ResponsibilitiesRoles and ResponsibilitiesUpskillingUpskillingOperating GuidelinesOperating GuidelinesPortfolio ManagementPortfolio ManagementBudget and Resource ManagementBudget and Resource ManagementStrategy1API Product StrategyConsumer Requirements & Onboarding2API Consumer ExperienceArchitecture & Platform Decisions3API PlatformArchitectureSolution & Interface Design4API DesignDelivery & Operations5API DeliveryQuality & Readiness Assurance6API AuditPublishing & Enablement7API PublishingMonitoring & Improvement8API Monitoring &ImprovementBusiness Opportunities LinePlatform Architecture LineDesign LineDelivery LinePublishing and Adoption LineOperating Model Line

Selected station: Strategy

People to involve

Related resources

Outcomes

  • A straightforward API value proposition and audience
  • Shared language between product, design, and tech
  • A solid pitch or case for funding/approval

Journey criteria

Entry criteria

  • Capability opportunity is identified and documented.
  • Consumer segments are identified.

Exit criteria

  • 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.

This is what success looks like

Provide guidelines and templates for creating API business models, value propositions, and roadmaps.

  1. Explore the customer or partner problem you expect to solve with APIs. Map the stakeholders, ther journeys and outcomes using the Customer Journey canvas. — Customer Journey Canvas
  2. Define core entities, their attributes, and relationships to create a shared conceptual understanding across journeys and eventually APIs. — Domain Canvas
  3. Use the API Value Proposition Canvas to capture the supported business tasks and the API consumer pains, gains, and features that shape new or reusable APIs. — API Value Proposition Canvas
  4. Define the value — for users and the business with the API Business Model canvas to make your API strategy visual, shareable, and easy to validate with your API consumers at the next station. — API Business Model Canvas

Metro lines

Operating Model Line

Covers the operating model for reusable capability management and governance.

Review station resources

Browse the resources selected for API Product Strategy; the summary above explains how they support this station’s work.

Station resources

Resources for API Product Strategy

canvas

Customer Journey Canvas

Map customer, partner, or consumer journeys to identify needs, pain points, gains, inputs, outputs, and experience expectations.

Outcomes

  • Shared understanding of the customer, partner, or consumer journey
  • Needs, pain points, gains, inputs, and outputs documented
  • Journey evidence available for capability, requirements, and architecture decisions

How it works

  1. Define customer persona
  2. Identify triggers for the journey
  3. Describe the journey's end
  4. Map journey steps with inputs/outputs
  5. Identify customer pains
  6. Summarize customer gains
  7. Define necessary inputs and resulting outputs
  8. Define interactions and processing expectations for each step

Relevant cycles

API Productization Cycle

The API-focused APIOps Cycles journey for productizing, designing, delivering, publishing, and improving APIs.

Automation Cycle

A cycle for identifying, designing, delivering, enabling, and improving automation opportunities.