A Guide to Working through Difficult Conversations at Work

Nobody enjoys difficult conversations. But avoiding them is always worse than having them. Unaddressed problems compound. Feedback you dodge in March becomes a performance issue by September. A conflict you "let them work out" poisons the team dynamic for months.

Here's how to handle these conversations, whether you're a manager, a contributor, or someone on a distributed Web3 team where most communication happens over text.

Types of Difficult Conversations

Not all tough conversations are the same. Your approach should vary.

Giving critical feedback. Someone's work isn't meeting expectations, or a specific behavior is causing problems. This is the most common difficult conversation and the one people avoid most.

Addressing conflict. Two people (or two groups) disagree, and it's affecting the work. You need to mediate or at least get the issue on the table.

Compensation discussions. Someone asks for a raise you can't give, or you need to explain why their pay isn't changing. Money conversations carry emotional weight because people tie compensation to self-worth.

Termination or offboarding. The hardest conversation in management. Telling someone their role is ending requires clarity and preparation.

Scope and commitment disagreements. Especially common in Web3 and DAO environments, where contributors may disagree about deliverables, timelines, or what was actually committed to in a governance proposal.

Preparation Is Everything

The biggest mistake is winging it. You walk in with a vague sense of the problem, get flustered when they push back, and leave with nothing resolved.

Before the conversation:

• Write down the specific issue. Not "their attitude is bad" but "They've missed the last three sprint commitments and didn't flag any in advance."
• Identify what outcome you want. What does "success" look like after this conversation? A behavior change? A plan? Know this before you start.
• Anticipate their perspective. They'll have reasons for whatever happened. Think about what those might be.
• Choose the right medium. For serious conversations, video or in-person is almost always better than text. Tone gets lost in Slack, and what you intended as direct can read as cold.

A Simple Framework for the Conversation

You don't need a script, but you do need structure. This three-part framework works:

1. State the issue clearly. Don't bury the point in small talk. "I want to talk about the last two deliverables, which were both late and had errors the team had to fix" is clear. "I just wanted to check in" is not.

2. Listen. After you state the issue, stop talking. Let them respond. They may have context you don't. They may disagree or get emotional. Your job here is to understand their perspective, not win an argument.

3. Agree on next steps. Every difficult conversation should end with something concrete. What's going to change? By when? How will you both know if it's working? Write this down and follow up on it.

Managing Emotions — Yours and Theirs

Difficult conversations trigger emotional responses. That's normal. Here's how to handle it:

If they get upset, don't rush to fix their feelings. Acknowledge what they're feeling — "I can see this is frustrating" — without backing away from the issue.

If you feel yourself getting reactive, slow down. Take a breath. Say "Let me think about that for a second" to buy yourself time.

If the conversation goes off the rails, pause. "Let's take a break and come back to this tomorrow" is not weakness — it's judgment.

The Async Complication

Remote and Web3 teams often default to text — Discord, Telegram, Slack. This adds real complexity to difficult conversations.

Text strips out tone, facial expressions, and natural conversational pacing. A message you write carefully can land as blunt or hostile.

Rules of thumb for async difficult conversations:

• Escalate to a call for anything serious. Text is fine for small asks. It's terrible for performance conversations.
• If it must be in text, over-communicate your tone. Say "I'm bringing this up because I want us to fix it together, not to blame you."
• Don't have these conversations in public channels. DMs or private calls only.

Follow Up

The conversation isn't the end — it's the beginning. Whatever you agreed to, check back on it. If you said you'd revisit the situation in two weeks, actually do it. If the other person committed to a change, notice when they make it and acknowledge it.

Following up shows the conversation mattered. Skipping it sends the opposite message.

Difficult conversations are a skill, not a personality trait. You get better by having more of them, preparing well, and learning from the ones that go sideways. In any work environment — especially one as distributed as Web3 — addressing problems directly is one of the most valuable things you bring to a team.