Every organization has them — the conflicts everyone knows about but nobody addresses. The passive-aggressive email chains. The two department heads who haven’t spoken directly in months. The team member whose behavior everyone works around instead of confronting.
These unresolved conflicts don’t stay contained. They spread through teams like slow leaks, eroding trust, draining energy, and quietly driving your best people toward the exit. A 2024 CPP Global study found that U.S. employees spend an average of 2.8 hours per week navigating workplace conflict — roughly $359 billion in paid hours annually.
The problem isn’t that conflict exists. Healthy disagreement fuels better decisions. The problem is that certain types of conflict become structural — embedded in how people interact — because leaders lack the specific language and frameworks to address them. This guide identifies the five most common unresolved workplace conflicts and provides conversation scripts for each one.
1. The role ambiguity conflict
What it looks like: Two people or teams repeatedly clash over who owns a decision, process, or outcome. Projects stall because nobody is sure who has final authority. Both parties feel overworked and underappreciated.
Why it persists: Leaders assume the org chart resolves ownership questions. It rarely does. Role ambiguity thrives in matrix structures, cross-functional projects, and anywhere responsibilities have evolved faster than documentation.
The fix — a responsibility mapping conversation:
Bring both parties together and say: “I’ve noticed we keep running into friction around [specific process]. I don’t think either of you is doing anything wrong — I think we have an ownership gap. Let’s map out who decides, who executes, who needs to be consulted, and who just needs to know. Then we’ll document it so we don’t have to relitigate this.”
The key is framing it as a systems problem, not a people problem. Use a RACI-style framework — Responsible, Accountable, Consulted, Informed — and put the result in writing. Most role conflicts evaporate when accountability is made explicit rather than assumed.
2. The feedback avoidance conflict
What it looks like: A team member consistently underperforms or behaves in ways that affect colleagues, but their manager avoids addressing it directly. The team compensates by working around the person, building resentment that surfaces as gossip, passive-aggression, or disengagement.
Why it persists: Most managers haven’t been taught how to deliver critical feedback without damaging the relationship. So they choose the relationship over honesty — and lose both over time.
The fix — a structured feedback script:
Use this framework for difficult conversations: “I want to talk about something I’ve observed because I think you’re capable of more than what’s showing up right now. In [specific situation], I noticed [specific behavior]. The impact was [concrete effect on team/project]. What I’d like to see instead is [clear expectation]. What’s your perspective on this?”
Notice the structure: observation, impact, expectation, invitation. The invitation at the end is critical — it transforms a monologue into a dialogue. Pair this with active listening when they respond. The goal isn’t to win the conversation. It’s to create a shared understanding of what needs to change.
3. The values misalignment conflict
What it looks like: Two colleagues or teams have fundamentally different philosophies about how work should be done — speed versus quality, innovation versus stability, individual accountability versus collective ownership. Their disagreements feel personal because they’re actually about identity.
Why it persists: Values conflicts masquerade as tactical disagreements. Leaders address the surface issue (which project to prioritize, which approach to take) without surfacing the deeper tension. The same conflict reappears in new forms.
The fix — a values surfacing conversation:
Meet with both parties individually first. Ask: “When you imagine this team operating at its best, what does that look like? What matters most to you about how we work together?” Then bring them together: “I’ve talked with both of you, and I think the friction we’re experiencing isn’t about [specific issue] — it’s about different priorities that both have real value. [Person A], you prioritize [value]. [Person B], you prioritize [value]. Both matter. The question isn’t who’s right — it’s how we honor both.”
This approach requires emotional intelligence and the willingness to sit in ambiguity. Not every values conflict resolves neatly. But naming the real tension — rather than pretending it’s about schedules or budgets — prevents the exhausting cycle of relitigating symptoms.
4. The credit and recognition conflict
What it looks like: Team members feel their contributions are invisible, misattributed, or systematically undervalued. Someone else presents the idea they developed. A collaborative win gets credited to one person. Quiet contributors watch vocal colleagues receive disproportionate recognition.
Why it persists: Recognition systems in most organizations are informal and biased toward visibility. Leaders recognize what they see, and what they see is often shaped by proximity, communication style, and existing relationships rather than actual contribution.
The fix — a recognition audit and protocol:
Address it directly: “I want to make sure our team’s recognition practices match actual contributions. I’m going to start doing two things differently. First, for every major deliverable, I’m going to ask the team to identify everyone who contributed and how. Second, in leadership meetings, I’m going to name specific contributions from specific people rather than speaking about the team generically.”
Then create a norm: when presenting work upward, always name contributors. When someone shares an idea in a meeting, credit them by name if you build on it. These small practices rebuild trust over time. A Harvard Business Review study found that employees who feel recognized are 2.7 times more likely to be highly engaged.
5. The workload imbalance conflict
What it looks like: Certain team members consistently carry heavier loads than others. High performers attract more work because they’re reliable, while lower performers coast. The overloaded employees burn out or leave, and the cycle intensifies.
Why it persists: Leaders distribute work based on capability and reliability rather than capacity. It feels efficient in the short term — give the important work to people who’ll actually do it well. But it’s a hidden tax on your best people that compounds over time.
The fix — a capacity transparency conversation:
Start with the team: “I want us to get honest about workload distribution. I’m going to ask each of you to list your current projects, estimated hours per week, and which ones you could hand off or share. This isn’t about who’s working hard enough — it’s about making invisible work visible so we can distribute it more fairly.”
Then address the structural issue: stop routing all critical work to the same people. Pair a development-ready team member with each high-stakes project alongside your top performer. This builds conflict resolution capacity across the team rather than concentrating it — and prevents the resentment that builds when overwork becomes someone’s unofficial job description.
The pattern behind all five
Notice what these conflicts have in common: they all persist because something that should be explicit remains implicit. Roles are assumed rather than documented. Feedback is hinted at rather than delivered. Values operate underground rather than in the open. Credit follows visibility rather than contribution. Workload distributes by default rather than by design.
The leader’s job isn’t to eliminate conflict — it’s to make the implicit explicit. Every unresolved conflict represents a conversation that hasn’t happened yet. The scripts above aren’t magic words. They’re structures that make those conversations possible.
Start with the conflict that’s costing you the most energy right now. Use the relevant script this week — not next month, not when the timing feels perfect. The timing for addressing a conflict that’s been festering for months will never feel perfect. What matters is that you begin.