The hidden cost of avoiding hard conversations.
The conversation you postponed in March is the resignation you'll get in September, the project you'll lose in December, and the culture problem you'll explain to investors next year. Here's how to count the iceberg.

Every leader has a list. The performance conversation they keep moving. The boundary they haven't drawn. The peer feedback they meant to give 'when the timing was right.' We tell ourselves we're being patient. The team experiences it as cowardice — and they're not wrong.
The cost of an avoided conversation is almost never the cost of the conversation itself. It's the compound cost of everything downstream. Here's how to make that math visible.
The five conversations leaders most commonly avoid
- Telling a long-tenured employee that the company has outgrown their current role.
- Telling a co-founder they're blocking a decision the company needs to make.
- Telling a high-performer that their behaviour is hurting the team, even if the output is great.
- Telling a peer leader that their team is creating a problem for yours.
- Telling a board member that their advice is wrong, in front of the other board members.
The psychology: amygdala hijack and the avoidance cycle
Daniel Goleman's work on emotional intelligence describes the 'amygdala hijack': when a conversation feels socially threatening, your brain treats it as a physical threat. You delay, you rehearse, you tell yourself you're being thoughtful. Meanwhile, every day of delay raises the emotional stakes — for you and for them. By month three, the conversation that would have taken 10 minutes in February requires 90 minutes, a witness, and a severance discussion.
The iceberg model: what avoidance actually costs
Above the waterline, the visible cost is the discomfort you saved yourself this week. Below the waterline, the compound costs build silently:
- Your other team members do extra work to cover. They notice. They don't complain — they update their CVs.
- Your high performers learn that standards are negotiable. They lower theirs accordingly.
- The person you're avoiding feels the avoidance and interprets it as either contempt or instability. Either is corrosive.
- You spend cognitive energy every day rehearsing the conversation you're not having. Decision quality on everything else drops.
- Your next hire inherits the unspoken rule that hard things don't get said here. They calibrate accordingly.
The SBI-N script: how to have it in 8 minutes
Adapted from CCL's Situation–Behaviour–Impact model, with a 'next' added. Use this when you don't know how to start.
- Situation (15 sec): 'In Tuesday's planning meeting…'
- Behaviour (15 sec): '…when you interrupted Priya three times before she finished her proposal…'
- Impact (30 sec): '…the team stopped contributing, and we shipped a worse plan. I noticed Priya didn't speak in Thursday's standup either.'
- Next (5 minutes): 'What's your read on this? What would help you do this differently next time?' Then listen.
What you'll discover when you start having them
- Most hard conversations are easier than the version you rehearsed. The other person often already knows.
- The person on the receiving end usually thanks you, weeks later, for the respect of being told the truth.
- Your team's perception of you as a leader recalibrates fast. They notice the change in the first 60 days.
- Your own stress drops. Avoidance is exhausting in a way you only realise once it's gone.
Take this home — the avoidance audit
- List the conversations you're avoiding. Be honest. Top three.
- For each, estimate the cost of one more month of avoidance. Write a number.
- Schedule the highest-cost one for this week. Use the SBI-N script.
- Tell one peer (co-founder, coach, fractional CHRO) which conversation you're having and when. External commitment is the cheat code.
- Debrief yourself in writing afterwards. What were you afraid of? What actually happened?
- Make the Monday avoidance list a weekly habit. It's the cheapest leadership development you'll ever do.
HR & Operations leader scaling global remote teams across Nepal, the Philippines, Australia, and the US. Tech-leaning writing lives on Medium.