How to Use the Situational Leadership Model (4 Styles)
Learn the four Hersey-Blanchard leadership styles, how to read competence and commitment, and which style to use with each person on each task.
To use the situational leadership model, assess how ready a person is for one specific task, then choose the leadership style that matches: directing, coaching, supporting, or delegating. Readiness means two things, skill and confidence, and both can change from task to task. Your job is to give exactly as much direction and as much encouragement as the person needs right now, and to reduce both as they grow.
The idea behind the model
Paul Hersey and Ken Blanchard built the model on a simple observation: no single leadership style works for everyone. A hands-off leader is great for an expert and a disaster for a new hire. A detail-obsessed leader is the reverse.
The model crosses two kinds of leader behavior:
- Directive behavior: telling people what to do, how, and by when, then checking the work.
- Supportive behavior: listening, encouraging, explaining why, and involving people in decisions.
Mix high or low amounts of each and you get four styles. The skill is not in memorizing them. It is in diagnosing the person and the task before you open your mouth.
The four styles
Here is how the styles line up with the readiness of the person you are leading.
| Style | Direction | Support | Person's readiness for this task | What you say |
|---|---|---|---|---|
| Directing (S1) | High | Low | Low skill, high enthusiasm | "Here is the task, the steps, and the deadline." |
| Coaching (S2) | High | High | Some skill, confidence dipping | "Let's walk through it. Here is why we do it this way. What's tripping you up?" |
| Supporting (S3) | Low | High | Solid skill, shaky confidence or motivation | "You know how to do this. What do you think we should do?" |
| Delegating (S4) | Low | Low | High skill, high commitment | "This is yours. Tell me what you need from me." |
Blanchard's later version, Situational Leadership II, labels the matching readiness levels as the enthusiastic beginner, the disillusioned learner, the capable but cautious performer, and the self-reliant achiever. Those names are useful because they describe the emotional arc. People start excited, hit a wall when the task proves harder than expected, regain skill before confidence, and finally own it.
Directing: for the enthusiastic beginner
Someone new to a task usually has energy and no map. They do not need a pep talk. They need clear steps, examples, and a deadline.
Make the decisions yourself, define success in measurable terms, and check progress often. "Write a good onboarding email" is vague. "Write three emails, 120 words each, sent on day 1, 3, and 7, using this template, draft to me by Thursday" is directing.
Coaching: for the disillusioned learner
Two to four weeks in, the novelty fades and the person realizes the task is harder than it looked. Output stalls, questions dry up, and they may get quiet. This is the most commonly mishandled stage.
Keep the direction high, but add real support. Explain the reasoning behind your decisions, ask for their ideas, and praise specific progress. You still make the final call, but you make it with their input.
Supporting: for the capable but cautious performer
This person can do the work but hesitates. They ask for approval they do not need, or their output is good one week and slow the next. The gap is confidence or motivation, not skill.
Pull back on instructions and lean into questions. "What would you do if I were not here?" works better than another checklist. Your role is to remove doubt, not to supply answers.
Delegating: for the self-reliant achiever
Skilled and committed people want a clear outcome, authority, and to be left alone. Agree on the result, the boundaries, and when you will check in. Then stay out of the way.
Delegating is not abandoning. You still need a way to see progress, such as a weekly dashboard or a short written update. If you want a fuller method for handing work over, read How to Delegate Effectively as a Team Lead or Founder.
How to use the model, step by step
1. Define the task narrowly
Readiness belongs to a task, not a person. "Marketing" is too broad. "Build the Q1 paid search budget" is the right size. If you cannot describe the task in one sentence, you cannot diagnose readiness for it.
2. Rate skill and confidence separately
Ask two questions and score each from 1 to 4:
- Skill: Has this person done this task, or a close cousin, successfully? How recently?
- Confidence and motivation: Do they volunteer for it, ask good questions, and recover from setbacks? Or do they avoid it, over-check, or go quiet?
A 1 on skill and a 4 on confidence is a classic new hire. A 3 on skill and a 2 on confidence is where supporting fits. Do not average the two numbers. The combination is the diagnosis.
3. Look for behavioral cues, not your gut
Your gut is biased toward people you like and people who talk like you. Use observable evidence instead.
- Signs of low skill: repeated errors of the same kind, questions about basic steps, work that misses the brief.
- Signs of falling confidence: more requests for approval, missed small deadlines, shorter messages, fewer ideas offered.
- Signs of high readiness: the person anticipates problems, brings solutions with the problem, and corrects their own mistakes before you see them.
4. Choose the style and say it out loud
Tell the person how you plan to work with them on this task. "Since this is new, I'll check in daily for the first week and then move to twice a week." People handle close oversight well when they know why it exists and when it ends. Without that explanation, it feels like distrust. Your 1 on 1 meetings are the natural place to agree on this.
5. Reassess on a schedule
Put a date on it. For a new task, review readiness every two weeks. For stable work, once a quarter is enough. The goal is to move people along the curve, from directing toward delegating, so you gain time back.
A worked example
Take a 12-person ecommerce company doing $2.4 million in annual revenue. The founder wants to launch a wholesale channel with a target of $300,000 in the first six months. Three people share the launch.
Priya, operations lead, six years in. Priya has run supplier relationships for years and wants the pricing and fulfillment work. Task: set wholesale pricing and fulfillment terms. Skill is high and commitment is high, so this is delegating. The founder agrees on the outcome (gross margin of at least 35 percent on wholesale orders, shipping within 5 business days) and asks for a one-page update every Friday. Total founder time: about 30 minutes a week.
Marcus, marketing generalist, eight months in. Marcus has run consumer email campaigns well but has never done outbound to retailers. After a strong first week, Marcus's list-building stalls at 40 contacts out of a target of 200 and the messages get shorter. Skill on this task is moderate and confidence has dropped, so this is coaching. The founder sits with Marcus for an hour, specifies the target account profile (independent retailers with 2 to 10 locations), explains why that segment pays faster, and asks Marcus to rewrite the first outreach email. The founder keeps the decision on who gets contacted but takes Marcus's suggestions on messaging. Within three weeks the list reaches 180 contacts.
Jordan, new hire in week two. Jordan has never handled a sales pipeline. Task: log and follow up on wholesale leads. This is directing. The founder provides a CRM template, a follow-up schedule (day 2, day 5, day 12), and a daily 10-minute check for the first two weeks.
The outcome after six months: the channel brings in $265,000, below the target, mostly because the first retailer contracts took longer to close than planned. But nobody was overmanaged or abandoned. By month three, Jordan's check-ins moved to weekly and Marcus was handling outreach on a supporting basis. The founder's weekly time on the launch fell from about 6 hours to 2.
The same three people would have gotten worse results under one style. Directing Priya would have wasted the founder's hours and irritated the person with the most context. Delegating to Jordan would have produced a messy pipeline and lost leads.
Common mistakes
Using your favorite style on everyone
Most leaders have a default. Founders who built the business by doing everything tend to over-direct. Leaders who dislike conflict tend to over-delegate. Both feel natural to the leader and wrong to at least half the team.
Fix: Before each assignment, ask which style you would pick if you ignored your habit. If your answer matches your default every time, you are probably not diagnosing.
Treating a dip as a skill problem
When a capable person's work slips, the reflex is to give more instructions. If the cause is confidence, motivation, or a personal issue, more instructions make it worse. The person hears "you can't do this" when the real issue is "you doubt you can."
Fix: Ask before you instruct. A simple "what's making this harder than last time?" tells you whether to direct or support. If the work has quality problems, tie your response to specifics, as described in How to Give Feedback That Actually Changes Behavior.
Jumping from directing to delegating
A new hire does well for two weeks and the leader steps away. The first real obstacle arrives and nobody is there. This is the disillusioned learner stage, and skipping coaching is the most common reason new hires fail.
Fix: Move one step at a time: directing, coaching, supporting, delegating. Never skip two.
Labeling the person instead of the task
Calling someone "a delegator" or "a hand-holder" locks in a style that outlasts the facts. A strong salesperson may be a beginner at forecasting.
Fix: Write the task next to each name in your notes, not a general rating.
Ignoring the team's climate
Coaching and supporting only work if people feel safe admitting what they do not know. If the team punishes mistakes, people hide their real readiness and your diagnosis fails. See How to Build Psychological Safety in Your Team for how to fix that first.
A quick cue checklist before you assign work
Run through this in two minutes:
- What exactly is the task, and when is it due?
- Has this person done it or something very close in the last six months?
- What did their last similar piece of work look like?
- Are they asking more or fewer questions than usual?
- What happens if this goes wrong, and how fast could I find out?
The last question matters. High-stakes tasks with slow feedback loops justify more oversight even for skilled people, because a mistake would show up too late to fix. That is a judgment about risk, layered on top of readiness.
Key takeaways
- Choose a leadership style per person and per task, never per personality.
- Diagnose skill and confidence separately, using observable behavior rather than your gut feeling.
- Match the style to the readiness: directing for beginners, coaching for the disillusioned learner, supporting for capable but cautious people, delegating for self-reliant performers.
- Move people one style at a time and reassess every two weeks on new tasks, since skipping coaching is where most new hires stall.
- Tell people which style you are using and why, so close oversight reads as support and not distrust.
- Watch your own default. The most common failure is applying the style you like to everyone.
Frequently asked questions
- What are the four styles of the Hersey-Blanchard situational leadership model?
- They are directing (telling), coaching (selling), supporting (participating), and delegating. Each one is a different mix of task direction and relationship support, and you pick one based on how ready the person is for the specific task.
- Do you use one situational leadership style per employee?
- No. The style attaches to the person and the task together. A senior designer can need delegating on brand work and directing on a new reporting tool in the same week.
- How do you know which leadership style to use?
- Assess two things for the task at hand: the person's skill and their confidence or motivation. Low skill with high enthusiasm calls for directing, low skill with dropping confidence calls for coaching, solid skill with shaky confidence calls for supporting, and high skill with high commitment calls for delegating.
- Is situational leadership still useful for small teams?
- Yes, and arguably more so, because small teams have few buffers. One badly matched style, such as micromanaging a strong performer or abandoning a new hire, shows up quickly in missed deadlines and turnover.
- What is the difference between Hersey-Blanchard and Situational Leadership II?
- Paul Hersey and Ken Blanchard created the original model in the late 1960s. Blanchard later revised it as Situational Leadership II, with updated names for the styles and a clearer view of how a person's confidence rises and falls as they learn. The practical idea of matching style to readiness is the same in both.
Related playbooks
How to Delegate Effectively as a Team Lead or Founder
Use the delegation ladder to match each task to the right level of autonomy. Stop micromanaging and hand off work with real confidence and clarity.
How to Communicate Business Strategy to Your Team
A communication cascade template that turns your strategy deck into a message frontline employees understand, remember, and connect to daily work.
How to Run a Strategy Offsite Meeting for a Small Team
A half-day and full-day agenda for a small-team strategy offsite, with facilitation tips and a worked example that ends in real, owned decisions.
Team Charter Template for Small Teams (That Gets Used)
Build a team charter for a small team in one 90-minute session. Get the key components, a copyable template, a worked example and facilitation tips.