Situational Leadership: Adapt Your Style to Any Team

You promote your best engineer to team lead. Six months later, she's drowning. She still solves every hard problem herself, her calendar is a wall of one-on-ones she scheduled out of guilt, and the two juniors she was supposed to develop are quietly doing the same three tasks they mastered in week one.

Nothing about her technical skill changed. What changed is that she's running the same play for everyone on the team — and situational leadership is the name for the thing she's missing. It's the practice of matching how much direction and how much support you give to what a specific person needs on a specific task, right now. Not to their personality. Not to their seniority. To the task in front of them.

What situational leadership actually means

Strip away the diagrams and the acronyms, and the idea is almost boringly practical: there is no single best way to lead. A style that makes one person flourish makes another person stall — and often it's the same person, just three months apart, on a different kind of work.

The model most people mean when they say "situational leadership" comes from Paul Hersey and Ken Blanchard, developed back in the late 1960s and refined for decades since. Their core claim was that effective leaders read two things at once: how much direction someone needs (clear instructions, defined steps, close follow-up) and how much support they need (encouragement, listening, shared decisions). Adjust those two dials, and you get four styles.

The four styles in plain English

You'll see these labeled S1 through S4, or by names like Directing, Coaching, Supporting, and Delegating. Here's what they look like on an ordinary Tuesday.

Style	Direction given	Support given	Sounds like
Directing	High	Low	"Here's the process. Do step one, then step two, then check in with me."
Coaching	High	High	"Try it this way, and tell me what felt wrong. I'll sit in on the next one."
Supporting	Low	High	"You've got the skills. What's actually blocking you — the work or the worry?"
Delegating	Low	Low	"Own it. Ping me if the budget crosses a line, otherwise I'll see it at review."

Notice that none of these is "the good one." Directing isn't bossy and delegating isn't enlightened. They're tools, and the only question that matters is which one fits this person, on this task, this month.

The D1 to D4 development levels, explained

Each style pairs with a development level — sometimes called readiness or maturity. The labels you'll run into are D1, D2, D3, and D4, and they describe someone's commitment and competence on one specific task, not their overall talent.

• D1 — the enthusiastic beginner. High motivation, low skill. They'll volunteer for anything and get it slightly wrong. Needs Directing.
• D2 — the disillusioned learner. Some skill now, but the excitement has curdled into frustration. This is the person who says "I thought this would be more interesting." Needs Coaching.
• D3 — the capable but cautious performer. Competent, but hesitant to commit without a second opinion. Needs Supporting.
• D4 — the self-reliant achiever. Knows the work, trusts their own judgment. Needs Delegating.

Here's the part that trips people up: the same person sits at different levels on different tasks at the same time. Your senior designer might be D4 on layout and D1 on the analytics dashboard you just handed her. Treat her as one or the other across the board and you'll get it wrong half the time.

Can you give me an example of situational leadership style?

Yes — and the clearest one I can give you comes from watching a manager handle two people on the same project in the same week, using two completely different styles.

Picture a small product team shipping a new onboarding flow. One contributor, Marcus, is two weeks into his first job out of university. He's bright and eager and has never run a user test. The other, Priya, has run hundreds of tests but has just been told her role is changing and she's suddenly second-guessing every call she makes.

Case one: the new hire

Marcus gets Directing. Not because he's junior in some permanent sense, but because his competence on this task is genuinely low. So the manager writes out the test script with him, sits in on the first two sessions, and reviews the notes before they go to stakeholders. Specific instructions, close follow-up, minimal debate about approach. That's not micromanagement — it's the correct amount of structure for a D1.

Case two: the capable but shaken expert

Priya gets something closer to Supporting. Her skill is high; her confidence just took a hit. Handing her a detailed script would insult her. Leaving her entirely alone would leave her spiraling. So the manager's job is mostly listening — asking what she'd change about the test plan, agreeing with her instincts when they're sound, and staying available without hovering.

Same project. Same week. Two entirely different leadership moves, and neither one is favoritism. That contrast is situational leadership.

What about someone who's an expert but never needs support?

That's your D4. You delegate, you set the boundaries — budget, deadline, escalation triggers — and you get out of the way. The mistake most managers make here is confusing "high performer" with "no need for anything." Even D4s need clarity on what success looks like. They just don't need you standing next to them while they get there.

How to diagnose someone's development level without guessing

This is where most advice on the topic gets slippery. Everyone tells you to "assess readiness," nobody tells you how. Here's the approach I've found actually holds up.

Ask three questions about the person, on this task, right now:

1. Have they ever done this before? Not something similar — this.
2. When they do it, do they ask for review or avoid it? Seeking feedback on approach signals D2 or D3. Avoiding it usually means either D4 confidence or D1 confusion, and you need to find out which.
3. What's their energy like when the topic comes up? Enthusiastic and naive, frustrated and stuck, careful and hesitant, or calm and independent — those four moods map almost perfectly onto D1 through D4.

One trap to flag: managers routinely overestimate the readiness of the people they like, and underestimate the people who remind them of themselves. You'll catch it if you write your read down before the conversation, then check it against what actually happens over the next two weeks.

What to do when your read turns out to be wrong

You will get it wrong. Regularly.

I once delegated a whole reporting cycle to someone I was sure was a D4, based on six months of watching her handle client work effortlessly. She delivered it two weeks late and quietly stopped volunteering for anything for a month afterward. She wasn't capable-but-cautious on that task. She was a D1 who'd never built a report and never told me, because I'd framed it as a vote of confidence. My diagnosis was wrong, and the cost was her trust, not the tardy report.

When you misread, the fix isn't to swing all the way back to directing forever. It's to add structure back for one task, say out loud that you moved too fast, and reset. That honesty does more for your credibility than getting it right every time.

What are the weaknesses of situational leadership?

Plenty — and the model gets sold far too cleanly. Three problems matter most.

It can read as manipulation. If you switch styles without explaining why, your team sees inconsistency, not adaptation. The person who got detailed instructions last month and loose reins this month may conclude you've lost faith in them. The fix is transparency: name the shift and the reason for it. "You've got this now, so I'm stepping back — that's a change from last quarter, deliberately."

Diagnosis is subjective. There's no instrument that tells you whether someone is D2 or D3. You're reading energy, hesitation, and follow-through, and you're reading them through your own biases. I've seen two managers disagree sharply about the same employee's readiness for the same responsibility, and both felt strongly about it.

It's a product of its era. The framework grew out of Western management thinking and assumes a fairly individual, task-focused view of work. On a team where decisions are collective, or where a manager's authority is expected to be more directive by cultural norm, the softer modes can land awkwardly. Worth knowing before you apply it as gospel.

The honest verdict: the underlying instinct — pay attention to what each person needs on each task — is sound, and almost any good manager already does it by feel. The four-box version is useful as a shared vocabulary. It's not a procedure.

Can you describe your leadership style and how you motivate your team?

If you're sitting across from someone in an interview and they ask this, don't recite the four styles. It sounds memorized, and it doesn't answer the question.

Describe your default posture, then how it moves. Something like: I lean toward delegating with clear boundaries, because I've watched capable people disengage when someone stands over them. But I move to coaching the moment I see frustration building, and I'll go fully directive for a week when someone is genuinely new to a task — no pretending that's beneath either of us.

Motivation follows the diagnosis, not the pep talk

Motivation isn't a speech you give. It's the byproduct of matching the support level to the person. A D1 is motivated by quick wins and clarity. A D2 is motivated by someone acknowledging that the frustration is normal and temporary. A D3 needs permission to trust their own call. A D4 needs room, and gets demotivated fast if you don't give it.

So when you're asked how you motivate your team, the strongest answer is a specific example: "One person on my team was stalling on every decision. I stopped reviewing her work and started asking what she'd choose if I weren't around. Her output doubled, but more importantly, she stopped asking me for permission on things she was already good at."

That's a style you can describe. It's also just situational leadership wearing normal clothes.

The model won't make you a better leader on its own. The discipline of asking, every few weeks, "what does this specific person need on this specific task right now" — that will. The four boxes just give you a place to put the answer.