Situational Leadership
There's no right way to lead — only the right way for this person right now: direct, coach, support, or delegate.
Find this on the mind-map
Introduction
Paul Hersey and Ken Blanchard first laid this out in their 1969 book Management of Organizational Behavior, where they called it the "Life Cycle Theory of Leadership." The name later changed to Situational Leadership, and the core claim stuck: no single leadership style works everywhere.
The right style depends on the person in front of you — specifically, on their readiness for the specific task at hand. You don't change who you are as a leader. You change how you lead in that moment.
How It Works

The model has two moving parts you're constantly matching against each other: the development level of the person you're leading (D1 to D4), and your own leadership style (S1 to S4).
| Development level | Competence and commitment | Matching style | What you do |
|---|---|---|---|
| D1 | Low competence, high commitment. New to the task, eager, inexperienced | S1: Directing | High direction, low support. Set goals, give clear instructions, supervise closely |
| D2 | Some competence, low commitment. Gaining experience but overwhelmed or discouraged | S2: Coaching | High direction, high support. Guide and motivate, stay very involved |
| D3 | High competence, variable commitment. Skilled, but short on confidence or motivation | S3: Supporting | Low direction, high support. Listen, ask questions, share the decision |
| D4 | High competence, high commitment. Seasoned, confident, self-driven | S4: Delegating | Low direction, low support. Set context, trust fully, step back |
Here's the part people miss: development level isn't a permanent label you stick on someone. It's task-specific. The same person can be a confident D4 on one project and a shaky D1 on the next, and commitment can shift week to week. That's why you run this as a loop, not a one-time checklist — diagnose, match your style, then re-diagnose.
Why It Matters for Leaders
You'll tend to fall into one of two traps: over-managing everyone, or under-managing everyone. Either way, you're leading from your own default preference instead of what the person in front of you actually needs — the same failure the Goldilocks Principle describes. Situational Leadership tells you which side of it you're on with each person.
The most common misread is mistaking enthusiasm for competence. Say you hand a bright new hire — high energy, zero domain experience — a critical project and tell them to "run with it." That person is a D1, and "run with it" just means they'll deliver on time against assumptions nobody checked. High commitment doesn't substitute for direction.
The reverse mistake costs just as much. A senior expert going through a confidence dip doesn't need to be taught their job — they need someone to listen and take some pressure off. Hit a D3 with S1-style direction and it reads as distrust, and you'll watch them disengage faster.
There's a psychological-safety payoff to just naming the style out loud. Tell someone "I'll be hands-on at the start and taper off from there," or "you've got full control here — flag me if you hit a wall," and they know exactly what to expect from you instead of guessing.
The practical upside is that leadership stops being a guessing game. You know when to coach, when to direct, and when to get out of the way — and the call is grounded in evidence about the person, not in habit.
What to do next
Test your knowledge of Situational Leadership
Practice Situational Leadership
Apply Situational Leadership to a real situation
Skills related to Situational Leadership
Mental Agility
Matching how you lead to the situation in front of you and the person you're leading, because the approach that worked yesterday might be exactly wrong today.
Team Development
Building a high-performing team on purpos, guiding people through the stages of a team's growth, building real trust between them, and handing over ownership as they earn it.
Frameworks related to Situational Leadership
Amara's Law
You overestimate new tech's short-run impact and underestimate its long-run impact — so ask if you're early, not whether it's working.
Dunning-Kruger Effect
Knowing little makes you feel unstoppable; knowing more makes you hesitate — the loudest voice is rarely the most reliable one.
Goldilocks Principle
Support runs on a dial between micromanagement and abdication — enough direction for clarity, enough space for ownership, always moving.
Hawthorne Effect
People change how they behave when they know they're watched — your attention is an intervention that changes what you see.
Maslow's Hierarchy of Needs
Abraham Maslow's five-level model of motivation, applied to leadership as a stack — mastery, trust, belonging, up through recognition and vision.
McKinsey 9-Box Model
A 3x3 grid that plots each person on performance against potential, giving nine distinct calls instead of one blurry verdict.
Multipliers and Diminishers
Liz Wiseman's split between leaders who bring out best thinking in people around them, and those who shut it down.
The 6 Human Needs
Every behavior at work is really an unmet need in disguise — six needs, popularized by Tony Robbins, worth checking first.
The Architecture of High-Performing Teams
Six elements, built like a temple — culture as the base, four pillars, vision as the roof — name the missing piece.
The Bannister Effect
One person breaking a barrier makes it stop being fixed for everyone else — break the unspoken belief in public first.
The Five Dysfunctions of a Team
Lencioni's pyramid of five team-killing behaviors — a lack of trust at the base drags everything above it down.
The Inner Drive
A leadership take on Daniel Pink's *Drive* that turns three conditions for motivation — autonomy, mastery, purpose — into habits for 1:1s.
The Pygmalion Effect
What you expect from someone leaks into how you treat them, which shapes what they become — for better or worse.
The Thomas-Kilmann (TKI) Model
Five conflict styles, two dials — how hard you push, how much room you give — chosen on purpose, not by default.
Tuckman's Stages of Team Development
Every team moves through five predictable stages — forming, storming, norming, performing, adjourning — each demanding a different move from you.
Books related to Situational Leadership
Coaching for Performance
Sir John Whitmore's foundational case for coaching-style management over command-and-control, built on a single idea: performance is limited less by skill than by interference, and a manager's job is to remove the interference, not supply the answer.
Elevate
Robert Glazer's case, from his book "Elevate: Push Beyond Your Limits and Unlock Success in Yourself and Others," that performance isn't a willpower problem. It's a capacity problem across four specific domains, built like a muscle, not willed into existence overnight.
First, Break All The Rules
A large-scale look at what the best managers actually do differently, and the uncomfortable finding that most of it runs against conventional management wisdom, starting with the idea that you shouldn't try to fix people's weaknesses.
Multipliers
Liz Wiseman's case that the biggest lever on a team's output isn't headcount or talent density, it's whether the leader in the room makes people smarter or slowly makes them smaller.
Team Topologies
Skelton and Pais's case that most team structures are drawn to fit an org chart, not the actual flow of work, and a small set of team shapes and interaction rules for fixing that, built around a resource every leader habitually overspends: people's cognitive load.
The Coaching Habit
Michael Bungay Stanier's pitch that most managers have an "advice monster" problem, and a short list of deceptively simple questions designed to starve it, a little at a time, in conversations that already happen every day.
The First-Time Manager
The unglamorous, practical handbook for the specific week your job title changed and nothing else came with instructions. Less a framework, more a set of answers to the questions new managers are usually too embarrassed to ask out loud.
The Five Dysfunctions of a Team
Patrick Lencioni's pyramid of the five behaviors that sink teams without much notice, stacked so that each one is actually caused by the dysfunction beneath it, which means fixing results or accountability first almost never works.
The Making of a Manager
Julie Zhuo's field notes from becoming a manager in her twenties with no idea what the job actually was. A clear-eyed answer to the question most new managers are too embarrassed to ask out loud: what am I actually supposed to be doing all day?
The Manager's Path
Camille Fournier's map of the actual career ladder from doing the work to leading an organization of leaders, written for engineering managers, but mostly a clear-eyed account of how the job itself changes at every rung, which almost nobody explains to you before you climb it.
Turn the Ship Around!
A submarine captain's account of giving up the one thing every leader is taught to protect, being the person who gives the orders, and turning the worst-performing submarine in the fleet into one of the best by making every sailor think like a captain instead.