Unit III — Group Dynamics
17. Groups and Teams
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.
- Role clarity and role conflict
- Group norms (formal and informal)
- Status hierarchy within the group
- Cohesion (task and social)
- Diversity of skills, background, and perspective
- Collective efficacy and social loafing
- 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
Suvidha Auto Components, a Pune-based tier-1 auto parts manufacturer with 1,400 employees, formed a 9-member cross-functional quality team (design, production, QA, and supplier-quality engineers) to cut warranty returns by 30% within two quarters. Each member is individually rated as a strong performer, yet after three months the team has missed two milestones and warranty returns have fallen only 6%. Meeting minutes show the same three engineers doing most of the talking while others stay silent or arrive late. The QA head suspects members are relying on each other, assuming someone else will chase the root-cause analysis. The plant head must decide how to fix team functioning before the CEO reviews progress next month.
Target warranty reduction
30% in 2 quarters
Actual reduction after 3 months
6%
Team size
9 members, 5 functions
Meeting attendance rate
62% average
Participation concentration
3 of 9 members generate 80% of discussion
Individual performance ratings
7 of 9 rated 'exceeds expectations' individually
ARedefine roles and accountability charts (RACI)
Introduce a RACI matrix for every root-cause task so each member has a named, trackable deliverable instead of shared ambiguous ownership.
BRun a cohesion-building offsite with norm-setting exercise
Facilitate a one-day session where the team co-creates explicit ground rules (meeting conduct, escalation, deadlines) and does trust-building activities.
CIntroduce smaller sub-teams with individual KPIs feeding a shared metric
Split the 9-member team into three 3-person pods, each owning a warranty defect category, reporting weekly to the full group.
DReplace dominant members and rotate leadership
Rotate the team-lead role monthly among members and formally coach the three dominant engineers to create space for others.
ARedefine roles and accountability charts (RACI)
Strengths
- Directly counters social loafing by removing anonymity of effort
- Creates measurable individual accountability within a team structure
Risks
- Risk of over-engineering process and slowing responsiveness
- May reduce spontaneous collaboration if roles become too rigid
BRun a cohesion-building offsite with norm-setting exercise
Strengths
- Builds shared norms members feel ownership over, increasing compliance
- Improves social cohesion which can support long-term collaboration
Risks
- One-off events often fade without follow-up reinforcement
- Does not address the structural cause of unequal participation
CIntroduce smaller sub-teams with individual KPIs feeding a shared metric
Strengths
- Smaller units raise perceived individual impact and reduce loafing
- Enables faster, more focused root-cause cycles per defect category
Risks
- Risk of losing cross-functional integration and shared mental model
- Coordination overhead between pods if categories overlap
DReplace dominant members and rotate leadership
Strengths
- Distributes status and voice more evenly, surfacing quieter expertise
- Builds leadership capability across the team
Risks
- Frequent leadership change can cause continuity and accountability gaps
- May be perceived as punitive by high-performing engineers
Which intervention should the plant head implement first to convert individual talent into team performance before the CEO review, and why?
Introduce a RACI matrix for every root-cause task so each member has a named, trackable deliverable instead of shared ambiguous ownership.
Strengths: Directly counters social loafing by removing anonymity of effort; Creates measurable individual accountability within a team structure. Risks: Risk of over-engineering process and slowing responsiveness; May reduce spontaneous collaboration if roles become too rigid.
Facilitate a one-day session where the team co-creates explicit ground rules (meeting conduct, escalation, deadlines) and does trust-building activities.
Strengths: Builds shared norms members feel ownership over, increasing compliance; Improves social cohesion which can support long-term collaboration. Risks: One-off events often fade without follow-up reinforcement; Does not address the structural cause of unequal participation.
Split the 9-member team into three 3-person pods, each owning a warranty defect category, reporting weekly to the full group.
Strengths: Smaller units raise perceived individual impact and reduce loafing; Enables faster, more focused root-cause cycles per defect category. Risks: Risk of losing cross-functional integration and shared mental model; Coordination overhead between pods if categories overlap.
Rotate the team-lead role monthly among members and formally coach the three dominant engineers to create space for others.
Strengths: Distributes status and voice more evenly, surfacing quieter expertise; Builds leadership capability across the team. Risks: Frequent leadership change can cause continuity and accountability gaps; May be perceived as punitive by high-performing engineers.
Set the weight of each criterion (1–5), then score every alternative (1–5). The matrix is a thinking aid, not a verdict.
| Criterion | Weight | A | B | C | D |
|---|---|---|---|---|---|
| Behavioural impact | |||||
| Employee acceptance | |||||
| Feasibility | |||||
| Cost (higher = more affordable) | |||||
| Risk containment | |||||
| Long-term sustainability |
With your current weights, alternative A scores highest. A matrix only reflects the weights you chose. Evidence, ethics, feasibility and the people affected still belong in your judgement — you decide.
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'.
- 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
- Why can a team of high performers still underperform as a collective unit?
- How would you measure whether social loafing, not skill gaps, is the real cause here?
- What role does status among engineers play in silencing quieter members?
- Could combining two alternatives (e.g., RACI plus rotated leadership) work better than either alone?
Social loafing refers to the tendency for individuals to:
In the Suvidha Auto case, which evidence most directly suggests social loafing rather than a skills gap?
Which combination best addresses both the structural and motivational roots of the team's underperformance?