Situational Leadership
Situational Leadership, developed by Paul Hersey and Ken Blanchard in 1969, holds that there is no single best leadership style — effective leaders match their style to the developmental level of each individual on each task. The model defines four leadership styles (Directing, Coaching, Supporting, Delegating) and four employee development levels (D1: Enthusiastic Beginner, D2: Disillusioned Learner, D3: Capable but Cautious, D4: Self-Reliant Achiever). Mismatches are catastrophic: delegating to a D1 produces failure and panic; directing a D4 produces resentment and resignation. The same leader, with the same person, must use different styles on different tasks — because that person can be a D4 at coding and a D1 at managing a team.
The Trap
Most managers have ONE style they default to and apply it universally. Hard-driving managers direct everyone (which infantilizes their D4s). Coaching-oriented managers ask 'what do you think?' to a D1 who literally doesn't know — leading to weeks of confused output. The trap is style fixation: you treat your style as your identity instead of as a tool. Worse, managers misdiagnose development level — they assume seniority equals competence on every task. A 15-year veteran joining a new company is a D1 on company-specific systems even if they're a D4 on the underlying craft. 80% of management failures trace to style-task-person mismatch, not to bad intent.
What to Do
For each direct report, build a Skill-Will Matrix per major task. Write down: (1) Their current task — be specific, not generic. (2) Their competence (low/high). (3) Their commitment (low/high). Map to style: Low Skill + High Will = Directing (give specific instructions, the enthusiasm is there). Low Skill + Low Will = Coaching (sell the why, build skill, restore confidence). High Skill + Low Will = Supporting (they CAN do it, ask what they need to want to). High Skill + High Will = Delegating (get out of the way, give resources). Re-audit quarterly — people move levels.
Formula
In Practice
When Satya Nadella took over Microsoft in 2014, he applied situational leadership at an enterprise scale. Veteran teams shipping Office got a Delegating/Supporting approach — they had decades of skill and just needed permission to break old constraints (cross-platform, cloud-first). New initiatives like Azure AI got a Directing/Coaching approach — Nadella personally set strategy, attended deep technical reviews, and rebuilt confidence. The same CEO, same week, used different styles on different teams — and Microsoft's market cap went from $300B to $3T.
Pro Tips
- 01
The 'New Job Reset' rule: every internal promotion or role change drops a person from D4 to D1 on the new responsibilities. Promoting your best engineer to manager and then delegating people-leadership to them on day one guarantees failure. They need Directing on management for 6-12 months, even though they're D4 on coding.
- 02
Ask development-level diagnosis questions instead of assuming. For competence: 'walk me through how you'd approach this.' For commitment: 'on a scale of 1-10, how excited are you about this project?' Below 7 means you have a commitment problem masquerading as a skill problem.
- 03
Style-shifting fatigue is real. If you have 8 direct reports operating at 4 different levels on 3 different tasks each, you're managing 96 style decisions. This is why effective managers cap direct reports at 7-8 — and why first-line managers should be promoted to managers-of-managers only when they can hold the matrix in their head.
Myth vs Reality
Myth
“The best leadership style is empowering / delegating”
Reality
Delegating to someone who lacks the skill is abandonment, not empowerment. The best style is the one that matches THIS person on THIS task RIGHT NOW. A directing style applied to a D1 is care; the same style applied to a D4 is insulting.
Myth
“Once you've assessed someone's level, it's stable”
Reality
Development level is task-specific and time-specific. The same person can regress (after a confidence-shaking failure, after burnout, after a re-org) or advance rapidly. Re-diagnosing quarterly is non-optional. Many of the worst manager-employee blowups happen when the manager's mental model of the employee is 18 months out of date.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Scenario Challenge
Your new senior PM, Raj, has 10 years of PM experience from Google. You hired him to lead your payments team. After 6 weeks, deliverables are slipping and the team is confused about priorities. He's frustrated and says he 'just needs to be left alone to do his job.'
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
Manager Style-Match Accuracy
Measured via 360 feedback comparing style used to development level on actual tasks.Skilled Situational Leader
85%+ correct style match
Average
55-85% match
Single-Style Default
< 55% (one-size-fits-all)
Source: Center for Leadership Studies (Hersey research)
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Microsoft (Satya Nadella era)
2014-Present
When Satya Nadella took over from Ballmer in 2014, Microsoft was a D4-everywhere assumption — engineers who'd shipped Windows for 20 years were treated as autonomous experts on EVERY future bet. But on cloud, mobile, and AI, the company was D1: lots of opinions, little real expertise. Nadella explicitly mapped style to capability: he Directed/Coached cloud-first transformation (personally attending Azure design reviews, being prescriptive on strategy), while Delegating execution of mature businesses to seasoned VPs. Same CEO, very different styles per team.
Market Cap (2014 → 2024)
$300B → $3T+
Cloud Revenue (2014 → 2024)
$3B → $130B+
Glassdoor CEO Rating
98% approval (industry top 1%)
Style Range Used Weekly
All 4 (per public interviews)
The same leader must operate multiple styles in parallel. Nadella's success isn't 'empowering culture' — it's calibrated direction where direction was needed, calibrated empowerment where capability existed.
Ken Blanchard Companies (Origin)
1969-Present
Ken Blanchard and Paul Hersey developed Situational Leadership in 1969 at Ohio University, then Blanchard refined it into SLII in 1985. Over 14 million managers have been trained in the model — making it one of the most widely deployed leadership frameworks in history. Companies adopting SLII report measurable shifts: Caterpillar, MetLife, and Pfizer all credit SLII implementation with 20-40% reductions in time-to-productivity for new hires and significant retention improvements among mid-career employees.
Managers Trained in SLII
14M+ globally
Fortune 500 Adoption
70%+ have used the model
Avg New-Hire Time-to-Productivity Reduction
20-40% (per case studies)
Year Introduced
1969 (refined 1985)
The model has survived 55+ years because it solves a real problem: managers who default to one style mismanage 60-75% of their team interactions. Putting language to development levels lets managers diagnose instead of just react.
Hypothetical: Engineering Manager 'Auto-Delegate' Failure
2022
Hypothetical: A newly promoted engineering manager at a 200-person SaaS company read 'Drive' and 'Multipliers' and decided his style would be 'maximum autonomy for everyone.' He delegated his entire roadmap to his 6 engineers, including a fresh new-grad and a recent transfer from data engineering with no backend experience. Within 90 days, the new-grad had built a feature with no test coverage that broke production three times, the transfer had quietly missed 4 sprint commitments, and the team's velocity dropped 40%. The manager was put on a PIP for 'failure to manage.'
Style Used
Delegating (universal)
D-Level of Team
2 D4s, 2 D3s, 2 D1s (mismatched)
Velocity Drop in 90 Days
-40%
Manager Outcome
PIP
Universal delegation feels modern but is malpractice when half your team isn't ready for it. Empowerment is a verb that requires assessment, not a value to be performatively applied.
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Situational Leadership into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Situational Leadership into a live operating decision.
Use Situational Leadership as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.