Difficult Situations

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.

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

---

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.

---

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.

---

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.

---