Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Turn Team Conflict into Creative Tension
Transcript
- Lucas: There's this stat from Google's Project Aristotle that has stuck with me for years. Teams where members felt safe disagreeing openly — they outperformed teams that reported 'no conflict' by a significant margin. Not by a little. By something like a thirty to forty percent lift on key performance metrics. Luna: I've seen that too. But the manager I worked for used to say 'I want everyone to speak their mind' and then visibly flinch when someone actually did. Lucas: Right. And that's the gap we're talking about today. There's a difference between destructive conflict — personality clashes, ego battles, people arguing to win — and creative tension, which is friction around ideas that makes the outcome better. Most managers treat all conflict as bad. But the best managers learn to cultivate the second kind. Luna: So how do you tell them apart in the moment? Lucas: I'd say the cleanest tell is what people focus on. In destructive conflict, people focus on who is right. In creative tension, they focus on what is right. You can hear it in the language. 'Your proposal doesn't work because you ignored the data' — that's personal. Versus 'I'm worried this proposal assumes low churn, but our data shows churn is actually climbing' — that's about the problem. Luna: I had a boss who was incredible at this. She would literally say 'I'm going to be hard on this idea because I believe in us finding the best one.' And it worked. People didn't take it personally. Lucas: That's the classic 'hard on the problem, soft on the person' framework. Ed Catmull, the co-founder of Pixar, wrote about this in his book 'Creativity, Inc.' Pixar's Braintrust meetings were designed specifically to surface raw, honest feedback on films while protecting the filmmaker's dignity. The rule was: you can say anything about the movie, but you can't attack the person. And it produced some of the most successful animated films ever made. Luna: But that's Pixar, a creative company. What about a finance team or a compliance department? Can you really have that kind of debate when the stakes are regulatory? Lucas: I'd argue it's even more important in high-stakes environments. Because if people can't voice concerns about a compliance risk or a flawed model, the cost is real — not just a bruised ego. One of my favorite examples is from Bridgewater Associates, the hedge fund. Ray Dalio's principle of 'radical transparency' meant that every meeting was recorded, and anyone could challenge any decision if they had data. It's extreme. But the point is they built a culture where disagreement was expected, not suppressed. Luna: Okay, but not every manager wants to run their team like a hedge fund. What's a practical first step for someone listening who has a team of, say, eight people and they want to encourage healthier debate? Lucas: I'd start with a pre-mortem. Before a project kicks off, gather the team and ask: 'It's six months from now, and this project failed completely. What went wrong?' That exercise surfaces hidden assumptions and disagreements before anyone is invested in a specific plan. It's low stakes, it's hypothetical, and it gives people permission to disagree without feeling like they're challenging the leader. Luna: I've done that! It's surprisingly effective. People who never speak up in regular meetings suddenly have strong opinions about what could go wrong. Lucas: Exactly. Because the framing is 'help us avoid failure' rather than 'criticize this idea.' The other thing I'd recommend is creating a shared glossary. A lot of team conflict actually comes from people using the same words to mean different things. 'Urgent' means something different to a project manager than to an engineer. 'Done' means different things to a designer and a QA tester. Define those terms together and half the arguments evaporate. Luna: That's so simple. And I've seen teams spend weeks arguing about timelines only to realize they actually agreed on the deadline — they just had different interpretations of what 'final review' meant. Lucas: Right. So the pre-mortem surfaces disagreements, the glossary prevents semantic conflicts, and then you need a process for structuring the debate itself. I use a simple four-step framework. One: state the decision that needs to be made. Two: each person shares their recommendation and the one key reason behind it. Three: the group discusses the risks of each option. Four: the decision-maker — usually the manager — makes the call and explains the rationale. Luna: And step four is crucial. Because if people argue and then the manager makes a decision without explaining why, they feel like their input didn't matter. Lucas: Exactly. The rationale is what closes the loop. You don't have to convince everyone, but they need to understand how their input factored in. That's the difference between a team that feels heard and a team that feels ignored. Luna: What about remote teams? Conflict over Slack or Zoom can escalate faster because you lose tone and body language. I've seen a simple disagreement turn into a week-long passive-aggressive email chain. Lucas: That's a real challenge. In person, you can say something blunt and then soften it with a smile. Over text, the blunt part lands but the smile doesn't. So for async communication, I'd suggest a 'written debate' protocol. When there's a disagreement, each person writes a one-paragraph summary of the other person's position before they respond. Forces empathy and understanding. Then they write their rebuttal. That alone reduces the temperature. Luna: I like that. It's like the 'listening first' principle but in writing. And it gives people time to think rather than react. Lucas: Yeah. And if the debate is happening in a live meeting, especially a video call, I recommend the 'one sentence rule.' Before anyone can respond to a point, they have to summarize it in one sentence to the speaker's satisfaction. It sounds formal, but it prevents the 'I heard you but I'm going to argue against what I think you said' dynamic. Luna: Okay, but there's a scenario I've struggled with as a manager. You have two top performers who just fundamentally disagree on a strategic direction. Both are passionate, both have good arguments. Taking sides feels risky. How do you handle that? Lucas: That's one of the hardest situations. First, don't take sides. Your role is to create a container where both can fully articulate their reasoning. I'd schedule a dedicated meeting — not in the regular status update — and tell them: 'I want to understand both of your positions completely. We're going to spend an hour on this, no decisions made today.' Then you ask questions and synthesize. Often the disagreement is based on different assumptions about the future, and once those assumptions are surfaced, you can test them. Luna: And if after that they still disagree? Lucas: Then you make the call. But you frame it as a decision based on the data available today, and you commit to revisiting it if new information comes in. That way neither person feels their position was dismissed — it was just outweighed by other factors. And you've shown the team that strong disagreement is safe, as long as it's about the work. Luna: Speaking of showing the team — I think a lot of managers worry that if they allow conflict, it'll spiral. They think harmony is the goal. Lucas: And that's the mistake. Psychological safety isn't about being nice. It's about being able to say what you need to say without fear of retaliation. A team that avoids all conflict is a team that makes avoidable mistakes. The most innovative teams — the ones Project Aristotle found — they had high psychological safety and high standards. They held each other accountable, and they argued about the work constantly. But they respected each other. Luna: So the manager's job is to set the norm that respectful disagreement is not just allowed — it's expected. Lucas: Right. And you model it. When someone challenges your idea, you say 'That's a good point, let me think about that' instead of getting defensive. That single behavior does more to create a healthy debate culture than any policy you could write. Luna: And I think that's also where the listener support angle comes in — not to pivot too hard, but it's funny. We talk about creating cultures where people feel heard, and this show itself only exists because listeners tell us it helps them navigate exactly these situations. Lucas: Yeah, that's true. And we've kept it ad-free from the start because we wanted it to be a genuine resource, not a commercial break every ten minutes. So if you've found value in episodes like this — maybe you've used the pre-mortem or the one-sentence rule — and you want to make sure we keep going, listener support is what makes that possible. You can find us at buy me a coffee dot com slash fexingo. Luna: It's a small way to keep the podcast independent. And every bit genuinely helps us keep producing for the audience. Lucas: Alright. So back to that top performer conflict — one more tool I want to mention. It's called 'steel-manning.' Instead of attacking the weakest version of someone's argument — which is straw-manning — you try to build the strongest version of their argument. You say 'Let me see if I can state your case even better than you did.' It disarms defensiveness and shows you're genuinely trying to understand. Luna: That's advanced. I've seen it work, but it takes practice. And it requires the other person to be acting in good faith. Lucas: Absolutely. And if someone is not acting in good faith — if they're just trying to win or undermine — that's a different problem that conflict management alone won't fix. But for the vast majority of healthy teams, these techniques shift the energy from 'us versus each other' to 'all of us versus the problem.' Luna: And I think that's the headline. Creative tension is a team sport. The manager is the coach, not the referee. Lucas: Yeah. And the best coaches don't stop the game every time there's a hard tackle — they make sure everyone gets up, shakes hands, and keeps playing hard. That's the culture worth building.