UPI Study › Courses › Principles of Management › Free lessons › Lesson 8.2 Free with a free account
Stronger Together: Team-Building Strategies That Enhance Group Cohesion
Principles of Management · Chapter 8: Team Dynamics: Building, Bonding, and Managing ConflictSection 8.2 · lesson 42 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: When Agreement Becomes a Trap: Understanding Groupthink and Its Consequences →← How Teams Come Together: Tuckman's Five Stages of Group DevelopmentNext lesson: When Agreement Becomes a Trap: Understanding Groupthink and Its Consequences →
In this lesson
What cohesion is, what it does, and how to strengthen it.
- Define group cohesion and explain what produces it
- State the cohesion-performance relationship carefully
- Match each team-building intervention to a diagnosis
- Judge an intervention by the symptom it targeted
Transcript
Everything said in the video, section by section (1,579 words). Read along, or search it.
Team Dynamics: Building, Bonding, and Managing Conflict
Stronger Together: Team-Building That Builds Cohesion
It's tempting to assume a close-knit team is always a better team. This section tests that belief carefully. We'll define cohesion, separate its two components, and look at what builds it. We'll state the link between cohesion and performance honestly, including when cohesion makes things worse. Then we'll treat team building as a diagnosed intervention, matched to a specific problem. And we'll finish with how to tell whether an intervention actually worked.
Defining Cohesion
2 Components That Don't Always Travel Together
Group cohesion is the degree to which members are attracted to the group, and motivated to remain in it. It has two distinct components. Task cohesion is shared commitment to the group's task and goals. Members are bound together by wanting the same work outcome. Social cohesion is mutual liking and attachment among members as people, independent of the task itself. The distinction matters, because the two don't always travel together. And importantly, task cohesion relates to performance more reliably than social cohesion does. A team can like one another warmly as people, while sharing little real commitment to a common outcome. That social warmth doesn't translate reliably into better task performance, the way genuine task cohesion does.
What Builds Cohesion
6 Reliable Factors
Several factors reliably build cohesion. The first is shared goals that members genuinely hold in common, rather than goals merely assigned from above. The second is interaction and time together. They build familiarity. People who rarely interact have little basis for feeling bound to one another as a group. The third is success. A group that achieves something together develops a shared sense of collective competence. The fourth is group size, which affects cohesion inversely past a certain point. In a larger group, it's harder for every member to interact meaningfully with every other member. The fifth is entry difficulty, meaning how hard it was to become a member. People tend to value membership more when it was harder to obtain. The sixth is external competition or threat, which unites members against a common outside pressure. Virtual and distributed teams face a specific challenge here. Interaction and time together happen less naturally when a team isn't co-located. So building cohesion takes more deliberate, scheduled effort, to make up for the incidental contact a co-located team gets for free.
Stated Carefully
Cohesion and Performance
The link between cohesion and performance has to be stated carefully, not assumed. The two are genuinely related. But the direction runs, at least in part, from performance to cohesion. A team that performs well together tends to become more cohesive because of that shared success. Here's the finding that matters most in practice. A cohesive team with norms against productivity performs worse than a non-cohesive one. Cohesion doesn't automatically produce good performance. It amplifies whatever the group's norms actually are. Those norms might favor high output, or something else entirely, like protecting a comfortable pace of work. This connects directly to the bank wiring room findings from Subchapter four point two. There, a highly cohesive work group had developed informal norms restricting output below what members could produce. And cohesion made those norms more effective at holding output down, not less.
Figure 8.2.1
4 Teams, 2 Kinds of Cohesion
Figure eight point two point one places four teams at a fictional firm, Harborline Manufacturing, on two axes. Task cohesion runs along the bottom. Social cohesion runs up the side. Team A is high on both, and gets a strong result. Team D is low on both, and gets a weak result. No surprises there. The two teams worth studying are B and C. Team B is high on task cohesion, but low on social cohesion. It still performs strongly. Team C is high on social cohesion, but low on task cohesion. It functions more like a social club than a productive team. That contrast is the clearest evidence for why task cohesion is the component that actually predicts performance.
High Cohesion's Costs
Not Costless, Even When It Helps
High cohesion isn't costless, even when it does support performance. The most consequential cost is pressure toward conformity. A highly cohesive group's desire to stay united can suppress the very disagreement a good decision sometimes needs. Subchapter eight point three develops that dynamic fully, as groupthink. The second cost is resistance to new members. A cohesive group is invested in its existing relationships. That can make a newcomer's entry, and the regression from Subchapter eight point one, harder than in a less cohesive group. The third cost is hostility toward other groups. Strong internal identification sharpens the boundary between the group and every group it is not. That echoes the silo effect from Subchapter seven point four, a structural consequence of departmentalization.
Table 8.2.1
Team Building Is a Diagnosed Intervention
Team building should be a diagnosed intervention, aimed at a specific problem. It shouldn't be a generic event, held because a team seems to need something. There are four intervention targets, and each has its own diagnostic symptom. Goal setting targets a team that's unclear, or in disagreement, about what it's actually trying to achieve. The fix is a facilitated session that sets a shared, specific objective. Its effect can show up almost immediately. Role clarification targets duplicated work, dropped work, or confusion over who owns what. Responsibility charting or explicit role definition fixes it, often in one focused session. Interpersonal process targets low trust, poor communication, or unresolved tension. Subchapter eight point four develops that kind of conflict. The fix is structured work on how members interact. It's slow, because trust and communication patterns change gradually. Problem solving targets a team that struggles specifically with how it decides, or works through difficult tasks. Decision-making or problem-solving training helps, at a moderate pace, because new methods take practice to become habits.
Responsibility Charting
The Highest-Yield, Lowest-Cost Intervention
Responsibility charting is a structured method for mapping roles, task by task. For each task, it records who is responsible for doing the work. It records who must be consulted before a decision. And who must simply be informed after the fact. And it records who holds final approval authority. This section identifies it as the highest-yield, lowest-cost intervention of the four. It needs no specialized facilitation expertise. It produces an immediately usable artifact the team can keep referring back to. And it directly resolves the duplicated-or-dropped-work symptom. That symptom also makes it easy to tell when charting is needed.
Explicit Norms
Set the Rules Before They Set Themselves
Team building can also mean establishing norms explicitly. Subchapter eight point one described how norms usually form unstated. The alternative is to set some on purpose. Two kinds are particularly worth setting deliberately. Norms about how disagreement is handled, and norms about how concerns are raised. These are exactly the norms most likely to form badly, and least visibly, if left to emerge on their own. Consider a team that never discusses how it wants to handle disagreement. It will likely default to whatever pattern the loudest, or most senior, voice happens to establish informally. Nobody chose that norm. But it governs the team all the same.
Psychological Safety
The Condition Underneath Learning
Psychological safety is the shared belief that raising a concern, a question, or a mistake will not be punished. It was introduced in Subchapter six point seven, on organizational learning. It's the condition underneath a team's capacity for genuine learning, and honest reporting. Here's what the evidence actually supports. Research associates psychological safety with better team learning behavior, and more candid internal reporting. But as with most organizational behavior research, much of that evidence is correlational. It doesn't establish a strictly proven causal mechanism for every claim. Even so, it remains one of the better-supported constructs in this area. And its relevance to team building is direct. A team lacking psychological safety will resist several of these interventions, especially interpersonal process work. Those interventions ask members to raise exactly the kind of concern, the kind psychological safety makes safe to raise.
Matching and Measuring
Use the Right Fix, Then Check the Right Symptom
Two practical rules follow from treating team building as a diagnosis. First, a social event does not fix a structural team problem. Unclear roles, a genuine goal disagreement, or an unresolved conflict won't be fixed by an afternoon together outside work. That's true however pleasant the afternoon is. A social event can build social cohesion, and that has its own modest value. But it does nothing for a diagnosed problem in goals, roles, interpersonal process, or problem-solving method. Second, measure an intervention against the specific symptom it targeted. That's the evaluation discipline Subchapter six point four set out for planned change. Judge role clarification by whether duplicated and dropped work actually declined, not by whether people enjoyed the session. Judge goal setting by whether disagreement about the team's objective genuinely resolved. Measuring general satisfaction instead risks concluding an intervention worked, when it fixed nothing.
Case Vignette
A Pizza Lunch That Fixed Nothing
Here is a composite case, constructed for instruction. A product team at Harborline Manufacturing had been missing internal deadlines for months. At the point of handoff, members kept discovering work that each had assumed belonged to someone else. That work had never been done by anyone. Sana, the team's manager, concluded the team needed to bond more. She organized a team lunch, hoping a relaxed, informal afternoon would improve how the team worked. The lunch was genuinely enjoyable, and members said they appreciated the gesture. The following month, deadlines were missed at the same rate, for the identical reason. No one had ever mapped, task by task, which team member owned which piece of work. Sana had diagnosed a social problem, and intervened with a social solution. But the observable symptom, dropped work reaching handoff before anyone noticed, pointed clearly to role clarification. A responsibility chart would have addressed the problem directly. A pizza lunch, however pleasant, addressed nothing the team was struggling with.
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 Stronger Together: Team-Building Strategies That Enhance Group Cohesion
What is the difference between task cohesion and social cohesion?
Does group cohesion improve team performance?
How do you choose the right team-building intervention?
What is responsibility charting?
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 →