Poor Performance

Introduction

Poor performance is one of the most uncomfortable causes of team conflict. Not because it is uncommon, it is in fact one of the most predictable sources of friction in teams, but because of how it interacts with everything else. Performance gaps do not just affect the person whose performance is below expectation. They affect everyone around them. They affect the colleagues who pick up the slack. They affect the leader who has to manage around the gap. They affect the people who depend on outputs that are not being produced. They affect the team's culture, which absorbs the unspoken message about what is being tolerated. They affect the trust between team members, which erodes when some people consistently deliver and others consistently do not. And the conflicts that emerge from poor performance are often not openly framed as conflicts about performance. They appear as something else. Communication problems. Personality clashes. Workload disputes. Resentment. Avoidance. Friction that no one can quite trace to its source, even when the source has been operating for months.

This indirection is one of the most common features of performance-related conflict in teams. The actual issue, which is that one or more team members are not performing at the level the team needs, often gets buried beneath a series of secondary conflicts that look like they are about other things. Two team members start clashing. Someone becomes harder to work with. Meetings get tense. People start complaining about workload. Other people start withdrawing. And by the time the leader notices that something is wrong, the team is in a state of compounded friction that has multiple visible sources and one invisible underlying cause. Even when the leader recognizes the performance issue at the center, addressing it has become more difficult because so much secondary damage has accumulated. The team has reorganized itself around the gap. The roles, expectations, and relationships have all shifted. And resolving the underlying performance issue now requires not just addressing the performance itself but also unwinding the patterns the team has developed in response to it.

There is another layer of difficulty. Poor performance is one of the topics most leaders find hardest to engage with directly. It involves judgments about people that feel personal. It involves potential consequences that feel high-stakes. It involves conversations that most leaders have not had enough practice with to feel comfortable conducting. And it involves emotional dynamics, including embarrassment, defensiveness, and sometimes shame, that are uncomfortable for everyone involved. For all of these reasons, leaders often delay engaging with performance issues longer than they should. They hope the situation will improve on its own. They tell themselves the team can absorb it. They focus on the secondary conflicts because those feel more manageable. And while they delay, the situation deepens. The performance gap continues. The compensation patterns calcify. The resentment grows. And the eventual intervention, when it comes, has to address a much larger and more complex situation than would have been required if the leader had engaged earlier.

This article explores poor performance as a cause of team conflict. What it really means in the context of team conflict, beyond the more familiar performance management lens. How performance gaps produce conflict in teams, often through indirect mechanisms. What patterns leaders fall into when they avoid engaging with performance issues, and what those patterns cost their teams. How to distinguish performance-driven conflict from other causes that might look similar. How to address performance-related conflict, both by engaging with the performance issue directly and by helping the team work through the secondary conflicts that have accumulated. And how to build conditions in a team that reduce the likelihood that performance gaps become entrenched sources of conflict in the first place. By the end of this article, you should be able to look at a team conflict and recognize when poor performance is the underlying driver, even when it has been masked by secondary friction. You should understand the unique dynamics of performance-related conflict and what they require of leaders. And you should carry forward the disposition to engage with performance issues earlier and more directly, because doing so prevents far more conflict than the difficult conversation itself produces.

Simple Meaning: What Is Poor Performance as a Cause of Conflict?

Poor performance as a cause of conflict refers to the friction that arises in a team when one or more members consistently produce work, behavior, or outcomes that fall significantly below what the team or organization needs, and that gap creates burdens, frustrations, or interpersonal tensions among the people affected by it. It is not about occasional mistakes or normal variation in output. It is about sustained patterns of falling short that the team has to absorb in some way. The conflict that emerges may be between the underperformer and their colleagues, between colleagues who disagree about how to handle the situation, between the team and its leader who is seen as not addressing the issue, or within the underperformer themselves as they navigate the situation. What makes it a cause of conflict, rather than just a performance problem, is the way the gap creates ripples that affect the relationships, expectations, and dynamics of the team as a whole.

Poor performance is one of the most consequential causes of conflict in teams, and one of the most often masked. The actual issue, which is that one or more team members are not meeting expectations, is uncomfortable enough to discuss that it often goes unaddressed, while the secondary conflicts it produces become the visible surface of the situation. Colleagues who have to pick up slack become frustrated, sometimes with the underperformer directly, sometimes with each other, sometimes with the leader, sometimes with the team as a whole. The underperformer themselves may feel exposed, defensive, or disengaged, depending on how the gap is being experienced and whether they recognize it. The leader, who is often most aware of the situation, may struggle with whether and how to address it, and the delay itself becomes part of what the team is conflicting about. And the team's culture absorbs the unspoken message about what is being tolerated, which shapes how everyone calibrates their own effort, their own honesty, and their own engagement. Performance-related conflict in teams is rarely just about performance. It is about what the performance gap reveals: the team's expectations, the leader's willingness to engage, the team members' relationships with each other, the conditions under which work is happening, and the larger culture that determines what is welcomed and what is avoided. Engaging with performance-related conflict well requires the leader to address all of these layers, not just the surface performance issue. It requires the leader to recognize when secondary conflicts are masking an underlying performance problem. It requires the leader to engage with the performance issue directly, even when the engagement is uncomfortable. It requires the leader to support the team in working through the patterns that have developed in response to the gap. And it requires the leader to build conditions in which performance issues can be addressed earlier and more directly in the future, so that the next performance gap does not have to produce months of compounded friction before it gets addressed. Done well, engaging with performance-related conflict can strengthen teams substantially, because it demonstrates that the team's standards are real, that the leader will act on what is needed, and that performance is something the team can discuss honestly. Done poorly, or not done at all, it can erode teams over years, as the unaddressed performance gap continues to produce conflicts that the team has no way to resolve at their source.

Poor performance as a cause of conflict can be understood through four essential dimensions:

How Performance Gaps Produce Conflict in Teams

Performance gaps produce conflict through several distinct mechanisms. Understanding these mechanisms helps leaders recognize the patterns and intervene at the right point.

Mechanism 1: Compensation Burden

When one team member is not delivering at expected level, others often pick up the slack. They take on extra work. They cover deliverables. They review and fix work that should have been delivered at standard. Over time, the compensation burden becomes resentment. The colleagues doing the extra work feel that they are being treated unfairly while the underperformer is not. This resentment is one of the most common sources of performance-related team conflict, and it is often expressed not as direct frustration with the underperformer but as friction between the colleagues who are absorbing the burden.

Mechanism 2: Output Dependencies

When team members depend on each other's outputs, performance gaps in one person cascade to others. Deadlines slip. Quality issues propagate. Other people's work is delayed or has to be redone. The dependencies create direct friction between the underperformer and the people whose work is affected. This friction is often substantively justified, but it can also become personal in ways that make resolution harder.

Mechanism 3: Standard Erosion

When poor performance is tolerated, the team's effective standards drop, regardless of what the stated standards are. Other team members notice what is being accepted. They calibrate their own effort accordingly. The team's overall performance drifts down. And conflicts emerge between those who continue to hold themselves to higher standards and those who have adjusted to the new effective baseline. The conflicts here are often substantive, but they can also be cultural, with team members differing on what level of effort is reasonable to expect.

Mechanism 4: Trust Erosion

Repeated underperformance erodes trust. Other team members stop relying on the underperformer's commitments. They double-check work that should not need double-checking. They route around the person when they can. They become guarded in interactions. The reduced trust changes the texture of every working relationship the underperformer has on the team, and the resulting interactions feel like conflict even when nothing dramatic has happened.

Mechanism 5: Leader Avoidance Visibility

When the leader does not address known performance issues, the team notices. They interpret the silence as endorsement, indifference, or weakness. The conflicts that emerge from this interpretation can be between the team and the leader directly, or they can be between team members who differ in how they interpret the leader's silence. Some team members become disengaged. Some become resentful of the leader. Some become resentful of colleagues who do not seem to care about the situation. The leader's avoidance becomes its own source of friction.

Mechanism 6: Identity and Status Pressure

For the underperformer themselves, the gap produces internal pressure that often spills into external behavior. They may become defensive, exaggerating their contributions or minimizing the gap. They may withdraw, reducing their visibility to limit how much the gap is seen. They may attack, deflecting attention by criticizing others. They may overcompensate, working harder in areas where they feel competent while continuing to underperform in the areas that matter. Each of these responses can produce its own conflicts with colleagues, even when the colleagues are not directly engaging with the performance issue.

Mechanism 7: Misaligned Expectations

Sometimes what looks like underperformance is actually misalignment about what good performance is. The underperformer believes they are performing well by their understanding of the role. Others believe they are underperforming by a different understanding. The conflict is not really about performance. It is about the gap in shared understanding of what the role requires. And until the expectations are clarified, the conflict cannot be resolved by addressing performance alone.

Mechanism 8: Comparison Dynamics

Performance gaps create comparisons that produce their own friction. Other team members may feel they should be recognized for their stronger performance. They may feel that recognition is being distributed unfairly. They may feel that promotions, opportunities, or rewards are being affected by the underperformer's continued presence. The conflict here is not just about the performance itself but about the implicit comparisons that the situation creates.

How Performance-Related Conflict Gets Masked

One of the most important skills a leader can develop is recognizing when a visible team conflict has an underlying performance driver that is not being named. The masking happens in recognizable patterns.

The "Communication Problem" Mask

Colleagues describe the situation as a communication breakdown. "We are not on the same page." "There are misunderstandings." "We need better alignment." Beneath the communication framing is often a performance issue: outputs that did not meet what was needed, commitments that were not honored, or work that did not match what was discussed. The framing as a communication problem allows the conversation to happen without naming performance directly.

The "Personality Clash" Mask

Two team members appear to be in a personality clash. Their interactions are tense. They struggle to collaborate. Beneath the personality framing is often a performance issue: one team member is consistently picking up the burden of the other's gap, and the resulting resentment is being expressed as personality conflict. The underlying cause is performance, but the visible cause is the relationship.

The "Workload" Mask

The team complains about workload. People feel overworked. Resentment builds about how the workload is distributed. Beneath the workload framing is often a performance issue: the workload is heavier on some people because they are absorbing what others are not delivering. The conversation about workload allows the substantive issue to be discussed without naming the underperformer.

The "Process" Mask

The team proposes new processes to address the friction. Better checklists. Clearer handoffs. More structured reviews. Beneath the process framing is often a performance issue: the process improvements are an attempt to compensate for performance that cannot be relied on, without naming the underlying gap. The processes may help marginally, but they do not address the actual cause.

The "Reorganization" Mask

Someone proposes that the team or roles be restructured. Beneath the reorganization framing is often a performance issue: the restructuring is an attempt to route around the underperformer, often by giving someone else the work they are not doing well, without addressing the performance issue directly. The reorganization can produce short-term relief but tends to create new problems while leaving the underlying issue intact.

The "Team Culture" Mask

The team discusses concerns about culture, engagement, or morale. Beneath the culture framing is often a performance issue: the eroding morale is a consequence of unaddressed performance problems, not a primary issue in its own right. Working on culture without addressing performance produces frustration because the actual driver continues to operate.

The "Leader Problem" Mask

The team's frustration with unaddressed performance issues sometimes manifests as criticism of the leader. The leader is described as disengaged, weak, or unsupportive. Some of this criticism may be deserved, especially if the leader has been avoiding the performance issue. But sometimes the criticism is the only way the team can express its frustration about a performance issue that no one is naming directly.

Why Leaders Avoid Engaging With Performance Issues

Understanding why leaders avoid performance issues is part of being able to engage with them more directly. The avoidance is rarely about not caring. It is usually about specific patterns and pressures that make engagement difficult.

None of these reasons is illegitimate. Leaders who recognize them in themselves are not failures. They are leaders who can begin to address the patterns that have been producing avoidance. The avoidance is changeable. It changes through specific work on the skills, documentation, framing, and engagement patterns that make performance conversations possible.

What Avoidance Costs the Team

Leaders who avoid performance issues often underestimate the cost of the avoidance. The costs are real and they compound over time.

• The performance gap continues. The team continues to operate below what it could.
• The compensation burden grows. Those absorbing the work become depleted and resentful.
• Trust erodes. Both trust in the underperformer and trust in the leader.
• Standards drift downward. The team adjusts to the new effective baseline, which is lower than the stated one.
• Strong performers disengage. The ones with the most options start to consider whether they want to stay.
• The underperformer themselves loses. Without honest feedback, they cannot improve. They may be staying in a role where they will eventually fail in worse ways.
• The team's capacity for honest engagement weakens. The team learns that hard truths are not engaged with, and this learning shapes everything else.
• Future performance issues become harder to address. The team's expectation of avoidance gets reinforced.
• The leader loses credibility. The team sees that the leader is not addressing what is visible to everyone.
• The eventual intervention is larger. When the issue finally has to be addressed, there is much more damage to unwind.

None of these costs is visible at the moment of avoidance. They accumulate quietly. And by the time they become visible, they often require significant work to address. Recognizing these costs is one of the most important motivators for earlier engagement with performance issues.

How to Engage With Performance-Related Conflict Well

Engaging with performance-related conflict requires working on multiple levels: the underlying performance issue, the secondary conflicts it has produced, and the team patterns that have developed in response.

Step 1: Diagnose Honestly

Before acting, determine whether what you are seeing is actually a performance issue or something else. Is the performance below standard? What is the standard? What specifically is below it? What are the contributing factors? Are there things that look like underperformance but are actually misalignment, missing support, or circumstances that need to be addressed first? Honest diagnosis is what prevents the wrong intervention.

Step 2: Address the Performance Issue Directly

Once you are clear that there is a real performance issue, engage with it directly with the person involved. Use the disciplines from the chapter on giving constructive feedback and the chapter on performance discussions. Be specific. Be honest. Be supportive. Treat the conversation as the beginning of work, not an end. Create the structure for change to be possible: clear expectations, support, milestones, indicators of progress.

Step 3: Acknowledge the Secondary Conflicts

The performance gap has produced secondary effects in the team. Even as you address the underlying issue, acknowledge that those effects are real. Talk with the colleagues who have been absorbing the burden. Recognize the strain they have been carrying. Be honest that you are now engaging with the underlying issue. Help them understand what they can expect.

Step 4: Restore the Team's Standards

When standards have drifted, restoring them requires explicit work. Name what the team's standards are. Reaffirm them with the whole team. Be consistent in how you apply them. Recognize that restoring standards is itself a process that takes time, and the team has to see consistency before they will trust the restoration.

Step 5: Rebuild Trust

Performance-related conflict erodes trust on multiple sides. Rebuilding it requires sustained engagement. The underperformer needs to see that improvement is possible and supported. The colleagues need to see that the leader is engaging with the issue. The team as a whole needs to see that the leader is willing to do the work that performance requires. Trust rebuilds through consistency over time, not through a single conversation.

Step 6: Address Conditions That Allowed the Gap to Persist

Often the performance gap was allowed to persist because of conditions in the team or leadership that did not surface or address it earlier. Unclear expectations. Limited feedback. Absence of regular performance check-ins. Avoidance patterns in the leader. Examine these conditions and address them so that the next performance issue gets engaged with earlier.

Step 7: Be Prepared for the Possibility That Improvement Will Not Happen

Despite good engagement, support, and the team member's effort, some performance issues do not resolve. The role may not be the right fit. The gap may be larger than what can be closed with reasonable support. The team member may not engage with the work. Be prepared, from the start of engagement, that the outcome may involve a role change, a move, or separation. This preparation is not pessimism. It is honesty about the range of possible outcomes. And it allows you to engage with the situation seriously rather than with false expectations.

Building Conditions That Surface Performance Issues Earlier

Beyond addressing specific performance-related conflicts, leaders can build conditions in their teams that surface performance issues earlier, when they are easier to address.

• Clear expectations. Every role has explicit expectations for what good performance looks like, and those expectations are communicated to the people in the roles.
• Regular feedback. Performance feedback flows continuously throughout the year, not just at formal review cycles.
• Honest performance conversations. Performance discussions are real conversations about real patterns, not formalities filled with vague affirmations.
• Visible standards. The team's standards are visible to everyone, and people understand how their work is being evaluated against them.
• Early intervention. When performance starts to slip, the leader engages early rather than waiting to see if it improves.
• Support systems. When performance issues are identified, there are real support systems available, including coaching, training, and mentoring.
• Cultural norms about performance. The team has a culture in which performance can be discussed honestly, in which feedback is normal, and in which engagement with development is expected.
• Leader modeling. The leader engages with their own performance honestly, including being open to feedback about their own work.
• Documented patterns. Performance patterns are documented over time, providing the basis for ongoing conversation.
• Distributed responsibility. The team has shared responsibility for performance, including peer feedback and mutual accountability, not just leader-to-team-member assessment.

These conditions do not eliminate performance issues. People still go through difficult periods. Standards still drift in some areas. But teams operating with these conditions tend to surface performance issues earlier, address them more directly, and resolve them with less secondary conflict.

When Poor Performance Is Not What It Appears

Not every situation that looks like poor performance actually is. Recognizing the alternatives helps leaders avoid mislabeling situations and applying the wrong interventions.

Misalignment of Expectations

The team member may be performing well by their understanding of the role, while not meeting what the leader or organization actually needs. The issue is not performance but alignment. Addressing it requires clarifying expectations, not coaching performance.

Missing Support or Resources

The team member may be unable to perform because they lack the support, resources, training, or information they need. The issue is not the person but the conditions. Addressing it requires changing the conditions, not changing the person.

Wrong Role Fit

The team member may be capable but in a role that does not match their strengths. The issue is not capability but fit. Addressing it may require a move, not a performance improvement plan.

Personal Circumstances

The team member may be navigating personal circumstances that are temporarily affecting their performance. The issue is not a sustained pattern but a period of difficulty. Addressing it requires support and flexibility, not the same response as a sustained gap.

Leadership Issue

The team member may be performing below capability because of how they are being led: unclear direction, lack of feedback, missing opportunities to grow, demoralizing dynamics. The issue is not the team member but the leadership. Addressing it requires the leader to examine their own contribution before treating the situation as a performance gap.

Systemic Issues

The team member may be operating in conditions that no one could perform in: impossible workloads, conflicting priorities, broken systems, dysfunctional teams. The issue is not individual performance but the system. Addressing it requires changing the system, not managing the individual.

Honest diagnosis is what allows leaders to distinguish these situations from genuine performance issues. And honest diagnosis often reveals that what looked like performance was actually something else, requiring different intervention.

Practical Workplace Scenario

Scenario

A team lead named Sneha had been managing a team of eight analysts for two years. Over the past four months, the team had become increasingly tense. Workload complaints had been rising. Two of the senior analysts were clearly frustrated with each other. Morale was dropping. Sneha had been treating the situation as a complex set of communication and collaboration issues. She had introduced new processes, scheduled team-building activities, and had several conversations about workload distribution. None of it had helped. The friction continued and seemed to be worsening. One day, in a one-on-one with one of her senior analysts, the analyst said quietly: "Sneha, I need to tell you something I have been holding back. The reason the team is struggling is not communication. It is that Kunal has not been carrying his weight for months, and the rest of us have been picking it up. I have not said anything because I did not want to seem like I was complaining about a colleague. But this is not sustainable."

Approach 1: Continued Avoidance (What Could Have Happened)

Sneha could have heard the feedback and continued to treat the situation as a team dynamics issue. She could have committed to more process work, more team building, more discussions about collaboration. She could have hesitated to engage with Kunal directly because she liked him, because she was uncertain about whether his performance was really the issue, because she did not feel prepared to have a difficult performance conversation. And the situation would have continued to deteriorate. The senior analyst who had finally spoken up would have concluded that her feedback had been useless. Other team members would have continued to absorb the burden. One or two of the strong performers would have eventually started looking elsewhere. And by the time Sneha was forced to engage with Kunal's performance, the team would have been substantially damaged.

Approach 2: Engaging Directly With the Performance Issue (What Actually Happened)

Sneha took the feedback seriously. She spent the next week looking carefully at Kunal's recent work, talking with the other team members in one-on-ones, and being honest with herself about what she had been seeing. What she saw was uncomfortable to acknowledge. Kunal's outputs had been declining for months. Quality issues had been increasing. Deadlines had been missed. And other team members had been quietly absorbing the work. She had been aware of some of this but had been telling herself that it was minor, that the team was working through normal variation, that Kunal was going through a hard time and would bounce back. She had been avoiding the conversation.

She scheduled a real conversation with Kunal. She prepared carefully. She used the disciplines from her training in performance discussions and constructive feedback. She brought specific examples. She framed the conversation as engagement with a pattern she had been seeing, not as a verdict. She acknowledged her own delay in raising it. She invited his perspective. And what she learned was complex. Kunal had been struggling with a health issue for the past year that he had not shared with her. He had been hiding it because he was worried about what would happen if it was known. His work had been suffering as a result, but he had been trying to compensate by staying quiet and hoping no one noticed. The performance gap was real. But the cause was not what Sneha had assumed.

They had a real conversation. Sneha was honest about what she had been seeing and the impact on the team. Kunal was honest about what had been going on for him. Together they built a plan. Kunal would work with HR to get the support he needed for his health. His workload would be adjusted for a defined period. He would meet with Sneha weekly to track progress on both his health and his work. And Sneha would be honest with the team about the fact that she was engaging with the situation, without disclosing the personal details.

Sneha then had follow-up conversations with the other team members. She acknowledged that she had been slow to engage with what they had been carrying. She thanked the senior analyst who had finally raised it. She shared what she could about how the situation was being addressed. She reaffirmed the team's standards. And she committed to closer engagement with performance going forward.

Result

Over the next four months, the team's dynamics shifted substantially. Kunal began to recover, both in his health and in his work. The other team members' frustration eased as they saw the situation being engaged with seriously. Morale recovered. The workload patterns rebalanced. And the senior analyst who had first raised the issue told Sneha later: "What changed everything was that you engaged with it directly. I had thought you were not seeing it. When you did, it was clear that you took it seriously. That has changed how I think about working here." Sneha carried into the rest of her leadership the recognition that performance-related conflict requires engagement with the performance issue at the center, even when that engagement is uncomfortable, and that secondary interventions on communication, process, or team building cannot substitute for engagement at the root.

Learning

The difference between the two approaches was not Sneha's intent. In both versions she cared about the team. The difference was her willingness to engage with the performance issue directly, even when the engagement was difficult. The avoidance version would have allowed the situation to deteriorate. The engagement version produced real change. And the deepest insight was that what looked like a complex team dynamics issue had, at its center, a performance gap that had not been engaged with. Engaging with the gap, with both honesty and care, addressed not just the underlying issue but also the secondary conflicts that had been masking it. That is what understanding performance-related conflict well makes possible. The willingness to engage with the issue at the center, even when it is uncomfortable, because doing so prevents far more conflict than the difficult conversation produces.

Poor Performance Checklist

Self-Reflection Questions

Use these questions to think about your own engagement with performance-related conflict in your team.

1. What performance issues in my team am I currently aware of but not actively engaging with?
2. What is my default pattern when I notice underperformance? Engagement, avoidance, hope, delegation?
3. What secondary conflicts in my team might have performance issues at their underlying source that I have not yet identified?
4. What have I been telling myself about why a performance issue does not need to be engaged with right now?
5. What costs has the avoidance of performance issues been producing in my team? Compensation burden? Trust erosion? Standard drift?
6. If a senior team member came to me to share that someone on the team had been carrying the weight of a colleague's gap, how would I respond?
7. How well are the conditions in my team set up to surface performance issues earlier? Clear expectations? Regular feedback? Honest performance conversations?
8. What pattern in my own leadership may be contributing to performance issues being slow to surface?
9. When I think about engaging with a performance issue that has been unaddressed for months, what specifically am I most concerned about? What would help me move forward?
10. If I imagined a team in which performance issues were engaged with directly and early, what would be different about how we work together?

Key Takeaways

• Poor performance is one of the most consequential causes of conflict in teams and one of the most often masked. The actual performance issue frequently goes unaddressed while the secondary conflicts it produces become the visible surface of the situation.
• Performance-related conflict has four essential dimensions: the performance gap itself, the ripple effects that produce friction in the team, the masking that hides the underlying cause, and the avoidance pattern that often delays engagement.
• Performance gaps produce conflict through specific mechanisms: compensation burden, output dependencies, standard erosion, trust erosion, leader avoidance visibility, identity and status pressure, misaligned expectations, and comparison dynamics. Each mechanism produces friction in characteristic ways.
• Performance issues often appear in masked forms: as communication problems, personality clashes, workload disputes, process gaps, reorganization needs, culture concerns, or criticism of the leader. Recognizing the masking is what allows the underlying issue to be addressed.
• Leaders avoid engaging with performance issues for many reasons: hope it will improve, discomfort with difficult conversations, lack of documentation, concern about damaging the relationship, belief that the team can absorb it, sympathy for personal circumstances, uncertainty about standards, fairness concerns, HR process anxiety, and the hope that someone else will address it.
• The costs of avoidance are real and compounding: the gap continues, the compensation burden grows, trust erodes, standards drift, strong performers disengage, the underperformer loses opportunity for honest feedback, the team's capacity for honest engagement weakens, future performance issues become harder to address, the leader loses credibility, and the eventual intervention becomes larger.
• Engaging with performance-related conflict well requires multiple levels of work: diagnosing honestly, addressing the performance issue directly, acknowledging secondary conflicts, restoring standards, rebuilding trust, addressing conditions that allowed the gap to persist, and being prepared for the range of possible outcomes including the possibility that improvement may not happen.
• Building conditions that surface performance issues earlier prevents many performance-related conflicts. Clear expectations, regular feedback, honest performance conversations, visible standards, early intervention, support systems, cultural norms about performance, leader modeling, documented patterns, and distributed responsibility all contribute.
• Not every situation that looks like poor performance actually is. Misalignment of expectations, missing support or resources, wrong role fit, personal circumstances, leadership issues, and systemic issues can all look like performance gaps but require different interventions. Honest diagnosis is what prevents the wrong response.
• The leaders who engage with performance-related conflict well do not eliminate performance issues. Issues still arise. But they engage with them earlier, more directly, and with more care, which prevents the compounded secondary conflicts that unaddressed performance issues produce. That early, direct, caring engagement is one of the most consequential leadership practices in working with teams over time.
• The willingness to engage with a performance issue, even when uncomfortable, is one of the most important things a leader can offer their team. It demonstrates that the standards are real, that the leader will act, and that performance is something the team can discuss honestly. The team's capacity for honest engagement with everything else depends, in part, on how the leader engages with performance.

Conclusion

Poor performance is one of the most consequential causes of conflict in teams, and one of the most uncomfortable to engage with directly. The discomfort produces avoidance. The avoidance produces compounded secondary conflicts that mask the underlying issue. And the masking allows the situation to deteriorate while the visible friction grows. Breaking this cycle requires leaders to engage with performance issues earlier, more directly, and with the willingness to do difficult work in service of the team as a whole. It is not glamorous. It is not comfortable. But it is one of the most consequential practices a leader can develop in the work of building healthy teams.

A leader who understands performance-related conflict well brings a different orientation to the friction that arises in their team. They look beneath visible conflicts for underlying performance drivers. They diagnose honestly whether what they are seeing is genuine performance or something else. They engage with performance issues earlier rather than waiting to see if they improve. They use the disciplines from the chapters on constructive feedback and performance discussions to make the engagement productive. They acknowledge the secondary conflicts that the gap has produced. They restore standards that have drifted. They rebuild trust that has eroded. They address conditions that allowed the gap to persist. And they build the conditions in their team that surface future performance issues earlier, when they are easier to address.

The most important lesson of this article is this: Poor performance is a cause of team conflict, but it is also a cause that is frequently masked by the secondary conflicts it produces. Leaders who recognize the masking, and who engage with the underlying performance issue directly, prevent far more conflict than the difficult conversation itself produces. The avoidance feels protective in the moment. It is not. It allows the situation to deepen, the secondary friction to compound, and the eventual intervention to require much more work than would have been needed if the engagement had happened earlier. Engage earlier. Engage directly. Engage with care, but also with honesty. Use the disciplines you have developed in the work on feedback and performance discussions. Address the conditions that allowed the gap to persist. Acknowledge the secondary effects on the team. Restore standards that have drifted. Rebuild trust through consistent action over time. And recognize that engaging with performance issues is one of the most consequential things a leader does, because it demonstrates what the team can expect, what the standards really are, and what the leader's relationship with honest engagement actually looks like. Your willingness to engage with performance, even when uncomfortable, is one of the foundations on which the team's capacity for honest engagement with everything else is built. When you engage, the team learns that honest engagement is possible and supported. When you avoid, the team learns that the topics that most need engagement get avoided. The leader's pattern shapes the team's pattern, and the team's pattern shapes its capacity to do the work it has been formed to do. Build the pattern of early, direct, caring engagement with performance. Build it by engaging with the performance issues currently in front of you, with the disciplines and care this article and this chapter and earlier chapters have tried to support. Build it by examining your own avoidance patterns honestly and addressing what has been producing them. Build it by creating the conditions in your team that surface performance issues earlier, when they can be addressed before they have produced months of compounded friction. And let your engagement with performance-related conflict, over years, become one of the quiet, consequential ways you build a team in which honest engagement with what is hard becomes one of the foundations of how you all work together. That is what this article has tried to support. That is what understanding poor performance as a cause of conflict makes possible. And that is one of the most important practices in the work of leading teams through the inevitable friction that performance gaps produce, conflict by conflict, year by year, throughout the long arc of your leadership career.