# Automation Owner

Canonical page: https://apiopscycles.com/roles/automation-owner

Language: en

Entity ID: automation-owner

Owns automation goals, business value, priorities, controls, and lifecycle outcomes.

## Decisions

- State the reusable integration capability hypothesis and intended outcome.
- Identify intended consumers, reuse scope, provider, owner, and optional supporting evidence.
- Record the initial implementation-style hypothesis without treating it as an architecture decision.
- Define critical assumptions, smallest validation experiment, and proceed-or-stop decision.
- Use shared journey, domain, value proposition, and business model canvases to gather technology-agnostic requirements and decide whether the capability should be reusable.
- 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.

## Outputs

- A testable integration capability hypothesis
- Consumers, reuse scope, provider, owner, and supporting evidence clarified
- Critical assumptions, validation step, and proceed-or-stop decision documented
- design-artifact
- documentation
- research
- roadmap
- Documented consumer requirements and onboarding expectations

## Recommended resources

- [Customer Journey Canvas](https://apiopscycles.com/resources/customer-journey-canvas.md)
- [Capability Value Proposition Canvas](https://apiopscycles.com/resources/capability-value-proposition-canvas.md)
- [Automation Hypothesis & Validation Canvas](https://apiopscycles.com/resources/automation-hypothesis-canvas.md)
- [Consumer Experience Requirements Canvas](https://apiopscycles.com/resources/consumer-experience-requirements-canvas.md)
- [Domain Canvas](https://apiopscycles.com/resources/domain-canvas.md)
- [Business Impact Canvas](https://apiopscycles.com/resources/business-impact-canvas.md)
- [Location Canvas](https://apiopscycles.com/resources/location-canvas.md)
- [Capacity Canvas](https://apiopscycles.com/resources/capacity-canvas.md)
- [Automation Architecture Decision Canvas](https://apiopscycles.com/resources/automation-architecture-decision-canvas.md)
- [Automation Workflow Canvas](https://apiopscycles.com/resources/automation-workflow-canvas.md)

## Participation by cycle and station

- [Automation Cycle](https://apiopscycles.com/cycles/automation-cycle.md) / [Automation Opportunity Strategy](https://apiopscycles.com/cycles/automation-cycle/stations/api-product-strategy.md): lead
- [Automation Cycle](https://apiopscycles.com/cycles/automation-cycle.md) / [Process & Experience Requirements](https://apiopscycles.com/cycles/automation-cycle/stations/api-consumer-experience.md): core
- [Automation Cycle](https://apiopscycles.com/cycles/automation-cycle.md) / [Automation Architecture & Platform Decision](https://apiopscycles.com/cycles/automation-cycle/stations/api-platform-architecture.md): core
- [Automation Cycle](https://apiopscycles.com/cycles/automation-cycle.md) / [Automation Workflow Design](https://apiopscycles.com/cycles/automation-cycle/stations/api-design.md): core
- [Automation Cycle](https://apiopscycles.com/cycles/automation-cycle.md) / [Automation Delivery & Operations](https://apiopscycles.com/cycles/automation-cycle/stations/api-delivery.md): core
- [Automation Cycle](https://apiopscycles.com/cycles/automation-cycle.md) / [Automation Readiness Review](https://apiopscycles.com/cycles/automation-cycle/stations/api-audit.md): core
- [Automation Cycle](https://apiopscycles.com/cycles/automation-cycle.md) / [Automation Rollout & Enablement](https://apiopscycles.com/cycles/automation-cycle/stations/api-publishing.md): lead
- [Automation Cycle](https://apiopscycles.com/cycles/automation-cycle.md) / [Automation Monitoring & Improvement](https://apiopscycles.com/cycles/automation-cycle/stations/monitoring-and-improving.md): lead