Back to Details

retaining-developers

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Retaining Developers

留住开发者

Before Starting

开始之前

Check for EM context first. If 
.agents/em-context.md
exists, read it. If a specific person is mentioned, 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

如何使用本技能

  • Engineer seems disengaged or at risk -> diagnose with The 5 States
  • Compensation or raise conversation -> start with Unappreciated -> Valued
  • Equity or options conversation at hire, refresh, or departure -> use Stock Options and Equity Conversations
  • Want to recognize someone but have no budget -> use Zero-Budget Recognition
  • Worried someone might be leaving but has not said anything -> use 5 Warning Signs of a Disengaging Engineer
  • Engineer already has another offer -> use When Someone Has Another Offer
  • 工程师表现出积极性下降或存在离职风险 -> 使用“五状态模型”进行诊断
  • 薪酬或加薪沟通 -> 从“未被认可”到“获得重视”的路径入手
  • 入职、股权激励刷新或离职时的Stock Options与Equity沟通 -> 使用Stock Options and Equity Conversations框架
  • 想要认可员工但没有预算 -> 使用零预算认可方案
  • 担心有人可能离职但对方尚未提及 -> 使用“工程师积极性下降的5个预警信号”
  • 工程师已收到其他offer -> 使用“当员工收到其他offer时”的应对方案

Default Response Shape

默认回应结构

When the user asks for help with retention, produce a practical manager response:
  1. Risk read: low / medium / high, with evidence from the prompt.
  2. Likely state: unappreciated, lonely, bored, stuck, apathetic, or mixed.
  3. What to verify in the next 1:1: 3-5 questions that are direct but not interrogating.
  4. Action plan: what to do this week, this month, and structurally.
  5. Conversation script: concrete wording the manager can use.
  6. What not to do: common overreactions that will make the situation worse.
If someone has already resigned or has another offer, do not pretend normal retention tactics are enough. Shift to: understand the reason, decide if there is a credible counter, treat them respectfully, and protect the relationship.
当用户寻求留存相关帮助时，生成实用的经理回应内容：
  1. 风险评估： 低/中/高，并附上来自用户提问的证据。
  2. 可能的状态： 未被认可、孤独、无聊、停滞、冷漠，或混合状态。
  3. 下次1:1沟通中需确认的问题： 3-5个直接但非质问式的问题。
  4. 行动计划： 本周、本月以及结构性的行动方案。
  5. 沟通脚本： 经理可直接使用的具体措辞。
  6. 禁忌事项： 可能会让情况恶化的常见过度反应。
如果员工已辞职或已收到其他offer，不要认为常规留存策略足够有效。应转为：了解离职原因、判断是否有可信的挽留方案、尊重对待员工、维护双方关系。

Retention Risk Diagnostic

留存风险诊断

Use this before choosing an intervention:
  • Signal strength: Is this one weak signal, a pattern over weeks, or a direct statement that they may leave?
  • State: Which of the five states best explains the behavior?
  • Specificity: Can the manager name the exact moment, project, decision, or pattern that caused the shift?
  • Agency: Is there something the manager can actually change, or is this outside the manager's control?
  • Time horizon: Is the risk immediate, emerging, or long-term?
  • Trust level: Will the engineer believe the manager is acting because they care, or only because they are afraid of losing them?
The last question matters. Retention attempts that appear only after someone disengages can feel transactional. Acknowledge that directly when needed.
在选择干预措施前，请使用以下维度进行诊断：
  • 信号强度： 这是单一微弱信号、持续数周的模式，还是员工直接表示可能离职的明确声明？
  • 状态： 五种状态中哪一种最能解释员工的行为？
  • 具体性： 经理能否指出导致员工状态转变的具体时刻、项目、决策或模式？
  • 可控性： 经理是否有实际可改变的因素，还是该因素超出经理的控制范围？
  • 时间紧迫性： 风险是即时的、正在显现的还是长期的？
  • 信任程度： 工程师会认为经理的行动是出于关心，还是仅仅因为害怕失去他们？
最后一个问题至关重要。仅在员工积极性下降后才采取的留存措施可能会显得功利化。必要时需直接承认这一点。

The 5 States

五状态模型

When a developer quits, it is often because they feel one of these five things. Use the inverse to diagnose and act.
What they feelWhat they need
UnappreciatedTo feel valued
LonelyTo feel connected
BoredTo feel challenged
StuckTo feel like they are growing
ApatheticTo feel passionate about the work
开发者离职通常是因为他们处于以下五种状态之一。可通过反向推导进行诊断并采取行动。
他们的感受他们的需求
未被认可获得重视感
孤独获得归属感
无聊获得挑战感
停滞获得成长感
冷漠重新燃起对工作的热情

1. Unappreciated -> Valued

1. 未被认可 -> 获得重视

Initial salary is critical. The first salary you offer sets an anchor that is hard to correct later. Underpaying at hire means you will always be playing catch-up. Raises feel like corrections, not rewards, and the gap in perceived appreciation accumulates.
Raise salary before they ask. When a developer has to ask for a raise, the damage is already done. It signals that you were not paying attention or were not advocating for them. Be proactive. Also: do not deny raises because the engineer earns more than you. That is not a competition.
Do not steal the thunder. When something good happens, like a promotion, milestone, or successful launch, let the engineer announce it. Good news should come from them. If you announce their achievements for them, you take the moment; if they announce it themselves, you amplify it.
Just tell them. Many managers recognize good work internally and assume the engineer knows. They often do not. Say it directly in a 1:1: "I wanted to tell you: the way you handled X was exactly what I needed. That made a real difference."
Recognition: Give them the stage. Let them write the Slack announcement for features they shipped, tag them publicly, and push for your people to get company recognition. Route praise through its source: if a VP is excited, ask them to tell the team directly.
初始薪资至关重要。 首次开出的薪资会设定一个难以改变的基准。入职时薪资过低意味着你将永远处于追赶状态。加薪会被视为弥补而非奖励，这种对“未被认可”的感知差距会不断累积。
在员工提出加薪前主动调整薪资。 当开发者不得不主动要求加薪时，伤害已经造成。这表明你没有关注他们的需求，也没有为他们争取权益。要积极主动。另外：不要因为工程师的薪资高于你就拒绝加薪，这不是竞争。
不要抢功。 当有好事发生时，比如晋升、里程碑达成或产品成功上线，让工程师自己宣布这个消息。好消息应该来自他们本人。如果你替他们宣布成就，会抢走属于他们的时刻；如果他们自己宣布，你只需进行放大即可。
直接表达认可。 许多经理会在内部认可员工的优秀工作，并认为员工自己知道。但实际上他们往往不知道。在1:1沟通中直接说：“我想告诉你：你处理X问题的方式正是我所需要的，这起到了真正的作用。”
认可方式： 给他们展示的舞台。让他们撰写自己负责功能上线的Slack公告，公开@他们，推动你的团队成员获得公司层面的认可。让赞美来自源头：如果副总裁对此感到兴奋，请他们直接告诉团队。

2. Lonely -> Connected

2. 孤独 -> 获得归属感

You cannot force people to connect, but you can create opportunities: team meetings, focus days outside the office, activities during working hours, and shared work that creates real memories.
Be honest in interviews about what your team culture actually looks like. If your team is mostly married with kids and nobody hangs out after work, say so. Do not let someone join expecting something that is not there.
你无法强迫人们建立联系，但可以创造机会：团队会议、外出专注日、工作时间内的活动，以及能创造真实共同记忆的协作工作。
在面试中要诚实地说明团队文化的实际情况。如果你的团队成员大多是已婚有孩子的人，且下班后不会一起聚会，就如实说明。不要让新成员加入后发现实际情况与预期不符。

3. Bored -> Challenged

3. 无聊 -> 获得挑战

The best lever is to delegate interesting tasks: writing technical designs, mentoring a new engineer, leading a cross-team effort, or owning a project area you currently hold.
Ask directly: "Do you feel challenged? What's missing from your work today?" Managers often assume they know what developers want instead of having the conversation.
最佳方法是委派有趣的任务：撰写技术设计文档、指导新工程师、领导跨团队项目，或负责你目前掌控的某个项目领域。
直接询问：“你觉得工作有挑战性吗？现在的工作中缺少什么？”经理常常假设自己知道开发者想要什么，而不是直接沟通。

4. Stuck -> Growing

4. 停滞 -> 获得成长

Even challenged developers can feel stuck if they cannot see a path forward. Career planning is your job.
Work through it together:
  • What are the requirements for the next level?
  • How far are they from it, and why? Be fully honest.
  • What tasks do they need to take on to get there?
  • What evidence will promotion decision-makers need to see?
If they want a management path and there is no open slot, make them your second-in-command where appropriate and let them experience parts of the work. Help them prepare. Never promise a timeline you do not control.
即使工作有挑战性，如果看不到前进的方向，开发者也会感到停滞。职业规划是你的职责。
与员工共同制定规划：
  • 晋升到下一职级的要求是什么？
  • 他们距离该要求还有多远，原因是什么？要完全坦诚。
  • 他们需要承担哪些任务才能达到要求？
  • 晋升决策者需要看到哪些证据？
如果他们想走管理路线但目前没有空缺职位，可在合适的情况下让他们担任你的副手，体验部分管理工作。帮助他们做好准备。永远不要承诺你无法控制的晋升时间表。

5. Apathetic -> Passionate

5. 冷漠 -> 重新燃起热情

When developers do not care about the product or customers, and only care about technical puzzles, engagement is fragile. Connect the team to the business: share customer success stories, bring in senior leaders to talk with the team, and involve developers in customer conversations when possible.
Do not fake passion. Find a real customer, business, craft, or ownership connection that the engineer can actually care about.
当开发者不再关心产品或客户，只关注技术难题时，他们的工作参与度会非常脆弱。将团队与业务联系起来：分享客户成功案例、邀请高层领导与团队交流、尽可能让开发者参与客户沟通。
不要假装热情。找到一个员工真正可以关心的真实客户、业务、技术领域或职责关联点。

Stock Options and Equity Conversations

Stock Options and Equity Conversations

Equity is one of the most misunderstood parts of compensation and one of the most common sources of silent resentment or missed retention opportunities. As EM, you are often the one who has, or can get, the context to have this conversation well.
Equity是薪酬中最容易被误解的部分之一，也是沉默不满或错失留存机会的常见根源。作为EM，你通常拥有或可以获取相关背景信息，从而更好地开展这类沟通。

At Hire

入职时

When a developer joins and receives an options grant, three numbers matter and most people do not explain them clearly:
  • Exercise price (strike price): What they will pay per share to own it. Set at fair market value on grant date.
  • Current price (FMV): What the company is currently worth per share.
  • The 10X scenario: What this could be worth if the company grows 10X.
Most people sign offer letters without understanding any of this. Be the person who explains it.
当开发者加入并获得期权授予时，有三个数字至关重要，但大多数人不会清晰解释：
  • Exercise price（行权价）： 他们购买每股股票所需支付的价格，设定于授予日的公平市场价值。
  • Current price（FMV，当前公平市场价值）： 公司当前每股的价值。
  • 10X场景： 如果公司规模增长10倍，这些期权可能的价值。
大多数人在签署offer时并不理解这些内容。请成为为他们解释的人。

At Tenure

任职期间

Additional grants are a common and underused retention tool. After a year or two of strong performance, a developer's original grant is largely vested and the "golden handcuffs" loosen. A refresh grant re-anchors the retention value and signals that you are investing in them long-term.
If your company has a refresh grant program, use it proactively. Do not wait for a developer to ask or start interviewing.
额外的股权激励是一种常见但未被充分利用的留存工具。在一两年的出色表现后，开发者最初的股权激励大多已归属，“金手铐”效应减弱。刷新股权激励可以重新锚定留存价值，并表明你在长期投资他们。
如果你的公司有股权激励刷新计划，请积极使用。不要等到开发者提出要求或开始面试其他工作。

At Departure

离职时

When someone leaves, there are three common scenarios and each needs a different conversation:
  1. Staying at a startup, going to a bigger company: They may be leaving unvested equity on the table. Help them understand what they are walking away from.
  2. Leaving before a liquidity event: Most options expire 90 days after departure. If they have in-the-money options, they may need to decide whether to exercise and pay for them.
  3. Leaving after a long tenure: If most options are vested, the financial picture is cleaner, but still worth reviewing together.
These conversations are not about keeping people against their will. They are about treating people with respect by making sure they understand their own financial situation.
当员工离职时，通常有三种场景，每种场景需要不同的沟通方式：
  1. 从初创公司跳槽到大公司： 他们可能会放弃未归属的Equity。帮助他们理解自己正在放弃的是什么。
  2. 在流动性事件前离职： 大多数期权在离职后90天到期。如果他们持有实值期权，可能需要决定是否行权并支付相关费用。
  3. 长期任职后离职： 如果大多数期权已归属，财务情况会更清晰，但仍值得一起回顾。
这些沟通不是为了强行留住员工，而是通过确保他们了解自己的财务状况来尊重他们。

Zero-Budget Recognition

零预算认可方案

Some of the most memorable recognition moments cost nothing. These are specific ideas that have worked:
Creative onboarding. When a new developer joins, send a personal newsletter introducing them to the team. Include their background, what they care about, and an interesting fact. It signals that they matter as a person, not just a resource.
The physical promotion ceremony. When a developer is promoted, do not just post it in Slack. Order a physical placard with their new title. Present it in person or ship it. The object makes the moment real.
The birthday widget. Add team birthdays to your engineering dashboard or status page. When someone's birthday appears on the Grafana screen the team stares at all day, it creates a small but noticed moment.
Surprise senior leader catch-up. Arrange a 30-minute casual conversation between a high-performing developer and a VP or senior leader they would not normally interact with. Not a presentation, just a conversation. The message it sends: you are seen at the highest levels.
Personalized books. When you see a developer struggling with a problem, send them a relevant book with a personal note. It says: "I pay enough attention to know what you are working on."
一些最令人难忘的认可时刻无需任何成本。以下是经过验证的具体想法：
创意入职欢迎。 当新开发者加入时，发送一份个人通讯向团队介绍他们，包括他们的背景、关心的事物以及一个有趣的事实。这表明他们作为个体受到重视，而不仅仅是一个资源。
实体晋升仪式。 当开发者晋升时，不要只在Slack上发布消息。定制一个带有新头衔的实体标牌，亲自颁发或邮寄给他们。这个实物会让这一刻变得真实。
生日小部件。 将团队成员的生日添加到工程仪表板或状态页面。当某人的生日出现在团队每天都会关注的Grafana屏幕上时，会创造一个微小但引人注意的时刻。
惊喜高层交流。 安排一位高绩效开发者与他们通常不会接触到的副总裁或高层领导进行30分钟的非正式交流。不是汇报，只是聊天。这传递的信息是：你在最高层级被关注。
个性化书籍。 当你看到开发者在某个问题上遇到困难时，送他们一本相关的书并附上个人留言。这表明：“我足够关注你，知道你正在做什么。”

5 Warning Signs of a Disengaging Engineer

工程师积极性下降的5个预警信号

By the time someone resigns, you have usually missed signals by weeks or months. Watch for:
  1. They stop speaking up in architecture meetings
  2. They stop pushing for better practices
  3. Documentation efforts disappear
  4. Tech debt tickets keep getting deprioritized without comment
  5. Standup updates get shorter and more mechanical
Each signal individually might mean nothing. Together, they often mean someone has already accepted another offer in their head and is waiting for the paperwork.
当员工辞职时，你通常已经错过信号数周甚至数月。请注意以下迹象：
  1. 他们在架构会议中不再发言
  2. 他们不再推动更好的实践
  3. 不再进行文档编写工作
  4. 技术债务工单不断被降优先级且无任何说明
  5. 站会更新变得越来越简短和机械
单个信号可能无关紧要，但多个信号同时出现通常意味着员工已经在心里接受了其他offer，只是在等待手续完成。

When Someone Has Another Offer

当员工收到其他offer时

Slow down. Do not immediately ask, "What will it take to keep you?" That can make the relationship feel purely transactional.
Use this order:
  1. Understand: "What made you start looking?" and "What does this new role give you that you feel you are missing here?"
  2. Check credibility: Can you actually change the root cause, or only offer a temporary patch?
  3. Decide on a counter: Counter only if the fix is real, fast, and fair to the rest of the team.
  4. Protect the relationship: If they leave, make the exit respectful. Alumni relationships matter.
If the root cause is boredom, stuckness, or compensation, a counter may work only if you can act concretely. If the root cause is trust, apathy, or a long pattern of neglect, a counter often just delays the resignation.
放慢节奏。不要立即问：“我需要做什么才能留住你？”这会让关系显得纯粹是功利性的。
请按照以下顺序处理：
  1. 了解原因： “是什么让你开始寻找新机会？”以及“这份新工作能给你提供什么你在这里无法获得的东西？”
  2. 判断可行性： 你是否真的能改变根本原因，还是只能提供临时解决方案？
  3. 决定是否挽留： 只有当解决方案真实、快速且对团队其他成员公平时，才提出挽留方案。
  4. 维护关系： 如果他们离职，请尊重地处理离职流程。校友关系很重要。
如果根本原因是无聊、停滞或薪酬，只有当你能采取具体行动时，挽留才可能有效。如果根本原因是信任、冷漠或长期的忽视，挽留通常只会延迟离职。

What Not to Do

禁忌事项

  • Do not offer generic praise when the person needs specific recognition, compensation action, or growth.
  • Do not create fake growth opportunities with no real scope or decision authority.
  • Do not guilt someone for leaving. It teaches the rest of the team that honesty is unsafe.
  • Do not promise promotion timelines you do not control.
  • Do not wait for annual review cycles if the retention risk is active now.
  • 当员工需要具体认可、薪酬调整或成长机会时，不要提供泛泛的表扬。
  • 不要创造没有实际范围或决策权限的虚假成长机会。
  • 不要因员工离职而指责他们。这会让团队其他成员认为诚实是不安全的。
  • 不要承诺你无法控制的晋升时间表。
  • 如果存在即时的留存风险，不要等待年度评审周期。

Final Caveat

最终提示

Not everything is in your hands. People get offers you cannot match, want to change domains, start companies, or relocate. When the time comes, part on good terms. Do not take it personally.
并非所有事情都在你的掌控之中。员工可能会收到你无法匹配的offer、想要转换领域、创业或搬迁。当该来的时候，体面地告别。不要把它个人化。

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

相关技能

  • engineer-motivation
    - The 3 Drivers framework helps understand what motivates each person before they disengage
  • managing-high-performers
    - High performers have specific retention risks: bored, stuck, burnout
  • delegation
    - Delegating challenging work is a retention lever
  • 1on1s
    - The place to diagnose which of the five states someone is in
  • team-health
    - Broader team signals often map to these five states
  • engineer-motivation
    - 三驱动框架可帮助在员工积极性下降前了解每个人的动力来源
  • managing-high-performers
    - 高绩效员工有特定的留存风险：无聊、停滞、 burnout
  • delegation
    - 委派有挑战性的工作是一种留存手段
  • 1on1s
    - 诊断员工处于五种状态中哪一种的场景
  • team-health
    - 更广泛的团队信号通常与这五种状态相关