返回提示词目录第 1408 页

工程工期估算沟通稿撰写

将工程估算转为面向相关方的简明说明,交代区间、未知项与范围取舍,并准备质疑回应。

完整提示词

<context>
Estimates go wrong in conversation more than in calculation. A range gets heard as its low end, a single number is treated as a promise, "six weeks" is compared with "it's just a button", and an engineer under pressure trims the estimate instead of trimming scope. Explaining an estimate well means stating the range and what confidence it carries, showing where the time actually goes (often integration, testing, migration and review, not the visible feature), naming the unknowns that drive the upper end and when they will be resolved, and offering real levers: smaller scope, a phased release, more certainty after a spike, or accepting more risk. The estimate itself should not change because someone is unhappy with it.
</context>

<task>
Write an explanation of this estimate for a {{audience}}.

<estimate>
{{estimate}}
</estimate>
{{#stakeholder_question}}
They asked: {{stakeholder_question}}
{{/stakeholder_question}}

1. Answer their question directly in the first two sentences, with the range and a plain statement of confidence.
2. Explain where the time goes in three to five plain bullets, including the invisible work, using only the breakdown in the input.
3. Name the unknowns that drive the upper end and when or how each will be resolved.
4. State the assumptions (people, priorities, dependencies on other teams) and what happens to the range if they change.
5. Offer two or three levers with their effect: cut or defer scope, phase the release, run a short spike to narrow the range, or accept specific risks. Say what each gives up.
6. Draft short talking points for likely pushback ("can't you just...", "the other team did it in two weeks").
</task>

<constraints>
- Never shrink the estimate to please the audience; change scope, not the number. If the input's range seems inconsistent with its breakdown, flag it in Gaps.
- Do not invent work items, dates or team capacity.
- No jargon; the message is under about 250 words.
</constraints>

<output_format>
## Message
Ready to send.

## Talking points for pushback
| They say | You say |

## Gaps
Bullets, or "None".
</output_format>

可替换内容

  • {{audience}}
  • {{estimate}}
  • {{#stakeholder_question}}
  • {{stakeholder_question}}
  • {{/stakeholder_question}}

分类与标签

办公效率、工期估算、项目沟通、范围管理、异议回应

前往 AI 图片创作