kangarooking/no-rules-rules-skill · Archived

talent-density

当管理?

First seen Apr 17, 2026

Installation

$ npx skills add kangarooking/no-rules-rules-skill --skill talent-density

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from kangarooking/no-rules-rules-skill.

npx skills add kangarooking/no-rules-rules-skill

Browse all from kangarooking/no-rules-rules-skill

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 11
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,645 B
  • docs SUMMARY.md 227 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 22 installs

SKILL.md

R - 原文摘录 (Reading)

"构建一个高效且具有创造力的工作环境,离不开出色的员工……你必须首先确保这一关键点落实到位,否则其他原则都没有意义。"

I - 诠释理解 (Interpretation)

Talent density is the ratio of high performers in a team. Research shows one underperformer can drag down team effectiveness by 30-40% through behavioral contagion — they consume manager energy, lower discussion quality, force workarounds, push out top performers, and signal that mediocrity is acceptable. The remedy: actively remove underperformers (not just the bottom 10%), eliminate "brilliant jerks" who damage psychological safety, and replace multiple average performers with one elite.

人才密度是Netflix自由与责任文化的基石。没有足够的人才密度,给予自由只会导致混乱。高人才密度之所以重要,不是因为"精英主义",而是因为低绩效者的行为具有传染性——一个人可以拉低整个团队的标准。

A1 - 过往案例 (Past Application)

  1. 2001年Netflix裁员:Letting go of 40 out of 120 employees paradoxically boosted morale and productivity. 裁掉三分之一后,留下的人反而更有活力——因为每天一起工作的都是真正出色的人,不再需要替别人兜底。
  1. Will Felps的"坏苹果"实验:Planted "bad apples" reduced team performance by 30-40%. 三个实验中的"坏苹果"角色(消极者、不合作者、支配者)分别让团队效率骤降。实验结束时,连原本优秀的团队成员也开始表现不佳——行为传染的实证。
  1. Paula的案例:A brilliant but domineering employee who undermined candor culture and eventually had to leave. Paula能力出众,但她的强势行为压制了其他人的发言意愿,破坏了坦诚文化。最终Reed不得不让她离开——即使她的业务能力很强。

A2 - 触发条件 (Future Trigger)

当出现以下场景时激活本技能:

  • User is a manager frustrated by a team member's performance
  • User is debating whether to let go of a "nice but mediocre" employee
  • User asks "should I tolerate a brilliant jerk?"
  • User's team seems to be underperforming despite having talented individuals
  • 管理者发现自己大部分精力花在处理个别低绩效者身上
  • 团队中的优秀成员开始沉默或流失
  • "还行""凑合""不算差"成为描述团队成员的高频词

E - 执行步骤 (Execution)

Step 1: 团队人才审计

Assess your team: for each member, would you enthusiastically rehire them today? If hesitation, flag for review.

  • 对每个团队成员问一个问题:"如果今天重新招聘,我会热切地再次雇佣这个人吗?"
  • 如果答案是犹豫的、勉强的、"看情况"的——标记此人需要进一步评估。
  • 注意:不是"他还能用吗",而是"我会兴奋地再选他吗"。

Step 2: 识别传染风险

Identify contagion risks: Is anyone consuming disproportionate manager energy? Lowering meeting quality? Causing others to disengage?

  • 检查团队中是否有人正在造成以下影响:

- 占用管理者不成比例的时间和精力 - 降低会议讨论的质量(其他人因此沉默或敷衍) - 迫使其他人绕着他工作(workarounds) - 让优秀的人开始考虑离开 - 向团队传递"平庸也可以被接受"的信号

Step 3: 果断行动

Act decisively: Remove underperformers with generous severance. Don't wait for a crisis. "Adequate" is not enough for elite teams.

  • 一旦确认,不要拖延到下一个绩效周期。
  • 给予丰厚的遣散费(这是非谈判项)。
  • 不要用PIP(绩效改进计划)浪费时间——它对双方都是折磨。
  • 核心原则:"够用"不等于"够好"。精英团队的标准不是"不差",而是"出色"。

B - 边界与限制 (Boundary)

  • This approach assumes you CAN attract top talent (requires competitive compensation — see elite-compensation). 在无法提供有竞争力薪酬的组织中,先解决薪酬问题,再提高人才密度标准。
  • Not applicable in tight labor markets where replacements aren't available. 当市场上根本找不到更好的人时,提升标准只会导致空缺——此时应优先投资现有成员的成长。
  • "Brilliant jerk" removal assumes the jerk's skills are replaceable — sometimes they aren't (acknowledge this honestly). 如果某人的独特能力确实不可替代,需要诚实面对这个困境,同时寻找替代方案。
  • The author's blind spot: this model works best in high-margin industries that can afford generous severance. 在利润率较低的行业中,慷慨的遣散费可能不现实——但果断处理低绩效的原则仍然适用,只是执行方式需要适配。
  • 不适用于初创团队早期:当团队只有3-5个人时,每个人都是多面手,"人才密度"的概念不如"团队互补性"重要。
  • 需要与坦诚反馈文化配合使用:没有4A反馈框架,直接开除低绩效者会制造恐惧文化,而非高绩效文化。