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

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

Selected station: Consumer Requirements & Onboarding

People to involve

Related resources

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.

This is what success looks like

Use consumer experience and onboarding guidance to make expectations explicit for both consumers and producers.

  1. Use the Consumer Experience Requirements Canvas to capture consumer goals, availability, freshness, volume, performance, data quality, security, onboarding, change, observability, and recovery expectations. — API Value Proposition Canvas
  2. Use onboarding guidance to describe how consumers will find, request, test, get approved for, and start using the capability. — Customer Journey Canvas
  3. Use the resulting journey and requirements to improve onboarding, documentation, support, and feedback loops for capability consumers.

Metro lines

Review station resources

Browse the resources selected for Process & User Requirements; the summary above explains how they support this station’s work.

Station resources

Resources for Process & User Requirements

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.