Iterating Within a Claude Session for Better Outputs

Claude for Product Managers

Why this course matters

What Claude Actually Does

The Context Equation

Three Things Claude Is Excellent At (For PMs)

The PM-Claude Feedback Loop

The Anatomy of a High-Value Prompt

The Most Useful Prompt Patterns for PMs

Prompts That Consistently Fail (And Why)

Iterating Within a Session

The PRD Briefing Prompt

The PRD Writing Prompt

Before and After: PRD Problem Statements

Writing Acceptance Criteria That Close the Interpretation Gap

The Requirements Completeness Check

The Research and Interview Synthesis Problem

The Research → Product Implication Chain

Synthesizing Support Tickets and Feedback at Scale

Competitive Research Prompt

Why Prioritization Needs an Analytical Foundation

The RICE Scoring Prompt

The Tradeoff Articulation Prompt

The Executive Update Prompt

Turning Data Into a Narrative

Meeting Synthesis Prompts

The Weekly PM Operating System

Your Prompt Library: Build It As You Go

Multi-Step Workflows (The High-Leverage Play)

The Mistakes That Degrade Your Outputs Over Time

Prompts Library

Terms to Remember

Lesson 4

Iterating Within a Session

Don't start a new conversation when your first output is wrong. Iterate within the session the context you've already given accumulates.

Good iteration statements:

"Section 3 is too long and buries the main point. Restructure it so the key insight is the first sentence, then supporting detail."

"The tone is too formal for our eng team. Rewrite for a technical audience that values directness over polish."

"You've conflated two different user problems here. Split this into two separate sections one for [problem A] and one for [problem B]."

"This is better. Now stress-test it: what's the most likely way this recommendation turns out to be wrong?"

Notice these are specific and directed. "Make this better" is not a direction.