Stakeholder guide

Platform Architect

Guides platform, integration, scalability, and architecture decisions that shape how the capability or API is built and operated.

Relevant cycles

API Productization Cycle

The API-focused APIOps Cycles journey for productizing, designing, delivering, publishing, and improving APIs.

Automation Cycle

A cycle for identifying, designing, delivering, enabling, and improving automation opportunities.

Relevant stations

  • Strategy

    Frame the business need as a reusable capability before choosing the implementation style.

  • Architecture & Platform Decisions

    Use requirements and constraints to decide the right architecture pattern and enabling platform capabilities.

  • Solution & Interface Design

    Design the interface contract and interaction model after the architecture choice is justified.

  • Delivery & Operations

    Deliver the selected implementation style with appropriate engineering, testing, security, automation, and operational practices.

  • Quality & Readiness Assurance

    Audit the capability interface contract, controls, support model, observability, documentation, and lifecycle readiness before release.

  • Monitoring & Improvement

    Monitor usage, reliability, data quality, consumer outcomes, operational cost, and reuse opportunities after release.

Decisions and outputs

Decisions

  • Map the customer or partner journey that creates the capability need and reveals tasks, pains, gains, inputs, outputs, and decision points.
  • Define the core entities, attributes, relationships, ownership, and business rules that the capability must respect.
  • Use the Capability Value Proposition Canvas to capture consumer tasks, gains, pains, and reusable capability features without naming the delivery technology too early.
  • Use the Capability Business Model Canvas to clarify ownership, partners, channels, costs, benefits, support, and lifecycle expectations for the reusable capability.
  • Use shared journey, domain, value proposition, and business model canvases to gather technology-agnostic requirements and decide whether the capability should be reusable.
  • Integration and API work often jumps too quickly to a technical pattern. This station keeps the team focused on the business journey, domain meaning, value, reuse potential, ownership, and viability before selecting APIs, events, files, streams, data products, or direct integration.

Outputs

  • A technology-agnostic capability opportunity statement
  • Shared understanding of consumers, producers, domain concepts, and reuse potential
  • A capability value proposition and business model before architecture selection
  • design-artifact
  • documentation
  • research
  • roadmap
  • A justified architecture choice

Recommended resources

Facilitate as Platform Architect

Use these prepared prompts alongside the stakeholder decisions, outputs, stations, and resources summarized above.

AI facilitation

Prompt pack

Facilitate a station with Platform Architect

facilitate-station

Stakeholder: Platform Architect
Cycles: Capability Productization Cycle, API Productization Cycle, Integration Productization Cycle, Automation Cycle
Stations: Strategy, Architecture & Platform Decisions, Solution & Interface Design, Delivery & Operations, Quality & Readiness Assurance, Monitoring & Improvement
Resources and canvases: Customer Journey Canvas, Domain Canvas, Capability Value Proposition Canvas, Capability Business Model Canvas, Business Impact Canvas, Locations Canvas, Capacity Canvas, Interaction Canvas, API Value Proposition Canvas, API Business Model Canvas, REST Canvas, Event Canvas, GraphQL Canvas

Act as an APIOps Cycles facilitator. Use the selected station questions, entry criteria, exit criteria, stakeholders, and related resources to guide the discussion. Produce decisions, evidence gaps, and next steps.