Verke Editorial

The hard conversation you keep avoiding: a script, and how to rehearse it

Verke Editorial · September 14, 2026

You know which one it is. It has been on the list since a Monday three weeks ago, and every week it slides a little further down. You have the opening line — you have had it for days, you have said it in the shower — and then Thursday comes, the 1:1 is fifteen minutes short, and it seems kinder, or wiser, or simply easier to leave it one more week.

Meanwhile the thing keeps happening. The report whose work has slipped keeps slipping. The deadline you should have pushed back on is now your deadline. The colleague who talks over you in meetings has done it four more times, and each time it gets a little harder to say anything, because now you would also have to explain why you said nothing before.

This article is about getting that conversation out of your head and into a room. It gives you a four-part script that works for most workplace conversations, a ladder for the replies you are dreading, and — the part most advice skips — a way to rehearse it until the words come out the way you mean them. It is written for managers and for people who have never managed anyone, because the conversation you avoid with your boss follows the same shape as the one you avoid with your report.

The pattern

Avoiding the conversation is not a pause. It is a decision.

Mikkel, Verke's executive coach, puts it in one line: the conversation you're avoiding becomes the decision you make by default. Not having the performance conversation is deciding that the current performance is acceptable. Not pushing back on the deadline is deciding to hit it. Not telling your peer that the interruptions bother you is deciding that they may continue. You do not experience these as decisions, because nothing was said. But the organization runs on what was not said just as much as on what was.

The avoidance also has a cost curve, and it bends the wrong way. In week one the conversation is about one thing. By week four it is about the thing, plus the three more times it happened, plus the question of why you waited. The other person can feel the weight of the delay even if they cannot name it, which is why a late conversation lands harder than an early one would have — and why people conclude, wrongly, that they were right to be afraid of it.

None of this means you should have blurted it out on day one. It means the useful question is not "when will this feel safe enough" but "what do I need to walk in with". The answer is shorter than you think: an outcome, an opening, and an ask. The rest is rehearsal.

The goal

Decide what Friday morning looks like

The most common mistake is to set "say the hard thing" as the goal. It is not a goal; it is a dare. If you go in to say the hard thing, you will say it, feel the relief of having said it, and leave the room with nothing changed — because the other person heard a complaint and you never told them what you wanted instead.

So before the script, one sentence: if this conversation goes well, what is different by Friday morning? Not "he understands" — something you could observe. "He has agreed to two specific changes for this sprint and we have a date to check." "The deadline has moved a week, or the scope has lost a feature, and my manager chose which." "She knows it bothers me and has said what she will do about it."

Write that sentence down. Everything in the conversation is now in service of it, which means you can drop anything that is not — the history, the pattern speech, the list of everything that has ever bothered you. A conversation with one clear outcome is short, and short is survivable.

The script

Four parts, in this order

Most hard conversations at work fit one shape. You describe one concrete thing, you say what it did, you ask for something specific, and then you hand over the turn with a real question. Each part has a job, and each is usually done badly in a predictable way.

The observation. One or two things that happened, recent and specific enough that a camera would have recorded them. "The last two releases went out with bugs that the tests would have caught" is an observation. "You've been sloppy lately" is a verdict, and verdicts get argued with. If you cannot name a concrete instance, you are not ready; go and find one.
The impact. What that did — to the team, the customer, the plan, or you. Kept short and factual: "Two people spent Friday on hotfixes, and I had to tell the client we had missed something." This is the part people either skip (so the observation sounds petty) or inflate into a speech (so it sounds like an indictment). One sentence.
The ask. What you want to be different, stated as something they could actually do. "I want you to run the full suite before every release, and I want us to look at the next two together." Not "I need you to care more." If your ask is a feeling, translate it into a behavior before you walk in.
The question. A genuine one, that hands them the turn: "What's your read on it?" "What am I not seeing?" "What would make that hard?" This is the line that turns a delivery into a conversation, and it is the line most people forget, because by this point they want to be finished. Ask it, and then stop talking.

The whole thing, said aloud, takes under a minute. If your opening takes longer, you are including things that belong to a different conversation.

Filled in: the report whose work has slipped

"I want to talk about the last two releases. Both went out with bugs the test suite would have caught, and both times someone else spent a day on the hotfix while I explained it to the client. That's not where your work usually is, and it's the reason I asked for this. What I want is the full suite run before anything ships, and for the two of us to review the next two releases together before they go. What's going on from where you sit?"

Notice what is not in it: no "lately", no "I've noticed a pattern", no "I'm worried about you", no reference to how long you waited to say it. Notice also that the last line is a question you do not know the answer to. Maybe the suite takes forty minutes and nobody has time. Maybe something is happening at home. The question is where the conversation actually starts.

The ladder

What you say when they say the thing you are afraid of

Nobody avoids the opening. People avoid the reply. Somewhere in your head there is a version of the other person who gets defensive, or cold, or upset, and your script ends the moment theirs begins. So map the replies before you walk in. Mikkel calls this the escalation ladder: for each rung, one sentence you can say that keeps the conversation on the outcome. There are only five rungs, and the same five come up in almost every conversation.

They get defensive

"That's not fair, you know how much I've had on." Do not argue the fairness. Agree with the true part and return to the ask: "You've had a lot on, and I know it. I'm still asking for the suite to run before every release. Can we make that work?" Defensiveness is usually a request to be seen; one sentence of seeing costs nothing and lets you move on.

They deny it

"That's not what happened." This is why the observation has to be camera-grade. Do not escalate to the pattern; stay on the instance. "Okay — walk me through Tuesday's release, then. Was the suite run?" If you were wrong, you find out now, cheaply. If you were right, the denial collapses on the detail and you can go back to the ask without anyone having to lose.

They get upset

Tears, or the shaking silence that comes before them. The instinct is to retract everything. Don't. Slow down, drop the volume, and keep the ask: "Take a minute. I'm not going anywhere, and this isn't a verdict on you — it's two releases and something I need to change." Offer to pause and pick it up tomorrow if they want; do not offer to pretend it was never raised.

They counter-attack

"Well, you changed the requirements twice that week." Sometimes this is true, and if it is, it deserves its own conversation — later. Name it and park it: "That might be fair, and I want to hear it properly. Can we take that separately? Right now I want to land the release question." The counter-attack wants you to defend yourself. Refusing to, while agreeing to hear it, is the strongest position in the room.

They go silent

"Fine." "Okay." Nothing. Silence feels like agreement and is usually the opposite. Do not fill it. Ask a smaller question than the one you asked: "Is there something about the ask that doesn't work?" If it stays silent, set a time: "Think about it. Let's talk again Thursday, and I'd like your view then." A closed-down person needs a door, not a push.

You will notice every rung ends the same way: back to the ask, or a date to come back to it. That is the whole technique. You are not trying to win the exchange; you are trying to keep it attached to the outcome you wrote down. If you also struggle to raise things at all — not this one conversation, but any of them — our article on being scared to speak up at work starts further back, with the smaller moments.

Got the opening line but not the conversation? Mikkel plays the other side and gives you the reply you are dreading, until it stops being the one you dread.

No signup, no HR ticket. Talk it through by voice or text; Mikkel plays your colleague, your manager or your report, and does not go easy on you.

Rehearse it with Mikkel →

Rehearsal

How to rehearse it so the words survive contact

A script on paper is not a conversation. The reason the opening line you have been carrying around never gets used is that it has only ever existed in your head, where the other person is either silent or perfectly reasonable. Rehearsal is what moves it into your mouth, and then into a room with someone in it who does not cooperate. Three passes, in order.

Pass one: write it, all four parts

Observation, impact, ask, question — on paper, in the words you would actually say. Then cut it until the whole thing is under a minute. Most first drafts are three times too long, because the writer is trying to make the case airtight. It does not need to be airtight. It needs to be clear and short enough that the other person can respond to it.

Pass two: say it out loud, alone

This feels absurd and is the step people skip. Stand up, say it to the wall, at conversation volume. You will discover that a sentence that read fine is unsayable, that your voice does something odd on the ask, that you speed up in the middle. Fix those on the page and say it again. Three times is usually enough for the words to stop being a performance.

Pass three: someone plays the other side, and does not go easy

This is the pass that changes the outcome. Brief someone on who the other person is and how they tend to react, and have them reply as that person — defensive first, then the denial, then whichever rung you are actually afraid of. Your job is to say your opening and then answer each rung with the sentence you prepared, until it comes out steady. The first time, it won't. The third time, it will, and you will notice that the fear has moved from the conversation to the calendar, which is where it belongs.

The problem with pass three is casting. A friend is too kind. A partner has views about your workplace. A colleague may be part of it. This is what Mikkel is built for: tell him who the other person is, and he plays them — by voice, like a phone call, for up to twenty minutes at a time, or in text if you are somewhere you cannot talk. He will give you the counter-attack you are dreading. He will also tell you, warmly, when your ask is not actually an ask, or when your observation is a verdict in disguise. And because he remembers the situation across weeks, the follow-up you need next month picks up where this one leaves off.

Three versions

The same shape, three directions

The script above was written downward, to a report. It works upward and sideways with small changes, and the changes are mostly about the ask.

Upward: telling your manager no to a deadline

The observation is the arithmetic, not your stress: "The estimate for the March scope is nine weeks and we have six." The impact is what breaks: "At six weeks we ship without the reporting piece, or we ship with it untested." The ask, going upward, is a choice rather than an instruction: "I need you to pick: move the date, cut reporting, or add a person. I'd recommend cutting reporting." The question: "Which of those can you live with?" You are not refusing. You are declining to make the trade-off silently on their behalf, which is what "yes" would have been. If you keep saying yes because the alternative feels like letting people down, our article on the weekly triage for when you are overloaded is the structural fix underneath this conversation.

Sideways: feedback a peer did not ask for

The hardest direction, because you have no authority and they have no obligation. So ask permission first, and mean it: "Can I tell you something I noticed in the planning meeting? You can tell me to mind my own business." Then the four parts, with the impact framed as yours: "You cut in on Priya twice while she was presenting the numbers. I found it hard to follow, and I think she lost the room. I'd ask you to let her finish next time. Did you notice it?" Keep it to one instance. A peer will accept one observation from a colleague; a pattern from a colleague sounds like a performance review from someone who is not their manager.

Downward, when they are well-liked and senior

The example in the script section, with one addition. Senior people who are well-liked have usually not been given hard feedback in years, and they can hear a first instance as an ambush. Say why now: "This is the first time I've raised it, and I'm raising it early because I'd rather it be two releases than ten." That sentence is also true, and it is the honest answer to the question they will not ask out loud: how long have you been thinking this?

If you are new to managing and the report in question was your peer until recently, the conversation carries a second load — the change in the relationship itself. Our article on the first 90 days as a new manager covers the conversation about that before you need the one about performance.

Honest limits

When a script is the wrong tool

Some conversations should not be had by two people alone in a room with a rehearsed opening, and pretending otherwise puts you at risk. If what you are avoiding involves harassment, discrimination, safety, or anything that could end in a legal process, the right first conversation is with HR, a union representative, or a lawyer, and the conversation with the person — if there is one at all — happens with someone else present and a record kept. A script is for problems between reasonable people. It is not protection.

A third person also belongs in the room when the same conversation has been had twice and nothing changed, when the power gap is large enough that the other person cannot safely push back, or when the two of you have a history that makes any observation land as an attack. Bringing someone in is not an escalation; it is a statement that you want the conversation to work more than you want it to be private.

And sometimes the conversation you are avoiding is not with a person. If you have rehearsed the ask and still cannot bring yourself to make it, check whether the thing you are actually avoiding is a conclusion about the job — that it has changed into something you did not sign up for, or that the relationship with your manager is not going to be repaired by a better sentence. That conversation is with yourself first, and it deserves the same honesty: one observation, its impact, and what you want to be different by Friday.

Where coaching fits

What an executive coach does with this, and what he doesn't

A coach cannot have the conversation for you, cannot tell you what the other person will say, and should not be used as a place to rehearse a grievance until it feels righteous. If that is what you want, a coach who pushes back is the wrong purchase.

What a coach does well is the work in this article, faster and with less flinching: turning "I need to talk to him" into an outcome you can observe, cutting the script until it is sayable, mapping the ladder for the specific person you are dealing with, and then playing that person until your answers hold. Mikkel is Verke's coach for work-shaped problems, and he is built for exactly this — you can read how he works on his coach page.

Have it this week, not next month

Tell Mikkel who the conversation is with and what you want different by Friday. He will help you write the four parts, cut them until they are sayable, and then play the other side — defensive, dismissive, upset, whichever you are bracing for — by voice or in text, until your reply comes out steady. No account to create, and he remembers where you left off when the follow-up comes around.

Rehearse the conversation with Mikkel — no signup needed

Common questions

What if I have the conversation and it makes things worse?

It can, briefly. The first honest conversation after weeks of silence often lands harder than the same words would have landed in week one, because the other person can feel how long you have been carrying it. That is the cost of the delay, not of the conversation. What makes things worse in a lasting way is a conversation with no ask in it: you name the problem, they get defensive, nobody says what should change, and you both leave with a grievance. If you go in with a concrete ask and a question that hands them the turn, the worst realistic outcome is an awkward week. The worst outcome of not going in is that the problem becomes the arrangement.

How do I start a difficult conversation without sounding rehearsed?

Rehearse the first two sentences and the ask, not the whole thing. People sound scripted when they try to deliver a monologue they memorized. They sound prepared when they know exactly how they will open, know what they want, and then actually listen to the answer. The opening should be one observation and one sentence about why it matters, said plainly. After that, the conversation belongs to both of you, and your preparation shows up as calm rather than as a speech.

Should I have the hard conversation in writing instead?

Use writing to book the conversation, not to have it. A message like 'I want to talk about how the last two sprints went. Can we take twenty minutes on Thursday?' is fair warning and lets the other person arrive prepared. Putting the substance in an email removes the thing that makes hard conversations work: seeing how it lands and adjusting. It also creates a document that both of you will read in the least generous tone possible. The exception is anything that needs a record for HR or legal reasons, in which case the written version follows the spoken one, not the other way round.

How long should I wait before having the conversation?

Long enough to know what you want from it, and not a day longer. A useful test: if you can write the outcome you want in one sentence, you are ready. If you cannot, the delay is legitimate and the work is to figure out the ask, which usually takes an hour, not a fortnight. Most people who have been avoiding a conversation for more than two weeks already know what they want and are waiting for a version of the moment that feels safe. That version does not arrive. The feeling of safety comes from having rehearsed it, not from having waited.

Can an AI coach really help me rehearse a difficult conversation?

For the rehearsal itself, yes, and it is one of the things it does best. The hard part of practicing a difficult conversation is finding someone to play the other side who will push back the way the real person will. A friend is too kind; a partner has opinions about your workplace. Verke's coach Mikkel will play your colleague, your manager or your report, by voice or in text, and give you the defensive reply, the denial, the counter-attack, until your answer to each comes out steady. He also remembers the situation, so the conversation you rehearse this week and the follow-up you need next month are one thread. What he cannot do is tell you what the other person will actually say, or replace an HR process where one is needed.

Verke provides coaching, not therapy or medical care. Results vary by individual. If you're in crisis, call 988 (US), 116 123 (UK/EU, Samaritans), or your local emergency services. Visit findahelpline.com for international resources.