board-deck-builder

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Board Deck Builder

Board Deck 制作指南

Build board decks that tell a story, not just show data. Every section has an owner, a narrative, and a "so what." Boards see 10+ decks per quarter -- yours needs a through-line.

制作能够讲述故事而非仅展示数据的董事会演示文稿。每个部分都有负责人、叙事逻辑和核心价值（so what）。董事会每季度要审阅10+份演示文稿——你的文稿需要有清晰的主线。

Keywords

关键词

board deck, investor update, board meeting, board pack, investor relations, quarterly review, board presentation, fundraising deck, investor deck, board narrative, QBR, quarterly business review, board report, metrics dashboard, bad news delivery, variance explanation

Deck Types and Structure

演示文稿类型与结构

Deck Type Selection

演示文稿类型选择

Type	When	Slide Count	Sent in Advance	Key Section
Quarterly Board Deck	Standard board meeting	20-30 slides	48 hours ahead	Full deck below
Monthly Update	Early-stage boards	8-12 slides	24 hours ahead	Metrics + risks
Fundraising Deck	Active fundraise	12-15 slides	During meeting	Vision + traction
Emergency/Ad-hoc	Crisis or major decision	5-8 slides	Depends	Situation + options

类型	适用场景	幻灯片数量	是否提前发送	核心板块
季度董事会演示文稿	常规董事会会议	20-30页	提前48小时	以下完整板块
月度更新演示文稿	早期阶段董事会	8-12页	提前24小时	指标+风险
募资演示文稿	正在进行的募资活动	12-15页	会议期间发送	愿景+业务进展
紧急/临时演示文稿	危机或重大决策场景	5-8页	视情况而定	现状+可选方案

Standard Board Deck (Section by Section)

标准董事会演示文稿（逐板块详解）

Section 1: Executive Summary (CEO)

板块1：执行摘要（CEO负责）

Three sentences. No more. No less.

Sentence	Purpose	Example
1	State of the business	"We closed Q3 at $2.4M ARR, up 22% QoQ"
2	Biggest development this period	"Signed our largest enterprise contract ($180K ACV)"
3	Forward-looking priority	"Q4 priority: close Series A and hit $2.8M ARR"

Anti-pattern: "We had a good quarter with lots of progress across all areas." Why it fails: Says nothing. Board learns nothing. Time wasted.

三句话，不多不少。

句子	目的	示例
1	说明业务现状	"Q3我们的ARR达到240万美元，环比增长22%"
2	本季度最重大进展	"签署了我们最大的企业客户合同（ACV 18万美元）"
3	未来优先级	"Q4核心目标：完成A轮融资，ARR达到280万美元"

反模式："我们这季度表现不错，各方面都有很多进展。" 问题所在：没有实质内容，董事会无法获取有效信息，浪费时间。

Section 2: Key Metrics Dashboard (COO)

板块2：核心指标仪表盘（COO负责）

6-8 metrics maximum. Every metric needs a target and a status.

Metric	This Period	Last Period	Target	Status	Trend
ARR	$2.4M	$1.97M	$2.3M	[G]	Up
MoM Growth	8.1%	7.2%	7.5%	[G]	Up
Burn Multiple	1.8x	2.1x	< 2x	[G]	Improving
NRR	112%	108%	> 110%	[G]	Up
CAC Payback	11 mo	14 mo	< 12 mo	[G]	Improving
Headcount	24	21	25	[Y]	Below plan

Rule: Only show metrics the board actually tracks. Ask what they care about. Remove anything they have said they do not care about.

最多展示6-8个指标，每个指标都需要包含目标值和状态。

指标	本季度数值	上季度数值	目标值	状态	趋势
ARR	240万美元	197万美元	230万美元	[G]	上升
月环比增长率	8.1%	7.2%	7.5%	[G]	上升
烧钱倍数	1.8x	2.1x	< 2x	[G]	改善
NRR	112%	108%	> 110%	[G]	上升
CAC回收期	11个月	14个月	< 12个月	[G]	改善
员工人数	24人	21人	25人	[Y]	低于计划

规则：仅展示董事会实际关注的指标。询问他们的关注点，移除任何他们明确表示不关心的内容。

Section 3: Financial Update (CFO)

板块3：财务更新（CFO负责）

Component	Include	Format
P&L Summary	Revenue, COGS, Gross Margin, OpEx, Net Burn	Table with variance column
Cash Position	Current balance + runway in months	Single number, bold
Burn Multiple Trend	3-quarter trend	Line chart
Variance to Plan	Each line item vs. budget	Table with one-sentence explanations
Forecast Update	Next quarter projections	Conservative, base, upside

Rule: Every variance needs a one-sentence explanation. "Revenue was below target" with no explanation is unacceptable.

组成部分	包含内容	格式
损益表摘要	收入、销货成本、毛利率、运营费用、净烧钱	带差异列的表格
现金状况	当前余额+可用运营月数	加粗的单个数值
烧钱倍数趋势	连续3个季度的趋势	折线图
与计划的差异	每个项目与预算的对比	带一句话解释的表格
预测更新	下季度预测值	保守值、基准值、乐观值

规则：每个差异都需要一句话解释。仅说“收入低于目标”而无解释是不可接受的。

Section 4: Revenue and Pipeline (CRO)

板块4：收入与销售漏斗（CRO负责）

Component	Include	Format
ARR Waterfall	Opening -> New -> Expansion -> Contraction -> Churn -> Closing	Waterfall chart
NRR and Logo Churn	Current + 4-quarter trend	Table + trend line
Pipeline by Stage	Dollar amounts, not just counts	Funnel visualization
Forecast	Next quarter with confidence level	"High confidence $2.6M, upside to $2.9M"
Top 3 Deals	Name, amount, close date, risk	Table

Rule: Forecast MUST include a confidence level. "We expect $2.8M" is weak.

组成部分	包含内容	格式
ARR waterfall	期初值 -> 新增 -> 扩容 -> 收缩 -> 流失 -> 期末值	瀑布图
NRR与客户流失	当前值+连续4个季度趋势	表格+趋势线
各阶段销售漏斗	金额（而非仅数量）	漏斗可视化图
预测	下季度预测值及置信度	"高置信度260万美元，乐观值290万美元"
前3大重点交易	客户名称、金额、预计关闭日期、风险	表格

规则：预测必须包含置信度。仅说“我们预计达到280万美元”是不够的。

Section 5: Product Update (CPO)

板块5：产品更新（CPO负责）

Component	Include	Format
Shipped This Quarter	3-5 items with user impact	Bullet list
Shipping Next Quarter	3-5 items with target dates	Bullet list
PMF Signals	NPS trend, DAU/MAU, feature adoption	Metrics table
Key Learning	One insight from customer research	Narrative paragraph

Rule: No feature lists. Only features with evidence of user impact.

组成部分	包含内容	格式
本季度已上线功能	3-5个带用户影响说明的功能	项目符号列表
下季度计划上线功能	3-5个带目标日期的功能	项目符号列表
PMF信号	NRR趋势、日活/月活、功能采用率	指标表格
核心洞察	来自客户调研的一个关键结论	叙事段落

规则：不要只列功能清单，仅展示有用户影响证据的功能。

Section 6: Growth and Marketing (CMO)

板块6：增长与营销（CMO负责）

Component	Include
CAC by Channel	Table with efficiency trend
Pipeline Contribution	$ by channel
What's Working	Specific channels/campaigns with data
What's Being Cut	Underperforming channels
What's Being Tested	New experiments with hypothesis

组成部分	包含内容
各渠道CAC	带效率趋势的表格
销售漏斗贡献	各渠道带来的金额
有效策略	带数据支撑的特定渠道/活动
拟取消策略	表现不佳的渠道
测试中策略	带假设的新实验

Section 7: Engineering and Technical (CTO)

板块7：工程与技术（CTO负责）

Component	Include
Delivery Velocity	4-quarter trend
Tech Debt Ratio	Current + plan to address
Infrastructure	Uptime, incidents, cost trend
Security Posture	One line unless there is a material issue

Rule: Keep this short unless there is a material issue. Boards do not need sprint details.

组成部分	包含内容
交付速度	连续4个季度趋势
技术债务占比	当前值+解决计划
基础设施	可用性、事故、成本趋势
安全状况	一句话概述（除非有重大问题）

规则：除非有重大问题，否则保持内容简洁。董事会不需要了解迭代细节。

Section 8: Team and People (CHRO)

板块8：团队与人力（CHRO负责）

Component	Include
Headcount	Actual vs. plan
Hiring	Offers out, pipeline, time-to-fill trend
Attrition	Regrettable vs. non-regrettable
Engagement	Latest survey score and trend
Notable	Key hires, key departures, key open roles

组成部分	包含内容
员工人数	实际值 vs 计划值
招聘进展	已发出offer、候选人漏斗、招聘周期趋势
人员流失	遗憾流失 vs 非遗憾流失
员工敬业度	最新调研分数及趋势
重点事项	关键招聘、关键离职、核心空缺岗位

Section 9: Risk and Security (CISO)

板块9：风险与安全（CISO负责）

Component	Include
Security Posture	Status of critical controls
Compliance	Certifications in progress, deadlines
Incidents	This quarter (if any): impact, resolution, prevention
Top 3 Risks	Risk description + mitigation status

组成部分	包含内容
安全状况	关键控制措施的状态
合规性	正在推进的认证、截止日期
安全事件	本季度事件（如有）：影响、解决方案、预防措施
前3大风险	风险描述+缓解状态

Section 10: Strategic Outlook (CEO)

板块10：战略展望（CEO负责）

Component	Include
Next Quarter Priorities	3-5 items, ranked by importance
Board Decisions Needed	Specific votes or approvals
Asks	Specific, actionable requests

Rule: The "asks" section is the most important. "We'd like 3 warm introductions to CFOs at Series B companies" beats "any help would be appreciated."

组成部分	包含内容
下季度优先级	3-5个按重要性排序的事项
需要董事会决策的事项	具体投票或审批请求
诉求	具体、可执行的请求

规则：“诉求”板块是最重要的。“希望获得3个B轮公司CFO的推荐”远好于“任何帮助都将感激不尽”。

Section 11: Appendix

板块11：附录

Include but do not present unless asked:

Detailed financial model
Full pipeline data
Cohort retention charts
Customer case studies
Detailed headcount breakdown

包含以下内容但仅在被询问时展示：

详细财务模型
完整销售漏斗数据
用户留存 cohort 图表
客户案例
详细员工人数 breakdown

Narrative Framework

叙事框架

The 4-Act Structure

四幕结构

Every board deck should follow this through-line:

Act 1: WHERE WE SAID WE'D BE
  Last quarter's targets and commitments

Act 2: WHERE WE ACTUALLY ARE
  Honest assessment -- good and bad

Act 3: WHY THE GAP EXISTS
  One cause per variance. Not excuses -- explanations.

Act 4: WHAT WE'RE DOING ABOUT IT
  Specific, dated, owned actions

This works for good news AND bad news. It is credible because it acknowledges reality.

每份董事会演示文稿都应遵循以下主线：

Act 1: 我们承诺的目标
  上季度的目标与承诺

Act 2: 我们实际的成果
  诚实评估——包括好消息和坏消息

Act 3: 差异原因
  每个差异对应一个原因，不是借口，而是解释

Act 4: 我们的解决方案
  具体、有截止日期、有负责人的行动

该结构适用于好消息和坏消息，因其承认现实而具有可信度。

Opening Frame

开场框架

The board should know the key message by slide 3, not slide 30.

Good Opening	Bad Opening
"We beat ARR target by 8% and NRR hit 112%"	"Let me walk you through our quarter..."
"We missed revenue by $300K. Here's why and the fix."	"First, some context about market conditions..."
"We need a board vote on the acquisition opportunity"	"Before we get to the main topic, some updates..."

董事会应在第3页而非第30页就了解核心信息。

优秀开场	糟糕开场
"我们的ARR超出目标8%，NRR达到112%"	"让我带大家回顾我们的季度..."
"我们的收入低于目标30万美元，以下是原因和解决方案"	"首先，介绍一下市场环境..."
"需要董事会就收购机会进行投票"	"在进入正题前，先看一些更新..."

Delivering Bad News

坏消息传达

The SOUF Framework

SOUF框架

Step	What	Example
State	State it plainly	"We missed Q3 ARR target by $300K (12% gap)"
Own	Own the cause	"Primary driver: longer enterprise sales cycle than modeled"
Understand	Show you understand it	"Analyzed 8 stalled deals; pattern is procurement delays"
Fix	Present the fix	"Three changes: [specific, dated], revised Q4 target: $2.6M"

步骤	内容	示例
State	直白陈述	"我们Q3的ARR低于目标30万美元（差距12%）"
Own	承担责任	"主要原因：企业销售周期比模型预测的更长"
Understand	展示你已分析原因	"分析了8个停滞的交易，发现共性是采购流程延迟"
Fix	提出解决方案	"三项调整：[具体、有截止日期的措施]，修订后的Q4目标：260万美元"

Bad News Anti-Patterns

坏消息传达反模式

Anti-Pattern	Why It Fails	Better Approach
Leading with good news to soften	Boards notice and distrust framing	Lead with the most important thing
"Market conditions" as cause	That is context, not a cause	Name specific, controllable causes
Fix without data	Board does not trust unfounded fixes	Show analysis behind the fix
Revised forecast without assumptions	Looks like guessing	Show bottom-up build

反模式	问题所在	改进方案
先用好消息铺垫	董事会会注意到并质疑你的立场	直接展示最重要的信息
以“市场环境”为原因	这是背景而非原因	明确具体的、可控的原因
无数据支撑的解决方案	董事会不会相信无依据的方案	展示方案背后的分析
无假设的修订预测	看起来像猜测	展示自下而上的推导过程

Common Board Deck Mistakes

董事会演示文稿常见误区

Mistake	Fix
Too many slides (> 25)	Cut ruthlessly. If you can not explain it, the slide is wrong.
Metrics without targets	Every metric needs a target and a status indicator
No narrative	Data without story forces boards to draw conclusions
Burying bad news	Lead with it, own it, fix it
Vague asks	Specific, actionable, person-assigned asks only
No variance explanation	Every gap from target needs a one-sentence cause
Stale appendix	Appendix is only useful if current
Designed for reader, not room	Decks are presented -- they must work spoken aloud
Inconsistent formatting	Use one template, one color scheme, one font
Too much text per slide	Max 6 lines per slide. Use speaker notes for detail.

误区	解决方案
幻灯片过多（>25页）	果断删减。如果你无法解释清楚，说明这页内容有问题。
指标无目标值	每个指标都需要目标值和状态标识
无叙事逻辑	仅展示数据会让董事会自行推导结论
隐藏坏消息	直接展示、承担责任、提出解决方案
诉求模糊	仅提出具体、可执行、有负责人的诉求
差异无解释	每个与目标的差距都需要一句话说明原因
附录内容过时	附录只有内容最新才有价值
仅为阅读设计而非演讲设计	演示文稿是用来讲解的——必须适合口头陈述
格式不一致	使用统一模板、配色方案和字体
单页文字过多	每页最多6行文字，细节放在演讲者备注里

Cadence Notes

时间节奏说明

Type	Timing	Length	Advance Send
Quarterly (standard)	48 hours before meeting	20-30 slides	48 hours
Monthly (early-stage)	24 hours before meeting	8-12 slides	24 hours
Fundraising	In the meeting	12-15 slides	Sometimes not shared

类型	时间	长度	提前发送时间
季度（标准）	会议前48小时	20-30页	48小时
月度（早期阶段）	会议前24小时	8-12页	24小时
募资	会议期间	12-15页	有时不提前分享

Deck Assembly Workflow

演示文稿制作流程

T-14 days: CEO sets agenda, identifies key messages
T-10 days: Section owners begin drafting their sections
T-7 days:  First drafts due. CEO reviews for narrative alignment.
T-5 days:  Second drafts. CFO validates all numbers.
T-3 days:  Final deck assembly. Narrative check.
T-2 days:  Send to board. Include cover note with 3 key takeaways.
T-0:       Meeting. CEO presents. Section owners available for questions.

T-14天：CEO设定议程，确定核心信息
T-10天：各板块负责人开始起草内容
T-7天：  初稿提交，CEO审阅叙事一致性
T-5天：  二稿提交，CFO验证所有数据
T-3天：  最终文稿整合，叙事检查
T-2天：  发送给董事会，附上包含3个核心要点的封面说明
T-0:       会议，CEO主讲，各板块负责人准备答疑

Red Flags

与C-suite的协作

Deck assembled night before the meeting -- no time for review or narrative alignment
Numbers in deck do not match financial model -- credibility destroyer
No asks section -- wasting board meeting time
Same deck format for 4+ quarters with no iteration -- not responsive to feedback
Board members surprised by information -- they should never learn bad news in the meeting
More than 30 slides -- attention lost after slide 20
No follow-up on previous meeting's action items -- accountability gap

每个板块由特定C-suite职位负责：

板块	负责人	关联技能
执行摘要	CEO	`ceo-advisor`
指标仪表盘	COO	`coo-advisor`
财务更新	CFO	`cfo-advisor`
收入/销售漏斗	CRO	`cro-advisor`
产品更新	CPO	`cpo-advisor`
增长/营销	CMO	`cmo-advisor`
工程	CTO	`cto-advisor`
团队/人力	CHRO	`chro-advisor`
风险/安全	CISO	`ciso-advisor`
战略展望	CEO	`ceo-advisor`

Integration with C-Suite

输出成果

Each section is owned by a specific C-suite role:

Section	Owner	Reference Skill
Executive Summary	CEO	`ceo-advisor`
Metrics Dashboard	COO	`coo-advisor`
Financial Update	CFO	`cfo-advisor`
Revenue/Pipeline	CRO	`cro-advisor`
Product Update	CPO	`cpo-advisor`
Growth/Marketing	CMO	`cmo-advisor`
Engineering	CTO	`cto-advisor`
Team/People	CHRO	`chro-advisor`
Risk/Security	CISO	`ciso-advisor`
Strategic Outlook	CEO	`ceo-advisor`

请求	交付物
"准备董事会演示文稿"	完整的文稿大纲，包含板块负责人和数据要求
"月度投资者更新"	精简版更新：指标、亮点、风险、诉求
"优化叙事逻辑"	四幕叙事结构及核心信息
"传达坏消息"	针对特定场景应用SOUF框架的方案
"募资演示文稿"	以愿景为核心的文稿，包含业务进展、团队、市场、诉求
"审阅我的董事会演示文稿"	基于最佳实践的评审，指出差距

Output Artifacts

工具参考

—

deck_structure_validator.py

Request	Deliverable
"Prepare the board deck"	Complete deck outline with section owners and data requirements
"Monthly investor update"	Condensed update: metrics, highlights, risks, asks
"Help with the narrative"	4-act narrative structure with key messages
"Deliver bad news"	SOUF framework applied to specific situation
"Fundraising deck"	Vision-led deck with traction, team, market, ask
"Review my board deck"	Critique against best practices, identify gaps

根据最佳实践的板块要求，验证董事会演示文稿的完整性。

bash

undefined

Tool Reference

使用演示数据验证

deck_structure_validator.py

—

Validates board deck completeness against best-practice section requirements.

bash

undefined

python scripts/deck_structure_validator.py

Validate with demo data

根据演示文稿类型和幻灯片数量验证

python scripts/deck_structure_validator.py

python scripts/deck_structure_validator.py --type quarterly --slides 24

Validate specific deck type with slide count

根据板块列表验证

python scripts/deck_structure_validator.py --type quarterly --slides 24

python scripts/deck_structure_validator.py --sections executive_summary metrics_dashboard financial_update

Validate with section list

从JSON文件验证

python scripts/deck_structure_validator.py --sections executive_summary metrics_dashboard financial_update

python scripts/deck_structure_validator.py --input deck.json

Validate from JSON file

输出JSON结果

python scripts/deck_structure_validator.py --input deck.json

python scripts/deck_structure_validator.py --input deck.json --json

undefined

JSON output

metrics_dashboard_generator.py

python scripts/deck_structure_validator.py --input deck.json --json

undefined

生成格式化的、适合董事会的指标仪表盘，包含RAG状态和趋势。

bash

undefined

metrics_dashboard_generator.py

生成演示仪表盘

Generates formatted board-ready metrics dashboards with RAG status and trends.

bash

undefined

python scripts/metrics_dashboard_generator.py

Generate demo dashboard

从JSON指标文件生成

python scripts/metrics_dashboard_generator.py

python scripts/metrics_dashboard_generator.py --input metrics.json

From JSON metrics file

从CSV文件生成

python scripts/metrics_dashboard_generator.py --input metrics.json

python scripts/metrics_dashboard_generator.py --csv metrics.csv

From CSV file

输出JSON结果

python scripts/metrics_dashboard_generator.py --csv metrics.csv

python scripts/metrics_dashboard_generator.py --json

undefined

JSON output

board_prep_checklist.py

python scripts/metrics_dashboard_generator.py --json

undefined

生成董事会会议筹备的倒计时任务清单。

bash

undefined

board_prep_checklist.py

生成会议前14天的任务清单

Generates T-minus timeline checklists for board meeting preparation.

bash

undefined

python scripts/board_prep_checklist.py

Generate checklist for meeting 14 days out

指定会议日期和已完成任务

python scripts/board_prep_checklist.py

python scripts/board_prep_checklist.py --meeting-date 2026-04-15 --completed agenda_set topics_confirmed

Specific meeting date with completed tasks

列出所有任务ID

python scripts/board_prep_checklist.py --meeting-date 2026-04-15 --completed agenda_set topics_confirmed

python scripts/board_prep_checklist.py --list-tasks

List all task IDs

输出JSON结果

python scripts/board_prep_checklist.py --list-tasks

python scripts/board_prep_checklist.py --meeting-date 2026-04-15 --json

---

JSON output

故障排除

python scripts/board_prep_checklist.py --meeting-date 2026-04-15 --json

---

问题	可能原因	解决方案
董事会成员询问演示文稿中已包含的基础问题	演示文稿发送太晚或不够通俗易懂	提前48小时以上发送，附上包含3个核心要点的封面说明；确保文稿可独立阅读
不同板块的财务数据不一致	没有CFO交叉验证步骤	添加T-5天的CFO验证 checkpoint；所有指标使用单一数据源
会议前期板块耗时过长导致超时	演示文稿细节过多，未设置时间限制	强制每页最多6行文字；细节放在演讲者备注里；指定计时员
董事会成员对坏消息感到意外	未在会前一对一沟通中提前告知	CEO在会前与每位董事会成员单独沟通重大问题
诉求板块未产生后续行动	诉求模糊（如“任何帮助都感激不尽”）	提出具体、明确、有指向性的诉求（如“3个B轮公司CFO的推荐”）
连续4个季度使用相同文稿格式未改进	没有会后反馈机制	在会议结束时评估文稿有效性；每个季度迭代一个板块
附录从未被提及	附录内容过时或与当前议程无关	每次会议前更新附录；移除连续2个季度无人询问的数据

Troubleshooting

成功标准

Problem	Likely Cause	Fix
Board members ask basic questions answered in the deck	Deck not sent far enough in advance or not self-explanatory	Send 48+ hours ahead with a 3-takeaway cover note; ensure deck reads standalone
Financial numbers don't match across sections	No CFO cross-validation step	Add T-5 day CFO validation checkpoint; single source of truth for all metrics
Meeting runs over time on early sections	Too much detail in presenter slides, no time boxing	Enforce max 6 lines per slide; use speaker notes for depth; assign timekeeper
Board members surprised by bad news	Information not previewed in 1:1 pre-calls	CEO pre-briefs each board member on material issues before the meeting
Asks section produces no follow-through	Asks are vague ("any help appreciated")	Make asks specific, named, and actionable ("3 warm intros to Series B CFOs")
Same deck format for 4+ quarters with no improvement	No post-meeting feedback loop	Rate deck effectiveness at meeting end; iterate one section per quarter
Appendix never referenced	Appendix is stale or not relevant to current agenda	Update appendix before every meeting; remove data nobody has asked about in 2+ quarters

80%以上的会议中，董事会成员提前阅读了演示文稿（通过会前收到的问题数量衡量）
70%以上的会议时间用于战略讨论而非状态更新，且会议不超时
每次董事会会议至少产生2个有负责人和截止日期的已记录决策
坏消息在会议中永远不会是意外——所有重大问题都通过会前一对一沟通提前告知
董事会NPS（非正式季度调查）在会议实用性上得分8+/10
90%以上的季度中，演示文稿在T-2天前完成，无最后一刻的慌乱
上一次会议的行动项在下次会议中的完成率达到80%以上

Success Criteria

范围与限制

Board members report reading the deck in advance in 80%+ of meetings (measured by pre-meeting questions received)
Meeting stays within time allocation with 70%+ of time on strategic discussion, not status updates
Every board meeting produces at least 2 logged decisions with named owners and deadlines
Bad news is never a surprise in the meeting -- all material issues previewed via 1:1 pre-calls
Board NPS (informal quarterly check) scores 8+/10 on meeting usefulness
Deck assembly completes by T-2 days with zero last-minute scrambles in 90%+ of quarters
Action items from previous meeting have 80%+ completion rate reported at the next meeting

包含范围：董事会演示文稿结构、板块模板、叙事框架、坏消息传达、指标仪表盘、文稿制作流程、董事会筹备清单、质量验证。

排除范围：实际财务数据收集、幻灯片设计/视觉格式、董事会成员关系管理、法律治理要求、委托声明准备、监管申报。

限制：本技能提供结构和流程，但无法替代制作董事会叙事所需的判断。文稿结构验证器仅检查完整性，不检查内容质量。指标仪表盘工具根据提供的数据计算RAG状态，但不获取实时指标。

Scope & Limitations

集成点

In Scope: Board deck structure, section templates, narrative frameworks, bad news delivery, metrics dashboards, deck assembly workflows, board prep checklists, quality validation.

Out of Scope: Actual financial data collection, slide design/visual formatting, board member relationship management, legal governance requirements, proxy statement preparation, regulatory filings.

Limitations: This skill provides structure and process but cannot replace the judgment required for crafting board narratives. The deck structure validator checks completeness, not quality of content. Metrics dashboard tools calculate RAG status from provided data but do not source live metrics.

技能	集成方式
`ceo-advisor`	执行摘要和战略展望板块；整体叙事方向
`cfo-advisor`	财务更新板块；所有数据通过CFO工具验证
`cro-advisor`	收入与销售漏斗板块；ARR waterfall和预测置信度
`cmo-advisor`	增长/营销板块；各渠道CAC、营销ROI数据
`chro-advisor`	团队/人力板块；员工人数、流失率、敬业度指标
`ciso-advisor`	风险/安全板块；安全状况、合规状态
`board-meeting`	文稿纳入六阶段董事会会议流程
`chief-of-staff`	筹备清单协调；板块负责人统筹
`company-os`	计分卡指标直接流入指标仪表盘板块

Integration Points

—

Skill	Integration
`ceo-advisor`	Executive summary and strategic outlook sections; overall narrative direction
`cfo-advisor`	Financial update section; all numbers validated through CFO tools
`cro-advisor`	Revenue and pipeline section; ARR waterfall and forecast confidence
`cmo-advisor`	Growth/marketing section; CAC by channel, marketing ROI data
`chro-advisor`	Team/people section; headcount, attrition, engagement metrics
`ciso-advisor`	Risk/security section; security posture, compliance status
`board-meeting`	Deck feeds into the 6-phase board meeting protocol
`chief-of-staff`	Prep checklist coordination; section owner orchestration
`company-os`	Scorecard metrics flow directly into the metrics dashboard section

—