With an unhappy internal client, the mistake is answering the tone instead of the content. The sequence that works: acknowledge without justifying, isolate the verifiable facts, propose a dated plan with a checkpoint, and deal separately — later, in private — with how the criticism was delivered.
Adrien VasseurUpdated
David, operations director, catches you at the end of a committee meeting in front of six people: «your deadlines haven’t been met for three months, we can’t work like this.» The tone is sharp, the attack is public, and part of what he says is accurate — two of the five delays are on his side, but the other three are genuinely yours. Your team is in the room. Whatever you answer will be retold in both departments before the end of the day.
You have no hierarchical authority over him, so none of the usual managerial levers apply. The public format creates a double bind: defending your team is necessary so as not to abandon them, but any energetic defence reads as denial. On top of that, you have to sort in real time — an aggressive criticism almost always mixes truth, exaggeration and projection, and you must separate them in seconds, without the data, in front of people who decide your resources for the quarter.
Answering «that’s not accurate, there were two, not five» loses even when you are right: the room registers that you are arguing while a department complains. Acknowledge the subject and ask for the data so you can look at it together.
Escalating in front of witnesses manufactures a durable inter-department conflict that will outlive both of you. You convert a fixable delivery problem into a turf war, which is not fixable.
«You’re right, we’re underperforming, I’ll take it in hand» settles the meeting and costs you your team, who will hear the sentence within the hour. You can acknowledge a collective problem without naming culprits.
Committing to a deadline under pressure, without consulting your team, guarantees a second incident — this time with a broken personal commitment, which costs far more than the original delay.
One calm sentence: «The issue is real and I’m not going to deal with it in three minutes here. Send me the five cases, I’ll look at them, and we meet on Thursday with the data.» You neither deny nor concede, and you move the conversation into a format where it can conclude.
Go through each case with dates and causes, including the ones that originate on his side. Arriving with a factual table changes the balance entirely: you are no longer defending, you are presenting.
A public attack of that kind is usually driven by pressure you cannot see — a commitment made to his own leadership, a target at risk. The useful question: «What are these delays costing you concretely, on your side?» The answer almost always opens a solution the deadline argument was blocking.
Two or three precise commitments, a shared indicator, a review date: «From the 1st you get the progress update every Monday, and we meet again in three weeks.» A scheduled checkpoint beats any promise of vigilance.
The delivery question is never settled in the same conversation as the substance. Once the plan is in place, a separate sentence: «I’m dealing with the issue, and I’d rather you came to me directly than raise it in committee.» Substance first, relationship second — the reverse does not work.