Stepthrough Start free

How do product managers actually use AI day to day?

Product managers mostly use AI for four everyday jobs: turning customer interviews into themes with quotes, drafting specs and docs after AI has asked them the right questions, scanning competitors with cited sources, and writing the updates that go to the team and stakeholders. The biggest time saver is usually interview synthesis, which you can try in Speak AI: Turn Customer Interviews into Themes and Quotes.

The pattern under all four is the same. AI does the first pass on a lot of text, and the PM decides what it means. AI can tell you that five customers mentioned the welcome email. It cannot tell you whether fixing it matters more than the roadmap item your biggest client is waiting for.

Where does AI fit in a PM's week?

Discovery: interviews and feedback. Upload call recordings or transcripts, get them split by speaker, and ask for themes, each with a direct quote and a timestamp. Across many interviews, the keywords that keep coming back point to the real problems. Tools like Speak AI transcribe and pull out themes; Dovetail collects interviews, feedback and survey answers in one place and uses AI to find themes across them.

Specs and docs. Instead of asking for "a PRD for feature X" and getting a generic template, have the assistant interview you first: the user, the problem, what success looks like, what is out of scope. Then it drafts. You still own the decisions and the trade-offs.

Market and competitor research. Research modes in Claude, ChatGPT and Gemini search the web and return a report with a source for every claim. Use them for pricing pages, feature lists and positioning, then open the sources that matter.

Communication. Release notes, stakeholder updates, meeting recaps and FAQ drafts for support. These are fast to check because you know the facts.

What does this look like in a real lesson?

In Speak AI: Turn Customer Interviews into Themes and Quotes a small accounting firm has run five onboarding interviews and nobody has time to replay them. You upload a three-minute recording, see Speaker 0 and Speaker 1 split by voice, and read Mike's line at 00:25 about a welcome email with 11 attachments. You scan the keywords (first week, onboarding, paperwork, document portal), check the people and brands list, where "Fair" from "It was fair" was wrongly tagged as a brand, and jump to the low point in the sentiment chart. AI Chat returns a three-bullet summary and three problems, each with a quote and a fix. Then the key step: at 00:59 Mike says "fine", but the transcript wrote "fun", so you press play on every quote before you share it.

For specs, Make ChatGPT Ask You Questions First uses a job posting as the example, but the prompt works for any doc. ChatGPT asks up to five questions one at a time, sums up what it understood, and only writes after you confirm. You save the prompt with blanks for [WHAT YOU NEED] and [MY BUSINESS].

For competitors, Research: a cited competitor price scan has Claude's Research mode build a cited price report. When you open a source, you find the prices are from March 2024, which the report did not say.

How do I start using AI as a PM this week?

  1. Pick last month's interviews and run them through a transcription tool. Compare its themes with your own notes.
  2. Save an interview prompt for specs, so every PRD starts from your answers, not a template.
  3. Run one cited competitor scan and open at least three sources.
  4. Draft this sprint's release notes from the ticket list, then edit for tone.

More prompts are in the prompts for product managers. For recordings, see how to transcribe interviews with speaker labels.

What mistakes should PMs avoid?

  • Quoting a transcript without checking the audio. One wrong word can flip a quote.
  • Letting AI rank priorities. Frequency of a theme is not the same as business impact.
  • Uploading recordings without consent. Get permission before you record or upload anyone, and redact personal details before sharing.
  • Trusting competitor facts without opening sources. Pages go out of date.
  • Accepting a generic spec. If it has no blanks you had to fill, it does not know your product.

Key takeaways

  • Interview synthesis is the biggest everyday win, but check every quote against the audio.
  • Have AI ask you questions before it drafts a spec.
  • Use research modes with citations, and open the sources.
  • AI finds patterns. The PM decides what matters.

Frequently asked questions

Can AI write a PRD?

It can write a solid first draft once it knows the user, the problem, the scope and the success measure. Ask it to interview you first, then edit the trade-offs yourself.

Is it OK to upload customer calls to an AI tool?

Only with the customer's permission and in a tool your company approves. Turn on redaction for personal details before you share transcripts outside the team.

Which AI tool is best for product managers?

Use your company's approved chat assistant for docs and research, and add a research repository like Dovetail or a transcription tool like Speak AI if you run regular interviews.

Learn it hands-on

Free, interactive lessons: you do every step yourself in a practice copy of the real tool, it checks your work as you go, and nothing touches your real accounts.

Start the free lesson

AI tools in this answer

Each one in the Stepthrough AI tools directory: what it does, who it is for and the free lesson where there is one.

The full AI tools directory

Plain-English definitions, each with an example from a free lesson.

The full AI glossary

All free prompt templates

More questions: AI by department · All AI questions · All free tutorials