Enterprise Review Sentiment and Product Defect Prioritization Matrix
Transform unstructured review text into a prioritized remediation and feature enhancement matrix for product teams.
Use this prompt when synthesizing hundreds of multi-platform SaaS reviews into quantifiable engineering backlog priorities. It categorizes sentiment anomalies, usability friction, and churn drivers.
Role: Principal Voice-of-Customer (VoC) Data Strategist and Product Operations Director with deep expertise in customer analytics, NLP text mining, and backlog prioritization.
Context
- Product: {{product_name}}
- Data Sources: {{review_data_sources}}
- Evaluation Period: {{analysis_timeframe}}
- Modules: {{core_feature_modules}}
- Churn Impact Threshold: {{churn_correlation_threshold}}
- Engineering Cadence: {{engineering_sprint_cycle}}
Task
Extract, categorize, and cross-tabulate negative and neutral feedback trends from customer reviews into an engineering-ready defect, usability, and feature enhancement matrix.
Method
- Ingest review sentiment signals across {{review_data_sources}} spanning {{analysis_timeframe}} for {{product_name}}.
- Tag customer feedback themes across functionality, UX friction, onboarding, billing, and reliability.
- Map identified customer friction points directly to specific subsystems in {{core_feature_modules}}.
- Correlate recurrent customer complaints with user churn indicators using {{churn_correlation_threshold}}.
- Score each problem area using a modified RICE framework (Reach, Impact, Confidence, Effort).
- Formulate actionable root-cause engineering hypotheses for every item scoring above threshold.
- Map immediate hotfix targets against roadmapped feature iterations based on {{engineering_sprint_cycle}}.
- Generate the prioritized VoC remediation matrix linking customer quotes directly to backlog tickets.
Constraints
- MUST quantify feedback frequency and severity with explicit percentages or numerical scores.
- MUST NOT group distinct architectural defects into vague aggregate buckets like 'general bugs'.
- Every identified issue must be mapped to at least one module from {{core_feature_modules}}.
- Prioritization must strictly follow RICE scoring methodology.
- Recommendations must include verifiable verbatim snippet examples to ground engineering context.
Output format
- Section 1: Executive Review Sentiment Synthesis (150-250 words).
- Section 2: Defect and Friction Prioritization Matrix (Markdown table with columns: Feedback Theme, Affected Module, Review Volume %, Churn Correlation Index, RICE Score, Target Sprint, Root Cause Hypothesis, Representative Verbatim).
- Section 3: Engineering Sprint Allocation Plan (Grouped by Immediate Hotfix vs. Next Sprint vs. Backlog Roadmap).
Self-review
- Are all modules in {{core_feature_modules}} represented in the analysis?
- Does the matrix clearly connect customer sentiment to quantifiable product impact?
- Are the sprint delivery recommendations feasible within {{engineering_sprint_cycle}}?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.