ابزار ساخت اسکریپت گفتگوهای سخت: پرامپت Claude برای اختلافات محیط کار
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
Example scenario: Direct report (Jordan) has missed three consecutive deadlines, the last of which caused a client to reduce their contract renewal.
1. SETTING THE STAGE
- Book 45 minutes (not 30 — rushed conversations get cut short at the worst moment). Title the invite: Check-in — project delivery and workload. Do not call it a performance review in the invite or Jordan will show up in self-defense mode.
- Find a private room or use video with cameras on. No open-plan seating. The conversation needs psychological safety on both sides.
- 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.
2. OPENING
"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."
3. CORE MESSAGE
"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."
4. THE LISTENING PAUSE
"Before I say anything else — I want to hear from you. What's your read on what's been happening?"
Then stop. Wait through the silence. Do not fill it. If they seem stuck, try: "Is there something going on that I'm not aware of that's making this harder than it should be?"
5. ANTICIPATED PUSHBACK — 3 SCENARIOS
Scenario A — They blame the process:
"The timelines are unrealistic. No one could hit those."
Response: "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?"
Scenario B — They go silent or emotional:
Response: "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."
Scenario C — They say they didn't know it was a problem:
"I didn't realize it was such a big deal."
Response: "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."
6. MOVING TO RESOLUTION
"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?"
If yes: "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."
7. FOLLOW-UP MESSAGE (within 24 hours)
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]
بیشتر مکالمات محیط کار نه به خاطر نیت بد، بلکه به خاطر ساختار بد به مشکل میخورند. افراد با پیام درست اما بدون نقشه حاضر میشوند – یا پیام را زیر لایههای نرمکننده دفن میکنند، یا جبران میکنند و حمله میکنند. در هر دو صورت، طرف مقابل حالت تدافعی میگیرد و گفتگو بینتیجه میماند.
این پرامپت چه تفاوتی دارد
اسکریپتی که این پرامپت تولید میکند بر سه اصل از تحقیقات حل اختلاف بنا شده. اول: جداسازی حقایق از قضاوت. بخش پیام اصلی شما را مجبور میکند رویدادهای قابل مشاهده (تاریخهای از دست رفته، تأثیر تجاری) را نام ببرید نه ارزیابی شخصیتی («شما غیرقابل اعتماد هستید»). دوم: معماری گوش دادن. بیشتر قالبهای اسکریپت مستقیماً از مشکل به راه حل میپرند. این یکی قبل از حل مسئله یک مکث اجباری برای گوش دادن قرار میدهد – چون افرادی که احساس نمیشوند نمیتوانند با مراحل بعدی به طور مؤثر درگیر شوند. سوم: پاسخهای از پیش نوشته شده به واکنشها. سه الگوی متداول انحرافی (مقصر دانستن سیستم، سکوت کردن، ادعای ناآگاهی) هر کدام یک پاسخ سفارشی دارند که نه تسلیم میشود و نه تشدید میکند.
چرا جمله شروع اینقدر مهم است
شصت ثانیه اول تعیین میکند طرف مقابل وارد حالت حل مسئله میشود یا حالت دفاع شخصی. پرامپت به Claude دستور میدهد شروعی بنویسد که کنجکاوی واقعی را نشان دهد – «نمیخواهم حکم بدهم» – قبل از بیان هر حقیقتی. این نرم کردن پیام نیست؛ ایجاد امنیت روانی لازم برای این است که گفتگو نتیجه بدهد. کسی که احساس کند در گوشه گیر کرده، دلیل واقعی رفتارش را به شما نخواهد گفت.
چه چیزی به پرامپت بدهید
هر چه ورودیهای شما دقیقتر باشد، اسکریپت بهتر میشود. ورودی مبهم مثل «همکارم سخت است» خروجی کلی تولید میکند. فیلدهای داخل براکت را جایگزین کنید: نقش فرد، رویدادهای قابل مشاهده خاص (با تاریخ و اعداد)، نتیجهای که واقعاً میخواهید به آن برسید، و ارزیابی صادقانه شما از واکنش احتمالی طرف مقابل. Claude سناریوهای واکنش و زبان حل مسئله را متناسب تنظیم میکند.
با چه مدلهایی بهتر کار میکند
Claude Sonnet 4.5 یا Claude Opus 4 دقیقترین و آگاهترین اسکریپتها را از نظر لحن تولید میکنند. GPT-4o هم این پرامپت را خوب اجرا میکند. نکته اصلی استفاده از مدلی با قدرت پیروی از دستورات و کنترل لحن است – مدلهای سبکتر معمولاً اسکریپتهای کلی و شرکتی میسازند. یک بار اجرا کنید، سپس یک بار بازبینی بخواهید و از Claude بخواهید هر جملهای که برای صدای شما غیرطبیعی به نظر میرسد را تنظیم کند.