Platform And API Productization Brief
Frames an internal capability as a productized API or platform with developer personas, contracts, and adoption path.
Prompt
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.
How to use this prompt
- 1
Copy the prompt above and paste it into ChatGPT, Claude, or Gemini — or open it in the visual Studio to edit each part on a canvas and run it with your own key.
- 2
Replace any bracketed placeholders with your specifics. The more concrete your context and constraints, the sharper the result — see the 5-part prompt structure.
- 3
Run it, then refine. Ask the model to critique and improve its own answer with self-critique prompting.
Techniques in this prompt
Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.
Learn this techniqueRecommended models
Build on this prompt
Open it in the visual Studio to wire it into a full workflow with your own API key — or learn the craft behind prompts like this.
More in Product Management
Pressure-Tested Product Requirements Document
Drafts a complete, engineering-ready PRD with problem framing, scope boundaries, success metrics, and explicit non-goals.
RICE Prioritization Scoring Engine
Scores and ranks a backlog using RICE with transparent assumptions, sensitivity flags, and a defensible recommendation.
Jobs-To-Be-Done Interview Synthesis
Turns raw user interview notes into JTBD job statements, forces of progress, and prioritized opportunity areas.
Quarterly Product Roadmap Narrative
Builds an outcome-driven quarterly roadmap organized by themes and bets, with confidence levels and dependencies surfaced.