WhoNot selectedWhyNot selectedWhereAutomation Workflow DesignCycleAutomation CycleDesign Line

Station

Automation Workflow Design

Design the automation workflow, triggers, decision points, integrations, data handling, relevant interface contracts, and exception paths.

Once the architecture pattern is known, the design must turn capability requirements into clear interface contracts, interactions, schemas, data rules, lifecycle expectations, and consumer obligations.

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 & UserRequirementsArchitecture & Platform Decisions3Automation PlatformDecisionSolution & 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 validated interface contract for the selected implementation style
  • Consistent interaction, data, event, file, workflow, or API contract decisions
  • Design traceability back to capability and consumer requirements
  • Designs aligned with domain models and interaction patterns

Journey criteria

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

Exit criteria

  • The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.
  • The selected interface provides an appropriate abstraction for consumers.
  • The interface design and exposed capabilities trace back to business value and consumer needs.
  • The interface design follows agreed design standards and conventions.

People to involve

Related resources

canvasInteraction CanvasDefine interactions, workflows, inputs, outputs, commands, queries, events, and expected responses to ensure a consistent consumer experience.canvasREST CanvasDesign APIs using RESTful principles, defining resources, verbs, and example requests and responses.canvasEvent CanvasDesign event-driven interfaces and integrations by defining events, triggers, schemas, producers, consumers, and processing logic.checklistAPI Audit ChecklistA lifecycle-based checklist to verify API readiness across design, delivery, publishing, and compliance using defined audit criteria and evidence.guidelineAPI Design PrinciplesA concise guide to API usability, discoverability, and consistency grounded in shared design rules and real consumer needs.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

Design Line

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