prioritize-features

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Prioritize Feature Backlog

功能待办事项优先级排序

Evaluate and rank a backlog of feature ideas to identify the top 5 to pursue.

评估并对功能创意待办事项进行排名，确定值得推进的Top5创意。

Context

背景信息

You are helping prioritize features for $ARGUMENTS.

If the user provides files (spreadsheets, backlogs, opportunity assessments), read and analyze them directly.

你正在为**$ARGUMENTS**协助进行功能优先级排序。

如果用户提供了文件（电子表格、待办事项列表、机会评估文档），请直接读取并分析。

Domain Context

领域背景

For framework selection guidance, see the

prioritization-frameworks

skill. Key recommendations:

Opportunity Score (Dan Olsen, The Lean Product Playbook) is recommended for evaluating customer problems: Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1. High Importance + low Satisfaction = best opportunities. Prioritize problems (opportunities), not solutions.

ICE is recommended for quick scoring of initiatives: Impact (Opportunity Score × # Customers) × Confidence × Ease. RICE adds Reach as a separate factor for larger teams.

关于框架选择指南，请查看

prioritization-frameworks

技能。核心推荐：

机会评分（Dan Olsen，《精益产品实战》）推荐用于评估客户问题：机会评分 = 重要性 × (1 − 满意度)，归一化至0–1区间。高重要性+低满意度=最佳机会。优先关注问题（机会），而非解决方案。

ICE模型推荐用于快速为举措评分：影响力（机会评分 × 客户数量）× 信心度 × 易用性。RICE模型则为大型团队额外增加了覆盖范围作为独立因素。

Instructions

操作步骤

The user will describe their product objective, desired outcomes, and provide feature ideas. Work through these steps:

Understand priorities: Confirm the product objective and success metrics.
Evaluate each feature against:
- Impact: How much does it move the needle on desired outcomes? Consider Opportunity Score if customer data is available.
- Effort: How much development, design, and coordination is required?
- Risk: How much uncertainty exists? What assumptions need testing?
- Strategic alignment: How well does it fit the product vision and current goals?
Recommend the top 5 features with:
- Clear ranking (1-5)
- Brief rationale for each selection
- Key trade-offs considered
- What was deprioritized and why
Present as a prioritization table if helpful.

Think step by step. Save as markdown if the output is substantial.

用户会描述其产品目标、期望成果，并提供功能创意。请按照以下步骤操作：

明确优先级基准：确认产品目标和成功指标。
评估每个功能，从以下维度出发：
- 影响力：对期望成果的推动程度有多大？如果有客户数据，可参考机会评分。
- 工作量：需要多少开发、设计和协调工作？
- 风险：存在多少不确定性？需要验证哪些假设？
- 战略契合度：与产品愿景和当前目标的匹配程度如何？
推荐Top5功能，需包含：
- 明确的排名（1-5）
- 每个入选功能的简短理由
- 考虑到的核心权衡因素
- 被降级优先级的功能及其原因
如有帮助，可整理为优先级排序表格。

请逐步思考。如果输出内容较多，请保存为markdown格式。