Difficult conversations

How Team Leaders Handle Difficult Conversations

The conversation a team leader keeps putting off almost never gets easier with time, it just gets more overdue.

A worker's practice has slipped in a way that matters, cutting a support session short, being short with the person they support on a bad day, letting documentation slide. The team leader notices. And notices again the next week. And decides, both times, that it's not quite bad enough to raise properly, so it gets logged mentally and nothing gets said out loud. By the time it finally gets addressed, weeks or months later, it's bigger, harder to unpick, and the worker is understandably confused about why something that's apparently been going on for a while is only being raised now.

This page is written for the leader's side of that moment, not the worker's side of ordinary shift-to-shift friction, which CORA covers separately in Conflict, Boundaries & Difficult Conversations. This one is about the conversations a supervisor has to initiate deliberately, about practice, performance, or values, that most people who get promoted into leadership were never actually taught how to start.

What makes a conversation difficult for a team leader specifically?

Usually it's not the content, it's the relationship risk. Raising a concern with someone you supervise, especially someone you like or used to work alongside as a peer, carries a real fear of damaging the relationship or being seen as the bad guy. That fear is legitimate. It's also exactly why so many of these conversations get delayed until the original issue has grown into something much harder to raise gently.

Why do most leaders wait too long to start the conversation?

Waiting feels like the safer option in the moment, and it almost never is. The gap between noticing something and naming it is where resentment quietly builds on both sides, the leader's frustration at watching it continue, and later, the worker's confusion at being pulled up on something nobody mentioned for weeks. Starting early, while the issue is still small and specific, is nearly always the kinder version of the conversation, even though it feels like the harder one to begin.

The overdue test

If a concern has been true for more than two or three shifts and hasn't been raised yet, it's already overdue. The conversation doesn't get easier by waiting for a better moment, it just gets bigger.

How do you structure the conversation itself?

Name the specific behaviour, not a general impression, describe its actual impact, and be clear about what needs to change from here. "You've seemed a bit off lately" gives a worker nothing to act on. "The last two shift notes were missing key details about how the visit went, and that leaves the next worker without information they need" gives them something concrete to respond to. Leaving space for the worker's side, there might be context the leader doesn't have, matters too, but it shouldn't replace the clarity of naming the issue directly.

What happens after the conversation, and why does that part matter most?

The conversation itself is only half the work. Following up, checking in a week or two later on whether the change has actually stuck, is what tells a worker the standard was real rather than a one-off telling-off. Skipping the follow-up is one of the more common reasons the same issue resurfaces a few months later, not because the conversation was handled badly, but because nothing came after it.

How CORA's course fits into this

CORA's course Managing Difficult Conversations, part of the Leadership & Workforce Sustainability stream in the course library, works team leaders through starting, structuring and following through on the conversations supervisors tend to avoid the longest, practice concerns, value conflicts, escalating issues. It builds understanding and judgement, and sits alongside Addressing Performance & Building Accountability for when a conversation needs to become a more formal process. It doesn't replace an organisation's own HR or performance management policy.

If you're mapping this alongside the rest of the Leadership & Workforce Sustainability stream, the Pathway Builder is a free tool that maps it for you, no sign-up required. Or request a demo if you'd rather talk it through.

Individual membership

One seat, for one support worker. Full access to the CORA course library, plus your own credential register to upload and track your certificates, and settings you manage yourself. The Workforce Capability Report is part of the organisation plans, not the individual membership. Standalone, and not combinable with organisation tiers.

See how CORA covers this and the rest of Leadership & Workforce Sustainability

Browse the full course library, or get in touch if you want to talk through what your team leaders need right now.

Try the Pathway Builder Browse the course library

Common questions

Why do team leaders avoid difficult conversations with staff for so long?

Mostly because of the perceived relationship risk, the fear of damaging rapport with someone they supervise, especially a former peer, or of being seen as unreasonable. That fear is real, but delay usually makes the eventual conversation harder, not easier, because the issue has had time to grow.

How should a team leader structure a difficult conversation with a worker?

Name the specific behaviour rather than a general impression, describe its actual impact, and be clear about what needs to change. Leave space for the worker's context, but don't let it replace clarity about the concern itself.

What's the difference between this and a course on handling workplace conflict?

Conflict, Boundaries and Difficult Conversations covers the everyday friction workers navigate with each other, families or the person they support. This course is specifically for the conversations a leader has to initiate deliberately with someone they supervise, about practice, performance or values.

Why does following up after a difficult conversation matter so much?

Because the conversation alone rarely changes anything on its own. Checking back a week or two later on whether the change has actually stuck tells the worker the standard was genuine, not a one-off. Skipping that step is one of the most common reasons the same issue resurfaces later.

Sources and further reading

This page is general information for team leaders and providers, not HR or legal advice. Always follow your organisation's own performance and conduct policies.

← Back to the course library