Groups and Teams

Understanding the concept

A collection of skilled people is not automatically an effective team. Performance depends on how contributions are combined, how disagreements are handled and what members expect from one another. The interdependence of the task determines how much coordination is required.

A team is more than a collection of skilled individuals; its performance depends on how roles, norms, status, and cohesion combine to convert individual ability into coordinated output. When these structural elements are weak or misaligned, even technically strong members can produce mediocre collective results, a gap often explained by social loafing and low collective efficacy.

Roles clarify contributions; norms establish expectations; status influences whose contribution carries weight. Cohesion can support cooperation but may also discourage dissent. Collective efficacy is a shared belief in the team's capability, not evidence that the capability already exists. Social loafing becomes more likely when individual contributions are difficult to identify or members doubt that effort matters. These constructs should be interpreted together rather than treated as isolated targets for a team-building event.

Core components and theoretical lenses

Use the following distinctions to unpack the chapter's central idea. Each identifies a different aspect of the problem; their relationships matter as much as the labels themselves.

1. 01

   Role clarity and role conflict

2. 02

   Group norms (formal and informal)

3. 03

   Status hierarchy within the group

4. 04

   Cohesion (task and social)

5. 05

   Diversity of skills, background, and perspective

6. 06

   Collective efficacy and social loafing

Conceptual constructs

A construct names an idea used to interpret behaviour. It is not directly interchangeable with a survey score or a single incident. In this chapter, the constructs below organize the diagnosis; examine how they could explain the observations before deciding what to change.

• Social loafing
• Collective efficacy
• Cohesion
• Group norms
• Process losses (related)

Observable and measurable indicators

Indicators connect an abstract explanation to something that can be observed. Check the operational definition, reporting period and comparison group. A survey average can conceal differences between teams, and an administrative record can reflect willingness to report as well as underlying behaviour.

• Meeting attendance and participation rates tracked over sprints
• Peer-review scores on individual contribution vs team output
• Defect/rework rate attributable to unclear ownership
• Team cohesion survey (task and social cohesion subscales)
• Ringelmann-style effort audits comparing individual vs group task output

Reading the case evidence

Separate what the case reports from what you infer. A figure can establish the scale of a problem without establishing its cause. Note what information is absent and how that gap affects your confidence in a recommendation.

Decision alternatives and trade-offs

Alternatives represent different priorities and assumptions. The advantages and limitations below are the existing module's analytical prompts. Compare them against the same evidence rather than choosing first and finding a theory afterward.

Evidence-based discussion

In the quality-team case, map handoffs and decision authority before diagnosing a lack of skill. Compare alternatives by the specific coordination problem they resolve. A team charter is useful only if assignments, meetings and follow-through change accordingly. Measure both the quality outcome and the process by which members contribute, including whether expertise from lower-status members reaches the discussion.

Theory-linked interpretation from the module

Frame the answer using social loafing theory (why individual effort dilutes in groups), collective efficacy (belief that the team can succeed together), and group norms/role theory (how explicit structure reduces ambiguity). A strong answer explains the causal mechanism linking the chosen intervention to reduced loafing or increased cohesion, not just that it 'sounds good'.

Your managerial judgement

Which intervention should the plant head implement first to convert individual talent into team performance before the CEO review, and why?

Write a recommendation that identifies a preferred alternative, uses the reported evidence, acknowledges uncertainty and specifies a review point. Another choice can be defensible when its assumptions and trade-offs are made explicit.

Possible consequences

The module offers the following projections for discussion. They depend on implementation and context; they are not guaranteed effects or verified forecasts.

• Short-term: clearer accountability may temporarily slow meetings as roles are documented
• Short-term: quieter members may initially resist increased individual visibility
• Long-term: sustained role clarity can raise collective efficacy and warranty metrics
• Long-term: unresolved loafing risks repeated cross-functional team failures on future projects
• Long-term: how this team is fixed sets a precedent for how other cross-functional initiatives are structured

Reflection questions

1. Why can a team of high performers still underperform as a collective unit?
2. How would you measure whether social loafing, not skill gaps, is the real cause here?
3. What role does status among engineers play in silencing quieter members?
4. Could combining two alternatives (e.g., RACI plus rotated leadership) work better than either alone?

Practice: Know → Analyse → Decide

These are the original module questions. Reading or printing this textbook does not change quiz scores, completion or certificate eligibility.