A leader can spend more time avoiding a difficult conversation than having it.
In this scenario, Dani drafts and deletes meeting invitations before sending a plain 1:1 with no agenda. Three colleagues have raised concerns about an analyst’s interactions, including incidents in Slack and a retrospective. Dani discusses workload and goals instead. The analyst leaves believing the meeting went fine.
That is not a resolution. It is a meeting that left the central question untouched.
Dani may call the delay caution, or a way to keep things from getting worse. And caution matters. Reports can be incomplete. People can interpret the same exchange differently. A leader who walks in with a verdict based on secondhand accounts can turn a fair process into an unfair confrontation.
But caution and avoidance are not the same thing.
If the reports concern you, your responsibility is to understand what happened: what was said or done, when, who was present, and whether there is context you do not yet have. Then speak with the employee about specific behavior and the standard expected. That is different from deciding someone is “toxic” and asking them to defend their character.
The distinction matters. A label closes the conversation before it begins. A concrete example gives both people something to examine.
“You have a bad attitude” is a judgment. “In the retrospective, you interrupted Priya twice while she was explaining the handoff, then called the concern ‘basic’” is a claim that can be discussed, checked, and answered. If your understanding is wrong or incomplete, you need to know that too.
What Dani cannot do is keep having meetings about everything except the concern. Each time she postpones it, she avoids the discomfort of uncertainty. The colleagues who raised the issue remain in it.
That does not establish that every report is accurate, or that the analyst intended harm. It does mean the leader has a question to take seriously. Silence can leave people unsure whether their concerns were heard, whether the behavior is acceptable, or whether raising it was worth the risk. The scenario does not tell us what those colleagues will conclude. It does show that Dani has not given them an answer.
The conversation does not need to begin with a polished speech. It needs to begin honestly:
“I want to discuss some specific interactions that colleagues have raised with me. I’m still working to understand what happened, and I want to hear your perspective. I also want to be clear about the standard for how we speak to one another.”
Then give the examples. Ask for the employee’s account. Listen without treating disagreement as proof of guilt. Explain what needs to change if the behavior is substantiated, and what follow-up will look like. If policy or the seriousness of the situation calls for support from HR or another appropriate resource, involve them rather than improvising your way through it.
You do not owe anyone a premature verdict. You do owe the situation attention.
It is tempting to wait until you feel certain, calm, and ready for every possible response. Sometimes more information is needed. Sometimes “not yet” is just the most respectable name you can find for “I do not want to deal with what happens next.”
Be honest about which one it is. Your team should not have to keep guessing whether you saw the problem—or whether you decided that avoiding it was easier.
