company-os

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Company Operating System

企业操作系统

The operating system is the collection of tools, rhythms, and agreements that determine how the company functions. Every company has one -- most just do not know what it is. Making it explicit makes it improvable.

企业操作系统是决定企业运作方式的工具、节奏与共识的集合。每家企业都有一套——只是大多数不知道它是什么。将其明确化才能加以优化。

Keywords

关键词

operating system, EOS, Entrepreneurial Operating System, Scaling Up, Rockefeller Habits, OKR, Holacracy, L10 meeting, rocks, scorecard, accountability chart, issues list, IDS, meeting pulse, quarterly planning, weekly scorecard, management framework, company rhythm, traction, annual planning, communication cadence

Operating System Selection

操作系统选型

Decision Tree

决策树

START: "Which operating system?"
  |
  v
[Company size?]
  |
  +-- 10-50 people
  |     |
  |     v
  |   [Is the founder operational or visionary?]
  |     |
  |     +-- Operational --> EOS / Traction (structured, simple)
  |     +-- Visionary --> Scaling Up (ambitious, strategy-heavy)
  |
  +-- 50-200 people
  |     |
  |     v
  |   [Engineering-led or sales-led?]
  |     |
  |     +-- Engineering-led --> OKR-native (hypothesis-driven)
  |     +-- Sales-led --> Scaling Up or EOS (execution-focused)
  |
  +-- 200+ people
  |     |
  |     v
  |   [High autonomy or high alignment needed?]
  |     |
  |     +-- High autonomy --> Holacracy (only if patient)
  |     +-- High alignment --> Custom hybrid (best of EOS + OKR)
  |
  +-- Not sure --> Start with EOS. It is the simplest to implement.

START: "Which operating system?"
  |
  v
[Company size?]
  |
  +-- 10-50 people
  |     |
  |     v
  |   [Is the founder operational or visionary?]
  |     |
  |     +-- Operational --> EOS / Traction (structured, simple)
  |     +-- Visionary --> Scaling Up (ambitious, strategy-heavy)
  |
  +-- 50-200 people
  |     |
  |     v
  |   [Engineering-led or sales-led?]
  |     |
  |     +-- Engineering-led --> OKR-native (hypothesis-driven)
  |     +-- Sales-led --> Scaling Up or EOS (execution-focused)
  |
  +-- 200+ people
  |     |
  |     v
  |   [High autonomy or high alignment needed?]
  |     |
  |     +-- High autonomy --> Holacracy (only if patient)
  |     +-- High alignment --> Custom hybrid (best of EOS + OKR)
  |
  +-- Not sure --> Start with EOS. It is the simplest to implement.

Framework Comparison Matrix

框架对比矩阵

Feature	EOS	Scaling Up	OKR-Native	Holacracy
Complexity	Low	Medium	Medium	High
Implementation time	30-90 days	90-180 days	60-120 days	6-12 months
Best company size	10-250	50-500	20-500	50-300
Goal framework	Rocks (binary)	OKRs + Priorities	OKRs (graded)	Roles + accountabilities
Meeting cadence	Weekly L10	Daily huddle + weekly	Weekly + quarterly	Governance + tactical
Issue resolution	IDS	Keep/Kill/Combine	Retrospective	Governance process
Accountability	Accountability chart	Function accountability	OKR ownership	Role-based
Scorecard	Weekly numbers	Weekly KPIs	Quarterly KRs	Metrics per role
Strengths	Simple, fast to implement	Rigorous, strategy-heavy	Flexible, tech-friendly	Distributed authority
Weaknesses	Can feel rigid	Complex, requires discipline	Can drift without structure	Steep learning curve

特性	EOS	Scaling Up	原生OKR	Holacracy
复杂度	低	中	中	高
实施周期	30-90天	90-180天	60-120天	6-12个月
适配企业规模	10-250人	50-500人	20-500人	50-300人
目标框架	Rocks（二元判定）	OKRs + 优先级	OKRs（分级判定）	角色+问责
会议节奏	每周L10会议	每日站会+周会	周会+季度会	治理会议+战术会议
问题解决流程	IDS	保留/淘汰/合并	回顾会议	治理流程
问责机制	问责图表	职能问责	OKR负责人	基于角色
计分卡	周度数据	周度KPI	季度KR	角色维度指标
优势	简洁、实施快速	严谨、侧重战略	灵活、适配技术团队	分布式权限
劣势	可能显得僵化	复杂、需要纪律性	缺乏结构易偏离	学习曲线陡峭

The Six Core Components

六大核心组件

Every effective operating system has these six, regardless of framework:

无论采用哪种框架，有效的企业操作系统都包含以下六大组件：

Component 1: Accountability Chart

组件1：问责图表

Not an org chart. An accountability chart answers: "Who owns this outcome?"

这不是组织结构图。问责图表要回答的是：“谁对这个结果负责？”

Design Principles

设计原则

Principle	Implementation
Single ownership	One person owns each function. Multiple may work in it.
Explicit gaps	Functions nobody owns are identified and assigned.
No overlap	If two people think they own it, neither does. Resolve immediately.
Stage-appropriate	One person can own multiple seats early. Be explicit about it.
Quarterly review	Ownership shifts as company grows. Review every quarter.

原则	落地方式
单一负责人	每个职能由一人负责，多人可参与执行
明确空白职能	识别并分配无人负责的职能
无重叠	若两人都认为自己负责，则实际无人负责，需立即解决
适配发展阶段	早期一人可负责多个职能，需明确说明
季度复盘	随着企业发展，负责人会发生变化，每季度复盘一次

Accountability Chart Template

问责图表模板

CEO
  |
  +-- Revenue (CRO/VP Sales)
  |     +-- Inbound pipeline
  |     +-- Outbound pipeline
  |     +-- Customer success
  |
  +-- Product & Engineering (CTO/CPO)
  |     +-- Product roadmap
  |     +-- Engineering delivery
  |     +-- Technical operations
  |
  +-- Operations (COO)
  |     +-- Finance & legal
  |     +-- People operations
  |     +-- Business operations
  |
  +-- Marketing (CMO/VP Marketing)
        +-- Demand generation
        +-- Brand & content
        +-- Product marketing

CEO
  |
  +-- Revenue (CRO/VP Sales)
  |     +-- Inbound pipeline
  |     +-- Outbound pipeline
  |     +-- Customer success
  |
  +-- Product & Engineering (CTO/CPO)
  |     +-- Product roadmap
  |     +-- Engineering delivery
  |     +-- Technical operations
  |
  +-- Operations (COO)
  |     +-- Finance & legal
  |     +-- People operations
  |     +-- Business operations
  |
  +-- Marketing (CMO/VP Marketing)
        +-- Demand generation
        +-- Brand & content
        +-- Product marketing

Workshop Protocol (2 hours)

工作坊流程（2小时）

Step 1: List all functions the company performs (30 min)
Step 2: Assign ONE owner per function (30 min)
Step 3: Identify gaps (functions nobody owns) (15 min)
Step 4: Identify overlaps (2+ people claiming ownership) (15 min)
Step 5: Resolve gaps and overlaps (20 min)
Step 6: Publish and communicate (10 min)

Step 1: 列出企业所有职能（30分钟）
Step 2: 为每个职能分配唯一负责人（30分钟）
Step 3: 识别空白职能（无人负责的职能）（15分钟）
Step 4: 识别重叠职能（2人及以上声称负责的职能）（15分钟）
Step 5: 解决空白与重叠问题（20分钟）
Step 6: 发布并同步全员（10分钟）

Component 2: Scorecard

组件2：计分卡

Weekly metrics that tell you if the company is on track. Not monthly. Not quarterly. Weekly.

用于判断企业是否在正轨上的周度指标。不是月度，也不是季度，必须是周度。

Scorecard Rules

计分卡规则

Rule	Rationale
5-15 metrics maximum	More than 15 = nothing gets attention
Each metric has an owner	Ownership drives accountability
Each metric has a weekly target	Not a range -- a specific number
Red/Yellow/Green status	Not paragraphs -- traffic lights
Only Red metrics get discussion	Green = no discussion needed in meeting

规则	理由
最多5-15个指标	超过15个则无法聚焦重点
每个指标都有负责人	责任驱动问责
每个指标有周度目标	不是范围，而是具体数值
红/黄/绿状态标识	不用长篇描述，用交通灯式标识
仅讨论红色指标	绿色指标无需在会议中讨论

Example Scorecard

示例计分卡

Metric	Owner	Target	Week	Status
New MRR	CRO	$50K	$43K	[R]
Logo churn	CS Lead	< 1%	0.8%	[G]
Active users	CPO	2,000	2,150	[G]
Deployments	CTO	3/week	3	[G]
Critical bugs open	CTO	0	2	[R]
Runway	CFO	> 18mo	16mo	[Y]
Offer acceptance	CHRO	> 85%	90%	[G]

指标	负责人	目标	本周数据	状态
新增MRR	CRO	$50K	$43K	[R]
客户流失率	客户成功负责人	< 1%	0.8%	[G]
活跃用户数	CPO	2,000	2,150	[G]
部署次数	CTO	3次/周	3	[G]
未解决严重BUG数	CTO	0	2	[R]
现金流储备	CFO	> 18个月	16个月	[Y]
Offer接受率	CHRO	> 85%	90%	[G]

Component 3: Meeting Pulse

组件3：会议节奏

Full Meeting Rhythm

完整会议节奏

Meeting	Frequency	Duration	Who	Purpose
Daily standup	Daily	15 min	Each team	Blockers only
L10 / Leadership sync	Weekly	90 min	Leadership team	Scorecard + issues
Department review	Monthly	60 min	Dept + leadership	Deep dive on dept metrics
Quarterly planning	Quarterly	1-2 days	Leadership	Set rocks, review strategy
Annual planning	Annual	2-3 days	Leadership	1-year + 3-year vision

会议类型	频率	时长	参与人员	目的
每日站会	每日	15分钟	各团队成员	仅讨论阻塞问题
L10 / 领导层同步会	每周	90分钟	领导团队	计分卡复盘+问题解决
部门复盘会	每月	60分钟	部门成员+领导层	深度复盘部门指标
季度规划会	每季度	1-2天	领导团队	设置Rocks、复盘战略
年度规划会	每年	2-3天	领导团队	制定1年+3年愿景

L10 Meeting Agenda (Weekly Leadership)

L10会议议程（每周领导层会议）

Segment	Duration	Activity
Good news	5 min	Personal + business wins
Scorecard review	5 min	Flag red items only
Rock review	5 min	On/off track for each rock
Customer/employee headlines	5 min	Notable events
Issues list (IDS)	60 min	Identify, Discuss, Solve
To-dos review	5 min	Last week's commitments: done or not?
Conclude	5 min	Rate meeting 1-10, what would make it 10 next time

环节	时长	内容
好消息分享	5分钟	个人+业务成果
计分卡复盘	5分钟	仅标记红色指标
Rocks复盘	5分钟	每个Rocks的进度（是否在正轨）
客户/员工动态	5分钟	重要事件分享
问题列表（IDS）	60分钟	识别、讨论、解决
待办事项复盘	5分钟	上周承诺事项：完成与否？
会议总结	5分钟	为会议打分1-10，提出改进建议

Component 4: Issue Resolution (IDS)

组件4：问题解决流程（IDS）

Maximum 15 minutes per issue. This is the core problem-solving loop.

IDENTIFY: What is the actual issue? (One sentence, root cause, not symptom)
  |
DISCUSS: Relevant facts + perspectives. Time-boxed.
  |       When discussion starts repeating, STOP.
  |
SOLVE: One owner. One action. One due date. Written down.

每个问题最多耗时15分钟。这是核心问题解决循环。

IDENTIFY: 实际问题是什么？（一句话描述，聚焦根本原因而非症状）
  |
DISCUSS: 相关事实+多方观点。限时讨论。
  |       当讨论开始重复时，立即停止。
  |
SOLVE: 指定一名负责人、一项行动、一个截止日期。书面记录。

IDS Anti-Patterns

IDS反模式

Anti-Pattern	Why It Fails	Fix
"Let's take this offline"	Things taken offline rarely get resolved	Solve it now or put it on next week's list
Discussing without deciding	Great discussion, no action item = wasted	Every discussion must end with a decision
Revisiting decided issues	Undermines the system	Once solved, off the list. Reopen only with new data.
Issue on list 3+ meetings	Either not real or too scary to address	Force it: address this week or remove it
Multiple issues conflated	Impossible to solve a bundled problem	One issue per entry. Separate if needed.

反模式	失败原因	解决方案
“我们线下讨论”	线下讨论的问题很少能得到解决	现在解决或列入下周问题列表
只讨论不决策	讨论充分但无行动项=浪费时间	每次讨论必须以决策收尾
重提已解决问题	破坏体系权威性	解决后移出列表，仅当有新数据时才可重新提出
问题连续3次出现在列表中	要么不是真问题，要么是不敢直面的结构性问题	强制处理：本周解决或永久移除
多个问题混为一谈	无法解决捆绑式问题	每个条目对应一个问题，必要时拆分

Component 5: Rocks (90-Day Priorities)

组件5：90天核心任务（Rocks）

Rock Rules

Rocks规则

Rule	Rationale
3-7 per person maximum	More than 7 = none get done
3-7 company-level rocks	Shared leadership priorities
Binary status: done or not done	No "60% complete"
Set at quarterly planning	Reviewed weekly (on/off track)
Not a to-do list	Rocks take 90 days of sustained work

规则	理由
每人最多3-7个	超过7个则无法完成任何一个
公司层面最多3-7个	领导层共同优先级
二元状态：完成或未完成	没有“完成60%”的说法
季度规划时设置	每周复盘（是否在正轨）
不是待办清单	Rocks需要90天持续推进

Good vs. Bad Rocks

优质Rocks vs 劣质Rocks

Bad Rock	Why	Good Rock
"Improve sales process"	Not measurable or specific	"Implement CRM with pipeline stages and reporting by Mar 31"
"Hire more engineers"	No target, no deadline	"Hire 3 senior engineers with offers accepted by Apr 15"
"Reduce churn"	No target	"Reduce monthly logo churn from 3% to 1.5% by end of Q2"
"Get better at communication"	Not observable	"Ship weekly company update every Friday for 12 weeks"

劣质Rocks	问题所在	优质Rocks
“优化销售流程”	无法衡量、不够具体	“3月31日前完成CRM部署，包含销售管道阶段与报表功能”
“招聘更多工程师”	无目标、无截止日期	“4月15日前完成3名高级工程师的Offer发放与接受”
“降低流失率”	无具体目标	“第二季度末将月度客户流失率从3%降至1.5%”
“提升沟通效率”	无法量化观察	“连续12周每周五发布公司周报”

Component 6: Communication Cadence

组件6：沟通节奏

Audience	What	When	Format
All employees	Company update	Monthly	Written + Q&A
All employees	Quarterly results + priorities	Quarterly	All-hands meeting
Leadership team	Scorecard	Weekly	Dashboard
Board	Company performance	Monthly or quarterly	Board memo/deck
Investors	Key metrics + narrative	Monthly or quarterly	Investor update
Customers	Product updates	Per release	Release notes

Default rule: If deciding whether to share internally, share it. Under-communication always costs more than over-communication.

受众	内容	频率	形式
全体员工	公司更新	每月	书面+问答环节
全体员工	季度业绩+优先级	每季度	全员大会
领导团队	计分卡	每周	仪表盘
董事会	公司业绩	每月/每季度	董事会备忘录/演示文稿
投资者	核心指标+业务叙事	每月/每季度	投资者更新报告
客户	产品更新	每次发布	版本说明

默认规则：当不确定是否要内部同步时，选择同步。沟通不足的成本永远高于过度沟通。

Implementation Roadmap

实施路线图

30-Day Quick Start

30天快速启动

Week	Activity	Time Investment
1	Build accountability chart	2-hour workshop
2	Define 5-10 weekly scorecard metrics	1-hour alignment session
3	Start weekly L10 meeting	90 min/week (ongoing)
4	Set first round of 90-day rocks	Half-day planning session

These four alone improve coordination more than most companies achieve in a year.

周	任务	时间投入
1	搭建问责图表	2小时工作坊
2	定义5-10个周度计分卡指标	1小时对齐会议
3	启动每周L10会议	每周90分钟（持续进行）
4	设置首批90天Rocks	半天规划会议

仅这四项就能让企业协作效率提升超过大多数公司一年的成果。

90-Day Full Implementation

90天完整实施

Month	Focus	Deliverables
1	Foundation	Accountability chart, scorecard, L10 meetings
2	Depth	Rocks defined, issues list active, daily standups
3	Cadence	Full meeting rhythm, communication cadence, first quarterly review

月	重点	交付成果
1	基础搭建	问责图表、计分卡、L10会议
2	深化落地	明确Rocks、激活问题列表、启动每日站会
3	固化节奏	完整会议节奏、沟通机制、首次季度复盘

Common Failure Modes

常见失败模式

Failure	Symptom	Fix
Partial implementation	"We do OKRs but skip check-ins"	Half an OS is worse than none. Commit to the full system.
Meeting fatigue	Added rhythm on top of existing meetings	Replace meetings, do not add them
Metric overload	30 KPIs because "they all matter"	Start with 5. Add only when cadence is established.
Rock inflation	12 rocks per person	Hard limit: 7 per person, 7 for the company.
Leader non-compliance	Leadership skips L10 or ignores IDS	The OS mirrors leadership respect. Leaders go first.
No quarterly review	Annual goals checked at year-end	Quarterly is the minimum review cycle.
Scorecard without targets	Tracking numbers without thresholds	Every metric needs a target to be actionable.

失败类型	症状	解决方案
部分实施	“我们做OKR但跳过复盘”	半吊子系统不如没有，承诺落地完整体系
会议疲劳	在现有会议基础上新增节奏	替换原有会议，而非叠加
指标过载	设置30个KPI因为“都重要”	从5个指标开始，仅当节奏稳定后再新增
Rocks膨胀	每人设置12个Rocks	严格限制：每人最多7个，公司层面最多7个
领导层不遵守	领导层跳过L10或无视IDS	体系的权威性取决于领导层，管理者必须以身作则
无季度复盘	年度目标仅在年底检查	季度是最低复盘周期
计分卡无目标	仅追踪数据无阈值	每个指标都需要目标才能具备可执行性

Red Flags

预警信号

Five team leads give different answers when asked "What are the top 3 company priorities?" -- alignment failure
Same issue on the issues list for 4+ weeks -- avoidance or structural problem
No weekly scorecard exists -- flying blind
Rocks set but never reviewed weekly -- goals without accountability
Accountability chart has not been updated in 6+ months -- reality has drifted
Meetings consistently end without decisions -- meeting design problem
Communication is all top-down, never bottom-up -- feedback loop broken

当被问及“公司前3优先级是什么”时，五位团队负责人给出不同答案——对齐失败
同一问题连续4周出现在问题列表中——回避问题或存在结构性问题
没有周度计分卡——盲目运营
设置了Rocks但从未每周复盘——目标缺乏问责
问责图表超过6个月未更新——与实际情况脱节
会议经常无决策收尾——会议设计存在问题
沟通全是自上而下，无自下而上反馈——反馈闭环断裂

Integration with C-Suite

与高管团队的整合

Role	OS Dependency
CEO ( `ceo-advisor` )	Sets vision that feeds 1-year plan and rocks
COO ( `coo-advisor` )	Owns meeting pulse and issue resolution cadence
CFO ( `cfo-advisor` )	Owns financial metrics in the scorecard
CTO ( `cto-advisor` )	Owns engineering rocks and tech scorecard metrics
CHRO ( `chro-advisor` )	Owns people metrics (attrition, hiring velocity)
Culture Architect ( `culture-architect` )	Culture rituals integrate into meeting pulse
Strategic Alignment ( `strategic-alignment` )	Validates team rocks cascade from company rocks
Change Management ( `change-management` )	New OS rollout follows ADKAR model

角色	与操作系统的关联
CEO ( `ceo-advisor` )	制定愿景，为1年规划与Rocks提供方向
COO ( `coo-advisor` )	负责会议节奏与问题解决流程
CFO ( `cfo-advisor` )	负责计分卡中的财务指标
CTO ( `cto-advisor` )	负责技术团队的Rocks与计分卡指标
CHRO ( `chro-advisor` )	负责人员指标（流失率、招聘速度）
文化架构师 ( `culture-architect` )	将文化仪式融入会议节奏
战略对齐 ( `strategic-alignment` )	验证团队Rocks是否与公司Rocks一致
变革管理 ( `change-management` )	新操作系统落地遵循ADKAR模型

Output Artifacts

交付成果

Request	Deliverable
"Set up our operating system"	Framework recommendation + 30-day implementation plan
"Design our meeting cadence"	Full meeting rhythm with agendas and owners
"Build our scorecard"	5-15 metrics with owners, targets, and thresholds
"Help with quarterly planning"	Planning session agenda + rock-setting framework
"Fix our accountability"	Accountability chart workshop + gap/overlap analysis
"We keep discussing the same issues"	IDS training + issues list audit

请求	交付物
“搭建我们的操作系统”	框架建议+30天实施计划
“设计我们的会议节奏”	完整会议节奏（含议程与负责人）
“搭建我们的计分卡”	5-15个指标（含负责人、目标与阈值）
“协助季度规划”	规划会议议程+Rocks设置框架
“解决问责问题”	问责图表工作坊+空白/重叠分析
“我们反复讨论同一问题”	IDS培训+问题列表审计

Tool Reference

工具参考

scorecard_builder.py

Builds and tracks weekly company scorecards with RAG status, trend analysis, and IDS-ready issue lists for L10 meetings.

bash

undefined

用于搭建并追踪周度公司计分卡，支持RAG状态、趋势分析，以及为L10会议生成可用于IDS的问题列表。

bash

undefined

Run with demo data

使用演示数据运行

python scripts/scorecard_builder.py

From JSON with metrics and rocks

从JSON文件导入指标与Rocks

python scripts/scorecard_builder.py --input scorecard.json

JSON output

输出JSON格式结果

python scripts/scorecard_builder.py --json

undefined

python scripts/scorecard_builder.py --json

undefined

rocks_tracker.py

Tracks 90-day company and individual rocks with binary status, blocker identification, and owner accountability.

bash

undefined

追踪公司与个人的90天Rocks，支持二元状态标记、阻塞问题识别与负责人问责管理。

bash

undefined

Run with demo data

使用演示数据运行

python scripts/rocks_tracker.py

Specify quarter

指定季度

python scripts/rocks_tracker.py --quarter Q2

From JSON

从JSON文件导入数据

python scripts/rocks_tracker.py --input rocks.json

JSON output

输出JSON格式结果

python scripts/rocks_tracker.py --json

undefined

python scripts/rocks_tracker.py --json

undefined

meeting_pulse_designer.py

Designs company meeting rhythms, validates meeting load, identifies redundancies and gaps, and generates L10 agenda templates.

bash

undefined

设计公司会议节奏，验证会议负荷，识别冗余与空白，并生成L10会议议程模板。

bash

undefined

Run with demo meetings

使用演示会议数据运行

python scripts/meeting_pulse_designer.py

Specify team size

指定团队规模

python scripts/meeting_pulse_designer.py --team-size 50

From JSON with current meetings

从JSON文件导入现有会议数据

python scripts/meeting_pulse_designer.py --input meetings.json

JSON output

输出JSON格式结果

python scripts/meeting_pulse_designer.py --json

---

python scripts/meeting_pulse_designer.py --json

---

Troubleshooting

故障排查

Problem	Likely Cause	Fix
Five team leads give different answers about top 3 priorities	Alignment failure -- rocks not cascaded or not reviewed weekly	Re-run quarterly planning; review rocks weekly in L10; publish company priorities visibly
Same issue on the issues list for 4+ weeks	Avoidance or structural problem too scary to address	Force it: address this week or permanently remove; escalate if needed
Scorecard has 30+ KPIs	Metric overload -- nothing gets attention	Cut to 5-10 metrics. Only the ones that tell you if the company is on track.
Rocks set but never reviewed	Goals without accountability; L10 meeting not happening	Weekly L10 is non-negotiable; 5 minutes on rocks review every week
Leadership team skips L10 or ignores IDS	Leader non-compliance destroys the OS	CEO must enforce: leaders go first. If CEO skips, the OS dies.
Meetings added on top of existing meetings	Meeting fatigue from accumulation	Replace meetings, don't add them. Audit meeting inventory; eliminate redundancies

问题	可能原因	解决方案
五位团队负责人对公司前3优先级给出不同答案	对齐失败——Rocks未向下传递或未每周复盘	重新开展季度规划；在L10会议中每周复盘Rocks；公开公示公司优先级
同一问题连续4周出现在问题列表中	回避问题或存在不敢直面的结构性问题	强制处理：本周解决或永久移除；必要时升级
计分卡有30+个KPI	指标过载——无法聚焦重点	精简至5-10个指标，仅保留能判断企业是否在正轨的核心指标
设置了Rocks但从未复盘	目标缺乏问责；未开展L10会议	每周L10会议是硬性要求；每周用5分钟复盘Rocks
领导团队跳过L10或无视IDS	领导层不遵守规则会摧毁整个体系	CEO必须强制执行：管理者以身作则。若CEO跳过，体系将失效
在现有会议基础上新增会议	叠加导致会议疲劳	替换原有会议，而非叠加。审计现有会议清单；消除冗余

Success Criteria

成功标准

Weekly L10 meeting happens every week with 90%+ leadership attendance (no exceptions for 12+ consecutive weeks)
Scorecard reviewed weekly with red metrics discussed using IDS format (zero red metrics ignored)
70%+ of quarterly rocks completed as binary done/not-done by end of quarter
Issues list: average issue resolved within 2 meetings (no issue lingers 4+ weeks)
All team leads can articulate top 3 company priorities identically (tested quarterly)
Meeting hours per person per week below 10 hours (measured via meeting_pulse_designer.py)
Accountability chart reviewed and updated quarterly with zero unowned functions

每周L10会议持续开展，领导层出席率90%+（连续12周无例外）
每周复盘计分卡，红色指标采用IDS格式讨论（无红色指标被忽略）
季度末70%+的Rocks以二元判定标准完成
问题列表：平均每个问题在2次会议内解决（无问题持续4周以上）
所有团队负责人能准确表述公司前3优先级（每季度测试）
每人每周会议时长低于10小时（通过meeting_pulse_designer.py测量）
问责图表每季度复盘更新，无空白职能

Scope & Limitations

范围与限制

In Scope: Operating system selection (EOS, Scaling Up, OKR, Holacracy), accountability charts, weekly scorecards, meeting pulse design, IDS issue resolution, 90-day rocks, communication cadence, implementation roadmap.

Out of Scope: OKR software configuration, project management tool setup, Agile/Scrum methodology, sprint planning, product backlog management, HR policy development.

Limitations: Scorecard builder calculates RAG from provided data but cannot source live metrics from business systems. Rocks tracker uses manual status updates -- it cannot automatically detect completion. Meeting pulse designer provides recommendations based on team size and meeting inventory but cannot account for company-specific cultural norms. Framework comparison is directional -- actual implementation success depends on leadership commitment.

包含范围：操作系统选型（EOS、Scaling Up、OKR、Holacracy）、问责图表、周度计分卡、会议节奏设计、IDS问题解决流程、90天Rocks、沟通节奏、实施路线图。

排除范围：OKR软件配置、项目管理工具搭建、Agile/Scrum方法论、冲刺规划、产品待办事项管理、HR政策制定。

限制：计分卡构建工具仅能根据提供的数据计算RAG状态，无法从业务系统获取实时指标。Rocks追踪工具依赖手动更新状态，无法自动检测完成情况。会议节奏设计工具根据团队规模与现有会议清单提供建议，但无法考虑企业特定文化规范。框架对比仅为方向性指导，实际实施成功与否取决于领导层的投入度。

Integration Points

集成点

Skill	Integration
`ceo-advisor`	CEO sets vision that feeds 1-year plan and rocks
`coo-advisor`	Owns meeting pulse and issue resolution cadence
`cfo-advisor`	Financial metrics in the weekly scorecard
`cto-advisor`	Engineering rocks and tech scorecard metrics
`chro-advisor`	People metrics (attrition, hiring velocity) in scorecard
`culture-architect`	Culture rituals integrate into meeting pulse
`strategic-alignment`	Validates team rocks cascade from company rocks
`change-management`	New OS rollout follows ADKAR model for adoption
`chief-of-staff`	Orchestrates quarterly planning sessions and L10 follow-up

技能	集成方式
`ceo-advisor`	CEO制定愿景，为1年规划与Rocks提供方向
`coo-advisor`	负责会议节奏与问题解决流程
`cfo-advisor`	负责周度计分卡中的财务指标
`cto-advisor`	负责技术团队的Rocks与计分卡指标
`chro-advisor`	负责计分卡中的人员指标（流失率、招聘速度）
`culture-architect`	将文化仪式融入会议节奏
`strategic-alignment`	验证团队Rocks是否与公司Rocks一致
`change-management`	新操作系统落地遵循ADKAR模型以提升 adoption
`chief-of-staff`	协调季度规划会议与L10会议的跟进事项