Back to Details

running-effective-meetings

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Running Effective Meetings

高效开展会议

Scope

适用范围

Covers
  • Deciding whether a meeting is needed (vs async doc/message)
  • Choosing the right meeting format (operational / strategic / decision / workshop)
  • Preparing a pre-read and “priming” to avoid context-less discussions
  • Facilitating discussion, capturing decisions, and ensuring follow-through
  • Improving recurring meeting hygiene (split/kill/shorten meetings)
When to use
  • “Create an agenda and facilitation plan for a decision meeting.”
  • “We need a weekly operational cadence — design the meeting format and templates.”
  • “This meeting keeps going in circles — redesign it so we decide and assign actions.”
  • “Turn this messy invite into a clear meeting brief + pre-read + follow-up.”
When NOT to use
  • The goal is purely status updates (use async updates instead).
  • There is no discussion to be had (you already have the decision and only need to broadcast it).
  • The “decision owner” is not attending and cannot delegate decision rights.
  • The topic is a sensitive HR/legal/medical issue requiring specialist handling.
  • You actually need a multi-day workshop (e.g., a full design sprint) rather than a single meeting.
涵盖内容
  • 判断是否需要召开会议（对比异步文档/消息沟通）
  • 选择合适的会议形式（运营会/战略讨论会/决策会/工作坊）
  • 准备预读材料和“预热内容”，避免无背景的讨论
  • 引导讨论、记录决策并确保行动落地
  • 优化周期性会议规范（拆分/取消/缩短会议）
适用场景
  • “为决策会议制定议程和引导方案。”
  • “我们需要每周的运营同步机制——设计会议形式和模板。”
  • “这个会议总是绕圈子——重新设计它，让我们能够做出决策并分配行动项。”
  • “将这份混乱的会议邀请整理为清晰的会议简报+预读材料+跟进方案。”
不适用场景
  • 目标仅为状态更新（改用异步更新）。
  • 无需进行讨论（你已经做出决策，仅需告知相关方）。
  • “决策负责人”无法参会且未授权决策权限。
  • 议题涉及敏感的HR/法务/医疗问题，需要专业人员处理。
  • 实际需要的是多日工作坊（例如完整的设计冲刺）而非单次会议。

Inputs

输入要求

Minimum required
  • Meeting objective (what changes after the meeting)
  • Meeting type (or “recommend”): operational / strategic discussion / decision / workshop
  • Attendees (and the decision owner, if any)
  • Time box + date/time constraints (and remote/hybrid details)
  • Context links or a 5–10 bullet background summary
Missing-info strategy
  • Ask up to 5 questions from references/INTAKE.md.
  • If answers aren’t available, proceed with explicit assumptions and label unknowns.
最低必要输入
  • 会议目标（会议结束后将产生哪些变化）
  • 会议类型（或要求“推荐”）：运营会/战略讨论会/决策会/工作坊
  • 参会人员（以及决策负责人，如有）
  • 时间限制+日期/时间约束（以及远程/混合参会的细节）
  • 背景链接或5-10条要点式背景概述
缺失信息处理策略
  • 从references/INTAKE.md中选取最多5个问题进行询问。
  • 如果无法获取答案，基于明确的假设推进，并标注未知信息。

Outputs (deliverables)

输出交付物

Produce a Meeting Pack in Markdown (in-chat; or as files if requested), in this order:
  1. Meeting brief (goal, type, decision(s), roles, pre-work)
  2. Pre-read (context, options, open questions; “discover” happens async)
  3. Agenda (timed, discussion-first)
  4. Facilitation script (priming, prompts, how to handle stalls)
  5. Notes template + Decision log + Action items table
  6. Follow-up message (decisions, owners, deadlines, who-else-needs-to-know)
  7. Risks / Open questions / Next steps (always included)
Templates: references/TEMPLATES.md
生成Markdown格式的Meeting Pack（可在对话中直接生成；或按要求生成文件），顺序如下：
  1. 会议简报（目标、类型、待决策事项、角色、会前准备）
  2. 预读材料（背景、可选方案、待解决问题；“信息收集”通过异步方式完成）
  3. 会议议程（带时间限制、以讨论为核心）
  4. 引导脚本（预热内容、引导问题、僵局处理方式）
  5. 记录模板 + 决策日志 + 行动项表格
  6. 跟进消息（决策内容、负责人、截止日期、需告知的其他人员）
  7. 风险/待解决问题/后续步骤（必须包含）
模板：references/TEMPLATES.md

Workflow (7 steps)

工作流程（7个步骤）

1) Decide if a meeting is needed and pick the format

1) 判断是否需要会议并选择合适形式

  • Inputs: Request + context + constraints.
  • Actions: Clarify objective; decide whether the live meeting is for discussion only; pick meeting type (operational vs strategic vs decision vs workshop).
  • Outputs: Meeting type recommendation + meeting objective + draft brief header.
  • Checks: You can answer: “What will be different after this meeting?”
  • 输入： 请求内容+背景信息+约束条件
  • 行动： 明确目标；判断实时会议是否仅用于讨论；选择会议类型（运营会/战略会/决策会/工作坊）
  • 输出： 会议类型建议+会议目标+简报标题草稿
  • 校验： 能够明确回答“会议结束后会有哪些变化？”

2) Define the discussion scope (what is in-room vs async)

2) 定义讨论范围（线下讨论vs异步处理）

  • Inputs: Objective; stakeholders; open questions.
  • Actions: Separate Discover / Discuss / Decide:
    • Discover (context/data/options) → async pre-read
    • Discuss (trade-offs, objections, clarifications) → live meeting
    • Decide (final call + recording) → after discussion, captured explicitly
  • Outputs: Pre-read outline + list of discussion questions + decision statement(s).
  • Checks: At least 60% of the live time is reserved for discussion, not reading.
  • 输入： 会议目标；利益相关者；待解决问题
  • 行动： 区分信息收集/讨论/决策三类事项：
    • 信息收集（背景/数据/可选方案）→ 异步预读材料
    • 讨论（权衡利弊、异议、澄清）→ 实时会议
    • 决策（最终结论+记录）→ 讨论后明确记录
  • 输出： 预读材料大纲+讨论问题列表+决策声明
  • 校验： 至少60%的会议时间用于讨论，而非阅读

3) Prime participants (pre-work + pre-read)

3) 引导参会者做好准备（会前工作+预读材料）

  • Inputs: Pre-read outline; attendee list.
  • Actions: Create a priming section (goal, conversation category, decision rights); assign pre-work; send pre-read 24–48h before when possible.
  • Outputs: Complete pre-read + pre-work assignments.
  • Checks: Every attendee can arrive “ready to discuss” without a live info dump.
  • 输入： 预读材料大纲；参会人员列表
  • 行动： 创建预热板块（目标、对话类别、决策权限）；分配会前工作；尽可能提前24-48小时发送预读材料
  • 输出： 完整预读材料+会前工作分配
  • 校验： 每位参会者都能“带着讨论准备”参会，无需在会议中进行信息灌输

4) Build a timed agenda that matches the format

4) 构建匹配会议形式的带时程议程

  • Inputs: Meeting type; discussion questions; time box.
  • Actions: Timebox segments; limit to 1–3 topics; include explicit decision points; reserve time for closing alignment.
  • Outputs: Agenda with timing, prompts, and expected outputs per section.
  • Checks: Agenda maps each segment to a tangible output (decision, list, owner, next step).
  • 输入： 会议类型；讨论问题；时间限制
  • 行动： 为各环节设置时间限制；限制为1-3个议题；包含明确的决策节点；预留时间用于收尾对齐
  • 输出： 包含时程、引导问题及各环节预期产出的议程
  • 校验： 议程中每个环节都对应明确的产出（决策、列表、负责人、后续步骤）

5) Assign roles and write the facilitation script

5) 分配角色并编写引导脚本

  • Inputs: Agenda; participants.
  • Actions: Assign facilitator, decision owner, note-taker, timekeeper; write prompts and “if stuck” branches; set ground rules (parking lot, stack, time boxing).
  • Outputs: Facilitation script + roles list.
  • Checks: Roles are named; escalation path is clear if consensus fails.
  • 输入： 会议议程；参会人员
  • 行动： 分配引导者、决策负责人、记录者、计时员；编写引导问题及“陷入僵局时的应对方案”；设定基本规则（ parking lot机制、发言顺序、时间限制）
  • 输出： 引导脚本+角色分配列表
  • 校验： 明确各角色；共识无法达成时的升级路径清晰

6) Run the meeting and capture decisions/actions in real time

6) 开展会议并实时记录决策/行动项

  • Inputs: Script; notes template.
  • Actions: Start with priming; facilitate discussion; capture decisions and action items as they happen; keep to time boxes.
  • Outputs: Filled notes + decision log entries + action items table.
  • Checks: No important decision is left implicit or “to be clarified later.”
  • 输入： 引导脚本；记录模板
  • 行动： 以预热内容开场；引导讨论；实时记录决策和行动项；严格遵守时间限制
  • 输出： 填写完成的记录+决策日志条目+行动项表格
  • 校验： 所有重要决策均被明确记录，无隐含或“待后续澄清”的内容

7) Close, follow up, and improve meeting hygiene

7) 收尾、跟进及优化会议规范

  • Inputs: Captured notes/decisions/actions.
  • Actions: End with: (1) What did we decide? (2) Who does what by when? (3) Who else needs to know? Send follow-up within 24h; propose hygiene changes (split strategic vs operational, cancel/shorten recurring meetings).
  • Outputs: Follow-up message + updated trackers + hygiene recommendations + Risks/Open questions/Next steps.
  • Checks: Every action item has an owner and due date; stakeholders to inform are named.
  • 输入： 已记录的内容/决策/行动项
  • 行动： 收尾时明确：(1) 我们做出了哪些决策？(2) 谁在何时完成什么任务？(3) 还需告知哪些人员？24小时内发送跟进消息；提出会议规范优化建议（拆分战略vs运营会议、取消/缩短周期性会议）
  • 输出： 跟进消息+更新后的追踪表+会议规范建议+风险/待解决问题/后续步骤
  • 校验： 每个行动项都有负责人和截止日期；明确需告知的利益相关者

Quality gate (required)

质量校验要求

  • Use references/CHECKLISTS.md and score with references/RUBRIC.md.
  • Always include: Risks, Open questions, Next steps.
  • 使用references/CHECKLISTS.md并通过references/RUBRIC.md进行评分。
  • 必须包含：风险、待解决问题、后续步骤。

Examples

示例

Example 1 (Operational cadence): “Design a weekly operational meeting for a product squad to track priority projects without drifting into strategy.”
Expected: a structured meeting brief, recurring agenda template, status update pattern, and a hygiene rule to move strategy to a separate forum.
Example 2 (Decision meeting): “Create a decision meeting pack for choosing between two onboarding flows (A vs B) with PM/Design/Eng and a decision owner.”
Expected: pre-read with options + evidence, timed agenda, facilitation prompts for trade-offs, and a decision record + action items.
Boundary example: “Schedule a meeting to ‘get alignment’ but there’s no decision, no owner, and no pre-read.”
Response: ask for the decision/outcome; recommend async discovery first; refuse to produce a meeting pack until objective/owner is defined.
示例1（运营同步机制）： “为产品团队设计每周运营会，用于跟踪重点项目，避免偏离至战略讨论。”
预期产出：结构化的会议简报、周期性议程模板、状态更新模式，以及将战略讨论移至单独会议的规范规则。
示例2（决策会议）： “为PM/设计/工程师团队及决策负责人创建Meeting Pack，用于在两个新用户引导流程（A vs B）中做出选择。”
预期产出：包含可选方案+依据的预读材料、带时间限制的议程、用于权衡讨论的引导问题，以及决策记录+行动项。
边界示例： “安排一场‘达成共识’的会议，但没有明确决策、没有负责人、也没有预读材料。”
回应：询问决策/预期成果；建议先进行异步信息收集；在明确目标/负责人前，拒绝生成Meeting Pack。

Reference files

参考文件

  • references/INTAKE.md
  • references/WORKFLOW.md
  • references/TEMPLATES.md
  • references/CHECKLISTS.md
  • references/RUBRIC.md
  • references/SOURCE_SUMMARY.md
  • references/EXAMPLES.md
  • references/INTAKE.md
  • references/WORKFLOW.md
  • references/TEMPLATES.md
  • references/CHECKLISTS.md
  • references/RUBRIC.md
  • references/SOURCE_SUMMARY.md
  • references/EXAMPLES.md