MGT2382 Week 7 Learning Journal

Chapter 8 — Team Dynamics

Initial Reflection: What Makes a Team Real?

Chapter 8 describes teams as groups of two or more people who interact, influence one another, share accountability for organizational goals, and recognize themselves as a social entity. It examines team effectiveness, task interdependence, team composition, norms, roles, cohesion, trust, mental models, self-directed teams, remote teams, psychological safety, and team decision-making.

My first question is more basic:

When does a collection of people become a real team?

People may work in the same building, wear the same uniform, and report to the same manager without genuinely functioning as a team. They may be performing separate jobs while using the language of teamwork. A company can call employees a “family” or a “team,” but that label means very little if responsibility, information, authority, and accountability are not shared honestly.

The chapter says that team members are mutually accountable. That word mutually matters.

If accountability travels only downward, is it really a team?

If employees are responsible for results but have no meaningful influence over the decisions producing those results, they are not participating in shared accountability. They are absorbing consequences.

This connects directly to a pattern I identified in Standing on the Ledge: conflict often begins when responsibility expands but authority does not. The person closest to the work becomes the shock absorber for decisions made elsewhere. Competence may hide this structural weakness because the capable person continues solving problems until the burden becomes unsustainable.

Chapter 8 therefore raises a question that goes beyond ordinary teamwork:

Can a team be effective if the people carrying the most responsibility possess the least authority?

My answer is that it may appear effective temporarily, but that effectiveness is being subsidized by someone’s additional effort.

The Benefits and Limitations of Teams

Teams can combine knowledge, divide complicated work, coordinate interdependent tasks, and generate better decisions than individuals working alone. Team members may also motivate and monitor one another. However, McShane and Warner identify two significant limitations: process losses and social loafing.

Process losses are the time and resources consumed by maintaining the team itself. Meetings, disagreements, duplicated work, unclear instructions, and attempts to coordinate too many people can take energy away from the actual task.

This makes me question the automatic assumption that every task should be assigned to a team. Some work genuinely requires collaboration. Other work becomes slower because someone decided that collaboration sounds progressive.

A team should not exist merely because management likes the word.

The task should require interdependence. Members should need one another’s knowledge or abilities. Otherwise, the “team” may be little more than several people performing individual work while attending additional meetings.

Who Carries the Wood?

Social loafing occurs when an individual contributes less effort in a group than they would working alone. Research by Karau and Williams found that social loafing is influenced by whether individual contributions can be identified, whether the task feels meaningful, and whether people believe their effort will affect the final result.

My writing on community repeatedly returns to a related question:

Who carries the wood, and who remains when the ashes must be cleaned?

A community is not demonstrated by how many people arrive when the fire is impressive. It is demonstrated by who contributes, respects the boundaries, accepts responsibility, and remains when the unpleasant work begins.

That is social loafing expressed outside the conventional workplace.

Some members enjoy the identity, status, or warmth produced by a group while contributing little to its maintenance. Others quietly perform the invisible work: preparation, emotional support, cleanup, conflict management, scheduling, and problem-solving.

The person doing invisible work may eventually appear resentful or uncooperative. However, the deeper issue may be that the team normalized an unequal distribution of responsibility.

This leads to another question:

Is the apparent “difficult team member” actually the person who has finally stopped compensating for everyone else?

Team Design and the Five Cs

McShane and Warner’s team-effectiveness model considers the organizational environment, team design, and team processes. Teams should be large enough to complete the work but small enough to permit meaningful participation and efficient coordination. Members require both taskwork abilities and teamwork abilities.

The Five Cs of effective teamwork are:

• cooperating
• coordinating
• communicating
• comforting or supporting
• conflict handling

I find the distinction between taskwork and teamwork particularly important. An employee may be technically excellent while damaging the team through poor communication, hostility, withholding information, or refusing to cooperate. The reverse is also possible: someone may be socially pleasant but unable or unwilling to perform the work.

A healthy team needs both.

However, I would question whether the Five Cs receive equal respect in real workplaces. Organizations often reward visible output while treating emotional support, conflict prevention, and informal coordination as secondary activities. Yet those supposedly secondary activities may be what prevents the team from collapsing.

The employee calming disagreements, translating unclear instructions, or helping a struggling coworker may be contributing substantially to performance even though that contribution does not appear in a production report.

The danger is that supportive employees become permanently assigned the role of team stabilizer. Their helpfulness becomes an expectation rather than a contribution.

At what point does cooperation become over-functioning?

When does supporting the team become carrying the team?

Norms, Roles, and the Quiet Rules of a Team

Chapter 8 identifies six central team processes:

1. team development
2. norms
3. roles
4. cohesion
5. trust
6. shared or complementary mental models

Norms are especially interesting because they are often more powerful than formal policies. A handbook may encourage employees to report concerns, while the team’s unwritten norm says, “Do not make the rest of us look bad.”

An organization may officially value initiative, while the real workplace norm punishes anyone who exceeds the informal performance standard.

The textbook’s critical-thinking example involving employees discouraging customer follow-up illustrates this problem: a productive behaviour can be rejected because it makes established members appear lazy.

Norms can support reliability and coordination, but they can also protect mediocrity, silence, and misconduct.

That gives me another question:

Who created the team’s norms, and whom do those norms protect?

A norm is not necessarily healthy merely because everyone follows it.

Roles create a similar problem. Formal roles may be assigned by management, but informal roles emerge through repeated behaviour. One person becomes the fixer. Another becomes the peacekeeper. Someone else becomes the critic, historian, scapegoat, or unofficial leader.

Once a person becomes the fixer, the team may stop fixing anything for itself.

Once someone becomes the peacekeeper, other members may stop managing their own conflicts.

A role that initially develops from competence can become a trap.

Cohesion: Belonging or Conformity?

Team cohesion refers to members’ attraction to the team and motivation to remain part of it. Research generally finds a positive relationship between cohesion and performance, although the strength of that relationship depends partly on how cohesion and performance are measured. A recent meta-analysis examined 195 samples involving more than 12,000 participants and concluded that cohesion remains an important contributor to team performance.

However, cohesion is not automatically ethical or productive.

A highly cohesive group can unite around excellence, service, and mutual support. It can also unite around secrecy, exclusion, resistance to change, or hostility toward outsiders.

Cohesion tells us that the group is bonded. It does not tell us what the group is bonded around.

This connects strongly with questions I have asked through Unplugged Pagan about community, belonging, loyalty, reciprocity, and the difference between stewardship and possession. A place may continue using the language of home or kinship after the relationships supporting those words have changed. A community can remember someone’s labour while forgetting their worth.

The organizational version of that question is:

Can a team continue calling itself cohesive after mutual obligation has disappeared?

Another concern is that cohesion can become conformity. People may remain silent because they fear losing membership, status, friendship, or access to the group.

A team may therefore appear harmonious because nobody feels safe enough to disagree.

That is not cohesion. It is managed silence.

Trust and Reciprocity

Trust is necessary when team members depend on one another and cannot monitor every action. A major meta-analysis involving 112 independent studies and 7,763 teams found a positive relationship between intrateam trust and team performance. Trust was particularly important where team members were highly interdependent and relied on different skills or levels of authority.

Trust is often discussed as though it means believing that other people have good intentions. I think that definition is incomplete.

Trust also depends on predictable behaviour, competence, honesty, and reciprocity.

My writing about frith and gift-bonds repeatedly asks whether loyalty can survive without reciprocity. A group cannot continually demand loyalty from members while treating loyalty as optional for those with authority.

A team that says, “Trust us,” while withholding information is asking for obedience, not trust.

Trust cannot be ordered into existence. It develops when behaviour repeatedly matches promises.

This also means that damaged trust cannot be repaired solely through language. A mission statement cannot repair conduct. The team must see different behaviour over time.

Psychological Safety: What Happens When Someone Says No?

Psychological safety is the shared belief that people can take interpersonal risks—ask questions, acknowledge mistakes, disagree, propose unusual ideas, or report bad news—without being humiliated or punished. McShane and Warner connect psychological safety to effective team decisions and creative work.

Amy Edmondson’s foundational study of 51 work teams found that psychological safety was associated with team learning behaviour. People were more willing to discuss errors, seek feedback, and experiment when they believed interpersonal risk would not bring harmful consequences.

My simplest test for psychological safety comes from a question developed in Unplugged Pagan:

What happens when the answer is no?

A request is genuine only when the person is allowed to decline. When refusal brings exclusion, retaliation, accusations of disloyalty, or punishment, the request was actually a command wearing softer clothing.

The same test applies to workplace teams.

What happens when an employee says:

• I do not understand.
• I made a mistake.
• This deadline is unrealistic.
• I disagree.
• I cannot safely do that.
• This decision is creating a problem.
• I need assistance.
• No.

The answer reveals more about psychological safety than any open-door policy.

A manager may claim that employees are free to speak. The real communication climate is revealed by what happens after someone does.

Self-Directed and Remote Teams

Self-directed teams receive substantial autonomy over how they complete an entire piece of work. They can be effective where tasks are highly interdependent and members possess the skills, information, and authority needed to coordinate their own work.

However, self-direction must not become abandonment.

Management cannot simply remove supervision, provide insufficient resources, and call the result empowerment. Genuine autonomy includes access to information, clear boundaries, adequate training, and real authority.

Remote teams create additional challenges because members operate across distance, time, and sometimes organizational boundaries. McShane and Warner emphasize structure, appropriate technology, communication skills, emotional intelligence, self-leadership, and early opportunities for richer interaction.

The deeper issue is not merely whether people can exchange messages. It is whether they develop shared mental models.

Do team members understand:

• the goal
• each person’s role
• who possesses which information
• what to do when conditions change
• how urgent different messages are
• how disagreement will be addressed

Technology can transmit words. It cannot automatically create shared understanding.

Team Decision-Making

Teams can produce better decisions because they contain more knowledge and perspectives. They can also make worse decisions because of time pressure, evaluation apprehension, conformity, and overconfidence. Chapter 8 recommends psychological safety, checks and balances, manageable team size, and structured idea-generation methods such as brainwriting and nominal group technique.

This connects to my Chapter 7 concern about whether decision-makers are working with accurate and complete information.

A team may possess the necessary information collectively while still making a bad decision because the information never reaches the discussion.

The employee closest to the work may remain silent.

The newest member may assume the experienced people know better.

The person with authority may speak first and unintentionally anchor the discussion.

The group may confuse agreement with accuracy.

Therefore, diversity alone does not improve decisions. The team must have a process that permits diverse information to be expressed and seriously considered.

Final Reflection

Chapter 8 initially appears to be about making teams function better. After examining it more closely, I think it is really about relationships under conditions of interdependence.

Teams require people to depend on one another without surrendering individual responsibility. They require cohesion without enforced conformity, autonomy without abandonment, trust without blindness, conflict without destruction, and leadership without domination.

The chapter also gives organizational language to questions I have already been asking through Standing on the Ledge and Unplugged Pagan:

• Who carries the invisible work?
• Who has responsibility without authority?
• Who is allowed to question the group?
• What happens when someone says no?
• Does loyalty travel in both directions?
• Are team members valued as people or only for what they produce?
• Is the group genuinely cohesive, or has disagreement merely become unsafe?
• Does the team remember the hands that carried the wood after the fire is burning?

My main conclusion is that a team is not defined by proximity, branding, or management language.

A real team exists when people share a purpose, understand their roles, contribute honestly, exchange relevant information, accept mutual accountability, and can raise concerns without being punished.

Anything less may still produce results for a while.

But it may be borrowing those results from someone else’s eventual exhaustion.

References