Synthesize Feedback: turn notes into feedback synthesis

Treat "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." as the desk note for feedback synthesis: copy the prompt only after the output target, reviewer, and risk check are named.

Start with the right jobUse this workflow when your note, output, and switch point line up.

First move: Let the first answer stay provisional until theme frequency, segment contrast, quote evidence, and product implication survives the repair pass and the user knows which sentence should be saved, changed, or rejected.
Keep after run: The final note should preserve source-backed claims, leave unsupported points in a needs-checking block, and state who must review the answer next.
Wrong page signal: Wrong page signal: switch to ChatGPT Prompts for Product Managers if the user cannot supply feedback items, segments, frequency, severity, quotes, and product area, if the desired result is not a feedback synthesis, or if theme frequency, segment contrast, quote evidence, and product implication is no longer the controlling decision.

First usable run

Start with the note you actually have

A realistic example is loaded. Try the flow once, then clear it and paste your own working notes.

1/3 ready

Next stepFinish the run setup2 items still need context before this becomes reusable.

Current note

Paste source notesMust keepDo not allow

PrepareSource noteReal notes are loaded.
RunCopy run prompt2 checks before copy.
ReviewReview answerCurrent choice: Repair.
SaveSave reusable version0/3 save checks closed.

Keep working laterPage work stays on this device until you save it.

Try the sample firstSee one messy note become a usable synthesize feedback run

Messy input: For feedback synthesis, the source note starts plainly: "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." is the rough request. The ready check for feedback synthesis is simple: before anyone reuses it, a feedback synthesis should preserve theme frequency, segment contrast, quote evidence, and product implication, show who checks it, and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Better answer should: The target feedback synthesis result should return a structured analysis table with claims, evidence, gaps, and recommended next step; separate supplied notes from assumptions, name the review owner, prepare feedback theme table with quote evidence, and make the human pass focused on feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.
Human edit: Product Managers final edit for synthesize feedback should keep the structure that saved time, replace polished filler with source-backed lines inside a feedback synthesis, remove private or one-time information, and rewrite the final wording for a product team, stakeholder, customer researcher, or release owner; compare the answer with "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." and make sure The final synthesis should show what is known, what is noisy, and what needs more research.

Fix before reuse2 gaps before reuseCopy can start the first pass, but the answer is not reusable until these checks are closed.

Separate facts from assumptionsMark which must-keep details came from the user and which details still need a human decision.
Name who checks it and the stop ruleGive approval work to the person who can spot when theme frequency, segment contrast, quote evidence, and product implication has drifted from the user's source material. must know what to reject before the answer is reused.

Real note: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions. a product team, stakeholder, customer researcher, or release owner can be misled by polished wording, so the reviewer check needs to stay visible. The model should not smooth away the missing context. Treat synthesize feedback as first-pass evidence for a feedback synthesis. Synthesize Feedback works better when the context is in named fields, because each variable can be checked before copying.
What will change: Run the answer through the repair section if it sounds finished before it proves how theme frequency, segment contrast, quote evidence, and product implication shaped the result.
Human check: Source review, synthesize feedback: the answer uses the supplied feedback items, segments, frequency, severity, quotes, and product area and does not fill missing facts with confident guesses.

Open run previewCheck the exact prompt before copying.

Run prompt preview

Copy this after checking the notes

Task: ChatGPT Prompts for Product Managers to Synthesize Feedback
Who checks it: Give approval work to the person who can spot when theme frequency, segment contrast, quote evidence, and product implication has drifted from the user's source material.

Paste source notes:
Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions. a product team, stakeholder, customer researcher, or release owner can be misled by polished wording, so the reviewer check needs to stay visible. The model should not smooth away the missing context. Treat synthesize feedback as first-pass evidence for a feedback synthesis. Synthesize Feedback works better when the context is in named fields, because each variable can be checked before copying.

Must keep:
Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.
feedback items, segments, frequency, severity, quotes, and product area
theme frequency, segment contrast, quote evidence, and product implication

Do not allow:
Discard the answer if it cannot trace which details came from the source and which details were inferred.
Reject it if the answer answers a related topic but not this task output.

Readiness before copy:
- Separate facts from assumptions: Mark which must-keep details came from the user and which details still need a human decision.
- Name who checks it and the stop rule: Give approval work to the person who can spot when theme frequency, segment contrast, quote evidence, and product implication has drifted from the user's source material. must know what to reject before the answer is reused.

Run prompt:
Act as a careful assistant for Product Managers.
Task: help me synthesize feedback. Target result: a feedback synthesis.
Source material I can provide: [source_material]. Typical source for this task is feedback items, segments, frequency, severity, quotes, and product area.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: theme frequency, segment contrast, quote evidence, and product implication.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as the first usable version: use the supplied fields, label assumptions, and produce the main artifact.
Stop rule: Stop if the request asks you to invent facts, evidence, credentials, numbers, or private details.
Return a structured analysis table with claims, evidence, gaps, and recommended next step.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: The user should get a working version they can inspect against the supplied notes.

Stop rule: Discard the answer if it cannot trace which details came from the source and which details were inferred.
Record to keep: Save the next run with the original note, the prompt variables that changed the answer, the section that still needs feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, and the final reason the accepted version can become feedback synthesis prompt pattern with source notes, constraints, and review checklist.

Open answer reviewUse this after ChatGPT returns the first answer.

After ChatGPT answers

Check the answer before saving it

Check against: Source review, synthesize feedback: the answer uses the supplied feedback items, segments, frequency, severity, quotes, and product area and does not fill missing facts with confident guesses. Output shape, synthesize feedback: the result clearly becomes a feedback synthesis, not broad advice about the task.
Reject if: Evidence issue, synthesize feedback: the answer invents or overstates source notes, examples, constraints, and reviewer judgment. Task drift, synthesize feedback: it ignores theme frequency, segment contrast, quote evidence, and product implication and moves into a neighboring workflow.
Keep after run: Save the next run with the original note, the prompt variables that changed the answer, the section that still needs feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, and the final reason the accepted version can become feedback synthesis prompt pattern with source notes, constraints, and review checklist.

Open first answer choiceChoose accept, repair, or reject only after review.

First answer choice

Pick accept, repair, or reject before reuse

After the first synthesize feedback answer, the product manager should choose Accept, Repair, or Reject before saving anything as feedback synthesis prompt pattern with source notes, constraints, and review checklist. The decision must compare "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." with a structured analysis table with claims, evidence, gaps, and recommended next step, theme frequency, segment contrast, quote evidence, and product implication, and source notes, examples, constraints, and reviewer judgment.

Choose when: Choose Repair when the answer has a useful shape but loses one of the required pieces: theme frequency, segment contrast, quote evidence, and product implication, source notes, examples, constraints, and reviewer judgment, the reviewer role, the source note, or the reusable fields needed for feedback synthesis prompt pattern with source notes, constraints, and review checklist.
Do next: Ask ChatGPT for a second pass that keeps the usable structure, rewrites only the weak sections, adds missing proof questions, and returns a feedback synthesis in a structured analysis table with claims, evidence, gaps, and recommended next step without inventing details.
Keep after run: Keep the weak answer beside the repair note, mark which line failed feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, and save the corrected line only after it can be traced back to "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.".

Answer choice prompt

Repair this synthesize feedback answer instead of accepting it. Source note: "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." Weak answer: [paste_chatgpt_output_here]. Preserve any useful structure, but fix the parts that hide theme frequency, segment contrast, quote evidence, and product implication, turn source notes, examples, constraints, and reviewer judgment into unsupported certainty, or skip the reviewer for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence. Return a repaired a structured analysis table with claims, evidence, gaps, and recommended next step, a list of changed lines, and one remaining question before this can become feedback synthesis prompt pattern with source notes, constraints, and review checklist.

Do not save a reusable feedback synthesis prompt pattern with source notes, constraints, and review checklist until one option has a written decision. The saved version must keep "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." as the example, turn private or one-time details into variables, and keep the risk check "Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided" visible for the next run.

Open saved versionTurn the reviewed answer into a reusable saved version.

Saved version

Save the final answer, human edit, and variables

Save only after review. The reusable version needs the answer, the human edit, and the reuse rule in one place.

Final answerHuman editReusable variables

Save only when

The final answer passed the answer review.The human edit names what changed before reuse.Who checks it and reuse rule are saved with the asset.

Who checks it: The human owner who approves the final packet for Product Managers to Synthesize Feedback before it is saved, shared, or reused.
Reuse rule: Save the feedback synthesis answer only when private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a feedback synthesis, and the review rule for theme frequency, segment contrast, quote evidence, and product implication still appears in the reusable prompt. Approval for product managers feedback synthesis belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the feedback theme table with quote evidence review standard visible.
Saved: 0/3 checks

Saved version preview

Final saved version for: ChatGPT Prompts for Product Managers to Synthesize Feedback
Who checks it: The human owner who approves the final packet for Product Managers to Synthesize Feedback before it is saved, shared, or reused.
Use or revise before saving: Repair

Save only after review:
- Source review, synthesize feedback: the answer uses the supplied feedback items, segments, frequency, severity, quotes, and product area and does not fill missing facts with confident guesses.
- Save the next run with the original note, the prompt variables that changed the answer, the section that still needs feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, and the final reason the accepted version can become feedback synthesis prompt pattern with source notes, constraints, and review checklist.
- Keep the original note, the exact prompt variables that changed the answer, the section that proves feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, and the final accept reason before the result reaches a product team, stakeholder, customer researcher, or release owner.
- Current answer choice: Keep the weak answer beside the repair note, mark which line failed feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, and save the corrected line only after it can be traced back to "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.".

Source note used:
Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions. a product team, stakeholder, customer researcher, or release owner can be misled by polished wording, so the reviewer check needs to stay visible. The model should not smooth away the missing context. Treat synthesize feedback as first-pass evidence for a feedback synthesis. Synthesize Feedback works better when the context is in named fields, because each variable can be checked before copying.

Final answer:
The target feedback synthesis result should return a structured analysis table with claims, evidence, gaps, and recommended next step; separate supplied notes from assumptions, name the review owner, prepare feedback theme table with quote evidence, and make the human pass focused on feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.

Human edit:
Product Managers final edit for synthesize feedback should keep the structure that saved time, replace polished filler with source-backed lines inside a feedback synthesis, remove private or one-time information, and rewrite the final wording for a product team, stakeholder, customer researcher, or release owner; compare the answer with "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." and make sure The final synthesis should show what is known, what is noisy, and what needs more research.

Reusable variables:
[source_material]: feedback items, segments, frequency, severity, quotes, and product area
[audience]: a product team, stakeholder, customer researcher, or release owner
[goal]: make a feedback synthesis easier to review, adapt, and use in a real product managers workflow
[constraints]: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

Reuse rule: Save the feedback synthesis answer only when private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a feedback synthesis, and the review rule for theme frequency, segment contrast, quote evidence, and product implication still appears in the reusable prompt. Approval for product managers feedback synthesis belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the feedback theme table with quote evidence review standard visible.
Stop if: Discard the answer if it cannot trace which details came from the source and which details were inferred.

First run setup

Set up the first run

Edit notes

First move: Run the answer through the repair section if it sounds finished before it proves how theme frequency, segment contrast, quote evidence, and product implication shaped the result.
Bring first: Bring the rough case note: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.
Switch if: The user cannot provide feedback items, segments, frequency, severity, quotes, and product area and would need ChatGPT to invent the important facts.
Keep after run: Save the next run with the original note, the prompt variables that changed the answer, the section that still needs feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, and the final reason the accepted version can become feedback synthesis prompt pattern with source notes, constraints, and review checklist.

Choose where you areGo to runner

Go to runnerWithin five minutes, the user should have a first feedback synthesis prompt pattern with source notes, constraints, and review checklist, one copied run prompt, and a reviewer check that keeps feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence and source notes, examples, constraints, and reviewer judgment visible before sharing anything. Start with: Run the answer through the repair section if it sounds finished before it proves how theme frequency, segment contrast, quote evidence, and product implication shaped the result.

Go to runner

Open switch notesWhat to bring, who checks it, and when to change workflows.

Who checks it

Give approval work to the person who can spot when theme frequency, segment contrast, quote evidence, and product implication has drifted from the user's source material.

Check before using

Inspect feedback items, segments, frequency, severity, quotes, and product area, the case note "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.", and any open proof around source notes, examples, constraints, and reviewer judgment; the answer should keep supplied notes, assumptions, and needs-checking points separate.

Compare later

Result feedback synthesis product managers check: open the top results and record whether they solve the task, not only a prompt phrase.

Visitor question: I have feedback items, segments, frequency, severity, quotes, and product area and need a feedback synthesis for a product team, stakeholder, customer researcher, or release owner; can this synthesize feedback page turn "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." into a structured analysis table with claims, evidence, gaps, and recommended next step without hiding theme frequency, segment contrast, quote evidence, and product implication?
5-minute outcome: Within five minutes, the user should have a first feedback synthesis prompt pattern with source notes, constraints, and review checklist, one copied run prompt, and a reviewer check that keeps feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence and source notes, examples, constraints, and reviewer judgment visible before sharing anything.
Wrong page signal: This is the wrong page if the work is closer to ChatGPT Prompts for Product Managers, if theme frequency, segment contrast, quote evidence, and product implication is not the controlling decision, or if the user only wants broad ideas instead of a reviewable a feedback synthesis.
Why this page fits: Save the rough note, the accepted prompt variables, the feedback synthesis query language, and the section that proves this a feedback synthesis is not interchangeable with ChatGPT Prompts for Product Managers.
Reuse decision: Reuse the output only when the answer traces back to feedback items, segments, frequency, severity, quotes, and product area, respects the risk check "Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided", and gives a product team, stakeholder, customer researcher, or release owner a clear accept, repair, or reject path.

Wrong page? Define acceptance criteriaUseful next step when this workflow needs a related product managers output or review pass.

Working brief

Check the job before copying

The distinct value is the stop rule: the answer should pause around source notes, examples, constraints, and reviewer judgment, name the reviewer, and keep unsupported claims away from the usable sections.

Use this when: Open this page when a fluent answer might hide the failure mode: feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence has not been checked against the real source notes.
Paste this kind of note: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions. a product team, stakeholder, customer researcher, or release owner can be misled by polished wording, so the reviewer check needs to stay visible. The model should not smooth away the missing context. Treat synthesize feedback as first-pass evidence for a feedback synthesis. Synthesize Feedback works better when the context is in named fields, because each variable can be checked before copying.
Expected result: The target feedback synthesis result should return a structured analysis table with claims, evidence, gaps, and recommended next step; separate supplied notes from assumptions, name the review owner, prepare feedback theme table with quote evidence, and make the human pass focused on feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.
Stop before reuse if: Discard the answer if it cannot trace which details came from the source and which details were inferred.
Human check: Source review, synthesize feedback: the answer uses the supplied feedback items, segments, frequency, severity, quotes, and product area and does not fill missing facts with confident guesses.

Bring first: Bring the rough case note: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.
Build when: Use this when the notes are ready and the next useful output is a structured analysis table with claims, evidence, gaps, and recommended next step, not more brainstorming.
Stop if: Stop if the answer hides missing context, blurs assumptions, or cannot trace key claims back to the notes.
Save when: Copy the external review checklist, record what changed, and save a version with reusable variables instead of private details.

Copy prompt Check answer

Fit and safety notes

Use this page for

Product Managers who have real notes or context and need a structured first version of a feedback synthesis.
Users who want ChatGPT to ask clarifying questions before it commits to a structured analysis table with claims, evidence, gaps, and recommended next step.
Teams that repeat synthesize feedback and need a prompt they can adapt without losing the review step.

Do not use for

Users who want ChatGPT to invent facts, credentials, numbers, or personal details.
Situations where the output needs final approval from a qualified human before it reaches a product team, stakeholder, customer researcher, or release owner.
Work that includes private data that has not been removed or summarized safely.

Wrong page?Define acceptance criteriaUseful next step when this workflow needs a related product managers output or review pass.

Editorial method Safe use About this library

Synthesize feedback Evidence-Aware Working Copy Prompt

Use this when the source material is ready and the answer needs to become a feedback synthesis.

Real input: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions. a product team, stakeholder, customer researcher, or release owner can be misled by polished wording, so the reviewer check needs to stay visible. The model should not smooth away the missing context. Treat synthesize feedback as first-pass evidence for a feedback synthesis. Synthesize Feedback works better when the context is in named fields, because each variable can be checked before copying.
Target output: The target feedback synthesis result should return a structured analysis table with claims, evidence, gaps, and recommended next step; separate supplied notes from assumptions, name the review owner, prepare feedback theme table with quote evidence, and make the human pass focused on feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.
Reject if: Discard the answer if it cannot trace which details came from the source and which details were inferred.

Scenario: A PM has 40 support tickets and 12 interview notes about reporting exports being confusing. The synthesize feedback work happens inside a product decision workflow where evidence and tradeoffs need to stay visible. For product managers feedback synthesis, current source notes should come first; stale or partial inputs should trigger a fresh feedback theme table with quote evidence pass instead of another saved answer. Approval for product managers feedback synthesis belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the feedback theme table with quote evidence review standard visible. For synthesize feedback, a short prompt usually misses the constraint stack here: the value comes from evidence, order of review, and the decision made after the answer.
Bring: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions. feedback items, segments, frequency, severity, quotes, and product area theme frequency, segment contrast, quote evidence, and product implication
Check: The final synthesis should show what is known, what is noisy, and what needs more research. Approval for product managers feedback synthesis belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the feedback theme table with quote evidence review standard visible. Before handing off synthesize feedback, the last edit should turn the model answer into a practical asset, not just a polished paragraph, with a short record of what changed before reuse and where For product managers feedback synthesis, current source notes should come first; stale or partial inputs should trigger a fresh feedback theme table with quote evidence pass instead of another saved answer.

Variable Builder

[source_material]The notes, facts, examples, or raw material behind synthesize feedback.[audience]Who will read, use, approve, or act on the output.[goal]The decision or work outcome the response should support.[constraints]Rules, tone, length, channel, privacy limits, and required sections.[review_lens]The most important thing a human should check after the answer.[task_focus]The task-specific detail that keeps this prompt from becoming generic.

Filled prompt

Copy this filled version

Act as a careful assistant for Product Managers.
Task: help me synthesize feedback. Target result: a feedback synthesis.
Source material I can provide: [source_material]. Typical source for this task is feedback items, segments, frequency, severity, quotes, and product area.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: theme frequency, segment contrast, quote evidence, and product implication.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as the first usable version: use the supplied fields, label assumptions, and produce the main artifact.
Stop rule: Stop if the request asks you to invent facts, evidence, credentials, numbers, or private details.
Return a structured analysis table with claims, evidence, gaps, and recommended next step.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: The user should get a working version they can inspect against the supplied notes.

Show raw template

Act as a careful assistant for Product Managers.
Task: help me synthesize feedback. Target result: a feedback synthesis.
Source material I can provide: [source_material]. Typical source for this task is feedback items, segments, frequency, severity, quotes, and product area.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: theme frequency, segment contrast, quote evidence, and product implication.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as the first usable version: use the supplied fields, label assumptions, and produce the main artifact.
Stop rule: Stop if the request asks you to invent facts, evidence, credentials, numbers, or private details.
Return a structured analysis table with claims, evidence, gaps, and recommended next step.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: The user should get a working version they can inspect against the supplied notes.

Expected output: Expect a structured analysis table with claims, evidence, gaps, and recommended next step that explicitly separates source-based content from assumptions and ends with a review pass for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.

First run

Run this page in four moves

Concrete outputThe target feedback synthesis result should return a structured analysis table with claims, evidence, gaps, and recommended next step; separate supplied notes from assumptions, name the review owner, prepare feedback theme table with quote evidence, and make the human pass focused on feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.

Keep after runSave the next run with the original note, the prompt variables that changed the answer, the section that still needs feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, and the final reason the accepted version can become feedback synthesis prompt pattern with source notes, constraints, and review checklist.

Reject before reuseDiscard the answer if it cannot trace which details came from the source and which details were inferred.

PrepareCollect ContextUse this when the product manager source notes are still uneven or missing the detail that would shape a feedback synthesis.CopyBuild The AssetUse this when the notes are ready and the next useful output is a structured analysis table with claims, evidence, gaps, and recommended next step, not more brainstorming.GradeReview The AnswerUse this when ChatGPT has already answered and the risk is accepting fluent wording before feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence is checked.SavePrepare HandoffUse this when the answer is close but needs to become a repeatable asset for a product manager, not a one-off chat result.

Work notes

Start from the real note, not a blank prompt

Current input: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions. a product team, stakeholder, customer researcher, or release owner can be misled by polished wording, so the reviewer check needs to stay visible. The model should not smooth away the missing context. Treat synthesize feedback as first-pass evidence for a feedback synthesis. Synthesize Feedback works better when the context is in named fields, because each variable can be checked before copying.
First move: Run the answer through the repair section if it sounds finished before it proves how theme frequency, segment contrast, quote evidence, and product implication shaped the result.
Who checks it: Give approval work to the person who can spot when theme frequency, segment contrast, quote evidence, and product implication has drifted from the user's source material.

Stop rule: Discard the answer if it cannot trace which details came from the source and which details were inferred.
Keep after run: Save the next run with the original note, the prompt variables that changed the answer, the section that still needs feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, and the final reason the accepted version can become feedback synthesis prompt pattern with source notes, constraints, and review checklist.

PrepareCollect ContextBring the rough case note: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.CopyBuild The AssetExpect a structured analysis table with claims, evidence, gaps, and recommended next step that explicitly separates source-based content from assumptions and ends with a review pass for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.GradeReview The AnswerReview the answer before making it reusable and require a short proof pass focused on source notes, examples, constraints, and reviewer judgment.SavePrepare HandoffCopy the external review checklist, record what changed, and save a version with reusable variables instead of private details.

Do not start if: Stop if the answer sounds polished but still cannot show the source notes behind theme frequency, segment contrast, quote evidence, and product implication.
Human check: Source review, synthesize feedback: the answer uses the supplied feedback items, segments, frequency, severity, quotes, and product area and does not fill missing facts with confident guesses.

Real note check

Check the answer against your note

This works best when the answer stays tied to the note you pasted, the question people search, and the person who can review it.

Question to compare: chatgpt prompts for product managers feedback synthesis

Open reference checks

Paste into ChatGPT: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions. a product team, stakeholder, customer researcher, or release owner can be misled by polished wording, so the reviewer check needs to stay visible. The model should not smooth away the missing context. Treat synthesize feedback as first-pass evidence for a feedback synthesis. Synthesize Feedback works better when the context is in named fields, because each variable can be checked before copying.
Question to compare: chatgpt prompts for product managers feedback synthesisResult feedback synthesis product managers check: open the top results and record whether they solve the task, not only a prompt phrase.
Reference page: NIST AI Risk Management FrameworkUsed as an external risk-management reference where a feedback synthesis needs human oversight, assumptions, and review controls.
Who checks it: Give approval work to the person who can spot when theme frequency, segment contrast, quote evidence, and product implication has drifted from the user's source material.Inspect feedback items, segments, frequency, severity, quotes, and product area, the case note "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.", and any open proof around source notes, examples, constraints, and reviewer judgment; the answer should keep supplied notes, assumptions, and needs-checking points separate.

The prompt is strongest when product managers bring the messy source first, because a structured analysis table with claims, evidence, gaps, and recommended next step needs to show what was supplied and what still needs checking. The source pack is not decoration; it controls the shape, claims, examples, and final checks inside a feedback synthesis. synthesize feedback practical edit: replace polished filler with source-backed lines inside a feedback synthesis. The strongest result leaves a clean trail from source material to output, then tells the user what to verify next. Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided. If the answer cannot pass the checklist, treat it as raw material and rerun the repair prompt.

Real use plan for treating the prompt like a work note

0/12 checked

The workflow stays practical by linking each copy action to a proof action: source fields before the prompt, source notes, examples, constraints, and reviewer judgment after the answer, and reusable variables after human review.

Before copying

Load the prompt with work context: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.Add the channel and review owner so a structured analysis table with claims, evidence, gaps, and recommended next step does not become generic advice.Tell ChatGPT what the human reviewer will enforce: The prompt must preserve evidence and uncertainty instead of forcing one tidy answer.Keep the answer grounded by making theme frequency, segment contrast, quote evidence, and product implication a required section or check.

After ChatGPT answers

Review the answer before making it reusable and require a short proof pass focused on source notes, examples, constraints, and reviewer judgment.Keep the answer editable by showing which parts affect feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.Request the next pass around the decision the answer must support, especially theme frequency, segment contrast, quote evidence, and product implication.Keep a reusable version only if another product manager could fill the same fields.

Reject the answer if

Discard the answer if it cannot trace which details came from the source and which details were inferred.Reject it if the answer answers a related topic but not this task output.Reject it when the final wording makes the boundary harder to see.Reject it if the answer does not leave a clear human review path.

Choose the next move

Begin with the messy notes, then choose the prompt path that matches the current state of the work.

Build The Asset

Use this when the notes are ready and the next useful output is a structured analysis table with claims, evidence, gaps, and recommended next step, not more brainstorming.

Open section

Do now: Copy the recommended prompt, replace the variables, and ask for a feedback synthesis with assumptions separated from source-backed details.
Bring first: Bring the task focus: theme frequency, segment contrast, quote evidence, and product implication. Add the channel, deadline, and any required sections.
Stop if: Stop if the first answer gives broad advice instead of a concrete a feedback synthesis.
Next check: Use the run sheet's review mode before sharing anything with a product team, stakeholder, customer researcher, or release owner.

Open prompt Prepare context Check answer

Before copying

Load the prompt with work context: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.
Add the channel and review owner so a structured analysis table with claims, evidence, gaps, and recommended next step does not become generic advice.
Tell ChatGPT what the human reviewer will enforce: The prompt must preserve evidence and uncertainty instead of forcing one tidy answer.

Accept only if

Review the answer before making it reusable and require a short proof pass focused on source notes, examples, constraints, and reviewer judgment.
Keep the answer editable by showing which parts affect feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.
Request the next pass around the decision the answer must support, especially theme frequency, segment contrast, quote evidence, and product implication.

Reject when

Discard the answer if it cannot trace which details came from the source and which details were inferred.

Know when the answer is ready

Use this quick check before saving the answer, rerunning the prompt, or switching to a neighboring workflow.

Ready signal

Treat the workflow as complete when the answer turns "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." into a structured analysis table with claims, evidence, gaps, and recommended next step, keeps theme frequency, segment contrast, quote evidence, and product implication visible, and gives the user deciding whether to rerun, repair, or reuse the answer a clear accept, repair, or reject choice before a product team, stakeholder, customer researcher, or release owner sees it.

First run action

Run the prompt only after naming feedback items, segments, frequency, severity, quotes, and product area, the intended a feedback synthesis, the audience, the stop rule "Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided", and the proof needed for source notes, examples, constraints, and reviewer judgment.

Keep after run: Save the next run with the original note, the prompt variables that changed the answer, the section that still needs feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, and the final reason the accepted version can become feedback synthesis prompt pattern with source notes, constraints, and review checklist.
Use or revise: the user deciding whether to rerun, repair, or reuse the answer should approve the output only if it can be traced back to feedback items, segments, frequency, severity, quotes, and product area, shows what is assumed, and does not turn source notes, examples, constraints, and reviewer judgment into a confident claim without review.
What makes this page different: The page should be compared against competitors on tying the query "chatgpt prompts for product managers feedback synthesis" to a fillable prompt, a realistic case, an answer repair path, and a no-fake-metrics proof boundary instead of only listing prompt phrases.
Why this page exists: This route is worth keeping for the feedback synthesis query because synthesize feedback changes the source material, reviewer, output shape, and failure mode; sending the user to a nearby product manager page would hide theme frequency, segment contrast, quote evidence, and product implication and weaken the final a feedback synthesis.

Editor margin

Second pass before the answer becomes reusable

Source line

Editor margin source for synthesize feedback: "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." It is the rough line that should survive the move from notes to reusable fields.

Reviewer voice

the person deciding whether feedback synthesis prompt pattern with source notes, constraints, and review checklist is safe to save reads the first ChatGPT answer beside the rough note and decides what survives. This pass turns a broad copy action into an editorial decision, so the user can see why the first answer is ready, repairable, or too thin. The check belongs before the prompt is saved as feedback synthesis prompt pattern with source notes, constraints, and review checklist.

Keep

the rough note "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions" as the visible source line for a feedback synthesis

Keep this because the rough note is the only part a product manager can compare against the answer when a structured analysis table with claims, evidence, gaps, and recommended next step starts to sound finished.

The accepted answer should repeat or clearly map back to "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." before it adds structure.

Cut

any confident claim about source notes, examples, constraints, and reviewer judgment that the pasted note does not prove

Cut it because the proof around source notes, examples, constraints, and reviewer judgment is the review risk for this page, and fluent wording can make an unsupported detail look approved.

If the source note does not show the fact, the answer should move it into a needs-checking line or remove it.

Ask

the missing audience, owner, or review detail needed before a product team, stakeholder, customer researcher, or release owner uses the answer

Ask before reuse because a feedback synthesis only helps a product team, stakeholder, customer researcher, or release owner when the channel, approval owner, and open proof are visible.

The next run should name the missing field instead of burying it inside a polished answer.

Rewrite

the first polished paragraph so it shows theme frequency, segment contrast, quote evidence, and product implication before tone improvements

Rewrite the opening because this task is about theme frequency, segment contrast, quote evidence, and product implication, not a general synthesize feedback answer that could fit any role page.

A reviewer should see theme frequency, segment contrast, quote evidence, and product implication in the first accepted section and again in the saved reuse rule.

Why this feels hand-edited

the person deciding whether feedback synthesis prompt pattern with source notes, constraints, and review checklist is safe to save leaves this margin pass because the page has to protect a real source note, not only offer another prompt. For product managers working on synthesize feedback, the human-feeling part is the specific tradeoff: keep "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.", cut unsupported certainty, ask for the missing owner, and rewrite the answer around theme frequency, segment contrast, quote evidence, and product implication. That proof trail makes the page feel edited rather than assembled from interchangeable blocks.

Run the margin pass

Run an editorial margin pass for this task. Source note: "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." Output being reviewed: [paste ChatGPT answer]. Mark four decisions: Keep the source-backed detail that should survive, Cut any unsupported claim about source notes, examples, constraints, and reviewer judgment, Ask the missing question that blocks a product team, stakeholder, customer researcher, or release owner from using the result, and Rewrite the section so theme frequency, segment contrast, quote evidence, and product implication stays visible before polish. End with one accept, repair, or reject decision and a reuse rule for feedback synthesis prompt pattern with source notes, constraints, and review checklist.

Task actions for the next useful move

Run the answer through the repair section if it sounds finished before it proves how theme frequency, segment contrast, quote evidence, and product implication shaped the result.

CollectCollect ContextBring the rough case note: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.CopyBuild The AssetExpect a structured analysis table with claims, evidence, gaps, and recommended next step that explicitly separates source-based content from assumptions and ends with a review pass for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.CheckReview The AnswerReview the answer before making it reusable and require a short proof pass focused on source notes, examples, constraints, and reviewer judgment.HandoffPrepare HandoffCopy the external review checklist, record what changed, and save a version with reusable variables instead of private details.

Wrong page ifThe user cannot provide feedback items, segments, frequency, severity, quotes, and product area and would need ChatGPT to invent the important facts.

Stay hereOpen this page when a fluent answer might hide the failure mode: feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence has not been checked against the real source notes. First move: Run the answer through the repair section if it sounds finished before it proves how theme frequency, segment contrast, quote evidence, and product implication shaped the result.

Switch ifDefine acceptance criteriaUseful next step when this workflow needs a related product managers output or review pass.

Stop ifThe user cannot provide feedback items, segments, frequency, severity, quotes, and product area and would need ChatGPT to invent the important facts. The desired result is not a feedback synthesis or cannot be shaped as a structured analysis table with claims, evidence, gaps, and recommended next step.

Not forUsers who want ChatGPT to invent facts, credentials, numbers, or personal details. Situations where the output needs final approval from a qualified human before it reaches a product team, stakeholder, customer researcher, or release owner.

Before you use the answer, make the call

Who checks it: The last human pass sits with the owner who will hand this to a product team, stakeholder, customer researcher, or release owner, especially where source notes, examples, constraints, and reviewer judgment or feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence could make a fluent answer unsafe.
Check before using: Inspect feedback items, segments, frequency, severity, quotes, and product area, the case note "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.", and any open proof around source notes, examples, constraints, and reviewer judgment; the answer should keep supplied notes, assumptions, and needs-checking points separate.
What this changes: Instead of treating ChatGPT's fluent response as the finish line, the checkpoint turns it into a reviewed work file with source-backed sections and explicit gaps.
Do next: The final synthesis should show what is known, what is noisy, and what needs more research. Then save only the repeatable fields, not the one-time case details, so the next run still asks for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.
Before saving for reuse: Before reusing the answer, keep any search, traffic, ranking, or popularity claim out of the final asset unless someone can point to Search Console evidence or other real search data after publishing for "chatgpt prompts for product managers feedback synthesis" and record where it came from.

Working case file: Synthesize Feedback working case for Product Managers

The useful job is to turn a rough request into a checkable run, not to collect more prompt examples. The user has enough material to start, but not enough to trust a smooth answer unless the prompt keeps feedback items, segments, frequency, severity, quotes, and product area, a structured analysis table with claims, evidence, gaps, and recommended next step, and the teammate turning the result into feedback synthesis prompt pattern with source notes, constraints, and review checklist in the same run.

Rough note

A PM has 40 support tickets and 12 interview notes about reporting exports being confusing. The rough note says: "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." The desired result is a feedback synthesis for a product team, stakeholder, customer researcher, or release owner.

Constraint to keep visible

The saved version must keep feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence and the reuse fields, not only the finished phrasing. Carry this rule into every section: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

What the user brought

The supplied case is "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.", so the answer should begin from the user's actual wording and not from broad synthesize feedback advice.

The finished a feedback synthesis should point back to feedback items, segments, frequency, severity, quotes, and product area and show how theme frequency, segment contrast, quote evidence, and product implication changed the answer.

What is still missing

The model should ask for audience, channel, approval owner, and any proof needed for source notes, examples, constraints, and reviewer judgment before it treats the result as usable.

Missing inputs belong in a needs-checking line, not inside polished wording that a product team, stakeholder, customer researcher, or release owner might treat as settled.

Who accepts the answer

the teammate turning the result into feedback synthesis prompt pattern with source notes, constraints, and review checklist should inspect feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, compare the answer with the rough note, and decide whether the output is ready, repairable, or too thin.

The page should leave a visible owner for the final check instead of implying that ChatGPT approval is enough.

What gets saved

The reusable version should keep variables for source notes, audience, reviewer, proof need, stop rule, and theme frequency, segment contrast, quote evidence, and product implication.

One-time details should be removed only after the accepted answer proves that a structured analysis table with claims, evidence, gaps, and recommended next step works for this case.

Before copying

Can the user point to the exact feedback items, segments, frequency, severity, quotes, and product area ChatGPT is allowed to use?
Is theme frequency, segment contrast, quote evidence, and product implication visible before the prompt asks for a feedback synthesis?
Has the user named the reviewer who checks feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence?
Is there a stop rule for unsupported claims about source notes, examples, constraints, and reviewer judgment?

Checks before sharing

Compare the first answer with "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." and mark any section that invents context.
Check whether the output is shaped as a structured analysis table with claims, evidence, gaps, and recommended next step, not a general explanation.
Move uncertain claims into a needs-checking block before sharing the answer with a product team, stakeholder, customer researcher, or release owner.
Save the pattern as feedback synthesis prompt pattern with source notes, constraints, and review checklist only after private or one-time details become variables.

Run this case first

Use this case file before writing. Start from this rough note: "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." Build a feedback synthesis as a structured analysis table with claims, evidence, gaps, and recommended next step. Keep theme frequency, segment contrast, quote evidence, and product implication visible, separate supplied facts from assumptions, ask for missing proof around source notes, examples, constraints, and reviewer judgment, name the teammate turning the result into feedback synthesis prompt pattern with source notes, constraints, and review checklist as the checker, and stop before using any claim that the source notes do not support.

The page has done its job when the user can accept, repair, or rerun the answer without guessing why. The accepted version should tell a product team, stakeholder, customer researcher, or release owner what is ready, what needs checking, and which fields the next user must replace before rerunning the prompt.

Input triage before running ChatGPT

Which problem is most likely to break this synthesize feedback run before a product team, stakeholder, customer researcher, or release owner can use it?

Selected issue

Missing context

Build context

Symptom: Synthesize Feedback starts from a rough note like "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." but the audience, decision, or approval point is still implied.
Ask now: What does a product team, stakeholder, customer researcher, or release owner already know, what source notes are available, and what must the final a feedback synthesis decide?
Do next: Ask ChatGPT to list missing inputs before it writes a feedback synthesis, then answer only the questions that change the final decision.
Prompt move: Before writing, ask me up to four questions needed to produce a structured analysis table with claims, evidence, gaps, and recommended next step; do not fill gaps with assumptions.
Stop if: Stop if the answer sounds polished but still cannot show the source notes behind theme frequency, segment contrast, quote evidence, and product implication.
Who checks it: a product team, stakeholder, customer researcher, or release owner

Build context Readiness check

Notes to save before reusing this prompt

Sort the rough note "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." before running synthesize feedback in a product decision workflow where evidence and tradeoffs need to stay visible. This note sheet tells ChatGPT what it may use, what it must label, and which part the owner sending this to a product team, stakeholder, customer researcher, or release owner checks before a product team, stakeholder, customer researcher, or release owner sees feedback theme table with quote evidence. For product managers feedback synthesis, current source notes should come first; stale or partial inputs should trigger a fresh feedback theme table with quote evidence pass instead of another saved answer.

Details copied from the user's case

Capture: Capture the concrete case first: A PM has 40 support tickets and 12 interview notes about reporting exports being confusing. The note says "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." and the requested asset is feedback theme table with quote evidence. For product managers feedback synthesis, current source notes should come first; stale or partial inputs should trigger a fresh feedback theme table with quote evidence pass instead of another saved answer.
Keep: Keep the facts that directly affect a structured analysis table with claims, evidence, gaps, and recommended next step, especially the audience, task focus, channel, and any details already present in feedback items, segments, frequency, severity, quotes, and product area.
Verify: Verify that every useful line in the answer can point back to the rough note or to feedback items, segments, frequency, severity, quotes, and product area.
Prompt direction: Tell ChatGPT to use only listed facts for the first pass and to put any extra idea in a needs-checking line.
Who checks it: the owner sending this to a product team, stakeholder, customer researcher, or release owner checks whether the answer still reflects feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence after the first pass.
If skipped: If this row is skipped, a feedback synthesis can sound specific while drifting into generic synthesize feedback advice.

Guesses that need a review line

Capture: List what the user did not provide but the answer may need: missing audience detail, missing proof around source notes, examples, constraints, and reviewer judgment, or an approval step for a product team, stakeholder, customer researcher, or release owner.
Keep: Keep assumptions outside the usable sections until the user confirms them or chooses a safer fallback.
Verify: Check whether the answer names what is unknown before it recommends wording, order, or next steps.
Prompt direction: Ask ChatGPT to return a short assumption list before writing any final copy or checklist.
Who checks it: the owner sending this to a product team, stakeholder, customer researcher, or release owner decides which assumptions are acceptable and which ones need another user answer.
If skipped: If assumptions are hidden, the answer may pass a style check while failing the real decision about theme frequency, segment contrast, quote evidence, and product implication.

Boundaries that decide readiness

Capture: Record the rule from this case: The prompt must preserve evidence and uncertainty instead of forcing one tidy answer. Also include Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided. and this field friction before the model writes: feedback synthesis can flatten contradictions into one tidy recommendation. Failure pattern for feedback synthesis with product managers: the feedback synthesis can sound polished while feedback synthesis can flatten contradictions into one tidy recommendation, so the page should make that miss easy to catch.
Keep: Keep the constraint near the requested format so it governs the whole a structured analysis table with claims, evidence, gaps, and recommended next step, not only the final paragraph.
Verify: Check whether the answer obeys the constraint even when it would be easier to produce a smoother or broader response.
Prompt direction: Tell ChatGPT to stop and ask before continuing if the constraint conflicts with the requested output.
Who checks it: the owner sending this to a product team, stakeholder, customer researcher, or release owner checks the constraint before approving any handoff to a product team, stakeholder, customer researcher, or release owner.
If skipped: If this row is skipped, the model may produce a fluent answer that the user cannot safely use.

Sensitive context to keep out

Capture: Mark names, private identifiers, account details, student or customer records, confidential strategy, and one-time case details before they enter the prompt.
Keep: Keep summaries that preserve meaning but remove details that should not travel into a reusable prompt.
Verify: Check whether the answer repeats private or one-time information that should have stayed outside the saved version.
Prompt direction: Ask ChatGPT to replace private details with role-safe descriptions and to flag anything it cannot safely generalize.
Who checks it: the owner sending this to a product team, stakeholder, customer researcher, or release owner confirms that the final a feedback synthesis can be shared in the intended channel.
If skipped: If this row is skipped, the page helps the user copy faster but may teach a bad reuse habit.

Items that should become blanks

Capture: Name the fields that should change next time: source notes, audience, output format, proof needed for source notes, examples, constraints, and reviewer judgment, reviewer, and stop rule.
Keep: Keep theme frequency, segment contrast, quote evidence, and product implication, feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, and feedback theme table with quote evidence as required fields so the saved prompt does not collapse into a generic role prompt. Approval for product managers feedback synthesis belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the feedback theme table with quote evidence review standard visible.
Verify: Check whether the reusable version still asks for the facts that made this case work, instead of saving the finished wording alone.
Prompt direction: Tell ChatGPT to return a reusable prompt with variables and a reject-if rule after the human accepts the current answer.
Who checks it: the owner sending this to a product team, stakeholder, customer researcher, or release owner signs off only when private details are removed and the next user can fill the variables without guessing.
If skipped: If this row is skipped, the user may save polished wording instead of a repeatable feedback synthesis prompt pattern with source notes, constraints, and review checklist.

Copy these saved notes with the prompt only after the product manager can point to the supplied facts, the uncertain parts, the hard limit, the reusable fields for theme frequency, segment contrast, quote evidence, and product implication, and the place where feedback synthesis can flatten contradictions into one tidy recommendation. Approval for product managers feedback synthesis belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the feedback theme table with quote evidence review standard visible. Outside proof for feedback synthesis with product managers: an independent resource must mention the feedback synthesis page visibly before feedback theme table with quote evidence becomes an authority claim.

Iteration loop: run the prompt as a working thread

Synthesize Feedback moves forward only when each answer still points back to the original note. Start from the rough note "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.", then ask ChatGPT to write, question, challenge, and hand off feedback theme table with quote evidence without hiding source notes, examples, constraints, and reviewer judgment. For product managers feedback synthesis, current source notes should come first; stale or partial inputs should trigger a fresh feedback theme table with quote evidence pass instead of another saved answer.

Thread goal

Thread goal for product manager: turn the rough case from A PM has 40 support tickets and 12 interview notes about reporting exports being confusing. into a structured analysis table with claims, evidence, gaps, and recommended next step for a product team, stakeholder, customer researcher, or release owner, while the teammate comparing the answer with the rough note can still inspect feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, theme frequency, segment contrast, quote evidence, and product implication, unsupported assumptions, and the friction that feedback synthesis can flatten contradictions into one tidy recommendation. Failure pattern for feedback synthesis with product managers: the feedback synthesis can sound polished while feedback synthesis can flatten contradictions into one tidy recommendation, so the page should make that miss easy to catch.

Synthesize Feedback ends with a decision by the teammate comparing the answer with the rough note, not with the smoothest sounding ChatGPT paragraph. The loop is stronger than a one-shot prompt because it makes the model show its first version, missing context, challenge, and reusable handoff before the product manager treats feedback theme table with quote evidence as finished. Approval for product managers feedback synthesis belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the feedback theme table with quote evidence review standard visible.

1
Source pass
Use this first when the source note is messy but concrete enough to produce a reviewable a feedback synthesis.
```
Synthesize Feedback first run: use the rough note "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." from A PM has 40 support tickets and 12 interview notes about reporting exports being confusing.; build a feedback synthesis as a structured analysis table with claims, evidence, gaps, and recommended next step; rely on supplied facts for the main answer, label assumptions, keep theme frequency, segment contrast, quote evidence, and product implication visible, and end with the proof still needed for source notes, examples, constraints, and reviewer judgment.
```
Keep
Keep the exact source note, the requested output shape, and any line that directly supports theme frequency, segment contrast, quote evidence, and product implication.
Accept if
Accept the first answer only if it separates source-backed details from assumptions and gives the teammate comparing the answer with the rough note something concrete to inspect.
Stop if
Stop if the answer invents missing context, treats source notes, examples, constraints, and reviewer judgment as proven, or drifts into general synthesize feedback advice.
2
Clarify pass
Use this after the first answer when the shape is useful but the model skipped questions that block real use.
```
Synthesize Feedback gap fill: compare the first answer with the rough note already in this thread; name the missing inputs that prevent a product team, stakeholder, customer researcher, or release owner from using the result; ask up to five questions grouped by audience, source proof, channel, reviewer, and reuse field, then say which part can continue with a safe fallback.
```
Keep
Keep any section that maps to feedback items, segments, frequency, severity, quotes, and product area; move guesses into open questions instead of deleting the whole answer.
Accept if
Accept this turn only if the missing questions would help a product manager make a clearer decision before rerunning or revising.
Stop if
Stop if the model asks generic questions that do not affect a structured analysis table with claims, evidence, gaps, and recommended next step, feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, or the final handoff.
3
Claim check
Use this before sharing the answer, especially when it sounds polished enough to hide weak evidence.
```
Synthesize Feedback skeptic pass: compare the current answer with the rough note already in this thread; mark unsupported claims, unclear owners, privacy issues, and weak spots around source notes, examples, constraints, and reviewer judgment; give each issue a repair sentence that keeps theme frequency, segment contrast, quote evidence, and product implication visible without adding new facts.
```
Keep
Keep the usable structure from the first answer, but require every claim and recommendation to survive the skeptic pass.
Accept if
Accept this turn only if it gives repair instructions that the teammate comparing the answer with the rough note can apply without rewriting the whole asset from scratch.
Stop if
Stop if the critique only says the answer is good or bad without naming the exact line, risk, and repair move.
4
Saveable prompt
Use this after the answer survives the gap fill and skeptic pass and is ready to become a working asset.
```
Synthesize Feedback handoff: prepare the accepted a feedback synthesis, a needs-checking block for source notes, examples, constraints, and reviewer judgment, a reviewer note for the teammate comparing the answer with the rough note, and a reusable version with variables for source notes, audience, output format, proof need, stop rule, and theme frequency, segment contrast, quote evidence, and product implication; remove one-time private details before saving.
```
Keep
Keep the accepted wording, the repair decisions, and the variables that make feedback synthesis prompt pattern with source notes, constraints, and review checklist safe to rerun.
Accept if
Accept the handoff only if a product team, stakeholder, customer researcher, or release owner can tell what is ready, what needs review, and what must be replaced next time.
Stop if
Stop if the final version saves polished case details instead of a reusable prompt structure with visible boundaries.

Prompt readiness check before you copy

Use this quick pass to decide whether to collect more context, build a context pack, or run the prompt and grade the answer.

0/6 ready

Source notes readyNeed themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions. a product team, stakeholder, customer researcher, or release owner can be misled by polished wording, so the reviewer check needs to stay visible. The model should not smooth away the missing context. Treat synthesize feedback as first-pass evidence for a feedback synthesis. Synthesize Feedback works better when the context is in named fields, because each variable can be checked before copying.Audience or recipient knownProduct Managers who have real notes or context and need a structured first version of a feedback synthesis.Constraints and no-go rules clearPrompts should surface assumptions and evidence gaps instead of pretending strategy is decided. Ask ChatGPT to label assumptions and verification needs before using a feedback synthesis.Facts to verify listedFeedback Synthesis source sort: which lines in the rough note are facts, preferences, constraints, or open questions? Feedback Synthesis blank rule: what should stay blank or flagged if source notes, examples, constraints, and reviewer judgment is missing?Checker is namedGive approval work to the person who can spot when theme frequency, segment contrast, quote evidence, and product implication has drifted from the user's source material.Reuse rule clearSave the feedback synthesis answer only when private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a feedback synthesis, and the review rule for theme frequency, segment contrast, quote evidence, and product implication still appears in the reusable prompt. Approval for product managers feedback synthesis belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the feedback theme table with quote evidence review standard visible.

Do next

Collect context first

The prompt can run, but the answer will likely fill gaps with assumptions. Start by collecting notes, constraints, and the person who will check it.

Use this prompt when: Product Managers who have real notes or context and need a structured first version of a feedback synthesis.
Wait if: Discard the answer if it cannot trace which details came from the source and which details were inferred.
Who checks it: Give approval work to the person who can spot when theme frequency, segment contrast, quote evidence, and product implication has drifted from the user's source material.
Reuse rule: Save the feedback synthesis answer only when private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a feedback synthesis, and the review rule for theme frequency, segment contrast, quote evidence, and product implication still appears in the reusable prompt. Approval for product managers feedback synthesis belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the feedback theme table with quote evidence review standard visible.

Collect context Open prompt Context pack Output grader

Session handoff: finish the run without losing the thread

Track the four decisions that turn a copied prompt into a usable work session.

0/4 steps

Context readyBuild a context pack before copying anything.Open stepPrompt runRun the recommended prompt with the prepared context.Open stepAnswer checkedGrade the answer against the task checks and repair weak sections.Open stepReuse decisionDecide whether to save the run, rerun it, or discard it.Open step

Next action

Collect working context

Start by getting source notes, constraints, the person who checks it, and the stop rule into one place.

Working note: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions. a product team, stakeholder, customer researcher, or release owner can be misled by polished wording, so the reviewer check needs to stay visible. The model should not smooth away the missing context. Treat synthesize feedback as first-pass evidence for a feedback synthesis. Synthesize Feedback works better when the context is in named fields, because each variable can be checked before copying.
Who checks it: Give approval work to the person who can spot when theme frequency, segment contrast, quote evidence, and product implication has drifted from the user's source material.
Stop rule: Discard the answer if it cannot trace which details came from the source and which details were inferred.
Reuse choice: Save the feedback synthesis answer only when private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a feedback synthesis, and the review rule for theme frequency, segment contrast, quote evidence, and product implication still appears in the reusable prompt. Approval for product managers feedback synthesis belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the feedback theme table with quote evidence review standard visible.

Open next step Prompt Context Grade

Work note: what the rough note changes

Use this when the answer must carry the original note, the missing context, and the review decision into the final prompt run.

Original working note

For feedback synthesis, the source note starts plainly: "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." is the rough request. The ready check for feedback synthesis is simple: before anyone reuses it, a feedback synthesis should preserve theme frequency, segment contrast, quote evidence, and product implication, show who checks it, and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

Received note: Received note for Product Managers Synthesize Feedback: "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." arrives as the source note inside a product decision workflow where evidence and tradeoffs need to stay visible, with The prompt must preserve evidence and uncertainty instead of forcing one tidy answer. as the first human concern and feedback theme table with quote evidence as the target artifact.
Question before run: Before copying, ask what a product team, stakeholder, customer researcher, or release owner must be able to decide from this a feedback synthesis, and which source detail would change that decision.
First answer flaw: First answer flaw for Product Managers Synthesize Feedback: the first answer can look useful but merge facts, assumptions, and missing details, making a feedback synthesis hard for a teammate who can check feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence to verify.
Human edit: Human edit for Product Managers Synthesize Feedback: move unsupported claims into a check-needed line, keep theme frequency, segment contrast, quote evidence, and product implication in the first section, and make a structured analysis table with claims, evidence, gaps, and recommended next step readable for a product team, stakeholder, customer researcher, or release owner; the editor also has to replace polished filler with source-backed lines inside a feedback synthesis; the edit has to preserve "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." and leave feedback theme table with quote evidence ready for a reviewer, not just prettier.
Reusable field: Reusable field for Product Managers Synthesize Feedback: keep the reusable version as feedback synthesis prompt pattern with source notes, constraints, and review checklist only after the note becomes variables, the reviewer stays named, and source notes, examples, constraints, and reviewer judgment has a visible checking slot. Keep the field set alert to this repeat risk: feedback synthesis can flatten contradictions into one tidy recommendation.

Questions before reuse

Feedback Synthesis source sort: which lines in the rough note are facts, preferences, constraints, or open questions?
Feedback Synthesis blank rule: what should stay blank or flagged if source notes, examples, constraints, and reviewer judgment is missing?
Feedback Synthesis reviewer stop: which section should a peer who knows feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence inspect before anyone uses the answer?

Who checks it

Give approval work to the person who can spot when theme frequency, segment contrast, quote evidence, and product implication has drifted from the user's source material.

Feedback Synthesis source note: treat "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." as the factual base, not decorative background; the next usable asset is feedback theme table with quote evidence.
Feedback Synthesis evidence check: mark any section where source notes, examples, constraints, and reviewer judgment is assumed instead of shown, especially when feedback synthesis can flatten contradictions into one tidy recommendation.
Feedback Synthesis scope check: keep the answer on theme frequency, segment contrast, quote evidence, and product implication; do not drift away from a product decision workflow where evidence and tradeoffs need to stay visible.
Feedback Synthesis final polish: rewrite final wording only after feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence is clear enough for a peer who knows feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, then replace polished filler with source-backed lines inside a feedback synthesis.
Feedback Synthesis freshness rule: For product managers feedback synthesis, current source notes should come first; stale or partial inputs should trigger a fresh feedback theme table with quote evidence pass instead of another saved answer.

Usable output

The target feedback synthesis result should return a structured analysis table with claims, evidence, gaps, and recommended next step; separate supplied notes from assumptions, name the review owner, prepare feedback theme table with quote evidence, and make the human pass focused on feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.

Save this noteRough note that changes the prompt: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions. Task-specific source material: feedback items, segments, frequency, severity, quotes, and product area Human check to keep visible: feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence

Stop hereDiscard the answer if it cannot trace which details came from the source and which details were inferred.

Save for reuseSave the feedback synthesis answer only when private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a feedback synthesis, and the review rule for theme frequency, segment contrast, quote evidence, and product implication still appears in the reusable prompt. Approval for product managers feedback synthesis belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the feedback theme table with quote evidence review standard visible.

Build context pack Check output Open work sample

Prompt run from pasted notes

Use this pass to see what should happen between the rough note and the answer that is safe enough to review.

Pasted notes

product manager start this synthesize feedback run from: A PM has 40 support tickets and 12 interview notes about reporting exports being confusing. The source says "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." The answer needs to become feedback theme table with quote evidence for a product team, stakeholder, customer researcher, or release owner; the run lives in a product decision workflow where evidence and tradeoffs need to stay visible and has to respect this rule before any wording polish: The prompt must preserve evidence and uncertainty instead of forcing one tidy answer.

Why this input is messy

Clean up the synthesize feedback note first because the note carries facts, preferences, limits, and open approval points in one line; a quick answer can smooth over source notes, examples, constraints, and reviewer judgment, miss theme frequency, segment contrast, quote evidence, and product implication, or make a feedback synthesis look ready before a peer who knows feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence checks it, especially when feedback synthesis can flatten contradictions into one tidy recommendation.

First prompt move

Open this synthesize feedback run by telling ChatGPT to tell ChatGPT to convert the rough note into named fields first, then pause if the audience, checker, or proof for source notes, examples, constraints, and reviewer judgment is missing; this is a context pass before polish because a structured analysis table with claims, evidence, gaps, and recommended next step has to stay traceable to the original note.

Questions ChatGPT should ask

Reader detail in synthesize feedback: who will read this a feedback synthesis, and what do they already know?
Source detail in synthesize feedback: which note details are verified facts, and which parts still need source notes, examples, constraints, and reviewer judgment?
Constraint detail in synthesize feedback: what tone, length, channel, or approval rule matters before the answer reaches a product team, stakeholder, customer researcher, or release owner?
Reuse detail in synthesize feedback: which person will inspect feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, and what would make the answer unsafe to reuse?

Usable answer shape

The result for synthesize feedback should return a structured analysis table with claims, evidence, gaps, and recommended next step, separate source-backed sections from assumptions and open questions, show how theme frequency, segment contrast, quote evidence, and product implication shaped the result, name a peer who knows feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, and end with a short check for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence before the answer is shared or saved.

Human revision

Product Managers final edit for synthesize feedback should keep the structure that saved time, replace polished filler with source-backed lines inside a feedback synthesis, remove private or one-time information, and rewrite the final wording for a product team, stakeholder, customer researcher, or release owner; compare the answer with "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." and make sure The final synthesis should show what is known, what is noisy, and what needs more research.

Save or discard

Keep or rerun synthesize feedback based on whether the note, output shape, checker, feedback theme table with quote evidence, and reuse rule stay visible; rerun or discard the answer when it could fit another product manager task without changing the source notes, or when source notes, examples, constraints, and reviewer judgment is implied but not checkable.

Run prompt Grade answer Repair answer

Why this page is not interchangeable

Work moment

Open this page when a fluent answer might hide the failure mode: feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence has not been checked against the real source notes.

Why this page

Do first

Run the answer through the repair section if it sounds finished before it proves how theme frequency, segment contrast, quote evidence, and product implication shaped the result.

Next best workflow

Define acceptance criteriaUseful next step when this workflow needs a related product managers output or review pass.

What to look for

Rough note that changes the prompt: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.
Task-specific source material: feedback items, segments, frequency, severity, quotes, and product area
Human check to keep visible: feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence
Evidence pressure point: source notes, examples, constraints, and reviewer judgment

Wrong page if

The user cannot provide feedback items, segments, frequency, severity, quotes, and product area and would need ChatGPT to invent the important facts.
The desired result is not a feedback synthesis or cannot be shaped as a structured analysis table with claims, evidence, gaps, and recommended next step.
The task would be safer on Define acceptance criteria because the main decision is closer to that workflow.

Nearby workflow differences

Use this when the page looks close, but the thing you need to make or the person checking it is different.

Write PRDs: Use this page
Stay with ChatGPT Prompts for Product Managers to Synthesize Feedback when your notes already include this check: Task-specific source material: feedback items, segments, frequency, severity, quotes, and product area.; Switch instead
Switch to Write PRDs when the thing you need to make or the person checking it matches that workflow: Useful next step when this workflow needs a related product managers output or review pass.; Keep separate
Keep the pages separate if The user cannot provide feedback items, segments, frequency, severity, quotes, and product area and would need ChatGPT to invent the important facts.
Write user stories: Use this page
Stay with ChatGPT Prompts for Product Managers to Synthesize Feedback when your notes already include this check: Human check to keep visible: feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.; Switch instead
Switch to Write user stories when the thing you need to make or the person checking it matches that workflow: Useful next step when this workflow needs a related product managers output or review pass.; Keep separate
Keep the pages separate if The desired result is not a feedback synthesis or cannot be shaped as a structured analysis table with claims, evidence, gaps, and recommended next step.
Define acceptance criteria: Use this page
Stay with ChatGPT Prompts for Product Managers to Synthesize Feedback when your notes already include this check: Evidence pressure point: source notes, examples, constraints, and reviewer judgment.; Switch instead
Switch to Define acceptance criteria when the thing you need to make or the person checking it matches that workflow: Useful next step when this workflow needs a related product managers output or review pass.; Keep separate
Keep the pages separate if The task would be safer on Define acceptance criteria because the main decision is closer to that workflow.

Run the page by work state

Begin with the messy notes, then choose the prompt path that matches the current state of the work.

Build The Asset

Use this when the notes are ready and the next useful output is a structured analysis table with claims, evidence, gaps, and recommended next step, not more brainstorming.

Open section

Do now: Copy the recommended prompt, replace the variables, and ask for a feedback synthesis with assumptions separated from source-backed details.
Bring: Bring the task focus: theme frequency, segment contrast, quote evidence, and product implication. Add the channel, deadline, and any required sections.
Stop if: Stop if the first answer gives broad advice instead of a concrete a feedback synthesis.
Next check: Use the run sheet's review mode before sharing anything with a product team, stakeholder, customer researcher, or release owner.

Bring this

Bring feedback items, segments, frequency, severity, quotes, and product area; add the reviewer, the audience, and the boundary from this case: The prompt must preserve evidence and uncertainty instead of forcing one tidy answer.

Reusable handoff

The final pass should leave a feedback synthesis ready for a product team, stakeholder, customer researcher, or release owner, with the uncertain parts marked instead of smoothed over.

Reality checks

Does the page-specific note "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." change the prompt, or could this still fit another task unchanged?
Can the reviewer check feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence without asking ChatGPT to invent missing facts?
Does the answer become a feedback synthesis, or does it stay at broad synthesize feedback advice?
Would a product team, stakeholder, customer researcher, or release owner know what was provided, what was assumed, and what still needs review?

Prompt path by where the work is stuck

advanced

Synthesize feedback Evidence-Aware Working Copy Prompt

Use this when the source material is ready and the answer needs to become a feedback synthesis.

Use this when: Use before asking ChatGPT for synthesize feedback so the model has enough task-specific context.
When this fits: Turn feedback items, segments, frequency, severity, quotes, and product area into a feedback synthesis for a product team, stakeholder, customer researcher, or release owner.
Do next: Review the answer before making it reusable and require a short proof pass focused on source notes, examples, constraints, and reviewer judgment.

Open this prompt card

Context pack before copying

0/8

Source notes are availableAudience or recipient is namedConstraints are explicitFacts to verify are listedChecker is named

Working notesConstraintsWho checks it

Ready to paste

Context brief for the next prompt

Context pack for Product Managers to Synthesize Feedback

Goal: Find a copyable prompt workbench that helps product managers synthesize feedback with the right source material, review lens, example, and follow-up prompts.
Working scenario: A PM has 40 support tickets and 12 interview notes about reporting exports being confusing. The synthesize feedback work happens inside a product decision workflow where evidence and tradeoffs need to stay visible. For product managers feedback synthesis, current source notes should come first; stale or partial inputs should trigger a fresh feedback theme table with quote evidence pass instead of another saved answer. Approval for product managers feedback synthesis belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the feedback theme table with quote evidence review standard visible. For synthesize feedback, a short prompt usually misses the constraint stack here: the value comes from evidence, order of review, and the decision made after the answer.

What I know:
Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions. a product team, stakeholder, customer researcher, or release owner can be misled by polished wording, so the reviewer check needs to stay visible. The model should not smooth away the missing context. Treat synthesize feedback as first-pass evidence for a feedback synthesis. Synthesize Feedback works better when the context is in named fields, because each variable can be checked before copying.

Constraints and no-go rules:
Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided. Ask ChatGPT to label assumptions and verification needs before using a feedback synthesis. Do not paste private names, identifiers, account details, student records, customer records, or confidential strategy when a summarized version is enough.

Who checks it:
Give approval work to the person who can spot when theme frequency, segment contrast, quote evidence, and product implication has drifted from the user's source material.

Readiness checks:
- [ ] Source notes are available
- [ ] Audience or recipient is named
- [ ] Constraints are explicit
- [ ] Facts to verify are listed
- [ ] Checker is named

Ask ChatGPT to request missing context before writing. Keep assumptions separate from source-based claims.

Output grader before reuse

0/5

Paste ChatGPT output

0 words checked against Give approval work to the person who can spot when theme frequency, segment contrast, quote evidence, and product implication has drifted from the user's source material.

Source review, synthesize feedback: the answer uses the supplied feedback items, segments, frequency, severity, quotes, and product area and does not fill missing facts with confident guesses.Output shape, synthesize feedback: the result clearly becomes a feedback synthesis, not broad advice about the task.Handoff clarity, synthesize feedback: the answer names missing inputs and the next human check for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.Audience fit, synthesize feedback: the result works for a product team, stakeholder, customer researcher, or release owner, including channel, tone, length, and decision context.Risk boundary, synthesize feedback: the final version respects Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

Needs another review pass

a feedback synthesis final pass: keep the useful structure, then replace polished filler with source-backed lines inside a feedback synthesis; readiness means a product team, stakeholder, customer researcher, or release owner can see what was provided, what was assumed, why feedback synthesis can flatten contradictions into one tidy recommendation, and what still needs review.

Task-specific output diagnosis

Paste the first Synthesize Feedback answer and compare it with "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." before checking style. A useful product manager output must prove it belongs to this page by keeping theme frequency, segment contrast, quote evidence, and product implication, a structured analysis table with claims, evidence, gaps, and recommended next step, and the task reviewer visible.

Pass when

The answer uses "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." as the controlling case, not as decoration, and turns it into a structured analysis table with claims, evidence, gaps, and recommended next step with theme frequency, segment contrast, quote evidence, and product implication still visible.
The answer shows which lines come from "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." and which lines remain assumptions before a product team, stakeholder, customer researcher, or release owner sees the feedback synthesis.
The answer gives the task reviewer a clear check tied to "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.", especially the point where source notes, examples, constraints, and reviewer judgment cannot be treated as proven.
The answer can become feedback synthesis prompt pattern with source notes, constraints, and review checklist only after the one-time facts in "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." are replaced with variables and the stop rule stays attached.

False pass

It sounds polished but never quotes or preserves the specific case in "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.", so the synthesize feedback output could fit another page.
It gives a generic next step while hiding theme frequency, segment contrast, quote evidence, and product implication, which makes the answer feel useful before it can support the real a feedback synthesis.
It skips the task reviewer or buries the review check, so the user cannot tell who should approve the answer before reuse.
It could fit a neighboring workflow because the response hides a structured analysis table with claims, evidence, gaps, and recommended next step, source notes, examples, constraints, and reviewer judgment, or the source material that makes this synthesize feedback page different.

Repair next

Rewrite the opening around "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." and keep the first sentence tied to theme frequency, segment contrast, quote evidence, and product implication before improving tone or length.
Add a needs-checking block for source notes, examples, constraints, and reviewer judgment, then separate supplied facts from assumptions before returning a structured analysis table with claims, evidence, gaps, and recommended next step.
Mark the line the task reviewer must inspect for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, and move unsupported claims out of the usable answer.
Replace one-time details with variables for the saved feedback synthesis prompt pattern with source notes, constraints, and review checklist, then rerun only the section that failed the synthesize feedback check.

Red flags

Evidence issue, synthesize feedback: the answer invents or overstates source notes, examples, constraints, and reviewer judgment.
Task drift, synthesize feedback: it ignores theme frequency, segment contrast, quote evidence, and product implication and moves into a neighboring workflow.
Readiness gap, synthesize feedback: it sounds complete while leaving feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence impossible to verify.
Privacy issue, synthesize feedback: it includes details that should have been summarized or removed.
Generic output, synthesize feedback: it produces a broad template that could fit any task in the role.

Answer repair for replies that sound right but are not ready

Weak answer pattern

The first Product Managers Synthesize Feedback pass copies a line like "I turned the notes into a clean version with the key points, a simple structure, and a recommended action" and then moves on. Synthesize Feedback failure to avoid for product manager: it treats the task as generic advice instead of a case with constraints; the actual note to protect is Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.

Why it fails

Synthesize Feedback repair note: the response has a tidy shape, yet the useful parts cannot be traced back to the rough note The next pass must bring back theme frequency, segment contrast, quote evidence, and product implication, show which parts depend on source notes, examples, constraints, and reviewer judgment, make a peer who can check feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence visible before a product team, stakeholder, customer researcher, or release owner sees the result, and handle the real friction: feedback synthesis can flatten contradictions into one tidy recommendation.

Trace the rough note

Problem: The answer mentions a feedback synthesis but does not reflect the concrete case: A PM has 40 support tickets and 12 interview notes about reporting exports being confusing.
Repair: Rewrite the first section around the user note, then mark which details came from the note, which details still need confirmation, and where feedback theme table with quote evidence changes the output.

Name the reviewer

Problem: The answer can move forward without anyone checking feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.
Repair: Add a reviewer line for a peer who can check feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, plus one question that must be answered before the result is shared.

Protect the evidence

Problem: The answer can imply source notes, examples, constraints, and reviewer judgment even when the source notes do not support it.
Repair: Keep unsupported claims in a separate needs-checking block and remove any claim the user cannot verify.

Keep the task narrow

Problem: The response can drift from synthesize feedback into broad advice that does not produce a structured analysis table with claims, evidence, gaps, and recommended next step.
Repair: Force the final answer back into a structured analysis table with claims, evidence, gaps, and recommended next step, keep theme frequency, segment contrast, quote evidence, and product implication as the main decision point, and replace polished filler with source-backed lines inside a feedback synthesis.

Human-edited direction

Human Synthesize Feedback revision for Product Managers: start with the actual case, name the audience, return a structured analysis table with claims, evidence, gaps, and recommended next step, keep supplied notes, assumptions, and missing checks separate, then replace polished filler with source-backed lines inside a feedback synthesis, tell a product team, stakeholder, customer researcher, or release owner what is ready to use, what a peer who can check feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence must verify, and how the answer becomes feedback synthesis prompt pattern with source notes, constraints, and review checklist without private or one-time details.

Rerun prompt

Rerun Product Managers Synthesize Feedback: repair this synthesize feedback answer, keep the result focused on theme frequency, segment contrast, quote evidence, and product implication, return a structured analysis table with claims, evidence, gaps, and recommended next step, put unsupported claims about source notes, examples, constraints, and reviewer judgment in a needs-checking block, name the reviewer as a peer who can check feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, protect this boundary "Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.", and use only these source notes: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.

Accept when

The answer visibly uses the rough note instead of generic synthesize feedback advice.
The result is shaped as a structured analysis table with claims, evidence, gaps, and recommended next step and can be checked by a peer who can check feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.
Any uncertain point about source notes, examples, constraints, and reviewer judgment is separated from the usable parts.
The reusable version keeps theme frequency, segment contrast, quote evidence, and product implication and removes one-time or private details.

Reject when

The answer could fit another product manager task without changing more than the title.
The response sounds polished but cannot show where the key claims came from.
The result skips feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence or hides who should approve it.
The answer asks the user to trust the model instead of checking the source notes.

Start from the user's actual notes

Search intent angle

PMs need feedback synthesis prompts that group evidence without flattening contradictory signals. For synthesize feedback, the page has to answer a product managers synthesize feedback need where feedback synthesis can flatten contradictions into one tidy recommendation. Search edge for feedback synthesis with product managers: show feedback theme table with quote evidence, a human review path for a feedback synthesis, and the task-specific reason the page deserves the query. Outside proof for feedback synthesis with product managers: an independent resource must mention the feedback synthesis page visibly before feedback theme table with quote evidence becomes an authority claim. For a feedback synthesis for product managers, the useful distinction is that the useful promise is a safer run: source material in, a feedback synthesis out, with assumptions and review gaps left visible.

Concrete scenario

A PM has 40 support tickets and 12 interview notes about reporting exports being confusing. The synthesize feedback work happens inside a product decision workflow where evidence and tradeoffs need to stay visible. For product managers feedback synthesis, current source notes should come first; stale or partial inputs should trigger a fresh feedback theme table with quote evidence pass instead of another saved answer. Approval for product managers feedback synthesis belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the feedback theme table with quote evidence review standard visible. For synthesize feedback, a short prompt usually misses the constraint stack here: the value comes from evidence, order of review, and the decision made after the answer.

Real user input

Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions. a product team, stakeholder, customer researcher, or release owner can be misled by polished wording, so the reviewer check needs to stay visible. The model should not smooth away the missing context. Treat synthesize feedback as first-pass evidence for a feedback synthesis. Synthesize Feedback works better when the context is in named fields, because each variable can be checked before copying.

Editor take

The prompt must preserve evidence and uncertainty instead of forcing one tidy answer. In this synthesize feedback review, the edit is to replace polished filler with source-backed lines inside a feedback synthesis. Failure pattern for feedback synthesis with product managers: the feedback synthesis can sound polished while feedback synthesis can flatten contradictions into one tidy recommendation, so the page should make that miss easy to catch. In the synthesize feedback review, the page should make unsupported assumptions easy to spot before the user treats the answer as ready; compare the answer with the actual notes before reuse.

Human polish

The final synthesis should show what is known, what is noisy, and what needs more research. Approval for product managers feedback synthesis belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the feedback theme table with quote evidence review standard visible. Before handing off synthesize feedback, the last edit should turn the model answer into a practical asset, not just a polished paragraph, with a short record of what changed before reuse and where For product managers feedback synthesis, current source notes should come first; stale or partial inputs should trigger a fresh feedback theme table with quote evidence pass instead of another saved answer.

Fast use path

Main card for a feedback synthesis: begin with one strong prompt and resist combining every card at once.
Source material for a feedback synthesis: replace [source_material] with feedback items, segments, frequency, severity, quotes, and product area.
Audience details for a feedback synthesis: replace broad context with the specific reader, deadline, and format requirement.
Review pass for a feedback synthesis: do one review loop focused on feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence and unsupported assumptions.

Specificity signals

A PM has 40 support tickets and 12 interview notes about reporting exports being confusing.
Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.
feedback items, segments, frequency, severity, quotes, and product area
theme frequency, segment contrast, quote evidence, and product implication
source notes, examples, constraints, and reviewer judgment
Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
feedback theme table with quote evidence
feedback synthesis can flatten contradictions into one tidy recommendation
replace polished filler with source-backed lines inside a feedback synthesis
a product decision workflow where evidence and tradeoffs need to stay visible
For product managers feedback synthesis, current source notes should come first; stale or partial inputs should trigger a fresh feedback theme table with quote evidence pass instead of another saved answer.
Approval for product managers feedback synthesis belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the feedback theme table with quote evidence review standard visible.
Search edge for feedback synthesis with product managers: show feedback theme table with quote evidence, a human review path for a feedback synthesis, and the task-specific reason the page deserves the query.
Failure pattern for feedback synthesis with product managers: the feedback synthesis can sound polished while feedback synthesis can flatten contradictions into one tidy recommendation, so the page should make that miss easy to catch.
Outside proof for feedback synthesis with product managers: an independent resource must mention the feedback synthesis page visibly before feedback theme table with quote evidence becomes an authority claim.

Real use sample: how the messy note changes the prompt

Messy brief

Ask before copying

Feedback Synthesis source sort: which lines in the rough note are facts, preferences, constraints, or open questions?
Feedback Synthesis blank rule: what should stay blank or flagged if source notes, examples, constraints, and reviewer judgment is missing?
Feedback Synthesis reviewer stop: which section should a peer who knows feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence inspect before anyone uses the answer?
Feedback Synthesis stop signal: which visible mistake would stop the team from using the answer?

Checks before sharing

Feedback Synthesis source note: treat "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions." as the factual base, not decorative background; the next usable asset is feedback theme table with quote evidence.
Feedback Synthesis evidence check: mark any section where source notes, examples, constraints, and reviewer judgment is assumed instead of shown, especially when feedback synthesis can flatten contradictions into one tidy recommendation.
Feedback Synthesis scope check: keep the answer on theme frequency, segment contrast, quote evidence, and product implication; do not drift away from a product decision workflow where evidence and tradeoffs need to stay visible.
Feedback Synthesis final polish: rewrite final wording only after feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence is clear enough for a peer who knows feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, then replace polished filler with source-backed lines inside a feedback synthesis.
Feedback Synthesis freshness rule: For product managers feedback synthesis, current source notes should come first; stale or partial inputs should trigger a fresh feedback theme table with quote evidence pass instead of another saved answer.
Feedback Synthesis failure pattern: Failure pattern for feedback synthesis with product managers: the feedback synthesis can sound polished while feedback synthesis can flatten contradictions into one tidy recommendation, so the page should make that miss easy to catch.
Feedback Synthesis decision owner: Approval for product managers feedback synthesis belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the feedback theme table with quote evidence review standard visible.

Before and after

Weak answer risk: The feedback synthesis failure mode is practical: the answer sounds complete while turning "need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions;" into broad advice, hiding missing context around source notes, examples, constraints, and reviewer judgment, and leaving a product team, stakeholder, customer researcher, or release owner without a clear decision path because feedback synthesis can flatten contradictions into one tidy recommendation. Failure pattern for feedback synthesis with product managers: the feedback synthesis can sound polished while feedback synthesis can flatten contradictions into one tidy recommendation, so the page should make that miss easy to catch.
Improved outcome: The target feedback synthesis result should return a structured analysis table with claims, evidence, gaps, and recommended next step; separate supplied notes from assumptions, name the review owner, prepare feedback theme table with quote evidence, and make the human pass focused on feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.
Why it feels real: The feedback synthesis case feels specific because: it starts from messy source notes, a product decision workflow where evidence and tradeoffs need to stay visible, a named review moment, and task-level evidence instead of a clean prompt sentence. For product managers feedback synthesis, current source notes should come first; stale or partial inputs should trigger a fresh feedback theme table with quote evidence pass instead of another saved answer.

Reusable version decision

Save the feedback synthesis answer only when private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a feedback synthesis, and the review rule for theme frequency, segment contrast, quote evidence, and product implication still appears in the reusable prompt. Approval for product managers feedback synthesis belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the feedback theme table with quote evidence review standard visible.

The job this page helps finish

The page should answer the practical question: what should I paste, what should ChatGPT return, and what would make the answer unsafe? It should keep the audience, source material, constraints, and reviewer connected to the same prompt run. The useful version keeps theme frequency, segment contrast, quote evidence, and product implication visible through the handoff.

Use Cases

Turn feedback items, segments, frequency, severity, quotes, and product area into a feedback synthesis for a product team, stakeholder, customer researcher, or release owner.
Review an existing synthesize feedback answer for feedback synthesis checkpoint, missing details, and unsupported claims.
Create a repeatable feedback synthesis prompt pattern with source notes, constraints, and review checklist so the next version starts from stronger context.
Make theme frequency, segment contrast, quote evidence, and product implication visible so the answer stays tied to a feedback synthesis instead of drifting into a neighboring task.
Condense a long ChatGPT answer into a structured analysis table with claims, evidence, gaps, and recommended next step without losing the decisions the human must make.

Input Prep

Write the audience or recipient in one sentence, including what they already know.
Paste or summarize feedback items, segments, frequency, severity, quotes, and product area; do not ask the model to guess it.
Name the final decision the synthesize feedback output must support.
Add constraints such as tone, length, required sections, privacy limits, and forbidden claims.
List the facts that must be checked after ChatGPT answers, especially source notes, examples, constraints, and reviewer judgment.
Add the task-specific focus: theme frequency, segment contrast, quote evidence, and product implication.

Check the answer against real references

What users are trying to finish

For synthesize feedback, the user needs more than sample wording: they need a prompt that names source material, audience, and review owner. A useful result should reduce blank-page time while still making the human review faster and clearer. This query needs a page where feedback items, segments, frequency, severity, quotes, and product area is not decoration; it controls a feedback synthesis, a structured analysis table with claims, evidence, gaps, and recommended next step, and feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.

Why the workflow matters

The page gives the user a copyable prompt plus the context pack and grader needed to decide whether the model answer is ready. The differentiator is especially important when a polished answer could hide missing proof around source notes, examples, constraints, and reviewer judgment.

External references

Google Search Central people-first content guidanceUsed as the search-quality yardstick because this page must solve a real user task and make source notes, examples, constraints, and reviewer judgment reviewable.
Google Search Central SEO Starter GuideUsed to keep titles, descriptions, links, and page structure focused on helping search engines and users understand a feedback synthesis.
OpenAI ChatGPT business overviewUsed for work-related prompt boundaries where AI output should support productivity while staying subject to human review.
NIST AI Risk Management FrameworkUsed as an external risk-management reference where a feedback synthesis needs human oversight, assumptions, and review controls.
FTC advertising and marketing guidanceUsed as the second product reference when a feedback synthesis affects market-facing claims, proof language, or customer communication.

Related ways people ask for this task

Main query covered: chatgpt prompts for product managers feedback synthesis

User intent: copy prompt workflow with template and review intent

Leave out popularity or ranking numbers until you can point to real search data after publishing.

Related ways people ask for this task

feedback synthesis chatgpt prompt for product managers
best chatgpt prompts for feedback synthesis
feedback synthesis prompt template for product managers
copyable feedback synthesis chatgpt prompt
feedback synthesis ai prompt with review checklist
chatgpt feedback synthesis workflow prompt

What to compare before using this prompt

Check whether ranking pages answer the task directly or only list broad prompts for product managers.
Compare whether competitors show a filled example for a feedback synthesis and not just a blank prompt.
Look for missing-source risks around source notes, examples, constraints, and reviewer judgment, especially claims that need manual checking.
Verify whether the SERP favors a role hub, a task page, a template page, or a tool-like prompt builder.
Confirm no volume, ranking, CPC, or difficulty number is used unless it comes from a live keyword tool export.

Check the answer before you reuse it

Who checks it

Give approval work to the person who can spot when theme frequency, segment contrast, quote evidence, and product implication has drifted from the user's source material.

Real-world case

a feedback synthesis scenario: a field-ready version should survive a messy paste where product managers provide feedback items, segments, frequency, severity, quotes, and product area, need a structured analysis table with claims, evidence, gaps, and recommended next step, and must keep theme frequency, segment contrast, quote evidence, and product implication visible while checking source notes, examples, constraints, and reviewer judgment. For product managers, synthesize feedback is reviewed inside a product decision workflow where evidence and tradeoffs need to stay visible, with feedback theme table with quote evidence as the concrete item on the desk.

Checks before sharing

Source review, synthesize feedback: the answer uses the supplied feedback items, segments, frequency, severity, quotes, and product area and does not fill missing facts with confident guesses.
Output shape, synthesize feedback: the result clearly becomes a feedback synthesis, not broad advice about the task.
Handoff clarity, synthesize feedback: the answer names missing inputs and the next human check for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.
Audience fit, synthesize feedback: the result works for a product team, stakeholder, customer researcher, or release owner, including channel, tone, length, and decision context.
Risk boundary, synthesize feedback: the final version respects Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

Compare with other results

Question to compare: chatgpt prompts for product managers feedback synthesis

Result feedback synthesis product managers check: open the top results and record whether they solve the task, not only a prompt phrase.
Example feedback synthesis product managers check: compare whether competing pages show a filled example for a feedback synthesis using realistic feedback items, segments, frequency, severity, quotes, and product area.
Evidence feedback synthesis product managers check: mark whether each page explains how to verify source notes, examples, constraints, and reviewer judgment and feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.
Differentiator feedback synthesis product managers check: compare the top results against this page promise: Search edge for feedback synthesis with product managers: show feedback theme table with quote evidence, a human review path for a feedback synthesis, and the task-specific reason the page deserves the query.
Failure feedback synthesis product managers check: mark whether competing pages show this failure mode or avoid it: Failure pattern for feedback synthesis with product managers: the feedback synthesis can sound polished while feedback synthesis can flatten contradictions into one tidy recommendation, so the page should make that miss easy to catch.
Freshness feedback synthesis product managers check: record whether competing pages say how source notes stay current. For product managers feedback synthesis, current source notes should come first; stale or partial inputs should trigger a fresh feedback theme table with quote evidence pass instead of another saved answer.
Page type feedback synthesis product managers check: confirm whether Google is rewarding a role hub, task page, tool, article, video, or forum thread for this query.
FAQ feedback synthesis product managers check: record People Also Ask questions that should become FAQ or section coverage before publishing changes.

Do not assume

Confirm the trust pages cite official Search Central guidance for helpful content and SEO basics.
Confirm source references support the safe-use and human-review framing.
Add or keep a role-specific external reference if product managers need policy, education, developer, hiring, sales, or marketing context beyond this prompt library.
External proof need: Outside proof for feedback synthesis with product managers: an independent resource must mention the feedback synthesis page visibly before feedback theme table with quote evidence becomes an authority claim.

Numbers to leave out unless verified

This page can prove local readiness, source coverage, and review depth. It cannot claim ranking, traffic, search volume, CPC, or difficulty until those numbers come from Search Console or another real search data source after publishing.

Weak prompt: too vague to trust

Help me synthesize feedback for my work.

It gives no source material, no stakeholder, no output shape, and no review lens, so ChatGPT can fill gaps with generic advice.

Stronger prompt: specific enough to review

Help product managers synthesize feedback by turning [source_material] into a feedback synthesis for [audience]. Keep the task focus on theme frequency, segment contrast, quote evidence, and product implication. Use this output shape: a structured analysis table with claims, evidence, gaps, and recommended next step. Do not add facts beyond the source. End with a review checklist for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence and source notes, examples, constraints, and reviewer judgment.

It names the task asset, required inputs, audience, format, evidence boundary, and human review step, so the answer is easier to adapt and check.

Rewrite case from vague request to usable prompt

Original need

A PM has 40 support tickets and 12 interview notes about reporting exports being confusing. The user needs help with synthesize feedback, but the real job is to turn a messy request into a feedback synthesis that a product team, stakeholder, customer researcher, or release owner can review without hidden assumptions.

Weak prompt

Write a good synthesize feedback from this: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.

This weak version includes a real situation but gives ChatGPT no output shape, audience rule, evidence boundary, or review owner. It can sound polished while missing theme frequency, segment contrast, quote evidence, and product implication, inventing details, or skipping feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.

Stronger prompt

Act as a careful assistant for Product Managers.
I need help with synthesize feedback. Use only this source material: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.
The usual source material for this task is feedback items, segments, frequency, severity, quotes, and product area.
The audience is [audience], and the output must work for a product team, stakeholder, customer researcher, or release owner.
Create a feedback synthesis in this shape: a structured analysis table with claims, evidence, gaps, and recommended next step.
Keep the task focus on theme frequency, segment contrast, quote evidence, and product implication.
Respect this editorial rule: The prompt must preserve evidence and uncertainty instead of forcing one tidy answer.
If context is missing, ask up to three clarifying questions before writing.
After the answer, include a review checklist for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, source notes, examples, constraints, and reviewer judgment, and this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

The stronger version gives ChatGPT a role, real input, audience, output shape, editorial boundary, and review lens. It also forces missing-context questions before creation and keeps source notes, examples, constraints, and reviewer judgment visible for human checking.

Sample input

A PM has 40 support tickets and 12 interview notes about reporting exports being confusing. User notes: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions. Audience: a product team, stakeholder, customer researcher, or release owner. Constraints: avoid unsupported claims, protect private details, and keep focus on theme frequency, segment contrast, quote evidence, and product implication.

Simulated output

A useful answer starts by restating the real situation, then provides a structured analysis table with claims, evidence, gaps, and recommended next step. It marks assumptions, shows which parts came from the user's notes, includes a concise next action, and ends with checks for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, source notes, examples, constraints, and reviewer judgment, and this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided. The output should already reflect the practical review target that matters here, so the final synthesis should show what is known, what is noisy, and what needs more research.

Human-edited final version

The human keeps the structure, removes any unsupported claim, adds missing facts from the real source, and saves the prompt as a reusable feedback synthesis prompt pattern with source notes, constraints, and review checklist. Before sharing with a product team, stakeholder, customer researcher, or release owner, the final pass checks tone, privacy, evidence, and whether theme frequency, segment contrast, quote evidence, and product implication is still the center of the answer. The pass is accepted only when the final synthesis should show what is known, what is noisy, and what needs more research.

Fit

Use when product managers have real source notes for synthesize feedback.
Use when the desired result is a feedback synthesis, not broad advice.
Use when a human can review feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence before the output reaches a product team, stakeholder, customer researcher, or release owner.

Not fit

Do not use when the model is expected to invent facts, numbers, credentials, or private details.
Do not use when source notes, examples, constraints, and reviewer judgment is unavailable and cannot be checked.
Do not use as final judgment for sensitive decisions covered by this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

Worked example: Synthesize feedback example from rough notes

Example input

A PM has 40 support tickets and 12 interview notes about reporting exports being confusing. Raw input: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.

Prompt use

Use the evidence-aware prompt to convert those notes into a feedback synthesis, then run the review prompt against this editorial rule: The prompt must preserve evidence and uncertainty instead of forcing one tidy answer.

Sample output shape

A useful answer would return a structured analysis table with claims, evidence, gaps, and recommended next step for a product team, stakeholder, customer researcher, or release owner, while making the source details and assumptions visible. It should preserve the real constraint in the input, keep theme frequency, segment contrast, quote evidence, and product implication at the center, and avoid adding facts that are not present. The final section should tell the user what still needs checking, especially source notes, examples, constraints, and reviewer judgment. The human pass is not decoration here: The final synthesis should show what is known, what is noisy, and what needs more research.

Review notes

Confirm the answer reflects this actual situation: A PM has 40 support tickets and 12 interview notes about reporting exports being confusing.
Compare the output against the raw user input: Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions.
Confirm the source material really supports source notes, examples, constraints, and reviewer judgment.
Check that the wording fits a product team, stakeholder, customer researcher, or release owner.
Confirm the answer handles theme frequency, segment contrast, quote evidence, and product implication instead of a neighboring task.
Remove details that violate this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

Prompt Workbench

beginner

Synthesize feedback Context Intake Prompt

Use this before synthesize feedback when the notes are rough and ChatGPT should ask clarifying questions first.

Act as a careful assistant for Product Managers.
Task: help me synthesize feedback. Target result: a feedback synthesis.
Source material I can provide: [source_material]. Typical source for this task is feedback items, segments, frequency, severity, quotes, and product area.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: theme frequency, segment contrast, quote evidence, and product implication.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as intake: ask the questions needed before writing, then wait for answers if the source material is missing.
Stop rule: Stop before creating the final asset if the audience, source material, or review owner is unclear.
Return a question list grouped by audience, source material, constraints, and review owner.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: The user should leave with a short context pack and a safe next prompt, not a finished answer.

[source_material]: The notes, facts, examples, or raw material behind synthesize feedback.Example: feedback items, segments, frequency, severity, quotes, and product area
[audience]: Who will read, use, approve, or act on the output.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The decision or work outcome the response should support.Example: make a feedback synthesis easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: The most important thing a human should check after the answer.Example: feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: theme frequency, segment contrast, quote evidence, and product implication

Expected output

Expect a question list grouped by audience, source material, constraints, and review owner that explicitly separates source-based content from assumptions and ends with a review pass for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.

Follow-up prompt

Now improve this working version into a feedback synthesis by tightening feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence, emphasizing theme frequency, segment contrast, quote evidence, and product implication, removing unsupported claims, and giving me one stronger version for a product team, stakeholder, customer researcher, or release owner.

Human review

Check whether the answer uses only provided context, handles source notes, examples, constraints, and reviewer judgment, fits a product team, stakeholder, customer researcher, or release owner, reflects theme frequency, segment contrast, quote evidence, and product implication, and respects this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.

Best for: Starting synthesize feedback when the source material still needs shape. Use when: Use before asking ChatGPT for synthesize feedback so the model has enough task-specific context.

advanced

Synthesize feedback Evidence-Aware Working Copy Prompt

Use this when the source material is ready and the answer needs to become a feedback synthesis.

Act as a careful assistant for Product Managers.
Task: help me synthesize feedback. Target result: a feedback synthesis.
Source material I can provide: [source_material]. Typical source for this task is feedback items, segments, frequency, severity, quotes, and product area.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: theme frequency, segment contrast, quote evidence, and product implication.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as the first usable version: use the supplied fields, label assumptions, and produce the main artifact.
Stop rule: Stop if the request asks you to invent facts, evidence, credentials, numbers, or private details.
Return a structured analysis table with claims, evidence, gaps, and recommended next step.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: The user should get a working version they can inspect against the supplied notes.

[source_material]: The notes, facts, examples, or raw material behind synthesize feedback.Example: feedback items, segments, frequency, severity, quotes, and product area
[audience]: Who will read, use, approve, or act on the output.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The decision or work outcome the response should support.Example: make a feedback synthesis easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: The most important thing a human should check after the answer.Example: feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: theme frequency, segment contrast, quote evidence, and product implication

Expected output

Expect a structured analysis table with claims, evidence, gaps, and recommended next step that explicitly separates source-based content from assumptions and ends with a review pass for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.

Follow-up prompt

Human review

Best for: Turning prepared context into a feedback synthesis. Use when: Use before asking ChatGPT for synthesize feedback so the model has enough task-specific context.

workflow

Synthesize feedback Repeatable Workflow Prompt

Use this when synthesize feedback repeats often enough to become feedback synthesis prompt pattern with source notes, constraints, and review checklist.

Act as a careful assistant for Product Managers.
Task: help me synthesize feedback. Target result: a feedback synthesis.
Source material I can provide: [source_material]. Typical source for this task is feedback items, segments, frequency, severity, quotes, and product area.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: theme frequency, segment contrast, quote evidence, and product implication.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as a repeatable workflow: separate one-time facts from fields that should change next time.
Stop rule: Stop if the reusable version would preserve private details or hide a human approval step.
Return a reusable step-by-step workflow with inputs, checks, and follow-up prompts.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: The user should get reusable fields, a run order, and a reject-if rule for the next use.

[source_material]: The notes, facts, examples, or raw material behind synthesize feedback.Example: feedback items, segments, frequency, severity, quotes, and product area
[audience]: Who will read, use, approve, or act on the output.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The decision or work outcome the response should support.Example: make a feedback synthesis easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: The most important thing a human should check after the answer.Example: feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: theme frequency, segment contrast, quote evidence, and product implication

Expected output

Expect a reusable step-by-step workflow with inputs, checks, and follow-up prompts that explicitly separates source-based content from assumptions and ends with a review pass for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.

Follow-up prompt

Human review

Best for: Creating a reusable process for repeated synthesize feedback work. Use when: Use when synthesize feedback repeats often enough to need a standard process.

review

Synthesize feedback Human Review Prompt

Use this after there is already working copy and the main need is feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.

Act as a careful assistant for Product Managers.
Task: help me synthesize feedback. Target result: a feedback synthesis.
Source material I can provide: [source_material]. Typical source for this task is feedback items, segments, frequency, severity, quotes, and product area.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: theme frequency, segment contrast, quote evidence, and product implication.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as a review of existing copy: score the answer, name the weak sections, and propose repairs.
Stop rule: Stop if the copy cannot be traced back to the supplied source material or the reviewer is not named.
Return a scored review table with issues, fixes, and what still needs human judgment.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: The user should get a decision about accept, repair, or reject before polishing the wording.

[source_material]: The notes, facts, examples, or raw material behind synthesize feedback.Example: feedback items, segments, frequency, severity, quotes, and product area
[audience]: Who will read, use, approve, or act on the output.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The decision or work outcome the response should support.Example: make a feedback synthesis easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: The most important thing a human should check after the answer.Example: feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: theme frequency, segment contrast, quote evidence, and product implication

Expected output

Expect a scored review table with issues, fixes, and what still needs human judgment that explicitly separates source-based content from assumptions and ends with a review pass for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.

Follow-up prompt

Human review

Best for: Finding weak spots in existing working copy. Use when: Use after product managers already have working copy and need to check feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.

format

Synthesize feedback Format Conversion Prompt

Use this when the substance is right but the output needs to fit a table, checklist, email, outline, or script.

Act as a careful assistant for Product Managers.
Task: help me synthesize feedback. Target result: a feedback synthesis.
Source material I can provide: [source_material]. Typical source for this task is feedback items, segments, frequency, severity, quotes, and product area.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: theme frequency, segment contrast, quote evidence, and product implication.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as format conversion: preserve the facts and change only the structure, order, or channel fit.
Stop rule: Stop if the requested format would require adding facts that were not in the original answer.
Return the same content reshaped without adding new facts.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: The user should get a reshaped version plus a note showing what stayed unchanged.

[source_material]: The notes, facts, examples, or raw material behind synthesize feedback.Example: feedback items, segments, frequency, severity, quotes, and product area
[audience]: Who will read, use, approve, or act on the output.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The decision or work outcome the response should support.Example: make a feedback synthesis easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: The most important thing a human should check after the answer.Example: feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: theme frequency, segment contrast, quote evidence, and product implication

Expected output

Expect the same content reshaped without adding new facts that explicitly separates source-based content from assumptions and ends with a review pass for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.

Follow-up prompt

Human review

Best for: Changing the output format without changing the facts. Use when: Use when the answer needs a precise structure before product managers can review it.

privacy

Synthesize feedback Privacy-Safe Prompt

Use this when the source material contains private, sensitive, or account-specific details.

Act as a careful assistant for Product Managers.
Task: help me synthesize feedback. Target result: a feedback synthesis.
Source material I can provide: [source_material]. Typical source for this task is feedback items, segments, frequency, severity, quotes, and product area.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: theme frequency, segment contrast, quote evidence, and product implication.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as a sanitizing pass: replace private details with role-safe descriptions before writing.
Stop rule: Stop if names, identifiers, account details, confidential strategy, or one-time records are still present.
Return a sanitized prompt-ready summary plus a list of removed details.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: The user should get a safe summary, removed-detail list, and a reusable version without sensitive data.

[source_material]: The notes, facts, examples, or raw material behind synthesize feedback.Example: feedback items, segments, frequency, severity, quotes, and product area
[audience]: Who will read, use, approve, or act on the output.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The decision or work outcome the response should support.Example: make a feedback synthesis easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: The most important thing a human should check after the answer.Example: feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: theme frequency, segment contrast, quote evidence, and product implication

Expected output

Expect a sanitized prompt-ready summary plus a list of removed details that explicitly separates source-based content from assumptions and ends with a review pass for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.

Follow-up prompt

Human review

Best for: Sanitizing context before asking ChatGPT for help. Use when: Use before adding sensitive context so private details stay out.

short

Synthesize feedback Fast Checklist Prompt

Use this for a quick pass when the user only needs the next few decisions for synthesize feedback.

Act as a careful assistant for Product Managers.
Task: help me synthesize feedback. Target result: a feedback synthesis.
Source material I can provide: [source_material]. Typical source for this task is feedback items, segments, frequency, severity, quotes, and product area.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: theme frequency, segment contrast, quote evidence, and product implication.
Goal: [goal]. Constraints: [constraints]. Do not add facts that are not in the source material.
Run mode: Run this as a fast decision pass: give only the next actions, the missing input, and the main risk.
Stop rule: Stop if the user needs a full artifact, a legal answer, a policy decision, or unsupported factual claims.
Return a concise checklist with the next action and the main risk.
Before the answer, ask up to 3 clarifying questions if the source material is too thin.
After the answer, include a human review section focused on feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence; verify source notes, examples, constraints, and reviewer judgment; and respect this boundary: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Check cue: The user should get a narrow next step they can complete before opening a longer prompt.

[source_material]: The notes, facts, examples, or raw material behind synthesize feedback.Example: feedback items, segments, frequency, severity, quotes, and product area
[audience]: Who will read, use, approve, or act on the output.Example: a product team, stakeholder, customer researcher, or release owner
[goal]: The decision or work outcome the response should support.Example: make a feedback synthesis easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: The most important thing a human should check after the answer.Example: feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: theme frequency, segment contrast, quote evidence, and product implication

Expected output

Expect a concise checklist with the next action and the main risk that explicitly separates source-based content from assumptions and ends with a review pass for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.

Follow-up prompt

Human review

Best for: Getting a quick decision checklist before spending more time. Use when: Use when time is short and the user needs the next action, not a full answer.

Variables

[source_material]: feedback items, segments, frequency, severity, quotes, and product area
[audience]: a product team, stakeholder, customer researcher, or release owner
[goal]: make a feedback synthesis easier to review, adapt, and use in a real product managers workflow
[constraints]: Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
[review_lens]: feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence
[task_focus]: theme frequency, segment contrast, quote evidence, and product implication

Quality Rubric

Output quality check: Can the user see when to use the prompt, when not to use it, what input to paste, and what result to expect?
Context: Does the prompt give enough feedback items, segments, frequency, severity, quotes, and product area to avoid guessing?
Specificity: Does the answer produce a feedback synthesis rather than broad advice?
Task focus: Does it handle theme frequency, segment contrast, quote evidence, and product implication instead of drifting into a neighboring workflow?
Reviewability: Can a human quickly check feedback synthesis checkpoint and source notes, examples, constraints, and reviewer judgment?
Fit: Does the wording match a product team, stakeholder, customer researcher, or release owner and the real channel?
Safety: Are private details, unsupported claims, and policy-sensitive assumptions controlled?

Common mistakes

Asking ChatGPT to synthesize feedback without giving feedback items, segments, frequency, severity, quotes, and product area.
Accepting polished wording before checking source notes, examples, constraints, and reviewer judgment.
Using the same prompt for every product manager task instead of changing the output shape and review lens.
Forgetting to name a product team, stakeholder, customer researcher, or release owner, which makes tone and detail level drift.
Ignoring the task-specific focus: theme frequency, segment contrast, quote evidence, and product implication.
Skipping the review pass for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.
Pasting private or sensitive details when a summarized version would work.

Risk Controls

Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided.
Ask ChatGPT to label assumptions and verification needs before using a feedback synthesis.
Do not paste private names, identifiers, account details, student records, customer records, or confidential strategy when a summarized version is enough.
Check that theme frequency, segment contrast, quote evidence, and product implication is supported by the source material and not invented.
Have a human review feedback synthesis checkpoint before sharing the output with a product team, stakeholder, customer researcher, or release owner.

FAQ

What is the best prompt for product managers to synthesize feedback?

Use a prompt that names feedback items, segments, frequency, severity, quotes, and product area, asks for a structured analysis table with claims, evidence, gaps, and recommended next step, and ends with a review pass for feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.

What should I paste into ChatGPT first?

Paste sanitized source notes, the intended audience, constraints, and the decision the output must support. For this task, the key input is feedback items, segments, frequency, severity, quotes, and product area.

How do I make the answer less generic?

Ask ChatGPT to use only the supplied material, show assumptions, and revise the answer against source notes, examples, constraints, and reviewer judgment and a product team, stakeholder, customer researcher, or release owner.

What should a human check before using the output?

Check facts, tone, privacy, unsupported claims, and the task-specific lens: feedback synthesis quality, theme frequency and segment contrast, and decision-ready evidence.

Next workflows

ChatGPT Prompts for Product ManagersReturn to the role guide to choose by situation, output, and reviewer.
Write PRDsUseful next step when this workflow needs a related product managers output or review pass.
Write user storiesUseful next step when this workflow needs a related product managers output or review pass.
Define acceptance criteriaUseful next step when this workflow needs a related product managers output or review pass.
Prioritize roadmapsUseful next step when this workflow needs a related product managers output or review pass.
Structure competitor analysisUseful next step when this workflow needs a related product managers output or review pass.

Synthesize Feedback: turn notes into feedback synthesis

Start with the note you actually have

Copy this after checking the notes

Check the answer before saving it

Pick accept, repair, or reject before reuse

Save the final answer, human edit, and variables

Set up the first run

Synthesize feedback Evidence-Aware Working Copy Prompt

Variable Builder

Copy this filled version

Run this page in four moves

Start from the real note, not a blank prompt

Check the answer against your note

Real use plan for treating the prompt like a work note

Before copying

After ChatGPT answers

Reject the answer if

Choose the next move

Build The Asset

Know when the answer is ready

Ready signal

First run action

Second pass before the answer becomes reusable

Source line

Reviewer voice

the rough note "Need themes, evidence quotes, affected segments, frequency, severity, contradictions, product areas, and recommended next questions" as the visible source line for a feedback synthesis

any confident claim about source notes, examples, constraints, and reviewer judgment that the pasted note does not prove

the missing audience, owner, or review detail needed before a product team, stakeholder, customer researcher, or release owner uses the answer

the first polished paragraph so it shows theme frequency, segment contrast, quote evidence, and product implication before tone improvements

Why this feels hand-edited

Run the margin pass

Task actions for the next useful move

Before you use the answer, make the call

Working case file: Synthesize Feedback working case for Product Managers

Rough note

Constraint to keep visible

What the user brought

What is still missing

Who accepts the answer

What gets saved

Before copying

Checks before sharing

Run this case first

Input triage before running ChatGPT

Missing context

Notes to save before reusing this prompt

Details copied from the user's case

Guesses that need a review line

Boundaries that decide readiness

Sensitive context to keep out

Items that should become blanks

Iteration loop: run the prompt as a working thread

Thread goal

Source pass

Clarify pass

Claim check

Saveable prompt

Prompt readiness check before you copy

Collect context first

Session handoff: finish the run without losing the thread

Collect working context

Work note: what the rough note changes

Original working note

Questions before reuse

Who checks it

Usable output

Prompt run from pasted notes

Pasted notes

Why this input is messy

First prompt move

Questions ChatGPT should ask

Usable answer shape

Human revision

Save or discard

Why this page is not interchangeable

Work moment

Why this page

Do first

Next best workflow

What to look for