# Process & Experience Requirements — Automation Cycle

Canonical page: https://apiopscycles.com/cycles/automation-cycle/stations/api-consumer-experience

Language: en

Entity ID: api-consumer-experience

Cycle: [Automation Cycle](https://apiopscycles.com/cycles/automation-cycle.md)

Read [shared station guidance](https://apiopscycles.com/stations/api-consumer-experience.md) first. The sections below supplement or replace the corresponding shared sections for this cycle. Sections not repeated here retain the shared guidance.

## Journey entry criteria

- Relevant market signals, feedback, or operational insights are available to guide this capability opportunity. — Relevant market signals, feedback, or operational insights are available to guide this API opportunity. (ID: metrics-feedback-available)
- Business goals are defined. (ID: business-goals-defined)
- Market research identifies capability opportunities. — Market research identifies API opportunities. (ID: market-research-done)
- Relevant stakeholders agree this capability opportunity is worth exploring and prioritizing. — Relevant stakeholders agree this API opportunity is worth exploring and prioritizing. (ID: stakeholder-approval)

## Journey exit criteria

- Capability opportunity is identified and documented. — Individual API opportunities are identified and documented. (ID: api-opportunity-documented)
- The capability addresses a clear business need and is reusable by its intended consumers. — The API meets a clear business need and is reusable for multiple API consumers. (ID: api-reusability)
- The selected interface provides an appropriate abstraction for consumers. — The API is intended to shield consumers from backend complexity and inconsistencies. (ID: hide-backend-discrepancies)
- The capability value proposition has been validated with business and consumer stakeholders. — The API value proposition has been reviewed and validated with the relevant business and consumer stakeholders. (ID: value-prop-validated)
- Consumer segments are identified. — API consumer segments (internal and external) are identified. (ID: consumer-segments-identified)
- A high-level implementation roadmap is defined. — High-level roadmaps for API development are established. (ID: api-roadmap-defined)

## Description

Clarify the process, experience, domain, service, and non-functional requirements that the later workflow and architecture must satisfy.

## Role participation and responsibilities

- [Process Owner](https://apiopscycles.com/roles/process-owner.md) (lead): Owns the business process being automated, including objectives, rules, outcomes, and improvement priorities.
- [Automation Owner](https://apiopscycles.com/roles/automation-owner.md) (core): Owns automation goals, business value, priorities, controls, and lifecycle outcomes.
- [Customer or Partner Representative](https://apiopscycles.com/roles/customer-specialist.md) (core): Contributes the business customer or partner perspective for the journey, value, and collaboration model.; suggested-answer-owner: [Consumer Experience Requirements Canvas](https://apiopscycles.com/resources/consumer-experience-requirements-canvas.md)
- [Domain Expert](https://apiopscycles.com/roles/domain-specialist.md) (core): Brings deep knowledge of the business domain, concepts, rules, and constraints the capability or interface must reflect.
- [Support and Operations Owner](https://apiopscycles.com/roles/operations-specialist.md) (core): Represents runtime support, incident handling, observability, and operational readiness for the capability, API, or automation.
- [Automation Engineer](https://apiopscycles.com/roles/automation-engineer.md) (consulted): Implements, tests, integrates, and maintains automation solutions and supporting workflows.
- [Compliance and Legal Specialist](https://apiopscycles.com/roles/compliance-specialist.md) (consulted): Clarifies legal, privacy, regulatory, and contractual requirements that affect the capability, API, interface, or automation.
- [Security Specialist](https://apiopscycles.com/roles/security-specialist.md) (consulted): Ensures security risks, controls, and trust boundaries are addressed throughout the API lifecycle.

## Resources

- [Consumer Experience Requirements Canvas](https://apiopscycles.com/resources/consumer-experience-requirements-canvas.md)
- [Domain Canvas](https://apiopscycles.com/resources/domain-canvas.md)