The Situational Leadership Model: A Brain-Based Guide to Leading Change in 2026

You gave two people the same instruction last week. One of them ran with it. The other went quiet, and you found out on Thursday that nothing had moved.

Nobody was being difficult. You handed the same thing to two people who needed different things from you, and that is almost impossible to see while it's happening.

This guide covers what the Situational Leadership® Model says, why adapting is harder than knowing you should, and what to do differently on Monday.

Key takeaways

• The model sorts by task, not by person. Someone can be an expert at one thing and a beginner at the next, in the same week.

• Under pressure, the approach you've practiced most is the one that shows up, whether or not it fits.

• Under-leading a beginner and over-leading an expert are both diagnosis errors, and both are common.

• Adapting your approach is not inconsistency. It becomes inconsistency when you never explain it.

• AI has put experienced people back at the beginning, and that's a question of readiness, not more training.

What the Situational Leadership® Model says

The Situational Leadership® Model came from Paul Hersey and Ken Blanchard, who first published the idea as life cycle theory of leadership in the Training and Development Journal in 1969. The Center for Leadership Studies, which Hersey founded, owns the mark. Blanchard later developed his own version, trademarked separately as SLII®. It isn't my framework, and it isn't what I teach. I'm using it here because it names something I see all the time.

The core claim was unusual at the time. No single way to lead is best. The right amount of direction depends on the person in front of you and the specific task you're handing them, and both change.

This might sound strange now, but the earlier thinking treated leadership as a fixed type, something you either had or you didn't. Hersey and Blanchard moved the question off your personality and onto the person and the task.

That last part is where most leaders go wrong. A senior developer can be at the top of their game writing code and completely at sea leading a client presentation. Same person, same week. Treat them as an expert in both, and you'll get a great sprint and a bad presentation.

Why one approach becomes your default

Early in my career, I was running an office, and one Friday afternoon the whole team walked out. I had driven that team way past what they could handle, and it was probably the best lesson I could have learned. I can laugh about it now. I wasn't laughing about it then.

My default back then was pacesetting, which Daniel Goleman described as "Do as I do, now." It worked on people who were already good at the work and already motivated, so I used it on everyone, and it was wrong for.

Most leaders can explain this model. Far fewer adapt in the moment.

In his 2000 Harvard Business Review article, Goleman reported research by the consulting firm Hay/McBer on a random sample of 3,871 executives. He wrote that leaders who had mastered four or more styles had the very best climate and business performance, that the most effective ones switch flexibly among the styles as needed, and that flexibility can be learned. My old favorite, pacesetting, wears people down when it's the only approach you have.

Choosing deliberately costs. You're holding the task, the person, their track record and your own read on the risk, all at the same time. Cowan's 2001 review says working memory holds about four things at once. That's hard to hold together on a busy afternoon with a deadline coming. Under pressure the practiced response is faster, so you do what you did last time.

This is why leaders over-direct in a crisis. It's the most practiced move. It's also why the leader who tells you they treat everyone the same is usually describing a habit.

The fix isn't more knowledge about the model. It's noticing which approach you reach for first.

The four approaches, and what they come down to

Hersey's model sorts leader behavior into four: telling, selling, participating and delegating. In practice, it comes down to three situations: someone who can't do it yet, someone who can and doubts it, and someone who can and has proved it.

High direction, for genuinely new work. When someone hasn't done a thing before, specifics aren't micromanagement. They get the work started. Give the steps, check the work, and be available. As they find their footing, keep the direction but start explaining your reasoning, because they'll need it when you're not there.

Reassurance, for people who can do it and doubt they can. Some people have the skill and are hesitant anyway. More instruction makes that worse. What helps is asking what's making them hesitate, and then telling them plainly that you think they can do it

Less direction, for people who have earned it. Others already know exactly what to do and need you to stop checking. This is where leaders get stuck, because you're still accountable for the result after you've handed over control. Agree on what you want to hear about and when, then leave the rest alone.

The two mistakes are opposites. Leave a beginner to figure it out, and they'll spend more time worrying about looking incompetent than doing the work. Tell an expert how to do their own job and you've told them you don't trust them, whatever your words said. The NeuroLeadership Institute's 2015 work on insight describes what happens when you hand someone the answer. It takes the problem out of their hands, and in front of their team it says you didn't think. They get defensive and stop thinking through the problem.

Neither one is a character flaw. Both are diagnosis errors, and diagnosis is a skill you can get better at.

Your one small shift this week: pick the person you're least sure about and ask them what part of their current work they'd want more support on. Then don't argue with the answer.

Applying The Shift Method

Knowing the model and changing your own behavior are different problems. This is where I use The Shift Method, which is mine: Identify, Question, Reframe, Vision, Act.

Identify. Name your default. Not the one you'd claim in an interview, but the one that shows up in a bad week, when the deadline moved, and you're tired.

Question. Ask whether that default is a judgment or a habit. The test is whether you can remember deciding.

Reframe. Move from "I have a leadership style" to "I have a set of responses, and I've been using one of them." A style feels like identity, and identity resists change. A set of responses is easier to add to.

Vision. Pick one person and one task, and decide what your approach should be, specifically, before the next conversation.

Act. Do it once, then again, past the point where it feels like effort. Gartner found the same thing about change itself. Their July 2025 research on change found that 79% of employees have low trust in change, and that the inspirational approach only works when change trust is high. When it's low, which is now the normal condition, making the new behavior routine works better. In Gartner's words, "When leaders routinize change, our model predicts that employees are three times more likely to adopt changes on time and in a healthy way even though they have low change trust."

Where this gets hard right now

AI has taken experienced, senior people on your team and put them back at the start.

That's a readiness problem, not a training problem, and the numbers suggest most organizations haven't treated it as either. Gallup's Q2 2026 tracker, fielded in May 2026, found 47% of U.S. employees say their organization has integrated AI tools, and only 25% say it has communicated a clear AI plan. Robert Half's Navigating the AI Era in 2026 found just 35% of workers feel "very confident" using AI tools effectively

So you have capable people, a tool they haven't used, and no stated expectation. Delegate into that, and you're not granting autonomy. You're leaving someone to guess in public, in front of colleagues who think of them as the person who knows things, and most people manage that risk by quietly doing nothing

Right now, I see senior leaders trying to use AI in public, and it tells you a lot about a person's leadership. Some of what I see being produced is truly awful, but it's an important part of the process. Making mistakes and learning from them. I’m sure you can recall something you created for the first time, were so proud of, and years later just cringe at how bad it was. I know I have more than my share of those experiences, and comes with learning in public.

The move here isn't fancy. Be specific at the start. What should they use it for, and what should they check? Then, once the mechanics are handled, have the harder conversation about what this means for the thing they're good at. Leaders often skip that second part, and it's often what decides whether anyone uses the tool at all.

This is the work FYB | AI Confidence covers. It's about mindset rather than prompts, and it deals with what it costs someone to be seen learning. Tool training leaves that part out.

Adapting is not inconsistency

The worry is that adapting makes you look like you have no principles. You give one person detailed direction and another almost none, and it can read as favoritism.

It reads that way only when it's unexplained. Say the reason out loud: "You've run these before, so this one is yours. I'm staying closer to David on the escalation because it's his first." Most people who hear that don't think you're inconsistent. They think you're paying attention.

What people experience as unfair is the opposite. One approach for everyone ignores what each person has earned, and the expert you're managing like a novice notices long before you do.

So make the call before the conversation, and tell the person why.

Frequently asked questions

What is the difference between the Situational Leadership Model and servant leadership?

I see the Situational Leadership® Model as tactical and task-specific. It answers what this person needs from you on this piece of work, right now. Servant leadership is a stance on your role. They aren't in conflict, and most good leaders do both. They just answer different questions.

How do I know if I am micromanaging or giving appropriate direction?

Ask whether the person has done this specific thing before. Detailed direction helps someone who hasn't. The same direction to someone who has done it forty times is a message about trust, whatever you intended. When you're unsure, ask them which they'd prefer and take the answer at face value.

What is the most common mistake leaders make with this model?

Diagnosing the person instead of the task. Once someone is filed as strong or weak, that label follows them into work they have never touched. You get both errors at once: the strong performer left alone with something they've never done, and the weaker one still supervised on work they mastered a year ago.

How long does it take to change how I lead?

Longer than a workshop, and less time per day than you'd think. In Lally and colleagues' 2010 study, the median time for a new behavior to become automatic was 66 days, with a range from 18 days to 254, so anyone who promises you a fixed number of days is guessing. What shortens it is repeating the new approach in the same situation, instead of whenever you happen to remember.

Is a model from the 1960s still relevant with AI?

AI has made capable people beginners again at something everyone can see them do. That is the situation the model was built to describe. The mechanics of the tools change constantly. The question of how much direction a capable person needs when they're new to something does not.

How do I handle someone who is expert at one thing and new at another?

Treat the tasks separately, and tell them that's what you're doing. The risk is letting seniority carry across. It's easy to leave someone alone on work they've never attempted just because they've earned that in their core job. They read your absence as a sign you expect them to already know how.

Will people think I am playing favorites?

Only if you never explain it. Say it at the time: this person has done this before; that one hasn't.

Situational Leadership® is a registered trademark of Leadership Studies, Inc. dba The Center for Leadership Studies. SLII® is a registered trademark of Blanchard Training and Development, Inc. This article references these models to identify them and is not affiliated with, licensed by, or endorsed by either company.

About this article. Tiffany Whitney is a NeuroLeadership-trained brain-based coach with 18 years of Fortune 500 Learning & Development leadership, and Amazon bestselling co-author of Strength with Kathy Ireland. Statistics are cited to primary sources. This article is for educational purposes and is not medical, psychological, or clinical advice. Feed Your Brain is not affiliated with or endorsed by the NeuroLeadership Institute.