Station

Capability Strategy

Frame the business need as a reusable capability with clear value, consumers, ownership, and business goals before selecting the implementation style.

Integration and API work often jumps too quickly to a technical pattern. This station keeps the team focused on the business journey, domain meaning, value, reuse potential, ownership, and viability before selecting APIs, events, files, streams, data products, or direct integration.

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 ManagementStrategy1Capability StrategyConsumer Requirements & Onboarding2Consumer Requirements &OnboardingArchitecture & Platform Decisions3Architecture & PlatformDecisionsSolution & Interface Design4Solution & InterfaceDesignDelivery & Operations5Delivery & OperationsQuality & Readiness Assurance6Quality & ReadinessAssurancePublishing & Enablement7Publishing & EnablementMonitoring & Improvement8Monitoring & ImprovementBusiness Opportunities LinePlatform Architecture LineDesign LineDelivery LinePublishing and Adoption LineOperating Model Line

Selected station: Strategy

People to involve

Related resources

Outcomes

  • A technology-agnostic capability opportunity statement
  • Shared understanding of consumers, producers, domain concepts, and reuse potential
  • A capability value proposition and business model before architecture selection

Journey criteria

Entry criteria

  • Business goals are defined.
  • Relevant stakeholders agree this capability opportunity is worth exploring and prioritizing.

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

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

  1. Map the customer or partner journey that creates the capability need and reveals tasks, pains, gains, inputs, outputs, and decision points. — Customer Journey Canvas
  2. Define the core entities, attributes, relationships, ownership, and business rules that the capability must respect. — Domain Canvas
  3. Use the Capability Value Proposition Canvas to capture consumer tasks, gains, pains, and reusable capability features without naming the delivery technology too early. — API Value Proposition Canvas
  4. Use the Capability Business Model Canvas to clarify ownership, partners, channels, costs, benefits, support, and lifecycle expectations for the reusable capability. — 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 Capability Strategy; the summary above explains how they support this station’s work.

Station resources

Resources for Capability 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.