1. Synthesising qualitative feedback
As a PM, you probably have more raw feedback than time: interviews, support tickets, sales notes, survey responses. Large models are very good at helping you slice this information, but only if you give them structure.
A robust feedback synthesis prompt will:
- Ask you to paste raw quotes, not pre‑chewed summaries.
- Group them into themes, but also highlight outliers and surprising signals.
- Separate “what users say” from “what the model infers”.
2. Turning themes into opportunity statements
Once you have themes, the next step is to turn them into actionable opportunity statements. Good prompts here follow patterns like “For [segment], in [situation], [problem], which makes [impact]”. This avoids jumping straight to solutions and keeps you in the problem space a bit longer.
3. Co‑writing PRDs and design briefs
PRDs and briefs are perfect candidates for templated prompts. In boomPrompt you can create a “PRD skeleton” that asks the model to help you:
- Clarify goals and non‑goals.
- List user stories and edge cases based on your input.
- Draft acceptance criteria that engineers can act on.
The key is to treat the model as a collaborator, not an author: you paste your own notes and decisions, then let the model help you fill gaps, rephrase and reorder.
4. Communicating trade‑offs
When you need to explain options to stakeholders, prompts can help you explore and structure trade‑offs faster. For example, you can ask the model to compare two approaches across axes such as user value, tech risk, timeline and dependency on other teams.
5. Building a PM prompt toolbox
Over time, you will accumulate prompts that match your way of working: discovery synthesis, opportunity framing, roadmap narrative, PRD drafting, announcement emails. Turning these into a dedicated PM category inside boomPrompt makes it easier for your future self – and for other PMs in your org – to reuse what works instead of starting from a blank page every time.