You are a product researcher.
Create a user research plan for the feature below.
Context:
- Feature idea: [feature]
- Target users: [users]
- Main unknowns or risks: [risks]
- Timeline: [timeline]
- Research constraints: [constraints]
Instructions:
1. Clarify what the team actually needs to learn before building further.
2. Recommend the most useful methods for the timeline and risk level.
3. Suggest research questions that are tied to product decisions.
4. Keep the plan lean enough to run quickly.
5. Explain what decision each part of the research should support.
Output format:
- Research objectives
- Recommended methods
- Key questions
- Session or study plan
- Decisions this should inform
Missing information policy:
Proceed with assumptions unless the feature idea or target users are unclear.
Quality bar:
- Decision-oriented.
- Lean.
- Avoid research theater.
02
Write a User Interview Discussion Guide
Create a user interview guide that uncovers motivations, workflows, and pain points without leading participants.
You’ll needresearch goaltarget usersproduct contextknown hypothesestime available
Prompt
You are a product researcher writing a user interview guide.
Create the guide using the context below.
Context:
- Research goal: [goal]
- Target users: [users]
- Product context: [product]
- Known hypotheses: [hypotheses]
- Time available per interview: [time]
Instructions:
1. Write an interview guide that surfaces behavior, context, and motivations.
2. Avoid leading or solution-biased questions.
3. Include warm-up, core questions, follow-up probes, and wrap-up.
4. Keep the guide practical for a live conversation.
5. Note what signals the interviewer should listen for.
Output format:
- Interview guide
- Follow-up probes
- Signals to watch for
Missing information policy:
Proceed with assumptions unless the research goal or target users are unclear.
Quality bar:
- Non-leading questions.
- Behavior-focused.
- Easy to run live.
03
Synthesize Research Findings into Decisions
Turn research findings into clear themes, risks, and product decisions instead of a passive recap.
You are a product researcher synthesizing findings for decision-making.
Synthesize the research below.
Context:
- Research notes or evidence: [notes]
- Study goal: [goal]
- Decision this should inform: [decision]
- Known tensions or disagreements: [tensions]
- Audience: [audience]
Instructions:
1. Identify the strongest themes and what evidence supports them.
2. Distinguish signals from noise.
3. Translate findings into product implications and open questions.
4. Call out where confidence is high versus low.
5. Avoid turning the synthesis into a bland recap.
Output format:
- Key themes
- Evidence-backed insights
- Product implications
- Confidence notes
- Recommended next decisions
Missing information policy:
Proceed with assumptions unless the research material or decision target is unclear.
Quality bar:
- Evidence-backed.
- Decision-oriented.
- No passive summary dump.
04
Turn User Research into a Stakeholder Readout
Turn research findings into a stakeholder-ready readout with signal, implications, and product decisions.
You’ll needresearch inputsmain findingsaudiencedecisions at stakeconfidence limits
Prompt
You are a product research translator.
Turn the research below into a stakeholder readout.
Context:
- Research inputs or study summary: [research inputs]
- Main findings: [findings]
- Audience for the readout: [audience]
- Decisions at stake: [decisions]
- Confidence limits or caveats: [confidence limits]
Instructions:
1. Summarize the most decision-relevant findings without drowning the audience in raw detail.
2. Distinguish strong signal from tentative interpretation.
3. Explain what the findings imply for product, design, or prioritization decisions.
4. Call out what should not be concluded from the research.
5. End with recommended actions or follow-up questions.
Output format:
- Executive summary
- Key findings
- Implications for decisions
- Confidence limits
- Recommended actions
Missing information policy:
Proceed with assumptions unless the findings or audience are too vague to synthesize credibly.
Quality bar:
- Keep the signal sharp.
- Respect uncertainty.
- Make the readout decision-useful.
05
Synthesize User Pain Points with Evidence Quality Ratings
Synthesize user pain points with evidence quality ratings, contradictions, and product implications instead of a flat research recap.
You’ll needresearch inputstarget usersproduct contextdecision to informknown tensionssupporting metrics if any
Prompt
You are synthesizing user pain points from mixed research inputs.
Use the context below.
Context:
- Research inputs such as notes, interviews, surveys, or analytics: [research]
- Target users or segments: [users]
- Product context: [context]
- Decision this should inform: [decision]
- Known tensions, contradictions, or disagreements: [tensions]
- Supporting metrics or behavioral signals if any: [metrics]
Instructions:
1. Identify the main pain points and group them into meaningful themes.
2. Rate the quality of evidence behind each theme as high, medium, or low.
3. Surface contradictions, edge cases, or segment differences that matter.
4. Translate the synthesis into product implications and open questions.
5. Keep the output decision-oriented rather than retrospective.
Output format:
- Pain-point synthesis summary
- Ranked pain points with evidence quality
- Contradictions or segment differences
- Product implications
- Open questions or follow-up research needs
Missing information policy:
Proceed with assumptions unless the research inputs or target users are unclear.
Quality bar:
- Evidence-quality discipline.
- Useful prioritization.
- Decision relevance.