What Situation-Based Coaching Actually Means.

Steven Rudolph · 5 min read

I've watched coaches encounter situation-based coaching — most often through the Hersey and Blanchard situational leadership model — and immediately apply it wrong. Usually within the first month. The framework clicks instantly — that's part of the problem.

You read where someone is: competence, commitment, readiness on this specific task. You flex your approach to match. More direction for a novice, more delegation for someone experienced. It's legitimate. It's also missing half the mechanism.

What Most People Think It Means

Situational coaching traces to Hersey and Blanchard's Situational Leadership model from the late 1960s. The core idea: effective leaders don't use one fixed style. They read the person's development level and adjust accordingly.

When you learn it, here's what you hear: Adjust your style to match where the person is.

Then you assume that where the person is is a property of the person.

So you assess them. Diagnose development level. Prescribe the coaching style. Flex. You feel like you're doing situational work.

You're doing half of what situation-based coaching actually requires.

The Half Most Coaches Skip

A situation doesn't shape you. It permits what's already there to emerge — or requires you to suppress it.

The development level someone shows in a coaching conversation isn't a fixed property of them. It's a reading of what the current situation is allowing them to express. Change the project, the reporting line, the stakes, the team dynamic — and you'll often get a different person. Because the situation stopped blocking what was already there.

Research on person-situation dynamics, tracing back to Walter Mischel's challenge to trait psychology, points at this consistently: behavior is more situationally variable than our intuitions about "personality" suggest. People aren't performing at a static level. They're performing at the level the situation permits.

If you're adjusting your style to match someone's apparent level, you may be optimizing for a reading the situation itself created. You're reading a symptom and calling it a diagnosis.

The missing question isn't How should I adapt my style? It's What is this situation currently permitting this person to express — and what is it blocking?

What the Misread Actually Costs

A manager tells you someone on their team lacks initiative. You adjust — more structure, more check-ins, more directive questions. The person improves marginally. Six months later, same complaint.

What nobody examined: the person is in a role where initiative gets absorbed into a process that erases their contribution. No trace of what they built. No signal it mattered. The situation produced the passivity. Your coaching accommodated it.

Or: a high-performer suddenly underperforming. You read low commitment. More motivation, more support, more check-ins.

What you didn't read: a reorganization shifted who has authority over their work. Their competence didn't drop. Their willingness to invest stopped making sense given what the situation now returns.

You diagnosed the wrong thing. Technique never had a chance.

Carol Dweck's work on growth mindset is frequently used to explain performance variation as a function of belief. Less cited: the same research shows that mindset interventions are significantly less effective when the environment doesn't support the behaviors they're trying to reinforce. Situation precedes and conditions what the person expresses. Coaching that reads only the person, ignoring what the situation permits or suppresses, will keep prescribing interventions that can't land.

What the Right Diagnosis Changes

The standard question: Where is this person in their development, and how should I adapt?

The more useful one: What is this situation currently permitting this person to express — and what is it requiring them to suppress?

These aren't the same question. The first keeps you inside the person. The second makes you read the context — what the role is actually asking of them, what the team dynamic is doing to their behavior, what the reporting relationship permits or blocks.

Sometimes the person genuinely needs development. More scaffolding, more direct feedback, more guided practice. The situational model's original insight holds.

Sometimes the person is already capable, and the situation has been suppressing it. Move the constraint — clarify authority, reduce the noise, change who's in the room. Competence that was invisible becomes visible.

That's the test: did something change in the person, or did something change in what the situation was blocking?

The Diagnostic That Changes the Conversation

The standard coaching assessment answers: what does this person need? You read their development level — competence on this specific task, commitment to the work — calibrate, and flex your approach. The framework gives you a lens, and the lens works.

A situation-based assessment answers a different question: what is this context currently requiring of this person, and what is it blocking?

These don't run in parallel. They produce different readings of the same behavior.

On the person side, the questions are about capability and choice. Can they do this work? Have they done something like it before? Is low output a function of missing skill or missing motivation — and have you been careful to distinguish the two?

On the situation side, the questions are about what the role is doing. If this person produces good work here, what happens to it? Who has authority over how it gets used? Does initiative get credited, or does it disappear into a process that produces no signal either way? What is the role actually asking of them — stated, and unstated?

Both assessments can point in the same direction. The person needs development, and the role is structured to support it. In that case, standard coaching moves work: more scaffolding, clearer feedback, more guided practice. Everything lands because the context isn't fighting it.

But sometimes they diverge.

The person is capable. The role requires them to act as if they're not. No real authority. Initiative generates friction instead of credit. Good work and bad work produce the same response, which is no response. What you're looking at isn't a development gap. It's what capable people look like when their situation keeps removing the conditions under which they function.

Coaching doesn't fix that. You can't develop what's already developed. What changes the reading is changing what the role is asking for.

Two things tell you which situation you're in. First: has this person performed differently in a different setting? If they've shown the same capability before — under a different manager, in a different role, on a different kind of project — then the setup is the variable, not the person. Second: what changes when you remove the constraint? If clarity of authority, credit for contribution, or visibility of impact becomes available and the person functions differently, that's not a development story. That's a situation story.

The question worth running first isn't how ready this person is. It's what this setup is doing to their readiness.

---

Frequently Asked Questions

What are the 4 styles of situational leadership?

The Hersey and Blanchard model describes four: Directing (high task, low relationship), Coaching (high task, high relationship), Supporting (low task, high relationship), and Delegating (low task, low relationship). Which one you use depends on the person's competence and commitment on a specific task. Not their overall seniority. Not your preference. The task.

What is the 70/30 rule in coaching?

Speaking time: the person being coached talks roughly 70% of the time, the coach 30%. It's not really a rule — it's a reminder that your job is to ask questions that make the person think, not to deliver answers. If you're talking more than they are, you've shifted into advising. That's a different job.

What are the 5 C's in coaching?

Different models use different lists, but Context is the one that consistently gets underweighted. Clarity, Competence, Confidence, Commitment — those are person-side variables. Context is what the situation is doing. Leave it out and you're assessing the person as if they exist in a vacuum. They don't.

What is situation-based coaching?

Reading what the current context is doing to a person before deciding how you should respond. That means two assessments: what's the person's development level on this specific task, and what is the situation currently permitting them to express? When those two things diverge — and they often do — the situation wins.

This is what the Xavigate Map was built for — to show you what your current arrangement is asking of you, what it's costing you, and what kind of path makes sense from here. Not a personality label. Not a pep talk. A clear picture of where you are and what to do next.