The Leadership Style You Default To Is Probably The Wrong One

In fifteen years of leading teams and coaching the people who lead them, I’ve watched a strange pattern repeat itself. Smart, experienced executives — people who can read a balance sheet in thirty seconds and a boardroom in less — go completely blind when it comes to reading the one variable that determines whether their people thrive: what this specific person needs from me, on this specific task, right now.

Situational leadership is one of the most taught and least applied frameworks in management. Most executives can recite it. Almost none use it well. And the reason isn’t that the model is complicated. It’s that we apply it to the wrong thing.

The idea in one breath

Situational leadership says there is no single best way to lead. The right approach depends on the person’s competence (can they do this task?) and their commitment (are they motivated and confident about it?). As those two things shift, your style should shift with them.

The model gives you four styles to move between:

• Directing — you provide the what, the how, and the when. High instruction, low hand-holding on the emotional side.
• Coaching — you still direct, but you explain, involve, and build buy-in.
• Supporting — they know how; you provide encouragement, a sounding board, and space.
• Delegating — you hand over ownership and get out of the way.

Simple enough. So why does it go wrong?

The mistake hiding in plain sight

Most managers diagnose the person. The model is about the task.

We say things like “John is a delegate-to kind of guy” or “Priya needs a lot of direction.” We file people into a fixed slot and lead them from that slot forever. But competence and commitment aren’t personality traits — they’re task-specific and they move. A brilliant operator who can run your largest region on autopilot may be a rank beginner the moment you hand her a post-merger integration. Same person. Completely different starting point.

This is where seniority becomes a trap. We assume senior means capable, so we default to delegating with experienced people. But seniority is not competence on a new task — it’s competence on old ones.

How to actually diagnose it

Diagnosis is a skill, and it’s learnable.

For competence, read the work, not the résumé. Has this person done something genuinely similar, and done it well? Watch the quality of their questions: beginners ask “what should I do?”, capable people ask “I’m planning to do X — does that hold up?” Watch how their plans survive contact with reality. Competence shows up as accurate self-assessment and plans that don’t fall apart on day three.

For commitment, read energy and ownership. Listen to pronouns and verbs. “I’ll have it Thursday” is ownership. “Should we maybe look at it?” is not. Notice whether they volunteer or wait to be assigned, whether they bring you problems with proposed solutions or just problems. Commitment is motivation plus confidence — and the two can diverge. Someone can be desperate to succeed and terrified they’ll fail.

Then just ask. Three questions get you most of the way:

1. “Walk me through how you’d approach this.” (Tests competence.)
2. “What’s the part you’re least sure about?” (Surfaces both gaps and confidence.)
3. “Where do you actually want me involved?” (They often know — and it builds the contract.)

A story about getting it wrong, then right

A few years ago I coached a managing director — call him Jay — who’d just handed a major systems integration to one of his strongest directors after an acquisition. The director had a spotless track record. So Jay did what you do with your best people: he delegated. Quarterly check-ins, full autonomy, “come to me if you need anything.”

Four months later the project was quietly underwater. The director hadn’t come to anyone, because asking for help felt like admitting he was out of his depth — which he was. He’d never run an integration. Jay had read the person (“he’s excellent”) instead of the task (“this is brand new to him”). High commitment, low competence — an enthusiastic beginner in disguise — and Jay had given him the one style that beginner couldn’t use.

The fix wasn’t to demote or rescue him. It was to switch styles. Jay moved to directing on the integration specifics — clear milestones, weekly working sessions, a defined playbook — while continuing to delegate the director’s home turf. Within a month the project had a pulse again.

Moving the same person across all four styles

The reason that story matters is what happened next, because it shows the whole model in motion on a single person and a single task.

In the first weeks, the director needed directing — structure, decisions made for him, a clear path. As he learned the terrain, Jay shifted to coaching: still hands-on, but now explaining the why, debating trade-offs, building judgment. Around month four — the dangerous dip, when the work is hard and the novelty has worn off — competence was rising but motivation sagged. That’s a supporting moment: less instruction, more encouragement and space to vent and recover. By month seven the director was running it cleanly and Jay could finally do what he’d tried to do on day one — delegate — except now it actually worked.

Four styles, one person, one task, six months. That’s situational leadership working as designed. The goal is to make your own involvement progressively obsolete.

The most common mistakes

• Leading from your comfort style. The hands-off executive delegates everything; the operator directs everything. We reach for the style that suits us, not the one the situation needs.
• Confusing a skill gap with a will gap. When someone capable stalls, we pile on more instruction. But more direction never fixes a motivation problem — and more cheerleading never fixes a competence problem. Diagnose which one you’re looking at.
• Misreading the dip. The drop in commitment a few months into hard work isn’t failure; it’s predictable. Pull back to directing and you’ll insult them. Push to delegating and you’ll lose them. They need support.
• Never graduating people. Getting stuck in directing or coaching long after someone’s ready is how you create dependent, frustrated, eventually-departing talent.

Where the model breaks down

It’s a framework, not physics, and it has limits worth naming.

Remote teams. Half of diagnosis lives in signals you pick up in a hallway — hesitation, energy, the thing someone almost says. Remotely, those signals thin out, and “supporting” loses its informal texture. The fix is to be deliberate: explicit check-ins, written reflections, and direct questions about confidence you’d normally read from a room.

Toxic environments. The model assumes good faith and a real development relationship. If someone is checked out because of fear, politics, or a broken system, no amount of style-flexing will reach them. Sometimes the problem isn’t your leadership style — it’s the environment, and that’s the thing to fix first.

Cultural differences. Style cues don’t translate cleanly. In higher power-distance cultures, a “supporting” leader asking lots of open questions can read as a boss who doesn’t know the answer, and “delegating” can feel like abandonment rather than trust. Calibrate to how authority and autonomy are actually expected to look.

Your Monday-morning checklist

You don’t need to overhaul anything. Try this on one person:

1. Pick a person and a current task. Not the person in general — this task.
2. Score the task. Competence: have they done this, well, before? Commitment: are they both motivated and confident?
3. Match the style to what you scored, not to your habit.
4. Ask, don’t assume. Use the three questions above.
5. Name the contract. Agree out loud on how involved you’ll be and when you’ll revisit it.
6. Re-diagnose monthly. The right style has a shelf life. People grow; your style should expire on schedule.

Four rules of thumb to keep in your pocket: seniority is not competence on a new task. When in doubt, diagnose before you direct. More direction fixes a skill gap, never a will gap. And your real job is to make your own style obsolete.

The next time you feel yourself reaching for your default — the move you always make, with everyone — stop for ten seconds and ask what this person needs on this task. That pause is the whole skill.