Don't avoid the hard conversation. Do prepare for it.

There is a particular kind of consultant behaviour which treats difficult stakeholder conversations as something to be avoided, postponed, or softened into meaninglessness. That behaviour makes us send vague emails that say "something to keep an eye on", or "thought you should know this". And it waits for the problem to become undeniable before they say anything useful.

While a potentially difficult conversation is brewing it’s not always obvious if the circumstances warrant being elevated to “we need to address this”. They say to pick your battles, right? And you also don’t want to be perceived as being alarmist.

I think that tension - along with a fear of perhaps disappointing the people around you - is what sometimes makes us bide our time.

However, difficult conversations, handled well, do not have to drain momentum from a project. Instead, they can actually create the momentum. The catch is that "handled well" takes some preparation - and some people skip that part.

Why preparation is the whole game

When you walk into a difficult conversation without grounded evidence, you are essentially asking a stakeholder to take your word for it. If the stakes are high, this rarely goes well. The moment they push back, you are left defending an opinion rather than a position. The conversation either collapses or could turn adversarial.

What changes the dynamic is arriving with a credible, specific prediction of what happens if your advice is ignored. Not a vague warning. Not "this could cause an issue." A plausible failure path with a real cost attached - endless support backlogs, broken reporting, slower deployments, a system that fails at the worst possible moment.

Before a difficult conversation, I sometimes choose to send a short note and relevant artifacts in advance. Data points, risk scenarios, test results - whatever is relevant. The purpose is to avoid overwhelming the stakeholder(s). It is to make sure they have context before they are sitting across from you and have to process new information under social pressure. That is not a fair position to put anyone in, and it does not tend to produce good decisions.

A three-step plan that actually works

Once you are in the room, I find a consistent structure helps.

Start with a clear preamble. State what you want to talk about and why it matters: "I want to talk about X today, and the outcome will affect Y." It doesn't have to be presented with the "Imperial March" as the metaphoric soundtrack. It can be presented respectfully and without drama. It signals that you have something specific to raise, that you have thought it through, and that you are not ambushing anyone.

Frame the trade-off. Describe the plausible failure path and its consequences: "Here is what I do not want to see happen." Keep it calm and specific. You are not threatening the stakeholder. You are just showing them what you are trying to help them avoid. The difference matters - one sounds like a warning, the other like a partnership.

Close with a choice. This is the part some consultants fumble. After making your case, the temptation is to either capitulate ("but of course it's your call") or keep pushing until the stakeholder agrees. Neither is right. The correct move is to hand the decision back, cleanly: "I have given my point of view. I need you to make the final decision." Then document it. Who decided, what was decided, and the context behind it.

That last step - documentation - is less about covering yourself than it is about clarity. Purely verbal decisions tend to develop amnesia over time. Especially if hindsight reveals it was the wrong decision.

Tone is doing more work than you think

The script is almost beside the point if the tone is wrong. Calm and specific. Brief. No drama.

Consultants sometimes confuse passion for persuasion. They become animated, repeat themselves, push harder when they sense resistance (I've done that myself sometimes). It rarely helps and often backfires.

If you want to be taken seriously in a difficult conversation, the most effective thing you can do is sound like someone who has thought about this carefully and is not particularly rattled by disagreement. Which - if you have actually done the preparation - you should not be.

What this builds over time

The short-term goal of a difficult conversation is a clear decision. The long-term effect is something more valuable: credibility.

Stakeholders learn patterns. When you consistently surface risks early - not after the fact, not buried in a status update, not wrapped in so many qualifications that the point is lost - they start to trust your read on things. They know that when you say something is a problem, it probably is. That trust is hard to build and easy to lose.

Winning the conversation is not the objective. A stakeholder who feels outmanoeuvred in a difficult conversation is not an ally. The aim is a clear decision, made with full information, owned by the right person. Everything else follows from that.

If that still feels uncomfortable, here is an alternative framing: the conversation you are avoiding is never as difficult as the one you will have to have three months later when the problem has materialised and everyone wants to know why nobody flagged it.