更新邮件翻车是因为写得像日记。读者只扫一眼。好的更新先写状态色（绿 / 黄 / 红）、一句话讲变化、写明 ask（如果有）。下面 15 个模板覆盖每种更新：周报、blocker、延期、里程碑、exec rollup，以及没人教过你怎么写的那些。（如果更新形式变成现场讲，切到10 页工作汇报大纲，把同样的”一条主线”放到 slide 里。）
适合哪些场景
PM、工程 lead、运营经理、创业者、客户经理——任何需要给组织架构上比自己高、只有 30 秒的人发更新的人。
什么时候不建议这样写 Prompt
真正的危机不要用邮件（先打电话 / Slack；邮件是回执）；HR / 敏感沟通也别全交给 AI——语气需要真人来定。
Prompt 结构公式
Stakeholder 更新 Prompt 一定要带这六个要素：
- 角色：让 AI 扮演谁（PM、chief of staff、运营、财务分析、经理）。
- 上下文：公司 / 团队 / 项目 / 受众 / 之前发生了什么。
- 目标：一个具体可交付物——memo、邮件、talking points、表格、优先级清单。
- 限制：不能做什么（别有营销腔、别超出事实推断、别写 PII、控制字数）。
- 输出格式：编号小节、markdown 表格、Slack 友好的 bullet，或 1 页 memo。
- 示例 / 信号：1-2 行”好语气”示例，或一个可模仿的过往样本。
这套 Prompt 适合用在哪
- 给指导委员会的周项目状态
- Blocker 升级——要决策或要解锁
- 里程碑——庆祝但不空洞
- 延期——主动认账，写明新日期 + 补救
- 跨职能更新——不同受众不同剪辑
15 个可直接复制的 Prompt 模板
1. 周报——绿 / 黄 / 红
默认模板。只学一个就学这个。
You are writing a weekly stakeholder update email. Below are my raw notes. Output an email with: (1) Subject line "{project} week {N} — {color}", (2) One-line status with green/yellow/red, (3) What shipped this week (≤4 bullets), (4) What is next week (≤3 bullets), (5) Risks / asks (≤2 bullets, ask must be specific — what / who / by when), (6) No closing fluff. Hard ceiling: 200 words.
Notes:
{paste}可替换变量： project —— 项目名, N —— 周数, paste —— 原始周笔记
优化建议： 输出太飘加一句：“Drop adjectives. State facts. The reader is a skeptical VP.”
2. Blocker 升级邮件
Write a blocker escalation email to {VP role}. Structure: (1) Subject: "Blocker on {project} — needs your call by {date}", (2) Two-sentence summary: what is blocked and what we need, (3) What we tried (3 bullets — name people and dates), (4) The specific ask (decision / resources / air cover), (5) Cost of inaction. ≤150 words. No apologies for emailing.
{paste}可替换变量： VP role —— 收件人 title, project —— 项目名, date —— 截止, paste —— blocker 背景
3. 里程碑公告
Write a milestone-hit email that celebrates without sounding like marketing. Structure: (1) Subject: "{milestone} shipped {date}", (2) What we shipped (one sentence with the user-visible thing), (3) Why it mattered (one sentence — the business outcome), (4) Who did the work (named contributors — at least 3 names), (5) What is next. Tone: confident, specific, no exclamation marks.
Notes: {paste}4. 延期邮件（主动认账）
最难写的一种。别藏。
We have slipped a committed date. Write the email that owns it. Structure: (1) Subject: "Update on {project} — date moved to {new date}", (2) The new date, in the lede, (3) Why we slipped (specific, not "complexity") — 2 bullets, (4) What we are doing differently (the mitigation, not a promise to "do better"), (5) Confidence in the new date (low / med / high) and what would still threaten it, (6) Apology — one sentence, not a paragraph.
Context: {paste}5. Exec rollup（5 个项目 → 1 封邮件）
Below are status notes for {N} projects. Write a single exec rollup email. For each project: 1 row in a table — Project | Status (G/Y/R) | This week | Next week | Risk. After the table, one paragraph: "Where I need your help this week" (≤3 specific asks with names). Total ≤300 words.
Notes:
{paste}6. 跨团队求助邮件
Write an email asking {other team} to do {ask}. Structure: (1) Subject names the ask, not the project, (2) Context in 2 sentences, (3) What we need — specific deliverable + by when, (4) Why this helps THEIR goals (not ours), (5) What we are doing on our side to make their work easier. No "as discussed" framing.
Context: {paste}可替换变量： other team —— 团队名, ask —— 具体交付物
7. 指导委员会月度
Write a monthly steering-committee email. Structure: (1) One paragraph: business outcome the project drives, (2) Status by workstream (table: workstream | progress % | risk), (3) Decisions needed from the committee this month (numbered, with options + recommendation), (4) Decisions FYI from last month (one line each). Skip the project history — they were there.
{paste}8. 围绕一张图的更新
Write a status email that revolves around one chart. Structure: (1) Subject: a one-sentence takeaway from the chart, (2) The chart description (one paragraph — what it shows + period), (3) Three implications for the reader, (4) What we are doing because of it, (5) One question for the reader. Pretend the chart is attached — refer to it as Figure 1.
Chart description: {paste}9. “本周无更新”的更新
没变化但还是欠一封信。
Nothing materially changed this week, but I owe a status. Write a 100-word email that: (1) Says explicitly "no material change", (2) Lists what is in flight (≤3 items, no padding), (3) Names the next milestone + date, (4) Asks if anyone needs deeper detail. Do NOT manufacture content to look busy.
{paste}10. 多受众邮件（同一封、两种剪辑）
Same update, two audiences: engineers + execs. Write the email with a top "TL;DR for execs" (3 bullets, business framing) and a "Details for engineers" section (technical specifics). Same facts, different abstraction. Subject line works for both.
Notes: {paste}11. 以客户影响为视角
Write an update that frames the work via customer impact. Structure: (1) Customer outcome (one sentence — what is now possible / faster / cheaper), (2) How we measured it (the metric), (3) What we shipped this week to get there, (4) What is next, (5) Quote from a customer or internal user if I provide one (paste below).
Notes + quote: {paste}12. 寻求 buy-in 的邮件
决策前，不是状态。要 sign-off。
Write an email seeking buy-in for {proposal}. Structure: (1) Subject names the proposal, not "FYI", (2) One-paragraph proposal, (3) Why now, (4) Three concerns I anticipated + my answer to each, (5) Explicit ask: "Please reply by {date} with yes / no / questions." Avoid the trap of burying the ask.
{paste}可替换变量： proposal —— 要 buy-in 的提案, date —— 回复截止
13. 投资人月报（创始人口吻）
Write a monthly investor update in founder voice (clear, specific, no hype). Structure: (1) TL;DR (3 lines), (2) Metrics block (table: metric | this month | last month | trend), (3) Wins (3 bullets, specific), (4) Challenges (3 bullets, no excuses), (5) Asks (intros, hires, advice — name them), (6) What I am personally focused on for next 4 weeks.
Raw notes: {paste}14. 重新激活沉默 stakeholder
A stakeholder has gone quiet for {weeks}. Write a re-engagement email that does NOT guilt-trip them. Structure: (1) One-sentence summary of where things stand, (2) Two specific moments where their input would help, (3) Offer of a 15-min sync or async write-up (let them pick), (4) Confirm the small action you will take regardless. No "circling back".
Context: {paste}可替换变量： weeks —— 沉默多久
15. 季度收尾邮件
Write an end-of-quarter wrap email. Structure: (1) What we committed at quarter start, (2) What shipped vs what slipped (table), (3) What we learned (3 bullets, real lessons not platitudes), (4) Quarter-over-quarter delta on key metrics, (5) Top 3 priorities next quarter + why we ranked them this way. Keep under 400 words.
Notes: {paste}容易踩的坑
- 状态色（G/Y/R）埋在下方——读者不会下滚。
- 模糊 ask（“欢迎想法”）——拿到模糊回复（沉默）。
- 延期用被动语态（“日期被调整”）——读者一眼看穿。
- 吹捧型 wins（“颠覆性""行业领先”）——信誉税。
- 一封邮件两类受众但不分剪辑——两边都没拿到自己要的。
- 主题没动作——“Update” 不是主题。
- 同一组人一周内发多次更新——疲劳后忽略。
优化技巧
- 开头写状态色和 ask，不要写回顾。回顾是第 3 段。
- 每周用同样的主题格式——读者能稳定过滤 / 归档。
- wins 和 asks 都要点名——“团队”是占位符不是 credit。
- 周更直接把 Slack / 笔记原文丢给 AI，不要自己先写”初稿”——会改两遍。
- 延期邮件要在延期变明显之前发。晚通知的成本 > 早通知的丑陋。
- 建一个”语气库”——3 封过去的更新放进 Prompt 当例子让 AI 模仿。
- 发出前重读一遍：“如果只有 10 秒，读者会带走什么？” 不清楚就重写开头。
FAQ
- Stakeholder 更新应该多长？: 周报 150-250 字。月报 300-400。季度收尾 400-600。再长就该是文档 + 邮件作封面信。
- 用 bullet 还是段落？: 需要扫读的（状态、wins、asks）用 bullet。需要语境或致歉的用段落。混合是为了好扫。
- AI 写整封还是写草稿？: 写草稿——尤其延期 / blocker，AI 会软化事实。开头一定自己重写一遍，读者分得出。
- emoji 和感叹号？: 少用。主题里一个绿 / 黄 / 红点可以。wins 别用感叹号——事实比热情更有力。
- 怎么知道更新有效？: 两个信号：(1) 收到具体问题的回复（说明被读了），(2) ask 真的有人回应。Asks 全沉默说明没扫到那。
- 回复前先让 AI 总结线程吗？: 可以，但要喂：(a) 线程；(b) 你的目标；(c) 受众。发出前核对名字和数字。