Back to Details

managing-high-performers

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Managing High Performers

管理高绩效工程师

Before Starting

开始之前

Check for EM context first. If 
.agents/em-context.md
exists, read it. If the person is named, check 
.agents/reports/[name].md
.
If 
.agents/em-context.md
does not exist, ask for a minimal manager profile first and save it before giving detailed advice: role/title, team size, team mission or ownership area, and current challenge or priority.
If a specific person is central to the conversation and 
.agents/reports/[name].md
does not exist, ask for a minimal profile for that person first and save it before giving detailed advice: title/level, tenure, strengths, and current challenge or growth area.

If the conversation reveals durable new context later, update 
.agents/em-context.md
or 
.agents/reports/[name].md
automatically. Save stable facts and patterns, not guesses, transient frustration, or unresolved interpretations.

首先检查EM（工程经理）上下文。如果存在
.agents/em-context.md
，请阅读该文件。如果涉及具体人员，检查
.agents/reports/[name].md
。
如果
.agents/em-context.md
不存在，请先询问并保存经理的基本资料，之后再提供详细建议：职位/头衔、团队规模、团队使命或负责领域，以及当前挑战或优先级。
如果对话核心是特定人员且
.agents/reports/[name].md
不存在，请先询问并保存该人员的基本资料，之后再提供详细建议：头衔/级别、任职年限、优势，以及当前挑战或成长领域。

如果后续对话中出现新的持久上下文，请自动更新
.agents/em-context.md
或
.agents/reports/[name].md
。仅保存稳定的事实和模式，不保存猜测、暂时的沮丧或未解决的解读。

Response Style

回应风格

Keep the first answer concise and useful. Do not dump the whole framework unless the user asks for depth.
Default to:
  • State the likely diagnosis or recommendation first
  • Ask at most 2-3 targeted questions only if the missing context changes the advice
  • Give the next concrete action and, when useful, exact wording the manager can use
  • Mention the relevant framework briefly, but do not explain every part of it
  • Offer a deeper version only after the direct answer
首次回答要简洁实用。除非用户要求深入讲解，否则不要全盘输出整个框架。
默认遵循：
  • 先说明可能的诊断或建议
  • 仅当缺失的上下文会改变建议时，最多提出2-3个针对性问题
  • 给出下一个具体行动，必要时提供经理可直接使用的准确措辞
  • 简要提及相关框架，但无需解释每个部分
  • 仅在给出直接回答后，再提供深入版本选项

How to Use This Skill

如何使用本技能

  • Not sure what kind of challenge you're dealing with → The 4 Quadrants (start here)
  • High performer who wants to keep climbing vs. one who's settled → Rock Stars and Superstars
  • Promotion conversation or setting goals for a high performer → What to Do
  • High performer is damaging team dynamics or being a jerk → The Brilliant Jerk Problem
  • Senior engineer seems productive but quietly stagnating → The Diminishing XP Diagnostic
  • High performer is burning people out or burning themselves out → Pushers and Pullers
  • 不确定面临的挑战类型 → 四象限模型（从这里开始）
  • 想要持续晋升的高绩效者 vs 安于现状的高绩效者 → Rock Stars与Superstars
  • 与高绩效者的晋升对话或目标设定 → 行动指南
  • 高绩效者破坏团队氛围或成为刺头 → 天才刺头问题
  • 资深工程师看似高效但悄然停滞 → Diminishing XP诊断
  • 高绩效者让他人倦怠或自身倦怠 → Pushers与Pullers

Default Response Shape

默认回应框架

When helping with a high performer, avoid treating excellence as a generic good:
  1. Type of high performer: rock star, superstar, pusher, puller, brilliant jerk, bored expert, or burnout risk.
  2. Core tension: autonomy vs. oversight, growth vs. stability, impact vs. team cost.
  3. Manager move: goals, visibility, feedback, constraints, scope, or recovery.
  4. Conversation script: direct wording that respects their competence.
  5. Team impact: how to protect the rest of the team while keeping the person engaged.
If the issue is harmful behavior, do not excuse it because the person is talented.
在协助管理高绩效者时，避免将卓越视为通用优势：
  1. 高绩效者类型：rock star、superstar、pusher、puller、天才刺头、倦怠专家或倦怠风险者。
  2. 核心矛盾：自主 vs 监督、成长 vs 稳定、影响力 vs 团队成本。
  3. 经理行动：目标设定、曝光度、反馈、约束、范围调整或恢复措施。
  4. 对话脚本：尊重其能力的直接措辞。
  5. 团队影响：如何在保持该人员积极性的同时保护团队其他成员。
如果涉及有害行为，不要因其才华而姑息。

The 4 Quadrants

四象限模型

Not every "difficult" engineer is a rockstar problem. Diagnose first:
Low ConfidenceHigh Confidence
High AbilityNeeds a mentor to grow — this is where you come inYour (positive) headache
Low AbilityOften the wrong role/fit — be honest with expectationsAlmost impossible to work with — give honest feedback; if no improvement, cut it
The true rockstar challenge is High Ability + High Confidence:
  • They expect you to always challenge them with bigger and bigger projects
  • They have tons of ideas they want implemented
  • The question of promotion always hangs in the air — if the org doesn't grow, they'll leave
并非所有“难管理”的工程师都是明星工程师问题。先进行诊断：
低自信高自信
高能力需要导师指导成长——这正是你的职责你的（积极的）难题
低能力通常是岗位不匹配——坦诚告知预期几乎无法共事——给出坦诚反馈；若无改进，果断处理
真正的明星工程师挑战是高能力+高自信：
  • 他们期望你始终用更大的项目挑战他们
  • 他们有大量想要落地的想法
  • 晋升问题始终悬而未决——如果组织没有发展，他们会离职

Rock Stars and Superstars

Rock Stars与Superstars

From Radical Candor (Kim Scott): not every high performer wants the same thing. The mistake is assuming they do.
Superstars are on a steep growth trajectory — they want challenge, advancement, and new scope constantly. They're building toward something bigger. Managing them well means clearing the path, delegating high-visibility work, and being honest about what promotion requires.
Rock Stars are excellent performers in stable mode — the "rock" of the team. They're not stagnating; they're doing great work at a level they've chosen. They may have interests outside work, have reached a career equilibrium they're satisfied with, or simply not want the cost of constant upward movement. They are not under-performing. They are essential.
The management mistake: treating Rock Stars as Superstars who failed to advance. Asking them repeatedly "where do you see yourself in two years?" signals that their current contribution isn't enough. It creates pressure they didn't ask for and resentment they shouldn't have to manage.
What Rock Stars need: recognition for the stability and expertise they provide. Meaningful work. Not being pushed toward a path they haven't chosen.
What Superstars need: visible, difficult assignments. Regular feedback on what's between them and the next level. An honest answer to "what do I need to do to get there?"
A team that has both — and treats each well — is more resilient than one that only prizes the Superstar trajectory.
出自《激进坦诚》（Kim Scott）：并非所有高绩效者的需求都相同。错误的做法是假设他们需求一致。
Superstars处于快速成长轨道——他们渴望挑战、晋升和持续拓展工作范围。他们在为更远大的目标积累资本。管理好他们的关键是扫清障碍、委派高曝光度工作，并坦诚告知晋升所需条件。
Rock Stars是稳定状态下的优秀执行者——团队的“基石”。他们并非停滞不前，而是在自己选择的层面上完成出色工作。他们可能有工作之外的兴趣、已达到满意的职业平衡，或根本不想承担持续晋升的成本。他们没有表现不佳，而是团队不可或缺的成员。
管理误区：将Rock Stars视为未能晋升的Superstars。反复询问“你两年后想达到什么位置？”意味着他们当前的贡献还不够。这会给他们带来不必要的压力，引发本不该有的不满。
Rock Stars的需求：认可他们提供的稳定性和专业能力。有意义的工作。不要强迫他们走上未选择的道路。
Superstars的需求：高难度、高曝光度的任务。关于晋升所需条件的定期反馈。对“我需要做什么才能晋升？”给出坦诚回答。
同时拥有这两类人才并妥善管理的团队，比只重视Superstar成长轨迹的团队更具韧性。

How NOT to Manage a Rockstar

明星工程师管理禁忌

Overpromise. The worst thing you can do. Painting a picture of a promotion that doesn't happen — even if your manager overrules you at the last moment — destroys trust permanently. If it's not 100% up to you, don't promise.
Ignore advice. You'll get good ideas constantly. If you say you'll do something, do it. If you decide not to — explain why. Don't just endlessly implement everything to please them, either — you'll lose credibility with the rest of the team.
Micromanage. They want freedom. Trust them to come to you when they need you.
过度承诺：最糟糕的做法。描绘无法兑现的晋升前景——即使最后是你的上级否决了晋升——也会永久破坏信任。如果晋升并非完全由你决定，不要承诺。
无视建议：你会不断收到好点子。如果你说要做某事，就去做。如果决定不做——解释原因。但也不要为了取悦他们而全盘接受所有想法——否则你会失去团队其他成员的信任。
微观管理：他们渴望自由。相信他们会在需要时主动找你。

What to Do

行动指南

Set clear goals. Ambitious people love goals. If they're aiming for promotion: sit together and define exactly what they need to do to make it happen. Verify with your superiors that achieving those targets will almost guarantee it (and still — don't promise).
Delegate the hardest and most visible tasks. This is the best way to lay groundwork for their promotion. When everyone in the organization gets a chance to work with them — including your peers and your manager — they'll support the promotion when you suggest it.
Give unfiltered feedback. Giving tough feedback to someone who gives everything can feel like picking on them. Don't. Superstars are always looking for good feedback. Even if they disagree, they'll appreciate it.
Help them focus. High performers can be in many places at once, wanting to make things better everywhere. Listen to why they're focusing on what they are. Find alternative solutions. Align on what's truly important.
设定清晰目标：有抱负的人喜欢目标。如果他们目标是晋升：一起坐下来明确界定晋升所需完成的具体事项。与你的上级确认，达成这些目标几乎能保证晋升（即便如此——也不要承诺）。
委派最困难、曝光度最高的任务：这是为他们的晋升打下基础的最佳方式。当组织中的每个人——包括你的同事和上级——都有机会与他们合作时，他们会在你提议晋升时给予支持。
给出坦诚反馈：向全力以赴的人提出严厉反馈可能会感觉像是找茬。不要犹豫。Superstars始终在寻找有价值的反馈。即使他们不同意，也会感激你的坦诚。
帮助他们聚焦：高绩效者可能同时关注多个方向，想要改善所有环节。倾听他们聚焦当前事项的原因。寻找替代解决方案。对齐真正重要的事项。

Protecting Them from Burnout

预防职业倦怠

A rockstar may get frustrated when working on a very ambiguous problem that requires cross-team alignment. The complexity and stakeholder involvement slows them down, and they may overwork to compensate.
Options:
  • Provide a secondary project for a sense of accomplishment
  • Pair them with an engineer who is comfortable with ambiguity
  • If frustration is high and they want to move on, find a different project
明星工程师在处理需要跨团队协作的高度模糊问题时可能会感到沮丧。复杂性和利益相关者的参与会拖慢他们的进度，他们可能会通过过度工作来弥补。
可选措施：
  • 提供第二个项目，让他们获得成就感
  • 搭配一位擅长处理模糊性的工程师与他们合作
  • 如果他们极度沮丧并想换项目，为他们寻找其他合适的项目

The Brilliant Jerk Problem

天才刺头问题

Rockstars can become brilliant jerks if not managed. They may grow impatient with "slower" team members, dismiss questions they consider trivial.
In most cases, they have good intentions and are simply oblivious. Bringing it up directly usually fixes it. If the problem is genuinely unfixable, you may have to let them go — a brilliant jerk who damages team trust and morale is not worth it.
如果管理不当，明星工程师可能会变成天才刺头。他们可能对“速度较慢”的团队成员失去耐心，轻视他们认为琐碎的问题。
大多数情况下，他们并无恶意，只是缺乏察觉。直接指出问题通常能解决。如果问题确实无法解决，你可能不得不让他们离开——损害团队信任和士气的天才刺头不值得挽留。

The Diminishing XP Diagnostic

Diminishing XP诊断

Engineers who stay in the same role for years can quietly stagnate even when they appear productive — doing familiar work returns negligible growth while the requirements for promotion keep increasing.
The RPG analogy is useful: the same task that was a stretch challenge at mid-level becomes rote at senior level. Rote work produces disengagement that precedes departure by months or years, often before either the engineer or manager notices.
How to use this: Periodically map each senior engineer's primary skills against what they have actually worked on in the last two quarters. If every assignment falls within their existing comfort zone, they are grinding low-XP monsters.
The fix isn't a job switch — most organizations have internal opportunities, but those require active EM intervention to surface and assign. Ask directly: "What skills do you want to level up in the next six months that you haven't had the chance to?" Then design at least one assignment per cycle that sits in their zone of proximal development — hard enough to generate real growth, not so far beyond current capability that it produces failure.
在同一岗位任职多年的工程师，即使看似高效，也可能悄然停滞——重复熟悉的工作几乎无法带来成长，而晋升要求却在不断提高。
RPG游戏的类比很有用：在中级阶段是挑战性任务的工作，到了高级阶段就变成了例行公事。例行公事会导致工作倦怠，往往在工程师或经理察觉之前，几个月或几年后就会引发离职。
使用方法：定期梳理每位资深工程师的核心技能与过去两个季度的实际工作内容。如果所有任务都在他们现有的舒适区内，他们就是在刷低经验值的怪物。
解决方案并非换工作——大多数组织都有内部机会，但需要EM主动介入去发掘和分配。直接询问：“未来六个月你想提升哪些尚未有机会锻炼的技能？”然后在每个周期至少设计一个处于他们最近发展区的任务——难度足以带来真正的成长，但又不会超出当前能力范围导致失败。

Pushers and Pullers

Pushers与Pullers

High performers fall into two distinct patterns — and each needs a different response:
Pushers always want more: more responsibility, more recognition, more impact. They drive themselves hard and can handle almost anything. The problem: they burn the people around them. They create friction by moving faster than the team can follow, and can make colleagues feel inadequate or pressured.
What to do: tell them directly that their success depends on the people around them succeeding too. Help them see that not everyone operates at their pace — and that bringing people along is a leadership skill, not a compromise.
Pullers don't ask — but they'll take everything you give them. They do great work, are reliable, and exercise good judgment. Then one day they explode: burned out, resentful, or quietly checked out.
What to do: set expectations proactively. Actively offload things from their plate before they ask. Check in on their energy, not just their output.
Identifying which type you're dealing with changes what kind of support to provide.
高绩效者分为两种截然不同的类型——每种类型需要不同的应对方式：
Pushers总是想要更多：更多责任、更多认可、更多影响力。他们对自己要求严苛，几乎能应对任何事情。问题在于：他们会让周围的人倦怠。他们的节奏快到团队无法跟上，会让同事感到自卑或压力山大。
应对方法：直接告诉他们，他们的成功依赖于周围人的成功。帮助他们理解并非所有人都能跟上他们的节奏——带领他人共同成长是一项领导力技能，而非妥协。
Pullers不会主动索取——但你给的一切他们都会接受。他们工作出色、可靠、判断力强。然后某天他们会爆发：倦怠、不满，或悄然退出。
应对方法：主动设定预期。在他们提出要求前，主动为他们减负。关注他们的精力状态，而不仅仅是工作产出。
判断你面对的是哪种类型，会决定你提供何种支持。

Dive Deeper

深入探索

If the user asks where a framework came from, wants to read the original article, or wants more context — read 
references/sources.md
.
如果用户询问框架来源、想要阅读原文或需要更多上下文——请阅读
references/sources.md
。

Related Skills

相关技能

  • retaining-developers
    — Rockstars are primarily in the "Bored" and "Stuck" states
  • engineer-motivation
    — Use the 3 Drivers to find what kind of high-visibility work actually motivates them
  • delegation
    — Delegating high-visibility work is both retention and development
  • performance-reviews
    — Setting clear promotion criteria is how you manage expectations
  • retaining-developers
    —— 明星工程师主要处于“无聊”和“受阻”状态
  • engineer-motivation
    —— 利用三大驱动力找到真正能激励他们的高曝光度工作
  • delegation
    —— 委派高曝光度工作既是留存人才也是培养人才的方式
  • performance-reviews
    —— 设定清晰的晋升标准是管理预期的关键