A cycle for defining and productizing reusable digital capabilities without assuming the implementation style in advance.
Guide reusable capability definition from hypothesis and consumer/producer requirements through architecture, solution design, delivery, readiness, publishing, and continuous improvement.
Method map
Navigate the method
Select a station, cycle, or stakeholder perspective to explore the method.
Relevant stakeholders agree this capability opportunity is worth exploring and prioritizing.
Exit criteria
The capability value proposition has been validated with business and consumer stakeholders.
The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.
Capability design, service definition, test evidence, operating model, permissions, monitoring, support, fallback, lifecycle arrangements, risks, and ownership have been reviewed for release readiness.
The reusable capability is discoverable with published purpose, value, ownership, lifecycle status, usage conditions, service expectations, access paths, support, versioning, and feedback channels.
Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable digital capability 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.
Agree mutual owner, producer, and consumer commitments for access, service, support, change, and lifecycle.
The right architecture depends on consumer goals, onboarding expectations, service levels, data quality needs, change tolerance, observability, support, and producer constraints.
Select the capability implementation style, architecture pattern, enabling platform, and governance model from evidence.
Architecture choices should follow from evidence about business impact, locations, trust boundaries, capacity, latency, data ownership, consistency, operability, security, privacy, governance, and cost.
Design how consumers access, interact with, receive, or use the capability through the selected implementation style.
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.
Deliver and operate the reusable capability using implementation-style-appropriate engineering, testing, security, release, support, and operational ownership practices.
A reusable integration capability needs reliable delivery and operations regardless of whether it uses APIs, events, messages, files, streams, data products, connectors, or direct integration.
Review capability readiness using evidence from solution design, contract or service definition, testing, operations, permissions, monitoring, support, fallback, lifecycle, risk, and ownership before release.
A formal readiness decision prevents automation solutions from being released without clear evidence, accepted risks, remediation actions, and business and operational ownership.
Publish the reusable capability so intended consumers can discover it, understand its purpose and service expectations, request access, onboard, use it, and get support.
Automation solutions only create value after rollout when affected people and consuming systems understand what changes, how access and operation work, where to get support, and when rollout should pause, expand, or roll back.
Monitor capability value, outcomes, adoption, reuse, service health, consumer experience, cost, sustainability, and lifecycle improvement needs.
Released solutions need evidence to show whether expected outcomes are being achieved, where manual intervention or recovery is still needed, and what lifecycle decision should be made next.
Publish this cycle
Export the page-specific template after reviewing the entity summary and supporting details above.
Publishing
Markdown and Confluence export
Use Markdown for repositories and static sites, or Confluence-wiki markup for compatible Confluence pages.
Markdown
# Capability Productization Cycle question template
A cycle for defining and productizing reusable digital capabilities without assuming the implementation style in advance.
Use this template to gather answers and evidence station by station. Canvas section prompts are listed first, followed by other related resources.
## 1. Capability Strategy
Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable digital capability should proceed.
### Canvas questions
#### Customer Journey Canvas
What journey does the most external meaningful customer experience, and what should improve?
- **Persona**: Who is the typical customer experiencing this journey?
- **Customer Discovers Need**: How does the customer recognize their need or problem?
- **Customer Need Is Resolved**: How is the customer's need ultimately resolved?
- **Journey Steps**: What are the steps the customer takes in their journey?
- **Pains**: What are the customer's pain points or challenges?
- **Gains**: What are the customer's gains or benefits?
- **Inputs & Outputs**: What are the inputs and outputs at each step?
- **Interaction & Processing Rules**: What are the interaction and processing rules at each step?
- **Improvement opportunities**: Which journey steps indicate that an underlying capability or process should be created, improved, automated, or removed?
#### Capability Value Proposition Canvas
Which reusable capability would create value for consumers without deciding yet whether it should be delivered as an API, event, file, stream, data product, or another implementation style?
- **Consumer tasks and outcomes**: What are consumers, partners, users, systems, or teams trying to achieve?
- **Gain-enabling capability features**: What capability features would help consumers achieve better outcomes, speed, automation, insight, reach, or compliance?
- **Pain-relieving capability features**: What capability features would remove friction, manual work, errors, delays, risk, or uncertainty for consumers?
- **Reusable capabilities**: What reusable business or data capabilities could serve these tasks, gains, and pains across more than one consumer or use case?
#### Capability Business Model Canvas
How viable, reusable, funded, owned, supported, and discoverable should this capability be?
- **Capability value proposition**: What value does this reusable capability provide to consumers and to the organization or ecosystem?
- **Capability consumer segments**: Who are the current and potential consumers of the capability, including teams, partners, systems, products, or data users?
- **Consumer engagement**: How will consumers discover, evaluate, request, onboard, get support for, and provide feedback on the capability?
- **Channels**: Through which catalogs, portals, marketplaces, documentation sites, support paths, or governance processes will consumers interact with the capability?
- **Key resources**: Which systems, data assets, platforms, people, standards, funding, and operational capabilities are required?
- **Key activities**: What must the capability owner and producers do to design, deliver, govern, support, and improve the capability?
- **Key partners**: Which business, technology, data, security, legal, platform, or external partners are needed to make the capability work?
- **Benefits**: What business, operational, ecosystem, reuse, compliance, or cost benefits justify the capability?
- **Costs**: What are the significant costs of building, operating, governing, supporting, and evolving the capability?
#### Capability Validation Canvas
Validate whether a proposed reusable digital capability should proceed.
- **Capability to validate**: Which proposed capability and reusable scope are being tested?
- **Reused evidence**: Which earlier canvas outputs support the proposal?
- **Critical assumptions**: What could invalidate value, reuse, ownership, sustainability, or adoption?
- **Minimum validation**: What is the smallest useful validation and success threshold?
- **Decision**: Proceed, narrow, revise and retest, or stop?
### Before this station
- [ ] Business goals are defined.
- [ ] Relevant stakeholders agree this capability opportunity is worth exploring and prioritizing.
### Ready to leave when
- [ ] 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.
## 2. Consumer & Producer Commitments
Agree mutual owner, producer, and consumer commitments for access, service, support, change, and lifecycle.
### Canvas questions
#### Capability Consumer & Producer Commitments Canvas
Agree mutual commitments for providing and consuming a reusable capability.
- **Selected consumers and use cases**: Which consumers and usage contexts are covered?
- **Owner and producer commitments**: What will owners and producers provide, maintain, monitor, and support?
- **Consumer responsibilities**: What must consumers do for appropriate use, access, testing, and feedback?
- **Access and onboarding**: What discovery, approval, testing, and onboarding path is agreed?
- **Service and lifecycle**: What service, change, deprecation, and retirement commitments are agreed?
- **Open commitments**: What remains unresolved before architecture or delivery?
### Before this station
- [ ] 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.
### Ready to leave when
- [ ] 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.
### Other related resources
- **Capability Consumer Onboarding Guide**: Guidance for helping consumers discover, evaluate, request access to, test, onboard, and begin using a reusable capability.
- **Reusable Capability Service Expectations Guide**: Guidance for defining service quality, availability, timeliness, support, change, lifecycle, and consumer commitments.
- **Capability Ownership and Producer Responsibilities Guide**: Guidance for defining business, capability, producer, operational, platform, and support ownership and commitments.
## 3. Capability Architecture & Platform Decisions
Select the capability implementation style, architecture pattern, enabling platform, and governance model from evidence.
### Canvas questions
#### Business Impact Canvas
What value, risk, operational, financial, customer, employee, compliance, and strategic impact is expected or at stake?
- **Expected benefits**: What business, customer, employee, quality, speed, risk, compliance, or strategic benefits are expected?
- **Operational efficiency impact**: How could work effort, waiting time, rework, throughput, reliability, support load, or operational cost change?
- **Customer and employee impact**: How will customers, employees, partners, operators, or support teams experience the change?
- **Financial impact**: What revenue, cost, investment, savings, loss avoidance, or funding impact is expected?
- **Compliance and strategic impact**: What regulatory, contractual, policy, reputation, market, ecosystem, or strategic consequences matter?
- **Impact of not proceeding**: What happens if the capability, automation, integration, or service is not improved or delivered?
- **Risks and criticality**: What availability, security, data, safety, process, adoption, or business continuity risks could affect the outcome?
- **Mitigations and decision impact**: Which mitigations, constraints, trade-offs, or residual risks should influence prioritization, architecture, rollout, or readiness decisions?
#### Location Canvas
What geopolitical, regulatory, network, and trust boundaries affect this capability or integration?
- **Location / Trust Groups**: What are the relevant geopolitical, regulatory, network, or trust groups?
- **Group Characteristics**: What are the characteristics of those groups, such as residency, trust level, or network exposure?
- **Relevant Locations / Zones**: What are the relevant locations, zones, or environments within each group?
- **Location / Zone Characteristics**: What are the characteristics of those locations or zones, such as ownership, region, or exposure?
- **Network / Regulatory Distances**: What latency, trust, regulatory, or connectivity distances exist between the locations?
- **Distance Characteristics**: What are the characteristics of those distances, such as latency sensitivity, residency constraints, or trust boundaries?
- **Connectivity Endpoints**: What connectivity endpoints or interfaces are associated with the locations?
- **Endpoint Access Characteristics**: What are the characteristics of those endpoints, such as exposure, protocol, security, or access restrictions?
#### Capacity Canvas
How much demand, load, timing, and scaling capacity must be understood for the capability, automation, integration, or service?
- **Current Business Volumes**: What are the current business volumes and transaction rates?
- **Future Consumption Trends**: What are the anticipated future consumption trends?
- **Peak Load and Availability Requirements**: What are the peak load and availability requirements?
- **Caching Strategies**: What caching strategies can be used to optimize performance?
- **Rate Limiting Strategies**: What rate limiting strategies can be used to manage consumption?
- **Scaling Strategies**: What scaling strategies can be used to accommodate growth?
#### Capability Architecture Decision Canvas
Choose how the capability will be delivered using evidence already gathered.
- **Reused inputs**: Which earlier decisions and constraints shape the implementation choice?
- **Viable options**: Which API, event, workflow, application, data product, shared service, human service, or hybrid options remain viable?
- **Selected approach**: Which implementation style and enabling platform are selected?
- **Decision rationale**: Why does the selected approach fit best?
- **Rejected alternatives**: Which serious alternatives were rejected, and why?
- **Open risks**: What still needs validation before delivery or release?
### Before this station
- [ ] 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.
### Ready to leave when
- [ ] 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.
## 4. Capability Solution & Interaction Design
Design how consumers access, interact with, receive, or use the capability through the selected implementation style.
### Canvas questions
#### Domain Canvas
What are the core entities and business rules related to this capability or domain?
- **Selected Customer Journey Steps**: Which customer journey steps are relevant to this domain?
- **Core Entities & Business Meaning**: What are the core entities and their business meaning?
- **Attributes & Business Importance**: What are the key attributes of each entity and their business importance?
- **Relationships Between Entities**: What are the relationships between the entities?
- **Business, Compliance & Integrity Rules**: What are the business, compliance, and integrity rules related to the entities?
- **Security & Privacy Considerations**: What are the security and privacy considerations related to the entities?
#### Capability Solution Design Canvas
Refine the selected implementation style into a clear consumer-facing capability design.
- **Selected inputs**: Which earlier journey, value, domain, commitment, and architecture decisions are reused?
- **Boundary and interaction**: What belongs inside the capability, and how do consumers use it?
- **Contract, rules, and outcomes**: What behavior, responsibilities, inputs, outputs, and outcomes are promised?
- **Errors and security**: How are exceptions, access, privacy, and trust handled?
- **Lifecycle and support**: How will change, versioning, support, deprecation, and retirement work?
- **Observability**: What health, usage, quality, value, and consumer signals must be visible?
#### Interaction Canvas
What kinds of interactions should this capability support before choosing a protocol-specific design?
- **CRUD Interactions**: Are CRUD (Create, Read, Update, Delete) interactions needed here?
- **CRUD Input & Output Models**: What are the input and output models for the CRUD interactions, if this style is needed?
- **CRUD Processing & Validation**: What are the processing and validation rules for the CRUD interactions, if this style is needed?
- **Query-Driven Interactions**: What read or query interactions are needed to answer consumer questions?
- **Query-Driven Input & Output Models**: What are the input and output models for the query-driven interactions?
- **Query-Driven Processing & Validation**: What are the processing and validation rules for the query-driven interactions?
- **Command-Driven Interactions**: What state-changing commands are needed, if any?
- **Command-Driven Input & Output Models**: What are the input and output models for the command-driven interactions, if this style is needed?
- **Command-Driven Processing & Validation**: What are the processing and validation rules for the command-driven interactions, if this style is needed?
- **Event-Driven Interactions**: What events need to be published or consumed, if any?
- **Event-Driven Input & Output Models**: What are the input and output models for the event-driven interactions, if this style is needed?
- **Event-Driven Processing & Validation**: What are the processing and validation rules for the event-driven interactions, if this style is needed?
### Before this station
- [ ] 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.
### Ready to leave when
- [ ] 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.
### Other related resources
- **Contract-First Capability Design**: Guidance for validating capability contracts before delivery, including API contracts, event schemas, file schemas, data contracts, service agreements, workflow inputs and outputs, and user-facing service promises.
## 5. Capability Delivery & Operations
Deliver and operate the reusable capability using implementation-style-appropriate engineering, testing, security, release, support, and operational ownership practices.
### Canvas questions
#### Capability Readiness & Operations Canvas
Prepare the minimum operating evidence needed before capability readiness review.
- **Ownership**: Who owns value, the capability lifecycle, production, operations, support, and changes?
- **Environments and access**: Are required environments, access, permissions, and credentials ready?
- **Test evidence**: What proves outcomes, quality, security, compatibility, resilience, and consumer usability?
- **Monitoring and support**: How will health, usage, value, incidents, consumers, and operators be supported?
- **Continuity and recovery**: How will service continue, degrade safely, recover, or fall back?
- **Readiness status**: Are service definitions, runbooks, risks, conditions, and blocking gaps clear?
### Before this station
- [ ] 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.
### Ready to leave when
- [ ] 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.
### Other related resources
- **Capability Delivery Guide**: Guidance for selecting implementation-style-appropriate engineering, configuration, validation, release, and operational practices.
- **Capability Testing and Validation Guide**: Guidance for validating expected outcomes, contracts or service definitions, quality, security, compatibility, resilience, and consumer usability.
- **Capability CI/CD and Release Guide**: Guidance for release automation when the selected implementation style includes deployable software, configuration, contracts, or infrastructure.
- **Capability Operational Ownership Guide**: Guidance for assigning runtime health, incident, support, recovery, change, and lifecycle ownership for a reusable capability.
- **Capability Security and Access Guide**: Guidance for defining identity, access, confidentiality, privacy, consent, retention, audit, and trust controls for a reusable capability.
- **Capability Support and Lifecycle Guide**: Guidance for support paths, change communication, service status, lifecycle expectations, deprecation, retirement, and improvement handling.
## 6. Capability Readiness Assurance
Review capability readiness using evidence from solution design, contract or service definition, testing, operations, permissions, monitoring, support, fallback, lifecycle, risk, and ownership before release.
### Station questions
- Review the completed design, test evidence, operating model, permissions, credentials, monitoring, support, fallback, and rollback arrangements.
- Verify that known risks, exceptions, unsafe actions, human oversight, compliance requirements, and unresolved assumptions have been addressed or explicitly accepted.
- Record blocking findings, accepted residual risks, release conditions, and required remediation actions.
- Decide whether the release is ready, ready with conditions, requires remediation, or is not approved.
- Record the decision owner, decision date, and evidence used.
- Confirm that nothing proceeds to release without clear business and operational ownership.
- Use readiness evidence to make an explicit go, conditional-go, or no-go decision before production use.
- A formal readiness decision prevents automation solutions from being released without clear evidence, accepted risks, remediation actions, and business and operational ownership.
### Before this station
- [ ] 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.
### Ready to leave when
- [ ] 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.
### Other related resources
- **Capability Readiness Checklist**: A checklist for reviewing evidence, risks, ownership, service commitments, support, continuity, lifecycle arrangements, and release readiness.
- **Capability Compliance and Governance Guide**: Guidance for compliance, policy, funding, ownership, data governance, auditability, and lifecycle governance of reusable capabilities.
- **Capability Service Quality Checklist**: A checklist for assessing availability, quality, timeliness, support, continuity, consumer impact, and service expectations before release.
## 7. Capability Publishing & Enablement
Publish the reusable capability so intended consumers can discover it, understand its purpose and service expectations, request access, onboard, use it, and get support.
### Station questions
- Affected people and changed work: Who will use, operate, support, approve, consume, or be affected by the release, and what responsibilities, decisions, handoffs, or working practices will change?
- Activation and rollout approach: How will access, permissions, pilot use, phased rollout, restricted groups, parallel operation, and rollout expansion be managed?
- Enablement and support: What communication, training, operating instructions, and support paths are required?
- Feedback and control: How will adoption, trust, actual use, issues, and unexpected behavior be monitored, and what conditions trigger pause, rollback, or return to manual operation?
- Plan rollout, enablement, support, feedback, and rollback so released solutions can be adopted safely.
- Automation solutions only create value after rollout when affected people and consuming systems understand what changes, how access and operation work, where to get support, and when rollout should pause, expand, or roll back.
### Before this station
- [ ] 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.
### Ready to leave when
- [ ] 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.
### Other related resources
- **Capability Publishing and Discovery Guide**: Guidance for publishing capability purpose, value, ownership, lifecycle status, usage conditions, examples, limitations, dependencies, access, and support.
- **Capability Consumer Onboarding Guide**: Guidance for helping consumers discover, evaluate, request access to, test, onboard, and begin using a reusable capability.
- **Capability Service Agreement Template**: A template for documenting reusable capability service expectations, responsibilities, support model, quality commitments, lifecycle rules, and consumer obligations.
- **Capability Versioning and Lifecycle Guide**: Guidance for capability change, compatibility, migration, versioning, deprecation, retirement, and consumer communication.
## 8. Capability Monitoring & Improvement
Monitor capability value, outcomes, adoption, reuse, service health, consumer experience, cost, sustainability, and lifecycle improvement needs.
### Station questions
- Outcomes and value: Are the expected process, user, and business outcomes being achieved?
- Operational performance: What do successful runs, failures, partial completions, exceptions, retries, timeouts, interventions, processing time, waiting time, and cost show?
- User, risk, and recovery signals: What errors, corrections, unsafe actions, bypassing, mistrust, support needs, fallback events, or recovery failures are occurring?
- Learning and lifecycle decision: Which hypothesis assumptions were supported or rejected, and should the solution be improved, expanded, restricted, redesigned, paused, or retired?
- Use operational, user, risk, and value evidence to decide what to improve, expand, restrict, pause, or retire.
- Released solutions need evidence to show whether expected outcomes are being achieved, where manual intervention or recovery is still needed, and what lifecycle decision should be made next.
### Before this station
- [ ] 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.
### Ready to leave when
- [ ] Consumer-facing documentation and onboarding materials are ready.
- [ ] Consumer onboarding, support, and communication processes are ready.
- [ ] Legal, privacy, and compliance requirements for publishing or release are defined and understood.
### Other related resources
- **Capability Monitoring and Value Metrics**: Guidance for measuring value, outcomes, adoption, reuse, service health, consumer experience, cost, sustainability, and lifecycle fitness.
- **Capability Adoption and Reuse Guide**: Guidance for tracking consumer adoption, reuse growth, duplicate capability creation, onboarding friction, and reuse barriers.
- **Capability Consumer Feedback Guide**: Guidance for collecting consumer feedback, support needs, improvement requests, abandonment signals, and evidence of consumer success.
- **Capability Lifecycle Management Guide**: Guidance for deciding whether to improve, expand, consolidate, standardize, replace, deprecate, or retire a reusable capability.
Confluence-wiki
h1. Capability Productization Cycle question template
A cycle for defining and productizing reusable digital capabilities without assuming the implementation style in advance.
Use this template to gather answers and evidence station by station. Canvas section prompts are listed first, followed by other related resources.
h2. 1. Capability Strategy
Start from customer journey, capability value, and viability evidence, then validate whether the proposed reusable digital capability should proceed.
h3. Canvas questions
h4. Customer Journey Canvas
What journey does the most external meaningful customer experience, and what should improve?
* *Persona*: Who is the typical customer experiencing this journey?
* *Customer Discovers Need*: How does the customer recognize their need or problem?
* *Customer Need Is Resolved*: How is the customer's need ultimately resolved?
* *Journey Steps*: What are the steps the customer takes in their journey?
* *Pains*: What are the customer's pain points or challenges?
* *Gains*: What are the customer's gains or benefits?
* *Inputs & Outputs*: What are the inputs and outputs at each step?
* *Interaction & Processing Rules*: What are the interaction and processing rules at each step?
* *Improvement opportunities*: Which journey steps indicate that an underlying capability or process should be created, improved, automated, or removed?
h4. Capability Value Proposition Canvas
Which reusable capability would create value for consumers without deciding yet whether it should be delivered as an API, event, file, stream, data product, or another implementation style?
* *Consumer tasks and outcomes*: What are consumers, partners, users, systems, or teams trying to achieve?
* *Gain-enabling capability features*: What capability features would help consumers achieve better outcomes, speed, automation, insight, reach, or compliance?
* *Pain-relieving capability features*: What capability features would remove friction, manual work, errors, delays, risk, or uncertainty for consumers?
* *Reusable capabilities*: What reusable business or data capabilities could serve these tasks, gains, and pains across more than one consumer or use case?
h4. Capability Business Model Canvas
How viable, reusable, funded, owned, supported, and discoverable should this capability be?
* *Capability value proposition*: What value does this reusable capability provide to consumers and to the organization or ecosystem?
* *Capability consumer segments*: Who are the current and potential consumers of the capability, including teams, partners, systems, products, or data users?
* *Consumer engagement*: How will consumers discover, evaluate, request, onboard, get support for, and provide feedback on the capability?
* *Channels*: Through which catalogs, portals, marketplaces, documentation sites, support paths, or governance processes will consumers interact with the capability?
* *Key resources*: Which systems, data assets, platforms, people, standards, funding, and operational capabilities are required?
* *Key activities*: What must the capability owner and producers do to design, deliver, govern, support, and improve the capability?
* *Key partners*: Which business, technology, data, security, legal, platform, or external partners are needed to make the capability work?
* *Benefits*: What business, operational, ecosystem, reuse, compliance, or cost benefits justify the capability?
* *Costs*: What are the significant costs of building, operating, governing, supporting, and evolving the capability?
h4. Capability Validation Canvas
Validate whether a proposed reusable digital capability should proceed.
* *Capability to validate*: Which proposed capability and reusable scope are being tested?
* *Reused evidence*: Which earlier canvas outputs support the proposal?
* *Critical assumptions*: What could invalidate value, reuse, ownership, sustainability, or adoption?
* *Minimum validation*: What is the smallest useful validation and success threshold?
* *Decision*: Proceed, narrow, revise and retest, or stop?
h3. Before this station
* [ ] Business goals are defined.
* [ ] Relevant stakeholders agree this capability opportunity is worth exploring and prioritizing.
h3. Ready to leave when
* [ ] 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.
h2. 2. Consumer & Producer Commitments
Agree mutual owner, producer, and consumer commitments for access, service, support, change, and lifecycle.
h3. Canvas questions
h4. Capability Consumer & Producer Commitments Canvas
Agree mutual commitments for providing and consuming a reusable capability.
* *Selected consumers and use cases*: Which consumers and usage contexts are covered?
* *Owner and producer commitments*: What will owners and producers provide, maintain, monitor, and support?
* *Consumer responsibilities*: What must consumers do for appropriate use, access, testing, and feedback?
* *Access and onboarding*: What discovery, approval, testing, and onboarding path is agreed?
* *Service and lifecycle*: What service, change, deprecation, and retirement commitments are agreed?
* *Open commitments*: What remains unresolved before architecture or delivery?
h3. Before this station
* [ ] 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.
h3. Ready to leave when
* [ ] 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.
h3. Other related resources
* *Capability Consumer Onboarding Guide*: Guidance for helping consumers discover, evaluate, request access to, test, onboard, and begin using a reusable capability.
* *Reusable Capability Service Expectations Guide*: Guidance for defining service quality, availability, timeliness, support, change, lifecycle, and consumer commitments.
* *Capability Ownership and Producer Responsibilities Guide*: Guidance for defining business, capability, producer, operational, platform, and support ownership and commitments.
h2. 3. Capability Architecture & Platform Decisions
Select the capability implementation style, architecture pattern, enabling platform, and governance model from evidence.
h3. Canvas questions
h4. Business Impact Canvas
What value, risk, operational, financial, customer, employee, compliance, and strategic impact is expected or at stake?
* *Expected benefits*: What business, customer, employee, quality, speed, risk, compliance, or strategic benefits are expected?
* *Operational efficiency impact*: How could work effort, waiting time, rework, throughput, reliability, support load, or operational cost change?
* *Customer and employee impact*: How will customers, employees, partners, operators, or support teams experience the change?
* *Financial impact*: What revenue, cost, investment, savings, loss avoidance, or funding impact is expected?
* *Compliance and strategic impact*: What regulatory, contractual, policy, reputation, market, ecosystem, or strategic consequences matter?
* *Impact of not proceeding*: What happens if the capability, automation, integration, or service is not improved or delivered?
* *Risks and criticality*: What availability, security, data, safety, process, adoption, or business continuity risks could affect the outcome?
* *Mitigations and decision impact*: Which mitigations, constraints, trade-offs, or residual risks should influence prioritization, architecture, rollout, or readiness decisions?
h4. Location Canvas
What geopolitical, regulatory, network, and trust boundaries affect this capability or integration?
* *Location / Trust Groups*: What are the relevant geopolitical, regulatory, network, or trust groups?
* *Group Characteristics*: What are the characteristics of those groups, such as residency, trust level, or network exposure?
* *Relevant Locations / Zones*: What are the relevant locations, zones, or environments within each group?
* *Location / Zone Characteristics*: What are the characteristics of those locations or zones, such as ownership, region, or exposure?
* *Network / Regulatory Distances*: What latency, trust, regulatory, or connectivity distances exist between the locations?
* *Distance Characteristics*: What are the characteristics of those distances, such as latency sensitivity, residency constraints, or trust boundaries?
* *Connectivity Endpoints*: What connectivity endpoints or interfaces are associated with the locations?
* *Endpoint Access Characteristics*: What are the characteristics of those endpoints, such as exposure, protocol, security, or access restrictions?
h4. Capacity Canvas
How much demand, load, timing, and scaling capacity must be understood for the capability, automation, integration, or service?
* *Current Business Volumes*: What are the current business volumes and transaction rates?
* *Future Consumption Trends*: What are the anticipated future consumption trends?
* *Peak Load and Availability Requirements*: What are the peak load and availability requirements?
* *Caching Strategies*: What caching strategies can be used to optimize performance?
* *Rate Limiting Strategies*: What rate limiting strategies can be used to manage consumption?
* *Scaling Strategies*: What scaling strategies can be used to accommodate growth?
h4. Capability Architecture Decision Canvas
Choose how the capability will be delivered using evidence already gathered.
* *Reused inputs*: Which earlier decisions and constraints shape the implementation choice?
* *Viable options*: Which API, event, workflow, application, data product, shared service, human service, or hybrid options remain viable?
* *Selected approach*: Which implementation style and enabling platform are selected?
* *Decision rationale*: Why does the selected approach fit best?
* *Rejected alternatives*: Which serious alternatives were rejected, and why?
* *Open risks*: What still needs validation before delivery or release?
h3. Before this station
* [ ] 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.
h3. Ready to leave when
* [ ] 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.
h2. 4. Capability Solution & Interaction Design
Design how consumers access, interact with, receive, or use the capability through the selected implementation style.
h3. Canvas questions
h4. Domain Canvas
What are the core entities and business rules related to this capability or domain?
* *Selected Customer Journey Steps*: Which customer journey steps are relevant to this domain?
* *Core Entities & Business Meaning*: What are the core entities and their business meaning?
* *Attributes & Business Importance*: What are the key attributes of each entity and their business importance?
* *Relationships Between Entities*: What are the relationships between the entities?
* *Business, Compliance & Integrity Rules*: What are the business, compliance, and integrity rules related to the entities?
* *Security & Privacy Considerations*: What are the security and privacy considerations related to the entities?
h4. Capability Solution Design Canvas
Refine the selected implementation style into a clear consumer-facing capability design.
* *Selected inputs*: Which earlier journey, value, domain, commitment, and architecture decisions are reused?
* *Boundary and interaction*: What belongs inside the capability, and how do consumers use it?
* *Contract, rules, and outcomes*: What behavior, responsibilities, inputs, outputs, and outcomes are promised?
* *Errors and security*: How are exceptions, access, privacy, and trust handled?
* *Lifecycle and support*: How will change, versioning, support, deprecation, and retirement work?
* *Observability*: What health, usage, quality, value, and consumer signals must be visible?
h4. Interaction Canvas
What kinds of interactions should this capability support before choosing a protocol-specific design?
* *CRUD Interactions*: Are CRUD (Create, Read, Update, Delete) interactions needed here?
* *CRUD Input & Output Models*: What are the input and output models for the CRUD interactions, if this style is needed?
* *CRUD Processing & Validation*: What are the processing and validation rules for the CRUD interactions, if this style is needed?
* *Query-Driven Interactions*: What read or query interactions are needed to answer consumer questions?
* *Query-Driven Input & Output Models*: What are the input and output models for the query-driven interactions?
* *Query-Driven Processing & Validation*: What are the processing and validation rules for the query-driven interactions?
* *Command-Driven Interactions*: What state-changing commands are needed, if any?
* *Command-Driven Input & Output Models*: What are the input and output models for the command-driven interactions, if this style is needed?
* *Command-Driven Processing & Validation*: What are the processing and validation rules for the command-driven interactions, if this style is needed?
* *Event-Driven Interactions*: What events need to be published or consumed, if any?
* *Event-Driven Input & Output Models*: What are the input and output models for the event-driven interactions, if this style is needed?
* *Event-Driven Processing & Validation*: What are the processing and validation rules for the event-driven interactions, if this style is needed?
h3. Before this station
* [ ] 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.
h3. Ready to leave when
* [ ] 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.
h3. Other related resources
* *Contract-First Capability Design*: Guidance for validating capability contracts before delivery, including API contracts, event schemas, file schemas, data contracts, service agreements, workflow inputs and outputs, and user-facing service promises.
h2. 5. Capability Delivery & Operations
Deliver and operate the reusable capability using implementation-style-appropriate engineering, testing, security, release, support, and operational ownership practices.
h3. Canvas questions
h4. Capability Readiness & Operations Canvas
Prepare the minimum operating evidence needed before capability readiness review.
* *Ownership*: Who owns value, the capability lifecycle, production, operations, support, and changes?
* *Environments and access*: Are required environments, access, permissions, and credentials ready?
* *Test evidence*: What proves outcomes, quality, security, compatibility, resilience, and consumer usability?
* *Monitoring and support*: How will health, usage, value, incidents, consumers, and operators be supported?
* *Continuity and recovery*: How will service continue, degrade safely, recover, or fall back?
* *Readiness status*: Are service definitions, runbooks, risks, conditions, and blocking gaps clear?
h3. Before this station
* [ ] 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.
h3. Ready to leave when
* [ ] 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.
h3. Other related resources
* *Capability Delivery Guide*: Guidance for selecting implementation-style-appropriate engineering, configuration, validation, release, and operational practices.
* *Capability Testing and Validation Guide*: Guidance for validating expected outcomes, contracts or service definitions, quality, security, compatibility, resilience, and consumer usability.
* *Capability CI/CD and Release Guide*: Guidance for release automation when the selected implementation style includes deployable software, configuration, contracts, or infrastructure.
* *Capability Operational Ownership Guide*: Guidance for assigning runtime health, incident, support, recovery, change, and lifecycle ownership for a reusable capability.
* *Capability Security and Access Guide*: Guidance for defining identity, access, confidentiality, privacy, consent, retention, audit, and trust controls for a reusable capability.
* *Capability Support and Lifecycle Guide*: Guidance for support paths, change communication, service status, lifecycle expectations, deprecation, retirement, and improvement handling.
h2. 6. Capability Readiness Assurance
Review capability readiness using evidence from solution design, contract or service definition, testing, operations, permissions, monitoring, support, fallback, lifecycle, risk, and ownership before release.
h3. Station questions
* Review the completed design, test evidence, operating model, permissions, credentials, monitoring, support, fallback, and rollback arrangements.
* Verify that known risks, exceptions, unsafe actions, human oversight, compliance requirements, and unresolved assumptions have been addressed or explicitly accepted.
* Record blocking findings, accepted residual risks, release conditions, and required remediation actions.
* Decide whether the release is ready, ready with conditions, requires remediation, or is not approved.
* Record the decision owner, decision date, and evidence used.
* Confirm that nothing proceeds to release without clear business and operational ownership.
* Use readiness evidence to make an explicit go, conditional-go, or no-go decision before production use.
* A formal readiness decision prevents automation solutions from being released without clear evidence, accepted risks, remediation actions, and business and operational ownership.
h3. Before this station
* [ ] 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.
h3. Ready to leave when
* [ ] 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.
h3. Other related resources
* *Capability Readiness Checklist*: A checklist for reviewing evidence, risks, ownership, service commitments, support, continuity, lifecycle arrangements, and release readiness.
* *Capability Compliance and Governance Guide*: Guidance for compliance, policy, funding, ownership, data governance, auditability, and lifecycle governance of reusable capabilities.
* *Capability Service Quality Checklist*: A checklist for assessing availability, quality, timeliness, support, continuity, consumer impact, and service expectations before release.
h2. 7. Capability Publishing & Enablement
Publish the reusable capability so intended consumers can discover it, understand its purpose and service expectations, request access, onboard, use it, and get support.
h3. Station questions
* Affected people and changed work: Who will use, operate, support, approve, consume, or be affected by the release, and what responsibilities, decisions, handoffs, or working practices will change?
* Activation and rollout approach: How will access, permissions, pilot use, phased rollout, restricted groups, parallel operation, and rollout expansion be managed?
* Enablement and support: What communication, training, operating instructions, and support paths are required?
* Feedback and control: How will adoption, trust, actual use, issues, and unexpected behavior be monitored, and what conditions trigger pause, rollback, or return to manual operation?
* Plan rollout, enablement, support, feedback, and rollback so released solutions can be adopted safely.
* Automation solutions only create value after rollout when affected people and consuming systems understand what changes, how access and operation work, where to get support, and when rollout should pause, expand, or roll back.
h3. Before this station
* [ ] 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.
h3. Ready to leave when
* [ ] 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.
h3. Other related resources
* *Capability Publishing and Discovery Guide*: Guidance for publishing capability purpose, value, ownership, lifecycle status, usage conditions, examples, limitations, dependencies, access, and support.
* *Capability Consumer Onboarding Guide*: Guidance for helping consumers discover, evaluate, request access to, test, onboard, and begin using a reusable capability.
* *Capability Service Agreement Template*: A template for documenting reusable capability service expectations, responsibilities, support model, quality commitments, lifecycle rules, and consumer obligations.
* *Capability Versioning and Lifecycle Guide*: Guidance for capability change, compatibility, migration, versioning, deprecation, retirement, and consumer communication.
h2. 8. Capability Monitoring & Improvement
Monitor capability value, outcomes, adoption, reuse, service health, consumer experience, cost, sustainability, and lifecycle improvement needs.
h3. Station questions
* Outcomes and value: Are the expected process, user, and business outcomes being achieved?
* Operational performance: What do successful runs, failures, partial completions, exceptions, retries, timeouts, interventions, processing time, waiting time, and cost show?
* User, risk, and recovery signals: What errors, corrections, unsafe actions, bypassing, mistrust, support needs, fallback events, or recovery failures are occurring?
* Learning and lifecycle decision: Which hypothesis assumptions were supported or rejected, and should the solution be improved, expanded, restricted, redesigned, paused, or retired?
* Use operational, user, risk, and value evidence to decide what to improve, expand, restrict, pause, or retire.
* Released solutions need evidence to show whether expected outcomes are being achieved, where manual intervention or recovery is still needed, and what lifecycle decision should be made next.
h3. Before this station
* [ ] 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.
h3. Ready to leave when
* [ ] Consumer-facing documentation and onboarding materials are ready.
* [ ] Consumer onboarding, support, and communication processes are ready.
* [ ] Legal, privacy, and compliance requirements for publishing or release are defined and understood.
h3. Other related resources
* *Capability Monitoring and Value Metrics*: Guidance for measuring value, outcomes, adoption, reuse, service health, consumer experience, cost, sustainability, and lifecycle fitness.
* *Capability Adoption and Reuse Guide*: Guidance for tracking consumer adoption, reuse growth, duplicate capability creation, onboarding friction, and reuse barriers.
* *Capability Consumer Feedback Guide*: Guidance for collecting consumer feedback, support needs, improvement requests, abandonment signals, and evidence of consumer success.
* *Capability Lifecycle Management Guide*: Guidance for deciding whether to improve, expand, consolidate, standardize, replace, deprecate, or retire a reusable capability.