Every business owner has one. A conversation with a team member about standards slipping. A conversation with a supplier about a price that's crept up without explanation. A conversation with a client about scope that's quietly expanded past what was agreed. It's been on the list for weeks, and every week it doesn't happen, it gets slightly harder.
The reason these conversations get avoided isn't usually cowardice — it's that most people have never been shown a structure for having them that doesn't feel either confrontational or spineless. Without a structure, the brain defaults to avoidance, because avoidance is the only option that doesn't feel risky in the moment.
A structure that works
State the specific thing you've observed, not your interpretation of their character. Say what impact it's having, concretely. Ask what's going on from their side, and actually listen to the answer before responding. Then agree, together, what happens next. Four steps, in that order, and the emotional temperature of the conversation drops considerably just from following the sequence.
The difference between 'you've been late three times this month' and 'you're unreliable' is enormous, even though they can feel like the same message to the person delivering it. The first is a fact someone can respond to. The second is a character judgement that invites defensiveness rather than a solution. Sticking to specific, observed behaviour — not character — is what keeps the conversation productive instead of personal.
The conversation you're avoiding is rarely as bad as the version you've rehearsed in your head. It's the rehearsal that's exhausting, not the conversation.
Three openers for the three most common versions
The four-step structure holds regardless of who's on the other side of the table, but the actual words change depending on the relationship. With a team member on standards slipping: 'You've been late to the last three morning handovers — I wanted to flag it before it becomes a pattern. What's going on?' With a supplier whose price has crept: 'Your invoice this quarter is higher than last, and I don't remember discussing that — can you talk me through what's changed?' With a client whose scope has quietly expanded: 'The last two jobs have included work that wasn't in the original quote — I'm happy to do it, but I need us to agree how it gets priced going forward.' Each one states the specific, observable fact first, asks rather than accuses, and leaves the door open for a reasonable explanation, without pretending the issue doesn't exist.
The listening step is the one people skip
It's tempting to treat step three — asking what's going on from their side — as a formality on the way to delivering your point. Done properly, it's often the step that changes the outcome most. The colleague who's been late three times might be dealing with a childcare problem you don't know about. The supplier whose prices crept up might be absorbing a cost increase they haven't yet explained. Skipping genuine listening in favour of rushing to state your position turns a conversation into a lecture, and lectures rarely change behaviour.
A worked example: the supplier whose price crept
Put figures on it and the cost of avoidance stops being abstract. A small manufacturer's quarterly invoice from its main materials supplier had been £4,200 for two years. It arrived at £4,830 with no covering note. That is £630 a quarter, or £2,520 a year, and on a business turning over £180,000 at a 38% gross margin — £68,400 of gross profit — it quietly removes 3.7% of the gross profit the whole business runs on. The owner sat on it for two quarters because the supplier was decent, the relationship mattered, and raising it felt petty over what looked like a few hundred pounds.
The conversation, when it finally happened, took under twenty minutes and followed the four steps exactly. Specific fact: 'the invoice has gone from £4,200 to £4,830 and I don't remember us agreeing that.' Impact: 'that's £2,520 a year and it comes straight off my margin.' Question: 'can you talk me through what's changed?' The answer was that £430 of the increase was a genuine raw-material rise the supplier had absorbed for a year and could no longer carry, and £200 was a delivery surcharge added across all accounts without anyone telling customers. The raw-material rise was fair and stayed. The surcharge was waived for a customer who collected their own orders. Settled invoice: £4,630, so £800 a year recovered.
The arithmetic is worth sitting with. Twenty minutes of mild discomfort returned £800 a year, and it also stopped the £1,720 that was legitimate from being a mystery the owner resented every quarter without ever naming. Two quarters of avoidance cost £400 of the recoverable amount outright — money that was gone because nobody asked. Delay is not a neutral option that keeps things as they are. It has a price, and the price runs every month the conversation doesn't happen.
When it stops being an informal chat
Most of the conversations owners avoid are genuinely informal — a quiet word, resolved in one sitting, no paperwork needed. But it's worth knowing where the line sits, because treating a genuinely serious issue as an informal chat repeatedly, rather than moving it into a proper process, can leave a business exposed if it ever ends in a dismissal or a tribunal claim. The ACAS Code of Practice on disciplinary and grievance procedures is the standard UK employers are measured against, and it expects a fair, documented process — a clear statement of the issue, a chance to respond, a right to be accompanied at any formal meeting — once an informal conversation has been tried and hasn't resolved the problem. Skipping straight to a formal written warning without ever having the informal conversation first is one of the more common, and avoidable, ways employers end up on the wrong side of that Code.
The practical rule of thumb: if you've had the informal conversation once, calmly, and the specific behaviour continues, that's the point to start keeping a brief written note of what was said and when — not because you're building a case against someone, but because a pattern that's only ever lived in your memory is a pattern you can't act on fairly later, for them or for you.
Why waiting makes it worse
Every week a difficult conversation gets delayed, two things happen: the issue gets a little more embedded, and your tolerance for it quietly recalibrates, until what would have been a five-minute conversation in week one has become a resentment by week eight. By the time an owner finally has the conversation they've been avoiding, it often comes out with more heat than the situation actually warrants — not because the issue got worse, but because weeks of silent frustration built up behind it.
The failure mode: waiting for the perfect script
The structure above is a starting point, not a script to be word-perfect before you'll allow yourself to start. Owners who wait for the ideal phrasing, the right mood, the perfectly calm moment, are usually just extending the avoidance with better branding. The conversation doesn't need to be eloquent. It needs to happen while the issue is still small enough that naming it doesn't feel disproportionate to either side.
What to do right after the conversation
The conversation itself is only half the job. Whatever gets agreed — a change in behaviour, a revised price, a tighter scope — needs a specific, small follow-up point, not a vague hope that things improve. 'Let's check in again in two weeks' does more to make an agreement stick than a conversation that ends with a handshake and no plan to revisit it. Without a follow-up point, it's very easy for both sides to quietly slide back to exactly where they started.
What to do this week
Name, on paper, the one conversation you've been avoiding longest. Write the first sentence using the structure above — specific fact, not character judgement — and read it back to yourself once. Then book the actual conversation this week, not 'soon'. If it turns out to need more than an informal chat, that's useful information too, and it's far easier to move into a proper process early than to explain, months later, why an obvious pattern was never addressed at all. The single best time to have the conversation was when you first noticed the issue. The second best time is this week.
Common questions
How do I open a difficult conversation without it turning into a row?
State the specific thing you observed, not your judgement of their character, and ask before you conclude. You have been late to the last three morning handovers is a fact someone can respond to; you are unreliable is a verdict that invites a defence. Follow the fact with the concrete impact, then a genuine question — what is going on? — and stop talking. The order matters more than the wording. Most of these conversations turn into arguments at the moment the other person realises the outcome was decided before they spoke, and asking first is what prevents that. Do not spend a fortnight hunting for perfect phrasing either; that is avoidance wearing better clothes.
When does an informal chat need to become a formal process?
Once you have had the informal conversation calmly and the specific behaviour continues, that is the point to start keeping written notes and to consider a formal process. The Acas Code of Practice on disciplinary and grievance procedures is the standard UK employment tribunals measure employers against, and a tribunal can increase a compensation award by up to 25% where an employer unreasonably fails to follow it. The Code expects a clear written statement of the issue, a proper chance to respond, the right to be accompanied at any formal meeting, and a right of appeal. The other direction counts too: jumping to a formal written warning without ever trying the informal conversation is its own way of falling foul of it.
Can I dismiss someone for poor performance without going through a process?
Legally you may have room, but it is a bad idea and the room is shrinking. Ordinary unfair dismissal claims currently need two years of continuous service, but that qualifying period drops to six months from 1 January 2027, so a good deal of what feels safe today will not be next year. Some dismissals are automatically unfair with no qualifying period at all — those connected to pregnancy, whistleblowing or asserting a statutory right, for instance — and discrimination claims tied to a protected characteristic have never required qualifying service. Beyond the law, a performance dismissal with no documented conversations behind it is one you cannot defend, cannot explain to the rest of the team, and cannot learn anything from.
Does an employee have the right to bring someone to the meeting?
Yes. At any formal disciplinary or grievance hearing, employees have a statutory right to be accompanied by a work colleague or a trade union representative. It is not a favour you grant, and refusing it is one of the specific failures that can attract an Acas Code uplift to a tribunal award. The companion can put the employee's case, sum up, and confer with them during the hearing, though they cannot answer questions on the employee's behalf. For a genuinely informal chat — a quiet word about lateness, settled in one sitting — the right does not bite, but offering it costs nothing. Mention it in the letter inviting them to the meeting rather than waiting to be asked.
How long does an employee have to bring a tribunal claim against me?
For most claims it is three months less one day from the act complained of — but this is changing. Under regulations approved in 2026, the time limit for a wide range of employment tribunal claims extends from three months to six months where the act or failure complained of falls on or after 1 October 2026. Anything arising wholly before that date keeps the three-month limit. Acas early conciliation pauses the clock while it runs. The practical consequence for an employer is a longer tail of exposure than you may be used to, which makes contemporaneous written notes more valuable rather than less: your memory of a chat two quarters ago is worth very little at a hearing.
