- Open Works
- Posts
- š¤ Open Works #018 How to Fix Feuding Teams
š¤ Open Works #018 How to Fix Feuding Teams
Every edition we solve a people and culture problem, crowd-sourced from the Open Org community.

Welcome to Open Works. Every edition we solve a āpeople and cultureā problem crowd-sourced from the Open Org Community of 380+ Startup and Scale-up People Leaders.
š This Weekās People Problem
"Sales and Marketing are at war. Meetings feel toxic, and collaboration is non-existent. Where do I even start?"

People Leaders, after observing the current state of ācollaborationā between Sales and Marketing.
š¤ Our Take on How You Solve It
š TL;DR
If your teams are clashing, you need to:
1ļøā£ Acknowledge the tension.
2ļøā£ Find the root cause.
3ļøā£ Work with the leaders to co-create the fix.
Letās break it down step by step. š
šØ Step 1: Acknowledge the Problem
When tensions between teams boil over, itās rarely a new issue. Your job is to bring it into the open and get everyone aligned that itās a problem worth solving.
How to Spot and Address the Tension
Individual complaints: Team members vent about āthe other sideā during 1:1s.
Leadership discussions: The friction makes its way to your leadership team meetings.
Survey/pulse data: Feedback or pulse surveys reveal frustration between teams.
Personal observations: Meetings devolve into blame games or passive aggression.
Wherever the signal is coming from, start by addressing it directly with the leaders involved. Quick calls or 1:1s work best. Your goal is simple šļø
šÆ Agreement that this is a problem, and itās one worth fixing.

I think so too.
š± Step 2: Find the Root Cause
Acknowledgment is step one; now, itās time to dig into whatās really going on.
š” Common Root Causes:
Misaligned incentives: Teams are rewarded for competing, not collaborating.
Leadership dynamics: The leaders themselves arenāt alignedāor worse, theyāre fighting.
Culture drift: Different norms and values are clashing.
The A**hole: One or two individuals are creating drama for everyone else.
How to Get to the Bottom of It
1:1 conversations: Speak with folks on the teams beforehand to pick up on dynamics you might not see in group settings.
Team workshops: Run separate sessions with each team (without leaders present if you have to) to surface honest perspectives. Go for an open and frank conversation, framing what youāve observed, the impact and inviting the team to share their perspective on what is at the root of the issue.
Anonymous mechanism: Additionally, give people a chance to share what they might not feel safe saying aloud.
š£ļø Step 3: Facilitate āHonesty Dayā
Once youāve uncovered the root cause, itās time to bring the leaders together for an āHonesty Day.ā
Whatās Honesty Day?
Itās a facilitated session with the leaders of the conflicting teams to confront the root cause and align on the fix. This is where you get to the heart of the matter and co-create a solution. Not going to lie, this can get pretty spicy so coffee up.
How It Works:
1ļøā£ Share the findings: Start with a clear, neutral summary of the problems both teams identified, best done as a pre-read async.
2ļøā£ Dig into the root cause: Use a structured discussion to explore whatās really behind the frictionāwhether itās goals, incentives, or personal dynamics. 5 Whys or Fishbones work well here.
3ļøā£ Co-create solutions: Best ideas to address the root cause. Focus on:
4ļøā£ Agree on next steps: Dot vote priorities, agree owners and set a review date.
š¤ļø From Honesty to Action
To avoid the āchat zoneā trapāwhere discussions happen, but no action follows....
Use transparent comms as a lever for accountability
Communicate the solve: Have the leaders jointly share the outcome with their teams. Transparency + Togetherness = the stuff dreams are made of.
Involve the teams: Co-create any new processes, shared goals, or working agreements and agree a simple measure of success. Go for simple and plain english e.g: āweāll know things are better if we see xyzā .
Check back in: After 4-12 weeks, run a retrospective to assess whether what got changed made a difference.
ā Key Outcomes
Youāll have:
Alignment from leaders and teams on the existence of the problem.
A deep understanding of whatās causing the conflict.
A co-created solution with buy-in from both teams.
A framework for measuring progress and iterating on the fix.

You bossing it, as per.
šļø Good reads relating to this problemā¦
š¤ Want to Share Your Messiest āPeople Problemā?
Weāre here for the gnarliest challenges youāve got. Hit reply to this email, and let us know whatās keeping you up at night.
š¤ John & Adam

This doesnāt have to be you. Problem shared = problem halved š
š¤ Are You Part Of The Open Org Community Yet?
Well goodness friend, you should be! š
Join 380+ startup and scale-up People & Talent leaders in Slack for exclusive access to twice-monthly live events (roundtables and guest firesides), quarterly hackathons, and direct support from Adam and me.
With š§ & š„
John & Adam
šļø Got a friend whoād love this newsletter? Forward it there way so they donāt miss out, and make my day whilst youāre at it! š
Reply