Back to Details

gtm-board-and-investor-communication

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Board and Investor Communication

董事会与投资者沟通

Structure board meetings, investor updates, and executive communication that builds trust and drives decisions — not slide decks that nobody reads.
构建能建立信任、推动决策的董事会会议、投资者更新及高管沟通机制——而非无人问津的演示文稿。

When to Use

适用场景

Triggers:
  • "How do I prepare for our board meeting?"
  • "What should go in our investor update?"
  • "We missed our numbers, how do we communicate this?"
  • "Board deck structure"
  • "How often should we update investors?"
  • "Our board meetings aren't productive"
Context:
  • Seed through growth-stage companies
  • Board meeting preparation and follow-up
  • Monthly/quarterly investor updates
  • Handling misses and bad news
  • Cascading strategy from board to organization
触发场景：
  • "我该如何筹备董事会会议？"
  • "投资者更新内容应包含哪些部分？"
  • "我们未达成目标，该如何向董事会沟通？"
  • "董事会演示文稿结构"
  • "我们应多久向投资者更新一次？"
  • "我们的董事会会议效率低下"
适用环境：
  • 种子轮到成长期企业
  • 董事会会议筹备及跟进
  • 月度/季度投资者更新
  • 处理目标未达成及坏消息
  • 将董事会战略向下传递至整个组织

Core Frameworks

核心框架

1. Tell the Story, Then Show the Data

1. 先讲叙事，再展示数据

The Pattern:
Most board meetings start with a data dump. Slide after slide of metrics, then 10 minutes of Q&A where board members try to figure out what it all means.
Flip it. The narrative should lead; data should confirm.
How It Works:
Open with where you are in the journey. Not "here's our ARR" but "here's what we believed coming into the quarter, what we learned, and where that puts us now." Then show the data that validates the narrative.
Board Meeting Structure:
Pre-Read (Sent 48-72 Hours Before)
  • Financial dashboard (ARR, burn, runway, pipeline)
  • Metric scorecard with health indicators (green/yellow/red)
  • 2-3 page narrative summary covering market context and strategic update
  • Rule: If it can be read, don't present it
The Meeting (90-120 Minutes)
  1. Market context and questions on pre-read (15 min)
    • What's changed in the market since last meeting?
    • Board asks about anything unclear from pre-read
    • No re-presenting the data
  2. CEO strategic update — The "Three Things" (15 min)
    • What's working (2-3 areas showing momentum)
    • What's not (1-2 specific gaps, not vague)
    • What we're doing about it (specific changes, not promises)
    • This is narrative, not numbers
  3. Decision items (30-45 min)
    • 1-3 topics where the board's input or approval is needed
    • Come prepared: "We're deciding between X and Y, board thoughts?"
    • Leave with a decision, not "let's revisit next quarter"
  4. Deep dive (20-30 min)
    • One topic explored in depth (rotating each meeting)
    • Bring the functional leader who owns it
    • Examples: pricing strategy, competitive landscape, org design, market expansion
  5. Closing (10 min)
    • Summarize decisions made and action owners
    • Closed session (board without management)
    • CEO and board chair debrief
Common Mistakes:
  • Opening with data before narrative (board gets lost in numbers without context)
  • Multiple competing narratives (board can't synthesize — pick one arc)
  • Trying to cover too many topics deeply (results in rushed decisions on everything)
  • No deep dives (board becomes a rubber stamp)
  • Filling the meeting with good news (boards don't trust CEOs who only share wins)
模式：
大多数董事会会议以数据堆砌开场，一页接一页的指标，随后是10分钟的问答环节，董事会成员试图理清这些数据的意义。
反过来做：先讲叙事，再用数据佐证。
操作方式：
开场先说明当前在发展旅程中的位置。不说“这是我们的ARR”，而是“本季度初我们的预期是什么，我们学到了什么，以及当前所处的阶段”。然后展示能佐证该叙事的数据。
董事会会议结构：
预读材料（会议前48-72小时发送）
  • 财务仪表盘（ARR、烧钱率、runway、pipeline）
  • 带健康状态标识（绿/黄/红）的指标评分卡
  • 2-3页的叙事摘要，涵盖市场背景及战略更新
  • 规则：可阅读的内容，无需在会议上展示
会议流程（90-120分钟）
  1. 市场背景及预读材料答疑（15分钟）
    • 自上次会议以来市场发生了哪些变化？
    • 董事会成员就预读材料中的疑问提问
    • 无需重新展示数据
  2. CEO战略更新——“Three Things”模型（15分钟）
    • 进展顺利的方面（2-3个体现增长势头的领域）
    • 存在问题的方面（1-2个具体的差距，而非模糊表述）
    • 我们的应对措施（具体的调整，而非空泛承诺）
    • 这部分是叙事，而非数字罗列
  3. 待决策事项（30-45分钟）
    • 1-3个需要董事会提供意见或批准的议题
    • 提前准备：“我们在X和Y之间犹豫，想听听董事会的看法？”
    • 会议结束时要得出决策，而非“下次会议再讨论”
  4. 深度研讨（20-30分钟）
    • 每次会议选取一个议题进行深度探讨（轮换制）
    • 邀请负责该领域的职能负责人参会
    • 示例：定价策略、竞争格局、组织架构、市场扩张
  5. 会议收尾（10分钟）
    • 总结已做出的决策及负责人
    • 闭门会议（管理层离场，仅董事会成员参会）
    • CEO与董事会主席复盘
常见误区：
  • 先展示数据再讲叙事（董事会成员在缺乏上下文的情况下会迷失在数字中）
  • 同时讲述多个相互冲突的叙事（董事会无法整合信息——选定一条主线）
  • 试图深入覆盖过多议题（导致所有事项的决策都很仓促）
  • 没有深度研讨环节（董事会沦为橡皮图章）
  • 会议全是好消息（董事会不会只分享胜利的CEO）

2. The "Three Things" Narrative Model

2. “Three Things”叙事模型

The Pattern:
Businesses are too complex to summarize in one headline. Three distinct points — what's working, what's not, what's changing — let the board grasp status and trajectory in minutes.
What's Working (2-3 areas): Be specific. Not "sales are going well" but "closed first six-figure enterprise deal, validating the commercial motion." Quantify momentum:
  • New product launches gaining adoption
  • Sales motion maturing (first big customer, repeatable motion emerging)
  • Community/ecosystem milestones
What's Not Working (1-2 areas): Be equally specific. Not "we had some challenges" but "self-serve conversion is weak — strong awareness but 0.1% conversion rate." Board needs to understand the actual problem, not a euphemism.
What We're Doing About It (for each "not working"): Articulate specific changes. What product changes? What org changes? What's the timeline? What resources are committed?
Why This Works:
Board members read dozens of updates. The Three Things model gives them a mental filing system: momentum (feel good), risk (pay attention), agency (this team handles problems). Without it, boards either over-index on one bad metric or miss the real issue buried in a 40-slide deck.
模式：
业务过于复杂，无法用一句话概括。三个明确的要点——进展顺利的方面、存在问题的方面、即将做出的调整——能让董事会在几分钟内掌握现状及发展趋势。
进展顺利的方面（2-3个领域）： 表述要具体。不说“销售情况良好”，而是“签下首个六位数企业客户，验证了商业化模式的可行性”。量化增长势头：
  • 新产品发布获得用户认可
  • 销售模式成熟（拿下首个大客户，可复制的模式逐渐成型）
  • 社区/生态系统里程碑
存在问题的方面（1-2个领域）： 同样要具体。不说“我们遇到了一些挑战”，而是“自助转化效果不佳——品牌认知度高，但转化率仅为0.1%”。董事会需要了解实际问题，而非委婉的说法。
我们的应对措施（针对每个“存在问题”的领域）： 明确说明具体的调整措施。产品层面有哪些变化？组织架构有哪些调整？时间线是什么？投入了哪些资源？
为何该模型有效：
董事会成员会阅读数十份更新内容。“Three Things”模型为他们提供了一个清晰的认知框架：增长势头（正面）、风险点（需关注）、执行力（团队能解决问题）。没有这个模型，董事会要么过度关注某个糟糕的指标，要么在40页的演示文稿中错过真正的问题。

3. Progress Is Directional, Not Absolute

3. 进展是方向性的，而非绝对的

The Pattern:
It doesn't matter if you hit 100K users if you were aiming for 50K — or if you missed 200K. Context is everything. Show progress toward your goal, not just the number.
How to Frame Progress:
  • On track: "Target 100K active developers. Currently 70K. All initiatives performing as planned. Confidence: High."
  • At risk: "Target 100K active developers. Currently 50K. Acquisition cost higher than expected. Testing new channels. Adjusted target: 85K. Confidence: Medium."
  • Ahead: "Target 100K active developers. Currently 95K. Exceeding acquisition forecasts. New partnerships accelerating growth. Confidence: Very high."
The Rules:
  1. Set the goal upfront (every metric needs a target)
  2. Show progress as % toward goal, not just absolute number
  3. Acknowledge misses; explain pivots
  4. State confidence level based on trajectory
Common Mistake:
Changing goals when you miss them. Boards track this. If Q1 target was 100K and you hit 60K, don't make Q2 target 75K and call it "revised guidance." State the miss, explain why, show the recovery plan. Credibility compounds faster than metrics.
模式：
如果你目标是5万用户却获得了10万，或是目标20万却只达到10万，单纯的数字没有意义。上下文才是关键。要展示朝着目标前进的进展，而非只看数字本身。
如何呈现进展：
  • 按计划推进：“目标是10万活跃开发者，当前已达7万。所有举措均按计划执行，信心：高。”
  • 存在风险：“目标是10万活跃开发者，当前仅达5万。获客成本高于预期，正在测试新渠道。调整后的目标：8.5万，信心：中。”
  • 超出预期：“目标是10万活跃开发者，当前已达9.5万。获客表现超出预期，新合作伙伴加速了增长，信心：极高。”
规则：
  1. 先明确目标（每个指标都要有对应的目标）
  2. 展示相对于目标的进展比例，而非仅展示绝对数字
  3. 坦诚未达成目标的情况，说明调整方向
  4. 根据发展趋势说明信心水平
常见误区：
未达成目标时就更改目标。董事会会注意到这一点。如果Q1目标是10万，实际仅达6万，不要把Q2目标设为7.5万并称之为“修订后的指引”。要说明未达成的情况、原因，以及恢复计划。可信度比指标增长更重要。

4. The Four-Tier Metric Hierarchy

4. 四级指标层级体系

The Pattern:
Too many metrics confuse the board. Too few miss important signals. Structure your metrics in four tiers, and never change them quarter to quarter.
Tier 1: North Star (1 metric) The single metric that best represents company health.
  • Examples: ARR, active users, tasks completed
  • Show trend line, not just current state
  • This is the one metric the board should remember if they forget everything else
Tier 2: Driver Metrics (3-5 metrics) Leading indicators that predict your north star.
  • User acquisition rate
  • Retention curves (how many active last month remain active this month?)
  • Feature adoption (% of users on key feature)
  • DAU/MAU ratio
  • Pipeline coverage
  • Why track these: early warning before revenue impact
Tier 3: Health Metrics (3-5 metrics) Signals of team and operational health.
  • Burn rate and runway
  • Headcount vs plan
  • Engineering velocity / shipping pace
  • NPS or customer satisfaction
  • Why track these: capacity constraints on growth
Tier 4: Red Flags (2-3 thresholds) Metrics that, if they cross a threshold, require immediate action.
  • Churn rate above X%
  • CAC above $Y
  • Retention decline greater than Z%
  • Why track these: triggers for strategic conversation, not just monitoring
The Discipline Rules:
  1. Same metrics every quarter. Build a 4-6 quarter track record. OK to add new metrics, but never drop old ones.
  2. One context sentence per metric. What does this metric tell us? Is it good or bad? What's the implication?
  3. Actuals vs plan, always. Never show a metric without showing what you planned. The delta is the conversation.
  4. Disaggregate when needed. Total usage hides segments. Break down by customer type, segment, product line — wherever averages mask reality.
  5. Use health indicators. Green/yellow/red status for quick board assessment. Lets board scan the dashboard and zoom in on yellows and reds.
Common Mistake:
Changing which metrics you show based on which ones look good this quarter. Boards notice immediately. It's the fastest way to lose credibility on your numbers. Show the same dashboard every time — when a metric looks bad, that's the conversation.
模式：
指标太多会让董事会困惑，太少则会遗漏重要信号。将指标分为四个层级，且每个季度保持不变。
第一层：北极星指标（1个） 最能代表公司健康状况的单一指标。
  • 示例：ARR、活跃用户数、完成任务量
  • 展示趋势线，而非仅当前状态
  • 这是董事会即使忘记其他所有指标也应该记住的指标
第二层：驱动指标（3-5个） 可预测北极星指标的领先指标。
  • 用户获客率
  • 留存曲线（上月活跃用户中本月仍活跃的比例？）
  • 功能 adoption（使用核心功能的用户占比）
  • DAU/MAU 比率
  • Pipeline覆盖率
  • 追踪这些指标的原因：在影响收入前发出预警
第三层：健康指标（3-5个） 反映团队及运营健康状况的信号。
  • 烧钱率及runway
  • 员工人数与计划的对比
  • 工程交付速度/发布节奏
  • NPS或客户满意度
  • 追踪这些指标的原因：增长的产能限制
第四层：红色预警指标（2-3个阈值） 一旦超过阈值就需要立即采取行动的指标。
  • 客户流失率高于X%
  • CAC高于$Y
  • 留存率下降幅度超过Z%
  • 追踪这些指标的原因：触发战略对话，而非仅监控
管理规则：
  1. 每个季度使用相同的指标。建立4-6个季度的追踪记录。可以添加新指标，但绝不能删除旧指标。
  2. 每个指标配一句上下文说明。这个指标告诉我们什么？是好是坏？有什么影响？
  3. 始终展示实际值与计划值的对比。绝不能只展示指标而不展示目标。差值就是讨论的重点。
  4. 必要时拆分指标。整体使用数据会掩盖细分情况。按客户类型、细分领域、产品线拆分——任何平均值会掩盖真相的地方都要拆分。
  5. 使用健康状态标识。用绿/黄/红状态让董事会快速评估。让董事会可以快速浏览仪表盘，重点关注黄/红指标。
常见误区：
根据本季度哪些指标好看就更换展示的指标。董事会会立刻注意到这一点。这是让董事会对你的数字失去信任最快的方式。每次都展示相同的仪表盘——当某个指标表现不佳时，这就是讨论的重点。

5. Deliver Bad News Before the Board Asks

5. 在董事会提问前传达坏消息

The Pattern:
Board confidence erodes when bad news is delayed or sugar-coated. They can handle bad news. They can't handle surprises. And they hate slow decision-making.
The Pre-Brief Pattern:
Before bad news hits the full board, pre-brief your lead director 48-72 hours before the meeting.
  • Who: Board chair or most experienced director
  • What: The issue, your assessment, your plan
  • Why: Director can help frame for the full board, avoid surprise shock, and may have seen this pattern before
Then send a short email to the full board:
"Wanted to flag something before our next meeting. [Specific problem]. Here's what we know so far, what we don't know yet, and what we're doing about it. Will have a full update at the board meeting."
The Bad News Framework:
For every piece of bad news, four elements:
  1. What happened (specific, one sentence — not defensive)
    • "We missed Q1 target of 10 new enterprise customers; achieved 7"
  2. Why it happened (root cause, not excuse)
    • "Customer evaluation timelines slipped due to product gaps we didn't diagnose early enough"
    • Own it: "We misread the demand signal" not "the market shifted"
  3. What's the impact (honest about severity)
    • "Affects Q1 ARR by ~$50K, pushing us below original guidance"
  4. What we're doing about it (specific actions, owners, timeline)
    • "Changed sales motion to qualify on product readiness upfront; revised Q2 target to 15 (including Q1 backlog of 7)"
How NOT to Communicate a Miss:
  • "We didn't hit Q1 goals, but the pipeline is strong"
  • "External factors slowed deals, but we're confident about Q2"
  • "We had some implementation challenges, but they're resolved now"
All vague. All defensive. None explain root cause or plan.
Follow-Through Pattern:
Every subsequent board update should reference previously raised issues: "Last quarter I flagged [issue]. Here's the update: [progress]. Status: [resolved / in progress / escalating]."
This builds a track record of follow-through. Boards remember who tracks their own problems.
Common Mistake:
Sandwiching bad news between good news hoping nobody notices. Board members see this immediately. It damages trust more than the bad news itself.
模式：
如果坏消息被推迟或粉饰，董事会的信心会受损。他们能接受坏消息，但无法接受突发状况，也讨厌决策缓慢。
预沟通模式：
在坏消息提交给全体董事会之前，提前48-72小时向首席董事进行预沟通。
  • **沟通对象：**董事会主席或最资深的董事
  • **沟通内容：**问题本身、你的评估、你的应对计划
  • **原因：**董事可以帮助向全体董事会铺垫，避免突发冲击，而且他们可能之前遇到过类似情况
然后向全体董事会发送一封简短的邮件：
“想在下次会议前提醒大家注意一件事。[具体问题]。以下是目前我们了解到的情况、尚未明确的信息，以及我们的应对措施。将在董事会会议上提供完整更新。”
坏消息沟通框架：
每条坏消息都应包含四个要素：
  1. 发生了什么（具体的一句话表述——不要辩解）
    • “我们未达成Q1新增10个企业客户的目标，仅完成7个”
  2. 原因是什么（根本原因，而非借口）
    • “客户评估周期延长，因为我们未能及早发现产品缺陷”
    • 主动承担责任：“我们误判了需求信号”而非“市场发生了变化”
  3. 影响是什么（坦诚严重程度）
    • “导致Q1 ARR减少约5万美元，低于原指引”
  4. 我们的应对措施是什么（具体行动、负责人、时间线）
    • “调整了销售模式，在前期就根据产品成熟度进行客户筛选；将Q2目标修订为15个（包含Q1未完成的7个）”
错误的未达成目标沟通方式：
  • “我们未达成Q1目标，但pipeline情况良好”
  • “外部因素导致交易放缓，但我们对Q2有信心”
  • “我们遇到了一些实施挑战，但现已解决”
这些表述都很模糊，充满辩解，没有说明根本原因或应对计划。
跟进模式：
后续每次董事会更新都要提及之前提出的问题：“上季度我提到了[问题]，以下是最新进展：[进展情况]，状态：[已解决/进行中/升级处理]。”
这能建立起跟进执行的记录。董事会会记得那些能跟踪自身问题的人。
常见误区：
把坏消息夹在两个好消息之间，希望没人注意到。董事会成员会立刻看穿这一点。这比坏消息本身更损害信任。

6. The Monthly Investor Update

6. 月度投资者更新

The Pattern:
Most founders send investor updates quarterly at best. The best founders send monthly — even when things are bad. Especially when things are bad.
Why Monthly:
  • Keeps investors engaged without scheduling calls
  • When you need help (intros, advice, bridge), investors already have context
  • Consistency signals operational discipline; irregular updates signal chaos
The Format:
Subject line: [Company Name] — [Month] Update
Opening (1 paragraph): One headline. Brief context.
TL;DR (3 bullets):
  • One number (the metric that matters most right now)
  • One win (specific — customer name, deal size, milestone)
  • One challenge (with what you're doing about it)
Key Metrics (same table every month):
MetricThis MonthLast Month3-Mo Avgvs Plan
ARR
MRR Growth
Burn Rate
Runway (months)
Pipeline
Customers
Don't include metrics unchanged from last update — focus on what's new.
Key Updates (2-3 bullets):
  • Major hires, product launches, partnership/customer wins
  • Strategic pivots or course corrections
  • Specific enough to matter
Asks (1-2 bullets):
  • What help do you need? Intros, hiring leads, strategic advice
  • Be specific: "Looking for intro to VP Eng at [company type]" not "Looking for engineering talent"
The Cadence Rules:
  • Same day every month. First Monday, last Friday — pick one and never miss it
  • Send within a week of major news (don't hold it for the next scheduled update)
  • During active fundraising: weekly updates to warm investors, monthly to existing
Common Mistake:
Only sending updates when things are good. Six months of good news followed by silence tells investors exactly what you're not telling them.
模式：
大多数创始人最多每季度发送一次投资者更新。最优秀的创始人会每月发送——即使情况不好，尤其是情况不好的时候。
为何要月度更新：
  • 无需安排电话会议就能保持投资者的参与度
  • 当你需要帮助（介绍资源、建议、过桥贷款）时，投资者已经了解上下文
  • 一致性体现了运营的规范性；不定期的更新则暗示混乱
格式：
主题：[公司名称] — [月份] 更新
开头（1段）： 一个核心标题，简短的上下文说明。
要点摘要（3个要点）：
  • 一个关键数字（当前最重要的指标）
  • 一个具体的胜利（客户名称、交易规模、里程碑）
  • 一个挑战及应对措施
核心指标（每月使用相同的表格）：
Metric本月上月3个月平均与计划对比
ARR
MRR Growth
烧钱率
Runway（月）
Pipeline
客户数
无需包含与上月相比无变化的指标——重点展示新情况。
重要更新（2-3个要点）：
  • 重要招聘、产品发布、合作伙伴/客户胜利
  • 战略调整或方向修正
  • 表述要具体，有实际意义
需求（1-2个要点）：
  • 你需要什么帮助？介绍资源、招聘线索、战略建议
  • 表述要具体：“希望能介绍[某类型公司]的工程副总裁”而非“寻找工程人才”
节奏规则：
  • 每月固定日期发送。比如每月第一个周一或最后一个周五——选定后绝不缺席
  • 重大消息发生后一周内发送（不要等到下一次计划好的更新）
  • 融资期间：向潜在投资者每周更新，向现有投资者每月更新
常见误区：
只在情况好的时候发送更新。六个月的好消息之后突然沉默，会让投资者立刻明白你在隐瞒什么。

7. Burn Is About Discipline; Revenue Is About Traction

7. 烧钱率体现规范性；收入体现增长势头

The Pattern:
Financial communication to the board has two separate stories. Don't conflate them.
Burn Communication:
  • Monthly rate, runway in months, YoY improvement
  • Efficiency gains (what did you cut, what did you optimize?)
  • Capital plan: what's secured, what's targeted, what's the timeline
The burn story is: "We are disciplined operators who make capital go further."
Revenue Communication:
  • MoM growth, CAC, LTV, payback period
  • Customer segmentation (self-serve vs enterprise, what's the mix?)
  • Monetization plan with timeline
The revenue story is: "We have traction and know how to grow it."
Reconcile Both: The best financial communication shows: "We're burning less while growing faster." That's evidence of operating leverage, and it's the single most compelling thing a board can hear.
Common Mistake:
Conflating burn with growth. A board that hears "we're growing fast" while burn rate climbs thinks you're buying growth. A board that hears "we cut burn by 40%" while growth stalls thinks you're in survival mode. Tell both stories, separately, and then connect them.
模式：
向董事会进行财务沟通时，要分开讲述两个独立的故事，不要混为一谈。
烧钱率沟通：
  • 月度烧钱率、剩余runway（月数）、同比改善情况
  • 效率提升措施（削减了什么、优化了什么？）
  • 资本计划：已落实的资金、目标资金、时间线
烧钱率的故事是：“我们是规范的经营者，能让资本发挥更大价值。”
收入沟通：
  • 月度环比增长、CAC、LTV、回收期
  • 客户细分（自助 vs 企业客户，占比如何？）
  • 带时间线的 monetization计划
收入的故事是：“我们有增长势头，且知道如何扩大规模。”
整合两个故事： 最好的财务沟通是：“我们在降低烧钱率的同时加快了增长速度。”这是运营杠杆的体现，也是董事会最想听到的内容。
常见误区：
将烧钱率与增长混为一谈。如果董事会听到“我们增长很快”但烧钱率在上升，会认为你是在“购买增长”。如果董事会听到“我们将烧钱率降低了40%”但增长停滞，会认为你处于生存模式。要分开讲述两个故事，然后再将它们联系起来。

8. Cascading Strategy from Board to Organization

8. 将董事会战略向下传递至整个组织

The Pattern:
Strategy decided in a board room doesn't matter if the team doesn't know it. Create a systematic communication cascade.
The Four Levels:
Level 1: Executive Team (Weekly)
  • Strategic priorities and emerging risks
  • Key decisions needing alignment
Level 2: Extended Leadership (Bi-weekly)
  • How strategy impacts each function
  • Key priorities and how success will be measured
Level 3: All-Hands (Monthly, 60 min)
  • Leadership update (15 min): where we are, what's changed
  • Wins celebration (10 min): customers, launches, people
  • Deep dive (20 min): one strategic initiative in detail
  • Q&A (15 min): real questions, real answers
Level 4: Team-Specific (Ongoing)
  • How team goals connect to company strategy
  • What success looks like for this team specifically
The Test:
Pick a random employee. Can they explain the company strategy? If not, the cascade is broken. Strategy that exists only in executive heads is not strategy — it's a secret.
Connect OKRs to Cascade:
  • Company OKRs from strategy
  • Function OKRs aligned to company
  • Team OKRs aligned to function
  • Individual understands how they contribute
Common Mistake:
Inconsistent messaging. If different leaders tell different stories about where the company is headed, the organization optimizes for conflicting goals. Write the strategy down. One page. Make everyone use the same words.
模式：
如果团队不了解董事会制定的战略，那么这个战略毫无意义。要建立系统化的沟通传递机制。
四个层级：
第一层：高管团队（每周）
  • 战略优先级及新出现的风险
  • 需要达成共识的关键决策
第二层：扩展领导团队（每两周）
  • 战略对各职能部门的影响
  • 核心优先级及成功衡量标准
第三层：全员会议（每月，60分钟）
  • 领导层更新（15分钟）：当前状态、发生的变化
  • 成果庆祝（10分钟）：客户、产品发布、员工
  • 深度讲解（20分钟）：一个战略举措的详细内容
  • 问答环节（15分钟）：真实问题，真实回答
第四层：团队层面（持续进行）
  • 团队目标如何与公司战略对齐
  • 该团队的成功标准是什么
检验标准：
随机挑选一名员工，看他们能否解释公司战略。如果不能，说明传递机制失效了。只存在于高管头脑中的战略不是战略——是秘密。
将OKRs与传递机制结合：
  • 公司OKRs源自战略
  • 职能部门OKRs与公司OKRs对齐
  • 团队OKRs与职能部门OKRs对齐
  • 员工了解自己的贡献
常见误区：
信息传递不一致。如果不同的领导者对公司发展方向有不同的表述，组织会朝着相互冲突的目标优化。要把战略写下来，一页纸即可，确保所有人使用统一的表述。

Decision Trees

决策树

Board Meeting vs Investor Update

董事会会议 vs 投资者更新

Is this a full board meeting?
├─ Yes → Full structure: pre-read + Three Things + decisions + deep dive
└─ No → Continue...
    │
    Is this a major event (fundraise close, big miss, key hire)?
    ├─ Yes → Ad-hoc update immediately (don't wait for schedule)
    └─ No → Monthly investor update format
Is this a full board meeting?
├─ Yes → Full structure: pre-read + Three Things + decisions + deep dive
└─ No → Continue...
    │
    Is this a major event (fundraise close, big miss, key hire)?
    ├─ Yes → Ad-hoc update immediately (don't wait for schedule)
    └─ No → Monthly investor update format

How to Frame a Metric

如何呈现指标

Did you hit the target?
├─ Yes → State it, move on. Don't over-celebrate.
└─ No → Continue...
    │
    Do you understand why?
    ├─ Yes → Root cause + plan + revised timeline
    └─ No → Say "we're diagnosing" + what you're doing to find out
        │
        Is the miss material (affects runway, strategy, or board confidence)?
        ├─ Yes → Pre-brief lead director before board meeting
        └─ No → Include in Three Things narrative, "what's not working"
Did you hit the target?
├─ Yes → State it, move on. Don't over-celebrate.
└─ No → Continue...
    │
    Do you understand why?
    ├─ Yes → Root cause + plan + revised timeline
    └─ No → Say "we're diagnosing" + what you're doing to find out
        │
        Is the miss material (affects runway, strategy, or board confidence)?
        ├─ Yes → Pre-brief lead director before board meeting
        └─ No → Include in Three Things narrative, "what's not working"

Common Mistakes

常见误区

1. Board meetings as status reports Board members can read. Send the pre-read. Use the meeting for decisions and discussion, not data walkthroughs.
2. Changing metrics every quarter Consistency in metrics builds trust. The moment you swap out a metric that looked bad for one that looks good, you've told the board your numbers can't be trusted.
3. No clear ask Every investor update, every board meeting should have an ask. Intros, advice, approval, patience. Investors want to help — if you never ask, they disengage.
4. Defending instead of describing When you're explaining away a miss for 10 minutes, the board hears defensiveness. State the miss, state the cause, state the plan. Move on.
5. Strategy stays in the board room If your team can't explain the strategy, you haven't communicated it. Cascade it or it doesn't exist.
6. Surprises in the board meeting Bad news should never land for the first time in a board meeting. Pre-brief the lead director. Send the flag email. Let the board process before the meeting.
1. 董事会会议沦为状态汇报 董事会成员会阅读材料。发送预读材料，将会议时间用于决策和讨论，而非数据讲解。
2. 每个季度更换指标 指标的一致性能建立信任。当你把表现不好的指标换成表现好的指标时，你就是在告诉董事会你的数字不可信。
3. 没有明确的需求 每次投资者更新、每次董事会会议都应该有明确的需求。介绍资源、建议、批准、耐心。投资者想提供帮助——如果你从不提出需求，他们会失去参与感。
4. 辩解而非描述 如果你花10分钟为未达成目标辩解，董事会听到的是你的防御心态。说明未达成的情况、原因、应对计划，然后继续。
5. 战略只停留在董事会层面 如果你的团队无法解释战略，说明你没有做好沟通。要么传递战略，要么战略就不存在。
6. 董事会会议上出现突发状况 坏消息绝不能首次出现在董事会会议上。提前与首席董事预沟通，发送提醒邮件，让董事会在会议前有时间消化。

Quick Reference

快速参考

Board meeting flow: Pre-read (48-72 hrs before) → Questions (15 min) → Three Things narrative (15 min) → Decision items (30-45 min) → Deep dive (20-30 min) → Closed session (10 min)
Three Things model: What's working + What's not + What we're doing about it
Metric hierarchy: North star (1) → Drivers (3-5) → Health (3-5) → Red flags (2-3 thresholds)
Bad news protocol: Pre-brief lead director (48-72 hrs) → Flag email to full board → What happened → Why → Impact → Plan → Follow up every subsequent meeting
Monthly investor update: TL;DR (3 bullets) → Same metrics table → Key updates (2-3) → Specific asks (1-2)
Communication cascade: Exec (weekly) → Leadership (bi-weekly) → All-hands (monthly) → Team (ongoing)
董事会会议流程： 预读材料（会前48-72小时）→ 答疑（15分钟）→ Three Things叙事（15分钟）→ 待决策事项（30-45分钟）→ 深度研讨（20-30分钟）→ 闭门会议（10分钟）
Three Things模型： 进展顺利的方面 + 存在问题的方面 + 我们的应对措施
指标层级： 北极星指标（1个）→ 驱动指标（3-5个）→ 健康指标（3-5个）→ 红色预警指标（2-3个阈值）
坏消息沟通流程： 提前48-72小时与首席董事预沟通 → 向全体董事会发送提醒邮件 → 发生了什么 → 原因 → 影响 → 应对计划 → 后续每次会议跟进
月度投资者更新： 要点摘要（3个要点）→ 相同的指标表格 → 重要更新（2-3个）→ 具体需求（1-2个）
沟通传递机制： 高管团队（每周）→ 扩展领导团队（每两周）→ 全员会议（每月）→ 团队层面（持续进行）

Related Skills

相关技能

  • operating-cadence: Internal meeting rhythms that feed board preparation
  • enterprise-account-planning: Pipeline and deal metrics for board reporting
  • technical-product-pricing: Pricing decisions that require board input
Based on preparing and supporting board communications across multiple companies from Series A through post-IPO — building the deck and sitting in the room at some, reporting updates to the board at others. Includes the investor update cadence that maintained trust through missed quarters, the "Three Things" narrative model used across multiple companies, and the metric discipline framework that survived years of hypergrowth. Not theory — patterns from being close enough to the board to see what lands and what doesn't.
  • operating-cadence: 为董事会筹备提供支持的内部会议节奏
  • enterprise-account-planning: 用于董事会汇报的pipeline及交易指标
  • technical-product-pricing: 需要董事会审批的定价决策
基于为从A轮到上市后多家公司筹备及支持董事会沟通的经验——有的公司是准备演示文稿并参会，有的是向董事会汇报更新内容。包含在未达成目标的季度中仍能保持信任的投资者更新节奏、被多家公司采用的“Three Things”叙事模型，以及在多年高速增长中持续有效的指标管理框架。这不是理论——是近距离观察董事会反应后总结出的可行模式。