difficult-workplace-conversations

0
0
Source

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

mkdir -p .claude/skills/difficult-workplace-conversations && curl -L -o skill.zip "https://mcp.directory/api/skills/download/5202" && unzip -o skill.zip -d .claude/skills/difficult-workplace-conversations && rm skill.zip

Installs to .claude/skills/difficult-workplace-conversations

About this skill

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

  1. Clarify the Issue

    • What specifically happened? (Observable facts only)
    • What is the impact? (On you, team, work)
    • What do you need to change?
  2. Check Your Emotions

    • What am I feeling? Why?
    • Am I calm enough to have this conversation?
    • What might trigger me during this conversation?
  3. 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?
  4. 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

  1. Open Neutrally

    • Start with facts, not judgments
    • Express intent to understand, not accuse
    • Create psychological safety
  2. Share Your Perspective

    • Describe behavior, not character
    • Focus on impact, not intention
    • Use "I" statements, not "you always"
  3. Listen Actively

    • Ask clarifying questions
    • Acknowledge their viewpoint
    • Look for shared interests
  4. Seek Resolution

    • Propose specific actions
    • Agree on next steps
    • Set check-in timeline

Phase 3: Followup (After)

Purpose: Ensure lasting resolution

  1. Document Agreements

    • What was agreed?
    • Who does what by when?
    • How will you measure success?
  2. Check Progress

    • Follow up as promised
    • Acknowledge improvements
    • Address continued issues promptly
  3. 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

scroll-experience

davila7

Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product pages, and award-winning web experiences. Makes websites feel like experiences, not just pages. Use when: scroll animation, parallax, scroll storytelling, interactive story, cinematic website.

6332

software-architecture

davila7

Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.

8125

senior-fullstack

davila7

Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architecture patterns, and complete tech stack guidance. Use when building new projects, analyzing code quality, implementing design patterns, or setting up development workflows.

8122

senior-security

davila7

Comprehensive security engineering skill for application security, penetration testing, security architecture, and compliance auditing. Includes security assessment tools, threat modeling, crypto implementation, and security automation. Use when designing security architecture, conducting penetration tests, implementing cryptography, or performing security audits.

6819

game-development

davila7

Game development orchestrator. Routes to platform-specific skills based on project needs.

5414

2d-games

davila7

2D game development principles. Sprites, tilemaps, physics, camera.

4812

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

643969

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

591705

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

318399

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

340397

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

452339

fastapi-templates

wshobson

Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.

304231

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.