Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Role guide
Chief Product Officer (CPO) source-backed Guide
Defines source-backed product vision, portfolio strategy, operating model, prioritization, and executive review, evidence handling, and action boundaries.
Read the fileOverview
Chief Product Officer (CPO) overview
Use this bundle to prepare source-backed product vision, portfolio strategy, operating model, prioritization, and executive review and a review-ready product portfolio decision brief.
Read the fileWorkflow
Chief Product Officer (CPO) source-backed triage
1. State the requested decision or artifact. 2. Inventory evidence: company strategy, users, markets, research, product evidence, and decision criteria; product portfolio, lifecycle.
Read the fileTemplate
product portfolio decision brief
Review-ready artifact for product vision, portfolio strategy, operating model, prioritization, and executive review, evidence quality, verification, and controlled actions.
Read the fileIs this bundle right for your task?
Who it is for
- People performing or supporting Chief Product Officer (CPO) work, plus teams reviewing its decisions and outputs
- Teams working in Digital products, Technology
When to use it
- A Chief Product Officer (CPO) task needs a structured plan, evidence checklist, or review-ready output.
- A recommendation needs its assumptions, owners, risks, dependencies, and success measures made explicit.
What you need to provide
- The task objective, intended audience, working context, constraints, source material, and decision owner.
- Relevant reports, exports, examples, policies, prior decisions, and success measures available for the task.
Tasks and expected outputs
Questions it helps answer
- Prepare a product portfolio decision brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce a review-ready decision with explicit verification and approval boundaries.
What it helps produce
- product portfolio decision brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the task objective, intended audience, working context, constraints, source material, and decision owner. Ask the agent to approach Chief Product Officer (CPO) work by producing product portfolio decision brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with O*NET OnLine — Summary / 11 1011.00, then confirm that the reference is current and applicable. Inspect Chief Product Officer (CPO) source-backed Guide before drafting.
Context path: bundles/roles/chief-product-officer-cpo
What the bundle includes
Frameworks
- source-evidence matrix
- product vision, portfolio strategy, operating model, prioritization, and executive review matrix
- qualified-review gate
Evaluations
- Chief Product Officer (CPO) source verification check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Treating the bundle as a substitute for organization-specific authority, firsthand evidence, or accountable review.
Known limitations
- Use the listed authoritative sources for general role or tool behavior; local configuration, records, values, states, permissions, and results require inspected evidence.
- Task-specific work requires current evidence for company strategy, users, markets, research, product evidence, and decision criteria; product portfolio, lifecycle, metrics, experiments, economics, competitive evidence, capacity, dependencies, roadmap, risks, accessibility, privacy, security, legal review, and approvals.
- Do not infer customer need, product-market fit, metric result, priority, forecast, competitive position, roadmap feasibility, or business impact.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, privileged, health, student, and other sensitive data.
- Require explicit confirmation before actions that approve strategy or roadmap, commit capacity or budget, launch or retire a product, change customer commitments, or make investor or market claims.
- Route legal, privacy, security, compliance, financial, employment, clinical, safety, and other qualified judgments to an evidenced accountable reviewer.