Back to Details

difficult-situations

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Difficult Situations

棘手管理场景

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

本工具使用场景

  • Offensive or inappropriate remark posted in a team channel → Inappropriate Remarks in Team Channels
  • Engineer is venting about or criticizing your manager to you → When an Engineer Talks Badly About Your Manager
  • Letting someone go but their personal circumstances are terrible → Letting Someone Go When the Timing Is Terrible
  • Feeling guilty about leaving your own job → Quitting as a Manager: The Guilt That Comes With It
  • Planning or executing a layoff → Handling Layoffs
  • 团队频道中出现冒犯性或不当言论 → 团队频道中的不当言论处理
  • 工程师向你吐槽或批评你的直属经理 → 工程师诋毁直属经理时的处理
  • 需解雇员工但其个人处境极其艰难 → 员工处境艰难时的解雇处理
  • 对离职感到愧疚 → 经理离职：伴随的愧疚感处理
  • 规划或执行裁员 → 裁员处理

Default Response Shape

默认回应框架

For difficult situations, prioritize safety, clarity, and sequence:
  1. Situation read: what is at stake and who could be harmed.
  2. Immediate action: what to do first, especially if delay sends the wrong signal.
  3. Private follow-up: who needs a 1:1 and what to say.
  4. Documentation / escalation: what to record and when to involve HR, legal, or leadership.
  5. Repair path: how to stabilize trust after the acute moment.
If the situation may involve harassment, discrimination, threats, layoffs, or termination, advise involving the appropriate company process rather than improvising alone.
针对棘手场景，需优先考虑安全性、清晰度和处理顺序：
  1. 场景评估：明确风险点及可能受到伤害的对象。
  2. 立即行动：首先要做的事，尤其是延迟处理会传递错误信号的情况。
  3. 私下跟进：哪些人需要一对一沟通，以及沟通内容。
  4. 记录/上报：需要记录哪些信息，以及何时需要联系HR、法务或领导层。
  5. 修复路径：如何在危机过后稳定团队信任。
若场景涉及骚扰、歧视、威胁、裁员或解雇，建议遵循公司对应流程处理，而非自行应对。

Inappropriate Remarks in Team Channels

团队频道中的不当言论

When something offensive or inappropriate is posted in a team channel — a homophobic remark, a racist joke, a comment that demeans a colleague — you have to act. Not acting is a decision too, and the team is watching.
What to do:
  1. Don't ignore it or wait. The longer you wait, the more the silence reads as endorsement.
  2. Address it in the channel first, briefly. Something like: "That's not the kind of thing we share in this space." Keep it short and non-escalating in public.
  3. Follow up 1:1 with the person who posted it. Don't pile on publicly, but the private conversation needs to happen. Be clear about what the expectation is going forward.
  4. Check in with anyone who may have been affected. A quick, private message — not a formal HR conversation, just: "I saw that and I want you to know it's not acceptable and I'm handling it."
The goal is to protect the team environment without creating a public shaming event. Both things matter.
当团队频道中出现冒犯性或不当言论——如恐同言论、种族歧视玩笑、贬低同事的评论时，你必须采取行动。不作为也是一种决策，团队成员都在关注。
处理步骤：
  1. 不要忽视或拖延：等待时间越长，沉默越会被视为认可。
  2. 先在频道中简短回应：例如：“这类内容不适合在团队空间中分享。”公开回应需简洁且避免激化矛盾。
  3. 与发布者进行一对一跟进沟通：不要在公开场合指责，但私下沟通必须进行。明确告知对方未来的行为准则。
  4. 向可能受影响的人员确认情况：发送简短的私人消息——无需正式的HR沟通，只需说明：“我看到了那条内容，我想让你知道这是不可接受的，我正在处理。”
目标是维护团队环境，同时避免公开羞辱事件。这两点同样重要。

When an Engineer Talks Badly About Your Manager

工程师诋毁直属经理时的处理

A developer tells you in a 1:1 that your manager is incompetent, made a bad call, or is screwing over the team. Or they say it in a way that's clearly trying to get you to take a side.
This is a loyalty test dressed as a venting session.
What to do:
  • Don't agree, even if you partly do. Validating criticism of your manager — to a direct report — breaks the chain of trust in both directions. You become the person who talks about your manager with your team.
  • Don't dismiss it either. "I hear that you're frustrated with that decision" is honest. "My manager is fine, you just don't understand" is dishonest and condescending.
  • Redirect toward what's actionable. "I can't speak to what's behind that decision, but I can look into how it affects your work and whether there's a way I can advocate for something different."
  • If there's a genuine grievance, take it seriously. Separately from the conversation, evaluate whether the concern is legitimate. If it is — raise it through the right channels.
The line is: you can think critically about your manager's decisions. You can't commiserate about them with your reports.
开发者在一对一沟通中向你抱怨你的经理无能、决策失误或损害团队利益，或是试图引导你站队。
这是一场披着吐槽外衣的忠诚度测试。
处理步骤：
  • 不要附和，哪怕你部分认同：在下属面前认可对经理的批评，会双向破坏信任链。你会成为在团队中议论经理的人。
  • 也不要直接否定：“我理解你对这个决策感到不满”是诚实的回应。“我的经理没问题，只是你不理解”既不诚实又居高临下。
  • 引导至可行动的方向：“我无法解释该决策背后的原因，但我可以了解它对你工作的影响，看看是否能为你争取调整的可能。”
  • 若存在真实不满，需认真对待：在对话结束后，单独评估该诉求是否合理。若合理，通过正确渠道上报。
原则是：你可以批判性地看待经理的决策，但不能与下属一起抱怨经理。

Letting Someone Go When the Timing Is Terrible

员工处境艰难时的解雇处理

The engineer is a father of four. They just bought a house. Their spouse is dealing with a health issue. You know about it all.
There is no clean version of this. The decision about whether to let someone go should be made on whether they're in the right role — not on the circumstances of their personal life. If you make exceptions based on personal circumstances, you'll never be able to make this call, and the team and the individual both pay the price of the right decision being deferred indefinitely.
What you can do:
  • Be generous on the timeline where possible — a few extra weeks of notice, a longer formal transition period
  • Be generous on the severance or support you advocate for internally
  • Be honest in the conversation: name what isn't working clearly, and be humane in how you frame it
  • Be available after — a good reference, an introduction, a recommendation
What you shouldn't do:
  • Keep someone in a role they're not succeeding in because you feel guilty about their circumstances
  • Avoid the conversation indefinitely while both parties know what's coming
The hardest version of this job is making a decision you know is right while knowing it's going to hurt someone. That discomfort doesn't go away. Carrying it is part of the role.
这位工程师是四个孩子的父亲，刚买了房子，配偶正面临健康问题。这些情况你都了解。
没有完美的处理方式。是否解雇员工的决策应基于其是否适配岗位——而非个人处境。若因个人处境破例，你将永远无法做出这个决定，团队和员工都会为延迟正确决策付出代价。
你可以做的：
  • 尽可能给予更充裕的时间——额外几周的通知期、更长的正式过渡时间
  • 在内部争取更优厚的遣散费或支持
  • 沟通时保持坦诚：明确说明问题所在，同时以人性化的方式表达
  • 后续提供帮助——良好的推荐信、人脉介绍、推荐机会
你不应该做的：
  • 因愧疚而让员工留在无法胜任的岗位上
  • 无限期回避沟通，让双方都陷入等待的煎熬
这份工作最艰难的部分，就是做出明知正确却会伤害他人的决定。这种不适感不会消失，承受它是岗位职责的一部分。

Quitting as a Manager: The Guilt That Comes With It

经理离职：伴随的愧疚感处理

When a manager leaves a job, the guilt structure is different from when an individual contributor leaves.
You feel responsible for your team — people who trusted you, whose careers you influenced, some of whom joined because of you. Leaving feels like abandonment, especially if the team is mid-project, mid-difficulty, or in a period of instability.
Some honest realities:
  • You're not betraying them. Your team members would leave for better opportunities without feeling they were betraying you. You're allowed to do the same.
  • Your replacement will be fine. Teams don't collapse when good managers leave. Strong teams outlast managers.
  • The guilt is a signal of care, not obligation. Feeling it means you took the role seriously. Acting on it by staying in a role that's no longer right for you doesn't serve the team either.
What you owe them:
  • A thoughtful transition — no disappearing act, no pretending nothing is happening
  • Honest conversations with people who deserve to hear it from you directly
  • A strong handoff — documentation, context, introductions
What you don't owe them:
  • Staying indefinitely
  • A timeline that's dictated by guilt rather than what's best for your next chapter
经理离职时的愧疚感与普通员工离职不同。
你会对团队感到责任重大——那些信任你、职业生涯受你影响、甚至因你加入团队的人。离职感觉像是抛弃他们，尤其是当团队正处于项目中期、面临困难或不稳定时期。
一些真实的事实：
  • 你没有背叛他们：你的团队成员若有更好的机会也会离职，不会觉得是背叛你。你也有同样的权利。
  • 你的继任者会做得很好：优秀的团队不会因优秀经理的离开而崩溃，强大的团队能历经多任经理。
  • 愧疚是关心的信号，而非义务：感到愧疚说明你认真对待这份职责。但因愧疚而留在不适合自己的岗位上，对团队也没有好处。
你对团队的责任：
  • 周到的过渡安排——不要突然消失，不要假装一切正常
  • 与值得直接告知的人员进行坦诚沟通
  • 顺畅的交接——文档整理、信息传递、人脉介绍
你不必做的：
  • 无限期留任
  • 因愧疚而制定不符合自身职业规划的离职时间表

Handling Layoffs

裁员处理

Layoffs are logistically and emotionally hard. Some things that reduce the harm:
Why secrecy during planning is necessary — and painful. You can't communicate details you don't yet have. In the absence of specifics, people fill the void with fear. Premature disclosure creates ruptures that can be permanent. This secrecy is uncomfortable but it protects people from worse outcomes.
Be a fair witness to the difficulty. It feels arbitrary and unfair — because it often is. People who didn't contribute to the business problem lose their jobs because of it. That's genuinely hard, and feeling bad about it is appropriate. What's not appropriate is letting that feeling drive decisions about who stays and goes (see "Letting Someone Go When the Timing Is Terrible" above).
For the people being let go:
  • Be direct and clear. Tell them in person (or live video). Don't bury the message.
  • Give them what they need to understand what comes next: severance, benefits continuation, timeline, reference availability.
  • End the conversation cleanly. Prolonged attempts to process it together usually make it harder, not easier.
For the people who stay:
  • Acknowledge what happened. Don't act like nothing changed. People who survived a layoff are processing loss and uncertainty — they need honesty about what comes next more than reassurance that everything is fine.
  • Be honest about what you know and what you don't. "I don't know" is more credible than false certainty.
  • Give them space for the grief. Productivity will dip. That's normal.
For yourself:
  • You may be implementing a decision you didn't make and didn't want. That's a real burden. Find a peer or mentor to process it with — outside your team.
裁员在流程和情感层面都极具挑战性。以下方法可减少伤害：
规划阶段保密的必要性与痛苦：你无法传达尚未确定的细节。缺乏具体信息时，人们会用恐惧填补空白。过早披露会造成难以修复的裂痕。这种保密虽令人不适，但能避免更糟的结果。
坦然面对困难：裁员看似随意且不公——因为事实往往如此。未参与造成业务问题的人却因此失业，这确实令人痛苦，感到难过是正常的。但不应让这种情绪影响留任人员的选择（参见上文“员工处境艰难时的解雇处理”）。
针对离职人员：
  • 直接明确地告知。当面或通过实时视频沟通，不要含糊其辞。
  • 提供他们需要了解的后续信息：遣散费、福利延续、时间安排、推荐信提供方式。
  • 干净利落地结束对话。试图一起长时间消化情绪通常会让情况更糟，而非更好。
针对留任人员：
  • 承认已发生的事。不要假装一切没变。经历裁员的留任人员正在处理失落和不确定性——他们需要关于未来的诚实信息，而非“一切都会好起来”的安慰。
  • 坦诚说明自己知道和不知道的事。“我不知道”比虚假的确定更可信。
  • 给他们留出悲伤的空间。生产力会暂时下降，这是正常的。
针对你自己：
  • 你可能在执行一个自己并未参与制定、甚至不认同的决策。这是沉重的负担。找一位同行或导师倾诉——不要在团队内部。

Dive Deeper

深入了解

If the user asks where a framework came from, wants to read the original article, or wants more context on any topic in this skill — read 
references/sources.md
 for the full list of source articles (with links) and books.
若用户询问框架来源、想要阅读原文或了解本工具中任何主题的更多背景信息，请查阅
references/sources.md
获取完整的来源文章（含链接）和书籍列表。

Related Skills

相关工具

  • feedback
    — Most difficult situations require a direct feedback conversation first
  • performance-reviews
    — The formal letting-someone-go process lives here
  • managing-yourself
    — How to lead under pressure and absorb team fear during hard moments
  • 1on1s
    — The place where most of these situations first surface
  • feedback
    —— 大多数棘手场景都需要先进行直接反馈对话
  • performance-reviews
    —— 正式解雇流程请使用本工具
  • managing-yourself
    —— 如何在压力下领导团队，并在艰难时刻缓解团队焦虑
  • 1on1s
    —— 大多数此类场景最初都出现在一对一沟通中