Plan Customer Interviews: keep interview guide with assumption probes sourced

Start the customer interviews run from "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.", then decide whether the first answer is strong enough to become customer interviews prompt pattern with source notes, constraints, and review checklist.

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

First move: The first run should preserve the messy input, ask for missing proof, and keep assumption, question ladder, probing plan, and bias control as the organizing constraint the reviewer can challenge.
Keep after run: The reusable version should save the structure, not the private case details, so the next run still asks for customer interview guide quality, assumption and question ladder, and fairness and policy fit instead of copying hidden assumptions.
Wrong page signal: Wrong page signal: switch to ChatGPT Prompts for Product Managers if the user cannot supply research goal, participant segment, assumptions, questions, and follow-up plan, if the desired result is not a customer interview guide, or if assumption, question ladder, probing plan, and bias control 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 plan customer interviews run

Messy input: A rough customer interviews note comes in: "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." is the rough request. Before reusing customer interviews, make a customer interview guide useful by keeping assumption, question ladder, probing plan, and bias control, naming the checker, and preserving this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
Better answer should: A usable customer interviews handoff would return a customer interview guide formatted as clear sections, bullets, and a review checklist; separate supplied notes from assumptions, name the review owner, prepare interview guide with assumption probes, and make the human pass focused on customer interview guide quality, assumption and question ladder, and fairness and policy fit.
Human edit: product manager should revise plan customer interviews by keeping the structure that saved time, replace polished filler with source-backed lines inside a customer interview guide, 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 interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." and make sure The final guide should be fair, focused, and ready for researcher review.

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 ruleThe final reviewer should know customer interview guide quality, assumption and question ladder, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to research goal, participant segment, assumptions, questions, and follow-up plan. must know what to reject before the answer is reused.

Real note: Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format. Examples for plan customer interviews help only when they keep the source note visible while shaping interview guide with assumption probes. A careful pass should keep the user's limit visible. In plan customer interviews, the supplied note becomes the base for a customer interview guide. A usable plan customer interviews input includes what is known, what is uncertain, and what the reviewer must verify.
What will change: Choose the recommended prompt only after the handoff owner and output shape are clear enough for a product team, stakeholder, customer researcher, or release owner.
Human check: Source review, plan customer interviews: the answer uses the supplied research goal, participant segment, assumptions, questions, and follow-up plan 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 Plan Customer Interviews
Who checks it: The final reviewer should know customer interview guide quality, assumption and question ladder, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to research goal, participant segment, assumptions, questions, and follow-up plan.

Paste source notes:
Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format. Examples for plan customer interviews help only when they keep the source note visible while shaping interview guide with assumption probes. A careful pass should keep the user's limit visible. In plan customer interviews, the supplied note becomes the base for a customer interview guide. A usable plan customer interviews input includes what is known, what is uncertain, and what the reviewer must verify.

Must keep:
Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.
research goal, participant segment, assumptions, questions, and follow-up plan
assumption, question ladder, probing plan, and bias control

Do not allow:
Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Reject it if the final shape cannot be used by a product team, stakeholder, customer researcher, or release owner.

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: The final reviewer should know customer interview guide quality, assumption and question ladder, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to research goal, participant segment, assumptions, questions, and follow-up plan. must know what to reject before the answer is reused.

Run prompt:
Act as a careful assistant for Product Managers.
Task: help me plan customer interviews. Target result: a customer interview guide.
Source material I can provide: [source_material]. Typical source for this task is research goal, participant segment, assumptions, questions, and follow-up plan.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: assumption, question ladder, probing plan, and bias control.
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 customer interview guide formatted as clear sections, bullets, and a review checklist.
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 customer interview guide quality, assumption and question ladder, and fairness and policy fit; verify true experience, measurable proof, and target role fit; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
Check cue: The user should get a working version they can inspect against the supplied notes.

Stop rule: Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Record to keep: Store the reusable version with the original note, the prompt variables that changed the answer, the section that still needs customer interview guide quality, assumption and question ladder, and fairness and policy fit, and the final reason the accepted version can become customer interviews 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, plan customer interviews: the answer uses the supplied research goal, participant segment, assumptions, questions, and follow-up plan and does not fill missing facts with confident guesses. Output shape, plan customer interviews: the result clearly becomes a customer interview guide, not broad advice about the task.
Reject if: Evidence issue, plan customer interviews: the answer invents or overstates true experience, measurable proof, and target role fit. Task drift, plan customer interviews: it ignores assumption, question ladder, probing plan, and bias control and moves into a neighboring workflow.
Keep after run: Store the reusable version with the original note, the prompt variables that changed the answer, the section that still needs customer interview guide quality, assumption and question ladder, and fairness and policy fit, and the final reason the accepted version can become customer interviews 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 plan customer interviews answer, the product manager should choose Accept, Repair, or Reject before saving anything as customer interviews prompt pattern with source notes, constraints, and review checklist. The decision must compare "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." with a customer interview guide formatted as clear sections, bullets, and a review checklist, assumption, question ladder, probing plan, and bias control, and true experience, measurable proof, and target role fit.

Choose when: Choose Repair when the answer has a useful shape but loses one of the required pieces: assumption, question ladder, probing plan, and bias control, true experience, measurable proof, and target role fit, the reviewer role, the source note, or the reusable fields needed for customer interviews 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 customer interview guide in a customer interview guide formatted as clear sections, bullets, and a review checklist without inventing details.
Keep after run: Keep the weak answer beside the repair note, mark which line failed customer interview guide quality, assumption and question ladder, and fairness and policy fit, and save the corrected line only after it can be traced back to "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.".

Answer choice prompt

Repair this plan customer interviews answer instead of accepting it. Source note: "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." Weak answer: [paste_chatgpt_output_here]. Preserve any useful structure, but fix the parts that hide assumption, question ladder, probing plan, and bias control, turn true experience, measurable proof, and target role fit into unsupported certainty, or skip the reviewer for customer interview guide quality, assumption and question ladder, and fairness and policy fit. Return a repaired a customer interview guide formatted as clear sections, bullets, and a review checklist, a list of changed lines, and one remaining question before this can become customer interviews prompt pattern with source notes, constraints, and review checklist.

Do not save a reusable customer interviews prompt pattern with source notes, constraints, and review checklist until one option has a written decision. The saved version must keep "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." as the example, turn private or one-time details into variables, and keep the risk check "keep the wording fair, job-related, and reviewed by the appropriate human" 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 Plan Customer Interviews before it is saved, shared, or reused.
Reuse rule: Reuse customer interviews only after private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a customer interview guide, and the review rule for assumption, question ladder, probing plan, and bias control still appears in the reusable prompt. Approval for product managers customer interviews belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the interview guide with assumption probes review standard visible.
Saved: 0/3 checks

Saved version preview

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

Save only after review:
- Source review, plan customer interviews: the answer uses the supplied research goal, participant segment, assumptions, questions, and follow-up plan and does not fill missing facts with confident guesses.
- Store the reusable version with the original note, the prompt variables that changed the answer, the section that still needs customer interview guide quality, assumption and question ladder, and fairness and policy fit, and the final reason the accepted version can become customer interviews 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 customer interview guide quality, assumption and question ladder, and fairness and policy fit, 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 customer interview guide quality, assumption and question ladder, and fairness and policy fit, and save the corrected line only after it can be traced back to "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.".

Source note used:
Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format. Examples for plan customer interviews help only when they keep the source note visible while shaping interview guide with assumption probes. A careful pass should keep the user's limit visible. In plan customer interviews, the supplied note becomes the base for a customer interview guide. A usable plan customer interviews input includes what is known, what is uncertain, and what the reviewer must verify.

Final answer:
A usable customer interviews handoff would return a customer interview guide formatted as clear sections, bullets, and a review checklist; separate supplied notes from assumptions, name the review owner, prepare interview guide with assumption probes, and make the human pass focused on customer interview guide quality, assumption and question ladder, and fairness and policy fit.

Human edit:
product manager should revise plan customer interviews by keeping the structure that saved time, replace polished filler with source-backed lines inside a customer interview guide, 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 interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." and make sure The final guide should be fair, focused, and ready for researcher review.

Reusable variables:
[source_material]: research goal, participant segment, assumptions, questions, and follow-up plan
[audience]: a product team, stakeholder, customer researcher, or release owner
[goal]: make a customer interview guide easier to review, adapt, and use in a real product managers workflow
[constraints]: keep the wording fair, job-related, and reviewed by the appropriate human

Reuse rule: Reuse customer interviews only after private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a customer interview guide, and the review rule for assumption, question ladder, probing plan, and bias control still appears in the reusable prompt. Approval for product managers customer interviews belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the interview guide with assumption probes review standard visible.
Stop if: Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.

First run setup

Set up the first run

Edit notes

First move: Choose the recommended prompt only after the handoff owner and output shape are clear enough for a product team, stakeholder, customer researcher, or release owner.
Bring first: Bring the rough case note: Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.
Switch if: The user cannot provide research goal, participant segment, assumptions, questions, and follow-up plan and would need ChatGPT to invent the important facts.
Keep after run: Store the reusable version with the original note, the prompt variables that changed the answer, the section that still needs customer interview guide quality, assumption and question ladder, and fairness and policy fit, and the final reason the accepted version can become customer interviews 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 customer interviews prompt pattern with source notes, constraints, and review checklist, one copied run prompt, and a reviewer check that keeps customer interview guide quality, assumption and question ladder, and fairness and policy fit and true experience, measurable proof, and target role fit visible before sharing anything. Start with: Choose the recommended prompt only after the handoff owner and output shape are clear enough for a product team, stakeholder, customer researcher, or release owner.

Go to runner

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

Who checks it

The final reviewer should know customer interview guide quality, assumption and question ladder, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to research goal, participant segment, assumptions, questions, and follow-up plan.

Check before using

Inspect research goal, participant segment, assumptions, questions, and follow-up plan, the case note "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.", and any open proof around true experience, measurable proof, and target role fit; the answer should keep supplied notes, assumptions, and needs-checking points separate.

Compare later

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

Visitor question: I have research goal, participant segment, assumptions, questions, and follow-up plan and need a customer interview guide for a product team, stakeholder, customer researcher, or release owner; can this plan customer interviews page turn "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." into a customer interview guide formatted as clear sections, bullets, and a review checklist without hiding assumption, question ladder, probing plan, and bias control?
5-minute outcome: Within five minutes, the user should have a first customer interviews prompt pattern with source notes, constraints, and review checklist, one copied run prompt, and a reviewer check that keeps customer interview guide quality, assumption and question ladder, and fairness and policy fit and true experience, measurable proof, and target role fit visible before sharing anything.
Wrong page signal: This is the wrong page if the work is closer to ChatGPT Prompts for Product Managers, if assumption, question ladder, probing plan, and bias control is not the controlling decision, or if the user only wants broad ideas instead of a reviewable a customer interview guide.
Why this page fits: Save the rough note, the accepted prompt variables, the customer interviews query language, and the section that proves this a customer interview guide is not interchangeable with ChatGPT Prompts for Product Managers.
Reuse decision: Reuse the output only when the answer traces back to research goal, participant segment, assumptions, questions, and follow-up plan, respects the risk check "keep the wording fair, job-related, and reviewed by the appropriate human", and gives a product team, stakeholder, customer researcher, or release owner a clear accept, repair, or reject path.

Wrong page? Write user storiesUseful next step when this workflow needs a related product managers output or review pass.

Working brief

Check the job before copying

The task belongs here when the next useful action is a reviewable a customer interview guide formatted as clear sections, bullets, and a review checklist; if the user only needs ideas, a different prompt path is safer.

Use this when: This page fits the handoff point where a product team, stakeholder, customer researcher, or release owner needs a customer interview guide formatted as clear sections, bullets, and a review checklist, not a longer explanation of plan customer interviews.
Paste this kind of note: Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format. Examples for plan customer interviews help only when they keep the source note visible while shaping interview guide with assumption probes. A careful pass should keep the user's limit visible. In plan customer interviews, the supplied note becomes the base for a customer interview guide. A usable plan customer interviews input includes what is known, what is uncertain, and what the reviewer must verify.
Expected result: A usable customer interviews handoff would return a customer interview guide formatted as clear sections, bullets, and a review checklist; separate supplied notes from assumptions, name the review owner, prepare interview guide with assumption probes, and make the human pass focused on customer interview guide quality, assumption and question ladder, and fairness and policy fit.
Stop before reuse if: Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Human check: Source review, plan customer interviews: the answer uses the supplied research goal, participant segment, assumptions, questions, and follow-up plan and does not fill missing facts with confident guesses.

Bring first: Bring the rough case note: Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.
Build when: Use this when the notes are ready and the next useful output is a customer interview guide formatted as clear sections, bullets, and a review checklist, 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 customer interview guide.
Users who want ChatGPT to ask clarifying questions before it commits to a customer interview guide formatted as clear sections, bullets, and a review checklist.
Teams that repeat plan customer interviews 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?Write user storiesUseful next step when this workflow needs a related product managers output or review pass.

Editorial method Safe use About this library

Plan customer interviews Evidence-Aware Working Copy Prompt

Use this when the source material is ready and the answer needs to become a customer interview guide.

Real input: Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format. Examples for plan customer interviews help only when they keep the source note visible while shaping interview guide with assumption probes. A careful pass should keep the user's limit visible. In plan customer interviews, the supplied note becomes the base for a customer interview guide. A usable plan customer interviews input includes what is known, what is uncertain, and what the reviewer must verify.
Target output: A usable customer interviews handoff would return a customer interview guide formatted as clear sections, bullets, and a review checklist; separate supplied notes from assumptions, name the review owner, prepare interview guide with assumption probes, and make the human pass focused on customer interview guide quality, assumption and question ladder, and fairness and policy fit.
Reject if: Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.

Scenario: A PM is planning interviews with operations managers about how they hand off weekly status reports. The plan customer interviews work happens inside a product decision workflow where evidence and tradeoffs need to stay visible. For product managers customer interviews, current source notes should come first; stale or partial inputs should trigger a fresh interview guide with assumption probes pass instead of another saved answer. Approval for product managers customer interviews belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the interview guide with assumption probes review standard visible. For plan customer interviews, the page should make this situation feel familiar enough that the user can swap in their own notes without guessing what each variable means.
Bring: Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format. research goal, participant segment, assumptions, questions, and follow-up plan assumption, question ladder, probing plan, and bias control
Check: The final guide should be fair, focused, and ready for researcher review. Approval for product managers customer interviews belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the interview guide with assumption probes review standard visible. Before handing off plan customer interviews, before reuse, the human should tighten tone, verify facts, and remove any claim the source material does not support, with a short record of what changed before reuse and where For product managers customer interviews, current source notes should come first; stale or partial inputs should trigger a fresh interview guide with assumption probes pass instead of another saved answer.

Variable Builder

[source_material]The notes, facts, examples, or raw material behind plan customer interviews.[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 plan customer interviews. Target result: a customer interview guide.
Source material I can provide: [source_material]. Typical source for this task is research goal, participant segment, assumptions, questions, and follow-up plan.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: assumption, question ladder, probing plan, and bias control.
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 customer interview guide formatted as clear sections, bullets, and a review checklist.
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 customer interview guide quality, assumption and question ladder, and fairness and policy fit; verify true experience, measurable proof, and target role fit; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
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 plan customer interviews. Target result: a customer interview guide.
Source material I can provide: [source_material]. Typical source for this task is research goal, participant segment, assumptions, questions, and follow-up plan.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: assumption, question ladder, probing plan, and bias control.
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 customer interview guide formatted as clear sections, bullets, and a review checklist.
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 customer interview guide quality, assumption and question ladder, and fairness and policy fit; verify true experience, measurable proof, and target role fit; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
Check cue: The user should get a working version they can inspect against the supplied notes.

Expected output: Expect a customer interview guide formatted as clear sections, bullets, and a review checklist that explicitly separates source-based content from assumptions and ends with a review pass for customer interview guide quality, assumption and question ladder, and fairness and policy fit.

First run

Run this page in four moves

Concrete outputA usable customer interviews handoff would return a customer interview guide formatted as clear sections, bullets, and a review checklist; separate supplied notes from assumptions, name the review owner, prepare interview guide with assumption probes, and make the human pass focused on customer interview guide quality, assumption and question ladder, and fairness and policy fit.

Keep after runStore the reusable version with the original note, the prompt variables that changed the answer, the section that still needs customer interview guide quality, assumption and question ladder, and fairness and policy fit, and the final reason the accepted version can become customer interviews prompt pattern with source notes, constraints, and review checklist.

Reject before reuseSend it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.

PrepareCollect ContextUse this when the product manager source notes are still uneven or missing the detail that would shape a customer interview guide.CopyBuild The AssetUse this when the notes are ready and the next useful output is a customer interview guide formatted as clear sections, bullets, and a review checklist, not more brainstorming.GradeReview The AnswerUse this when ChatGPT has already answered and the risk is accepting fluent wording before customer interview guide quality, assumption and question ladder, and fairness and policy fit 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 interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format. Examples for plan customer interviews help only when they keep the source note visible while shaping interview guide with assumption probes. A careful pass should keep the user's limit visible. In plan customer interviews, the supplied note becomes the base for a customer interview guide. A usable plan customer interviews input includes what is known, what is uncertain, and what the reviewer must verify.
First move: Choose the recommended prompt only after the handoff owner and output shape are clear enough for a product team, stakeholder, customer researcher, or release owner.
Who checks it: The final reviewer should know customer interview guide quality, assumption and question ladder, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to research goal, participant segment, assumptions, questions, and follow-up plan.

Stop rule: Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Keep after run: Store the reusable version with the original note, the prompt variables that changed the answer, the section that still needs customer interview guide quality, assumption and question ladder, and fairness and policy fit, and the final reason the accepted version can become customer interviews prompt pattern with source notes, constraints, and review checklist.

PrepareCollect ContextBring the rough case note: Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.CopyBuild The AssetExpect a customer interview guide formatted as clear sections, bullets, and a review checklist that explicitly separates source-based content from assumptions and ends with a review pass for customer interview guide quality, assumption and question ladder, and fairness and policy fit.GradeReview The AnswerTreat the model answer as working copy to test and tag the parts where true experience, measurable proof, and target role fit changes the decision.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 assumption, question ladder, probing plan, and bias control.
Human check: Source review, plan customer interviews: the answer uses the supplied research goal, participant segment, assumptions, questions, and follow-up plan 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 customer interviews

Open reference checks

Paste into ChatGPT: Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format. Examples for plan customer interviews help only when they keep the source note visible while shaping interview guide with assumption probes. A careful pass should keep the user's limit visible. In plan customer interviews, the supplied note becomes the base for a customer interview guide. A usable plan customer interviews input includes what is known, what is uncertain, and what the reviewer must verify.
Question to compare: chatgpt prompts for product managers customer interviewsResult customer interviews 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 customer interview guide needs human oversight, assumptions, and review controls.
Who checks it: The final reviewer should know customer interview guide quality, assumption and question ladder, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to research goal, participant segment, assumptions, questions, and follow-up plan.Inspect research goal, participant segment, assumptions, questions, and follow-up plan, the case note "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.", and any open proof around true experience, measurable proof, and target role fit; the answer should keep supplied notes, assumptions, and needs-checking points separate.

Use this page to move from a rough note to a customer interview guide while keeping source-backed details separate from open questions. The example case shows how rough notes become a reviewable asset while keeping risky claims out of the polished section. customer interviews weak spot: interview guides can lead the participant instead of testing assumptions neutrally. The reject-if rules matter most when the model fills missing evidence with confident wording. Prompts should surface assumptions and evidence gaps instead of pretending strategy is decided. If the source material changes, rerun the prompt instead of recycling the old answer.

Real use plan for treating the prompt like a work note

0/12 checked

It works because the prompt run does not end at a fluent answer. The user compares the output with "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.", repairs weak sections, and keeps assumption, question ladder, probing plan, and bias control visible before handoff.

Before copying

Start from the actual handoff: Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.Add the recipient, channel, and approval owner before asking for a finished a customer interview guide.Include the rule that decides whether the answer is safe to use: The prompt must prioritize past behavior and neutral wording.Tell the model that assumption, question ladder, probing plan, and bias control is the center of the answer, then request a customer interview guide formatted as clear sections, bullets, and a review checklist.

After ChatGPT answers

Treat the model answer as working copy to test and tag the parts where true experience, measurable proof, and target role fit changes the decision.Compare each section with the notes before editing for customer interview guide quality, assumption and question ladder, and fairness and policy fit.Use the next prompt to repair one clear gap around assumption, question ladder, probing plan, and bias control.Keep the reusable version focused on research goal, participant segment, assumptions, questions, and follow-up plan, customer interview guide quality, assumption and question ladder, and fairness and policy fit, and the approval step.

Reject the answer if

Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.Reject it if the final shape cannot be used by a product team, stakeholder, customer researcher, or release owner.Reject it if the answer treats keep the wording fair, job-related, and reviewed by the appropriate human as optional cleanup.Reject it when the final pass would depend on guessing what the user meant.

Choose the next move

Start by turning the rough request into named fields before asking for a customer interview guide.

Build The Asset

Use this when the notes are ready and the next useful output is a customer interview guide formatted as clear sections, bullets, and a review checklist, not more brainstorming.

Open section

Do now: Copy the recommended prompt, replace the variables, and ask for a customer interview guide with assumptions separated from source-backed details.
Bring first: Bring the task focus: assumption, question ladder, probing plan, and bias control. Add the channel, deadline, and any required sections.
Stop if: Stop if the first answer gives broad advice instead of a concrete a customer interview guide.
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

Start from the actual handoff: Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.
Add the recipient, channel, and approval owner before asking for a finished a customer interview guide.
Include the rule that decides whether the answer is safe to use: The prompt must prioritize past behavior and neutral wording.

Accept only if

Treat the model answer as working copy to test and tag the parts where true experience, measurable proof, and target role fit changes the decision.
Compare each section with the notes before editing for customer interview guide quality, assumption and question ladder, and fairness and policy fit.
Use the next prompt to repair one clear gap around assumption, question ladder, probing plan, and bias control.

Reject when

Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.

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

The task is complete when the answer turns "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." into a customer interview guide formatted as clear sections, bullets, and a review checklist, keeps assumption, question ladder, probing plan, and bias control visible, and gives the owner sending this to a product team, stakeholder, customer researcher, or release owner a clear accept, repair, or reject choice before a product team, stakeholder, customer researcher, or release owner sees it.

First run action

Begin with the supplied source research goal, participant segment, assumptions, questions, and follow-up plan, the intended a customer interview guide, the audience, the stop rule "keep the wording fair, job-related, and reviewed by the appropriate human", and the proof needed for true experience, measurable proof, and target role fit.

Keep after run: Store the reusable version with the original note, the prompt variables that changed the answer, the section that still needs customer interview guide quality, assumption and question ladder, and fairness and policy fit, and the final reason the accepted version can become customer interviews prompt pattern with source notes, constraints, and review checklist.
Use or revise: the owner sending this to a product team, stakeholder, customer researcher, or release owner should approve the output only if it can be traced back to research goal, participant segment, assumptions, questions, and follow-up plan, shows what is assumed, and does not turn true experience, measurable proof, and target role fit into a confident claim without review.
What makes this page different: Compared with broad role pages, this route wins by tying the query "chatgpt prompts for product managers customer interviews" 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 customer interviews query because plan customer interviews changes the source material, reviewer, output shape, and failure mode; sending the user to a nearby product manager page would hide assumption, question ladder, probing plan, and bias control and weaken the final a customer interview guide.

Editor margin

Second pass before the answer becomes reusable

Source line

Editor margin source for plan customer interviews: "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." It names the practical limit the reviewer has to see before approving the result.

Reviewer voice

a second-pass owner protecting true experience, measurable proof, and target role fit reads the first ChatGPT answer beside the rough note and decides what survives. The page should feel handled by a human because the margin note says what to keep, what to cut, what to ask, and what to rewrite before reuse. The check belongs before the prompt is saved as customer interviews prompt pattern with source notes, constraints, and review checklist.

Keep

the rough note "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format" as the visible source line for a customer interview guide

Keep this because the rough note is the only part a product manager can compare against the answer when a customer interview guide formatted as clear sections, bullets, and a review checklist starts to sound finished.

The accepted answer should repeat or clearly map back to "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." before it adds structure.

Cut

any confident claim about true experience, measurable proof, and target role fit that the pasted note does not prove

Cut it because the proof around true experience, measurable proof, and target role fit 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 customer interview guide 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 assumption, question ladder, probing plan, and bias control before tone improvements

Rewrite the opening because this task is about assumption, question ladder, probing plan, and bias control, not a general plan customer interviews answer that could fit any role page.

A reviewer should see assumption, question ladder, probing plan, and bias control in the first accepted section and again in the saved reuse rule.

Why this feels hand-edited

a second-pass owner protecting true experience, measurable proof, and target role fit leaves this margin pass because the page has to protect a real source note, not only offer another prompt. For product managers working on plan customer interviews, the human-feeling part is the specific tradeoff: keep "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.", cut unsupported certainty, ask for the missing owner, and rewrite the answer around assumption, question ladder, probing plan, and bias control. 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 interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." Output being reviewed: [paste ChatGPT answer]. Mark four decisions: Keep the source-backed detail that should survive, Cut any unsupported claim about true experience, measurable proof, and target role fit, Ask the missing question that blocks a product team, stakeholder, customer researcher, or release owner from using the result, and Rewrite the section so assumption, question ladder, probing plan, and bias control stays visible before polish. End with one accept, repair, or reject decision and a reuse rule for customer interviews prompt pattern with source notes, constraints, and review checklist.

Task actions for the next useful move

Choose the recommended prompt only after the handoff owner and output shape are clear enough for a product team, stakeholder, customer researcher, or release owner.

CollectCollect ContextBring the rough case note: Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.CopyBuild The AssetExpect a customer interview guide formatted as clear sections, bullets, and a review checklist that explicitly separates source-based content from assumptions and ends with a review pass for customer interview guide quality, assumption and question ladder, and fairness and policy fit.CheckReview The AnswerTreat the model answer as working copy to test and tag the parts where true experience, measurable proof, and target role fit changes the decision.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 research goal, participant segment, assumptions, questions, and follow-up plan and would need ChatGPT to invent the important facts.

Stay hereThis page fits the handoff point where a product team, stakeholder, customer researcher, or release owner needs a customer interview guide formatted as clear sections, bullets, and a review checklist, not a longer explanation of plan customer interviews. First move: Choose the recommended prompt only after the handoff owner and output shape are clear enough for a product team, stakeholder, customer researcher, or release owner.

Switch ifWrite user storiesUseful next step when this workflow needs a related product managers output or review pass.

Stop ifThe user cannot provide research goal, participant segment, assumptions, questions, and follow-up plan and would need ChatGPT to invent the important facts. The desired result is not a customer interview guide or cannot be shaped as a customer interview guide formatted as clear sections, bullets, and a review checklist.

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: Treat the teammate accountable for customer interview guide quality, assumption and question ladder, and fairness and policy fit as the gate for this a customer interview guide; the answer should not move forward until they can trace it to the pasted notes.
Check before using: Inspect research goal, participant segment, assumptions, questions, and follow-up plan, the case note "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.", and any open proof around true experience, measurable proof, and target role fit; the answer should keep supplied notes, assumptions, and needs-checking points separate.
What this changes: The checkpoint makes the page do real work: it asks whether the answer can survive customer interview guide quality, assumption and question ladder, and fairness and policy fit while still reflecting "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." and the actual handoff to a product team, stakeholder, customer researcher, or release owner.
Do next: The final guide should be fair, focused, and ready for researcher review. Then save only the repeatable fields, not the one-time case details, so the next run still asks for customer interview guide quality, assumption and question ladder, and fairness and policy fit.
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 customer interviews" and record where it came from.

Working case file: Plan Customer Interviews working case for Product Managers

The page should help the user slow down long enough to name the proof, owner, and stop rule. The user has enough material to start, but not enough to trust a smooth answer unless the prompt keeps research goal, participant segment, assumptions, questions, and follow-up plan, a customer interview guide formatted as clear sections, bullets, and a review checklist, and the owner sending the result to a product team, stakeholder, customer researcher, or release owner in the same run.

Rough note

A PM is planning interviews with operations managers about how they hand off weekly status reports. The rough note says: "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." The desired result is a customer interview guide for a product team, stakeholder, customer researcher, or release owner.

Constraint to keep visible

The run is not ready until the owner sending the result to a product team, stakeholder, customer researcher, or release owner can compare the answer with the source note. Carry this rule into every section: keep the wording fair, job-related, and reviewed by the appropriate human.

What the user brought

The supplied case is "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.", so the answer should begin from the user's actual wording and not from broad plan customer interviews advice.

The finished a customer interview guide should point back to research goal, participant segment, assumptions, questions, and follow-up plan and show how assumption, question ladder, probing plan, and bias control changed the answer.

What is still missing

The model should ask for audience, channel, approval owner, and any proof needed for true experience, measurable proof, and target role fit 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 owner sending the result to a product team, stakeholder, customer researcher, or release owner should inspect customer interview guide quality, assumption and question ladder, and fairness and policy fit, 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 assumption, question ladder, probing plan, and bias control.

One-time details should be removed only after the accepted answer proves that a customer interview guide formatted as clear sections, bullets, and a review checklist works for this case.

Before copying

Can the user point to the exact research goal, participant segment, assumptions, questions, and follow-up plan ChatGPT is allowed to use?
Is assumption, question ladder, probing plan, and bias control visible before the prompt asks for a customer interview guide?
Has the user named the reviewer who checks customer interview guide quality, assumption and question ladder, and fairness and policy fit?
Is there a stop rule for unsupported claims about true experience, measurable proof, and target role fit?

Checks before sharing

Compare the first answer with "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." and mark any section that invents context.
Check whether the output is shaped as a customer interview guide formatted as clear sections, bullets, and a review checklist, 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 customer interviews 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 interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." Build a customer interview guide as a customer interview guide formatted as clear sections, bullets, and a review checklist. Keep assumption, question ladder, probing plan, and bias control visible, separate supplied facts from assumptions, ask for missing proof around true experience, measurable proof, and target role fit, name the owner sending the result to a product team, stakeholder, customer researcher, or release owner as the checker, and stop before using any claim that the source notes do not support.

The final move is to keep the structure that saves time, then remove one-time detail before reuse. 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 plan customer interviews run before a product team, stakeholder, customer researcher, or release owner can use it?

Selected issue

Missing context

Build context

Symptom: Plan Customer Interviews starts from a rough note like "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." 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 customer interview guide decide?
Do next: Start by rewriting the rough note into named fields before asking for a customer interview guide formatted as clear sections, bullets, and a review checklist, then confirm the reviewer can inspect each field.
Prompt move: Before writing, ask me up to four questions needed to produce a customer interview guide formatted as clear sections, bullets, and a review checklist; do not fill gaps with assumptions.
Stop if: Stop if the answer sounds polished but still cannot show the source notes behind assumption, question ladder, probing plan, and bias control.
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 interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." before running plan customer interviews 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 teammate checking customer interview guide quality, assumption and question ladder, and fairness and policy fit checks before a product team, stakeholder, customer researcher, or release owner sees interview guide with assumption probes. For product managers customer interviews, current source notes should come first; stale or partial inputs should trigger a fresh interview guide with assumption probes pass instead of another saved answer.

Facts the prompt can safely use

Capture: Capture the concrete case first: A PM is planning interviews with operations managers about how they hand off weekly status reports. The note says "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." and the requested asset is interview guide with assumption probes. For product managers customer interviews, current source notes should come first; stale or partial inputs should trigger a fresh interview guide with assumption probes pass instead of another saved answer.
Keep: Keep the facts that directly affect a customer interview guide formatted as clear sections, bullets, and a review checklist, especially the audience, task focus, channel, and any details already present in research goal, participant segment, assumptions, questions, and follow-up plan.
Verify: Verify that every useful line in the answer can point back to the rough note or to research goal, participant segment, assumptions, questions, and follow-up plan.
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 teammate checking customer interview guide quality, assumption and question ladder, and fairness and policy fit checks whether the answer still reflects customer interview guide quality, assumption and question ladder, and fairness and policy fit after the first pass.
If skipped: If this row is skipped, a customer interview guide can sound specific while drifting into generic plan customer interviews advice.

Unknowns the model must not hide

Capture: List what the user did not provide but the answer may need: missing audience detail, missing proof around true experience, measurable proof, and target role fit, 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 teammate checking customer interview guide quality, assumption and question ladder, and fairness and policy fit 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 assumption, question ladder, probing plan, and bias control.

Rules the answer must obey

Capture: Record the rule from this case: The prompt must prioritize past behavior and neutral wording. Also include keep the wording fair, job-related, and reviewed by the appropriate human and this field friction before the model writes: interview guides can lead the participant instead of testing assumptions neutrally. Failure pattern for customer interviews with product managers: the customer interview guide can sound polished while interview guides can lead the participant instead of testing assumptions neutrally, so the page should make that miss easy to catch.
Keep: Keep the constraint near the requested format so it governs the whole a customer interview guide formatted as clear sections, bullets, and a review checklist, 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 teammate checking customer interview guide quality, assumption and question ladder, and fairness and policy fit 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.

Details to summarize before reuse

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 teammate checking customer interview guide quality, assumption and question ladder, and fairness and policy fit confirms that the final a customer interview guide 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.

Reusable fields for the next run

Capture: Name the fields that should change next time: source notes, audience, output format, proof needed for true experience, measurable proof, and target role fit, reviewer, and stop rule.
Keep: Keep assumption, question ladder, probing plan, and bias control, customer interview guide quality, assumption and question ladder, and fairness and policy fit, and interview guide with assumption probes as required fields so the saved prompt does not collapse into a generic role prompt. Approval for product managers customer interviews belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the interview guide with assumption probes 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 teammate checking customer interview guide quality, assumption and question ladder, and fairness and policy fit 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 customer interviews 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 assumption, question ladder, probing plan, and bias control, and the place where interview guides can lead the participant instead of testing assumptions neutrally. Approval for product managers customer interviews belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the interview guide with assumption probes review standard visible. Outside proof for customer interviews with product managers: an independent resource must mention the customer interview guide page visibly before interview guide with assumption probes becomes an authority claim.

Iteration loop: run the prompt as a working thread

Plan Customer Interviews should stay unfinished until the missing proof and reviewer check are complete. Start from the rough note "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.", then ask ChatGPT to write, question, challenge, and hand off interview guide with assumption probes without hiding true experience, measurable proof, and target role fit. For product managers customer interviews, current source notes should come first; stale or partial inputs should trigger a fresh interview guide with assumption probes pass instead of another saved answer.

Thread goal

Thread goal for product manager: turn the rough case from A PM is planning interviews with operations managers about how they hand off weekly status reports. into a customer interview guide formatted as clear sections, bullets, and a review checklist for a product team, stakeholder, customer researcher, or release owner, while the owner deciding whether this becomes customer interviews prompt pattern with source notes, constraints, and review checklist can still inspect customer interview guide quality, assumption and question ladder, and fairness and policy fit, assumption, question ladder, probing plan, and bias control, unsupported assumptions, and the friction that interview guides can lead the participant instead of testing assumptions neutrally. Failure pattern for customer interviews with product managers: the customer interview guide can sound polished while interview guides can lead the participant instead of testing assumptions neutrally, so the page should make that miss easy to catch.

Plan Customer Interviews should keep the task-specific proof trail and remove one-time details before reuse. 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 interview guide with assumption probes as finished. Approval for product managers customer interviews belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the interview guide with assumption probes review standard visible.

1
Working pass
Use this first when the source note is messy but concrete enough to produce a reviewable a customer interview guide.
```
Plan Customer Interviews first run: use the rough note "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." from A PM is planning interviews with operations managers about how they hand off weekly status reports.; build a customer interview guide as a customer interview guide formatted as clear sections, bullets, and a review checklist; rely on supplied facts for the main answer, label assumptions, keep assumption, question ladder, probing plan, and bias control visible, and end with the proof still needed for true experience, measurable proof, and target role fit.
```
Keep
Keep the exact source note, the requested output shape, and any line that directly supports assumption, question ladder, probing plan, and bias control.
Accept if
Accept the first answer only if it separates source-backed details from assumptions and gives the owner deciding whether this becomes customer interviews prompt pattern with source notes, constraints, and review checklist something concrete to inspect.
Stop if
Stop if the answer invents missing context, treats true experience, measurable proof, and target role fit as proven, or drifts into general plan customer interviews advice.
2
Missing proof pass
Use this after the first answer when the shape is useful but the model skipped questions that block real use.
```
Plan Customer Interviews 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 research goal, participant segment, assumptions, questions, and follow-up plan; 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 customer interview guide formatted as clear sections, bullets, and a review checklist, customer interview guide quality, assumption and question ladder, and fairness and policy fit, or the final handoff.
3
Reviewer challenge
Use this before sharing the answer, especially when it sounds polished enough to hide weak evidence.
```
Plan Customer Interviews 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 true experience, measurable proof, and target role fit; give each issue a repair sentence that keeps assumption, question ladder, probing plan, and bias control 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 owner deciding whether this becomes customer interviews prompt pattern with source notes, constraints, and review checklist 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
Final pass
Use this after the answer survives the gap fill and skeptic pass and is ready to become a working asset.
```
Plan Customer Interviews handoff: prepare the accepted a customer interview guide, a needs-checking block for true experience, measurable proof, and target role fit, a reviewer note for the owner deciding whether this becomes customer interviews prompt pattern with source notes, constraints, and review checklist, and a reusable version with variables for source notes, audience, output format, proof need, stop rule, and assumption, question ladder, probing plan, and bias control; remove one-time private details before saving.
```
Keep
Keep the accepted wording, the repair decisions, and the variables that make customer interviews 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 interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format. Examples for plan customer interviews help only when they keep the source note visible while shaping interview guide with assumption probes. A careful pass should keep the user's limit visible. In plan customer interviews, the supplied note becomes the base for a customer interview guide. A usable plan customer interviews input includes what is known, what is uncertain, and what the reviewer must verify.Audience or recipient knownProduct Managers who have real notes or context and need a structured first version of a customer interview guide.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 customer interview guide.Facts to verify listedCustomer Interviews reader check: who will read or approve this a customer interview guide, and what do they already know? Customer Interviews source sort: which lines in the rough note are facts, preferences, constraints, or open questions?Checker is namedThe final reviewer should know customer interview guide quality, assumption and question ladder, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to research goal, participant segment, assumptions, questions, and follow-up plan.Reuse rule clearReuse customer interviews only after private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a customer interview guide, and the review rule for assumption, question ladder, probing plan, and bias control still appears in the reusable prompt. Approval for product managers customer interviews belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the interview guide with assumption probes 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 customer interview guide.
Wait if: Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Who checks it: The final reviewer should know customer interview guide quality, assumption and question ladder, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to research goal, participant segment, assumptions, questions, and follow-up plan.
Reuse rule: Reuse customer interviews only after private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a customer interview guide, and the review rule for assumption, question ladder, probing plan, and bias control still appears in the reusable prompt. Approval for product managers customer interviews belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the interview guide with assumption probes 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 interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format. Examples for plan customer interviews help only when they keep the source note visible while shaping interview guide with assumption probes. A careful pass should keep the user's limit visible. In plan customer interviews, the supplied note becomes the base for a customer interview guide. A usable plan customer interviews input includes what is known, what is uncertain, and what the reviewer must verify.
Who checks it: The final reviewer should know customer interview guide quality, assumption and question ladder, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to research goal, participant segment, assumptions, questions, and follow-up plan.
Stop rule: Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.
Reuse choice: Reuse customer interviews only after private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a customer interview guide, and the review rule for assumption, question ladder, probing plan, and bias control still appears in the reusable prompt. Approval for product managers customer interviews belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the interview guide with assumption probes 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

A rough customer interviews note comes in: "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." is the rough request. Before reusing customer interviews, make a customer interview guide useful by keeping assumption, question ladder, probing plan, and bias control, naming the checker, and preserving this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.

Received note: Received note for Product Managers Plan Customer Interviews: "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." arrives as the source note inside a product decision workflow where evidence and tradeoffs need to stay visible, with The prompt must prioritize past behavior and neutral wording. as the first human concern and interview guide with assumption probes as the target artifact.
Question before run: Before the first run, ask which part of "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." is fixed source material and which part is only preference, guesswork, or a missing approval point for the person who will approve a customer interview guide.
First answer flaw: First answer flaw for Product Managers Plan Customer Interviews: the first answer may sound polished while it drops the rough-note constraint, skips the reviewer, and turns true experience, measurable proof, and target role fit into an implied claim instead of a checkable line.
Human edit: Human edit for Product Managers Plan Customer Interviews: rewrite the answer so each useful section names what came from the note, what still needs true experience, measurable proof, and target role fit, and where the person who will approve a customer interview guide should stop before sharing it; the editor also has to replace polished filler with source-backed lines inside a customer interview guide; the edit has to preserve "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." and leave interview guide with assumption probes ready for a reviewer, not just prettier.
Reusable field: Reusable field for Product Managers Plan Customer Interviews: save the reusable fields as source note, audience, output shape, reviewer, stop rule, and assumption, question ladder, probing plan, and bias control; do not save private details or one-time facts as fixed wording. Keep the field set alert to this repeat risk: interview guides can lead the participant instead of testing assumptions neutrally.

Questions before reuse

Customer Interviews reader check: who will read or approve this a customer interview guide, and what do they already know?
Customer Interviews source sort: which lines in the rough note are facts, preferences, constraints, or open questions?
Customer Interviews blank rule: what should stay blank or flagged if true experience, measurable proof, and target role fit is missing?

Who checks it

Customer Interviews source note: treat "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." as the factual base, not decorative background; the next usable asset is interview guide with assumption probes.
Customer Interviews evidence check: mark any section where true experience, measurable proof, and target role fit is assumed instead of shown, especially when interview guides can lead the participant instead of testing assumptions neutrally.
Customer Interviews scope check: keep the answer on assumption, question ladder, probing plan, and bias control; do not drift away from a product decision workflow where evidence and tradeoffs need to stay visible.
Customer Interviews final polish: rewrite final wording only after customer interview guide quality, assumption and question ladder, and fairness and policy fit is clear enough for the product team, stakeholder, customer researcher, or release owner owner, then replace polished filler with source-backed lines inside a customer interview guide.
Customer Interviews freshness rule: For product managers customer interviews, current source notes should come first; stale or partial inputs should trigger a fresh interview guide with assumption probes pass instead of another saved answer.

Usable output

A usable customer interviews handoff would return a customer interview guide formatted as clear sections, bullets, and a review checklist; separate supplied notes from assumptions, name the review owner, prepare interview guide with assumption probes, and make the human pass focused on customer interview guide quality, assumption and question ladder, and fairness and policy fit.

Save this noteRough note that changes the prompt: Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format. Task-specific source material: research goal, participant segment, assumptions, questions, and follow-up plan Human check to keep visible: customer interview guide quality, assumption and question ladder, and fairness and policy fit

Stop hereSend it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.

Save for reuseReuse customer interviews only after private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a customer interview guide, and the review rule for assumption, question ladder, probing plan, and bias control still appears in the reusable prompt. Approval for product managers customer interviews belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the interview guide with assumption probes 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 Managers bring plan customer interviews source notes: A PM is planning interviews with operations managers about how they hand off weekly status reports. The source says "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." The answer needs to become interview guide with assumption probes 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 prioritize past behavior and neutral wording.

Why this input is messy

This plan customer interviews input needs care because the note carries facts, preferences, limits, and open approval points in one line; a quick answer can smooth over true experience, measurable proof, and target role fit, miss assumption, question ladder, probing plan, and bias control, or make a customer interview guide look ready before the person approving a customer interview guide checks it, especially when interview guides can lead the participant instead of testing assumptions neutrally.

First prompt move

product manager should start plan customer interviews by asking ChatGPT to ask ChatGPT to restate the source notes in three buckets before writing: facts it can use, assumptions it must not hide, and missing points that affect true experience, measurable proof, and target role fit; this is a context pass before polish because a customer interview guide formatted as clear sections, bullets, and a review checklist has to stay traceable to the original note.

Questions ChatGPT should ask

Reader detail in plan customer interviews: who will read this a customer interview guide, and what do they already know?
Source detail in plan customer interviews: which note details are verified facts, and which parts still need true experience, measurable proof, and target role fit?
Constraint detail in plan customer interviews: what tone, length, channel, or approval rule matters before the answer reaches a product team, stakeholder, customer researcher, or release owner?
Reuse detail in plan customer interviews: which person will inspect customer interview guide quality, assumption and question ladder, and fairness and policy fit, and what would make the answer unsafe to reuse?

Usable answer shape

The plan customer interviews answer should return a customer interview guide formatted as clear sections, bullets, and a review checklist, separate source-backed sections from assumptions and open questions, show how assumption, question ladder, probing plan, and bias control shaped the result, name the person approving a customer interview guide, and end with a short check for customer interview guide quality, assumption and question ladder, and fairness and policy fit before the answer is shared or saved.

Human revision

product manager should revise plan customer interviews by keeping the structure that saved time, replace polished filler with source-backed lines inside a customer interview guide, 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 interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." and make sure The final guide should be fair, focused, and ready for researcher review.

Save or discard

Save the plan customer interviews run only when the note, output shape, checker, interview guide with assumption probes, 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 true experience, measurable proof, and target role fit is implied but not checkable.

Run prompt Grade answer Repair answer

Why this page is not interchangeable

Work moment

This page fits the handoff point where a product team, stakeholder, customer researcher, or release owner needs a customer interview guide formatted as clear sections, bullets, and a review checklist, not a longer explanation of plan customer interviews.

Why this page

Do first

Choose the recommended prompt only after the handoff owner and output shape are clear enough for a product team, stakeholder, customer researcher, or release owner.

Next best workflow

Write user storiesUseful 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 interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.
Task-specific source material: research goal, participant segment, assumptions, questions, and follow-up plan
Human check to keep visible: customer interview guide quality, assumption and question ladder, and fairness and policy fit
Evidence pressure point: true experience, measurable proof, and target role fit

Wrong page if

The user cannot provide research goal, participant segment, assumptions, questions, and follow-up plan and would need ChatGPT to invent the important facts.
The desired result is not a customer interview guide or cannot be shaped as a customer interview guide formatted as clear sections, bullets, and a review checklist.
The task would be safer on Write user stories 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 Plan Customer Interviews when your notes already include this check: Task-specific source material: research goal, participant segment, assumptions, questions, and follow-up plan.; 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 research goal, participant segment, assumptions, questions, and follow-up plan and would need ChatGPT to invent the important facts.
Write user stories: Use this page
Stay with ChatGPT Prompts for Product Managers to Plan Customer Interviews when your notes already include this check: Human check to keep visible: customer interview guide quality, assumption and question ladder, and fairness and policy fit.; 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 customer interview guide or cannot be shaped as a customer interview guide formatted as clear sections, bullets, and a review checklist.
Define acceptance criteria: Use this page
Stay with ChatGPT Prompts for Product Managers to Plan Customer Interviews when your notes already include this check: Evidence pressure point: true experience, measurable proof, and target role fit.; 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 Write user stories because the main decision is closer to that workflow.

Run the page by work state

Start by turning the rough request into named fields before asking for a customer interview guide.

Build The Asset

Use this when the notes are ready and the next useful output is a customer interview guide formatted as clear sections, bullets, and a review checklist, not more brainstorming.

Open section

Do now: Copy the recommended prompt, replace the variables, and ask for a customer interview guide with assumptions separated from source-backed details.
Bring: Bring the task focus: assumption, question ladder, probing plan, and bias control. Add the channel, deadline, and any required sections.
Stop if: Stop if the first answer gives broad advice instead of a concrete a customer interview guide.
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 research goal, participant segment, assumptions, questions, and follow-up plan; add the reviewer, the audience, and the boundary from this case: The prompt must prioritize past behavior and neutral wording.

Reusable handoff

A usable handoff is a customer interview guide formatted as clear sections, bullets, and a review checklist with assumptions, source-backed sections, and a reviewer note for customer interview guide quality, assumption and question ladder, and fairness and policy fit.

Reality checks

Does the page-specific note "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." change the prompt, or could this still fit another task unchanged?
Can the reviewer check customer interview guide quality, assumption and question ladder, and fairness and policy fit without asking ChatGPT to invent missing facts?
Does the answer become a customer interview guide, or does it stay at broad plan customer interviews 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

Plan customer interviews Evidence-Aware Working Copy Prompt

Use this when the source material is ready and the answer needs to become a customer interview guide.

Use this when: Use before asking ChatGPT for plan customer interviews so the model has enough task-specific context.
When this fits: Turn research goal, participant segment, assumptions, questions, and follow-up plan into a customer interview guide for a product team, stakeholder, customer researcher, or release owner.
Do next: Treat the model answer as working copy to test and tag the parts where true experience, measurable proof, and target role fit changes the decision.

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 Plan Customer Interviews

Goal: Find a copyable prompt workbench that helps product managers plan customer interviews with the right source material, review lens, example, and follow-up prompts.
Working scenario: A PM is planning interviews with operations managers about how they hand off weekly status reports. The plan customer interviews work happens inside a product decision workflow where evidence and tradeoffs need to stay visible. For product managers customer interviews, current source notes should come first; stale or partial inputs should trigger a fresh interview guide with assumption probes pass instead of another saved answer. Approval for product managers customer interviews belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the interview guide with assumption probes review standard visible. For plan customer interviews, the page should make this situation feel familiar enough that the user can swap in their own notes without guessing what each variable means.

What I know:
Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format. Examples for plan customer interviews help only when they keep the source note visible while shaping interview guide with assumption probes. A careful pass should keep the user's limit visible. In plan customer interviews, the supplied note becomes the base for a customer interview guide. A usable plan customer interviews input includes what is known, what is uncertain, and what the reviewer must verify.

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 customer interview guide. Do not paste private names, identifiers, account details, student records, customer records, or confidential strategy when a summarized version is enough.

Who checks it:
The final reviewer should know customer interview guide quality, assumption and question ladder, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to research goal, participant segment, assumptions, questions, and follow-up plan.

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 The final reviewer should know customer interview guide quality, assumption and question ladder, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to research goal, participant segment, assumptions, questions, and follow-up plan.

Source review, plan customer interviews: the answer uses the supplied research goal, participant segment, assumptions, questions, and follow-up plan and does not fill missing facts with confident guesses.Output shape, plan customer interviews: the result clearly becomes a customer interview guide, not broad advice about the task.Handoff clarity, plan customer interviews: the answer names missing inputs and the next human check for customer interview guide quality, assumption and question ladder, and fairness and policy fit.Audience fit, plan customer interviews: the result works for a product team, stakeholder, customer researcher, or release owner, including channel, tone, length, and decision context.Risk boundary, plan customer interviews: the final version respects keep the wording fair, job-related, and reviewed by the appropriate human.

Needs another review pass

a customer interview guide final pass: keep the useful structure, then replace polished filler with source-backed lines inside a customer interview guide; readiness means a product team, stakeholder, customer researcher, or release owner can see what was provided, what was assumed, why interview guides can lead the participant instead of testing assumptions neutrally, and what still needs review.

Task-specific output diagnosis

Paste the first Plan Customer Interviews answer and compare it with "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." before checking style. A useful product manager output must prove it belongs to this page by keeping assumption, question ladder, probing plan, and bias control, a customer interview guide formatted as clear sections, bullets, and a review checklist, and the task reviewer visible.

Pass when

The answer uses "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." as the controlling case, not as decoration, and turns it into a customer interview guide formatted as clear sections, bullets, and a review checklist with assumption, question ladder, probing plan, and bias control still visible.
The answer shows which lines come from "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." and which lines remain assumptions before a product team, stakeholder, customer researcher, or release owner sees the customer interview guide.
The answer gives the task reviewer a clear check tied to "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.", especially the point where true experience, measurable proof, and target role fit cannot be treated as proven.
The answer can become customer interviews prompt pattern with source notes, constraints, and review checklist only after the one-time facts in "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." 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 interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.", so the plan customer interviews output could fit another page.
It gives a generic next step while hiding assumption, question ladder, probing plan, and bias control, which makes the answer feel useful before it can support the real a customer interview guide.
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 customer interview guide formatted as clear sections, bullets, and a review checklist, true experience, measurable proof, and target role fit, or the source material that makes this plan customer interviews page different.

Repair next

Rewrite the opening around "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." and keep the first sentence tied to assumption, question ladder, probing plan, and bias control before improving tone or length.
Add a needs-checking block for true experience, measurable proof, and target role fit, then separate supplied facts from assumptions before returning a customer interview guide formatted as clear sections, bullets, and a review checklist.
Mark the line the task reviewer must inspect for customer interview guide quality, assumption and question ladder, and fairness and policy fit, and move unsupported claims out of the usable answer.
Replace one-time details with variables for the saved customer interviews prompt pattern with source notes, constraints, and review checklist, then rerun only the section that failed the plan customer interviews check.

Red flags

Evidence issue, plan customer interviews: the answer invents or overstates true experience, measurable proof, and target role fit.
Task drift, plan customer interviews: it ignores assumption, question ladder, probing plan, and bias control and moves into a neighboring workflow.
Readiness gap, plan customer interviews: it sounds complete while leaving customer interview guide quality, assumption and question ladder, and fairness and policy fit impossible to verify.
Privacy issue, plan customer interviews: it includes details that should have been summarized or removed.
Generic output, plan customer interviews: 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

A rushed Product Managers Plan Customer Interviews pass copies a line like "Here is a polished version based on your notes It covers the main points, keeps a professional tone, and adds a useful next step" and then moves on. Plan Customer Interviews failure to avoid for product manager: it also leaves no place for assumptions, missing facts, or a reviewer note; the actual note to protect is Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.

Why it fails

Plan Customer Interviews repair note: the answer looks confident because it uses smooth wording, but it never proves where the key claims came from The next pass must bring back assumption, question ladder, probing plan, and bias control, show which parts depend on true experience, measurable proof, and target role fit, make the person approving a customer interview guide visible before a product team, stakeholder, customer researcher, or release owner sees the result, and handle the real friction: interview guides can lead the participant instead of testing assumptions neutrally.

Trace the rough note

Problem: The answer mentions a customer interview guide but does not reflect the concrete case: A PM is planning interviews with operations managers about how they hand off weekly status reports.
Repair: Rewrite the first section around the user note, then mark which details came from the note, which details still need confirmation, and where interview guide with assumption probes changes the output.

Name the reviewer

Problem: The answer can move forward without anyone checking customer interview guide quality, assumption and question ladder, and fairness and policy fit.
Repair: Add a reviewer line for the person approving a customer interview guide, plus one question that must be answered before the result is shared.

Protect the evidence

Problem: The answer can imply true experience, measurable proof, and target role fit 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 plan customer interviews into broad advice that does not produce a customer interview guide formatted as clear sections, bullets, and a review checklist.
Repair: Force the final answer back into a customer interview guide formatted as clear sections, bullets, and a review checklist, keep assumption, question ladder, probing plan, and bias control as the main decision point, and replace polished filler with source-backed lines inside a customer interview guide.

Human-edited direction

Human Plan Customer Interviews revision for Product Managers: start with the actual case, name the audience, return a customer interview guide formatted as clear sections, bullets, and a review checklist, keep supplied notes, assumptions, and missing checks separate, then replace polished filler with source-backed lines inside a customer interview guide, tell a product team, stakeholder, customer researcher, or release owner what is ready to use, what the person approving a customer interview guide must verify, and how the answer becomes customer interviews prompt pattern with source notes, constraints, and review checklist without private or one-time details.

Rerun prompt

Rerun Product Managers Plan Customer Interviews: repair this plan customer interviews answer, keep the result focused on assumption, question ladder, probing plan, and bias control, return a customer interview guide formatted as clear sections, bullets, and a review checklist, put unsupported claims about true experience, measurable proof, and target role fit in a needs-checking block, name the reviewer as the person approving a customer interview guide, protect this boundary "keep the wording fair, job-related, and reviewed by the appropriate human", and use only these source notes: Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.

Accept when

The answer visibly uses the rough note instead of generic plan customer interviews advice.
The result is shaped as a customer interview guide formatted as clear sections, bullets, and a review checklist and can be checked by the person approving a customer interview guide.
Any uncertain point about true experience, measurable proof, and target role fit is separated from the usable parts.
The reusable version keeps assumption, question ladder, probing plan, and bias control 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 customer interview guide quality, assumption and question ladder, and fairness and policy fit 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 interview prompts that test assumptions without leading the participant. For plan customer interviews, the page has to answer a product managers plan customer interviews need where interview guides can lead the participant instead of testing assumptions neutrally. Search edge for customer interviews with product managers: show interview guide with assumption probes, a human review path for a customer interview guide, and the task-specific reason the page deserves the query. Outside proof for customer interviews with product managers: an independent resource must mention the customer interview guide page visibly before interview guide with assumption probes becomes an authority claim. For a customer interview guide for product managers, the useful distinction is that the page has value when it turns a broad ChatGPT request into a sequence the user can inspect, repair, and reuse carefully.

Concrete scenario

A PM is planning interviews with operations managers about how they hand off weekly status reports. The plan customer interviews work happens inside a product decision workflow where evidence and tradeoffs need to stay visible. For product managers customer interviews, current source notes should come first; stale or partial inputs should trigger a fresh interview guide with assumption probes pass instead of another saved answer. Approval for product managers customer interviews belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the interview guide with assumption probes review standard visible. For plan customer interviews, the page should make this situation feel familiar enough that the user can swap in their own notes without guessing what each variable means.

Real user input

Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format. Examples for plan customer interviews help only when they keep the source note visible while shaping interview guide with assumption probes. A careful pass should keep the user's limit visible. In plan customer interviews, the supplied note becomes the base for a customer interview guide. A usable plan customer interviews input includes what is known, what is uncertain, and what the reviewer must verify.

Editor take

The prompt must prioritize past behavior and neutral wording. In this plan customer interviews review, the edit is to replace polished filler with source-backed lines inside a customer interview guide. Failure pattern for customer interviews with product managers: the customer interview guide can sound polished while interview guides can lead the participant instead of testing assumptions neutrally, so the page should make that miss easy to catch. In the plan customer interviews review, the editorial test is whether the answer can be checked quickly against customer interview guide quality, assumption and question ladder, and fairness and policy fit and the user's actual source; compare the answer with the actual notes before reuse.

Human polish

The final guide should be fair, focused, and ready for researcher review. Approval for product managers customer interviews belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the interview guide with assumption probes review standard visible. Before handing off plan customer interviews, before reuse, the human should tighten tone, verify facts, and remove any claim the source material does not support, with a short record of what changed before reuse and where For product managers customer interviews, current source notes should come first; stale or partial inputs should trigger a fresh interview guide with assumption probes pass instead of another saved answer.

Fast use path

Main card for a customer interview guide: use the main prompt as the first pass so the page stays action-oriented.
Source material for a customer interview guide: replace [source_material] with research goal, participant segment, assumptions, questions, and follow-up plan.
Audience details for a customer interview guide: fill in the audience, channel, and approval point before asking for a finished answer.
Review pass for a customer interview guide: ask for a second pass that flags issues in customer interview guide quality, assumption and question ladder, and fairness and policy fit.

Specificity signals

A PM is planning interviews with operations managers about how they hand off weekly status reports.
Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.
research goal, participant segment, assumptions, questions, and follow-up plan
assumption, question ladder, probing plan, and bias control
true experience, measurable proof, and target role fit
keep the wording fair, job-related, and reviewed by the appropriate human
interview guide with assumption probes
interview guides can lead the participant instead of testing assumptions neutrally
replace polished filler with source-backed lines inside a customer interview guide
a product decision workflow where evidence and tradeoffs need to stay visible
For product managers customer interviews, current source notes should come first; stale or partial inputs should trigger a fresh interview guide with assumption probes pass instead of another saved answer.
Approval for product managers customer interviews belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the interview guide with assumption probes review standard visible.
Search edge for customer interviews with product managers: show interview guide with assumption probes, a human review path for a customer interview guide, and the task-specific reason the page deserves the query.
Failure pattern for customer interviews with product managers: the customer interview guide can sound polished while interview guides can lead the participant instead of testing assumptions neutrally, so the page should make that miss easy to catch.
Outside proof for customer interviews with product managers: an independent resource must mention the customer interview guide page visibly before interview guide with assumption probes becomes an authority claim.

Real use sample: how the messy note changes the prompt

Messy brief

Ask before copying

Customer Interviews reader check: who will read or approve this a customer interview guide, and what do they already know?
Customer Interviews source sort: which lines in the rough note are facts, preferences, constraints, or open questions?
Customer Interviews blank rule: what should stay blank or flagged if true experience, measurable proof, and target role fit is missing?
Customer Interviews stop signal: which visible mistake would stop the team from using the answer?

Checks before sharing

Customer Interviews source note: treat "Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format." as the factual base, not decorative background; the next usable asset is interview guide with assumption probes.
Customer Interviews evidence check: mark any section where true experience, measurable proof, and target role fit is assumed instead of shown, especially when interview guides can lead the participant instead of testing assumptions neutrally.
Customer Interviews scope check: keep the answer on assumption, question ladder, probing plan, and bias control; do not drift away from a product decision workflow where evidence and tradeoffs need to stay visible.
Customer Interviews final polish: rewrite final wording only after customer interview guide quality, assumption and question ladder, and fairness and policy fit is clear enough for the product team, stakeholder, customer researcher, or release owner owner, then replace polished filler with source-backed lines inside a customer interview guide.
Customer Interviews freshness rule: For product managers customer interviews, current source notes should come first; stale or partial inputs should trigger a fresh interview guide with assumption probes pass instead of another saved answer.
Customer Interviews failure pattern: Failure pattern for customer interviews with product managers: the customer interview guide can sound polished while interview guides can lead the participant instead of testing assumptions neutrally, so the page should make that miss easy to catch.
Customer Interviews decision owner: Approval for product managers customer interviews belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the interview guide with assumption probes review standard visible.

Before and after

Weak answer risk: The weak customer interviews answer risk is specific: the answer sounds complete while turning "need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format;" into broad advice, hiding missing context around true experience, measurable proof, and target role fit, and leaving a product team, stakeholder, customer researcher, or release owner without a clear decision path because interview guides can lead the participant instead of testing assumptions neutrally. Failure pattern for customer interviews with product managers: the customer interview guide can sound polished while interview guides can lead the participant instead of testing assumptions neutrally, so the page should make that miss easy to catch.
Improved outcome: A usable customer interviews handoff would return a customer interview guide formatted as clear sections, bullets, and a review checklist; separate supplied notes from assumptions, name the review owner, prepare interview guide with assumption probes, and make the human pass focused on customer interview guide quality, assumption and question ladder, and fairness and policy fit.
Why it feels real: The customer interviews example feels grounded 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 customer interviews, current source notes should come first; stale or partial inputs should trigger a fresh interview guide with assumption probes pass instead of another saved answer.

Reusable version decision

Reuse customer interviews only after private details are removed, one-time facts become variables, replace polished filler with source-backed lines inside a customer interview guide, and the review rule for assumption, question ladder, probing plan, and bias control still appears in the reusable prompt. Approval for product managers customer interviews belongs with the accountable reviewer before the answer reaches a product team, stakeholder, customer researcher, or release owner; keep the interview guide with assumption probes review standard visible.

The job this page helps finish

Users who search this task are likely comparing quick copy-and-run help with pages that explain the whole run. It should explain what a good answer includes and what kind of answer should be sent back. The prompt path stays useful because it keeps returning to assumption, question ladder, probing plan, and bias control.

Use Cases

Turn research goal, participant segment, assumptions, questions, and follow-up plan into a customer interview guide for a product team, stakeholder, customer researcher, or release owner.
Review an existing plan customer interviews answer for customer interview guide checkpoint, missing details, and unsupported claims.
Create a repeatable customer interviews prompt pattern with source notes, constraints, and review checklist so the next version starts from stronger context.
Make assumption, question ladder, probing plan, and bias control visible so the answer stays tied to a customer interview guide instead of drifting into a neighboring task.
Condense a long ChatGPT answer into a customer interview guide formatted as clear sections, bullets, and a review checklist 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 research goal, participant segment, assumptions, questions, and follow-up plan; do not ask the model to guess it.
Name the final decision the plan customer interviews 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 true experience, measurable proof, and target role fit.
Add the task-specific focus: assumption, question ladder, probing plan, and bias control.

Check the answer against real references

What users are trying to finish

The user intent is task-level; a role page alone would not show how a customer interview guide should be built or checked. Users should see how the prompt changes when the audience, evidence, or approval owner changes. The route should make the output less generic by showing how research goal, participant segment, assumptions, questions, and follow-up plan changes a customer interview guide and the review burden.

Why the workflow matters

It combines runnable prompts with a run sheet, so users can choose whether they are collecting context, creating, reviewing, or handing off. The grader and repair lab make the page useful when the first model answer is plausible but weak.

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 true experience, measurable proof, and target role fit reviewable.
Google Search Central SEO Starter GuideUsed to keep titles, descriptions, links, and page structure focused on helping search engines and users understand a customer interview guide.
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 customer interview guide needs human oversight, assumptions, and review controls.
FTC advertising and marketing guidanceUsed as the second product reference when a customer interview guide affects market-facing claims, proof language, or customer communication.

Related ways people ask for this task

Main query covered: chatgpt prompts for product managers customer interviews

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

customer interviews chatgpt prompt for product managers
best chatgpt prompts for customer interviews
customer interviews prompt template for product managers
copyable customer interviews chatgpt prompt
customer interviews ai prompt with review checklist
chatgpt customer interviews 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 customer interview guide and not just a blank prompt.
Look for missing-source risks around true experience, measurable proof, and target role fit, 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

Real-world case

a customer interview guide scenario: this task feels human when the page handles the moment where product managers provide research goal, participant segment, assumptions, questions, and follow-up plan, need a customer interview guide formatted as clear sections, bullets, and a review checklist, and must keep assumption, question ladder, probing plan, and bias control visible while checking true experience, measurable proof, and target role fit. For product managers, plan customer interviews is reviewed inside a product decision workflow where evidence and tradeoffs need to stay visible, with interview guide with assumption probes as the concrete item on the desk.

Checks before sharing

Source review, plan customer interviews: the answer uses the supplied research goal, participant segment, assumptions, questions, and follow-up plan and does not fill missing facts with confident guesses.
Output shape, plan customer interviews: the result clearly becomes a customer interview guide, not broad advice about the task.
Handoff clarity, plan customer interviews: the answer names missing inputs and the next human check for customer interview guide quality, assumption and question ladder, and fairness and policy fit.
Audience fit, plan customer interviews: the result works for a product team, stakeholder, customer researcher, or release owner, including channel, tone, length, and decision context.
Risk boundary, plan customer interviews: the final version respects keep the wording fair, job-related, and reviewed by the appropriate human.

Compare with other results

Question to compare: chatgpt prompts for product managers customer interviews

Result customer interviews product managers check: open the top results and record whether they solve the task, not only a prompt phrase.
Example customer interviews product managers check: compare whether competing pages show a filled example for a customer interview guide using realistic research goal, participant segment, assumptions, questions, and follow-up plan.
Evidence customer interviews product managers check: mark whether each page explains how to verify true experience, measurable proof, and target role fit and customer interview guide quality, assumption and question ladder, and fairness and policy fit.
Differentiator customer interviews product managers check: compare the top results against this page promise: Search edge for customer interviews with product managers: show interview guide with assumption probes, a human review path for a customer interview guide, and the task-specific reason the page deserves the query.
Failure customer interviews product managers check: mark whether competing pages show this failure mode or avoid it: Failure pattern for customer interviews with product managers: the customer interview guide can sound polished while interview guides can lead the participant instead of testing assumptions neutrally, so the page should make that miss easy to catch.
Freshness customer interviews product managers check: record whether competing pages say how source notes stay current. For product managers customer interviews, current source notes should come first; stale or partial inputs should trigger a fresh interview guide with assumption probes pass instead of another saved answer.
Page type customer interviews product managers check: confirm whether Google is rewarding a role hub, task page, tool, article, video, or forum thread for this query.
FAQ customer interviews 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 customer interviews with product managers: an independent resource must mention the customer interview guide page visibly before interview guide with assumption probes 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 plan customer interviews 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 plan customer interviews by turning [source_material] into a customer interview guide for [audience]. Keep the task focus on assumption, question ladder, probing plan, and bias control. Use this output shape: a customer interview guide formatted as clear sections, bullets, and a review checklist. Do not add facts beyond the source. End with a review checklist for customer interview guide quality, assumption and question ladder, and fairness and policy fit and true experience, measurable proof, and target role fit.

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 is planning interviews with operations managers about how they hand off weekly status reports. The user needs help with plan customer interviews, but the real job is to turn a messy request into a customer interview guide that a product team, stakeholder, customer researcher, or release owner can review without hidden assumptions.

Weak prompt

Write a good plan customer interviews from this: Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.

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 assumption, question ladder, probing plan, and bias control, inventing details, or skipping customer interview guide quality, assumption and question ladder, and fairness and policy fit.

Stronger prompt

Act as a careful assistant for Product Managers.
I need help with plan customer interviews. Use only this source material: Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.
The usual source material for this task is research goal, participant segment, assumptions, questions, and follow-up plan.
The audience is [audience], and the output must work for a product team, stakeholder, customer researcher, or release owner.
Create a customer interview guide in this shape: a customer interview guide formatted as clear sections, bullets, and a review checklist.
Keep the task focus on assumption, question ladder, probing plan, and bias control.
Respect this editorial rule: The prompt must prioritize past behavior and neutral wording.
If context is missing, ask up to three clarifying questions before writing.
After the answer, include a review checklist for customer interview guide quality, assumption and question ladder, and fairness and policy fit, true experience, measurable proof, and target role fit, and this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.

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 true experience, measurable proof, and target role fit visible for human checking.

Sample input

A PM is planning interviews with operations managers about how they hand off weekly status reports. User notes: Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format. Audience: a product team, stakeholder, customer researcher, or release owner. Constraints: avoid unsupported claims, protect private details, and keep focus on assumption, question ladder, probing plan, and bias control.

Simulated output

A useful answer starts by restating the real situation, then provides a customer interview guide formatted as clear sections, bullets, and a review checklist. It marks assumptions, shows which parts came from the user's notes, includes a concise next action, and ends with checks for customer interview guide quality, assumption and question ladder, and fairness and policy fit, true experience, measurable proof, and target role fit, and this boundary: keep the wording fair, job-related, and reviewed by the appropriate human. The output should already reflect the practical review target that matters here, so the final guide should be fair, focused, and ready for researcher review.

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 customer interviews 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 assumption, question ladder, probing plan, and bias control is still the center of the answer. The pass is accepted only when the final guide should be fair, focused, and ready for researcher review.

Fit

Use when product managers have real source notes for plan customer interviews.
Use when the desired result is a customer interview guide, not broad advice.
Use when a human can review customer interview guide quality, assumption and question ladder, and fairness and policy fit 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 true experience, measurable proof, and target role fit is unavailable and cannot be checked.
Do not use as final judgment for sensitive decisions covered by this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.

Worked example: Plan customer interviews example from rough notes

Example input

A PM is planning interviews with operations managers about how they hand off weekly status reports. Raw input: Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.

Prompt use

Use the evidence-aware prompt to convert those notes into a customer interview guide, then run the review prompt against this editorial rule: The prompt must prioritize past behavior and neutral wording.

Sample output shape

A useful answer would return a customer interview guide formatted as clear sections, bullets, and a review checklist 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 assumption, question ladder, probing plan, and bias control at the center, and avoid adding facts that are not present. The final section should tell the user what still needs checking, especially true experience, measurable proof, and target role fit. The human pass is not decoration here: The final guide should be fair, focused, and ready for researcher review.

Review notes

Confirm the answer reflects this actual situation: A PM is planning interviews with operations managers about how they hand off weekly status reports.
Compare the output against the raw user input: Need interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format.
Confirm the source material really supports true experience, measurable proof, and target role fit.
Check that the wording fits a product team, stakeholder, customer researcher, or release owner.
Confirm the answer handles assumption, question ladder, probing plan, and bias control instead of a neighboring task.
Remove details that violate this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.

Prompt Workbench

beginner

Plan customer interviews Context Intake Prompt

Use this before plan customer interviews when the notes are rough and ChatGPT should ask clarifying questions first.

Act as a careful assistant for Product Managers.
Task: help me plan customer interviews. Target result: a customer interview guide.
Source material I can provide: [source_material]. Typical source for this task is research goal, participant segment, assumptions, questions, and follow-up plan.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: assumption, question ladder, probing plan, and bias control.
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 customer interview guide quality, assumption and question ladder, and fairness and policy fit; verify true experience, measurable proof, and target role fit; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
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 plan customer interviews.Example: research goal, participant segment, assumptions, questions, and follow-up plan
[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 customer interview guide easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: keep the wording fair, job-related, and reviewed by the appropriate human
[review_lens]: The most important thing a human should check after the answer.Example: customer interview guide quality, assumption and question ladder, and fairness and policy fit
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: assumption, question ladder, probing plan, and bias control

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 customer interview guide quality, assumption and question ladder, and fairness and policy fit.

Follow-up prompt

Now improve this working version into a customer interview guide by tightening customer interview guide quality, assumption and question ladder, and fairness and policy fit, emphasizing assumption, question ladder, probing plan, and bias control, 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 true experience, measurable proof, and target role fit, fits a product team, stakeholder, customer researcher, or release owner, reflects assumption, question ladder, probing plan, and bias control, and respects this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.

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

advanced

Plan customer interviews Evidence-Aware Working Copy Prompt

Use this when the source material is ready and the answer needs to become a customer interview guide.

Act as a careful assistant for Product Managers.
Task: help me plan customer interviews. Target result: a customer interview guide.
Source material I can provide: [source_material]. Typical source for this task is research goal, participant segment, assumptions, questions, and follow-up plan.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: assumption, question ladder, probing plan, and bias control.
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 customer interview guide formatted as clear sections, bullets, and a review checklist.
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 customer interview guide quality, assumption and question ladder, and fairness and policy fit; verify true experience, measurable proof, and target role fit; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
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 plan customer interviews.Example: research goal, participant segment, assumptions, questions, and follow-up plan
[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 customer interview guide easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: keep the wording fair, job-related, and reviewed by the appropriate human
[review_lens]: The most important thing a human should check after the answer.Example: customer interview guide quality, assumption and question ladder, and fairness and policy fit
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: assumption, question ladder, probing plan, and bias control

Expected output

Expect a customer interview guide formatted as clear sections, bullets, and a review checklist that explicitly separates source-based content from assumptions and ends with a review pass for customer interview guide quality, assumption and question ladder, and fairness and policy fit.

Follow-up prompt

Human review

Best for: Turning prepared context into a customer interview guide. Use when: Use before asking ChatGPT for plan customer interviews so the model has enough task-specific context.

workflow

Plan customer interviews Repeatable Workflow Prompt

Use this when plan customer interviews repeats often enough to become customer interviews prompt pattern with source notes, constraints, and review checklist.

Act as a careful assistant for Product Managers.
Task: help me plan customer interviews. Target result: a customer interview guide.
Source material I can provide: [source_material]. Typical source for this task is research goal, participant segment, assumptions, questions, and follow-up plan.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: assumption, question ladder, probing plan, and bias control.
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 customer interview guide quality, assumption and question ladder, and fairness and policy fit; verify true experience, measurable proof, and target role fit; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
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 plan customer interviews.Example: research goal, participant segment, assumptions, questions, and follow-up plan
[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 customer interview guide easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: keep the wording fair, job-related, and reviewed by the appropriate human
[review_lens]: The most important thing a human should check after the answer.Example: customer interview guide quality, assumption and question ladder, and fairness and policy fit
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: assumption, question ladder, probing plan, and bias control

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 customer interview guide quality, assumption and question ladder, and fairness and policy fit.

Follow-up prompt

Human review

Best for: Creating a reusable process for repeated plan customer interviews work. Use when: Use when plan customer interviews repeats often enough to need a standard process.

review

Plan customer interviews Human Review Prompt

Use this after there is already working copy and the main need is customer interview guide quality, assumption and question ladder, and fairness and policy fit.

Act as a careful assistant for Product Managers.
Task: help me plan customer interviews. Target result: a customer interview guide.
Source material I can provide: [source_material]. Typical source for this task is research goal, participant segment, assumptions, questions, and follow-up plan.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: assumption, question ladder, probing plan, and bias control.
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 customer interview guide quality, assumption and question ladder, and fairness and policy fit; verify true experience, measurable proof, and target role fit; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
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 plan customer interviews.Example: research goal, participant segment, assumptions, questions, and follow-up plan
[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 customer interview guide easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: keep the wording fair, job-related, and reviewed by the appropriate human
[review_lens]: The most important thing a human should check after the answer.Example: customer interview guide quality, assumption and question ladder, and fairness and policy fit
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: assumption, question ladder, probing plan, and bias control

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 customer interview guide quality, assumption and question ladder, and fairness and policy fit.

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 customer interview guide quality, assumption and question ladder, and fairness and policy fit.

format

Plan customer interviews 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 plan customer interviews. Target result: a customer interview guide.
Source material I can provide: [source_material]. Typical source for this task is research goal, participant segment, assumptions, questions, and follow-up plan.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: assumption, question ladder, probing plan, and bias control.
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 customer interview guide quality, assumption and question ladder, and fairness and policy fit; verify true experience, measurable proof, and target role fit; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
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 plan customer interviews.Example: research goal, participant segment, assumptions, questions, and follow-up plan
[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 customer interview guide easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: keep the wording fair, job-related, and reviewed by the appropriate human
[review_lens]: The most important thing a human should check after the answer.Example: customer interview guide quality, assumption and question ladder, and fairness and policy fit
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: assumption, question ladder, probing plan, and bias control

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 customer interview guide quality, assumption and question ladder, and fairness and policy fit.

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

Plan customer interviews 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 plan customer interviews. Target result: a customer interview guide.
Source material I can provide: [source_material]. Typical source for this task is research goal, participant segment, assumptions, questions, and follow-up plan.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: assumption, question ladder, probing plan, and bias control.
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 customer interview guide quality, assumption and question ladder, and fairness and policy fit; verify true experience, measurable proof, and target role fit; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
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 plan customer interviews.Example: research goal, participant segment, assumptions, questions, and follow-up plan
[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 customer interview guide easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: keep the wording fair, job-related, and reviewed by the appropriate human
[review_lens]: The most important thing a human should check after the answer.Example: customer interview guide quality, assumption and question ladder, and fairness and policy fit
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: assumption, question ladder, probing plan, and bias control

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 customer interview guide quality, assumption and question ladder, and fairness and policy fit.

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

Plan customer interviews Fast Checklist Prompt

Use this for a quick pass when the user only needs the next few decisions for plan customer interviews.

Act as a careful assistant for Product Managers.
Task: help me plan customer interviews. Target result: a customer interview guide.
Source material I can provide: [source_material]. Typical source for this task is research goal, participant segment, assumptions, questions, and follow-up plan.
Audience or stakeholder: [audience]. The output must work for a product team, stakeholder, customer researcher, or release owner.
Task-specific focus: assumption, question ladder, probing plan, and bias control.
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 customer interview guide quality, assumption and question ladder, and fairness and policy fit; verify true experience, measurable proof, and target role fit; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
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 plan customer interviews.Example: research goal, participant segment, assumptions, questions, and follow-up plan
[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 customer interview guide easier to review, adapt, and use in a real product managers workflow
[constraints]: Rules, tone, length, channel, privacy limits, and required sections.Example: keep the wording fair, job-related, and reviewed by the appropriate human
[review_lens]: The most important thing a human should check after the answer.Example: customer interview guide quality, assumption and question ladder, and fairness and policy fit
[task_focus]: The task-specific detail that keeps this prompt from becoming generic.Example: assumption, question ladder, probing plan, and bias control

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 customer interview guide quality, assumption and question ladder, and fairness and policy fit.

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]: research goal, participant segment, assumptions, questions, and follow-up plan
[audience]: a product team, stakeholder, customer researcher, or release owner
[goal]: make a customer interview guide easier to review, adapt, and use in a real product managers workflow
[constraints]: keep the wording fair, job-related, and reviewed by the appropriate human
[review_lens]: customer interview guide quality, assumption and question ladder, and fairness and policy fit
[task_focus]: assumption, question ladder, probing plan, and bias control

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 research goal, participant segment, assumptions, questions, and follow-up plan to avoid guessing?
Specificity: Does the answer produce a customer interview guide rather than broad advice?
Task focus: Does it handle assumption, question ladder, probing plan, and bias control instead of drifting into a neighboring workflow?
Reviewability: Can a human quickly check customer interview guide checkpoint and true experience, measurable proof, and target role fit?
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 plan customer interviews without giving research goal, participant segment, assumptions, questions, and follow-up plan.
Accepting polished wording before checking true experience, measurable proof, and target role fit.
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: assumption, question ladder, probing plan, and bias control.
Skipping the review pass for customer interview guide quality, assumption and question ladder, and fairness and policy fit.
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 customer interview guide.
Do not paste private names, identifiers, account details, student records, customer records, or confidential strategy when a summarized version is enough.
Check that assumption, question ladder, probing plan, and bias control is supported by the source material and not invented.
Have a human review customer interview guide 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 plan customer interviews?

Use a prompt that names research goal, participant segment, assumptions, questions, and follow-up plan, asks for a customer interview guide formatted as clear sections, bullets, and a review checklist, and ends with a review pass for customer interview guide quality, assumption and question ladder, and fairness and policy fit.

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 research goal, participant segment, assumptions, questions, and follow-up plan.

How do I make the answer less generic?

Ask ChatGPT to use only the supplied material, show assumptions, and revise the answer against true experience, measurable proof, and target role fit 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: customer interview guide quality, assumption and question ladder, and fairness and policy fit.

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.

Plan Customer Interviews: keep interview guide with assumption probes sourced

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

Plan customer interviews 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 interview guide, warm-up, behavior questions, probes, assumption checks, avoid-leading rewrites, and note-taking format" as the visible source line for a customer interview guide

any confident claim about true experience, measurable proof, and target role fit 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 assumption, question ladder, probing plan, and bias control 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: Plan Customer Interviews 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

Facts the prompt can safely use

Unknowns the model must not hide

Rules the answer must obey

Details to summarize before reuse

Reusable fields for the next run

Iteration loop: run the prompt as a working thread

Thread goal

Working pass

Missing proof pass

Reviewer challenge

Final pass

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