# Managing Team Conflict and Performance

> Chapter 6 of the Courseiva PMI-PMP curriculum — https://courseiva.com/learn/pmi-pmp/managing-team-conflict-and-performance

**Official objective:** 1.5 — Manage team conflict, performance, and continuous improvement.

## Introduction

Managing team conflict and performance is one of the most underrated skills a project manager can master because even a perfectly planned project can fail if the team is fighting or disengaged. For the PMP exam, this concept tests whether you know how to diagnose the root cause of a disagreement and then choose the right leadership response—not just keep the peace. You will be asked to identify the situation and apply the matching conflict-resolution technique or performance-improvement action from the PMBOK guide.

## The Kitchen Brigade Analogy

When a head chef doesn't clarify who is responsible for the grill versus the garnish station, the kitchen quickly falls into chaos because orders get backed up and dishes go out wrong. That conflict between cooks over overlapping duties leads directly to a performance drop: wait times increase, plates are returned, and the whole team's morale suffers. Just like in a professional kitchen, a project team needs clear assignments, a defined process for resolving disagreements, and a system for giving honest feedback without blaming. The head chef holds a daily "briefing" where each cook confirms their station's prep status and flags any shortages—this is the project manager's stand-up meeting. When the sous chef notices the salad station is falling behind, she doesn't shout; she reassigns a prep cook temporarily and checks in after thirty minutes. That is the project manager using situational leadership and collaborative problem-solving to address both the conflict (who owns the bottleneck) and the performance (getting orders out on time). Just like a kitchen that runs smoothly during the Saturday dinner rush because everyone knows their role and how to handle a fire, a well-managed project team handles conflict as a routine part of delivery, not a emergency.

## Core explanation

Managing team conflict and performance is the systematic process a project manager uses to identify interpersonal disagreements, address their root causes, and then help team members work together more effectively while also tracking and improving individual and group productivity. The PMP exam treats this as a core skill because research shows that unresolved conflict is one of the top three causes of project failure.

When two team members disagree about a technical approach, that is a conflict. But not all conflict is bad. Constructive conflict — where people argue about ideas, not personalities — can lead to better solutions. Destructive conflict — personal attacks, blame, or refusal to collaborate — damages trust and slows delivery. Your job as a project manager is to distinguish between the two and act accordingly.

The PMBOK guide (the Project Management Institute's official book of best practices) outlines five common conflict-resolution techniques. You need to memorise these for the exam:

- Withdrawing / Avoiding: The project manager stays out of the conflict entirely, hoping it will resolve itself. This works only for trivial disagreements that don't affect the project.
- Smoothing / Accommodating: Emphasising areas of agreement while downplaying disagreement. Useful to maintain harmony temporarily but doesn't fix the root cause.
- Compromising: Each party gives up something to reach a middle ground. Quick but often leaves both sides partly dissatisfied.
- Forcing: One person imposes their solution using authority. Rarely used because it breeds resentment.
- Collaborating / Problem-solving: The ideal approach. Both sides work together to find a solution that meets everyone's underlying needs. Takes more time but produces the strongest commitment.

The exam expects you to choose "collaborating" or "problem-solving" as the preferred technique whenever the question describes a situation where the conflict is substantive (about the work) and there is time to discuss it.

Performance management is the second half of this objective. It means setting clear expectations, monitoring work quality and speed, giving regular feedback, and taking corrective action when someone underperforms. The exam uses a model called the "Tuckman ladder" — Forming, Storming, Norming, Performing, and Adjourning — to describe how teams develop. Conflict peaks during the "Storming" phase, and your job is to help the team move into "Norming" (where ground rules are accepted) and then "Performing" (where the team runs on its own).

A key tool for performance is the "team charter" — a document the team creates together at the start of a project. It lists ground rules for communication, decision-making, meeting etiquette, and how to handle disagreements. When you have a team charter, you can refer back to it during a conflict instead of making up rules on the spot.

For continuous improvement, the exam introduces "lessons learned" — formal sessions at the end of each project phase (or at the end of the project) where the team discusses what went well, what went wrong, and what should change next time. You also use "retrospectives" (common in agile frameworks) which are shorter, held more frequently, and focus on small process adjustments.

The mistake beginners make is thinking the project manager must solve every conflict personally. In reality, you act as a facilitator: you bring the parties together, ensure everyone speaks, and help them find their own resolution. Only escalate to a sponsor or senior manager if the conflict involves ethical violations or is blocking critical decisions.

## Real-world context

An IT project manager named Priya is leading a team building a customer portal for a bank. During a sprint review, a developer named Raj says the front-end designer, Lena, keeps adding features that weren't approved. Lena says Raj is too rigid and is ignoring user feedback. The team is stuck.

Priya does not take sides. She schedules a thirty-minute meeting with just Raj and Lena, using the "collaborating" technique. First, she asks each person to describe the problem from their perspective while the other listens without interrupting. Raj says he is worried about the sprint deadline because each unapproved feature takes two extra days to integrate. Lena says the design team's user-testing report recommended those changes.

Priya then asks them to restate each other's concerns to confirm understanding. She says, "Raj, can you tell Lena what you heard her say?" After that, she asks, "What is the underlying need for each of you?" Raj needs to hit the deadline; Lena needs the product to meet user-testing thresholds. Priya helps them brainstorm a compromise: they will merge only two of the four unapproved features into this sprint, and the other two will go into the next sprint after formal approval from the product owner. Both agree.

Priya also uses this moment to improve future performance. She updates the team's working agreement: all feature requests must go through the product owner before any code changes are made. In the next retrospective, the team discusses this process and decides to add a daily fifteen-minute "design sync" so developers and designers can flag conflicts early.

Priya tracks individual performance using velocity — a measure of how many story points the team completes per sprint. She notices that one junior developer, Mei, has consistently low output. Instead of assuming laziness, she has a private chat and discovers that Mei is spending three hours a day fixing merge conflicts because she does not understand the branch strategy. Priya pairs Mei with a senior developer for two days to learn the workflow. After that, Mei's velocity doubles.

At the end of the project, Priya runs a lessons-learned session. The team writes down that the design sync should become permanent, that the working agreement should include a clear escalation path for unapproved features, and that Mei's mentoring model should be repeated for future new hires. These notes go into the organisation's project repository for the next team to reference.

## Exam focus

The PMP exam will test this objective — 1.5 — primarily through situational questions. You will be given a short paragraph describing a team dynamic, and you must select the best response from four options. The exam loves to trap you into picking "forcing" or "avoiding" because those seem fast. The correct answer is almost always "collaborating" or "problem-solving" when the conflict is about the work and time allows.

Here are the exact concepts you need to master:

- The five conflict-resolution techniques from PMBOK: withdrawing, smoothing, compromising, forcing, collaborating. Memorise the order of preference: collaborating is best, then compromising, then smoothing. Withdrawing and forcing are last resort.
- Tuckman ladder phases: recognise that conflict is normal in Storming. Do not take it personally. Help the team reach Norming.
- The difference between conflict of interest (personal gain) and substantive conflict (disagreement about the work). The exam will ask you to identify which one is happening.
- The team charter: know that it is created by the team, not imposed by the PM. It contains ground rules for communication and conflict resolution.
- Performance management tools: velocity, burn-down charts, and the team performance assessment. The exam might ask what metric to use to track progress.
- Continuous improvement methods: retrospective (agile) and lessons learned (predictive). Know that retrospectives happen on a regular cadence, while lessons learned happen at phase or project end.

Common traps:

- Trap 1: The question says the project is behind schedule and two team members are arguing. The trap answer is "forcing the project manager's decision" because it saves time. The correct answer is "meet with both parties to understand the root cause and find a collaborative solution."
- Trap 2: The question says a team member is consistently underperforming. The trap answer is "replace them immediately." The correct answer is first have a private conversation to understand the reason, then offer coaching or training.
- Trap 3: The question describes a minor personality clash. The trap answer is "escalate to the sponsor." The correct answer is "use smoothing to maintain harmony while focusing on project goals."

Key definitions to memorise for the exam:
- Conflict resolution: the process of addressing disagreements using one of the five techniques.
- Team charter: a document that establishes team values, agreements, and ground rules.
- Retrospective: a regular meeting to inspect the team's process and make adjustments.
- Lessons learned: a formal record of knowledge gained during the project for future benefit.
- Velocity: the amount of work a team completes in a fixed time period (used in agile).
- Tuckman ladder: a model describing the stages of team development.

## Step by step

1. **Identify the Conflict Type** — First, determine whether the disagreement is substantive (about the work) or personal (about egos). Substantive conflict can be productive if addressed. Personal conflict needs immediate intervention to prevent toxicity.
2. **Choose the Resolution Technique** — Based on the situation, select one of the five techniques: collaborate if time allows, compromise if a quick decision is needed, smooth if harmony is temporarily more important, or force only as a last resort.
3. **Facilitate a Structured Conversation** — Bring the conflicting parties together. Let each person speak without interruption. Ask them to restate the other's perspective. Then guide them toward a mutually acceptable solution without imposing your own.
4. **Update the Team Charter or Working Agreements** — After resolving the conflict, document any new ground rules or process changes that emerged. This prevents the same conflict from recurring and helps the team mature into the Norming phase.
5. **Monitor Performance and Provide Feedback** — After the conflict is resolved, continue to observe the team's interactions and individual contributions. Give timely, specific feedback — both positive and constructive — to reinforce good behaviours and address slippage.
6. **Conduct a Retrospective or Lessons Learned Session** — At the end of the iteration or project, hold a structured review where the team reflects on what worked, what didn't, and what to change. Capture these insights for future projects to enable continuous improvement.

## Comparisons

### Collaborating (Problem-Solving) vs Compromising

**Collaborating (Problem-Solving):**
- Seeks a win-win outcome satisfying all underlying needs
- Takes more time and requires open discussion
- Produces highest team commitment and long-term solution

**Compromising:**
- Each party gives up something to reach a middle ground
- Faster than collaborating but leaves both sides partially dissatisfied
- Used when time is limited or collaboration is not possible

### Retrospective vs Lessons Learned

**Retrospective:**
- Held frequently (e.g., every sprint)
- Focuses on process improvements for the immediate team
- Informal, short meetings (typically 1-2 hours)

**Lessons Learned:**
- Held at the end of a project phase or project
- Focuses on capturing knowledge for the entire organisation
- Formal, documented session with stakeholders

### Team Charter vs Project Charter

**Team Charter:**
- Created by the team members themselves
- Sets ground rules for communication, meetings, and behaviour
- Not a formal project document; it is more like a social contract

**Project Charter:**
- Created by the project manager and sponsor
- Authorises the project and defines high-level scope and objectives
- A formal document that initiates the project

### Forcing (Conflict Technique) vs Collaborating (Conflict Technique)

**Forcing (Conflict Technique):**
- One person imposes a solution using authority or power
- Creates resentment and damages team morale
- Use only for urgent decisions or ethical violations

**Collaborating (Conflict Technique):**
- Both parties work together to find a mutually agreeable solution
- Builds trust and long-term team cohesion
- Preferred technique when time and willingness exist

## Diagram

_A flowchart showing the steps from conflict identification through resolution, team charter updates, and into the performing phase with continuous improvement._

```mermaid
flowchart TD
    A[Conflict Arises] --> B{Is it substantive or personal?}
    B -->|Substantive| C[Collaborate / Problem-Solve]
    B -->|Personal| D[Use Smoothing or Compromising]
    C --> E[Reach Mutual Agreement]
    D --> F[Reduce Tension, Then Collaborate]
    E --> G[Update Team Charter]
    F --> G
    G --> H[Team Moves to Norming
(agreed processes)]
    H --> I[Performing Phase:
High Productivity]
    I --> J[Retrospective
(Continuous Improvement)]
```

## Common misconceptions

- **Misconception:** The project manager should always resolve every conflict personally to show authority. **Reality:** The project manager's role is to facilitate resolution, not impose it. Collaborative problem-solving where the parties themselves find a solution leads to better buy-in and long-term team health. (New managers often confuse authority with leadership. They think stepping in and deciding makes them look strong, but it actually undermines team ownership and creates dependency.)
- **Misconception:** If a team is in the 'Storming' phase, the project manager has failed to lead properly. **Reality:** Storming is a natural and expected phase of team development. Every team goes through it. The project manager's job is to guide them through it, not prevent it. (Beginners see conflict as a personal failure instead of a predictable stage. They panic and try to skip it, which often makes the storm last longer.)
- **Misconception:** Compromising is the best conflict-resolution technique because everyone gives something up. **Reality:** Compromising is a fallback, not the preferred technique. Collaborating is better because it seeks a win-win solution that satisfies both parties' underlying needs. Compromising leaves both sides partly dissatisfied. (People misunderstand 'compromise' as a positive word. In project management, it is considered a moderate approach used when time is limited, not the ideal.)
- **Misconception:** Performance issues should always be documented immediately in a formal warning. **Reality:** The first step should always be a private, supportive conversation to understand the root cause. Underperformance is often caused by unclear expectations, lack of training, or personal challenges, not laziness. (Many people come from industries where poor performance is handled punitively. The PMI approach prioritises coaching and empathy first, which feels unfamiliar to those with a disciplinary mindset.)

## Key takeaways

- The preferred conflict-resolution technique in the PMBOK is collaborating / problem-solving, which seeks a win-win outcome by addressing underlying needs.
- Team development follows the Tuckman ladder: Forming, Storming, Norming, Performing, Adjourning — conflict is normal and expected during Storming.
- A team charter is created by the team, not the project manager, and contains ground rules for communication and conflict resolution.
- If a team member is underperforming, the first action is a private conversation to understand the cause, not a formal warning or replacement.
- Retrospectives occur on a regular cadence (e.g., every sprint) while lessons learned happen at phase or project end.
- The project manager should facilitate conflict resolution, not impose a solution, because team ownership leads to better long-term outcomes.

## FAQ

**What is the difference between conflict resolution and conflict management in PMP?**

Conflict resolution refers to the specific techniques (like collaborating, compromising, forcing) used to end a particular disagreement. Conflict management is the broader, ongoing process of anticipating, preventing, and handling conflicts across the project lifecycle.

**Should I always choose 'collaborating' on the PMP exam?**

Almost always. When the question describes a substantive conflict where the parties are willing to talk, 'collaborating' (also called 'problem-solving') is the preferred PMBOK technique. Avoid choosing it only if the question says time is extremely limited or the issue is trivial.

**What is the team charter and do I need one for every project?**

The team charter is a document that the team creates together that lists ground rules for communication, meeting behaviour, decision-making, and conflict resolution. The PMBOK recommends one for every project, and the exam expects you to know it is created by the team, not imposed by the PM.

**How do I handle a team member who is underperforming without demotivating them?**

Have a private, empathetic conversation first. Ask open-ended questions to understand if the issue is skill-related, motivational, or external. Offer coaching, training, or pair them with a senior team member. Only escalate to formal measures if there is no improvement after reasonable support.

**What is the Tuckman ladder and why does it matter for the PMP exam?**

The Tuckman ladder describes five stages of team development: Forming, Storming, Norming, Performing, and Adjourning. The exam tests whether you recognise that conflict peaks during Storming and that your role is to guide the team through it, not avoid it.

**What is the difference between a retrospective and lessons learned?**

A retrospective is a short, frequent meeting (often at the end of each sprint in agile) where the team focuses on process improvements. Lessons learned is a formal, often longer session held at the end of a project phase or the entire project, and the output is stored in the organisation's knowledge base.

## Check your understanding

1. **A project manager notices two developers are arguing about which programming language to use for a new feature. The deadline is two weeks away. What is the best conflict-resolution technique to apply?**

   Answer: Collaborating / problem-solving, because the conflict is substantive (about the work) and there is enough time to discuss the options and find a solution that satisfies both developers' technical concerns.

2. **What is the primary purpose of a team charter?**

   Answer: The team charter establishes ground rules for communication, meeting etiquette, and conflict resolution that the team agrees to follow, helping the team move through the Tuckman stages more quickly.

3. **During which Tuckman stage does conflict typically peak, and what should the project manager do?**

   Answer: Conflict peaks during the Storming stage. The project manager should facilitate open communication, help the team agree on ground rules, and guide them toward the Norming stage.

4. **A team member has been consistently missing deadlines and delivering low-quality work. What is the FIRST action the project manager should take?**

   Answer: Have a private, empathetic conversation with the team member to understand the root cause — whether it is a skill gap, unclear expectations, or personal issues — before deciding on coaching or other corrective actions.

5. **What is the key difference between a retrospective and lessons learned?**

   Answer: A retrospective is a short, frequent meeting focused on process improvement for the team (used in agile), while lessons learned is a formal session at the end of a phase or project that captures knowledge for the organisation.

---

Interactive version with quiz and diagrams: https://courseiva.com/learn/pmi-pmp/managing-team-conflict-and-performance