# Documentation and DevRel Owner

Canonical page: https://apiopscycles.com/roles/api-devrel-specialist

Language: en

Entity ID: api-devrel-specialist

Owns onboarding content, developer communication, and documentation quality for API consumers.

## Decisions

- Identify consumer systems and teams, provider responsibilities, interaction needs, data needs, onboarding, and access expectations.
- Define environments, test access, credentials, identity, compatibility, versioning, and service expectations.
- Capture data quality, observability, support, failure handling, replay, reconciliation, and recovery needs.
- Use consumer experience and onboarding guidance to make expectations explicit for both consumers and producers.
- The right architecture depends on consumer goals, onboarding expectations, service levels, data quality needs, change tolerance, observability, support, and producer constraints.
- 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?

## Outputs

- Documented consumer requirements and onboarding expectations
- Clear producer responsibilities and support expectations
- Architecture-relevant constraints ready for decision making
- Improved adoption through consumer empathy, standards, and producer clarity
- design-artifact
- documentation
- consumer-feedback
- Safe rollout and enablement plan

## Recommended resources

- [Capability Consumer & Producer Commitments Canvas](https://apiopscycles.com/resources/capability-consumer-producer-requirements-canvas.md)

## Participation by cycle and station

- [Capability Productization Cycle](https://apiopscycles.com/cycles/capability-productization-cycle.md) / [Consumer & Producer Commitments](https://apiopscycles.com/cycles/capability-productization-cycle/stations/api-consumer-experience.md): consulted
- [Capability Productization Cycle](https://apiopscycles.com/cycles/capability-productization-cycle.md) / [Capability Publishing & Enablement](https://apiopscycles.com/cycles/capability-productization-cycle/stations/api-publishing.md): core
- [Capability Productization Cycle](https://apiopscycles.com/cycles/capability-productization-cycle.md) / [Capability Monitoring & Improvement](https://apiopscycles.com/cycles/capability-productization-cycle/stations/monitoring-and-improving.md): consulted
- [API Productization Cycle](https://apiopscycles.com/cycles/api-productization-cycle.md) / [API Consumer Experience](https://apiopscycles.com/cycles/api-productization-cycle/stations/api-consumer-experience.md): core
- [API Productization Cycle](https://apiopscycles.com/cycles/api-productization-cycle.md) / [API Design](https://apiopscycles.com/cycles/api-productization-cycle/stations/api-design.md): consulted
- [API Productization Cycle](https://apiopscycles.com/cycles/api-productization-cycle.md) / [API Publishing](https://apiopscycles.com/cycles/api-productization-cycle/stations/api-publishing.md): core
- [API Productization Cycle](https://apiopscycles.com/cycles/api-productization-cycle.md) / [API Monitoring & Improvement](https://apiopscycles.com/cycles/api-productization-cycle/stations/monitoring-and-improving.md): core
- [Integration Productization Cycle](https://apiopscycles.com/cycles/integration-productization-cycle.md) / [Integration Consumer & Provider Commitments](https://apiopscycles.com/cycles/integration-productization-cycle/stations/api-consumer-experience.md): consulted
- [Integration Productization Cycle](https://apiopscycles.com/cycles/integration-productization-cycle.md) / [Integration Publishing & Enablement](https://apiopscycles.com/cycles/integration-productization-cycle/stations/api-publishing.md): core