org-planning

Anthropic ｜ 商業與營運 ｜ 原文 ｜ Apache-2.0

規劃人力編制、組織架構和招募順序

---
name: org-planning
description: 人力編制規劃、組織設計和團隊結構最佳化。用「org planning」、「headcount plan」、「team structure」、「reorg」、「who should we hire next」觸發，或在使用者思考團隊規模、匯報架構或組織設計時使用。
---

# 組織規劃（Org Planning）

協助規劃組織結構、人力編制和團隊設計。

## 規劃面向

- **人力編制（Headcount）**：我們需要多少人、什麼職位、什麼時候要到位？
- **結構（Structure）**：匯報關係、管理幅度、團隊邊界
- **排序（Sequencing）**：哪些招募最關鍵？正確的順序是什麼？
- **預算（Budget）**：人力成本建模與取捨

## 健康組織的基準

| 指標 | 健康範圍 | 警訊 |
|--------|---------------|--------------|
| 管理幅度（Span of control） | 5-8 位直屬下屬 | < 3 或 > 12 |
| 管理層級 | 500 人規模有 4-6 層 | 太多 = 決策變慢 |
| IC 與主管的比例 | 6:1 到 10:1 | < 4:1 = 頭重腳輕 |
| 團隊規模 | 5-9 人 | < 4 = 孤單，> 12 = 難管理 |

## 輸出

產出組織圖（純文字）、附成本建模的人力編制計畫，以及排好順序的招募路線圖。標出結構性問題，例如單點故障（single point of failure）或過高的管理負擔。

---
name: org-planning
description: Headcount planning, org design, and team structure optimization. Trigger with "org planning", "headcount plan", "team structure", "reorg", "who should we hire next", or when the user is thinking about team size, reporting structure, or organizational design.
---

# Org Planning

Help plan organizational structure, headcount, and team design.

## Planning Dimensions

- **Headcount**: How many people do we need, in what roles, by when?
- **Structure**: Reporting lines, span of control, team boundaries
- **Sequencing**: Which hires are most critical? What's the right order?
- **Budget**: Headcount cost modeling and trade-offs

## Healthy Org Benchmarks

| Metric | Healthy Range | Warning Sign |
|--------|---------------|--------------|
| Span of control | 5-8 direct reports | < 3 or > 12 |
| Management layers | 4-6 for 500 people | Too many = slow decisions |
| IC-to-manager ratio | 6:1 to 10:1 | < 4:1 = top-heavy |
| Team size | 5-9 people | < 4 = lonely, > 12 = hard to manage |

## Output

Produce org charts (text-based), headcount plans with cost modeling, and sequenced hiring roadmaps. Flag structural issues like single points of failure or excessive management overhead.