El Constructor de Guiones para Conversaciones Difíciles: Convierte una Situación Laboral Tensa en una Conversación que Realmente Puedes Tener
Por qué importa este prompt
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.
Para qué lo usamos
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
Resultado
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."
La mayoría de los consejos sobre conversaciones difíciles son lo suficientemente genéricos como para aplicarse a cualquier conflicto, lo que significa que no aplican útilmente a ninguno. «Usa frases con yo» y «supón buena intención» son ciertas pero vacías sin las palabras específicas para la situación específica.
Por qué la frase de apertura tiene su propio paso dedicado
Los primeros diez segundos de una conversación difícil típicamente determinan si la otra persona escucha o empieza a construir una defensa. El prompt prohíbe la palabra «pero», acusaciones, y listas de ejemplos en la apertura específicamente porque los tres son movimientos clásicos de construcción de caso.
Por qué la resistencia predicha debe ser realista, no un espantapájaros
Un modo de fallo común en la preparación de conversaciones es imaginar la objeción de la otra persona como obviamente equivocada. El requisito de que la resistencia sea «realista, no un espantapájaros» — incluyendo escenarios donde la otra persona tiene un punto justo — obliga al prompt a producir una respuesta que realmente se involucre con un contraargumento razonable.
Por qué el paso de cierre debe ser observable
Las conversaciones que terminan en un sentimiento («seamos ambos más conscientes en el futuro») son difíciles de seguir. Exigir que el paso de cierre sea algo que «o sucede o no sucede» le da a ambas personas algo concreto que notar en la próxima reunión.
Por qué la línea de respaldo importa incluso cuando la apertura funciona
Incluso una apertura bien diseñada no garantiza que la conversación se mantenga tranquila. Tener una línea de desescalada preescrita significa que no estás componiendo una recuperación en tiempo real.
Cómo adaptar esto para tu propia situación
El prompt funciona para conflictos entre pares y retroalimentación ascendente a un gerente tan bien como para la dirección de gerente a subordinado en el ejemplo.