
Context Not Control
- 19 installs
- 10 repo stars
- Updated April 17, 2026
- kangarooking/no-rules-rules-skill
Learn organizational practices for building high-performance teams and culture
About
Netflix culture principle on context not control. Key practice for creating high-trust, high-performing organizations.
- Lessons from Netflix's organizational culture
- Practical implementation patterns
Context Not Control by the numbers
- 19 all-time installs (skills.sh)
- +2 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #2,032 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/kangarooking/no-rules-rules-skill --skill context-not-controlAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 19 |
|---|---|
| repo stars | ★ 10 |
| Last updated | April 17, 2026 |
| Repository | kangarooking/no-rules-rules-skill ↗ |
What it does
Learn organizational practices for building high-performance teams and culture
Files
context-not-control(情景管理而非控制管理)
R — 原文摘录 (Reading)
"不要告诉员工应该做什么,而是应该通过讨论来设置情景,达成一致,最后让他们自己去做出正确的决定。"
I — 诠释理解 (Interpretation)
情景管理用"提供决策所需的信息"替代"告诉别人该做什么"。这不是放任自流,而是通过充分的信息共享让团队自主做出正确决策。
四个前提条件: 1. 高人才密度 — 你必须信任他们的判断力 2. 创新导向目标 — 追求创新而非防范错误 3. 松耦合组织 — 团队能够独立运作,无需层层审批 4. 共同理解 — 所有人对齐同一个北极星目标
树模型(Tree Model):
- CEO(根)→ 设定全局情景(使命、愿景、战略方向)
- 高管(干)→ 添加战略情景
- 经理(枝)→ 添加运营情景
- 知情指挥(叶)→ 做出最终决策
关键思维转变: 当员工犯错时,不要责怪他们——问自己"我在情景设置上哪里出了问题?"修复情景,而不是修复人。
A1 — 过去应用 (Past Application)
1. 16 岁儿子隐喻: 控制模式 = 审批他能参加哪些派对、安装手机追踪器。情景模式 = 教育他了解危险(酒精、毒品、鲁莽驾驶),然后信任他的判断。后者才能真正培养决策能力。
2. 《Mighty Little Bheem》的成功: 这是一个 4 层情景级联的典型案例。Reed Hastings 设定全球战略("进军印度市场"),高管添加战略情景("投资本土原创内容"),经理添加运营情景("寻找印度动画合作伙伴"),Aram Yakubian 作为知情指挥做出最终决策——买下这部动画。结果成为 Netflix 全球排名第一的动画节目。整个过程没有层层审批,只有情景传递。
3. 新加坡 5 年规划事件: 设施经理询问 Reed 关于未来 5 年的人员增长预测(用于办公空间规划)。Reed 没有责怪他提了错误的问题,而是意识到这是情景传递的缺失——Netflix 的核心理念是灵活而非可预测。Reed 将此加入季度业务回顾(QBR)议程,确保所有人理解"灵活性优先于可预测性"。
A2 — 未来触发 (Future Trigger)
以下场景触发此技能:
- 用户正在微观管理团队(审批每一个决定)
- 用户询问"如何在不失控的情况下赋能员工"
- 用户是创始人瓶颈——所有决策都需要经过自己
- 用户想从命令控制型管理转向自主团队
- 用户抱怨下属"不会独立思考"
- 用户引用 Netflix 的管理理念
- 用户在快速扩张中遇到管理带宽不足
E — 执行步骤 (Execution)
步骤 1:检查前提条件
在实施情景管理之前,逐一确认:
- 人才密度够高吗? 如果团队中有很多平庸 performer,你需要先提升人才密度
- 目标是创新导向的吗? 如果核心目标是防范错误(如合规、安全),控制模式可能更合适
- 组织是松耦合的吗? 如果每个变更都需要多个团队协调,情景管理的效果会大打折扣
- 是否有共同理解? 团队是否对齐了同一个北极星?
步骤 2:用情景替代指令
- 不要说"做这个",而是分享:战略目标是什么、背后的假设是什么、潜在风险是什么
- 通过讨论达成一致(alignment),而非通过命令达成服从(compliance)
- 使用树模型逐层传递情景:确保每一层都添加了属于自己层面的上下文
步骤 3:用"修复情景"替代"责怪人"
- 当员工做出错误决定时,克制责怪的冲动
- 问自己:"我在情景设置上哪里出了问题?我遗漏了什么关键信息?"
- 修复情景(补充信息、澄清优先级),而不是修复人(批评、惩罚)
- 将这次经验纳入未来的情景传递中
B — 边界与限制 (Boundary)
- 不适合安全关键型操作: 医院、航空、核电站等场景中,一个错误可能是致命的,控制模式不可替代
- 不适合紧耦合组织: 如果组织架构中一个团队的变更会级联影响多个团队,情景管理的独立性优势无法发挥
- 人才密度低时不可用: 如果团队还没有达到高人才密度,需要先解决人才问题(参考" keeper test")
- 组织架构转换极难: 作者的盲点——从紧耦合转向松耦合在实践中极其困难,这个模式在组织设计之初就植入效果最好
- 不是放任自流: 情景管理不等于"不管了",而是用信息共享替代审批控制。管理者仍需持续投入时间进行情景传递
{
"skill": "context-not-control",
"version": "0.1.0",
"source_book": "《不拘一格》 里德·哈斯廷斯 / 艾琳·迈耶",
"darwin_compatible": true,
"test_cases": [
{
"id": "st-001",
"category": "should_trigger",
"prompt": "I keep micromanaging my team. I review every decision, ask for constant updates, and I know it's killing their motivation. How do I stop?",
"expected_behavior": "Should trigger the context-not-control skill and explain the principle of leading with context instead of control — providing clear goals and information rather than dictating actions.",
"tags": ["micromanaging", "control behavior", "leadership style"]
},
{
"id": "st-002",
"category": "should_trigger",
"prompt": "How do I empower my employees to make decisions without me? Right now everything flows through me and I'm the bottleneck.",
"expected_behavior": "Should trigger the context-not-control skill and explain how to distribute decision-making by ensuring employees have full context (business strategy, goals, constraints) rather than requiring approval at every step.",
"tags": ["empower employees", "founder bottleneck", "decision distribution"]
},
{
"id": "st-003",
"category": "should_trigger",
"prompt": "I want my teams to be more autonomous and self-directing. What does it take to build teams that can operate without a manager hovering over them?",
"expected_behavior": "Should trigger the context-not-control skill and explain how building autonomous teams requires investing in shared context, clear alignment on goals, and trust in decision-making capability.",
"tags": ["autonomous teams", "self-directing", "team independence"]
},
{
"id": "st-004",
"category": "should_trigger",
"prompt": "As a founder, I find myself in every important meeting and every key decision. I've become the single point of failure. How do I step back without losing control of the company direction?",
"expected_behavior": "Should trigger the context-not-control skill and address the founder's dilemma of being a bottleneck, explaining how to shift from controlling decisions to providing strategic context.",
"tags": ["founder bottleneck", "context sharing", "stepping back"]
},
{
"id": "snt-001",
"category": "should_not_trigger",
"prompt": "How do I delegate tasks more effectively? I have too much on my plate and need to assign work to my team members.",
"expected_behavior": "Should NOT trigger the context-not-control skill. Delegation is about distributing specific tasks. Context-not-control is a broader leadership philosophy about how decisions get made, not task assignment.",
"tags": ["delegation", "task assignment", "workload"]
},
{
"id": "snt-002",
"category": "should_not_trigger",
"prompt": "What project management tool do you recommend? We need something to track tasks, deadlines, and team workload.",
"expected_behavior": "Should NOT trigger the context-not-control skill. This is a tool selection question, not a leadership philosophy or management approach question.",
"tags": ["project management tool", "software selection", "tooling"]
},
{
"id": "ec-001",
"category": "edge_case",
"prompt": "I run a hospital department. Lives are at stake if decisions go wrong. Can the 'context not control' philosophy work in a safety-critical environment like healthcare, or does patient safety require more direct control?",
"expected_behavior": "Should trigger the skill with careful adaptation. The context-not-control principle can still apply — providing clinical staff with clear protocols, shared goals, and full situational context — but safety-critical environments have legitimate reasons for stricter guardrails. The skill should acknowledge this tension and offer a modified approach where context is maximized within necessary safety boundaries.",
"tags": ["safety-critical", "hospital", "healthcare", "context vs safety", "boundary condition"]
}
],
"minimum_pass_rate": 0.8,
"notes": "Test cases for the context-not-control concept from No Rules Rules. The core idea is that leaders should provide rich context (strategy, goals, constraints, business landscape) rather than exerting control over decisions. This empowers employees to make great decisions independently. Safety-critical edge cases require acknowledging that some control mechanisms are necessary while still maximizing context sharing within those boundaries."
}