The situational leadership model

Paul Hersey and Ken Blanchard set out the model in the late 1960s, originally calling it the life cycle theory of leadership, in their textbook on organisational behaviour. They later went separate ways, and the framework now exists in two branded lineages with slightly different vocabulary: Hersey's version talks about follower readiness, Blanchard's about development level. The underlying claim is the same. Leadership style should be a variable, not a personality trait.

That claim is why the model has outlived most of its contemporaries. Every manager has watched a colleague who is superb with juniors flounder with experts. Situational leadership gives that observation a structure you can act on.

The four styles at a glance

Two behaviours move underneath those four labels: how much task direction you give, and how much relationship support you give. Directing is high task, low support. Coaching is high on both. Supporting is low task, high support. Delegating is low on both. Once you see it as two dials rather than four boxes, the model becomes much easier to use in the moment.

Readiness is about the task, not the person

This is the single most misused part of the model, and it is misused in almost every organisation that has bought the training. Managers label people. "She's an S4." "He needs directing." That is not what the model says.

Readiness is per task, per moment. Your most senior engineer is S4 on architecture and S1 on the first client presentation of their life.

Treat readiness as a coordinate on a specific piece of work and the model starts working. Treat it as a rating of the human being and you have simply invented a new way to condescend to experienced people.

• Before choosing a style, name the task out loud: not "managing the account" but "running the quarterly review without me in the room".
• Assess two things separately: can they do it, and will they do it. Ability and willingness move independently.
• Expect a person to sit in different styles across their own job on the same day. That is the model working, not a contradiction.

Matching style to readiness

S1 Directing: new to the task

Someone who has never done the work needs specifics, not encouragement. Vague autonomy given to a beginner reads as neglect, and they will fill the gap by guessing. Be concrete about standards and deadlines, and check early rather than at the end.

S2 Coaching: the enthusiasm has worn off

This is the stage where people discover the task is harder than it looked. Skill is rising, morale is falling. The instinct is to back off and give them space. Resist it. Keep giving direction, but start explaining the reasoning behind it so they can eventually generate the answers themselves. Coaching is the most demanding style for a manager because it costs the most time.

S3 Supporting: capable but not yet confident

The work is technically within reach and the person keeps checking in anyway. Every time you answer the question, you confirm they were right to ask. Turn the question back: "what would you do if I were away this week?" Then back their answer publicly. Confidence is built by having a decision survive contact with reality, not by being reassured.

S4 Delegating: competent and confident

Hand over the outcome, the decisions and the visibility. Delegating is not disappearing. Agree what would make them come to you early, then stay out of it. The fastest way to demote a performing person back down the grid is to delegate the task and keep the authority.

The mismatches that cost the most

The model earns its keep in the errors it helps you name. Four are worth watching for:

1. Delegating to a beginner. Usually dressed up as trust or as respecting autonomy. It is normally a manager avoiding the work of explaining.
2. Directing an expert. Reliably reads as distrust, and it is the fastest route to losing your best people quietly.
3. Supporting when someone needs direction. Warmth applied to a skill gap. The person feels cared for and still cannot do the task.
4. Coaching forever. The manager enjoys being needed, so the explaining never stops and the person never gets handed anything.

How to run the conversation

Situational leadership is applied in a two-minute exchange, not in an annual plan. A workable sequence:

1. Name the specific task and the standard for done.
2. Ask the person to rate their own confidence on it, then say where you'd put them. Compare the two openly.
3. Agree the style out loud: "For this one I'm going to be quite prescriptive, and I'll back off once you've done two."
4. Set the check-in points before the work starts, not after something goes wrong.
5. Name the exit condition. What has to be true for you to move from directing to delegating? If nobody can answer that, you are not developing anyone.

The fourth and fifth steps are the ones people skip, and they are the ones that stop close supervision curdling into micromanagement. Direction agreed in advance is support. The same direction imposed mid-task is interference. If those conversations are difficult, the underlying skill is feedback rather than the model itself.

Where the model breaks down

Situational leadership is taught almost everywhere and questioned almost nowhere. Four honest limitations:

1. The empirical support is thin and uneven. Independent tests over several decades have produced mixed results. The clearest support is for directing inexperienced people; the predictions about the middle and upper levels of the grid hold up much less consistently. It is a useful heuristic, not a validated law.
2. Readiness is hard to measure and easy to fake. Ability and willingness are judged subjectively, usually under time pressure, often through self-report. Confident people get read as capable and quiet competent people get read as needing help.
3. It is a one-to-one model in a team world. It says nothing about how you lead a group whose members sit at four different readiness levels simultaneously, and nothing about what the rest of the team infers when they watch you direct one colleague and delegate to another. For the group dynamics it ignores, Tuckman's stages is the better lens.
4. Context is missing. Culture, hierarchy, remote working, crisis conditions and the leader's own credibility all change what a style communicates. The same delegating behaviour lands as respect in one setting and abandonment in another.

There is also a practical failure mode: the model is easy to learn and hard to do. Managers leave the workshop able to recite four styles and go straight back to the one they have always used, now with better vocabulary for it.

A short self-audit

• List your direct reports and, beside each name, the last significant task you gave them. Which style did you actually use?
• Count the styles. If three of the four are missing, you have a default, not a range.
• Find one person you are over-directing and give a piece of it away this week, with the check-ins agreed up front.
• Ask one person directly: where do you want more direction from me, and where do you want less? The answers are usually not where you'd guess.

That last question is where the model meets reality. Style flexibility is a behaviour, not an insight, and behaviours only shift with practice under pressure. Put a manager into a live exercise where the pace is real and the outcome is uncertain, and their default style appears within minutes: the person who directs everyone regardless, the person who supports and supports and never decides. Seeing that pattern in yourself, in a room, with people who saw it too, does more than any grid on a slide. It is the argument for experiential learning over another briefing on leadership styles.

Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning appsThe Weekly Challenge to see the method in ten minutes.