Difficult Workplace Complete
Battle-tested skill for structured, approach, workplace, conflicts. Includes structured workflows, validation checks, and reusable patterns for enterprise communication.
Difficult Workplace Complete
A structured skill for navigating challenging workplace conversations ā covering conflict resolution, performance feedback delivery, sensitive topic discussions, negotiation preparation, and emotionally charged interactions with colleagues, managers, and reports.
When to Use This Skill
Choose Difficult Workplace Complete when you need to:
- Prepare for a challenging conversation with a colleague or manager
- Deliver negative performance feedback constructively
- Address interpersonal conflicts before they escalate
- Navigate salary or promotion negotiations
- Respond to hostile or passive-aggressive workplace behavior
Consider alternatives when:
- You need HR policy guidance (consult your HR department)
- You're dealing with workplace harassment or legal issues (consult legal counsel)
- You need team-building exercises (use a team management skill)
Quick Start
# Prepare for a difficult conversation claude "Help me prepare for a conversation with a team member who consistently misses deadlines but is defensive when given feedback. I want to address the pattern without damaging the relationship."
# Conversation Preparation: Deadline Accountability ## Opening (Set Context, Not Blame) "I'd like to talk about how we can work together to hit our sprint commitments more consistently. I value your contributions, and I want to make sure we're set up for success." ## Facts (Specific, Observable, Neutral) - Sprint 14: Auth module delivered 3 days late - Sprint 15: API docs missed deadline by 2 days - Sprint 16: Test suite delivered on time ā - Sprint 17: Dashboard feature 4 days late ## Impact Statement (Focus on Team/Project) "When deliverables come in late, it creates a cascade ā QA has to compress their timeline, and the release gets pushed. The team depends on reliable estimates." ## Explore Together (Not Prescribe) - "What's getting in the way of hitting these dates?" - "Are the estimates realistic, or are we underscoping?" - "What support would help you deliver on time?" ## Agree on Next Steps - Concrete commitment with measurable outcome - Check-in cadence (weekly 1:1 for first month) - Written summary shared after conversation
Core Concepts
Conversation Framework
| Phase | Goal | Technique |
|---|---|---|
| Opening | Set collaborative tone | "I'd like to discuss..." |
| Facts | Establish shared reality | Specific examples, no labels |
| Impact | Connect behavior to consequences | "When X happens, Y results" |
| Explore | Understand their perspective | Open questions, active listen |
| Agree | Commit to measurable next steps | Written summary, follow-up |
Managing Defensive Reactions
## When They Get Defensive ### Deflection: "Everyone misses deadlines" ā Redirect: "I hear you ā let's focus on what we can control on our team. What would help us specifically?" ### Counter-attack: "You're not giving me enough resources" ā Acknowledge and explore: "That could be a factor. Walk me through what resources would make the difference." ### Withdrawal: Goes silent, shuts down ā Pause and check in: "I can see this is tough. Should we take 10 minutes and come back to this?" ### Emotional escalation: Raises voice, gets upset ā Stay calm, validate: "I can tell this matters to you. That's actually a good sign ā let's channel that into finding a solution."
Feedback Models
## SBI Model (Situation-Behavior-Impact) - **Situation**: "In last Thursday's client call..." - **Behavior**: "...you interrupted the client three times while they were describing their requirements..." - **Impact**: "...which made them visibly frustrated, and they cut the meeting short." ## COIN Model (Context-Observation-Impact-Next) - **Context**: "During sprint planning meetings..." - **Observation**: "...I've noticed you check your phone frequently and miss action items assigned to you..." - **Impact**: "...which means items get dropped and others have to follow up." - **Next**: "Going forward, can we agree to close laptops and phones during the 30-minute planning sessions?"
Configuration
| Parameter | Description | Example |
|---|---|---|
scenario_type | Type of difficult conversation | "performance" / "conflict" |
relationship | Your relationship to the person | "peer" / "report" / "manager" |
tone | Desired tone of the conversation | "firm" / "empathetic" |
outcome_goal | What you want from the conversation | "behavior change" |
include_script | Generate a conversation script | true |
follow_up_plan | Include post-conversation plan | true |
Best Practices
-
Prepare with specific examples, never generalizations ā "You're always late" triggers defensiveness. "The auth module in Sprint 14 was 3 days late, and the dashboard in Sprint 17 was 4 days late" gives the person something concrete to respond to without feeling attacked.
-
Separate the person from the behavior ā Frame feedback around actions and outcomes, not character. "The report had 12 data errors" is actionable. "You're careless" is a character judgment that destroys trust and produces nothing useful.
-
Ask before telling ā Before offering your interpretation, ask for theirs: "What happened with the Sprint 17 delivery?" You may discover legitimate obstacles you weren't aware of. People accept solutions they helped create more readily than solutions imposed on them.
-
Document agreements immediately after the conversation ā Send a brief email within 24 hours: "Here's what we agreed to..." Memory is unreliable, and written documentation prevents "I never said that" disputes. It also shows you take the commitments seriously.
-
Follow up on commitments without micromanaging ā Schedule a check-in for the agreed date. If the person meets their commitment, acknowledge it explicitly. If they don't, address it promptly using the same framework. Consistency signals that accountability is real, not performative.
Common Issues
You avoid the conversation entirely ā The most common failure mode is procrastination. The conversation gets harder with every day you delay because resentment builds and patterns entrench. Schedule it within 48 hours of deciding it's needed, even if it's uncomfortable.
The conversation goes off-script and you lose control ā Prepare for 3-4 likely reactions (defensive, emotional, dismissive, counter-attacking) with specific responses for each. If the conversation completely derails, it's okay to say "Let's pause and pick this up tomorrow" rather than pushing through a counterproductive exchange.
Nothing changes after the conversation ā If you have the conversation but don't follow up on agreed actions, you've taught the person that accountability conversations have no teeth. Set calendar reminders for follow-up dates, and address missed commitments in the next 1:1 ā not three months later in a performance review.
Reviews
No reviews yet. Be the first to review this template!
Similar Templates
Full-Stack Code Reviewer
Comprehensive code review skill that checks for security vulnerabilities, performance issues, accessibility, and best practices across frontend and backend code.
Test Suite Generator
Generates comprehensive test suites with unit tests, integration tests, and edge cases. Supports Jest, Vitest, Pytest, and Go testing.
Pro Architecture Workspace
Battle-tested skill for architectural, decision, making, framework. Includes structured workflows, validation checks, and reusable patterns for development.