Product management
AuraScore 85/100

Empirical Research Synthesis and Product Taxonomy

Synthesize mixed-method product research and survey data into a structured problem taxonomy framework.

Use this template when transforming messy quantitative survey results and qualitative research transcripts into an actionable product taxonomy. It produces a structured analytical framework that isolates core user friction points.

Template

Role: Principal Product Insights Lead specializing in research synthesis and behavioral product modeling.

Context

  • Target user cohort: {{target_cohort}}
  • Research dataset: {{raw_survey_data}}
  • Empirical sample size: {{sample_size}}
  • Working assumptions: {{key_hypotheses}}
  • Statistical threshold: {{confidence_interval}}
  • Product environment: {{product_domain}}

Task

Synthesize empirical user data into a multi-tiered problem taxonomy and opportunity scoring framework that validates or refutes {{key_hypotheses}} within {{product_domain}}.

Method

  1. Group {{raw_survey_data}} into categorical response buckets based on recurring semantic clusters and behavioral events.
  2. Filter findings against {{confidence_interval}} to separate statistically significant trends from sample noise.
  3. Map frequency distributions against cohort attributes specified in {{target_cohort}}.
  4. Cross-reference observed behavioral friction points with each item in {{key_hypotheses}}.
  5. Construct a three-level problem taxonomy: Primary Need Category, Root Mechanism, and Manifested Friction.
  6. Compute an Opportunity Severity Score (OSS) for each taxonomy node combining prevalence, urgency, and user churn risk.
  7. Synthesize findings into actionable architectural requirements for product discovery.

Constraints

  • MUST evaluate every claim against {{confidence_interval}} and explicit sample thresholds.
  • MUST NOT treat anecdotal qualitative remarks as statistically validated unless supported by frequency data.
  • Taxonomy classifications must be mutually exclusive and collectively exhaustive (MECE).
  • Findings MUST explicitly declare whether each hypothesis in {{key_hypotheses}} is supported, inconclusive, or refuted.

Output format

  1. Research Synthesis Summary: Cohort profile, statistical boundaries, and key anomalies (max 200 words).
  2. Hypothesis Validation Ledger: Structured table listing hypothesis, empirical evidence, and status.
  3. Product Problem Taxonomy: Hierarchical tree structure (Levels 1-3) with Opportunity Severity Scores.
  4. Discovery Recommendations: Prioritized list of target problem spaces with quantitative rationale.

Self-review

  • Verify that the taxonomy nodes are strictly MECE and map back to {{raw_survey_data}}.
  • Confirm all hypothesis verdicts are backed by data meeting {{confidence_interval}}.
  • Ensure sample size context from {{sample_size}} is reflected in data reliability assertions.
AuraScore breakdown
85/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

business-strategy
business-product
complex-reasoning-analysis-math
product-management
research-synthesis
taxonomy