# 1. capability-cover Introduce the capability view of the method. It begins with value and mutual service commitments before selecting an implementation style. The supplier-payment status capability is a newly authored fictional teaching example, not a client implementation or measured outcome. Figures, service promises and release criteria are illustrative proposals requiring validation. Working summaries are not reproductions of canonical canvas templates. Source: apiops-cycles-method-data 4.2.1, src/data/method/cycles.json and en/labels.cycles.json; reviewed 4 November 2026. https://apiopscycles.com/cycles/capability-productization-cycle . Method: APIOps Cycles / Osaango Ltd, CC-BY-SA 4.0. # 2. Start with the outcome people need The method description explicitly avoids assuming implementation style in advance. A capability might be accessed through APIs, events, integrations or automation. This is not an organisational maturity assessment. The supplier-payment status capability is a newly authored fictional teaching example, not a client implementation or measured outcome. Figures, service promises and release criteria are illustrative proposals requiring validation. Working summaries are not reproductions of canonical canvas templates. Source: apiops-cycles-method-data 4.2.1, src/data/method/cycles.json and en/labels.cycles.json; reviewed 4 November 2026. https://apiopscycles.com/cycles/capability-productization-cycle . Method: APIOps Cycles / Osaango Ltd, CC-BY-SA 4.0. # 3. Eight stations, revisited as evidence changes The eight labels and their order follow the Capability Productization Cycle station mapping in method-data. This simplified route is an original presentation diagram, not the API Productization metro map. It does not prescribe a one-way delivery process. The supplier-payment status capability is a newly authored fictional teaching example, not a client implementation or measured outcome. Figures, service promises and release criteria are illustrative proposals requiring validation. Working summaries are not reproductions of canonical canvas templates. Source: apiops-cycles-method-data 4.2.1, src/data/method/cycles.json and en/labels.cycles.json; reviewed 4 November 2026. https://apiopscycles.com/cycles/capability-productization-cycle . Method: APIOps Cycles / Osaango Ltd, CC-BY-SA 4.0. # 4. 1. Strategy: test one capability hypothesis Recommended strategy resources: Customer Journey Canvas, Capability Value Proposition Canvas, Capability Business Model Canvas and Capability Hypothesis Canvas. This table is a filled working summary, not the canonical canvas. Validate reuse with actual intended consumers. The supplier-payment status capability is a newly authored fictional teaching example, not a client implementation or measured outcome. Figures, service promises and release criteria are illustrative proposals requiring validation. Working summaries are not reproductions of canonical canvas templates. Source: apiops-cycles-method-data 4.2.1, src/data/method/cycles.json and en/labels.cycles.json; reviewed 4 November 2026. https://apiopscycles.com/cycles/capability-productization-cycle . Method: APIOps Cycles / Osaango Ltd, CC-BY-SA 4.0. # 5. 2. Requirements: agree the service together Canonical station: Consumer & Producer Service Requirements. Use the Capability Consumer/Producer Requirements Canvas. Agree access, service, support, change and lifecycle commitments with all parties. The example is a proposed service expectation, not an SLA already agreed. The supplier-payment status capability is a newly authored fictional teaching example, not a client implementation or measured outcome. Figures, service promises and release criteria are illustrative proposals requiring validation. Working summaries are not reproductions of canonical canvas templates. Source: apiops-cycles-method-data 4.2.1, src/data/method/cycles.json and en/labels.cycles.json; reviewed 4 November 2026. https://apiopscycles.com/cycles/capability-productization-cycle . Method: APIOps Cycles / Osaango Ltd, CC-BY-SA 4.0. # 6. 3. Architecture: choose how to provide it Canonical station: Capability Architecture & Platform Decisions. Recommended resources include Business Impact, Locations, Capacity and Capability Architecture Decision canvases. Options can be combined; do not imply the method requires one implementation. The supplier-payment status capability is a newly authored fictional teaching example, not a client implementation or measured outcome. Figures, service promises and release criteria are illustrative proposals requiring validation. Working summaries are not reproductions of canonical canvas templates. Source: apiops-cycles-method-data 4.2.1, src/data/method/cycles.json and en/labels.cycles.json; reviewed 4 November 2026. https://apiopscycles.com/cycles/capability-productization-cycle . Method: APIOps Cycles / Osaango Ltd, CC-BY-SA 4.0. # 7. 4. Design: make the service promise testable Canonical station: Capability Solution & Interaction Design. Recommended resources: Domain Canvas, Capability Solution Design Canvas, Interaction Canvas and contract-first design. Select the contract or service definition appropriate to the architecture; an OpenAPI contract only covers an HTTP API portion. The supplier-payment status capability is a newly authored fictional teaching example, not a client implementation or measured outcome. Figures, service promises and release criteria are illustrative proposals requiring validation. Working summaries are not reproductions of canonical canvas templates. Source: apiops-cycles-method-data 4.2.1, src/data/method/cycles.json and en/labels.cycles.json; reviewed 4 November 2026. https://apiopscycles.com/cycles/capability-productization-cycle . Method: APIOps Cycles / Osaango Ltd, CC-BY-SA 4.0. # 8. 5. Delivery includes operation and support Canonical station: Capability Delivery & Operations. Use implementation-style-appropriate engineering, testing, security, release, support and operational ownership practices. The Capability Readiness & Operations Canvas connects delivery decisions to operation. The numbered sequence is a suggested teaching workflow, not an additional mandatory method process. The supplier-payment status capability is a newly authored fictional teaching example, not a client implementation or measured outcome. Figures, service promises and release criteria are illustrative proposals requiring validation. Working summaries are not reproductions of canonical canvas templates. Source: apiops-cycles-method-data 4.2.1, src/data/method/cycles.json and en/labels.cycles.json; reviewed 4 November 2026. https://apiopscycles.com/cycles/capability-productization-cycle . Method: APIOps Cycles / Osaango Ltd, CC-BY-SA 4.0. # 9. Use AI with agreed capability context Author-developed guidance applying the delivery station to AI-assisted work; this is not a separate canonical capability station. For an API implementation, scaffold contracts, linting, tests and CI using the API tooling described in the technical deck. For integrations or workflows, use equivalent checks for those artefacts. AI output and a clean lint result do not establish service readiness. Do not put client secrets or restricted data in prompts. The supplier-payment status capability is a newly authored fictional teaching example, not a client implementation or measured outcome. Figures, service promises and release criteria are illustrative proposals requiring validation. Working summaries are not reproductions of canonical canvas templates. Source: apiops-cycles-method-data 4.2.1, src/data/method/cycles.json and en/labels.cycles.json; reviewed 4 November 2026. https://apiopscycles.com/cycles/capability-productization-cycle . Method: APIOps Cycles / Osaango Ltd, CC-BY-SA 4.0. # 10. 6. Readiness: decide from evidence Canonical station: Capability Readiness Assurance. Use the capability readiness checklist, compliance/governance guide and service-quality checklist. Review design, contract or service definition, tests, operations, permissions, monitoring, support, fallback, lifecycle, risk and ownership. This is a teaching selection, not the complete canonical checklist. The supplier-payment status capability is a newly authored fictional teaching example, not a client implementation or measured outcome. Figures, service promises and release criteria are illustrative proposals requiring validation. Working summaries are not reproductions of canonical canvas templates. Source: apiops-cycles-method-data 4.2.1, src/data/method/cycles.json and en/labels.cycles.json; reviewed 4 November 2026. https://apiopscycles.com/cycles/capability-productization-cycle . Method: APIOps Cycles / Osaango Ltd, CC-BY-SA 4.0. # 11. 7. Publish a capability people can adopt Canonical station: Capability Publishing & Enablement. Publish so intended consumers can discover, understand, request access, onboard, use and get support. Resources include publishing/discovery, consumer onboarding, service-agreement and versioning/lifecycle guides. Use a catalogue entry and service agreement appropriate to the selected style. The supplier-payment status capability is a newly authored fictional teaching example, not a client implementation or measured outcome. Figures, service promises and release criteria are illustrative proposals requiring validation. Working summaries are not reproductions of canonical canvas templates. Source: apiops-cycles-method-data 4.2.1, src/data/method/cycles.json and en/labels.cycles.json; reviewed 4 November 2026. https://apiopscycles.com/cycles/capability-productization-cycle . Method: APIOps Cycles / Osaango Ltd, CC-BY-SA 4.0. # 12. 8. Measure value and improve the service Canonical station: Capability Monitoring & Improvement. Monitor value, outcomes, adoption, reuse, service health, consumer experience, cost, sustainability and lifecycle needs. Establish a baseline, data source, owner and review cadence before interpreting changes. Metrics above are proposals; no measured benefit or target is claimed. The supplier-payment status capability is a newly authored fictional teaching example, not a client implementation or measured outcome. Figures, service promises and release criteria are illustrative proposals requiring validation. Working summaries are not reproductions of canonical canvas templates. Source: apiops-cycles-method-data 4.2.1, src/data/method/cycles.json and en/labels.cycles.json; reviewed 4 November 2026. https://apiopscycles.com/cycles/capability-productization-cycle . Method: APIOps Cycles / Osaango Ltd, CC-BY-SA 4.0. # 13. Choose a cycle view for the work ahead The method catalog defines four cycle views over shared stations. These descriptions explain their relationship in the fictional example; they do not require executing every cycle as a sequential project phase. The supplier-payment status capability is a newly authored fictional teaching example, not a client implementation or measured outcome. Figures, service promises and release criteria are illustrative proposals requiring validation. Working summaries are not reproductions of canonical canvas templates. Source: apiops-cycles-method-data 4.2.1, src/data/method/cycles.json and en/labels.cycles.json; reviewed 4 November 2026. https://apiopscycles.com/cycles/capability-productization-cycle . Method: APIOps Cycles / Osaango Ltd, CC-BY-SA 4.0. # 14. Use canvases to make decisions visible Resource selection follows recommendedResources in the canonical capability cycle definition. Full canvas names and links: https://apiopscycles.com/resources/capability-hypothesis-canvas ; https://apiopscycles.com/resources/capability-value-proposition-canvas ; https://apiopscycles.com/resources/capability-business-model-canvas ; https://apiopscycles.com/resources/capability-consumer-producer-requirements-canvas ; https://apiopscycles.com/resources/capability-architecture-decision-canvas ; https://apiopscycles.com/resources/capability-solution-design-canvas ; https://apiopscycles.com/resources/capability-readiness-operations-canvas . Canvas attribution: APIOps Cycles / Osaango Ltd; preserve notices in the actual templates. The supplier-payment status capability is a newly authored fictional teaching example, not a client implementation or measured outcome. Figures, service promises and release criteria are illustrative proposals requiring validation. Working summaries are not reproductions of canonical canvas templates. Source: apiops-cycles-method-data 4.2.1, src/data/method/cycles.json and en/labels.cycles.json; reviewed 4 November 2026. https://apiopscycles.com/cycles/capability-productization-cycle . Method: APIOps Cycles / Osaango Ltd, CC-BY-SA 4.0. # 15. Start with one capability and its consumers Suggested workshop facilitation sequence. Invite the capability owner, producer, intended consumers and architecture/operations representatives. Capture unknowns rather than inventing evidence. The method entry criteria are business goals defined and stakeholder approval; exit criteria are value proposition validated, architecture patterns validated, capability readiness confirmed and capability published for reuse. The supplier-payment status capability is a newly authored fictional teaching example, not a client implementation or measured outcome. Figures, service promises and release criteria are illustrative proposals requiring validation. Working summaries are not reproductions of canonical canvas templates. Source: apiops-cycles-method-data 4.2.1, src/data/method/cycles.json and en/labels.cycles.json; reviewed 4 November 2026. https://apiopscycles.com/cycles/capability-productization-cycle . Method: APIOps Cycles / Osaango Ltd, CC-BY-SA 4.0. # 16. Make the next reuse easier Close with an actionable next step. Method exit criteria provide the readiness anchors; the slide is a practical summary, not a replacement for those criteria. The website provides downloadable canonical resources and this deck’s source, PPTX, PDF and Reveal.js versions. The supplier-payment status capability is a newly authored fictional teaching example, not a client implementation or measured outcome. Figures, service promises and release criteria are illustrative proposals requiring validation. Working summaries are not reproductions of canonical canvas templates. Source: apiops-cycles-method-data 4.2.1, src/data/method/cycles.json and en/labels.cycles.json; reviewed 4 November 2026. https://apiopscycles.com/cycles/capability-productization-cycle . Method: APIOps Cycles / Osaango Ltd, CC-BY-SA 4.0.