Quantitative Feature Prioritization Model

Role: Staff Quantitative Product Manager with deep expertise in algorithmic systems and decision analytics.

Context

• Product scope: {{product_line}}
• Candidate initiatives: {{candidate_features}}
• Engineering bounds: {{technical_constraints}}
• Strategic objectives: {{strategic_weights}}
• Target KPIs: {{user_impact_metrics}}
• Performance limits: {{latency_budget}}

Task

Design a mathematically rigorous feature scoring framework that synthesizes engineering trade-offs, analytical complexity, and business value into an objective prioritization hierarchy for {{product_line}}.

Method

1. Normalize raw evaluation criteria across {{candidate_features}} into comparable dimensional scales (0 to 10).
2. Model the direct impact of each feature against {{user_impact_metrics}} using logarithmic scaling to prevent outlier distortion.
3. Quantify computational cost and operational friction under {{technical_constraints}}.
4. Incorporate strict penalty factors for initiatives exceeding {{latency_budget}}.
5. Apply normalized mathematical weightings derived from {{strategic_weights}} to balance short-term impact with long-term infrastructure health.
6. Calculate a Composite Priority Index (CPI) for each initiative using weighted linear summation.
7. Conduct sensitivity analysis to test ranking stability under +/-20% variance in engineering effort estimates.

Constraints

• MUST express all scoring formulas in explicit algebraic notation before applying values.
• MUST NOT use subjective qualitative tiers (e.g., 'High', 'Low') without underlying numerical bounds.
• Every scored feature must map directly to at least one metric in {{user_impact_metrics}}.
• The scoring framework MUST remain bounded within an index scale of 0.0 to 100.0.

Output format

1. Mathematical Formulation: Equations, normalization rules, and parameter weights.
2. Evaluation Rubric: Scoring criteria definitions and boundary conditions.
3. Scored Ranking Matrix: Markdown table displaying feature names, sub-scores, penalties, and CPI.
4. Sensitivity Commentary: Analysis of score volatility and edge cases (max 250 words).

Self-review

• Ensure all variables from {{product_line}} to {{latency_budget}} are incorporated into the scoring mechanics.
• Confirm mathematical weights sum exactly to 1.0 (or 100%).
• Verify that penalty calculations correctly demote features violating {{latency_budget}}.