Before any product roadmap meeting, sprint planning session, or customer success review
You are a senior {{role}} brought in to help a professional complete a {{use_case}} task. # Context - Category: Research & Analysis - Use case: Analyse product feedback to surface themes and priorities - Source task: - I will paste a collection of user feedback : support tickets, NPS comments, app store reviews, survey responses, or interview notes. Analyse and produce: - Before analysing: check sample size and note if any segment (user type, plan, region) is over- or under-represented in the feedback. - 1. Top 5 themes by frequency : with representative quotes for each. - 2. Sentiment breakdown : what proportion of feedback is positive, negative, and mixed per theme. - 3. High-impact low-frequency issues : problems mentioned rarely but with high severity signals. - 4. What users love most : features or experiences that generate the strongest positive sentiment. - 5. The single most common reason a user would leave or recommend us : based on what the data shows. - 6. Prioritisation recommendation : rank the top 3 issues by: frequency × severity × ease of fix. - Feedback: {{paste_all_feedback_data}}. # Goal A theme analysis with sentiment breakdown, severity flags, and a prioritisation matrix for the top 3 issues # Constraints - Think like an expert advisor before writing the final output. - Ask clarifying questions only if the missing information would materially change the result. - Avoid generic filler, vague advice, and corporate-sounding language. - Make the output specific, practical, and ready to use. # Output A theme analysis with sentiment breakdown, severity flags, and a prioritisation matrix for the top 3 issues
{{double-curly}} with your real context.Before any product roadmap meeting, sprint planning session, or customer success review
High-impact low-frequency issues (step 3) are where most product teams lose customers silently. A problem mentioned by 5% of users with high severity language often affects a much larger silent majority.
Build a complete weekly plan. Time-block every day, protect deep work hours, and ensure the top 3 priorities get the best time slots.
Break this project into a full execution plan with milestones, tasks, owners, and deadlines.
Design a complete meeting agenda with time allocations, facilitation notes, and a clear decision or action framework.
Build a complete goal achievement framework using proven goal-setting principles (SMART, OKR, or milestone-based as appropriate). Include the goal, the plan, the tracking method, and accountability st