Most product managers are leaving their best tool almost completely untouched. Let us fix that.
I used Claude for two weeks before I realised I had been doing it wrong. I was treating it like a fancy search engine: asking one-off questions, copying answers, moving on. Then a colleague showed me how she had handed her entire discovery synthesis workflow to it, and I felt like I had been walking to work while a car sat in the driveway.
This piece is your shortcut.
The honest pitch: Claude will give you back hours every week, specifically on the work you find most draining, which is synthesis, first drafts, and preparing for difficult conversations. Here is how to actually start.
Step 1: Start with your most hated recurring task.
Do not begin with the glamorous work. Think about the work you dread, the interview summaries you keep putting off, the PRD section you rewrite five times, the stakeholder update that takes forty-five minutes to word. That is your entry point. Give Claude the raw material and ask it to do the tedious version first. You then edit from a draft instead of starting from a blank page.
Step 2: Use it for discovery synthesis.
After user interviews, paste your raw notes in and say: “You are a senior product researcher. Here are notes from six customer interviews. Identify the top three recurring pain points, surface any surprising or contradictory signals, and suggest two or three opportunity areas worth exploring.” What used to take half a day of affinity mapping now takes ten minutes, and you still do the thinking that matters.
Step 3: Use it as a sparring partner for your PRDs.
Before you send your next PRD to engineering, try: “Act as a sceptical senior engineer reviewing this PRD. What assumptions am I making? What edge cases have I not considered? What would make you push back on building this?” You catch gaps before standup, your credibility goes up, and your revision cycles go down.
Step 4: Prepare for difficult conversations.
Stakeholder pushback, executive reviews, cross-functional friction. Try: “I need to tell my VP that we are deprioritising Feature X. She has championed it for months. Help me frame this in a way that acknowledges her investment while making the case for the trade-off.” It will not write the conversation for you, but it will help you think through angles you would miss under pressure.
Step 5: Build reusable prompts, not one-offs.
The PMs getting the most value are not starting from scratch every time. They have built a small library of prompts they reuse and refine. Start with three: a discovery synthesis prompt, a PRD challenge prompt, and a stakeholder framing prompt. Save them. Iterate on them. They compound in value over time.
One tip worth more than the rest: give Claude a role before you give it a task. The difference between “Summarise this feedback” and “You are a senior PM who specialises in B2B SaaS. Summarise this feedback, flagging anything that signals retention risk” is enormous. The more specific the persona, the more targeted the output.
If this is the kind of thinking you want more of, the newsletter goes out once a week: one field note, and nothing else.