Where AI actually helps a PM, beyond "write my PRD"

An honest thread: a PM who writes about AI tools admitted they still hadn't found a single core use case fully accelerated by AI. Research, maybe — but most PMs don't actually spend their days researching. PRDs fast-track, but iterating on them with AI is painful. Prototyping was never a PM's job to begin with. Another PM asked the flip side — what AI tools or agents people built that actually made an impact on the wider team, not just personal productivity.

Both are asking the right question, and the honest answer is that the wins are real but narrower than the marketing implies. Here's where AI genuinely moves the needle.

The real wins

• Aggregating and clustering unstructured input. Turning a thousand feedback fragments across six channels into themed, ranked signal is tedious for a human and well-suited to a model. This is the biggest, most reliable win and it's not the one people lead with.
• Grounding and gap-checking, not drafting. "Write my PRD" is the overhyped use case. "Read these transcripts and tell me what my draft is missing" is the underrated one. The model is better as a second set of eyes than as a first draft.
• Mechanical transformation between formats. Spec to tickets, PRs to release notes, raw notes to a clean transcript. Low-judgment, high-volume conversions where the model's job is faithfulness, not creativity.
• Reverse-spec. Describing what a built product actually does, in plain language, from behavior or code. Genuinely hard by hand, genuinely good with a model.

Why "write my PRD" disappoints

The reason drafting feels underwhelming is that it's the task where the model has the least to work with and the most room to invent. You give it a thin prompt, it gives you a plausible document, and iterating means fighting its confident fabrications. The use cases that actually accelerate are the ones where the model operates on material you already have — feedback, a transcript, a codebase, an existing spec. Give it substance to work on and it's genuinely fast. Ask it to conjure substance and you get slop you then have to repair.

The team-impact version

The PM asking what made a wider impact is pointing at the real prize. Personal time savings are nice; the tools that change a team are the ones that remove a shared bottleneck — the feedback pile everyone drowns in, the spec-to-ticket grind, the gap check that used to depend on one senior reviewer's availability. Automate the bottleneck, not the drafting, and the impact compounds past your own to-do list.