Product Feature Prioritization Chain

validated business chain v1.0.0 cc-by-sa

Block ID: 4f4c3d0b-b499-441f-949d-e3775754c14d

Community-contributed block. PromptDNA makes no guarantee of output quality or fitness for purpose. User assumes all responsibility for use.

Template

Prioritize the product features in {feature_backlog} against the reality that you can build only a fraction of them. (1) Tie each candidate to a specific user problem and a business outcome, discarding features justified only by "a customer asked" or "competitors have it" — because a roadmap built from requests without a problem behind them accretes complexity that serves no strategy. (2) Distinguish who wants each feature: a loud minority, the segment you're targeting, or the customers you're losing — since building for the loudest voice rather than the strategic segment is a classic misallocation. (3) Estimate the value of solving each problem (reach × impact × your confidence in both) and the effort, honestly, and rank by value-per-effort rather than by absolute value, since a stream of cheap high-value wins usually beats one expensive bet. (4) Separate the features that move your current strategic objective from those that are merely nice, and protect capacity for the foundational and reliability work that no customer requests but everyone needs. (5) Check dependencies and sequencing, since some features unlock others. (6) State the prioritized set, what you're deferring and why, and the estimate (usually impact or confidence) most likely to be wrong — treating the explicit "not now" list as the real output, since a roadmap without cuts is a wish list.

Prioritize the product features in {feature_backlog} against the reality that you can build only a fraction of them. (1) Tie each candidate to a specific user problem and a business outcome, discarding features justified only by "a customer asked" or "competitors have it" — because a roadmap built from requests without a problem behind them accretes complexity that serves no strategy. (2) Distinguish who wants each feature: a loud minority, the segment you're targeting, or the customers you're losing — since building for the loudest voice rather than the strategic segment is a classic misallocation. (3) Estimate the value of solving each problem (reach × impact × your confidence in both) and the effort, honestly, and rank by value-per-effort rather than by absolute value, since a stream of cheap high-value wins usually beats one expensive bet. (4) Separate the features that move your current strategic objective from those that are merely nice, and protect capacity for the foundational and reliability work that no customer requests but everyone needs. (5) Check dependencies and sequencing, since some features unlock others. (6) State the prioritized set, what you're deferring and why, and the estimate (usually impact or confidence) most likely to be wrong — treating the explicit "not now" list as the real output, since a roadmap without cuts is a wish list.

Variables

Name	Type	Required	Trust level
feature_backlog		yes

product-managementroadmapfeature-prioritizationchain-of-thought

Ratings

0.0

Overall (0)

0.0

Accuracy

0.0

Consistency

0.0

Clarity

0.0

Efficiency

Benchmarks

Not yet self-validated against any benchmark. Automated, evaluative only - not a factor in whether this block was published.

Submitted by James P FounderMod via mcp · 2026-07-18