What AI actually looks like for a product team

Product managers are, underneath the strategy and the roadmaps, professional writers. PRDs, spec documents, user story maps, OKR write-ups, stakeholder updates, research synthesis, release notes — the writing never stops. And most of it is structural: the same format, different content, over and over.

That is the space where Claude changes the job.

Where Claude genuinely helps product teams

PRD first drafts. Give Claude the problem statement, the key user research, the proposed solution, and the constraints. Ask it to produce a first-draft PRD in your team's format. You get a complete document with gaps you need to fill rather than a blank page. The quality of the PRD depends on the quality of your input — but even a 70% draft saves 90 minutes of writing time.

User story generation. "Given this feature description, write the user stories in the format 'As a [user type], I want [goal], so that [reason].'" Claude can produce 20 stories from a feature description in seconds. You review, edit, and cut. Far faster than writing from scratch.

Research synthesis. Paste in 10 user interview transcripts. Ask Claude to identify the top five themes, with quotes. This is not a replacement for the researcher's analysis — it is a first pass that organises the material so the researcher can do deeper analysis faster. The RAG approach (uploading research documents to a Project) makes this repeatable across the whole research archive.

Stakeholder communication. "Here is the technical spec for this feature. Write a non-technical summary for the executive team that explains the business impact." Claude bridges the translation gap that product managers spend enormous time on. Same information, two audiences, one round of human review.

Release notes and changelogs. Give Claude the list of changes and their technical descriptions. Ask it to produce user-facing release notes in plain language. It is entirely mechanical — exactly the kind of task where Claude consistently performs well.

Competitive analysis first pass. "Here is our competitor's pricing page and their recent blog posts. Summarise their positioning and what has changed in the last quarter." Claude cannot do deep strategic analysis, but it can structure the raw material so you spend your time on analysis rather than gathering and organising.

What does not work well

Product strategy. Claude can help you articulate a strategy you have already developed. It cannot develop strategy. If you ask Claude "what should our product strategy be," you will get a well-structured answer that sounds good and reflects nothing about your actual market, your customers, or your company's position. Use it to sharpen and articulate; not to originate.

Deciding what to build. Prioritisation is a judgment call that depends on context Claude does not have. Claude can help you structure your prioritisation criteria, but do not let it rank your roadmap.

Replacing user research. Claude can help synthesise research. It cannot replace it. Any Claude output that contains a user insight must be traced back to a real user who said it.

The Project setup

One Product Project with:

• Your PRD template
• User story format and examples
• Your product principles and north star metric
• Current roadmap context
• Glossary of your product's domain-specific terms

System prompt: "You are a product writing assistant for [Company]. You help the product team draft PRDs, user stories, stakeholder updates, and release notes. You know our product, our users, and our way of writing. When you are missing information needed to write accurately, ask for it rather than inventing it."

That last instruction matters — a product Claude that invents user needs or product details is worse than useless. Make it ask.

The real change

The product managers who get the most out of Claude are not the ones who use it to think for them. They are the ones who use it to spend their thinking time on thinking — and their writing time on editing instead of generating. That is a significant shift in how the job feels. Less grinding; more judgment.