# Integration Monitoring & Improvement — Integration Productization Cycle

Canonical page: https://apiopscycles.com/cycles/integration-productization-cycle/stations/monitoring-and-improving

Language: en

Entity ID: monitoring-and-improving

Cycle: [Integration Productization Cycle](https://apiopscycles.com/cycles/integration-productization-cycle.md)

Read [shared station guidance](https://apiopscycles.com/stations/monitoring-and-improving.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

- The solution passes quality, security, compliance, and readiness checks. — The API passes compliance, security, and audit checks. (ID: audit-passed)
- Audit findings and remediation decisions are shared with the relevant stakeholders. (ID: audit-reports-shared)
- The capability is ready to be published or released through the selected delivery mechanism. — The API is ready to be deployed and exposed through the intended gateways and environments. (ID: api-ready-for-publishing)
- Consumer-facing documentation and onboarding materials are ready. — Consumer-facing API documentation is complete enough for publishing and onboarding. (ID: api-documentation-ready)

## Journey exit criteria

- Consumer-facing documentation and onboarding materials are ready. — Consumer-facing API documentation is complete enough for publishing and onboarding. (ID: api-documentation-ready)
- Consumer onboarding, support, and communication processes are ready. — Registration, support, and communication processes are ready for API consumers. (ID: consumer-support-ready)
- Legal, privacy, and compliance requirements for publishing or release are defined and understood. — Legal, privacy, and compliance requirements for publishing are defined and understood. (ID: legal-compliance-clear)

## Description

Monitor integration reliability, reuse, incidents, performance, consumer outcomes, and improvement needs.

## Role participation and responsibilities

- [Integration Architect](https://apiopscycles.com/roles/integration-architect.md) (lead): Designs integration approaches and implementation styles that connect the capability or API with other systems.
- [API Consumer Representative](https://apiopscycles.com/roles/api-consumer-specialist.md) (core): Represents the needs of developers, integrators, or other API consumers who use the API directly.
- [Delivery Engineer](https://apiopscycles.com/roles/api-engineer.md) (core): Owns implementation, automation, testing, and release flow concerns needed to deliver the capability, API, or automation reliably.
- [Platform Owner](https://apiopscycles.com/roles/platform-owner.md) (core): Owns platform capabilities, roadmap, operational model, and service expectations.
- [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.
- [Business Owner](https://apiopscycles.com/roles/business-owner.md) (consulted): Represents business goals, funding, and expected outcomes for the capability, API, or automation initiative.
- [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.
- [Platform Architect](https://apiopscycles.com/roles/platform-architect.md) (consulted): Guides platform, integration, scalability, and architecture decisions that shape how the capability or API is built and operated.
- [Security Specialist](https://apiopscycles.com/roles/security-specialist.md) (consulted): Ensures security risks, controls, and trust boundaries are addressed throughout the API lifecycle.