Claude for Product Managers

Lesson 1

The PRD Briefing Prompt

PRDs fail for three reasons:

The problem statement is too broad "Users want better notifications" tells an engineer nothing designable
Requirements are ambiguous "The feature should be fast" is not a requirement
Edge cases are missing The happy path is documented; everything else is discovered in QA

Claude can help with all three but only if you brief it with the right inputs first.

Run this before asking Claude to write anything. It surfaces the gaps in your thinking.

I'm going to write a PRD for [feature name]. Before I do, help me pressure-test my brief.

Here's what I know:

PRODUCT: [Describe your product in 2–3 sentences]

USER: [Who has this problem, in their specific job context]

PROBLEM: [What the user currently experiences that is painful, in concrete terms]

PROPOSED SOLUTION: [What we're building]

SUCCESS: [How we'll know it worked]

CONSTRAINTS: [Technical, timeline, or scope limits]

WHAT I DON'T KNOW YET: [Be honest about gaps]

Based on this brief:

1. Is the problem statement specific enough to design a solution for?

2. What questions would an engineer have that my brief doesn't answer?

3. What user scenarios have I not considered?

4. What am I most likely missing?

Example output for Flowdesk's search feature:

Your problem statement "users can't find things" is too broad. Is the core pain about searching across all content or specifically about finding old items? These suggest different solutions.

An engineer would ask: What is the scope of search tasks only, or also comments, files, and templates? Is this real-time or batch-indexed? What happens when there are no results?

You haven't addressed: What happens when a user searches and finds a task they no longer have access to? What's the ranking logic for results?

Most likely missing: The non-happy-path states empty results, partial matches, performance at scale.

This output is more valuable than a first draft. Fix these gaps before writing anything.

Claude for Product Managers

Module 1Introduction

Module 2The Right Mental Model Before You Start

Module 3Prompting That Actually Produces Value

Module 4Writing PRDs That Engineers Actually Use

Module 5User Research: From Raw Data to Product Decisions

Module 6Prioritization: Building the Analytical Case

Module 7Stakeholder Communication That Drives Decisions

Module 8 Building Your PM Workflow System

Module 9Prompt Templates by Use Case

Module 10GLOSSARY: Terms You'll Encounter

The PRD Briefing Prompt