Communitygithub.com

cbrock84/組織設計

設計組織結構,包含匯報關係、團隊邊界、管理幅度與層級、角色定義以及與策略對齊的人力規劃。可用於架構新團隊、重組現有團隊、釐清團隊間模糊的所有權、規劃人力,或診斷團隊因結構性而非個人因素導致的績效不佳。

組織設計 是什麼?

此技能提供一套基於結構性思維的組織設計方法論,強調「從工作出發」而非「從人出發」來設計組織。它涵蓋了管理幅度與層級(Spans and Layers)、明確的成果所有權、根據實際工作量而非歷史數據進行人力規劃,以及重組(Restructuring)的最佳實務與禁忌。其核心觀點是:多數持續性的協作問題本質上是結構性的,無法透過要求人們「加強溝通」來解決。此技能支援所有需要在團隊或組織層級進行設計與重組的場景,例如在 AI 輔助開發或協作平台(如 Claude Code、Cursor 等)中,協助開發者或技術領導者進行組織結構決策。它強調以「便宜交接點」劃分團隊邊界,確保每個團隊能獨立交付價值,並避免常見的重組陷阱(如為了迴避績效談話而重組、為了留人而創造不需要的角色、或讓一個成果有兩個所有人)。

相容平台~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.

相關技能