← The library

Leadership / people development

Situational Leadership

Paul Hersey and Ken Blanchard's claim that there is no single best leadership style: the right one depends on the development level of the person being led on a specific task.

Match a directive, hands-on style to a keen beginner and a hands-off, delegating style to a proven expert, and everything in between. Get the match wrong in either direction, over-managing an expert or abandoning a novice, and you demotivate the person and stall the work.

Problem
Leadership / people development
Altitude
Individual to team
Effort to run
Light
Evidence base
Emerging

Theory & origin

Paul Hersey and Ken Blanchard introduced Situational Leadership in 1969, and Blanchard later refined it into the widely taught SLII model. The core claim is contingency: leadership effectiveness is not a fixed trait but a match between the leader's style and the follower's readiness on a particular task. Two behaviors define the styles, directive behavior, structure, instruction, and close supervision, and supportive behavior, encouragement, listening, and involving the person in decisions. Cross them and you get four styles. S1 Directing is high directive and low supportive, telling. S2 Coaching is high on both, explaining and persuading. S3 Supporting is low directive and high supportive, facilitating. S4 Delegating is low on both, handing over. The follower is read on a development scale for the specific task. D1, the enthusiastic beginner, has low competence but high commitment. D2, the disillusioned learner, has some competence but low commitment as the difficulty bites. D3, the capable but cautious performer, has high competence but variable confidence. D4, the self-reliant achiever, is high on both. The prescription is a diagonal: D1 needs S1, D2 needs S2, D3 needs S3, D4 needs S4, and the leader's job is to move the person along by adjusting style as they develop. Two honesty notes. The empirical support for the precise four-by-four prescription is thin. And development level is per task, not a global label for a person, so the same employee can be a D4 on one task and a D1 on another. Used loosely, as a reminder to diagnose before you lead and to flex your style, it is one of the most practical management models there is. Used rigidly, as a formula that types people, it becomes another box.

Key components

The parts at a glance. Click any term for the full definition, a field example, and the common failure, in the model below.

Explore the model

D1: enthusiastic beginner: keen, unskilled

How a consultant runs it

  1. 01 Diagnose the person on the specific task before choosing a style. The same employee can be a self-reliant expert on one task and a nervous beginner on another, and a global label is the first mistake.
  2. 02 Match the style to the development level, not to your comfort. Leaders default to their favorite style and apply it to everyone, so half their people end up over-managed or abandoned.
  3. 03 Watch for the two expensive mismatches. Delegating to a D1 beginner sets them up to fail, and directing a D4 expert insults them into disengagement.
  4. 04 Treat style as a dial to turn, not an identity. The goal is to move people up the development scale by gradually withdrawing direction as competence grows.
  5. 05 Hold the four-by-four loosely. The value is the habit of diagnosing readiness and flexing, not the precise prescription, whose evidence base is thin.

When to use

  1. 01 Coaching managers to flex their style instead of leading everyone the same way
  2. 02 Diagnosing why a specific person is stalling: over-managed, or left without enough support
  3. 03 Onboarding and development planning, mapping how leadership support should change as competence grows

When not to use

  1. 01 As a fixed personality label for a person. Development level is per task, not a global type.
  2. 02 As a precise, evidence-proven formula. The four-by-four prescription has thin empirical support and is best held loosely.
  3. 03 As a substitute for the leader building actual relationship and judgment. It is a diagnostic aid, not autopilot.

Worked example

A credit team lead is frustrated that two of her analysts are underperforming, and Situational Leadership shows the two problems are opposite mismatches. The first is a new hire, six weeks in, keen but green. She has been delegating to him the way she does with her seniors, handing over cases with a shout if you need me, and he is drowning quietly, too anxious to ask and making avoidable errors. He is a D1 who needs S1 Directing: a checklist, close review, and clear instruction until competence builds. The second is her most senior analyst, a genuine D4, whom she has recently started reviewing case by case after one bad loan, reverting to S1 Directing on a self-reliant expert. He reads it, correctly, as lost trust, and has started doing the minimum while he looks around. He needs S4 Delegating restored, with recognition. The lead flips her approach: heavy structure and coaching for the beginner, a step back and an honest conversation for the expert. Within two months the new hire is handling standard cases unaided and the senior is re-engaged. Nothing about either analyst changed. The leadership style finally matched the person.

Common pitfalls

  1. 01 Applying one favorite style to everyone, so half the team is over-managed and half is abandoned
  2. 02 Delegating to a beginner, who then fails from lack of direction, not lack of ability
  3. 03 Directing an expert, who reads the micromanagement as distrust and disengages
  4. 04 Typing a person as a fixed level, when development level is specific to each task
  5. 05 Treating the four-by-four as a proven formula rather than a loose diagnostic habit

Sample deliverable

One real engagement, start to finish. Watch the numbers travel from raw input, onto the chart, into the finished artifact.

Style-to-readiness match across a credit team

Input

  • New hire (D1) needs Directinghigh directive, low support
  • Disillusioned (D2) needs Coachinghigh directive, high support
  • Capable (D3) needs Supportinglow directive, high support
  • Expert (D4) needs Delegatinglow directive, low support

Process

Each analyst is read on the task, and the leadership style is matched to the development level

OutputDeliverable

Style-to-readiness match across a credit team

  • Diagnoseread each person on the specific task
  • MatchD1 to Directing, D4 to Delegating, and so on
  • Resultthe beginner learns, the expert re-engages

Sources

Next in the library The GROW Model