Design the internal workflow needed to deliver the selected customer and capability outcomes, including work allocation, controls, exceptions, recovery, evidence, and monitoring.
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.
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.
Focuses on solution and interface design principles that can be used across APIs, integrations, automations, data products, and other implementation styles.