feature-decision

Feature prioritization uses an impact-effort framework to evaluate strategic fit, consult stakeholders for alignment, and generate a markdown decision log documenting the rationale, evidence, and next steps for future reference.

A product decision log is a durable markdown record capturing the rationale, evidence, and next steps for a feature prioritization choice. You need one during roadmap trade-off reviews and stakeholder consultations to prevent context loss.

Evaluating a new feature request requires assessing it against customer intel and roadmap context, performing an impact-effort analysis, checking strategic alignment, and deciding whether to do it now, defer it, or say no.

Yes, the feature decision process requires stakeholder alignment checks. It explicitly prompts you to consult engineering, design, sales, and leadership during evaluation to ensure the final feature prioritization recommendation is viable.

The best way to structure roadmap trade-off reviews is to apply an impact-effort framework, validate choices against customer intel and strategic alignment, and document the outcome in a markdown decision record.