Back to Details

pm-weekly-review

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

PM Weekly Review Skill

PM每周回顾技能

Turn the chaotic end-of-week brain dump into a structured 20-minute ritual that keeps you, your team, and your stakeholders aligned — without a meeting.
将混乱的周末头脑风暴转化为一套结构化的20分钟流程，无需开会就能让你、你的团队和利益相关者保持目标一致。

The Weekly Review Structure (20 minutes)

每周回顾流程（20分钟）

5 min — Metrics check: What moved? What didn't? What's surprising? 5 min — Ship progress: What shipped? What slipped? What's blocked? 5 min — Insights: Any customer feedback, support tickets, or research findings? 5 min — Next week priorities: What are the 3 things that matter most?
5分钟——指标核查： 哪些指标有变动？哪些没有？哪些情况出乎意料？ 5分钟——交付进度： 完成了哪些交付？哪些延期了？哪些被阻塞了？ 5分钟——洞察发现： 有没有收到客户反馈、支持工单或研究成果？ 5分钟——下周优先级： 最重要的3件事是什么？

Output Format

输出格式

PM Weekly Review — Week of [Date]

PM每周回顾——[日期]周

Product Area: [What you own] Written by: [PM Name] Time to read: ~3 minutes
负责产品领域： [你负责的业务范围] 撰写人： [PM姓名] 阅读时长： ~3分钟

📊 Metrics This Week

📊 本周指标

MetricThis WeekLast WeekTargetTrend
[Primary metric][Value][Value][Target]↑ / ↓ / →
[Secondary metric][Value][Value][Target]↑ / ↓ / →
[Health metric][Value][Value][Target]↑ / ↓ / →
Notable movement:
  • [What changed and why — 1 sentence each]
Concern to watch:
  • [Anything trending in the wrong direction]
指标本周数值上周数值目标值趋势
[核心指标][数值][数值][目标值]↑ / ↓ / →
[次要指标][数值][数值][目标值]↑ / ↓ / →
[健康度指标][数值][数值][目标值]↑ / ↓ / →
值得关注的变动：
  • [变动内容及原因——每条1句话]
需留意的问题：
  • [任何呈反向趋势的情况]

🚢 This Week's Progress

🚢 本周进展

Shipped:
  • ✅ [What went live] — [1-line impact or observation]
In Progress:
  • 🔄 [Feature/initiative] — [% complete or current status]
Slipped / Blocked:
  • ⚠️ [What didn't happen] — Reason: [brief] — Action: [who's unblocking it]
Carry-forward to next week:
  • [Item + why it's carrying over]
已交付：
  • ✅ [已上线内容] — [1句话说明影响或观察结果]
进行中：
  • 🔄 [功能/项目] — [完成百分比或当前状态]
延期/阻塞：
  • ⚠️ [未完成事项] — 原因：[简要说明] — 行动：[负责解决阻塞的人员]
顺延至下周：
  • [事项 + 顺延原因]

💡 Insights & Signals

💡 洞察与信号

Customer feedback:
  • "[Quote or paraphrase]" — Source: [user/channel] — Theme: [tag]
Support signals:
  • [Top ticket category this week + volume]
  • [Anything that signals a product gap]
Research / data:
  • [Any discovery from user interviews, analytics, or experiments]
客户反馈：
  • "[引用或转述内容]" — 来源：[用户/渠道] — 主题：[标签]
支持信号：
  • [本周最高频工单类别 + 数量]
  • [任何显示产品缺口的信号]
研究/数据：
  • [来自用户访谈、数据分析或实验的发现]

🎯 Next Week — Top 3 Priorities

🎯 下周——三大优先事项

#PriorityWhy This WeekOwnerDone =
1[Most important thing][Reason it can't wait][Name][Clear definition of done]
2[Second priority][Why][Name][Done criteria]
3[Third priority][Why][Name][Done criteria]
Decisions needed:
  • [Any decision that's blocking progress — who needs to make it]
Asks / dependencies:
  • [What you need from engineering / design / data / leadership]
序号优先事项本周优先级原因负责人完成标准
1[最重要事项][无法延后的原因][姓名][明确的完成定义]
2[第二优先事项][原因][姓名][完成标准]
3[第三优先事项][原因][姓名][完成标准]
待决策事项：
  • [任何阻碍进展的决策——需由谁做出]
请求/依赖：
  • [你需要从工程/设计/数据/领导层获得的支持]

🧠 Reflection (Optional but powerful)

🧠 反思（可选但作用显著）

What's one thing from this week I'd do differently? [Your honest answer — 1–2 sentences]
What's the biggest unknown I'm carrying into next week? [Name the uncertainty explicitly]
本周有一件事我会换种方式处理，是什么？ [你的坦诚回答——1-2句话]
我带入下周的最大未知是什么？ [明确说出不确定性]

Required Inputs

必填输入信息

Ask the user for these if not provided:
  • Product area or team you own
  • Key metrics this week (with values and prior week comparison)
  • What shipped, slipped, or is blocked
  • Top 3 priorities for next week
  • Any customer insights or signals (optional)
若用户未提供以下信息，请主动询问：
  • 你负责的产品领域或团队
  • 本周核心指标（含数值及与上周的对比）
  • 已交付、延期或阻塞的事项
  • 下周三大优先事项
  • 任何客户洞察或信号（可选）

Quality Checks

质量检查清单

  • Metrics include period-over-period comparison (not just raw numbers)
  • Every blocked item has an owner and a specific unblocking action
  • Next week's priorities have a "why this week" rationale
  • Total length is under 400 words (skimmable in 3 minutes)
  • Reflection section is honest, not aspirational
  • 指标包含同期对比（而非仅原始数值）
  • 每个阻塞事项都有负责人和具体的解决行动
  • 下周优先事项包含“本周优先级原因”的说明
  • 总字数控制在400字以内（3分钟可快速浏览）
  • 反思部分内容坦诚，而非空泛的目标

Guidelines

指导原则

  • Keep the whole document under 400 words — if stakeholders won't read it, it doesn't exist
  • The reflection section is for you, not your stakeholders — keep it honest
  • Always name a clear owner for every blocked item — "the team will figure it out" is a blocker in disguise
  • Recommend sending this by end of Friday — Monday morning is too late to course-correct
  • If three weeks of weekly reviews show the same blocked item, escalate immediately
  • 整篇文档控制在400字以内——如果利益相关者不会读，那它就毫无意义
  • 反思部分是为你自己准备的，而非给利益相关者看的——请保持坦诚
  • 每个阻塞事项都要明确指定负责人——“团队会解决”本质上就是一种阻塞
  • 建议在周五下班前发送这份文档——周一早上发送太晚，无法及时调整方向
  • 如果连续三周的每周回顾都显示同一个阻塞事项，请立即升级处理