WhoNot selectedWhyNot selectedWhereAutomation Architecture & Platform DecisionCycleAutomation CycleDesign Line

Station

Automation Architecture & Platform Decision

Use impact, location, capacity, and earlier requirements to choose the automation implementation approach and record the rationale and remaining risks.

Architecture choices should follow from evidence about business impact, locations, trust boundaries, capacity, latency, data ownership, consistency, operability, security, privacy, governance, and cost.

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 ManagementStrategy1Automation OpportunityStrategyConsumer Requirements & Onboarding2Process & ExperienceRequirementsArchitecture & Platform Decisions3Automation Architecture& Platform DecisionSolution & Interface Design4Automation WorkflowDesignDelivery & Operations5Automation Delivery &OperationsQuality & Readiness Assurance6Automation ReadinessReviewPublishing & Enablement7Automation Rollout &EnablementMonitoring & Improvement8Automation Monitoring &ImprovementBusiness Opportunities LinePlatform Architecture LineDesign LineDelivery LinePublishing and Adoption LineOperating Model Line

Outcomes

  • A justified integration architecture decision
  • Selected style or hybrid and platform decision documented
  • Rejected alternatives, risks, assumptions, and supporting evidence recorded

Journey criteria

Entry criteria

  • Capability opportunity is identified and documented.
  • The capability addresses a clear business need and is reusable by its intended consumers.
  • The selected interface provides an appropriate abstraction for consumers.
  • The capability value proposition has been validated with business and consumer stakeholders.
  • Consumer segments are identified.
  • A high-level implementation roadmap is defined.

Exit criteria

  • The capability addresses a clear business need and is reusable by its intended consumers.
  • The selected interface provides an appropriate abstraction for consumers.
  • The capability value proposition has been validated with business and consumer stakeholders.
  • Consumer segments are identified.
  • A high-level implementation roadmap is defined.

People to involve

Related resources

canvasBusiness Impact CanvasAssess expected benefits, operational, customer, employee, financial, compliance, strategic, risk, and not-proceeding impacts that should shape prioritization and decisions.canvasLocation CanvasMap consumer, producer, system, data, network, regulatory, and trust-boundary locations to ensure compliance and performance across regions.canvasCapacity CanvasQuantify demand, load, timing, availability, and scaling needs for capabilities, automations, integrations, or services.canvasAutomation Architecture Decision CanvasChoose the implementation approach using evidence already gathered.

Metro lines

Design Line

Focuses on solution and interface design principles that can be used across APIs, integrations, automations, data products, and other implementation styles.