high-output-management

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

High Output Management

高效产出管理

Think like Intel's legendary CEO. Apply Andy Grove's management operating system to maximize your team's output through leverage, OKRs, and systematic decision-making.

像英特尔传奇CEO一样思考。运用Andy Grove的管理操作系统，通过杠杆效应、OKRs和系统化决策最大化团队产出。

When to Use This Skill

适用场景

Scaling a team when individual contribution isn't enough
Performance management to measure and improve output
Meeting optimization to make meetings productive
Decision-making in management contexts
New manager transition from individual contributor
Organizational design for efficiency

团队扩张：当个人贡献不足以支撑发展时
绩效管理：衡量并提升产出
会议优化：让会议更具成效
管理决策：各类管理场景下的决策
新任管理者转型：从个人贡献者转型为管理者
组织设计：提升效率

Methodology Foundation

方法论基础

Aspect	Details
Source	Andy Grove - High Output Management (1983)
Core Principle	"A manager's output = Output of their organization + Output of neighboring organizations under their influence."
Why This Matters	Management is a skill, not just a title. Grove's engineering approach to management created modern tech management practices, including OKRs (used by Google, Intel, LinkedIn, etc.).

维度	详情
来源	Andy Grove - 《高效产出管理》（1983）
核心原则	"管理者的产出 = 其负责组织的产出 + 受其影响的相邻组织的产出。"
重要性	管理是一项技能，而非仅仅是头衔。Grove的工程化管理方法奠定了现代科技行业的管理实践，包括OKRs（被谷歌、英特尔、领英等公司采用）。

What Claude Does vs What You Decide

Claude的职责 vs 你的决策

Claude Does	You Decide
Structures analysis frameworks	Strategic priorities
Synthesizes market data	Competitive positioning
Identifies opportunities	Resource allocation
Creates strategic options	Final strategy selection
Suggests implementation approaches	Execution decisions

Claude负责	由你决定
构建分析框架	战略优先级
整合市场数据	竞争定位
识别机会	资源分配
创建战略选项	最终战略选择
建议实施方法	执行决策

What This Skill Does

本技能的作用

Defines management as output - Measurable, not abstract
Teaches leverage - Maximize output per unit of management time
Structures 1:1s and meetings - For information gathering and decision-making
Introduces OKRs - Objectives and Key Results framework
Builds management rhythm - Systematic operating cadence
Improves performance management - Task-relevant maturity

将管理定义为产出——可衡量，而非抽象概念
传授杠杆效应——最大化单位管理时间的产出
构建1:1沟通和会议体系——用于信息收集和决策
引入OKRs——目标与关键成果框架
建立管理节奏——系统化的运营周期
优化绩效管理——任务相关成熟度管理

How to Use

使用方法

Design Your Management System

设计你的管理系统

I'm managing a team of [X] people doing [type of work].
Help me design a Grove-style management operating system.

我管理着一支[X]人的团队，从事[工作类型]。
帮我设计一套Grove风格的管理操作系统。

Improve Your Leverage

提升你的杠杆效应

I'm spending my time on [activities].
Apply High Output Management thinking to improve my leverage.

我目前在[具体活动]上花费时间。
运用高效产出管理思维提升我的杠杆效应。

Set Up OKRs

制定OKRs

Help me create OKRs for [team/individual/company].
Context: [current goals, challenges]

帮我为[团队/个人/公司]制定OKRs。
背景：[当前目标、挑战]

Instructions

操作步骤

Step 1: Understand Management as Production

步骤1：将管理视为生产过程

undefined

undefined

The Production Principle

生产原则

Grove's Key Insight

Grove的核心洞察

Management isn't about status or authority. Management is about OUTPUT.

A manager's output = Output of their team + Output of other teams they influence

管理无关地位或权威。管理的核心是产出。

管理者的产出 = 团队产出 + 受其影响的其他团队产出

The Factory Analogy

工厂类比

Think of your team as a production line:

Raw materials → Work in progress → Finished goods
Input → Process → Output

Your job:

Identify limiting steps
Remove bottlenecks
Increase throughput
Maintain quality

将你的团队视为一条生产线：

原材料 → 在制品 → 成品
输入 → 流程 → 输出

你的职责：

识别瓶颈环节
消除障碍
提升吞吐量
维持质量

Manager Activities

管理者的活动分类

Everything you do falls into three categories:

1. Information gathering

1:1s
Staff meetings
Reports
Walking around

2. Information giving

Direction setting
Teaching
Decisions communicated
Feedback

3. Decision-making

Prioritization
Resource allocation
Hiring/firing
Process design

你所做的一切都可归为三类：

1. 信息收集

1:1沟通
团队会议
报告
走动式管理

2. 信息传递

方向设定
培训指导
决策传达
反馈

3. 决策制定

优先级排序
资源分配
招聘/解雇
流程设计

The Leverage Equation

杠杆公式

Leverage = Output / Activity

High leverage activities:

Training (multiplies across many people)
Decisions (unlock blocked work)
Systems (automate repeated work)

Low leverage activities:

Doing work others could do
Meetings without decisions
Reviewing what's already done well

---

杠杆效应 = 产出 / 活动

高杠杆活动：

培训（效果覆盖多人）
决策（解锁受阻工作）
系统搭建（自动化重复工作）

低杠杆活动：

做他人可完成的工作
无决策的会议
审核已完成的优质工作

---

Step 2: Master Management Leverage

步骤2：掌握管理杠杆

undefined

undefined

Types of Leverage

杠杆类型

High Leverage Activities

高杠杆活动

1. Training An hour spent training 10 people = 10 hours of improved output. Training has the highest ROI of any management activity.

Questions:

Who on my team could I train?
What knowledge do I have that would help them?
How can I systematize training?

2. Decisions that unblock work When your decision is the bottleneck, make it. Delayed decisions multiply delays.

Questions:

What decisions are people waiting on?
Which decisions must be mine vs. delegated?
How fast am I making decisions?

3. Motivation and recognition Peak performance requires motivation, not just direction. Recognition costs you nothing but drives output.

Questions:

Who deserves recognition this week?
What motivates each person on my team?
Am I providing meaning, not just tasks?

1. 培训 花1小时培训10人 = 获得10小时的产出提升。培训是所有管理活动中投资回报率最高的。

思考问题：

团队中哪些人需要我培训？
我拥有哪些能帮助他们的知识？
如何系统化培训？

2. 解锁工作的决策 当你的决策是瓶颈时，尽快做出决策。延迟决策会导致延误扩散。

思考问题：

大家在等待哪些决策？
哪些决策必须由我做出，哪些可以授权？
我的决策速度如何？

3. 激励与认可 巅峰绩效需要激励，而非仅仅是指令。认可无需成本，却能显著提升产出。

思考问题：

本周谁值得认可？
团队中每个人的激励点是什么？
我是否在赋予工作意义，而非仅分配任务？

Low Leverage Traps

低杠杆陷阱

1. Doing work yourself If someone else can do it 70% as well, delegate. Your job is enabling output, not doing output.

2. Attending meetings you don't need Every meeting is time not doing high-leverage work. Audit: "Would this meeting happen without me?"

3. Over-reviewing work Review is valuable. Over-review is micromanagement. Match review depth to risk and skill level.

1. 亲力亲为 如果他人能完成70%的质量，就授权出去。你的职责是赋能产出，而非亲自产出。

2. 参加不必要的会议 每一场会议都占用了你做高杠杆工作的时间。审核标准：“没有我，这场会议还会召开吗？”

3. 过度审核工作 审核有价值，但过度审核就是微观管理。根据风险和技能水平匹配审核深度。

The Meddling Trap

干预陷阱

Signs you're meddling:

Making decisions your team should make
Reviewing work that doesn't need review
Being in every meeting
People wait for your approval on everything

The fix: Delegate. Then don't take it back.

---

干预的迹象：

做出团队本应自行做出的决策
审核无需审核的工作
参加所有会议
凡事都需要你的批准

解决方法： 授权，然后不要收回。

---

Step 3: Run Effective Meetings

步骤3：高效运行会议

undefined

undefined

Grove on Meetings

Grove的会议理念

Two Types of Meetings

两类会议

Process-oriented meetings (Regular)

1:1s
Staff meetings
Operations reviews

Purpose: Information flow, coordination, rhythm

Mission-oriented meetings (Ad hoc)

Decisions needed
Problems to solve
Opportunities to evaluate

Purpose: Make a decision, then disband

流程导向型会议（常规）

1:1沟通
团队会议
运营回顾

目的：信息流转、协调、维持节奏

任务导向型会议（临时）

需要做出决策
需要解决问题
需要评估机会

目的：做出决策后解散

The 1:1

1:1沟通

Purpose:

Information exchange (both ways)
Mutual teaching and coaching
Problem surfacing
Relationship building

Frequency: Depends on task-relevant maturity (more often for newer/struggling people). Weekly is baseline. Bi-weekly for senior/independent people.

Agenda: Report's agenda, not manager's. Manager asks questions, doesn't lecture.

Structure:

Report shares what's going well
Report shares challenges/blockers
Manager asks clarifying questions
Discussion of development/priorities
Manager shares relevant context

Key principle: The 1:1 is their meeting, not yours.

目的：

双向信息交流
相互教学与辅导
发现问题
建立关系

频率： 取决于任务相关成熟度（新人或绩效不佳者更频繁）。每周一次为基准，资深/独立员工可每两周一次。

议程： 由汇报者制定，而非管理者。管理者多提问，少说教。

结构：

汇报者分享进展
汇报者分享挑战/障碍
管理者提出澄清问题
讨论发展/优先级
管理者分享相关背景信息

核心原则： 1:1沟通是汇报者的会议，而非你的。

Staff Meetings

团队会议

Purpose:

Cross-team information sharing
Peer-level problem solving
Coordination decisions

What doesn't belong:

Reporting what could be read
Manager lecturing
Decisions without the right people

Facilitation: Manager as facilitator, not star. "What does the group think?"

目的：

跨团队信息共享
同级问题解决
协调决策

不应包含的内容：

可通过阅读获取的汇报
管理者说教
缺少关键人员的决策

主持方式： 管理者作为主持人，而非主角。多问：“大家怎么看？”

Operations Reviews

运营回顾

Purpose:

Present to senior management
Teaching tool (everyone learns)
Accountability mechanism

Format: Formal presentation + Q&A Monthly or quarterly

目的：

向高层汇报
教学工具（全员学习）
问责机制

形式： 正式演示 + 问答每月或每季度一次

Decision Meetings

决策会议

Purpose: Make a specific decision

Requirements:

Clear decision to be made
Right people in the room
Data/options prepared
End with decision + owner

Rule: If you didn't make a decision, the meeting failed.

---

目的： 做出特定决策

要求：

明确要做出的决策
关键人员到场
准备好数据/选项
结束时明确决策及负责人

规则： 如果未做出决策，会议就是失败的。

---

Step 4: Implement OKRs

步骤4：实施OKRs

undefined

undefined

Objectives and Key Results

目标与关键成果（OKRs）

Origin

起源

Andy Grove invented OKRs at Intel. John Doerr brought them to Google. Now used by thousands of companies.

Andy Grove在英特尔发明了OKRs。 John Doerr将其引入谷歌。如今被数千家公司采用。

The Framework

框架

Objective: What do we want to achieve?

Qualitative
Inspirational
Time-bound (usually quarterly)

Key Results: How will we know we achieved it?

Quantitative
Measurable
3-5 per objective

目标（Objective）： 我们想要达成什么？

定性描述
具有启发性
有时间限制（通常为季度）

关键成果（Key Results）： 如何判断我们是否达成了目标？

定量描述
可衡量
每个目标对应3-5个关键成果

Good OKRs

优秀OKRs示例

Objective: Become the preferred CRM for mid-market companies

Key Results:

Increase NPS from 42 to 55
Grow mid-market ARR from $5M to $8M
Reduce mid-market churn from 8% to 5%
Launch 3 features identified by mid-market research

目标：成为中端市场首选的CRM

关键成果：

将NPS从42提升至55
将中端市场ARR从500万美元增长至800万美元
将中端市场客户流失率从8%降至5%
推出3项中端市场调研确定的功能

Bad OKRs

糟糕OKRs示例

Objective: Improve the product

Key Results:

Ship features
Fix bugs
Make customers happy

Problems:

Objective is vague
Key results aren't measurable
No targets to aim for

目标：改进产品

关键成果：

发布功能
修复漏洞
让客户满意

问题：

目标模糊
关键成果不可衡量
没有明确的目标值

OKR Principles

OKR原则

1. Cascading alignment Company OKRs → Team OKRs → Individual OKRs Each level supports the level above.

2. Stretch goals 70% achievement = success 100% = you aimed too low If you always hit OKRs, they're not ambitious enough.

3. Public and transparent Everyone can see everyone's OKRs. Creates alignment and accountability.

4. Separate from compensation OKRs are for focus and alignment. Don't tie to bonuses (creates sandbagging).

1. 层级对齐 公司OKRs → 团队OKRs → 个人OKRs 每个层级支撑上一层级。

2. 挑战性目标 完成70%即为成功完成100%说明目标设置过低如果你总能达成OKRs，说明目标不够有野心。

3. 公开透明 所有人都能看到他人的OKRs。促进对齐和问责。

4. 与薪酬分离 OKRs用于聚焦和对齐。不要与奖金挂钩（会导致目标缩水）。

OKR Cadence

OKR周期

Quarterly:

Set new OKRs at quarter start
Review at quarter end
Score (0.0 to 1.0)

Weekly:

Check in on key results
Adjust activities
Surface blockers

Never:

Change OKRs mid-quarter (unless massive shift)
Let OKRs become task lists
Forget to review

---

季度：

季度初制定新OKRs
季度末回顾
评分（0.0至1.0）

每周：

跟进关键成果进展
调整活动
发现障碍

禁止：

季度中途更改OKRs（除非发生重大变化）
将OKRs变成任务清单
忘记回顾

---

Step 5: Task-Relevant Maturity

步骤5：任务相关成熟度

undefined

undefined

Matching Management to Maturity

匹配管理风格与成熟度

The Framework

框架

Task-Relevant Maturity (TRM): How experienced/capable is this person at THIS specific task?

Note: Not overall experience. Task-specific.

任务相关成熟度（TRM）： 此人在这项特定任务上的经验/能力如何？

注意：并非整体经验，而是任务特定的。

TRM Levels and Management Style

TRM层级与管理风格

Low TRM:

New to task
Uncertain, needs guidance
Might fail without support

Management style: Structured

Clear instructions
Defined process
Frequent check-ins
More directive

Medium TRM:

Some experience
Can do basics independently
Needs coaching for advanced

Management style: Coaching

Ask more than tell
Check results, not process
Problem-solve together
Guide decisions

High TRM:

Expert at this task
Knows more than you might
Self-directed

Management style: Delegation

Set objectives, let them run
Infrequent check-ins
Available when needed
Trust their judgment

低TRM：

刚接触任务
不确定，需要指导
若无支持可能失败

管理风格：结构化

明确指令
定义流程
频繁检查
更具指导性

中TRM：

有一定经验
能独立完成基础工作
高级工作需要辅导

管理风格：教练式

多提问少指令
检查结果而非流程
共同解决问题
引导决策

高TRM：

该任务的专家
可能比你更了解
自主驱动

管理风格：授权式

设置目标，让其自主执行
较少检查
需要时提供支持
信任其判断

The Matching Principle

匹配原则

Wrong match = Problems:

High TRM + Directive = Demotivation "You're micromanaging me!"

Low TRM + Delegation = Failure "I didn't know what I was doing and no one helped."

错误匹配 = 问题：

高TRM + 指令式管理 = 积极性受挫 “你在微观管理我！”

低TRM + 授权式管理 = 失败 “我不知道该做什么，也没人帮我。”

TRM Is Task-Specific

TRM是任务特定的

Example: A senior engineer (High TRM at coding) who becomes a manager is Low TRM at management. Manage them accordingly.

Reassess when:

New tasks/responsibilities
New environment
Declining performance
Explicit request for support

---

示例： 一位资深工程师（编码方面高TRM）晋升为技术主管在管理方面属于低TRM。需相应调整管理方式。

重新评估时机：

新任务/职责
新环境
绩效下滑
明确请求支持

---

Examples

示例

Example 1: Management Operating System Design

示例1：管理操作系统设计

Input:

"I manage a team of 8 engineers. I feel like I'm in meetings all day and not adding value. Help me design a Grove-style management system."

Output:

输入：

"我管理着一支8人的工程师团队。我感觉整天都在开会，没有创造价值。帮我设计一套Grove风格的管理系统。"

输出：

Management Operating System: Engineering Team

管理操作系统：工程师团队

Current State Analysis

当前状态分析

8 direct reports = Full management load

Grove recommends 6-8 direct reports maximum. You're at capacity. Focus on leverage.

8位直接下属 = 满负荷管理

Grove建议最多6-8位直接下属。你已达容量上限。聚焦杠杆效应。

Weekly Rhythm

每周节奏

Day	AM	PM
Monday	1:1s (2)	Team Planning
Tuesday	1:1s (2)	Focus Time
Wednesday	1:1s (2)	Cross-Team Sync
Thursday	1:1s (2)	Focus Time
Friday	Staff Meeting	Decision Time

Total 1:1 time: 4-8 hours/week (30-60 min each) Total meeting time: ~12 hours/week Focus/leverage time: ~20 hours/week

日期	上午	下午
周一	1:1沟通（2次）	团队规划
周二	1:1沟通（2次）	专注时间
周三	1:1沟通（2次）	跨团队同步
周四	1:1沟通（2次）	专注时间
周五	团队会议	决策时间

1:1沟通总时长： 4-8小时/周（每次30-60分钟） 会议总时长： ~12小时/周 专注/杠杆工作时间： ~20小时/周

Meeting Structure

会议结构

1:1s (30-60 min each)

Template:
1. How are you doing? (5 min)
   - Energy, mood, blockers

2. What did you accomplish? (10 min)
   - Celebrate wins
   - Surface issues early

3. What's challenging? (15 min)
   - Blocker removal
   - Coaching opportunities

4. What's next? (10 min)
   - Priorities aligned
   - Support needed

5. Anything else? (5 min)
   - Open floor

Staff Meeting (Friday, 60 min)

Agenda:
1. Announcements (5 min)
   - Company updates, logistics

2. Metrics review (10 min)
   - Key team metrics
   - Trends, anomalies

3. Around the horn (20 min)
   - Each person: 2 min
   - What's going well, what's stuck

4. Discussion topic (20 min)
   - One deep dive
   - Rotating owner each week

5. Decisions needed (5 min)
   - Quick decisions or schedule decision meeting

1:1沟通（每次30-60分钟）

模板：
1. 近况如何？（5分钟）
   - 精力、情绪、障碍

2. 完成了什么？（10分钟）
   - 庆祝成果
   - 尽早发现问题

3. 遇到了哪些挑战？（15分钟）
   - 消除障碍
   - 辅导机会

4. 下一步计划？（10分钟）
   - 对齐优先级
   - 需要的支持

5. 其他事项？（5分钟）
   - 自由交流

团队会议（周五，60分钟）

议程：
1. 公告（5分钟）
   - 公司更新、后勤事项

2. 指标回顾（10分钟）
   - 关键团队指标
   - 趋势、异常

3. 轮流发言（20分钟）
   - 每人2分钟
   - 进展、卡点

4. 深度讨论（20分钟）
   - 一个主题深入探讨
   - 每周轮换主持人

5. 待决策事项（5分钟）
   - 快速决策或安排决策会议

Leverage Analysis

杠杆效应分析

High Leverage Activities (Increase these):

Activity	Current	Target	How
Training/coaching	2 hr/wk	5 hr/wk	Add 30 min to each 1:1 for skill building
Decision-making	Reactive	Proactive	Schedule "Decision Time" Friday PM
System building	0 hr/wk	3 hr/wk	One system improvement per week

Low Leverage Activities (Reduce these):

Activity	Current	Action
Status meetings	4 hr/wk	Async updates, meeting only for discussion
Code review	5 hr/wk	Reduce to critical PRs only
Attending meetings	Many	Ask: "Do they need me?"

高杠杆活动（增加）：

活动	当前	目标	方法
培训/辅导	2小时/周	5小时/周	每次1:1沟通增加30分钟技能培养
决策制定	被动	主动	周五下午安排“决策时间”
系统搭建	0小时/周	3小时/周	每周完成一项系统改进

低杠杆活动（减少）：

活动	当前	行动
状态会议	4小时/周	异步更新，仅讨论时开会
代码审核	5小时/周	仅审核关键PR
参会	多次	自问：“他们需要我吗？”

Management Dashboard

管理仪表盘

Track weekly:

undefined

每周跟踪：

undefined

Week of [Date]

[日期]周

Team Output

团队产出

My Activities

我的活动

Next Week Focus

下周重点

Example 2: OKR Creation

示例2：OKR制定

Input:

"Help me create OKRs for my product marketing team. We're focused on launching a new product line and improving our competitive positioning."

Output:

输入：

"帮我为产品营销团队制定OKRs。我们专注于推出新产品线并提升竞争定位。"

输出：

Q2 OKRs: Product Marketing Team

Q2 OKRs：产品营销团队

Objective 1: Successfully launch Product Line X

目标1：成功推出产品线X

Key Results:

KR	Metric	Current	Target
1.1	Launch assets delivered on time	N/A	100%
1.2	Sales team trained	0%	100% enabled
1.3	Pipeline generated in first 30 days	$0	$500K
1.4	Analyst coverage secured	0	3 analysts

Initiatives:

Create launch messaging and positioning
Build sales enablement kit
Execute launch campaign
Brief analysts

关键成果：

KR	指标	当前值	目标值
1.1	按时交付发布物料	N/A	100%
1.2	销售团队完成培训	0%	100%具备能力
1.3	发布首30天生成的销售线索	$0	$50万
1.4	获得分析师报道	0	3位分析师

行动计划：

制定发布信息和定位
构建销售赋能工具包
执行发布活动
对接分析师

Objective 2: Establish clear competitive differentiation

目标2：建立清晰的竞争差异化

Key Results:

KR	Metric	Current	Target
2.1	Sales win rate vs. competitor A	35%	50%
2.2	Battle cards usage by sales	20%	80%
2.3	Competitive content produced	2 assets	10 assets
2.4	Sales confidence score (survey)	3.2/5	4.2/5

Initiatives:

Deep competitive analysis
Create/update battle cards
Competitive training sessions
Win/loss program

关键成果：

KR	指标	当前值	目标值
2.1	对比竞品A的销售赢单率	35%	50%
2.2	销售团队使用竞争手册的比例	20%	80%
2.3	产出的竞争内容数量	2份	10份
2.4	销售信心评分（调研）	3.2/5	4.2/5

行动计划：

深度竞争分析
创建/更新竞争手册
竞争培训课程
赢单/丢单分析项目

Objective 3: Improve product marketing efficiency

目标3：提升产品营销效率

Key Results:

KR	Metric	Current	Target
3.1	Time from product brief to launch	8 weeks	5 weeks
3.2	Asset reuse rate	15%	40%
3.3	Sales satisfaction with PMM	3.5/5	4.5/5

Initiatives:

Templatize launch playbook
Build reusable content library
Weekly sales sync

关键成果：

KR	指标	当前值	目标值
3.1	从产品 brief 到发布的时间	8周	5周
3.2	物料复用率	15%	40%
3.3	销售对产品营销的满意度	3.5/5	4.5/5

行动计划：

模板化发布手册
构建可复用内容库
每周销售同步会议

OKR Tracking Cadence

OKR跟踪周期

Weekly:

Update key result progress
Identify blockers
Adjust activities (not OKRs)

Monthly:

OKR review in staff meeting
Score progress (0.0-1.0)
Course correct

End of Quarter:

Final scoring
Retrospective
Input to next quarter OKRs

每周：

更新关键成果进展
识别障碍
调整活动（而非OKRs）

每月：

团队会议中回顾OKRs
评分（0.0-1.0）
调整方向

季度末：

最终评分
回顾总结
为下季度OKRs提供输入

OKR Scoring Guide

OKR评分指南

Score	Meaning
0.0-0.3	Failed to make progress
0.4-0.6	Progress but fell short
0.7-0.9	Strong delivery
1.0	Fully achieved (maybe too easy?)

Target: Average 0.7 across OKRs

分数	含义
0.0-0.3	未取得进展
0.4-0.6	有进展但未达目标
0.7-0.9	出色交付
1.0	完全达成（可能目标过低？）

目标： OKRs平均得分0.7

Example 3: Task-Relevant Maturity Assessment

示例3：任务相关成熟度评估

Input:

"I have a team member who's been an engineer for 5 years but just got promoted to tech lead. How do I manage them?"

Output:

输入：

"我有一位团队成员，做了5年工程师，刚晋升为技术主管。我该如何管理他？"

输出：

TRM Assessment: New Tech Lead

TRM评估：新任技术主管

Analysis

分析

Overall experience: High (5 years engineering) Task-relevant maturity for leadership: Low

Why Low TRM for leadership:

First time leading
Different skills required
New failure modes
New stakeholder relationships

整体经验： 丰富（5年工程师经验） 领导力任务相关成熟度： 低

领导力TRM低的原因：

首次担任领导角色
需要不同的技能
面临新的失败模式
需要建立新的利益相关者关系

Recommended Management Approach

Activity	Frequency	Purpose
1:1s	2x/week	Close monitoring
Check-ins	Daily	Surface problems early
Shadowing	Key meetings	Teach by example

Activity	Frequency	Purpose
1:1s	Weekly	Reflection and learning
Check-ins	2x/week	Lighter touch
Debrief	After key situations	Extract learnings

Activity	Frequency	Purpose
1:1s	Weekly or bi-weekly	Partnership
Check-ins	As needed	Available when called

活动	频率	目的
1:1沟通	每周2次	密切监控
日常检查	每日	尽早发现问题
陪同参会	关键会议	以身作则教学

活动	频率	目的
1:1沟通	每周1次	反思与学习
检查	每周2次	轻量级跟进
复盘	关键事件后	提取经验

活动	频率	目的
1:1沟通	每周或每两周1次	伙伴关系
检查	按需	需要时提供支持

Warning Signs to Watch

需要关注的预警信号

Struggling (intervene):

Team complaining about lack of direction
Decisions being avoided
Burnout signs
Reverting to IC work

Thriving (celebrate):

Team is productive
Confident in decisions
Seeking new challenges
Developing others

表现不佳（需干预）：

团队抱怨缺乏方向
回避决策
倦怠迹象
回归个人贡献者工作

表现出色（需庆祝）：

团队高效产出
决策自信
寻求新挑战
培养他人

The Transition Conversation

转型沟通话术

"[Name], you've been a strong engineer, and I'm excited about your move to tech lead. I want to be clear: this is a new job with new skills.

For the first month, I'm going to be more hands-on than usual. Not because I don't trust you—because I do—but because leadership has different failure modes than engineering, and I want to set you up to succeed.

As you get more comfortable, I'll step back. My goal is for you to be running your team independently within 90 days.

What questions do you have? What are you most nervous about?"

“[姓名]，你一直是一位优秀的工程师，我对你晋升技术主管感到兴奋。我想明确：这是一份新工作，需要新的技能。

第一个月，我会比平时更介入。不是因为我不信任你——恰恰相反——而是因为领导力的失败模式与工程不同，我想帮你成功。

当你逐渐适应后，我会退居幕后。我的目标是让你在90天内能够独立管理团队。

你有什么问题？你最担心什么？”

Checklists & Templates

清单与模板

Weekly Management Review

每周管理回顾

undefined

undefined

Week of [Date] - Management Review

[日期]周 - 管理回顾

Team Output

团队产出

Shipped: [list]
Progress: [key initiatives]
Quality: [issues, wins]

交付：[列表]
进展：[关键举措]
质量：[问题、成果]

Leverage Assessment

杠杆效应评估

High leverage hours: [X] / Target: [Y]
Low leverage activities cut: [list]
Decisions made: [list]
Blockers removed: [list]

高杠杆工作时长：[X] / 目标：[Y]
减少的低杠杆活动：[列表]
做出的决策：[列表]
消除的障碍：[列表]

People

人员管理

1:1s completed: [X]/[Y]
Development conversations: [who]
Recognition given: [who, what]
Performance concerns: [who, what]

完成1:1沟通：[X]/[Y]
发展对话：[对象]
给予的认可：[对象、事由]
绩效问题：[对象、问题]

Improvement

改进方向

What did I do this week that only I could do?
What did I do that someone else should do?
What should I do more of next week?

---

本周我做了哪些只有我能做的事？
本周我做了哪些本该由他人做的事？
下周我应该多做什么？

---

1:1 Template

1:1沟通模板

undefined

undefined

1:1 with [Name] - [Date]

与[姓名]的1:1沟通 - [日期]

Check-in

近况检查

How are you doing? (1-10)
What's your energy like?

近况如何？（1-10分）
精力状态如何？

Their Agenda

对方的议程

My Questions

我的问题

Discussion Notes

讨论记录

Decisions/Commitments

决策/承诺

Follow-ups

跟进事项

Me:
Them:

我：
对方：

Next 1:1

下次1:1沟通

Date:
Topic to revisit:

---

日期：
需回顾的主题：

---

Skill Boundaries

技能边界

What This Skill Does Well

本技能擅长

Structuring strategic analysis
Identifying market opportunities
Creating strategic frameworks
Synthesizing competitive data

构建战略分析框架
识别市场机会
创建战略框架
整合竞争数据

What This Skill Cannot Do

本技能无法做到

Replace market research
Guarantee strategic success
Know proprietary competitor info
Make executive decisions

替代市场调研
保证战略成功
知晓竞争对手的专有信息
做出高管决策

References

参考资料

Grove, Andy. "High Output Management" (1983, updated 1995)
Doerr, John. "Measure What Matters" (2018) - OKRs
Intel management practices
Google OKR implementation
Ben Horowitz on Grove's influence

Grove, Andy. 《高效产出管理》（1983，1995更新）
Doerr, John. 《这就是OKR》（2018）- OKRs相关
英特尔管理实践
谷歌OKR实施方法
Ben Horowitz关于Grove影响力的论述

Related Skills

Skill Metadata

技能元数据

Mode: centaur

yaml

name: high-output-management
category: leadership
subcategory: management
version: 1.0
author: MKTG Skills
source_expert: Andy Grove
source_work: High Output Management
difficulty: intermediate
estimated_value: $5,000+ management training
tags: [management, Andy Grove, Intel, OKRs, leverage, meetings, performance]
created: 2026-01-25
updated: 2026-01-25

模式: centaur

yaml

name: high-output-management
category: leadership
subcategory: management
version: 1.0
author: MKTG Skills
source_expert: Andy Grove
source_work: High Output Management
difficulty: intermediate
estimated_value: $5,000+ management training
tags: [management, Andy Grove, Intel, OKRs, leverage, meetings, performance]
created: 2026-01-25
updated: 2026-01-25