prompt guide · product research workflow
Market research
Competitive landscape
Trend scan
Interview & survey plan
Evidence synthesis
Research report
Stakeholder review
User segments
Personas
Developed by Jad · AI Tooltip
Start here
1. Create one Claude Project for this product initiative.
2. Add the product brief, existing research, analytics notes, strategy, constraints, and relevant customer material to Project knowledge.
3. Paste the instruction block below into Set project instructions.
4. Use a fresh chat for each workflow. After review, save the approved output back to Project knowledge.
5. Turn on Web Search or Research when the task depends on current market facts, competitors, regulations, or trends.
✦
You are my product research partner. Work from Project knowledge first, then use current reputable sources when Web Search or Research is enabled.
Ground every important claim in evidence. Cite sources inline. Include source dates. Label estimates, assumptions, contradictions, and gaps explicitly. Never invent statistics, quotes, respondents, competitors, or citations.
Keep evidence, interpretation, and recommendation separate. Explain how each insight could affect product decisions without presenting inference as fact.
Protect participant privacy. Remove unnecessary personal information and flag sensitive material before using it.
Create concise, decision-ready outputs. When requested, produce a downloadable document or PDF. Use an HTML Artifact only when interaction, filtering, or charts materially improve the result.
Ask only the questions that are necessary to avoid a misleading result. End with a short verification checklist and unresolved questions.
Workflow index
Run the workflows in order when you are starting from zero, or jump to the task you need. Each output becomes input for the next stage only after you review and approve it.
01
Market research
Size the space and map the evidence.
02
Competitive landscape
Compare verified alternatives and positioning.
03
Trend scan
Find changes that could reshape the product.
04
Interview and survey plan
Turn unknowns into research questions.
05
Evidence synthesis
Analyze transcripts and survey results.
06
Research report
Unify findings into decisions and next steps.
07
Stakeholder review
Prepare the meeting, objections, and deck.
08
User segments
Define evidence-backed behavioral groups.
09
Personas
Humanize segments without inventing facts.
1
Workflow 01
Establish the size, structure, momentum, and uncertainty of the market before you decide what to build.
Add to Project knowledge first
• Product or service brief, target customer, geography, and time horizon.
• Existing business assumptions, constraints, and any internal market data.
Starter prompt
✦
Create a market research brief for [product or service] in [market and geography], current as of [date]. Use Web Search or Research and prioritize primary sources, official statistics, filings, and reputable industry research.
For every market-size or growth figure, state the source, publication date, geography, definition, currency, and forecast period. If reputable sources disagree, show the range and explain why instead of choosing one silently.
Cover market definition, customer groups, current size and projected growth, demand drivers, major players, emerging trends, barriers, regulatory factors, opportunities, threats, and implications for product design.
Separate verified evidence, interpretation, and recommendations. Create a decision-ready downloadable document or PDF with inline citations, a methodology note, and a source appendix. Do not invent a chart value that is not present in the evidence.
What you should get
A sourced market brief with ranges rather than false precision, dated claims, a clear methodology, and implications tied to product decisions.
Quality check
Verify that every number uses the same market definition. Check publication dates, geographic scope, currency, and whether a forecast comes from the cited source.
2
Workflow 02
Compare direct, indirect, and substitute solutions using current evidence rather than feature-list guesswork.
Add to Project knowledge first
• Approved market research brief.
• Your product brief, known competitors, and any sales or customer notes that mention alternatives.
Starter prompt
✦
Build a competitive landscape for [product] using the approved Project knowledge and current web research. Include direct competitors, indirect competitors, and meaningful substitutes. Explain the inclusion criteria.
For the most relevant competitors, compare target users, jobs served, core offer, positioning, pricing and packaging as of [date], differentiators, strengths, weaknesses, proof points, and recent strategic signals. Link every changing fact to a dated source.
Create a comparison matrix and a short profile for each competitor. Distinguish what the company claims from what independent evidence supports. Identify crowded areas, unmet needs, and risks without turning absence of evidence into a market gap.
End with product implications, questions that require customer validation, and a citation appendix. Create a downloadable document or PDF.
What you should get
A defensible competitor map, dated pricing evidence, concise profiles, a comparison matrix, and opportunity hypotheses ready for validation.
Quality check
Open the cited pricing and product pages. Confirm that each competitor serves the target segment and that the analysis includes substitutes, not only obvious direct rivals.
3
Workflow 03
Find technological, behavioral, regulatory, and sustainability changes that could materially affect the product.
Add to Project knowledge first
• Approved market and competitive reports.
• Product time horizon, markets, technologies, and regulatory exposure.
Starter prompt
✦
Create a trend scan for [industry or product category] with a horizon of [time period]. Use Project knowledge plus current Web Search or Research.
Cover technological shifts, changing customer behavior, business-model changes, regulation, accessibility expectations, privacy and security, sustainability, and relevant macroeconomic signals. Include only trends with evidence and a plausible link to this product.
For each trend, provide evidence, source date, maturity, confidence, likely time horizon, affected users, potential product impact, leading indicators to watch, and what would disconfirm the trend.
Prioritize the trends by impact and uncertainty. Separate observations from implications. Create a downloadable trend report with inline citations and a monitoring table.
What you should get
A prioritized trend portfolio with confidence levels, leading indicators, product implications, and a monitoring plan.
Quality check
Remove trend-shaped opinions that have no evidence. Make sure regulatory claims apply to the right geography and distinguish enacted rules from proposals.
4
Workflow 04
Translate uncertain assumptions into a research plan that can generate evidence from real people.
Add to Project knowledge first
• Approved research reports and the product decisions currently at risk.
• Target participants, recruitment limits, timeline, method, and ethical or privacy constraints.
Starter prompt
✦
Design a research plan for [product decision]. Start by listing the decisions we need to make, the assumptions behind them, and the evidence that would change those decisions.
Recommend interviews, a survey, or a mixed method based on the objective. Define participant criteria, sample rationale, recruitment screener, session structure, consent language, recording notes, and an analysis plan. Do not claim that a small qualitative sample represents the full market.
For interviews, write neutral, behavior-first questions that ask about recent real experiences before opinions. Include follow-up probes and avoid leading, double-barreled, hypothetical, and solution-selling questions.
For surveys, use clear response options, balanced scales, an Other option where useful, and open-text sparingly. Map every question to a research objective and flag questions that collect sensitive data.
What you should get
A method recommendation, participant plan, screener, consent checklist, interview guide and/or survey, plus a question-to-objective map and analysis plan.
Quality check
Pilot the guide with one person. Remove leading language, unnecessary demographics, and questions that cannot influence a product decision.
5
Workflow 05
Turn raw transcripts and responses into traceable findings without flattening disagreement or inventing consensus.
Add to Project knowledge first
• Anonymized transcripts, notes, and survey export.
• Research objectives, participant metadata that is safe to use, and the discussion guide or questionnaire.
Starter prompt
✦
Analyze the attached research material against the stated objectives. First inventory the files, participants, missing data, and any quality limitations. Do not infer facts that participants did not state.
For qualitative data, code observations, cluster themes, preserve contradictions, and attach every finding to participant evidence. Use short excerpts only when needed and remove identifying details. Report counts as counts, not percentages, when the sample is small.
For survey data, clean the dataset, state the valid response count for each question, separate skipped answers, summarize distributions, and compare segments only when the sample supports it. Do not imply statistical significance without a valid test and sufficient sample.
Deliver findings, supporting evidence, confidence, notable exceptions, open questions, and product implications. Create a downloadable report plus an appendix that maps findings back to source material.
What you should get
A traceable evidence report with themes, response summaries, contradictions, confidence levels, anonymized evidence, and unanswered questions.
Quality check
Spot-check several findings against the original transcript or row. Confirm that minority views were not erased and that quotes are accurate and anonymized.
6
Workflow 06
Combine market, competition, trends, and user evidence into one decision-oriented narrative.
Add to Project knowledge first
• Approved outputs from workflows 01–05.
• Current product strategy, constraints, roadmap questions, and known business goals.
Starter prompt
✦
Create a comprehensive product research report from the approved materials in Project knowledge. Treat earlier reports as sources, not unquestionable truth, and preserve their caveats.
Synthesize the strongest findings across market, competition, trends, interviews, and surveys. Show where sources agree, disagree, or answer different questions. Separate facts, participant evidence, interpretation, and recommendation.
Structure the report around decisions: key findings, user needs, opportunities, constraints, risks, product implications, evidence strength, and the next questions to answer. Trace each major conclusion back to its source report and original citation when available.
End with prioritized next steps using impact, confidence, effort, and reversibility. Create a concise downloadable document or PDF, followed by an evidence appendix and unresolved-questions list.
What you should get
A single research narrative that connects evidence to decisions, exposes uncertainty, and gives the team a prioritized next-step plan.
Quality check
Make sure no recommendation appears stronger than its evidence. Resolve duplicated or contradictory market figures before stakeholders see the report.
7
Workflow 07
Turn the research into a focused decision meeting instead of a dense report walkthrough.
Add to Project knowledge first
• Approved research synthesis report.
• Meeting objective, attendees, decision rights, time limit, known tensions, and presentation constraints.
Starter prompt
✦
Prepare a stakeholder review for [decision]. Use the approved research report and the known roles of the attendees. The meeting should lead to a documented decision, not just information sharing.
Create an agenda with time boxes, the decision to make, the evidence stakeholders need, the assumptions still open, and the explicit owner of each follow-up. Anticipate likely questions, objections, tradeoffs, and requests for more evidence.
Create a separate slide-by-slide presentation outline. For each slide include the purpose, headline, supporting evidence, suggested visual, speaker note, and the decision or reaction it should unlock. Keep the story concise and preserve uncertainty.
End with a decision log template covering decision, rationale, evidence, dissent, owner, due date, and what would trigger reconsideration.
What you should get
A time-boxed agenda, talking points, anticipated questions, a slide-by-slide deck outline, and a reusable decision log.
Quality check
Every slide should support the meeting decision. Remove ornamental data, confirm numbers against the source report, and assign a clear decision owner.
8
Workflow 08
Group people by meaningful needs and behaviors rather than convenient demographic stereotypes.
Add to Project knowledge first
• Approved interview and survey synthesis plus the research report.
• The product decision the segments must support and any market constraints.
Starter prompt
✦
Identify 3–5 candidate user segments for [product] from the approved evidence. Segment primarily by needs, behaviors, context, frequency, constraints, and desired outcomes. Use demographics only when the evidence shows they materially affect the product experience.
For each segment, provide a definition, qualifying signals, core job, needs, pain points, current alternatives, behaviors, constraints, evidence base, confidence, and product implications. Include disconfirming evidence and explain where segments overlap.
Do not estimate market percentages unless the project contains representative quantitative evidence. If it does not, label size as unknown and recommend how to measure it.
Finish with a comparison table, recommended priority, risks of using the segmentation, and the data required to validate or revise it.
What you should get
A behavioral segmentation with inclusion signals, supporting evidence, confidence, overlaps, product implications, and a validation plan.
Quality check
Remove unsupported percentages and stereotypes. Confirm each segment is distinct enough to change a product or research decision.
9
Workflow 09
Make the validated segments memorable while keeping every detail traceable to research.
Add to Project knowledge first
• Approved user segments and the evidence behind them.
• Product scenarios, tasks, journey context, and decisions the personas will support.
Starter prompt
✦
Create one evidence-based persona for each approved user segment. The persona is a communication tool, not a fictional biography.
Include the segment definition, context, goals, behaviors, constraints, pain points, current workarounds, triggers, success criteria, product expectations, accessibility or trust needs, and a realistic scenario. Use short anonymized quotes only when they come from the research.
For every section, mark whether it is directly observed, synthesized from multiple observations, or an assumption to validate. Do not invent a name, age, job, family detail, photo, quote, or preference unless it helps the team and is grounded in evidence; use a role label when a fictional name would imply false precision.
Create a downloadable persona pack plus a traceability appendix that links each important claim to its source segment and research evidence. End with the product decisions each persona can and cannot support.
What you should get
A persona pack that is relatable without pretending to know more than the research supports, plus a traceability appendix and usage guidance.
Quality check
Audit every detail for evidence. Delete decorative biography, stock-photo stereotypes, fabricated quotes, and traits that do not change a design decision.
Closing rule
The best version of this workflow gives designers more time for framing, interviewing, sense-making, ideation, and difficult decisions. Claude should only make the evidence easier to gather and communicate, humans should still make the decisions.
Explore more free guides
Developed by Jad · AI Tooltip