WhoNot selectedWhyNot selectedWhereIntegration Capability StrategyCycleIntegration Productization CycleBusiness Opportunities Line

Station

Integration Capability Strategy

Frame the reusable integration capability, business need, ownership, and expected reuse 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

Navigate the method

Select a station, cycle, or stakeholder perspective to explore the method.

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 ManagementStrategy1Integration CapabilityStrategyConsumer Requirements & Onboarding2Integration ConsumerRequirements &OnboardingArchitecture & Platform Decisions3Integration Architecture& Platform DecisionsSolution & Interface Design4Integration SolutionDesignDelivery & Operations5Integration Delivery &OperationsQuality & Readiness Assurance6Integration ReadinessAssurancePublishing & Enablement7Integration Publishing &EnablementMonitoring & Improvement8Integration Monitoring &ImprovementBusiness Opportunities LinePlatform Architecture LineDesign LineDelivery LinePublishing and Adoption LineOperating Model Line

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.
  • Capability opportunity is identified and documented.

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.

People to involve

Related resources

canvasCustomer Journey CanvasMap customer, partner, or consumer journeys to identify needs, pain points, gains, inputs, outputs, and experience expectations.canvasAPI Value Proposition CanvasAlign API features with user needs by mapping tasks, pains, and gains to API products.canvasCapability Value Proposition CanvasA technology-agnostic canvas for mapping consumer tasks, gains, pains, and candidate reusable capabilities before selecting an implementation style.canvasAPI Business Model CanvasStrategically assess API business viability by mapping value propositions, consumer segments, and key resources.canvasCapability Business Model CanvasA business model canvas for reusable capabilities, covering value, consumers, ownership, engagement, costs, and benefits without assuming an implementation style.canvasDomain CanvasA modeling tool to define and communicate the key entities and relationships in your domain, ensuring semantic consistency across capabilities, integrations, APIs, data products, and services.

Metro lines

Operating Model Line

Covers the operating model for reusable capability management and governance.