Communitygithub.com

cbrock84/组织设计

用于设计组织架构——包括汇报关系、团队边界、管理幅度与层级、角色定义以及基于战略的人力规划。适合用于组建新团队、重构现有团队、解决团队间所有权不明确的问题、规划人力,或诊断团队因结构性问题而非个人原因导致的绩效不佳。

组织设计 是什么?

该技能(org-design)指导AI助手(如Claude Code)帮助用户进行组织架构设计。其核心原则是“从工作出发进行设计”:先明确必须完成的工作及其自然边界(即上下游交接成本高或低的地方),然后在交接成本较低处划分团队。每个团队应能独立交付有价值成果,而无需频繁依赖其他团队。技能涵盖了管理幅度与层级、所有权分配、人力规划、重组方法等关键模块。它支持通用平台(与编辑器或CLI无关),并强调结构问题无法通过改善沟通来解决,必须从结构入手。使用时需注意:不要以人为核心设计组织,不要留下两个团队共享同一个所有权的模糊地带,不要为了留住某人而设立不必要的角色。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/cbrock84/headcount/tree/main/plugins/people/skills/org-design

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

组织设计 是做什么的?

结构决定了什么是容易的,什么需要英雄主义。大多数持续的协作问题都是结构性的,无法通过要求人们更好地沟通来解决。

从工作出发进行设计

从必须完成的工作及其自然边界开始——即交接成本高的地方和低的地方。在交接成本较低的地方划定团队边界。

然后检查:每个团队是否能交付有意义的成果而无需等待其他团队?一个没有三个依赖关系就无法交付的团队不是团队,而是队列。

围绕工作设计组织,而不是围绕目前在职的个人。 然后有意识地进行调整,记下你做出了哪些妥协以及原因。围绕个人构建的结构在这些人离开时会失败,而且每个人都能看出它们是那样构建的。

管理幅度与层级

宽的管理幅度将决策权下放,但会削弱对个人的关注度。窄的管理幅度给予更多关注,但会产生层级,从而增加每个决策的延迟。

大致上:如果管理者需要对下属进行指导,则大约五到九名直接下属;如果工作一致性强且下属经验丰富,则可以有更多直接下属。每个层级都必须增加决策价值——只传递信息的层级应该被移除,而且通常很容易看出是哪个层级。

所有权

每个成果有且只有一个所有者。如果两个团队共享一个成果,那么谁都不真正拥有它,它会在间隙中失败。如果所有者缺乏交付所需的权力,那么问责制就是虚构的。

写下边界——每个团队可以单独决定什么,需要协商什么,需要批准什么。高级团队之间的模糊地带代价高昂,且不会自行解决。

人力规划

根据工作和计划规划角色,而不是根据去年的数字加上一定比例。针对每个提议的角色:如果没有它,什么工作无法完成?它能为其他人分担什么?需要多长时间才能独立贡献?

安排招聘顺序,让每个新员工都有前辈可以学习。在招聘能够带领团队的高级员工之前,先招聘三名初级员工是一种常见且代价高昂的顺序错误。

重组

  • 坦诚说明原因以及要解决什么问题。人们会用比真相更糟糕的解释来填补沉默。
  • 一次性宣布全部变更。系列性重组造成的持续不确定性成本高于一次性重大变更。
  • 任何涉及个人角色、级别或薪酬的变动,都必须事先经过人员职能部门的审查,无一例外。

永远不要

  • 为了避免一场绩效谈话而进行重组。
  • 为了留住某个组织不需要的人而设立一个角色。
  • 让一个成果有两个所有者。

Individual skills in this repo

This repo contains 11 individual skills — each has its own dedicated page.

cbrock84/interface-craft

Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or when an interface needs to feel trustworthy rather than merely functional.

cbrock84/portfolio-governance

Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things. Use this to set up intake and prioritization, run a stage gate, decide between competing initiatives, resolve resource contention across projects, or work out why everything is in flight and nothing is finishing.

cbrock84/product-launch

Takes something built and gets it into the market — tiering the launch to match what it actually warrants, sequencing internal readiness before external announcement, preparing sales and support to answer the questions it creates, choosing the date for a reason, and measuring adoption rather than announcement reach. Use this to plan a launch, right-size one that is consuming more than it deserves, work out why a released feature nobody uses was launched loudly, or run the weeks after launch day.

cbrock84/program-management

Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving. Use this to run a multi-team initiative, recover a program that is slipping, build a delivery plan with dependencies, structure status reporting, or diagnose why cross-team work keeps missing dates.

cbrock84/project-delivery

Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips. Use this to plan a project, build or challenge a schedule, estimate credibly, track progress meaningfully, or recover a project that is late.

cbrock84/retention

Diagnoses and reduces churn — cancellation flows, save offers, failed-payment recovery, at-risk detection, and the product and service causes underneath. Use this when churn is rising or unexplained, to design a cancellation or win-back flow, to recover involuntary churn, to identify at-risk accounts before they leave, or to decide whether a retention problem is a product problem.

cbrock84/sales-enablement

Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies. Use this to create or fix sales collateral, prepare for a competitive deal, build a demo flow, document objection responses, or diagnose why a pitch is not converting.

cbrock84/tax

Structures the tax questions a growing business faces — corporate income, sales and use, payroll, nexus, and the obligations created by hiring or selling somewhere new. Use this to work out what a new state or country obligates you to, prepare for a tax filing or audit, understand sales tax on your product, or check what a remote hire or new market triggers.

cbrock84/unit-economics

Establishes whether the business makes money on each customer or unit — contribution margin, acquisition cost, payback period, lifetime value, and the cohort behavior underneath. Use this to assess whether growth is profitable, evaluate a channel or segment, support a pricing decision, judge how fast the business can afford to grow, or diagnose why revenue growth is not producing profit.

cbrock84/video-content

Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watched. Use this to script a video, plan a series, fix retention or click-through problems, design thumbnail and title concepts, or turn written content into video. For a YouTube channel specifically — idea selection, retention teardowns, and channel-level strategy — use `youtube-producer`.

cbrock84/visual-content

Designs and directs the visual assets that carry content — carousels, infographics, quote graphics, diagrams, and social imagery — including the generation prompts where they are AI-produced. Use this to turn a written piece into a visual format, design a carousel or infographic, create social graphics, or fix visuals that are not stopping the scroll.

相关技能