返回提示词目录第 1504 页

路线图方案对比与决策分析

帮助团队按统一容量和假设比较多套路线图,展示交付范围、结果变化、风险与资源边际价值。

完整提示词

<context>
You prepare a side-by-side comparison of alternative roadmaps so leaders can choose between budgets, headcount levels or priorities with the consequences in view. Leaders often approve a budget and only later learn what it bought. A useful comparison holds everything constant except the variable being decided, uses the same capacity maths for every scenario, and shows the differences in outcomes and risk rather than only in feature counts. Extra headcount is not instantly extra capacity: hiring takes months and new people need time to become productive, which shrinks the gain in the first half of the year. Cuts rarely remove only the bottom item; they often break dependencies, commitments and morale.
{{#context}}
Context: {{context}}
{{/context}}
</context>

<task>
Scenarios:

<scenarios>
{{scenarios}}
</scenarios>

Initiatives:

<initiatives>
{{initiatives}}
</initiatives>

1. State the shared assumptions every scenario uses: capacity per person or team, the reserve for support and maintenance, hiring lead time and ramp-up for added headcount, and the order of priority used to fill capacity.
2. For each scenario, fill capacity in priority order and list what is in, what is out, and what slips to a later period. Respect fixed dates and commitments first; if a scenario cannot meet one, flag it.
3. Translate each scenario into outcomes: which goals it moves, by roughly how much where the user gave targets, and what customers or the business would notice.
4. Show the differences explicitly: the items and outcomes that change between scenarios, and the marginal value of the extra money or people.
5. List risks per scenario: delivery, commitments broken, team morale or attrition, dependency breaks, and what happens if estimates are wrong by 30 percent.
6. Recommend one scenario with the reasons, or say the decision is a values call and name the trade-off. List what the decision-makers still need to answer.
</task>

<constraints>
- Use the same method and numbers for every scenario so the comparison is fair. Show the capacity arithmetic.
- Never invent sizes, revenue figures or targets; mark unknowns and how they affect the comparison.
- Do not make one scenario look better by optimistic assumptions applied only to it.
- Keep the recommendation separate from the comparison so readers can disagree with it.
{{> output/uncertainty}}
</constraints>

<output_format>
## Shared assumptions
Bullets.

## Scenarios side by side
Table: initiative | scenario A | scenario B | scenario C (in, out, slipped, with timing).

## What changes between them
Bullets: outcomes gained or lost, and the marginal value of the difference.

## Risks per scenario
Table: scenario | main risks | likelihood | what would show it early.

## Recommendation
Short paragraph with reasons.

## Questions for the decision
Numbered list.
</output_format>

可替换内容

  • {{#context}}
  • {{context}}
  • {{/context}}
  • {{scenarios}}
  • {{initiatives}}
  • {{> output/uncertainty}}

分类与标签

办公效率、路线图规划、方案比较、资源分配、团队决策

前往 AI 图片创作