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
Product Leadership Role Guide
Start with the approved job description, level framework, organization chart, product topology, and decision records.
Read the fileOverview
Overview
Group Product Manager and Director of Product are related but non-interchangeable product-leadership archetypes.
Read the fileQuality rubric
Group Product Manager Director of Product Quality Check
- Archetype grounding: Distinguishes GPM and Director patterns without presenting one employer's ladder as universal.
Read the fileBundle file
Role Review Workflow
1. Record the request, intended audience, decision to support, organization and product context, evidence supplied, and evidence date. 2.
Read the fileIs this bundle right for your task?
Who it is for
- People performing or supporting Group Product Manager / Director of Product work, plus teams reviewing its decisions and outputs
- Teams working in software, SaaS, digital products
When to use it
- A Group Product Manager / Director of Product 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
- distinguish GPM and Director role archetypes
- define product-leadership scope and interfaces
- review decision rights and measures without inventing authority
What it helps produce
- role charter draft
- product-area and portfolio scope map
- leadership decision-rights review
- metric definition and accountability 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 Group Product Manager / Director of Product work by producing role charter draft with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with GitLab, then confirm that the reference is current and applicable. Inspect Product Leadership Role Guide before drafting.
Context path: bundles/roles/group-product-manager-director-of-product
What the bundle includes
Frameworks
- GPM-Director archetype matrix
- leadership-scope and interface map
- evidence-and-decision-rights ledger
Evaluations
- Group Product Manager Director of Product quality 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
- Role-support bundle only; not authority to set product strategy, roadmaps, staffing, performance decisions, organization design, budget, P&L, procurement, access, metrics, pricing, releases, or external commitments.
- GPM and Director titles vary by organization size, product topology, management model, geography, and career framework; neither title establishes an universal span or mandate.
- O*NET 11-2021.00, SOC 11-2021, ISCO-08 1221, and the ICT product manager ESCO mapping are broad or adjacent taxonomy proxies, not exact standards for these leadership levels.
Safety notes
- Protect roadmaps, customer and employee information, strategy, product telemetry, pricing, launches, incidents, contracts, workforce plans, performance records, and commercial information.
- Verify the local job framework, reporting line, product scope, decision rights, systems, access, staffing authority, budget authority, metric definitions, owners, and approval paths before relying on any deliverable.
- Require explicit confirmation before personnel, investment, roadmap, release, system, access, customer-contact, procurement, pricing, or communication actions.