Der Schwierige-Gespräche-Skript-Builder: Verwandeln Sie eine angespannte Arbeitssituation in ein Gespräch, das Sie tatsächlich führen können
Warum dieser Prompt wichtig ist
Difficult conversations that get avoided don't stay small — they compound into resignations, formal complaints, or a public blowup in a meeting, at which point the manager loses the ability to handle it privately and constructively; the cost of the conversation doesn't go away by delaying it, it just moves from an uncomfortable fifteen minutes now to a much larger problem later.
Wofür wir ihn verwenden
A manager needs to address a high-performing but sarcastic team member whose comments have visibly shut down a colleague, ahead of a 1:1 tomorrow, without triggering defensiveness that derails the conversation or escalating to a formal HR complaint.
Prompt
Act as an experienced workplace mediator who specializes in conversations that are necessary but easy to keep avoiding — performance concerns, boundary issues, conflicts between colleagues, and feedback the other person doesn't expect. Context: Here is the situation: [DESCRIBE WHAT HAPPENED, BE SPECIFIC — e.g., "my direct report has made three sarcastic comments about a colleague's ideas in the last two team meetings, and I've noticed the colleague has gone quiet in meetings since"]. My relationship to this person: [YOUR ROLE RELATIVE TO THEM, e.g., "their manager," "a peer," "someone who reports to them"]. What I want as the outcome: [DESIRED OUTCOME, e.g., "the behavior stops and the relationship with their colleague can recover, without this becoming a formal HR matter"]. Relevant constraints: [CONSTRAINTS, e.g., "this is our first conversation about it," "a previous similar conversation with someone else on the team went badly," "this needs to happen over video call, not in person"]. Task: Write an opening line that states the issue without being read as an attack in the first ten seconds — this is the line most likely to determine whether the rest of the conversation is productive or defensive. Then identify the 2-3 key points that need to be raised, and for each one, predict the most likely pushback or defensive reaction and write a specific response to it. Write one fallback line to use if the conversation becomes emotional or derails despite the opening. Close with a next step that is concrete enough that both people would recognize if it happened or didn't. Constraints: - Do not write generic conflict-resolution phrases like "I hear you" or "let's find common ground" without specific content attached to them — every line must reference the actual situation described above. - The opening line must not contain the word "but," an accusation, or a list of examples — those all read as building a case rather than opening a conversation. - Predicted pushback must be realistic, not a strawman — write the response the other person would actually plausibly give, including if it's a reasonable point. - The closing next step must be observable (something that either happens or doesn't) rather than a feeling or intention. Output Format: 1. Opening line (one sentence, exact wording) 2. Key points, each with: the point to raise, likely pushback, and your response (2-3 points) 3. Fallback line for if the conversation escalates or the person becomes defensive 4. Closing line with a concrete next step
Ergebnis
Situation provided: A manager's direct report has made three sarcastic comments dismissing a colleague's ideas in the last two team meetings. The colleague has gone quiet in meetings since. This is the first conversation about it. Manager wants the behavior to stop and the working relationship to recover without escalating to HR.
1. Opening line:
"I want to check in about something I've noticed in our last two team meetings — how are you feeling about how those went?"
Why this works: It opens with observation and curiosity, not accusation. Asking how they experienced the meetings gives them room to self-report before being told what you noticed, which usually produces a more honest conversation than leading with the complaint.
2. Key points:
Point 1: "In the last two meetings, when [colleague] shared ideas, your response came across as dismissive to me and, I think, to them — comments like [specific example]."
Likely pushback: "I was just being direct, I didn't mean anything by it, and honestly I think their idea wasn't that strong."
Response: "You might be right that the idea had issues — that's a separate conversation we can have. What I want to focus on is the delivery, because [colleague] has gotten noticeably quieter in meetings since, and I don't want us to lose their input."
Point 2: "I need the team meetings to be a place where people feel safe raising half-formed ideas, even ones that don't hold up — that's actually how we get to the good ones."
Likely pushback: "So I'm not allowed to disagree with anyone anymore?"
Response: "Disagreeing is fine and useful — I want more of it, actually. The difference is disagreeing with the idea versus making the person feel dismissed for raising it. Those can look similar but land very differently."
3. Fallback line (if they become defensive or the conversation escalates):
"I can tell this doesn't feel great to hear, and that's fair — I'm not trying to make this bigger than it is. Can we take a breath and come back to what would actually change going forward?"
4. Closing line with concrete next step:
"Here's what I'd like to see: in our next team meeting, when someone raises an idea, ask one clarifying question before responding with a critique — for anyone's idea, not just [colleague]'s. I'll check in with you after that meeting to see how it felt."
Die meisten Ratschläge zu schwierigen Gesprächen sind generisch genug, um auf jeden Konflikt zuzutreffen, was bedeutet, dass sie auf keinen davon sinnvoll anwendbar sind. «Verwenden Sie Ich-Aussagen» und «gehen Sie von positiver Absicht aus» sind wahr, aber leer ohne die spezifischen Worte für die spezifische Situation.
Warum der Eröffnungssatz einen eigenen dedizierten Schritt bekommt
Die ersten zehn Sekunden eines schwierigen Gesprächs bestimmen typischerweise, ob die andere Person zuhört oder eine Verteidigung aufbaut. Der Prompt verbietet das Wort «aber», Anschuldigungen und Beispiellisten in der Eröffnung speziell deshalb, weil alle drei klassische Fallaufbau-Bewegungen sind.
Warum vorhergesagter Widerstand realistisch sein muss, kein Strohmann
Ein häufiger Fehlermodus bei der Gesprächsvorbereitung besteht darin, sich den Einwand der anderen Person als offensichtlich falsch vorzustellen. Die Anforderung, dass der Widerstand «realistisch, kein Strohmann» sein muss, zwingt den Prompt, eine Antwort zu erstellen, die sich tatsächlich mit einem vernünftigen Gegenargument auseinandersetzt.
Warum der Abschlussschritt beobachtbar sein muss
Gespräche, die mit einem Gefühl enden («lasst uns beide zukünftig achtsamer sein»), sind schwer nachzuverfolgen. Die Anforderung, dass der Abschlussschritt etwas sein muss, das «entweder passiert oder nicht passiert», gibt beiden Personen etwas Konkretes, das sie beim nächsten Meeting bemerken können.
Warum die Rückfalllinie wichtig ist, selbst wenn die Eröffnung funktioniert
Selbst eine gut gestaltete Eröffnung garantiert nicht, dass das Gespräch ruhig bleibt. Eine vorgeschriebene Deeskalationslinie zu haben bedeutet, dass Sie keine Erholung in Echtzeit komponieren.
Wie Sie dies für Ihre eigene Situation anpassen
Der Prompt funktioniert für Kollegenkonflikte und Aufwärts-Feedback an einen Manager genauso gut wie für die Manager-zu-Mitarbeiter-Richtung im Beispiel.