OpenKnowledgeBank
Bundle catalog

roles bundle

Growth Product Manager

A free, open-source set of 10 Markdown files that gives an AI assistant practical guidance for the Growth Product Manager role.

Use the Growth Product Manager bundle to assess product-growth opportunities, prioritize experiments, review instrumentation and guardrails, and prepare a rollout brief that keeps user evidence, assumptions, and missing verification separate.

Project-reviewed beta
Preview contents Download bundle Inspect source

10 Markdown files · 1,004 words · no signup · CC-BY-4.0

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

Growth Product Manager

- Frame the requested decision and required evidence. - Reconcile domain records, definitions, dates, states, and owners.

Read the file

Overview

Growth Product Manager Overview

ONET marketing-manager context supports customer, demand, strategy, and program-effectiveness work; the mapping is approximate and does not define product-management authority.

Read the file

Workflow

Growth Product Manager Source-Aware Triage

1. State the requested decision or deliverable. 2. Inventory evidence: product outcome and strategy, user research, event and identity schema, baseline and segment definitions, experiment.

Read the file

Template

Product growth experiment and rollout brief

State the decision, recommendation, or draft purpose.

Read the file

Is this bundle right for your task?

Who it is for

  • Growth product managers and cross-functional product, design, engineering, data, and lifecycle teams

When to use it

  • A growth opportunity or experiment needs to be prioritized against a stated product outcome and available user evidence.
  • An experiment proposal needs baseline, segment, event-schema, guardrail, technical-constraint, rollout, and rollback review.
  • Stakeholders need a review-ready experiment and rollout brief rather than an unsupported roadmap recommendation.

What you need to provide

  • Product outcome and strategy, user research, baseline and segment definitions, event and identity schema, and current experiment state.
  • Experiment design and guardrails, technical constraints, ownership, rollout and rollback controls, and known approval boundaries.

Tasks and expected outputs

Questions it helps answer

  • Prepare product growth experiment and rollout brief without fabricating local facts.
  • Separate verified, provided, assumed, and missing evidence.
  • Produce review-ready decisions with explicit verification and approval boundaries.

What it helps produce

  • Product growth experiment and rollout 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.

Load the Growth Product Manager bundle and provide the target outcome, user research, current funnel baseline, segment definitions, event schema, candidate experiment, engineering constraints, and rollout guardrails. Ask the agent to label verified and missing evidence, assess the proposal, and produce a product-growth experiment and rollout brief for accountable review.

Context path: bundles/roles/growth-product-manager

What the bundle includes

Frameworks

  • source-evidence matrix
  • product-growth evidence matrix
  • qualified-review gate

Evaluations

  • Growth Product Manager source-awareness 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.

O*NET OnLine — Summary / 11 2021.00 Role or occupation reference for Growth Product Manager scope and source checks.

Limitations and safe use

Do not use this for

  • Inferring user needs, event names, baseline performance, experiment outcomes, technical feasibility, feature state, or roadmap commitments without local evidence and accountable approval.

Known limitations

  • Treat the occupational mapping as approximate; product goals, user evidence, event schemas, experiment state, technical constraints, and outcomes require local evidence.
  • Task-specific work requires current evidence for product outcome and strategy, user research, event and identity schema, baseline and segment definitions, experiment design and guardrails, technical constraints, rollout and rollback controls.
  • Do not infer user needs, event names, baseline metrics, experiment results, technical feasibility, feature state, roadmap commitment.

Safety notes

  • Minimize personal, customer, employee, financial, credential, and other sensitive data.
  • Require explicit confirmation before feature, experiment, tracking, customer, data, or production rollout changes.
  • Route legal, privacy, security, compliance, financial, employment, and other qualified judgments to accountable reviewers.

Next step

Inspect it before relying on it

Download the bundle for use, review its source files and evidence, or read the agent guidance. If the project is useful, starring the repository helps others discover it.

Download Review source Agent guidance Star on GitHub