Start from the most external meaningful customer. Reuse journey and capability-value evidence to validate whether an automation hypothesis should proceed.
Integration work often jumps too quickly to a technical pattern. This station keeps the team focused on consumer need, value, domain meaning, ownership, reuse potential, viability, assumptions, and validation before selecting APIs, events, files, streams, data products, direct integration, or hybrids.
Method map
Navigate the method
Select a station, cycle, or stakeholder perspective to explore the method.
Outcomes
A testable integration capability hypothesis
Consumers, reuse scope, provider, owner, and supporting evidence clarified
Critical assumptions, validation step, and proceed-or-stop decision documented
Journey criteria
Entry criteria
The automation hypothesis has enough referenced evidence about expected outcome, scope, initial implementation assumptions, critical risks, validation experiment, thresholds, and decision to determine whether it should proceed.
Ownership is clear for the automation opportunity, process decisions, PoC validation, risks, and lifecycle outcomes.
Exit 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.
People to involve
Related resources
canvasCustomer Journey CanvasWhat journey does the most external meaningful customer experience, and what should improve?
canvasCapability Value Proposition CanvasA technology-agnostic canvas for mapping consumer tasks, gains, pains, and candidate reusable capabilities before selecting an implementation style.