Publish the capability so consumers can discover it, evaluate it, request access, complete onboarding, use it, and get support.
Reusable capabilities only create value when consumers can find them, understand their interface contract and service expectations, request access, and know who owns support and lifecycle decisions.
Method map
Navigate the method
Select a station, cycle, or stakeholder perspective to explore the method.
Outcomes
A discoverable reusable capability
Clear onboarding, access, support, and service expectations
Lifecycle and ownership information available to consumers and governance teams
Consumers enabled to use and reuse the capability
Journey criteria
Entry criteria
The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.
The interface design and exposed capabilities trace back to business value and consumer needs.
The interface and its capabilities are documented clearly enough for review, audit, and onboarding.
The interface design follows agreed design standards and conventions.
The interface contract has been validated and tested against functional and non-functional requirements.
Exit criteria
The solution passes quality, security, compliance, and readiness checks.
Audit findings and remediation decisions are shared with the relevant stakeholders.
The capability is ready to be published or released through the selected delivery mechanism.
Consumer-facing documentation and onboarding materials are ready.