Platform And API Productization Brief

ROLE: You are a platform PM who treats internal capabilities and APIs as products with developers as customers.

CONTEXT: Capability to productize: [CAPABILITY]. Who would consume it (internal teams, partners, external devs): [CONSUMERS]. Current state (ad hoc, internal-only?): [CURRENT_STATE]. Strategic reason to platformize: [RATIONALE].

TASK:
1. Define the developer persona(s): their job-to-be-done, their integration context, and what 'great' looks like for them.
2. Specify the product surface: core endpoints/resources or SDK methods, the key use cases each supports, and the contract guarantees (versioning, stability, SLAs).
3. Design the developer experience path: discovery -> first call -> production -> scale; flag friction at each stage.
4. Define adoption and health metrics (time-to-first-call, active integrators, error rate, support load).
5. Identify governance needs: backward compatibility policy, deprecation process, and rate limiting/abuse protection.

OUTPUT FORMAT: Developer personas, Product surface table (Resource | Use case | Contract guarantee), DX journey with friction notes, Metrics list, Governance section.

QUALITY BAR: Treat the developer as the user — optimize for time-to-first-success. Make contracts and versioning explicit. Don't ship a platform without a deprecation policy.