Customer interview synthesis into sharp product themes
Clusters research notes into recurring pains, evidence-backed insights, and product opportunities.
Workflow
Research
Model fit
Gemini 2.5 Pro
Author
PromptJoy Editorial
Author role
Editorial curation
Origin
PromptJoy curated launch library
Published
Apr 10, 2026
Copies the full prompt body so you can use it immediately in your model of choice.
Visible copy count on this device: 435
Current vote signal: +142
Sign in to save or vote on this curated prompt. Your state will stay on this device for your signed-in account while the shared library fills in.
What happens here
Copy keeps the prompt body exact and updates the visible count on this device. Save and vote also work on this curated prompt for signed-in users until the shared public library is live.
Live trust breakdown
Task clarity
+18 names the role the model should play
Input contract
+24 tells the user what inputs to provide
Output contract
+14 specifies how the answer should be organized
Guardrails
+22 includes explicit constraints
Safety
+12 does not request secrets or sensitive identifiers
Reusability
+12 separates context, output, and rules into readable blocks
Community signal
+24 strong positive vote ratio
Trust score
60
Vote signal
+142
Saves
119
Copies
435
Task clarity
Checks whether the prompt clearly names the role, task, and workflow it is meant to support.
Evidence
- +18 names the role the model should play
- +18 states the job the prompt is meant to do
- +14 title describes the use case rather than a generic label
- +10 has task-oriented tags
Improve
- No obvious improvement flagged.
Input contract
Checks whether the prompt tells the user what context, data, or materials to provide.
Evidence
- +24 tells the user what inputs to provide
- +12 uses bullets to separate input fields or context
Improve
- Ask for the goal, audience, or situation behind the request.
You are a senior product researcher. I will paste raw customer interview notes. Synthesize them into: - recurring pains and jobs to be done - exact customer language worth preserving - tensions or contradictory signals - opportunity areas ranked by evidence strength - follow-up questions for the next interview round Rules: - quote customer phrasing when it is memorable - separate strong evidence from weak inference - avoid vague summaries like "users want simplicity" unless supported by specifics