Difficult Conversation Script Builder: Claude Prompt for Workplace Conflicts
Why this prompt matters
<p>Unaddressed workplace conflict costs more than you think. Research from CPP Inc. found that U.S. employees spend an average of 2.8 hours per week dealing with conflict — that's $359 billion in lost working hours annually. But the bigger cost is not the time: it's the relationships damaged when poorly handled conversations turn someone defensive, resentful, or disengaged.</p><p>Most people avoid these conversations until the situation has festered into something much harder to fix. And when they finally do have the conversation, they either over-prepare (over-rehearsed lines that feel robotic) or under-prepare (they improvise, get emotional, and say something they regret). This prompt gives you a third path: a structured, human-sounding script that keeps you on track even when the other person pushes back hard.</p><p>The script structure is built on conflict resolution research — specifically the model from <em>Crucial Conversations</em> (Grenny et al.) combined with Nonviolent Communication principles. The 'listening pause' section alone prevents the most common failure mode: people who feel unheard stop engaging with solutions.</p>
What we use it for
You have a conversation that needs to happen — but you keep postponing it. Maybe a team member keeps missing deadlines, a peer is undermining your work, or a manager gave you feedback you strongly disagree with. You know what you want to say but can't figure out how to say it without it going sideways.
Prompt
Act as a seasoned executive coach and organizational psychologist with 20+ years of experience guiding leaders through high-stakes workplace conversations. CONTEXT: I need to have a difficult conversation with [PERSON'S ROLE, e.g., "a direct report", "my manager", "a peer/colleague"] named [NAME OR LEAVE BLANK]. The issue is: [DESCRIBE THE SITUATION IN 2-3 SENTENCES, e.g., "They have been consistently missing project deadlines, and the last missed deadline caused us to lose a client. I've mentioned it informally before but nothing has changed."] The relationship dynamic: [DESCRIBE, e.g., "I manage this person directly", "We are peers but I depend on their output", "This is my manager and I need to escalate concerns upward"] My goal for this conversation: [e.g., "Reach a clear agreement on changed behavior with a measurable timeline", "Understand their perspective and decide together whether this role is still a fit", "Set a formal performance improvement process in motion"] Their likely emotional state or resistance: [e.g., "Defensive — they tend to deflect blame", "Anxious — they're going through personal difficulties", "Dismissive — they don't think this is a serious issue"] TASK: Design a complete, ready-to-use conversation script for this situation. The script must feel human, not robotic — I should be able to read these lines naturally. CONSTRAINTS: - Do not include corporate jargon or HR-speak (no "going forward", "circle back", "touch base") - The opening must not sound like an ambush — ease in with genuine intent - Avoid accusatory language; use observable facts, not character judgments - Include a moment where I actively listen and acknowledge their perspective before pushing forward - Do not skip to solutions before the other person has felt heard - If an agreement or commitment is reached, show me how to document it verbally during the conversation OUTPUT FORMAT: Return the script in these exact sections: **1. SETTING THE STAGE (Pre-conversation)** [2-3 bullet points on how to frame the meeting invite and set the right environment] **2. OPENING (First 60 seconds)** [Exact words to say. Warm, direct, and non-threatening.] **3. CORE MESSAGE** [Deliver the key issue with specific observable facts — no vague generalities] **4. THE LISTENING PAUSE** [Script for pausing, asking an open question, and genuinely processing what they say] **5. ANTICIPATED PUSHBACK — 3 SCENARIOS** For each likely response they might give, show: - What they might say - How to respond without getting defensive or capitulating **6. MOVING TO RESOLUTION** [How to propose next steps, get verbal commitment, and close the conversation constructively] **7. FOLLOW-UP** [One follow-up message to send within 24 hours that reinforces the agreement]
Result
<p><strong>Example scenario:</strong> Direct report (Jordan) has missed three consecutive deadlines, the last of which caused a client to reduce their contract renewal.</p><hr/><h3>1. SETTING THE STAGE</h3><ul><li>Book 45 minutes (not 30 — rushed conversations get cut short at the worst moment). Title the invite: <em>Check-in — project delivery and workload</em>. Do not call it a performance review in the invite or Jordan will show up in self-defense mode.</li><li>Find a private room or use video with cameras on. No open-plan seating. The conversation needs psychological safety on both sides.</li><li>Have specific dates and project names written down in front of you — not to wave them accusatorially, but so you speak with precision, not approximation.</li></ul><h3>2. OPENING</h3><p><em>"Jordan, I appreciate you making time. I want to talk about the last few project cycles because something is not working, and I want to understand what's going on from your side before we talk about what happens next. I'm not coming into this with a verdict — I'm coming in to figure this out together."</em></p><h3>3. CORE MESSAGE</h3><p><em>"In Q1, the data migration for the Henley account was due February 14th and delivered February 28th. The API integration for Storrow was due March 3rd and came in March 19th. And last week's deliverable for Cairns Group — that was due the 22nd, we got it on the 29th, and because of that delay they've reduced their renewal from 12 months to 6 months. That's a $47K impact to the team's number. I need us to address this directly."</em></p><h3>4. THE LISTENING PAUSE</h3><p><em>"Before I say anything else — I want to hear from you. What's your read on what's been happening?"</em></p><p>Then stop. Wait through the silence. Do not fill it. If they seem stuck, try: <em>"Is there something going on that I'm not aware of that's making this harder than it should be?"</em></p><h3>5. ANTICIPATED PUSHBACK — 3 SCENARIOS</h3><p><strong>Scenario A — They blame the process:</strong><br/><em>"The timelines are unrealistic. No one could hit those."</em><br/>Response: <em>"That's worth exploring. If the timelines are genuinely off, I need to know that, and we'll fix it. But the timelines were agreed to at kickoff with your sign-off — so the question I have is: when did you first know you couldn't hit the February date, and why didn't that surface earlier so we could adjust?"</em></p><p><strong>Scenario B — They go silent or emotional:</strong><br/>Response: <em>"Take a breath — I'm not going anywhere. This conversation matters to me because you matter to this team. I just need us to get to a real answer together."</em></p><p><strong>Scenario C — They say they didn't know it was a problem:</strong><br/><em>"I didn't realize it was such a big deal."</em><br/>Response: <em>"I hear that, and that's on me too — I should have been clearer earlier that late delivery has real consequences downstream. I'm being clear now."</em></p><h3>6. MOVING TO RESOLUTION</h3><p><em>"Here's what I want to leave this conversation with: a clear plan for the next two deliverables — specifically, I want you to flag me within 24 hours if you hit any blocker that might push a date. Not after the fact — during. Can we agree to that?"</em></p><p>If yes: <em>"Good. I'll send you a short follow-up note today with what we've agreed to, just so we both have a record. I want this to work — and I think it can."</em></p><h3>7. FOLLOW-UP MESSAGE (within 24 hours)</h3><p><em>Jordan — thanks for the honest conversation today. To summarize what we agreed: for the upcoming Hartley integration (due June 12) and the Mercer report (due June 18), you'll flag me by EOD if anything looks like it could push either date. I'll check in mid-project rather than waiting until deadline week. Let me know if anything is unclear. — [Your name]</em></p>
<p>Most workplace conversations go wrong not because of bad intent, but because of bad structure. People show up with the right message but no map — so they either bury the point under layers of softening, or they overcorrect and come out swinging. Either way, the other person ends up defensive, and the conversation achieves nothing.</p><h2>What This Prompt Does Differently</h2><p>The script this prompt generates is built on three principles from conflict resolution research. First: <strong>separation of facts from judgment</strong>. The core message section specifically forces you to name observable events (missed dates, business impact) rather than character assessments ("you're unreliable"). Second: <strong>the listening architecture</strong>. Most script templates skip straight from the problem to the solution. This one inserts a mandatory listening pause before resolution — because people who feel unheard cannot engage productively with next steps. Third: <strong>pre-scripted pushback responses</strong>. The three most common deflection patterns (blame the system, go silent, claim ignorance) each get a tailored response that doesn't capitulate or escalate.</p><h2>Why the Opening Line Matters So Much</h2><p>The opening 60 seconds determine whether the other person enters problem-solving mode or self-defense mode. The prompt instructs Claude to write an opening that signals genuine curiosity — <em>"I'm not coming in with a verdict"</em> — before stating any facts. This is not softening the message; it's creating the psychological safety needed for the conversation to actually produce a result. A person who feels cornered will not give you the real reason behind their behavior.</p><h2>What to Feed the Prompt</h2><p>The more specific your inputs, the better the script. Vague input like "my colleague is difficult" produces a generic output. Replace the bracketed fields with: the person's role, the specific observable incidents (with dates and numbers), what outcome you're actually trying to achieve, and your honest assessment of how they'll likely respond. Claude will tailor the pushback scenarios and resolution language accordingly.</p><h2>Works Best With</h2><p>Claude Sonnet 4.5 or Claude Opus 4 produce the most nuanced, tonally aware scripts. GPT-4o also handles this prompt well. The key is using a model with strong instruction-following and tone control — lighter models tend to produce scripts that feel generic or corporate. Run it once, then do one revision pass asking Claude to adjust any line that sounds unnatural for your voice.</p>