Escreva o roteiro de qualquer conversa difícil no trabalho antes de entrar
Why this prompt matters
A poorly delivered difficult conversation rarely just fails once — it tends to recur, and each repeat costs more. Gallup has tied disengaged, poorly-managed teams to roughly 18% lower productivity and significantly higher voluntary turnover; replacing a mid-level technical employee typically runs 50-200% of their annual salary in recruiting, onboarding, and lost-productivity costs. Beyond the direct cost, an avoided or mishandled confrontation lets the underlying behavior calcify — the blame-shifting in this scenario, left unaddressed, tends to spread to other team members within a quarter, and by the time it reaches HR it's a formal complaint rather than a coaching conversation. Managers who wing these conversations also disproportionately trigger the two worst outcomes: the employee feels blindsided (which reads as unfair and drives grievance, even litigation risk in termination scenarios) or the manager backs off mid-conversation and nothing changes at all.
What we use it for
You're a mid-level engineering manager and you have a 1:1 scheduled for tomorrow morning with a senior team member who has missed three consecutive sprint deadlines and has started publicly blaming other teams for the delays in front of the group. You've never had to confront someone senior about both a performance pattern and a trust-damaging behavior in the same conversation, and you're worried about either being too soft (letting the pattern continue) or too harsh (damaging a working relationship you still need).
Prompt
Act as an experienced workplace mediator and executive communication coach who has prepared hundreds of managers for high-stakes conversations, including layoffs, performance confrontations, and conflict resolution. Context: I need to have a difficult conversation at work. Here are the details: - Who I'm talking to: [THE PERSON YOU'RE TALKING TO — name/role] - My relationship to them: [YOUR RELATIONSHIP TO THEM — e.g., direct manager, peer, skip-level] - The situation: [THE SITUATION — describe what happened and what needs to be addressed] - What makes this sensitive: [ANYTHING THAT MAKES THIS SENSITIVE — e.g., prior history, emotional stakes, legal/HR considerations, power dynamics] - What outcome I want: [WHAT OUTCOME YOU WANT — the ideal result of this conversation] - When this is happening: [TIMING — e.g., tomorrow morning, end of this week] Task: Write a complete conversation script I can use to prepare for and guide this conversation in real time. Constraints: - Keep the tone honest and direct, never falsely soft or euphemistic — avoid corporate jargon that obscures the message. - The opening line must state the purpose within the first two sentences; do not bury the point. - Anticipate realistic pushback based on human psychology (defensiveness, denial, anger, bargaining), not generic objections. - Every prepared response must acknowledge the pushback before redirecting — no dismissiveness. - Keep the entire script deliverable in under 10 minutes of actual talk time. - Do not suggest recording the conversation or bringing in a witness unless the situation explicitly involves formal HR/legal process. Output Format: 1. **Opening Line** (1-3 sentences, exact wording to say first) 2. **Key Points** (3-5 bullet points, the core message in the order to deliver it) 3. **Anticipated Pushback & Responses** (2-4 pairs: the likely reaction, and exactly what to say back) 4. **Closing & Next Steps** (how to end the conversation and what happens after) 5. **One-Line Reminder** (a single sentence to keep in mind if the conversation goes off script)
Result
Scenario used for this example: You are a mid-level engineering manager. A senior developer on your team, Priya, has missed three consecutive sprint deadlines and has started publicly blaming other teams in stand-ups for the delays, which is damaging cross-team trust. You need to address the pattern directly, tomorrow morning, in a 1:1.
1. Opening Line
"Priya, I want to talk about the last three sprints and how we're communicating about delays with other teams — this isn't a performance review, it's a conversation I need to have now before it becomes a bigger problem."
2. Key Points
- The team has missed three consecutive sprint commitments, and the pattern is now visible to stakeholders outside the team.
- In the last two stand-ups, the delays were attributed to the platform team and the design team without first checking with them — that's created friction I've had to smooth over twice this week.
- I need to understand what's actually blocking delivery — whether it's scope, dependencies, or something else — so we can fix the root cause together.
- Going forward, any blocker involving another team gets raised to me first, so we can verify it and raise it jointly instead of attributing blame in a group setting.
- This is fixable, and I'm not looking to punish you for it — I need us to reset how we handle blockers as a team.
3. Anticipated Pushback & Responses
- Pushback: "The platform team really has been slow, I'm not wrong about that."
Response: "You might be right that they're a bottleneck — I'm not disputing the facts, I'm addressing how it was raised. Calling it out in stand-up in front of five other people isn't the way to solve it. Bring it to me and we'll escalate it properly." - Pushback: "It feels like I'm being singled out — other people miss deadlines too."
Response: "This isn't about singling you out, it's about a three-sprint pattern with your name on it and its effect on other teams. If I see the same pattern elsewhere, I'll have this same conversation there." - Pushback: (goes quiet, disengages)
Response: "I know this isn't a fun conversation to be in. Take a moment — I want to actually hear what's been getting in the way, because I'd rather solve it than keep having this talk."
4. Closing & Next Steps
"Let's agree on two things before you go: first, any inter-team blocker comes to me before it comes up in stand-up. Second, let's set a check-in this Friday to see where the current sprint stands. I'll send a two-line summary of what we agreed on right after this so we're both working from the same page."
5. One-Line Reminder
"Stay on the pattern and the impact, not on Priya's character — if the conversation drifts into 'you always' or 'you never,' pause and come back to specific sprints and specific stand-ups."
A maioria dos conselhos sobre conversas difíceis diz o que sentir — mantenha a calma, seja empático, ouça ativamente. Raramente diz o que realmente dizer quando a outra pessoa resiste, fica em silêncio ou se torna defensiva na sala. Este prompt preenche essa lacuna: em vez de conselhos genéricos, ele produz um roteiro palavra por palavra construído em torno da sua situação específica.
Por que este prompt é estruturado dessa forma
O prompt começa apresentando a IA como mediadora e coach executiva, em vez de um assistente genérico. Esse enquadramento importa — empurra o modelo em direção a uma linguagem direta e testada em campo, em vez do tom suavizado e cauteloso que um assistente de propósito geral usa por padrão quando um tópico parece sensível.
O bloco de contexto pede cinco entradas específicas: com quem você está falando, seu relacionamento com a pessoa, a situação, o que a torna sensível e o resultado desejado. Cada uma dessas altera o roteiro materialmente. Uma conversa com um par precisa de um enquadramento diferente do que com um subordinado direto ou um superior hierárquico, e "o que a torna sensível" permite que o modelo considere o histórico — conflitos anteriores, considerações de classes protegidas ou volatilidade emocional — que um template genérico perderia completamente.
A seção de restrições faz o verdadeiro trabalho de controle de qualidade. Exigir que a frase de abertura declare o propósito em duas frases previne o modo de falha mais comum em conversas difíceis: enterrar o ponto principal sob cinco minutos de conversa fiada, o que faz a virada eventual parecer uma emboscada. Exigir que cada resposta preparada reconheça a objeção antes de redirecionar impede que o roteiro produza respostas que soem desdenhosas ou ensaiadas quando a outra pessoa reage emocionalmente — o que, em uma conversa difícil real, geralmente acontece.
O formato de saída em cinco partes reflete como essas conversas realmente se desenrolam em tempo real: uma abertura que você diz textualmente, pontos principais na ordem que evita que a conversa descarrile, respostas preparadas para as duas ou três reações que você pode realmente prever, um fechamento que fixa os próximos passos em vez de se dissipar, e um lembrete de uma linha para se recolocar nos trilhos se as coisas saírem do curso — porque roteiros raramente sobrevivem intactos ao contato com uma sala emocional.
Onde este prompt mostra seu valor
Isso não se limita a demissões ou rescisões. Funciona para os casos mais comuns e igualmente desconfortáveis: dizer a um colega que seu comportamento em reuniões está prejudicando você, dar a um funcionário antigo um feedback direto de que suas habilidades não acompanharam o cargo, lidar com um conflito entre dois membros da equipe que se reportam a você, ou contestar um cliente que continua mudando o escopo sem ajustar o orçamento. O padrão — dizer cedo, esperar objeção específica, responder sem ser desdenhoso, fechar com passos concretos — se aplica a todos eles.
Execute-o na noite anterior, não cinco minutos antes. O valor não é apenas o roteiro em si; é que escrever as objeções antecipadas força você a pensar no momento mais difícil da conversa antes de estar parado nele.