Claude Code SkillEnterprise Communication8 installs

Difficult Workplace Conversations

Structured approach to workplace conflicts, performance discussions, and challenging feedback using preparation-delivery-followup framework. Use when preparing for tough conversations, addressing conflicts, giving critical feedback, or navigating sensitive workplace discussions.

Install with the Claude Code Templates CLI
$ npx claude-code-templates@latest --skill="enterprise-communication/difficult-workplace-conversations" --yes

Requires Claude Code. The command adds this skill to your project's .claudedirectory — nothing runs on ToolZip's servers.

What's inside this skill

Component source

Difficult Conversations Skill

A structured framework for approaching challenging workplace conversations including conflicts, performance issues, sensitive feedback, and emotionally charged discussions.

When to Use This Skill

  • Preparing for a challenging conversation with a colleague
  • Addressing performance issues with a team member
  • Delivering difficult feedback to a peer or manager
  • Navigating conflict between team members
  • Discussing sensitive topics (salary, promotion, termination)
  • Handling emotional or defensive reactions
  • Following up after difficult discussions

Core Framework: Preparation-Delivery-Followup

Difficult conversations succeed or fail based on three phases:

Phase 1: Preparation (Before)

Purpose: Set yourself up for a productive conversation
  • Clarify the Issue
- What specifically happened? (Observable facts only)

- What is the impact? (On you, team, work)

- What do you need to change?

  • Check Your Emotions
- What am I feeling? Why?

- Am I calm enough to have this conversation?

- What might trigger me during this conversation?

  • Consider Their Perspective
- How might they see this situation?

- What constraints or pressures might they have?

- What do they care about that I can acknowledge?

  • Define Your Goal
- What outcome do I want?

- What is the minimum acceptable result?

- What am I willing to compromise on?

Phase 2: Delivery (During)

Purpose: Have the conversation effectively
  • Open Neutrally
- Start with facts, not judgments

- Express intent to understand, not accuse

- Create psychological safety

  • Share Your Perspective
- Describe behavior, not character

- Focus on impact, not intention

- Use "I" statements, not "you always"

  • Listen Actively
- Ask clarifying questions

- Acknowledge their viewpoint

- Look for shared interests

  • Seek Resolution
- Propose specific actions

- Agree on next steps

- Set check-in timeline

Phase 3: Followup (After)

Purpose: Ensure lasting resolution
  • Document Agreements
- What was agreed?

- Who does what by when?

- How will you measure success?

  • Check Progress
- Follow up as promised

- Acknowledge improvements

- Address continued issues promptly

  • Maintain Relationship
- Separate issue from person

- Rebuild trust over time

- Watch for regression

Key Principles

Separate Impact from Intent

What happened: Observable behavior What I felt: Your emotional response What I assume: Their intention (often wrong)

Focus conversation on behavior and impact, not assumed intentions.

The SBI Model

Situation: When and where did this happen? Behavior: What specifically did they do/say? Impact: What was the effect on you, the team, or the work?

Managing Emotions

If You FeelBefore Acting
AngryWait 24 hours, write but don't send
HurtTalk to neutral party first
AnxiousPractice the conversation
DefensiveIdentify your contribution

When to Escalate

Escalate when:

  • Safety is at risk
  • Legal issues involved
  • Repeated conversations haven't worked
  • Power dynamics prevent resolution
  • You need documentation

Conversation Types

Performance Feedback

  • Lead with specific examples
  • Connect to expectations/standards
  • Focus on future improvement
  • Offer support and resources

Conflict Resolution

  • Hear both sides separately first
  • Identify underlying interests
  • Look for win-win solutions
  • Document agreements

Sensitive Topics

  • Choose private, neutral setting
  • Allow time for processing
  • Be direct but compassionate
  • Respect confidentiality

Receiving Feedback

  • Thank them for feedback
  • Ask clarifying questions
  • Don't defend immediately
  • Reflect before responding

References (Load When Needed)

Detailed Frameworks

See Also

  • feedback-mastery skill - SBI feedback model (overlaps but more feedback-focused)
  • professional-effective-communication skill - General communication patterns

Example Scenarios

Scenario 1: Addressing Missed Deadlines

**Issue:** Team member missed 3 deadlines in past month
**Impact:** Project delayed, others blocked
**Goal:** Understand root cause, agree on prevention plan

**Opening:** "I wanted to check in about the recent deliverables. I've noticed
the last three have come in past deadline, and I'd like to understand what's
happening and how we can address it together."

Scenario 2: Peer Conflict

**Issue:** Colleague publicly criticized your work in meeting
**Impact:** Embarrassed, trust damaged
**Goal:** Address behavior, rebuild working relationship

**Opening:** "I'd like to talk about what happened in yesterday's standup.
When you said my code 'missed obvious issues,' I felt called out in front
of the team. I'd like to understand your concerns and find a better way
to handle code quality feedback."

Scenario 3: Asking Manager for Raise

**Issue:** Feel underpaid relative to market/contribution
**Impact:** Demotivation, considering leaving
**Goal:** Discuss compensation, get timeline or adjustment

**Opening:** "I'd like to discuss my compensation. I've been here two years,
taken on the payments project leadership, and want to make sure my salary
reflects my contributions and the current market."

Anti-Patterns to Avoid

In Preparation

  • Scripting every word - You'll sound robotic; prepare themes, not scripts
  • Building a case - This isn't a trial; seek understanding, not winning
  • Waiting too long - Issues compound; address promptly

In Delivery

  • Starting with "You always..." - Triggers defensiveness immediately
  • Burying the lead - Get to the point; don't soften excessively
  • Asking leading questions - "Don't you think..." isn't asking

In Followup

  • Forgetting to check in - Without follow-up, nothing changes
  • Holding grudges - Issue resolved means relationship continues
  • Over-documenting - Not everything needs written record

Success Metrics

A successful difficult conversation:

  • Both parties feel heard
  • Specific actions are agreed
  • Relationship is preserved or improved
  • The issue doesn't recur (or has clear escalation)
  • Neither party is blindsided later
Type
Skill
Category
Enterprise Communication
Installs
8
Source
GitHub ↗

Related Claude Code Skills

SkillEnterprise Communication

Excel Analysis

Analyze Excel spreadsheets, create pivot tables, generate charts, and perform data analysis. Use when analyzing Excel files, spreadsheets, tabular data, or .xlsx files.

287 installsView →
SkillEnterprise Communication

Email Composer

Draft professional emails for various contexts including business, technical, and customer communication. Use when the user needs help writing emails or composing professional messages.

148 installsView →
SkillEnterprise Communication

Brand Guidelines

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

96 installsView →
SkillEnterprise Communication

Telegram Bot Builder

"Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot."

42 installsView →
SkillEnterprise Communication

Internal Comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

39 installsView →
SkillEnterprise Communication

Data Privacy Compliance

Data privacy and regulatory compliance specialist for GDPR, CCPA, HIPAA, and international data protection laws. Use when implementing privacy controls, conducting data protection impact assessments, ensuring regulatory compliance, or managing data subject rights. Expert in consent management, data minimization, and privacy-by-design principles.

27 installsView →

Catalog data and component content are sourced from the open-source davila7/claude-code-templates project (MIT license). ToolZip curates the listing and writes original descriptions; every component links back to its original source. Claude Code is a product of Anthropic. ToolZip is an independent catalog and is not affiliated with or endorsed by Anthropic.