top of page

Why You're Avoiding That Difficult Conversation (And How to Actually Have It)

Sep 27
7 min read
Two people having a calm one-to-one conversation at work

AI Summary

This article explains why people avoid direct feedback conversations, using neuroscience (social pain, the SCARF model) to show that avoidance protects the avoider, not the relationship. It offers a three-step structure — observation, impact, ask — and points to leadership training and The Standing Appointment retainer as ways to build the skill.


The Feedback Conversation You've Been Avoiding (Yes, Even the Dishwasher One)


This is, hands down, the skill I get asked to teach more than any other — and not just by leaders managing underperformance. Partners navigating the same argument on repeat. Parents trying to get through to a teenager without triggering World War III. Managers who've been sitting on the same piece of feedback for three months. Turns out we're all having some version of the same conversation, badly, in every part of our lives.


What We Actually Mean by "Difficult Conversation"


Before we go further, let's define it — because "difficult conversation" gets used as a catch-all, and that vagueness is part of why we avoid them.


A difficult conversation is any exchange where you need to say something the other person may not want to hear, and where you're genuinely uncertain how they'll respond. It's difficult because the outcome isn't guaranteed and the relationship feels like it's on the line.


And before you open your mouth, it's worth being honest with yourself about the goal, because the three most common ones require different approaches entirely:


  • Influence — you want something to change (a behaviour, a habit, an approach).

  • Clarify — you want to understand what happened, or make sure you're not assuming the worst.

  • Confirm — you want to check that what you think is true, actually is, before you act on it.


Walking in without knowing which of these you're after is how conversations go sideways — you think you're clarifying, they think you're attacking, and now you're both defending positions nobody actually stated.


The Pattern


Here's a scene that plays out in boardrooms and kitchens with equally impressive frequency: someone does something that doesn't quite land right, and instead of saying so, we... don't.


We drop hints. We over-explain the "right way" one more time, hoping it sinks in by osmosis. We give the look. We quietly re-stack the dishwasher ourselves at 11pm, muttering about how "if you want something done properly." Sound familiar?


Now scale that up to a team. A report that's consistently late. A meeting habit that derails the agenda. A pattern of talking over people. Leaders will often carry that irritation for weeks — sometimes months — rehearsing the conversation in the shower, drafting it in their heads, building it into something enormous. And then one of two things happens: they ambush the person in a moment of frustration, or they soften it so much in the actual conversation that the message evaporates entirely and everyone leaves confused about what was actually said.


Either way, the conversation that was supposed to fix the problem often makes it worse. And the dishwasher stays stacked wrong.


The Psychology


There's a reason this is so universally uncomfortable, and it's not a character flaw — it's wiring.


Giving direct feedback activates the same threat-response system in our brains as physical danger. Social psychologist Naomi Eisenberger's research on social pain showed that the brain processes relational threat — the risk of damaging a relationship, being disliked, or causing conflict — through overlapping neural pathways to physical pain. When we're about to say something that might land badly, our amygdala doesn't distinguish neatly between "this might hurt the relationship" and "this might actually hurt." It just says danger.


Here's the part most people miss, though: when we avoid the conversation, we tell ourselves it's to protect the other person, or the relationship. Mostly, it's to protect ourselves. Avoidance is a remarkably effective short-term strategy for reducing our own distress — it makes the discomfort go away right now. The cost gets paid later, and usually with interest: the resentment builds, the pattern repeats, and when it finally comes out, it comes out bigger and messier than it needed to be.


This is where the SCARF model (David Rock) is genuinely useful — not as theory, but as a checklist for why conversations go well or badly. It names five domains our brains treat as social survival needs:


  • Status — do I feel respected, or diminished?

  • Certainty — do I know what's happening, or is this ambushing me?

  • Autonomy — do I have any say here, or is this being done to me?

  • Relatedness — are we still on the same side, or are you now "against" me?

  • Fairness — does this feel just, or arbitrary?


Threaten any of these — even accidentally, even with good intentions — and the other person's brain shifts into defend mode before they've processed a word of what you actually said. Which means how you open a conversation often matters more than what you say next. Give someone a heads-up (certainty), ask rather than declare (autonomy), acknowledge what's working before naming what isn't (status) — and you've dramatically increased the odds the conversation actually goes somewhere useful, instead of into a defensive spiral.


Why Leaders Actually Avoid These Conversations


I was asked recently what's genuinely missing from most leadership capability programs — why leaders who've sat through the training still aren't having the conversations on the ground. My honest answer: it isn't that they lack a framework. Most of them can recite the model back to you — observation, impact, ask. What they're short on is something harder and far less trainable: having actually sat down and worked out what their observation, their impact and their ask are, for the real, specific, slightly awkward conversation they're avoiding.


A framework tells you where to put your thinking. It doesn't do the thinking for you. That's where the applied clarity comes from — the training, done properly, gets you there.


But clarity alone doesn't get you through the door. That takes something else entirely: the courage to actually try the conversation, knowing your first attempt at anything is rarely your best one.


  • Clarity comes from training — applying the framework to your own real situation, not just knowing the model.

  • Courage to try is what turns that clarity into an actual conversation, rather than a well-prepared thought that never leaves your head.

  • Courage to fail is what happens next, when it doesn't go to plan — and it's what actually builds confidence, not the other way around. You don't get brave and then try. You try, it goes sideways sometimes, and the trying is what makes you brave.


Most training gives people the framework and calls it done. It doesn't give them the rehearsal, and it doesn't give them permission to get it wrong. So the first time it's tested for real — with something at stake — there's clarity but nowhere to put it, because nobody built the courage to actually use it, or survive using it badly. The leader defaults to what feels safest: silence, or an ambush.


Here's a version of courage nobody puts on the leadership poster: the courage to have a go. The courage to try something that might not land. The courage to be vulnerable in front of the people who report to you. And, uncomfortably, the courage to fail — and to be wrong, out loud, in front of an audience. Effective performance conversations don't happen because a leader finally became fearless. They happen because a leader decided that being occasionally wrong was a more acceptable risk than staying silent. 


Effective leadership isn't fearlessness. It's the courage to fail.


The Leadership Move


Effective performance conversations aren't about being blunter, or softer — they're about being structured, and about being aware of SCARF as you go.


A simple shape that works whether you're managing a missed deadline, a recurring argument with a partner, or a dishwasher tragedy:


  • Observation — What actually happened, specifically and without interpretation. ("The report was three days late" not "you don't respect deadlines.")

  • Impact — What that meant, for the work, the team, or you. ("It meant I had to present without the full data, which was stressful in the room.")

  • Ask — What you need going forward, stated plainly — and, where you can, as a question rather than a directive, to protect their autonomy. ("Can we agree on a buffer day before the deadline next time, or a heads-up if it's slipping?")


That's it. No ambush, no mush. Just clarity, delivered in a way that keeps the other person's brain out of threat mode long enough to actually hear you.


Do this well and something interesting happens: people stop dreading feedback from you, because they know what they're going to get — something clear, fair, and survivable. That's what builds the kind of trust that actually holds a team together under pressure. (It also does wonders for the teenager and the dishwasher situation. Results on the dishwasher may still vary.)


Where To From Here


Of everything I teach, this is the one people come back and tell me they use the most — at work, at home, everywhere in between. It's not a leadership skill so much as a human one; leadership just happens to be where it gets tested daily, and where the cost of avoiding it compounds fastest.


Here's the thing about clarity and courage, though: training can hand you the first. It can't hand you the second. Courage doesn't arrive from a workshop — it arrives from actually trying the conversation, and from surviving the ones that don't go to plan.


That's why this tends to work as two things, not one. A training session — for a small team or a whole leadership group — is where the framework becomes applied clarity: where you actually sit down, in a room, and work out what your observation, your impact and your ask are for the real conversation you've been avoiding. It's the fastest way to build that clarity, together.


Then there's what happens after the training day, back in the real job, where the courage to try — and the courage to fail — actually gets tested. That's what Your Business Psychologist — The Standing Appointment is built for: ongoing, one-to-one support to try it for real, debrief the conversations that went sideways, and keep building the kind of courage that only comes from doing it again anyway.


Comments


bottom of page