Intro to Organizational Behavior (OB): Leadership - Behavioral Theories, Ohio State Studies University of Michigan Blake Moutons Managerial Grid

Behavioral Theories of Leadership (Ohio State Studies, University of Michigan, Blake & Mouton’s Managerial Grid)

What This Is

Behavioral theories of leadership focus on what leaders do—their actions and behaviors—rather than innate traits. These theories emerged in the 1940s–1960s as researchers sought to identify patterns of leader behavior that predict effectiveness. They matter because they provide a trainable framework for managers: unlike trait theories (e.g., "leaders are born"), behavioral theories suggest leadership can be learned. For example, Google’s Project Oxygen (2008) found that the best managers exhibit behaviors like coaching, empowering teams, and showing concern for well-being—directly aligning with the dimensions identified in these theories.

Key Theories & Models

• Ohio State Studies (1940s–1950s): Initiating Structure vs. Consideration
• Initiating Structure: Task-oriented behaviors (e.g., defining roles, setting deadlines, enforcing standards). Example: A Netflix manager clarifies performance expectations ("Freedom & Responsibility" culture) to ensure high output.
• Consideration: People-oriented behaviors (e.g., showing empathy, building trust, supporting team members). Example: Southwest Airlines’ "LUV" culture emphasizes employee well-being, reducing turnover.

• Implication: High-performing leaders balance both dimensions. Overemphasizing structure (e.g., micromanaging) can stifle creativity; neglecting it (e.g., "nice guy" syndrome) may lead to chaos.

• University of Michigan Studies (1950s): Employee-Centered vs. Production-Centered Leadership

• Employee-Centered: Focuses on relationships, team development, and individual needs. Example: Zappos’ holacracy empowers employees to self-organize, prioritizing autonomy over rigid hierarchies.
• Production-Centered: Focuses on tasks, efficiency, and goal achievement. Example: Amazon’s "Day 1" mentality drives relentless execution but can create high-stress environments.

• Implication: Employee-centered leaders tend to achieve higher satisfaction and long-term performance, but production-centered approaches may excel in crisis or short-term projects.

• Blake & Mouton’s Managerial Grid (1964): Concern for People vs. Concern for Production

• A 9x9 grid plotting leader behavior on two axes:
  • Concern for People (Y-axis): From 1 (low) to 9 (high).
  • Concern for Production (X-axis): From 1 (low) to 9 (high).
• Five Key Styles:
  1. Impoverished (1,1): Minimal effort; avoids responsibility. Example: A disengaged manager who delegates everything and offers no feedback.
  2. Country Club (1,9): High people focus, low task focus. Example: A manager who prioritizes harmony over deadlines (e.g., a team that misses targets but has "fun").
  3. Produce-or-Perish (9,1): High task focus, low people focus. Example: A factory supervisor who enforces strict quotas but ignores employee burnout.
  4. Middle-of-the-Road (5,5): Balanced but mediocre. Example: A manager who meets goals but fails to inspire or innovate.
  5. Team Leader (9,9): High on both axes; ideal style. Example: Patagonia’s CEO Yvon Chouinard balances environmental goals (production) with employee well-being (people).

• Implication: The grid helps leaders diagnose their style and shift toward 9,9 for optimal performance. However, context matters—e.g., a 9,1 style may be necessary in a turnaround situation.

• Likert’s System 4 (1967): Participative Leadership

• Extends Michigan studies by categorizing leadership into four systems:
  1. Exploitative-Authoritative: Top-down, fear-based (e.g., early Ford factories).
  2. Benevolent-Authoritative: Paternalistic (e.g., some family-owned businesses).
  3. Consultative: Seeks input but retains control (e.g., Google’s "20% time" policy).
  4. Participative: Full team involvement in decisions (e.g., Valve’s flat hierarchy).
• Implication: Participative leadership (System 4) correlates with higher productivity and satisfaction, but requires trust and psychological safety.

Step-by-Step Application

1. Diagnose Your Leadership Style
2. Take the Managerial Grid self-assessment (available online) to plot your concern for people vs. production.

3. Example: If you score 7,3, you’re task-heavy but could improve empathy (e.g., schedule 1:1s to build rapport).

4. Assess Team Needs

5. Use the Ohio State dimensions to evaluate whether your team needs more structure (e.g., unclear roles) or consideration (e.g., low morale).

6. Example: A startup team struggling with ambiguity may need more initiating structure (e.g., defined OKRs).

7. Adapt Your Style

8. For high-stress teams (e.g., crisis): Shift toward 9,1 (Produce-or-Perish) temporarily.
9. For creative teams (e.g., R&D): Use 9,9 (Team Leader) to balance autonomy and support.

10. Example: Netflix’s "Keeper Test" ("Would I fight to keep this person?") combines high structure (performance standards) with high consideration (trust in employees).

11. Train for Balance

12. For task-heavy leaders: Practice active listening (e.g., "What’s one challenge you’re facing this week?").
13. For people-heavy leaders: Set clear deadlines (e.g., "Let’s review progress every Friday at 3 PM").

14. Example: Google’s "g2g" (Googler-to-Googler) program trains employees in coaching behaviors to develop 9,9 leaders.

15. Measure Outcomes

16. Track employee engagement scores (e.g., Gallup Q12) and productivity metrics (e.g., output per employee).
17. Example: Zappos saw a 30% increase in engagement after implementing holacracy (employee-centered leadership).

Common Misconceptions

• Misconception: "The best leaders always use a 9,9 style."

• Correction: Context matters. A 9,1 (Produce-or-Perish) style may be necessary in a turnaround (e.g., Steve Jobs at Apple in 1997) or crisis (e.g., healthcare during COVID-19). The grid is a tool, not a rigid rule.

• Misconception: "Initiating structure and consideration are opposites—you can’t do both."

• Correction: The Ohio State studies found these dimensions are independent. A leader can be high on both (e.g., a manager who sets clear goals and supports team well-being). Example: Southwest Airlines’ leaders balance operational efficiency with employee-first policies.

• Misconception: "Employee-centered leadership always leads to higher performance."

• Correction: While employee-centered leadership often improves satisfaction, production-centered leadership can outperform in short-term, high-pressure environments (e.g., Amazon’s warehouse operations). The key is fit with the situation.

• Misconception: "The Managerial Grid is outdated because modern leadership is more nuanced."

• Correction: The grid remains foundational because it simplifies complex behaviors into actionable dimensions. Modern theories (e.g., transformational leadership) build on these ideas. Example: Google’s Project Oxygen identified "coaching" and "empowering" as key behaviors—both align with the 9,9 style.

Exam / Case Interview Tips

1. Question Pattern: "Which leadership style is best for [scenario]?"

2. How to Answer:

   • Start with context (e.g., "In a crisis, a 9,1 style may be necessary to stabilize operations").
   • Compare trade-offs (e.g., "While 9,1 drives short-term results, 9,9 fosters long-term innovation").
   • Reference real examples (e.g., "Netflix uses a 9,9 approach to balance high performance with employee autonomy").

3. Tricky Distinction: Ohio State vs. Michigan Studies

4. Ohio State: Two independent dimensions (initiating structure and consideration).
5. Michigan: Two opposing dimensions (employee-centered vs. production-centered).

6. Trap: Don’t assume they’re the same—Michigan’s model suggests a trade-off, while Ohio State’s allows for high scores on both.

7. Case Interview Tip: When analyzing a leadership problem, map the leader’s behavior to the Managerial Grid.

8. Example: If a case describes a manager who avoids conflict and sets no goals, label them 1,1 (Impoverished) and recommend shifting toward 5,5 or 9,9.

9. SHRM/CIPD Tip: These exams often test application, not just definitions. For example:

10. Question: "A team is underperforming despite high morale. What’s the likely issue?"
11. Answer: The leader is likely 1,9 (Country Club)—high on people, low on production. Recommend adding structure (e.g., SMART goals).

Quick Practice Scenario

Scenario: At a tech startup, the engineering team is highly collaborative and supportive (e.g., regular team lunches, open feedback), but they consistently miss deadlines. The manager, Alex, prides himself on being "a people person" and avoids setting strict timelines to maintain harmony.

Question: Using Blake & Mouton’s Managerial Grid, what is Alex’s leadership style, and what should he do to improve team performance?

Answer: Alex is a 1,9 (Country Club) leader—high concern for people, low concern for production. To improve performance, he should shift toward 9,9 by:
1. Setting clear deadlines (e.g., "We’ll demo the feature on Friday").
2. Balancing support with accountability (e.g., "I’ll help unblock you, but let’s agree on a backup plan if we miss the deadline"). Example: Google’s "Objectives and Key Results" (OKRs) combine high structure with high support.

Last-Minute Cram Sheet

1. Ohio State Studies: Initiating structure (tasks) + consideration (people) are independent dimensions.
2. University of Michigan: Employee-centered (people) vs. production-centered (tasks) are opposing dimensions.
3. Blake & Mouton’s Grid: 9,9 (Team Leader) is ideal, but context matters (e.g., 9,1 in crises).
4. Likert’s System 4: Participative leadership (full team involvement) is most effective.
5. Trap: Ohio State-Michigan—Ohio State allows high scores on both dimensions; Michigan treats them as trade-offs.
6. Real-World Example: Google’s Project Oxygen = 9,9 leadership (coaching + high standards).
7. Real-World Example: Amazon’s warehouse management = 9,1 (production-focused).
8. Trap: "9,9 is always best"-No! 9,1 may be needed in turnarounds.
9. Diagnostic Tool: Use the Managerial Grid to plot your style and identify gaps.
10. Application Tip: For low-performing teams, ask: "Do they need more structure (initiating) or support (consideration)?"