Fewer People Higher Pay logo

Fewer People Higher Pay

Community
ace3000chao
fewer-people-higher-pay

当你在思考招聘规模、团队配置、人力成本占比,或面临"是招更多人还是激励现有团队"的抉择时,激活此技能。 当你听到"我们人手不够"、"招人太贵养不起"、"人多力量大"等观点时,主动激活。 不适用于:紧急填补关键岗位(先止血)、初创探索期(需要试错人数)、完全依赖外包的场景。 关键触发信号:团队规模讨论、人力成本占比担忧、招聘质量vs数量困惑。

Overview

Publisherace3000chao
Repositorybook2startup
Skill namefewer-people-higher-pay
Stars
93
Forks
14
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by ace3000chao on GitHub. Read the source before you install it.

Installation

Install the Fewer People Higher Pay AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/ace3000chao/book2startup/tree/master/ScalingUp-skills/fewer-people-higher-pay
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/ace3000chao/book2startup.git /tmp/book2startup
mkdir -p .claude/skills
cp -r /tmp/book2startup/ScalingUp-skills/fewer-people-higher-pay .claude/skills/fewer-people-higher-pay
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Fewer People Higher Pay in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Fewer People Higher Pay on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Fewer People Higher Pay is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Fewer People, Higher Pay(少人高薪)

R — 原文 (Reading)

"Hire fewer people, but pay them more. One great person equals three good people in terms of business productivity."

— Verne Harnish, Scaling Up (第4章 The Team)

翻译: 少招人,但给更高的薪水。从业务产出看,一个顶尖人才等于三个普通人才。


I — 方法论骨架 (Interpretation)

  1. 核心逻辑: 人才质量差异是乘数效应,而非加法。A类人才的产出约等于3个B/C类人才,但薪资溢价通常不到3倍。
  2. 财务收益: 更少的人数 → 更低的工资总额占比 → 更高的利润率。工资单是最大固定成本,减少人头是提升利润最直接的杠杆。
  3. 复杂度降低: 每增加一个人,沟通路径指数增长(n×(n-1)/2)。少人才能保持敏捷。
  4. 文化纯度: 小团队更容易保持核心价值观的传递,减少"免疫排异"冲突。
  5. 执行路径: 不是"省钱招人",而是"花更多钱招更少人"——用高溢价过滤出真正的A类人才。
  6. 配套要求: 招到A类人才后,必须给予高薪酬、高自主、高挑战,避免其因无聊而离开。

A1 — 书中的应用 (Past Application)

案例 1: 六人精英队 vs. 十二人普通队

  • 问题: 某公司面临增长瓶颈,管理层第一反应是扩充团队。
  • 方法论的使用: Harnish建议比较两种方案:维持6人精英团队 vs. 扩张到12人的传统配置。
  • 结论: 精英队的人力成本占总成本比例更低,人均产出更高。
  • 结果: 选择精英模式的团队在一年内实现了更高的营收增长率,且组织决策速度明显更快。

案例 2: "A类人才不愿与B/C类共事"

  • 问题: A类人才如果被安排与大量B/C类人才合作,往往会因效率被拖累、决策被拉低而产生离职念头。
  • 方法论的使用: 识别并移除B/C类人才,或将其安置在不影响核心产出的岗位。
  • 结论: #1去障碍因素就是"不要让A类人才和B/C类人才一起工作"。
  • 结果: 团队专注度提升,项目交付质量提高。

A2 — 触发场景 (Future Trigger) ★

用户会在什么情境下需要这个 skill?

  1. 招聘规模决策:公司在启动新项目或面对增长压力时,团队领导在"扩张人手"和"提升现有团队"之间犹豫。
  2. 人力成本过高:财务报表显示工资占比过高(如>40%),CEO或CFO想要降本增效。
  3. 团队效率低下:明明人多,产出却少——开会是"人多嘴杂"而非"集思广益"。
  4. 薪酬体系设计:设计薪酬方案时,纠结于"是普调还是重金留尖子"。
  5. 扩张vs稳守:面对市场机会,是快速招人抢占还是保持精干等待。

语言信号 (用户的话里出现这些就应激活)

  • "我们是不是应该多招点人?"
  • "团队扩张后反而效率变低了"
  • "工资单占比太高了,利润都被吃掉了"
  • "一个人干三个人的活,太累了"
  • "A类人才留不住"

与相邻 skill 的区分

  • 与 hire-for-culture-fit 的区别:少人高薪关注"数量+薪酬"决策,文化招聘关注"招聘标准"本身,两者结合才是完整招聘策略。
  • 与 topgrading-interview 的区别:序列面试解决"如何识别A类人才",少人高薪解决"为什么要招更少人且付更多钱"。

E — 可执行步骤 (Execution)

  1. 诊断团队现状

    • 盘点现有团队,按A/B/C分类当前成员(A=前10%产出者)
    • 计算工资总额占营收比例,参照行业基准(健康<35%)
    • 完成标准:获得清晰的"当前人力资源资产负债表"
  2. 制定少人高薪方案

    • 识别可合并的岗位/职能,寻找"一个A类顶三个"的重叠区域
    • 确定目标薪资溢价:高于市场P75分位,锚定A类人才
    • 判停条件:若某岗位无法找到A类人才,宁可空缺或外包,不降格招B/C类
  3. 执行并重新校准

    • 实施新的团队配置,前3个月密切跟踪人均产出变化
    • 每季度回顾工资占比和员工敬业度,确保持续改善
    • 完成标准:工资占比下降5%以上,且产出持平或提升

B — 边界 (Boundary) ★

不要在以下情况使用此 skill

  • 紧急岗位空缺:业务已因缺人受损,急需止血时先用B/C类顶上,再逐步替换为A类。
  • 高度重复性工作:流水线作业或劳动密集型岗位,个体差异对产出影响小,不适用此逻辑。
  • 初创探索期:0→1阶段需要快速试错,人数多是探索成本,此时"多"比"精"更重要。

作者在书中警告的失败模式

  • 招了太多B/C类人才来"分担工作",结果A类人才被拖累离开,最终整体产出下降。
  • 工资占比过高挤压利润,导致公司财务脆弱,经不起市场波动。

作者的盲点 / 时代局限

  • 对"谁是A类"的判断依赖主观,书中未提供足够客观的量化标准,容易出现"我招的人都是A类"的认知偏差。
  • 在劳动法严格的市场(如欧洲),高薪酬+少人数的弹性较低,裁员成本反而更高。

容易混淆的邻近方法论

  • "小而美"创业心态:强调少人,但少人高薪是主动选择(花更多钱雇更少人),而非被动节省(少花钱不进人)。
  • OKR精简目标:两者都强调"少",但OKR关注目标数量,少人高薪关注团队规模,是不同的精简维度。

相关 skills (阶段 3 填充)

  • depends-on: [hire-for-culture-fit, topgrading-interview]
  • contrasts-with: []
  • composes-with: [dont-demotivate-dehassle]

审计信息

  • 验证通过: V1 ✓ / V2 ✓ / V3 ✓
  • 测试通过率: 待填充 (详见 test-prompts.json)
  • 蒸馏时间: 2026-04-26

Frequently asked questions

What does the Fewer People Higher Pay AI skill do?

当你在思考招聘规模、团队配置、人力成本占比,或面临"是招更多人还是激励现有团队"的抉择时,激活此技能。 当你听到"我们人手不够"、"招人太贵养不起"、"人多力量大"等观点时,主动激活。 不适用于:紧急填补关键岗位(先止血)、初创探索期(需要试错人数)、完全依赖外包的场景。 关键触发信号:团队规模讨论、人力成本占比担忧、招聘质量vs数量困惑。

Why use Fewer People Higher Pay on TypingMind?

Because you install it once and use it with any model. Fewer People Higher Pay is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Fewer People Higher Pay in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ace3000chao/book2startup/tree/master/ScalingUp-skills/fewer-people-higher-pay. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Fewer People Higher Pay?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Fewer People Higher Pay?

As many as you like. As long as a model supports skills, you can use Fewer People Higher Pay with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Fewer People Higher Pay AI skill free?

Yes. It is published on GitHub by ace3000chao under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇