WhoNot selectedWhyNot selectedWhereProcess & User RequirementsCycleAutomation CyclePlatform Architecture Line

Station

Process & User Requirements

Capture process users, roles, handoffs, exceptions, constraints, and service expectations before designing the automation.

The right architecture depends on consumer goals, onboarding expectations, service levels, data quality needs, change tolerance, observability, support, and producer constraints.

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

  • Documented consumer requirements and onboarding expectations
  • Clear producer responsibilities and support expectations
  • Architecture-relevant constraints ready for decision making
  • Improved adoption through consumer empathy, standards, and producer clarity

Journey criteria

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

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

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.canvasConsumer Experience Requirements CanvasA requirements canvas for consumer experience and non-functional needs that should guide the later architecture and implementation-style decision.

Metro lines