The session on fierce conversations had the sharpest line of the whole training, and I wrote it down immediately. Avoiding a hard conversation is also a choice. It just isn’t a free one. That line is going to be in my pocket for years. It also describes something I already practise — being the manager people bring hard things to early, because the conversation that follows is going to be honest, kind, and useful.
I want this essay to be specific about how I think about hard conversations, because too much of the literature treats them as an event you must steel yourself for. They aren’t an event. They’re a default mode that, once your team trusts it, makes most of the rest of management lighter.
What a fierce conversation actually is
The word fierce is what throws people. The session was clear that this isn’t about being aggressive. It’s about being honest, clear, and human — three qualities that don’t usually appear in the same sentence about hard conversations because we tend to imagine them as trade-offs.
The trade-off framing is the problem. The whole reason fierce conversations are a skill is that they’re the moves where you don’t have to choose. You can be honest and warm. You can be clear and curious. You can name a hard thing and leave the other person feeling more seen, not less. That combination doesn’t come naturally to most leaders, but it’s the combination I’ve spent these last two years building toward, drawing on the best managers I worked under as an engineer who made it look effortless.
The mental anchor the facilitator gave us: what is the most loyal version of the truth I can say right now? That phrasing is going to be in my pocket. Loyal signals that the relationship matters. Truth signals that comfort isn’t the point. Right now signals that the conversation cannot wait.
How I work to make hard conversations cheap
The single most important move I’ve made as a manager is creating a space where hard things get said early. Not because I’m an unusually brave conversationalist — I’m not — but because I built the conditions that make it cheap for my team to bring concerns directly, and I made bringing them feel productive.
I’m available. Genuinely. People don’t have to schedule a meeting to flag something — they can catch me in a thread or in the rhythm of the day. The signal I’m sending is bring it now. The cost of waiting is higher than the cost of telling me.
I’m prepared to be wrong. When someone brings me a hard thing, I take it seriously even when I don’t initially agree. I sit with it. I repeat it back. I ask what I’m not seeing. I’ve been doing this long enough that the team trusts the engagement will be real, which is most of what makes them willing to bring more.
I name the agreement. I’m a routine person; I love explicit agreements. After a hard conversation, I name what we agreed on, what’s still open, and what I’m going to do by when. The clarity at the end of a difficult talk is part of what makes my team willing to come back. The same applies to the hard conversations I initiate.
I don’t avoid the ones I owe. When I owe someone a hard conversation, I have it. Not always perfectly, not always on the first attempt, but I have it. The cost of avoiding it is something I’ve felt enough — from the engineering side under managers who avoided, and once or twice in my own first year as a manager when I delayed something I should have addressed — that I treat the avoidance impulse as a flag, not a feeling to obey.
What the session added
Two real things.
The “loyal truth” line is going to be reference vocabulary for me. I’ll be using it in one-on-ones, in writing, in moments where I need to remind myself what the conversation is for. The phrase compresses the whole posture into four words.
A teachable shape for my team. I’d been having fierce conversations with my team and modelling them in small ways, but I hadn’t been explicit about why they work. The session gave me language I’ll use to teach my senior engineers how to have these conversations with each other and with their peers. That’s the multiplier — me having fierce conversations is good; my team having them with each other is much, much better.
A small story
A few weeks ago, a senior on my team came to me and said I think we’re about to make a decision that won’t age well. I don’t want to overstep — I just need you to know I see it. He didn’t have it perfectly formed; he had the shape of an objection and the courage to bring it before I’d asked. That’s the move I’ve been working to make cheap. The conversation that followed was twenty minutes. The decision shifted. The team avoided a quarter of unwinding work.
I want to be clear: that conversation happened because the space is genuinely safe, not because he is an unusually brave person. The team I lead has dozens of those exchanges a quarter, and almost none of them feel hard in the moment, because hard things get said in small chunks early instead of in big chunks late. The investment in that culture is one I’d make again every time. It compounds.
What avoiding costs, specifically
I want to be concrete about the cost, because the abstract version is easy to discount.
When a leader delays a performance conversation with someone who needs to hear it, three things happen, none of them visible right away. First, the person continues to underperform, because nobody has named for them that they’re underperforming. Second, the rest of the team starts noticing — not the performance issue, but the non-response. Third, when the conversation finally happens, the gap between the behaviour and the reaction is now months wide, and the person can fairly ask why didn’t you tell me earlier? and the leader will not have a good answer.
When a leader delays a hard call about scope or strategy, the team works on the wrong thing for the duration of the hesitation. That work isn’t free. It’s engineer-weeks, customer-impact, opportunity cost.
When a leader delays a hard conversation with a peer, the small issue that could have been resolved with one direct sentence calcifies into an organisational pattern, and at some point everyone is no longer arguing about the original thing — they are managing around a relationship that’s started to brittle.
None of this is dramatic. All of it is real. And the teams I’ve watched run best across years are led by people who chose, over and over, to have the conversation now.
The team effectiveness piece
The throughput case for fierce conversations is simpler than it looks.
A team in which hard things are said early, kindly, and honestly is a team that fixes problems while they’re small. A team in which hard things get deferred until they’re unavoidable is a team that spends a lot of energy on damage control that wasn’t necessary. The compounding effect is enormous. Six months of small, honest conversations is dramatically less expensive than one quarter of postponed reckoning.
The other piece — the one I find most interesting — is that teams know when their leader is avoiding. They might not name it. They might not even consciously notice it. But they read the pattern. And the leader who avoids the hard conversation, even with the best intentions, slowly teaches the team that hard things will not be addressed. That posture is contagious. The team starts avoiding the hard things with each other, too, because the model in the room is to defer.
That’s why I’m relentless about not avoiding. Not because I’m brave. Because I’ve seen what avoiding teaches and I’m not willing to teach it to a team I care about.
The honest close
I still get scared before hard conversations. I still over-prepare. I still occasionally catch myself reaching for the postpone. What’s true is that I have it anyway, almost every time, because the cost of not having it is something I can feel viscerally now. The cost isn’t abstract. It’s the engineer who would have left because nobody told her what she needed to hear two quarters earlier — except I had the conversation, and she’s still here, and she’s better.
I’d much rather have the hard conversation, badly, today, than the much harder version of it three months from now. That’s not bravery. That’s economics, and care, and respect for the people I’m trying to lead.
The session gave me a line for that. I’m going to carry it.