Intro to Organizational Behavior (OB): Team Dynamics - Roles and Norms, Role Ambiguity Role Conflict Role Overload Social Loafing

Roles and Norms: Study Guide

What This Is

Roles are the expected behaviors, tasks, and responsibilities tied to a position in an organization (e.g., "team leader" or "customer service rep"). Norms are the unwritten rules that govern how group members actually behave (e.g., "We don’t email after 6 PM" or "We celebrate wins with cake"). When roles are unclear (ambiguity), clash (conflict), or overwhelm (overload), performance suffers—and social loafing (free-riding) can emerge. Why it matters: Poor role design leads to stress, turnover, and inefficiency. Example: At Zappos, the shift to Holacracy (self-managed teams) initially caused role ambiguity, leading to confusion and slower decision-making until norms were redefined.

Key Theories & Models

• Role Theory (Kahn et al., 1964): Roles are shaped by role senders (e.g., managers, peers) who communicate expectations. Mismatches between expectations and reality cause stress. Implication: Clarify roles in writing (e.g., Netflix’s "Freedom & Responsibility" culture doc) and align them with team goals.

• Role Ambiguity (Rizzo et al., 1970): Unclear expectations about tasks, authority, or performance standards. Implication: Reduce ambiguity with job descriptions, regular feedback (e.g., Google’s OKRs), and "pre-mortems" (imagining failure to clarify roles).

• Role Conflict (Kahn et al., 1964): When expectations from different role senders clash (e.g., a manager wants you to cut costs, but your team expects high-quality work). Types:

• Intersender conflict (two bosses give conflicting orders).
• Intrarole conflict (one role has incompatible demands, e.g., "be innovative" but "don’t take risks").

• Person-role conflict (role violates personal values, e.g., Wells Fargo’s sales pressure leading to fraud). Implication: Prioritize expectations (e.g., Southwest Airlines pilots help load luggage to resolve "not my job" conflicts).

• Role Overload (French & Caplan, 1972): Too many roles or tasks exceed an individual’s capacity. Implication: Use time-blocking (e.g., Cal Newport’s "Deep Work") or delegate (e.g., Amazon’s "two-pizza teams" to limit scope).

• Social Loafing (Ringelmann Effect, 1913): Individuals exert less effort in groups than when working alone. Causes:

• Diffusion of responsibility (e.g., "Someone else will do it").
• Lack of accountability (e.g., anonymous group projects).

• Perceived dispensability (e.g., "My effort won’t matter"). Implication: Assign individual tasks (e.g., Spotify’s "squads" with clear ownership) or use peer evaluations (e.g., GE’s forced-ranking system).

• Norm Formation (Feldman, 1984): Norms emerge through:

• Explicit statements (e.g., Netflix’s "No brilliant jerks" policy).
• Critical events (e.g., Patagonia’s environmental activism after a pollution scandal).
• Primacy (first behaviors set the tone, e.g., Apple’s secrecy culture under Jobs).

• Carryover (norms from past groups, e.g., military veterans bringing hierarchy to startups). Implication: Shape norms early (e.g., Pixar’s "Braintrust" meetings to normalize candid feedback).

• Equity Theory (Adams, 1963): People compare their input:output ratio to others’. Role ambiguity/conflict can create perceived inequity (e.g., "Why am I doing more work for the same pay?"). Implication: Transparent role definitions (e.g., Buffer’s salary formula) reduce resentment.

• Job Characteristics Model (Hackman & Oldham, 1976): Role clarity and autonomy (skill variety, task identity, task significance) increase motivation. Implication: Design roles with job enrichment (e.g., Whole Foods teams manage their own inventory).

Step-by-Step Application

How to Diagnose and Fix Role/Norm Problems

1. Map the Role Ecosystem
2. List all role senders (bosses, peers, customers) and their expectations.
3. Example: A Salesforce account manager might have conflicting demands from marketing (data entry), sales (client calls), and support (troubleshooting).

4. Tool: Use a RACI matrix (Responsible, Accountable, Consulted, Informed) to clarify roles.

5. Identify Gaps: Ambiguity, Conflict, or Overload?

6. Ambiguity: "I don’t know what success looks like."-Provide metrics (e.g., HubSpot’s "Smarketing" SLA).
7. Conflict: "My boss wants X, but my team expects Y."-Negotiate priorities (e.g., Basecamp’s "Shape Up" method for scope limits).

8. Overload: "I have 10 priorities."-Use Eisenhower Matrix (urgent vs. important) or MoSCoW (Must-have, Should-have, Could-have, Won’t-have).

9. Redesign Roles with "Job Crafting" (Wrzesniewski & Dutton, 2001)

10. Let employees tweak their roles to fit strengths (e.g., Google’s 20% time).

11. Example: A Starbucks barista might add "mentor new hires" to their role for more task significance.

12. Set Norms Intentionally

13. Hold a norm-setting workshop (e.g., IDEO’s "Rules of Engagement" for brainstorming).

14. Example: Airbnb teams normed around "default to trust" to reduce micromanagement.

15. Prevent Social Loafing

16. Make contributions visible (e.g., GitHub’s commit history).
17. Use small groups (e.g., Amazon’s two-pizza teams).

18. Link rewards to individual effort (e.g., Salesforce’s commission structure).

19. Monitor and Adjust

20. Use pulse surveys (e.g., Glassdoor’s "Mood Tracker") to catch role stress early.
21. Example: Microsoft shifted from stack-ranking to continuous feedback after role conflict led to toxic competition.

Common Misconceptions

• Misconception: "Role ambiguity is always bad." Correction: Some ambiguity can foster creativity (e.g., 3M’s "15% time" for unstructured innovation). Key: Balance clarity with autonomy.

• Misconception: "Social loafing is just laziness." Correction: It’s often a systemic issue (e.g., lack of accountability). Example: Enron’s "rank-and-yank" system encouraged loafing by punishing collaboration.

• Misconception: "Norms are always positive." Correction: Norms can be toxic (e.g., Uber’s "always be hustling" culture led to burnout). Fix: Audit norms (e.g., Netflix’s "sunshining" bad behavior).

• Misconception: "Role conflict is unavoidable in matrix organizations." Correction: Conflict can be managed with clear escalation paths (e.g., Spotify’s "chapter leads" to resolve cross-team disputes).

• Misconception: "Role overload is just about workload." Correction: It’s also about emotional labor (e.g., healthcare workers managing patient grief). Fix: Provide psychological safety (e.g., Google’s "gPause" rooms).

Exam / Case Interview Tips

1. Question Pattern: "A team is underperforming. How do you diagnose the issue?"
2. Answer Framework:
   • Step 1: Check for role ambiguity (e.g., "Do they know their goals?").
   • Step 2: Look for role conflict (e.g., "Are there competing priorities?").
   • Step 3: Assess overload (e.g., "Are they spread too thin?").
   • Step 4: Watch for social loafing (e.g., "Is effort uneven?").

3. Example: In a McKinsey case, a client’s R&D team is slow—diagnose role overlap between engineers and product managers.

4. Tricky Distinction: Role ambiguity vs. role conflict

5. Ambiguity: "I don’t know what to do." (Lack of clarity)
6. Conflict: "I know what to do, but the demands clash." (Competing expectations)

7. Example: A Tesla factory worker might face ambiguity ("What’s my safety protocol?") and conflict ("My supervisor wants speed, but safety says slow down").

8. Norms vs. Rules

9. Rules: Formal (e.g., Amazon’s "no PowerPoint" policy).
10. Norms: Informal (e.g., Amazon’s norm of "disagree and commit").

11. Trap: Ignoring norms can undermine rules (e.g., Wells Fargo’s sales quotas led to fraud despite compliance training).

12. Social Loafing vs. Free-Riding

13. Social loafing: Unintentional (e.g., "I didn’t realize my effort mattered").
14. Free-riding: Intentional (e.g., "I’ll let others do the work").
15. Fix: For loafing, increase visibility (e.g., Slack’s @mentions); for free-riding, use consequences (e.g., Bridgewater’s "radical transparency" reviews).

Quick Practice Scenario

Scenario: At Shopify, a product team is missing deadlines. The designer complains, "I’m doing the PM’s job," while the PM says, "The engineers keep changing requirements." The engineers say, "We’re waiting on the designer’s mockups." Question: What’s the root cause, and how would you fix it?

Answer: Role conflict (PM vs. designer vs. engineer expectations) and role ambiguity (unclear handoffs). Fix: Use a RACI matrix to define responsibilities and hold a norm-setting workshop (e.g., "We’ll use Figma comments for feedback, not Slack").

Last-Minute Cram Sheet

1. Role ambiguity: Unclear expectations-stress, lower performance.
2. Role conflict: Competing demands-burnout (e.g., Wells Fargo sales vs. ethics).
3. Role overload: Too many roles-exhaustion (e.g., healthcare workers during COVID).
4. Social loafing: Reduced effort in groups-fix with accountability (e.g., GitHub commits).
5. Norms form via: Explicit statements, critical events, primacy, carryover (e.g., Apple’s secrecy).
6. Equity Theory: Role stress-perceived inequity-demotivation.
7. Job Crafting: Employees redesign roles (e.g., Google’s 20% time).
8. RACI matrix: Clarifies Responsible, Accountable, Consulted, Informed roles.
9. Norms-rules: Norms are informal (e.g., Netflix’s "no brilliant jerks").
10. Social loafing-free-riding: Loafing is unintentional; free-riding is intentional.