Practical PM artifacts

Product Management Templates

Choose the artifact for the decision you need to make. This hub includes editable templates, generators, decision tools, and reusable examples where those are the stronger way to solve the job.

Use the lightest artifact that supports the decision. A small, well-understood change may need only a short brief and clear acceptance criteria; a larger ambiguous initiative may justify deeper discovery, strategy, prioritization, a PRD, and launch planning.

Common starting points

Start from the product decision, not the document name

Each card shows what the artifact produces, what to bring, and what a good finished result looks like. Full fill-in detail stays on the linked template or tool page.

GeneratorHub summary

Problem Statement Generator

Frame the user, goal, barrier, current workaround, impact, evidence, and open questions without smuggling a preferred feature into the problem.

Best for
The team has observations or evidence, but the problem is still too vague or solution-led to prioritize well.
You get
Problem statement, user-needs view, How Might We prompts, evidence summary, quality checks, and exportable Markdown/CSV/JSON.
Good finished shape (hypothetical example)
One paragraph naming the user, goal, barrier, and current workaround, plus evidence notes and 1–2 open questions, with no feature hidden in the problem sentence.
Frame the problem →

Opens the full generator with examples, quality checks, and export.

Interactive templateHub summary

Product Strategy Template

Make explicit choices about target customer, chosen problem, strategic bets, non-goals, success signals, assumptions, and risks.

Best for
You need a product direction that constrains later roadmap and prioritization decisions, not another list of goals or features.
You get
Editable one-page strategy with quick/deep modes, hypothetical examples, quality checks, sharing, Markdown/JSON/CSV export, and print/PDF.
Good finished shape (hypothetical example)
One target, one diagnosis, one rejected alternative, 2–3 bets, explicit non-goals, and one success signal with what would trigger reconsideration.
Build the strategy →

Opens the full interactive template with examples, quality checks, and export.

Decision toolHub summary

Product Prioritization Tool

Compare problems, opportunities, features, experiments, initiatives, or bets while making impact, evidence, effort, strategic fit, assumptions, and hard constraints visible.

Best for
Several credible candidates compete for limited capacity and the team needs a defensible choice rather than an automatic score winner.
You get
Decision-support workspace plus routes to the dedicated RICE, ICE, MoSCoW, and Kano tools when one method fits the decision.
Good finished shape (hypothetical example)
3–5 candidates compared on impact, evidence, effort, strategic fit, and constraints, with assumptions visible and one explicit “not now” choice.
Prioritize the bets →

Opens the full decision tool with examples, quality checks, and export.

Interactive templateHub summary

Product Roadmap Template

Turn selected product investments into a clear direction with outcomes, themes, initiatives, horizons, confidence, dependencies, risks, and explicit non-priorities.

Best for
You have made enough investment choices to communicate what matters and in what direction or sequence, while keeping uncertainty visible.
You get
Editable roadmap with hypothetical examples, browser autosave, Markdown copy/download, CSV download, and print.
Good finished shape (hypothetical example)
2–3 themes with initiatives in Now/Next/Later or quarter horizons, each with confidence, dependencies, and explicit non-priorities.
Build the roadmap →

Opens the full interactive template with examples, quality checks, and export.

GeneratorHub summary

PRD Template & Generator

Capture the problem, outcome, scope, requirements, constraints, dependencies, risks, assumptions, open questions, measurement, and rollout context for a selected initiative.

Best for
The initiative has enough product justification to need deeper definition for review and delivery; use a Product Brief instead when the opportunity is still contested.
You get
Copyable blank PRD, structured generator, hypothetical examples, quality warnings, Markdown/JSON export, requirements CSV, sharing, and browser autosave.
Good finished shape (hypothetical example)
Problem, outcome, scope boundaries, 5–8 requirements with source context, blocking vs non-blocking open questions, and measurement plus rollout context.
Open the PRD workflow →

Opens the full generator with examples, quality checks, and export.

Interactive templateHub summary

Product Launch Plan Template

Coordinate the launch decision, audience cohorts, scope, rollout stages, dependencies, communications, risks, success signals, launch-day controls, and post-launch decisions.

Best for
A built or near-built change needs cross-functional launch coordination beyond the narrower release go/no-go checklist.
You get
Editable Launch Decision & Coordination Ledger with four hypothetical examples, browser persistence, Launch Plan Audit, versioned JSON import/export, Markdown/CSV, and print/PDF.
Good finished shape (hypothetical example)
Audience cohorts, 2–3 rollout stages with advance/hold conditions, owners, communications, risks, 2–3 success signals, and post-launch decisions.
Build the launch plan →

Opens the full interactive template with examples, quality checks, and export.

Artifact decision guide

What decision are you trying to make?

Pick the closest question. You can move to a heavier artifact later if the uncertainty or coordination cost actually grows.

Is the problem still fuzzy or solution-led?

Frame the problem before choosing the feature.

Use Problem Statement Generator when
You have observations or stakeholder requests, but the user, barrier, and evidence are still vague or a preferred feature is already assumed.
When not to use it
Skip when the initiative is already selected and the team needs delivery detail, use a Product Brief or PRD instead.
Problem Statement Generator →

Need to decide where the product should focus?

Make the strategic choices and non-goals explicit.

Use Product Strategy Template when
You need a direction that constrains later prioritization and roadmap choices, with explicit trade-offs and success signals.
When not to use it
Skip when you only need to communicate sequence or coordinate delivery, use a Roadmap, Brief, or PRD instead.
Product Strategy Template →

Several credible bets compete for capacity?

Compare impact, evidence, effort, strategy, and constraints.

Use Product Prioritization Tool when
Multiple defensible candidates compete for limited capacity and you need a reviewable choice, not an automatic score winner.
When not to use it
Skip when one initiative is already chosen, use a Brief or PRD, or when the job is sequencing an approved set, which belongs on a Roadmap.
Product Prioritization Tool →

Need to communicate investment direction and sequence?

Turn selected bets into outcomes, themes, initiatives, and horizons.

Use Product Roadmap Template when
Investment choices are made enough to show direction, themes, horizons, confidence, and explicit non-priorities.
When not to use it
Skip when the strategic choice itself is still contested, use Strategy first, or when the work is near release and needs rollout coordination, which belongs in a Launch Plan.
Product Roadmap Template →

Need lightweight alignment before detailed requirements?

Keep the opportunity, outcome, direction, scope, and unknowns visible.

Use Product Brief Template when
An opportunity is credible enough to align on, but detailed requirements would create premature certainty.
When not to use it
Skip when the initiative is selected and reviewers need requirements, constraints, and delivery context, use a PRD instead.
Product Brief Template →

Need deeper definition for a selected initiative?

Capture requirements and constraints without inventing missing decisions.

Use PRD Template & Generator when
The initiative has enough justification to need reviewable requirements, scope boundaries, and open-question ownership.
When not to use it
Skip when the opportunity is still contested or discovery is open, use a Brief or Problem Statement first rather than adding PRD ceremony.
PRD Template & Generator →

Need implementation-ready user behavior?

Express the user need, then clarify observable conditions of satisfaction.

Use User Stories + Acceptance Criteria when
The behavior is understood well enough to slice one delivery-sized need with observable acceptance conditions.
When not to use it
Skip when discovery is still open, do not use a polished story as a substitute for problem framing or a Brief/PRD decision.
User Stories + Acceptance Criteria →Acceptance Criteria examples

Need to coordinate rollout and launch readiness?

Align audience, rollout, owners, communications, risks, and measurement.

Use Product Launch Plan Template when
A built or near-built change needs cross-functional rollout, readiness, communication, and post-launch decision ownership.
When not to use it
Skip when you are still choosing investment direction, use Strategy, Prioritization, or Roadmap, or when you only need a narrow release go/no-go check.
Product Launch Plan Template →

One possible workflow

Let each artifact answer one decision, then stop documenting when the next artifact adds no value

A complex initiative may move through the sequence below. It is a map, not process law. Use only the artifacts your team needs, and skip any document that would add ceremony without reducing uncertainty or coordination cost.

ProblemStrategyPrioritizeRoadmapBriefPRDUser StoryAcceptance CriteriaLaunch Plan

Scope check: add a document only when it changes the decision

  • • One artifact answers one decision. Name the decision before opening the template.
  • • If the next artifact would not reduce uncertainty or coordination cost, stop. A finished Brief plus clear acceptance criteria beats an invented PRD.
  • • Keep unknowns visible. Do not promote a Brief to a PRD, or a story to a full initiative plan, to hide missing evidence.
  • • Delete sections that do not help this decision. An unused template section is ceremony, not rigor.
  • • Revisit heavier artifacts only when uncertainty or coordination cost actually grows.

Finished signal: what “done” looks like at hub level

  • • Problem: no feature in the problem sentence; evidence and open questions are listed.
  • • Strategy: the choice rules out something plausible and names a success signal.
  • • Prioritization: assumptions are visible and one credible option is explicitly not now.
  • • Roadmap and Brief: confidence, dependencies, and non-goals are explicit.
  • • PRD, story, and launch plan: requirements have provenance, behavior is observable, and owners plus next decisions are named.

These are hub-level signals only. Field-by-field guidance and complete worked examples live on each child template or tool page.

Artifact boundaries

Similar artifacts should not do the same job

Use these distinctions when a team starts creating two documents that answer the same question.

Strategy vs Roadmap

Strategy makes choices about where to focus and why. A roadmap communicates the investments and sequence that follow from those choices.

  • • Choose Strategy when the team still disagrees about target, diagnosis, trade-offs, or what to rule out.
  • • Choose Roadmap when direction is settled enough to show themes, horizons, confidence, and explicit non-priorities.
  • Stop: Stop if the roadmap is being used to avoid the strategic choice, return to Strategy until the trade-off is explicit.
StrategyRoadmap

Brief vs PRD

A Product Brief is lightweight alignment while important uncertainty remains. A PRD adds deeper requirements and delivery context after the initiative is selected.

  • • Choose a Brief when evidence, assumptions, counter-evidence, or the next decision still need to stay visible.
  • • Choose a PRD when the opportunity is selected and reviewers need requirements, scope boundaries, and delivery context.
  • Stop: Stop if the PRD would invent missing decisions, keep the Brief until the opportunity earns deeper definition.
Product BriefPRD

PRD vs User Story

A PRD preserves initiative-level problem, outcome, scope, constraints, and requirements. A user story expresses one delivery-level user need and outcome.

  • • Choose a PRD when the initiative needs shared problem, outcome, scope, and requirement context for review and delivery.
  • • Choose a user story when the team is ready to refine one delivery-sized behavior with clear value and boundaries.
  • Stop: Stop if one polished story is carrying the whole initiative rationale, restore the PRD decision context first.
PRDUser Story

User Story vs Acceptance Criteria

The story states who needs what and why. Acceptance criteria state the observable conditions that must be true for that behavior to be accepted.

  • • Use the story to keep the user, need, and outcome visible in one sliceable unit.
  • • Add acceptance criteria when behavior, edge cases, permissions, or failure states are still ambiguous.
  • Stop: Stop adding criteria when they restate the story instead of clarifying observable pass/fail conditions.
User StoryAcceptance Criteria

Roadmap vs Launch Plan

A roadmap communicates investment direction and uncertainty. A launch plan coordinates rollout, readiness, communication, risk, and post-launch decisions for work that is approaching release.

  • • Choose a Roadmap when stakeholders need direction, sequence, and uncertainty across multiple investments.
  • • Choose a Launch Plan when a built or near-built change needs audience cohorts, rollout stages, owners, and readiness checks.
  • Stop: Stop if the launch plan is being filled before scope and rollout reality exist, keep the Roadmap until the release candidate is concrete.
RoadmapLaunch Plan

Understand

Understand the problem

Turn evidence and current user behavior into a problem the team can inspect before choosing a solution.

GeneratorCore artifact

Problem Statement Generator

Frame the user, goal, barrier, current workaround, impact, evidence, and open questions without smuggling a preferred feature into the problem.

Use when
The team has observations or evidence, but the problem is still too vague or solution-led to prioritize well.
You get
Problem statement, user-needs view, How Might We prompts, evidence summary, quality checks, and exportable Markdown/CSV/JSON.
Frame the problem

Decide

Decide what to build

Make choices about focus, competing investments, product direction, and sequencing without outsourcing judgment to a document or score.

Interactive templateCore artifact

Product Strategy Template

Make explicit choices about target customer, chosen problem, strategic bets, non-goals, success signals, assumptions, and risks.

Use when
You need a product direction that constrains later roadmap and prioritization decisions, not another list of goals or features.
You get
Editable one-page strategy with quick/deep modes, hypothetical examples, quality checks, sharing, Markdown/JSON/CSV export, and print/PDF.
Build the strategy
Decision toolCore artifact

Product Prioritization Tool

Compare problems, opportunities, features, experiments, initiatives, or bets while making impact, evidence, effort, strategic fit, assumptions, and hard constraints visible.

Use when
Several credible candidates compete for limited capacity and the team needs a defensible choice rather than an automatic score winner.
You get
Decision-support workspace plus routes to the dedicated RICE, ICE, MoSCoW, and Kano tools when one method fits the decision.
Prioritize the bets
Interactive templateCore artifact

Product Roadmap Template

Turn selected product investments into a clear direction with outcomes, themes, initiatives, horizons, confidence, dependencies, risks, and explicit non-priorities.

Use when
You have made enough investment choices to communicate what matters and in what direction or sequence, while keeping uncertainty visible.
You get
Editable roadmap with hypothetical examples, browser autosave, Markdown copy/download, CSV download, and print.
Build the roadmap
Interactive template

PR/FAQ Template

Write a hypothetical future press release and FAQ, keep facts, assumptions, counter-evidence and open questions separate, and audit unsupported future-state claims before the team commits to detailed definition.

Use when
A customer-first narrative would expose weak assumptions, contradictions or missing evidence before the team commits to detailed definition or delivery.
You get
Editable PR/FAQ with a future-state claim audit, evidence and assumption map, customer and internal FAQ, Working-Backwards Decision Contract, qualified handoffs, browser autosave and Markdown/JSON export.
Build the PR/FAQ

Define

Define the work

Add only the product context and behavioral detail needed for the team to align, refine, and deliver the selected work.

Interactive templateCore artifact

Product Brief Template

Create lightweight alignment around one opportunity: connect material claims to real evidence, keep counter-evidence, assumptions and risks visible, and record the next decision before detailed requirements.

Use when
An opportunity is credible enough to align on, but writing detailed requirements would create premature certainty.
You get
Editable brief with a Brief Claim & Evidence Map, Investment Decision Audit (no score), PRD Handoff Contract, synthetic examples, browser autosave, Markdown/JSON export and print/PDF.
Build the product brief
GeneratorCore artifact

PRD Template & Generator

Capture the problem, outcome, scope, requirements, constraints, dependencies, risks, assumptions, open questions, measurement, and rollout context for a selected initiative.

Use when
The initiative has enough product justification to need deeper definition for review and delivery; use a Product Brief instead when the opportunity is still contested.
You get
Copyable blank PRD, structured generator, hypothetical examples, quality warnings, Markdown/JSON export, requirements CSV, sharing, and browser autosave.
Open the PRD workflow
GeneratorCore artifact

User Story Template & Generator

Turn an understood user need into a delivery-level story with contextual acceptance criteria while catching vague actors, solution-first wording, and oversized stories.

Use when
The team understands the behavior well enough to refine a delivery-sized need; do not use a polished story as a substitute for discovery.
You get
User story pack with acceptance criteria, quality checks, and Markdown/JSON/CSV/Gherkin export.
Create a user story
Guide + template

Acceptance Criteria Examples & Templates

Write observable conditions that clarify what must be true for a story or requirement, using plain language or Given/When/Then only when it improves clarity.

Use when
The need is understood but behavior, edge cases, permissions, failure states, or conditions of satisfaction are still ambiguous.
You get
Reusable plain-language and Gherkin patterns, realistic examples, edge-case guidance, and a direct handoff to the User Story Generator.
See criteria examples

Ship

Ship the work

Coordinate rollout, readiness, communication, risk, measurement, and the decisions that follow release.

Interactive templateCore artifact

Product Launch Plan Template

Coordinate the launch decision, audience cohorts, scope, rollout stages, dependencies, communications, risks, success signals, launch-day controls, and post-launch decisions.

Use when
A built or near-built change needs cross-functional launch coordination beyond the narrower release go/no-go checklist.
You get
Editable Launch Decision & Coordination Ledger with four hypothetical examples, browser persistence, Launch Plan Audit, versioned JSON import/export, Markdown/CSV, and print/PDF.
Build the launch plan

Onboard

Career & onboarding

Use a working plan when a PM role transition or new-role ramp benefits from explicit learning and ownership goals.

Interactive template

Product Manager 30/60/90 Day Plan

Structure a new PM role around learning context, reducing uncertainty, contributing useful decisions, and taking increasing ownership without inventing universal milestones.

Use when
A new-role ramp benefits from an explicit working hypothesis you can review with your manager and revise as the real context becomes clearer.
You get
Editable onboarding plan with practical prompts and an adaptable 30/60/90 structure rather than a guaranteed performance formula.
Build the onboarding plan

Artifact skill is not Product judgment

Learn the decision, then use the lightest artifact that makes it visible

Templates help you capture a decision. Courses and practice help you make a better one. If the gap is discovery, strategy, prioritization, metrics, or execution judgment rather than document structure, continue into the relevant learning path instead of adding more paperwork.

Follow the PM learning pathAssess PM skillsLearn PM foundations