Team conflict rarely looks like conflict at the top of an organization. It looks like polite meetings, slow decisions and the same issue returning every quarter. McKinsey’s research links healthy disagreement, trust and alignment to better team performance, which makes conflict handling a lever to increase team productivity rather than a soft skill. This guide gives CEOs and COOs five practices for turning disagreement into execution, and a way to check that the managers carrying them out can do it.
I. The Meeting Where Everyone Agrees and Nothing Moves
When did your last leadership meeting end in full agreement, and how many of those decisions were still moving a month later?
Most executives know two kinds of difficult meeting. In the first, tension is visible, voices rise and someone leaves irritated. In the second, everyone nods, the chair summarizes, and the real argument happens afterward in corridors and chat threads. The first kind gets attention. The second kind does more damage.
Both are conflict problems. Disagreement is a normal part of teamwork, and a team that never disagrees is usually hiding it. McKinsey’s research on top-team performance makes this point to CEOs directly. A polite discussion about a hard decision often signals a team that does not feel safe enough to debate trade-offs, or is unsure of its role in the decision.
For a leader who wants to increase team productivity, that changes where to look. The problem is not only the shouting match. It is every disagreement that goes underground and resurfaces as delay, rework and a project that stalls at the handoff between two functions. Handling it well starts with treating conflict as an operating capability, not a personality trait.
II. What Unresolved Conflict Costs an Executive Team
A. Quiet Conflict Costs More Than Loud Conflict
Loud conflict is at least visible. SHRM’s 2024 survey found that almost two-thirds of employees had encountered or witnessed incivility in the past month. That is the workforce view. At the executive level the same dynamic is quieter and more expensive, because it hides inside agreement.
McKinsey’s data on top teams shows the stakes. Companies whose top team is aligned and working well together are almost twice as likely to achieve above-median financial performance. The same research finds that top teams are confident about goals, commitment and purpose, and weakest on the behaviors that involve friction: psychological safety, conflict management and feedback. They do well when everyone agrees. They struggle at the moment two people disagree and one of them has to say so.
B. Where the Cost Lands
The cost lands on the work CEOs and COOs care about most. McKinsey’s research on team effectiveness reports that three in four cross-functional teams underperform on key metrics. Cross-functional teams carry transformation programs, product launches and post-acquisition integration. They are also the teams where conflict is hardest to see, because no single manager owns the whole disagreement.
The same research links team behavior to output. Teams that scored above average on trust were 3.3 times more efficient and 5.1 times more likely to produce results than teams with below-average trust. Efficiency here means the team is productive and meets its deadlines, which is the outcome anyone trying to increase team productivity is after.
Trust is built partly in how disagreements get resolved. A team that watches a conflict handled fairly learns to trust the process. A team that watches it ignored learns to stay quiet.
The cost shows up as slipped dates, decisions reopened after they were made, and strong people who stop contributing in meetings. None of it appears on a dashboard labeled conflict.
III. Why Conflict Handling Is Assumed, Not Assured
Organizations promote people for results and then assume they can run a hard conversation. Most leaders have never seen evidence either way. A manager’s ability to hear out two senior people who disagree, find the real issue and land a decision that holds is a capability. Like any capability, it varies widely across a company. And like most capabilities, it is rarely checked.
Most organizations have assessed this at some point: a leadership workshop on difficult conversations, a 360 review, a line on an annual form. Almost none can assure it. Assessment is a photograph. By the time anyone acts on it, the team has changed, the manager has a new remit and the conflict has moved. Assurance is closer to how finance treats its numbers: continuously verified, current, and trusted enough to make decisions on.
That distinction explains why conflict training so often fails to increase team productivity. The workshop is real. The evidence that it changed behavior in a specific manager, in a specific team, six months later is missing. So the CEO or COO keeps hearing the same disagreements surface in different rooms, with no way to tell whether the cause is the people, the structure, or a skill that was assumed and never confirmed.
Capability you can see + a standard to judge it against = disagreements that get resolved instead of recycled.
IV. Five Practices That Increase Team Productivity
These five practices are simple to state and hard to sustain. Each works at the workflow level, which is where a COO can actually install it.
A. Listen to Understand, Not to Reply
Most disagreements escalate because each side prepares a rebuttal while the other speaks. Build one rule into high-stakes meetings: before anyone counters a position, they restate it to the other person’s satisfaction. Ask a clarifying question, paraphrase, and name the concern behind the position. A supply lead who can accurately restate the sales lead’s customer commitment has already removed half the argument. Listening is the cheapest way to increase team productivity, because it costs minutes and prevents weeks of rework.
B. Ask Why Before You Ask Who
Finger-pointing is the fastest route to a stalled decision. When two functions clash over a delivery date, the date is rarely the real issue. One side is protecting a customer promise, the other is protecting quality or cost. Before options are discussed, have each side write its underlying need in one sentence. The group is then solving a shared problem with two constraints instead of ruling on whose fault it is. Moving from who to why is one of the most reliable ways to increase team productivity in cross-functional work.
C. Aim for Solutions That Serve Every Side
Compromise is a negotiation staple for a reason. Ask for several options that address each side’s stated need before anyone argues for a favorite. Be willing to bend on method while holding firm on the outcome. Be honest about the limit, too: not every disagreement has a solution that satisfies everyone. When none exists, the decision owner decides, explains the reasoning in plain terms, and the team commits. A clear decision with visible reasoning serves a team better than a long search for consensus.
D. Set Ground Rules for Debate
Healthy debate and destructive drama differ in rules, not temperament. Agree the rules once, in writing. Critique ideas, not people. One voice at a time. Decisions are recorded with an owner and a date. After a decision is made, remaining disagreement goes to the decision owner directly, not into side conversations. These rules are boring on purpose. They keep the argument about the work, and they let a team disagree hard without damaging trust.
E. Treat Different Perspectives as Working Material
A team with one view of a problem has one view of its risks. McKinsey’s top-team framework counts diverse perspectives among the drivers of team health, alongside clear roles and external orientation. Make that operational. Before a major decision, assign someone to argue the strongest case against it, and invite the person closest to the customer or the shop floor to speak first. Differences of experience then become inputs to the decision instead of sources of friction.
V. Making the Practices Hold Across the Organization
Five good practices in the CEO’s meeting change little if the managers two layers down cannot use them. The job of the CEO or COO is to make that spread deliberate.
Start with where conflict repeats. When the same disagreement keeps returning in different teams, the cause is often structural rather than personal: overlapping roles, unclear decision rights, or capability gaps that nobody has named. Empathy does not fix a role that two people both believe they own. Changing how roles and reporting lines are drawn can remove the source of the conflict, which is the argument behind redesigning org charts to reduce talent risk.
Then look at the roles where conflict handling matters most: cross-functional program leads, site and regional heads, anyone who sits between two functions that want different things. A leader in one of those roles who avoids hard conversations is also a talent risk of the kind CEOs increasingly ask about, because the organization depends on that person’s judgment more than its structure admits.
Finally, check whether the capability exists. Training completion tells you who attended. It does not tell you who can hold the room when two senior people disagree. The leaders who increase team productivity at scale ask for evidence of capability in the roles that carry the most conflict, and they ask for it more than once.
The organizations that handle conflict well are not less argumentative. They found out sooner who could handle the argument.
VI. How PeopleBlox Helps?
Capability Assurance is the discipline of continuously verifying, not just assessing, that your organization has the capabilities its strategy requires. PeopleBlox is built around it.
Leadership Capability Assurance applies that discipline to the people expected to carry your strategy and run its hard moments: the leaders who must resolve disagreements, hold teams together and land decisions that stick. It sits inside the wider discipline of Organizational Capability Assurance, the same verification applied to every critical role, not only the top of the house.
For a CEO or COO, the practical question is where capability is strong and where it is thin. The Capability Command Center gives one view of that across teams and roles. PeopleBlox builds unusually structured, detailed competency frameworks, and leaders judge capability through structured, multi-perspective assessment against a defined standard. The judgment stays human. It becomes comparable across people and roles, and it is revisited over time instead of recalled under pressure.
When a team keeps stalling, that view helps separate three possibilities: a people problem, a structural problem and a capability problem. Each has a different fix, and guessing wrong is expensive. Leaders who can see the difference spend their effort on the right one, which is how an organization can increase team productivity without another round of generic training.
Frequently Asked Questions
1. How do you resolve conflict in a team?
Start by listening until each person can restate the other’s position. Find the underlying need behind each position, generate options that serve both, and agree ground rules for debate. If no shared solution exists, the decision owner decides, explains the reasoning, and the team commits. Record the decision with an owner and a date so it is not reopened.
2. How does team conflict affect productivity?
Unresolved conflict slows decisions, causes rework and pushes strong contributors to stay quiet. McKinsey finds that teams with above-average trust are 3.3 times more efficient than teams with below-average trust, and ignored conflict tends to erode that trust. The cost usually appears as slipped dates and reopened decisions, not as a line item.
3. Is conflict in a team ever healthy?
Yes. McKinsey notes that the best top teams actively embrace healthy conflict and surface uncomfortable truths, while a team that never disagrees may be hiding something. Disagreement about ideas improves decisions. Disagreement that turns personal damages trust. Ground rules that keep debate focused on the work separate the two.
4. What is a manager’s role in resolving team conflict?
A manager should notice conflict early, listen to each side, bring people together around the underlying need, and own the decision when agreement is not possible. The manager also sets the ground rules for debate and follows up afterward. Avoiding the conversation is the failure to watch for, and it signals a capability gap worth addressing.
5. What causes conflict between team members?
Common causes are unclear roles, overlapping decision rights, competing priorities between functions and differing working styles. Many conflicts that look personal are structural, with two people both believing they own the same decision. Fixing role clarity and decision rights often removes the conflict faster than coaching the individuals involved.
6. How can leaders increase team productivity?
Leaders can increase team productivity by removing the friction that slows teams: unresolved disagreements, unclear decision rights and managers who avoid hard conversations. Set ground rules for debate, give every decision a named owner, and check that managers in conflict-heavy roles can handle them. Capability that is verified, not assumed, is what makes the habits stick.
7. What are practical ways to increase team productivity at work?
Five habits help most: listen to understand before responding, ask why before asking who, aim for solutions that serve every side, set written ground rules for debate, and bring different perspectives into decisions early. Each takes minutes to apply in a meeting and prevents the rework that unresolved conflict leaves behind.
read next

Capability Assurance for Leadership and Organizational Readiness: Why Capability Cannot Be Managed in Fragments
