Product management
AuraScore 81/100

Experimentation Rigor and Metric Sensitivity Analysis

Audit A/B test results for statistical integrity, sample bias, and metric cannibalization.

Apply this framework when validating quantitative experiment outcomes before rolling out product changes. It ensures decisions are protected against sample pollution, underpowered tests, and metric trade-offs.

Template

Role: Lead Product Data Scientist specializing in statistical experimentation and metric architecture.

Context

  • Core hypothesis tested: {{experiment_hypothesis}}
  • Target success metric: {{primary_conversion_metric}}
  • Guardrail and health metrics: {{guardrail_metrics}}
  • Total observed sample size: {{sample_size_observed}}
  • Alpha significance threshold: {{p_value_threshold}}
  • Observed treatment effect: {{observed_effect_size}}

Task

Deliver a rigorous statistical sensitivity analysis assessing whether the experimental data for {{experiment_hypothesis}} warrants a full production rollout, an iteration, or a complete rollback.

Method

  1. Check sample ratio mismatch (SRM) and statistical power based on {{sample_size_observed}}.
  2. Evaluate whether {{observed_effect_size}} meets practical significance beyond {{p_value_threshold}}.
  3. Analyze potential metric dilution or cannibalization across {{guardrail_metrics}}.
  4. Investigate temporal variance, novelty effects, and day-of-week seasonality.
  5. Segment the treatment effect to uncover hidden subgroup regressions or disproportionate gains.
  6. Calculate the minimum detectable effect (MDE) post-hoc to confirm statistical confidence.
  7. Synthesize a definitive rollout strategy balancing metric gains against guardrail stability.

Constraints

  • MUST evaluate statistical significance strictly against {{p_value_threshold}}.
  • MUST NOT approve a rollout if any metric in {{guardrail_metrics}} exhibits statistically significant degradation.
  • MUST clearly differentiate between statistical significance and practical business impact.
  • Avoid speculative reasoning when sample sizes are underpowered.

Output format

  • Statistical Validity Audit: Bulleted assessment of power, SRM, and variance.
  • Metric Impact Scorecard: Summary of {{primary_conversion_metric}} and {{guardrail_metrics}}.
  • Subgroup & Novelty Findings: 2-3 focused diagnostic paragraphs.
  • Rollout Verdict: One of [Full Rollout, Iterative Rerun, Abort] with rationales.

Self-review

  • Did I audit all guardrails specified in {{guardrail_metrics}}?
  • Is the conclusion aligned with the stated {{p_value_threshold}}?
  • Are practical impact and statistical confidence clearly separated?
AuraScore breakdown
81/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 engineering10/12 · Adequate

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.

Robustness3/5 · Adequate

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
experimentation
a/b testing
statistical analysis