Claude for Product Managers: Roadmap, Specs, and User Research

Writing PRDs (Product Requirements Documents)

From Brief to Complete PRD

Write a PRD for the following feature.

Brief:
- Problem: [2-3 sentences describing the user problem]
- Audience: [primary persona + estimated volume]
- Constraints: [budget, timeline, technical dependencies]
- Success metric: [primary KPI to impact]

PRD structure:
1. Context and problem
2. Objectives and success metrics (SMART)
3. Target audience and personas
4. User stories (format "As a... I want... so that...")
5. Functional specifications (detailed expected behavior)
6. Non-functional specifications (performance, security, accessibility)
7. Edge cases and error scenarios
8. Design mockup requirements (text description)
9. Technical dependencies
10. Rollout plan (phases, feature flags)
11. Out of scope (what is NOT in this version)
12. Open questions

Be exhaustive on edge cases — that's often the missing part of PRDs.

Example: PRD for a Notification Feature

Brief: Users complain about missing important updates on their projects.
Audience: 15,000 daily active users, primarily project managers.
Constraint: Delivery in 6 weeks, team of 3 developers.
Metric: Increase D7 retention rate from 45% to 55%.

Claude generates a 3-4 page PRD covering:

• →8 user stories with acceptance criteria
• →Notification matrix (type × channel × frequency)
• →Edge cases: time zones, do not disturb mode, duplicate notifications
• →3-phase rollout plan with feature flags

Iterating with Stakeholders

A key advantage: you can iterate with Claude in the conversation.

The CTO has questions about the technical section:
1. How to handle notifications for users with 50+ projects?
2. What's the database impact?
3. Can we use WebSockets instead of polling?

Update the "Non-functional Specifications" and "Technical Dependencies"
sections of the PRD to address these questions.

User Stories

Structured Generation

Generate user stories for the [name] feature.

Context: [PRD or feature summary in 3-4 lines]

For each story:
- Format: "As a [persona], I want [action] so that [benefit]"
- Acceptance criteria (3-5 per story, Given/When/Then format)
- Estimated size (S/M/L/XL)
- Priority (Must/Should/Could)
- Dependencies (if applicable)

Organize by epic, then by descending priority.

Refinement and Splitting

This user story is too large (estimated XL by the team):
"As an admin, I want to manage user permissions"

Split it into S or M-sized stories maximum.
Each sub-story must be:
- Independent (deliverable on its own)
- Testable (verifiable acceptance criteria)
- Valuable (delivers user value even without the others)

Propose a logical delivery order.

Feature Prioritization

RICE Framework with Claude

Here is my list of feature candidates for next quarter.

For each feature, I've estimated:
- Reach: number of users impacted
- Impact: low (1), medium (2), high (3)
- Confidence: % certainty on estimates
- Effort: in dev-weeks

Features:
1. [Feature A] - Reach: 5000, Impact: 3, Confidence: 80%, Effort: 4 weeks
2. [Feature B] - Reach: 12000, Impact: 1, Confidence: 90%, Effort: 2 weeks
3. [Feature C] - Reach: 3000, Impact: 3, Confidence: 50%, Effort: 8 weeks
...

Calculate the RICE score for each feature.
Produce a ranked table + reasoned recommendation.
Identify dependencies between features.
Propose an optimal 12-week sequencing.

Framework Comparison

I have 12 features. Apply both RICE AND MoSCoW in parallel.
Compare the results and identify divergences.
Divergences are often the features that deserve the most discussion.

[list features with data]

Competitive Product Analysis

Feature Comparison Matrix

I'm the PM for [my product].
Here are the feature pages of 3 competitors:
- Competitor A: [paste or summarize]
- Competitor B: [paste or summarize]
- Competitor C: [paste or summarize]

Produce:
1. Feature matrix (my product vs. A vs. B vs. C)
   ✅ = available, ⚠️ = partial, ❌ = absent
2. Critical gaps: features ALL competitors have that we don't
3. Differentiators: features only WE have
4. Opportunities: features no one has yet
5. Strategic recommendations (3 actions)

Positioning Analysis

Analyze the product positioning of these 4 competitors based on their homepage and pricing.

For each competitor:
- Main value proposition (1 sentence)
- Target audience
- Price positioning (low-cost, mid-market, premium)
- Perceived strengths
- Potential weaknesses

Produce a recommended positioning map (2 axes) to visualize the landscape.
Suggest a differentiating position for our product.

User Research Synthesis

Interview Analysis

Here are the transcripts from 15 user interviews (30 min each).
Context: we're exploring needs around [topic].

Analyze:
1. Recurring themes (ranked by frequency of appearance)
2. Major pain points (with direct quotes)
3. Expressed needs vs. latent needs
4. Identified user segments (if patterns emerge)
5. Surprising insights (what contradicts our hypotheses)
6. Product recommendations (5 concrete actions)

For each theme, indicate:
- Frequency (X users out of 15 mentioned it)
- Intensity (low/medium/high frustration)
- Most representative quote

[paste the transcripts]

Product Feedback Analysis

Here are 200 user feedbacks collected via our in-app tool this month.
Mix of NPS comments, feature requests, and bug reports.

Produce:
1. Categorization (bug, feature request, UX issue, praise, other)
2. Top 10 themes by volume
3. Sentiment by category
4. Most requested features (with frequency)
5. Correlation: do users with NPS < 7 mention specific themes?
6. Quick wins: high-impact, low-effort improvements

[paste the feedback]

Roadmap Planning

Quarterly Roadmap

Here are the inputs for the Q[quarter] [year] roadmap:
- Strategic objectives: [O1, O2, O3]
- Feature candidates (with RICE scores from backlog)
- Team capacity: [X] available dev-weeks
- Technical debt to address: [list]
- Customer commitments: [if applicable]

Produce:
1. Roadmap proposal — breakdown by month
2. Capacity allocation: features (70%) / tech debt (20%) / exploration (10%)
3. Identified dependencies and risks
4. Deferred features and justification
5. "Narrative" version for stakeholder presentation

Roadmap Communication by Audience

Adapt this roadmap for a 3-slide board presentation:
Slide 1: Executive summary (vision + 3 big bets)
Slide 2: Timeline with milestones and expected metrics
Slide 3: Required resources and risks

[paste the detailed roadmap]

Spec Reviews and Quality

Technical Spec Review

Here are the technical specs written by the engineering team for the [name] feature.
As PM, I want to ensure that:

1. All user stories are covered by the specs
2. Edge cases identified in the PRD are addressed
3. The rollout plan is compatible with the product strategy
4. Success metrics are measurable with the proposed implementation
5. No technical compromises unacceptably impact the user experience

Original PRD: [paste]
Technical specs: [paste]

Produce a gap analysis report with identified discrepancies.

Definition of Done

Create a Definition of Done (DoD) for the [product name] product team.

Context: team of [X] devs, B2B SaaS product, weekly release.

The DoD should cover:
- Code (review, tests, lint)
- Product (specs met, edge cases, accessibility)
- Design (pixel-perfect, responsive, states)
- QA (manual tests, smoke tests, regression)
- Documentation (changelog, help center, release notes)
- Monitoring (alerts, logs, metrics)

Format: actionable checklist directly integrable into Jira/Linear.