running-effective-meetings

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Running Effective Meetings

高效开展会议

Help the user run more effective meetings using frameworks from 40 product leaders.

利用40位产品负责人的框架，帮助用户更高效地开展会议。

How to Help

如何提供帮助

When the user asks for help with meetings:

Question the meeting's necessity - Ask if this could be async or if a meeting is truly needed
Clarify the purpose - Determine if it's for discovery, discussion, or decision
Design the structure - Help them create an appropriate agenda and process
Ensure follow-through - Guide them on capturing decisions and next steps

当用户寻求会议相关帮助时：

质疑会议的必要性——询问是否可以通过异步方式解决，或者是否真的需要召开会议
明确会议目的——确定会议是用于探索、讨论还是决策
设计会议结构——帮助他们制定合适的议程和流程
确保跟进落实——指导他们记录决策和后续行动

Core Principles

核心原则

Separate strategic from operational meetings

区分战略会议与运营会议

Naomi Gleit: "We have one weekly sort of strategic meeting. It's more open-ended, there is time for discussion... We also have one weekly operational meeting, which is highly structured where we go through all of the priority projects." Don't mix unstructured strategic discussion with structured operational updates.

Naomi Gleit："我们每周召开一次战略会议，形式更开放，有足够时间进行讨论……我们还会每周召开一次高度结构化的运营会议，梳理所有重点项目。" 不要将无结构的战略讨论与结构化的运营更新混为一谈。

Meetings are only for discussion

会议仅用于讨论

Annie Duke: "People generally think the purpose of a meeting is for three things, discover, discuss, decide. The only thing that's ever supposed to happen in a meeting is the discussion part." Discovery and decision-making should happen asynchronously. Reserve synchronous time for actual dialogue.

Annie Duke："人们通常认为会议有三个目的：探索、讨论、决策。但会议真正应该承载的只有讨论环节。" 探索和决策应通过异步方式进行，同步时间应留作真正的对话交流。

End with three questions

以三个问题结束会议

Alisa Cohn: "My three questions to end the meeting are, what did we decide here? Who needs to do what by when? And who else needs to know?" Ending meetings with standardized questions ensures alignment and prevents re-meetings.

Alisa Cohn："我用来结束会议的三个问题是：我们在这里做出了哪些决策？谁需要在何时完成什么任务？还有哪些人需要知晓这些信息？" 用标准化问题结束会议，确保达成共识，避免重复开会。

Don't skip the priming phase

不要跳过准备阶段

Evan LaPointe: "Meetings, generally speaking, are a combination of priming and decision making... A lot of meetings skip the priming step altogether." Most meeting dysfunction stems from skipping context-setting. Explicitly include a priming phase before diving into decisions.

Evan LaPointe："一般来说，会议包含准备和决策两个环节……很多会议完全跳过了准备步骤。" 大多数会议的问题都源于跳过了背景设定环节。在进入决策环节前，明确设置准备阶段。

Clear the calendar for important decisions

为重要决策预留专属时间

Jake Knapp + John Zeratsky: "The big idea with a design Sprint is to go from a zero to a prototype and a test of that prototype in just five days. And it's a recipe, it's a scripted set of activities." High-stakes strategic decisions benefit from time-boxed, calendar-cleared workshops.

Jake Knapp + John Zeratsky："设计冲刺的核心理念是在短短五天内从0到1完成原型制作并进行测试。这是一套标准化的流程和活动脚本。" 高风险的战略决策受益于有时间限制、专属日历时段的工作坊。

Minimize meetings ruthlessly

无情地减少会议数量

Gibson Biddle: "Minimize meetings, okay? Minimize meetings. That sucks the life out of everybody, including you." Protect productivity by actively removing non-essential meetings. A full calendar is a badge of shame, not honor.

Gibson Biddle："减少会议，好吗？减少会议。会议会榨干每个人的精力，包括你自己。" 通过主动取消非必要会议来保护生产力。日程排满是耻辱的标志，而非荣誉。

State changes maintain engagement

状态切换维持参与度

Wes Kao: "The state change method is that you should punctuate your monologues with state changes. So state changes are anything that shakes your audience awake." In virtual meetings, break up monologues every 3-5 minutes with polls, chat prompts, or speaker changes.

Wes Kao："状态切换法是指在独白过程中穿插状态切换。状态切换可以是任何能让听众保持清醒的活动。" 在虚拟会议中，每3-5分钟通过投票、聊天提示或切换发言者来打破独白。

Pre-reads shift status updates to async

会前预读将状态更新转为异步

Matt Mochary: "If everyone pre-prepared their update... we could take a three hour meeting down to a 45 minute meeting." Require attendees to submit written updates and proposed solutions before the meeting. Dedicate the first part to silent reading.

Matt Mochary："如果所有人都提前准备好更新内容……我们可以将3小时的会议缩短至45分钟。" 要求参会者在会前提交书面更新和拟议解决方案。会议前半段用于静默阅读。

Questions to Help Users

用于引导用户的问题

"Does this meeting need to happen, or could this be resolved async?"
"What's the purpose of this meeting: discovery, discussion, or decision?"
"What pre-work should attendees complete before the meeting?"
"Who is the decision-maker, and does everyone know that?"
"How will you capture and communicate decisions after the meeting?"
"What would need to be true for you to cancel this recurring meeting?"

"这个会议真的有必要召开吗？还是可以通过异步方式解决？"
"本次会议的目的是什么：探索、讨论还是决策？"
"参会者需要在会前完成哪些准备工作？"
"谁是决策者，所有人都清楚这一点吗？"
"会议结束后，你将如何记录并传达决策内容？"
"要满足什么条件，你才会取消这个定期会议？"

Common Mistakes to Flag

需要指出的常见错误

Status update meetings - Using synchronous time for information that could be shared async
No clear purpose - Meetings without explicit objectives
Missing priming - Jumping to decisions without establishing shared context
No documented outcomes - Ending without capturing what was decided and who's doing what
Too many attendees - Every additional person reduces candor and increases cost

状态更新会议——利用同步时间分享本可以异步传达的信息
缺乏明确目的——没有明确目标的会议
跳过准备阶段——未建立共同背景就直接进入决策环节
未记录会议成果——会议结束时未记录决策内容和行动责任人
参会人数过多——每增加一位参会者，都会降低坦诚度并增加成本

Deep Dive

深入了解

For all 54 insights from 40 guests, see

references/guest-insights.md

如需获取40位嘉宾的全部54条见解，请查看

references/guest-insights.md