WhoNot selectedWhyNot selectedWhereSolution & Interface DesignCycleNot selectedDesign Line

Station

Solution & Interface Design

Design the interface contract and interaction model after the architecture choice is justified.

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 ManagementStrategy1Capability StrategyConsumer Requirements & Onboarding2Consumer Requirements &OnboardingArchitecture & Platform Decisions3Architecture & PlatformDecisionsSolution & Interface Design4Solution & InterfaceDesignDelivery & Operations5Delivery & OperationsQuality & Readiness Assurance6Quality & ReadinessAssurancePublishing & Enablement7Publishing & EnablementMonitoring & Improvement8Monitoring & 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

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.

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.