internal-comms-3p-updates
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseInstructions
说明
Write a 3P update. 3P updates stand for "Progress, Plans, Problems." The main audience is executives, leadership, and teammates. Keep updates succinct and to-the-point: 30-60 seconds reading time. Write for people with some context on what the team does, but not deep familiarity.
3Ps can cover a team of any size, ranging all the way up to the entire company. The bigger the team, the less granular the tasks should be. For example, "mobile team" might have "shipped feature" or "fixed bugs," whereas the company might have really meaty 3Ps, like "hired 20 new people" or "closed 10 new deals."
They represent the work of the team across a time period, almost always one week. They include three sections:
- Progress: what the team has accomplished over the next time period. Focus mainly on things shipped, milestones achieved, tasks created, etc.
- Plans: what the team plans to do over the next time period. Focus on what things are top-of-mind, really high priority, etc. for the team.
- Problems: anything that is slowing the team down. This could be things like too few people, bugs or blockers that are preventing the team from moving forward, some deal that fell through, etc.
Before writing, confirm the team name. If not specified, ask explicitly for the team name.
撰写一份3P更新。3P更新代表“进展（Progress）、计划（Plans）、问题（Problems）”。主要受众为高管、领导层及团队成员。更新内容需简洁明了，阅读时间控制在30-60秒。撰写时假设读者对团队业务有基本了解，但并非深入熟悉。
3P更新适用于任何规模的团队，小到小组，大到整个公司。团队规模越大，任务描述应越宏观。例如，“移动团队”的更新可以是“上线新功能”或“修复漏洞”，而公司层面的3P更新则应更具分量，比如“招聘20名新员工”或“达成10笔新交易”。
3P更新涵盖团队在某一时间段内的工作，通常为一周。内容分为三个部分：
- 进展：团队在过去时间段内已完成的工作。重点关注已上线的功能、达成的里程碑、已启动的任务等。
- 计划：团队在未来时间段内的工作安排。重点关注团队当前最核心、优先级最高的事项。
- 问题：任何阻碍团队推进工作的因素。例如人员不足、阻碍工作进展的漏洞或障碍、失败的交易等。
撰写前，请确认团队名称。若未指定，请明确询问用户。
Tools Available
可用工具
Whenever possible, try to pull from available sources to get the information you need:
- Slack: posts from team members with their updates - ideally look for posts in large channels with lots of reactions
- Google Drive: docs written from critical team members with lots of views
- Email: emails with lots of responses of lots of content that seems relevant
- Calendar: non-recurring meetings that have a lot of importance, like product reviews, etc.
Gather as much context as possible, focusing on the time period being covered:
- Progress: anything between a week ago and today
- Plans: anything from today to the next week
- Problems: anything between a week ago and today
If lacking access, ask the user for topics to cover. They may also provide these directly - in which case, format them appropriately for this particular format.
尽可能从以下可用渠道获取所需信息：
- Slack：团队成员发布的更新内容——优先查看大型频道中获得大量互动的帖子
- Google Drive：核心团队成员撰写、浏览量高的文档
- Email：收到大量回复、内容相关度高的邮件
- 日历：重要的非周期性会议，如产品评审会等
收集尽可能多的相关信息，重点关注对应时间段：
- 进展：过去一周到今天的所有相关事项
- 计划：今天到未来一周的工作安排
- 问题：过去一周到今天出现的所有阻碍因素
若无法获取上述渠道的信息，请询问用户需要涵盖的主题。用户也可能直接提供相关内容——此时需按照本框架的格式进行整理。
Workflow
工作流程
- Clarify scope: Confirm the team name and time period (usually past week for Progress/Problems, next week for Plans)
- Gather information: Use available tools or ask the user directly
- Draft the update: Follow the strict formatting guidelines
- Review: Ensure it's concise (30-60 seconds to read) and data-driven
- 明确范围：确认团队名称和时间段（通常进展/问题为过去一周，计划为未来一周）
- 收集信息：使用可用工具或直接向用户询问
- 撰写初稿：严格遵循格式规范
- 审核：确保内容简洁（阅读时间30-60秒）且基于数据
Formatting
格式要求
The format is always the same, very strict formatting. Never use any formatting other than this. Pick an emoji that is fun and captures the vibe of the team and update.
[pick an emoji] [Team Name] (Dates Covered, usually a week)
Progress: [1-3 sentences of content]
Plans: [1-3 sentences of content]
Problems: [1-3 sentences of content]
Each section should be no more than 1-3 sentences: clear, to the point. It should be data-driven, and generally include metrics where possible. The tone should be very matter-of-fact, not super prose-heavy.
格式需严格统一，不得使用其他格式。选择一个符合团队风格和更新主题的有趣表情符号。
[选择一个表情符号] [团队名称]（涵盖时间段，通常为一周）
进展：[1-3句话的内容]
计划：[1-3句话的内容]
问题：[1-3句话的内容]
每个部分最多1-3句话，清晰直白。内容需基于数据，尽可能包含指标。语气应客观平实，避免过于冗长的表述。