UPI Study › Courses › Principles of Management › Free lessons › Lesson 8.4 Free with a free account
Friction at Work: Navigating Team Conflict and Its Impact on Workflow
Principles of Management · Chapter 8: Team Dynamics: Building, Bonding, and Managing ConflictSection 8.4 · lesson 44 of 11712 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of Principles of Management.
Lesson complete
Earn the 3 college credits for Principles of Management
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: What Leaders Really Do: Purpose and Impact in Organizations →← When Agreement Becomes a Trap: Understanding Groupthink and Its ConsequencesNext lesson: What Leaders Really Do: Purpose and Impact in Organizations →
In this lesson
Which disagreements help, which harm, and what a manager does.
- Distinguish task, process and relationship conflict
- State the conflict-performance evidence carefully
- Explain how task conflict turns personal
- Manage a described team conflict at the team level
Transcript
Everything said in the video, section by section (1,687 words). Read along, or search it.
Team Dynamics: Building, Bonding, and Managing Conflict
Friction at Work: Team Conflict and Workflow
Many people treat any conflict on a team as a sign that something has gone wrong. This section argues that view is mistaken, and also that some conflict really is damaging. We'll separate three types of conflict, and look carefully at what the evidence says about each. Then we'll focus on the moment a useful disagreement turns personal, and how to prevent it. We'll trace what unresolved conflict does to a team's workflow, and how it escalates. And we'll finish with what a manager actually does at the team level. The key idea running through all of it is that not all disagreement is equal. Some of it sharpens a team's thinking. Some of it quietly wrecks the work.
Conflict Reframed
A Normal Product of Interdependence
Conflict is perceived incompatibility between parties. It's a felt sense that what one party wants, believes, or needs stands at odds with what another does. Here's the reframing this section opens with. Conflict is a normal product of interdependence. It is not a sign that a team is failing. Recall the definition of a team from Subchapter eight point one. Interdependent members, working toward a shared goal. Precisely because those members depend on one another, they'll periodically want different things. They'll believe different things about how the shared work should proceed. That's what interdependence produces. So a team with literally zero conflict isn't necessarily working well. It may simply be a team whose members have stopped voicing their genuine differences. We'll come back to that possibility, because it turns out to matter a great deal.
3 Types of Conflict
What, How, and Who You Are
Conflict within a team takes three distinct forms. The distinction matters, because the three have very different effects on performance. Task conflict is disagreement about what should be done. Which approach to take, which priority comes first, which outcome the team should pursue. Process conflict is disagreement about how work should be done, and by whom. It covers method, sequencing, and the division of responsibility. Notice that process conflict isn't about the goal. Members may agree on the goal completely. Relationship conflict is disagreement rooted in interpersonal incompatibility. It's personal friction between members, with little or nothing to do with the task or the process. Keep these three apart in your mind. Most of what follows depends on telling them apart.
The Evidence
Stated Carefully, Type by Type
The evidence on these three types needs to be stated with real precision. Relationship conflict is consistently harmful, to both performance and satisfaction. Across the research, there's little genuine debate on that point. Task conflict is the interesting case. For a long time, it was held to be simply beneficial. The intuition was that healthy disagreement about substance sharpens a team's thinking. The later evidence is considerably more qualified than that early, optimistic view. Task conflict shows benefit at moderate levels, not high ones. It helps on non-routine tasks, where genuine debate about approach has real value. And it helps only where relationship conflict is absent. When the two occur together, task conflict tends to lose whatever benefit it might have carried. Process conflict is generally harmful, and more consistently so than task conflict is helpful. Arguing over how and by whom work gets done eats attention and goodwill, without producing much insight.
Figure 8.4.1
Underperformance at Both Extremes
Figure eight point four point one plots team performance against the overall level of conflict. Performance is low at both extremes, and higher in a moderate range between them. At the low end, conflict is avoided, and important issues go unexamined. At the high end, relationship conflict takes hold, and the workflow breaks down. In the middle sits the moderate range, where there's a qualified benefit. Now the important caution. The curve on its own overstates the finding. This shape describes task conflict specifically, under the conditions we just named. Non-routine work, moderate intensity, and no relationship conflict. It does not describe conflict of every type, at every level, indiscriminately. Relationship conflict, for instance, has no helpful middle range at all.
Table 8.4.1
3 Types, 3 Responses
Table eight point four point one pulls the three types together, with an example and a response for each. Task conflict might be a disagreement over which product feature to prioritize this quarter. Its effect is a qualified benefit, at moderate levels, on non-routine work, without relationship conflict. The manager's response is to structure the debate, and keep it focused on the substantive disagreement. Process conflict might be a disagreement over who should lead a shared deliverable. It's generally harmful, so the manager clarifies roles and process quickly, rather than letting it linger. Relationship conflict might be ongoing personal friction between two members, unrelated to the work itself. It's consistently harmful. The manager addresses it directly and promptly. And critically, the manager doesn't allow it to be absorbed into task discussions, where it does the most damage.
The Conversion Problem
When Disagreement Becomes Personal
The practical heart of this section is what we can call the conversion problem. Task conflict becomes relationship conflict when disagreement is experienced as personal, rather than substantive. One member says, I disagree with your proposed approach. Another member hears, I have a problem with you. The first is a genuine, separable difference of view about the work. The second is an attack. Once that conversion happens, it can't easily be converted back. A disagreement that has become personal carries an emotional residue. Returning to purely substantive discussion doesn't automatically dissolve it, even once the original question is settled. This is why the manager's real job isn't eliminating disagreement. It's keeping the separation between task disagreement and personal friction from collapsing in the first place.
Keeping the Separation
4 Safeguards Against Conversion
Four things keep task disagreement from converting into relationship conflict. The first is norms about disagreement, established early. That connects to the forming stage from Subchapter eight point one. The team gets a shared, pre-agreed way of disagreeing, before any specific disagreement has arisen. Timing is the point. Norms are far easier to set before they're needed than in the middle of a heated moment. The second is focusing on the problem, rather than the person. The discussion is actively framed, and re-framed, around the substantive question, not anyone's judgment or character. The third is explicitly acknowledging shared goals. It reminds members they're on the same side of the outcome, even while they disagree about the path. That weakens the sense of opposition that makes a personal conversion more likely. The fourth is the manager's own modeling. A manager who treats disagreement with colleagues as personal teaches the team, by example, that this is how disagreement works here. And that lesson wins, regardless of what any stated norm claims.
Functional or Dysfunctional
The Distinction Cuts Across the Types
Another useful distinction is between functional and dysfunctional conflict. Functional conflict supports the team's goals. Dysfunctional conflict undermines them. This distinction cuts across the three types, rather than mapping neatly onto them. Task conflict is functional under the qualified conditions we named, and dysfunctional outside them. Relationship conflict is essentially always dysfunctional. But here's the point worth holding onto. Too little conflict is also a problem. This links straight back to Subchapter eight point three, and groupthink. A team that has suppressed all disagreement hasn't reached some ideal, conflict-free state. It has likely converged prematurely, in exactly the way groupthink describes. And in doing so, it lost the moderate task conflict that would have surfaced a genuinely better option.
Workflow and Escalation
What Unresolved Conflict Costs
Unresolved conflict, of any type, damages a team's workflow in ways you can observe. Delay is the first. Decisions stall while the underlying disagreement stays unresolved. Withheld information is the second. Members in conflict become less willing to share what they know. Third, duplicated or abandoned work, because members stop coordinating well enough to avoid it. Fourth, diverted attention. Energy goes into managing, avoiding, or ruminating on the conflict, instead of the task. Conflict escalation describes how a manageable disagreement becomes entrenched. First, an initial, specific disagreement broadens into a wider set of grievances. Then positions harden, and become tied to identity rather than simply a viewpoint. Then other team members get drawn in, and are asked, openly or implicitly, to take a side. Each stage makes resolution harder, and more costly, than it would have been one stage earlier. That's why early intervention beats waiting until a conflict becomes undeniable.
The Manager's Actions
3 Team-Level Moves, and Their Limit
At the team level, three actions belong specifically to the manager. The first is surfacing conflict early. That means naming a brewing disagreement before it escalates, not waiting until it's undeniable. The second is structuring the discussion. A genuine disagreement gets an actual forum, and a process to work through it. Otherwise it plays out across scattered, informal conversations, where nobody can resolve it. The third is deciding when to decide. At some point, debate stops producing new information, and just repeats the same positions. The manager recognizes that point, and closes the discussion with an actual decision. Some conflict genuinely exceeds team-level management. That includes significant escalation, a formal grievance, or a structured negotiation the manager isn't positioned to run. Those call for the conflict resolution approaches of Subchapter twelve point five. Where no internal party can resolve it, they call for the mediation and arbitration methods of Subchapter twelve point six.
Case Vignette
A Disagreement Over Method That Became Personal
Here's a composite case, constructed for instruction. Wren and Devon, two members of a product team at Harborline Manufacturing, disagreed early in a project. The question was which technical approach the team should adopt. At first the disagreement was substantive and specific. Each favored a different method, for stated, defensible reasons. But the team had no norm for handling disagreement. And no manager was framing the discussion around the substance. Over several meetings, their exchanges grew sharper. By the fourth meeting, each was dismissing the other's contributions, even on unrelated topics. Other members had begun quietly aligning with one or the other, instead of engaging with the technical question. The original disagreement was ordinary task conflict, the kind that can carry a qualified benefit. No norms, no focus on the problem, and no reaffirmed shared goal. So it fully converted into relationship conflict. By the time the manager intervened, the conversion was complete. It would have been far easier to prevent than to reverse. That closes Chapter eight. Chapter nine turns to leadership styles, and the influence a leader exercises over teams like these.
About Principles of Management at UPI Study
Principles of Management (Business 101) is a self-paced online course of 117 video lessons in 17 chapters, from the classical schools and the four management functions to leadership, motivation, change, human resources, strategy and ethics. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus Every course with PRO →
Why take it here
Why students take Principles of Management with UPI Study
Where the credit goes
Universities that work with NCCRS
Principles of Management carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About Friction at Work: Navigating Team Conflict and Its Impact on Workflow
What are the three types of team conflict?
Is task conflict good for team performance?
How does task conflict turn into relationship conflict?
How should a manager handle conflict within a team?
About the Principles of Management course
How many college credits is Principles of Management?
How much does Principles of Management cost and what is included?
Which universities accept UPI Study credits?
How long does Principles of Management take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Principles of Management.
117 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →