Situational Leadership

Situational Leadership

Overview

Match your leadership style to each person's development level on each specific task — cycling through four styles (Directing, Coaching, Supporting, Delegating) as competence and commitment evolve. Introduced by Hersey & Blanchard (1969); formalized as SLII by Blanchard, Zigarmi & Zigarmi (1985).

Core diagnostic: instead of "what kind of leader should I be?" ask "what does this person need from me on this task right now?" Failure to update style as the person grows is the most common cause of high performers disengaging.

Composes with: kotter-change for org-level transformation (Kotter = org sequence; this = each individual relationship); principal-agent to rule out incentive problems first; okr-goal-setting to set goals (OKR) then govern how to support each person toward them.

When to Use

• A manager-report relationship has friction or underperformance and root cause is undiagnosed
• A high performer is disengaging ("I'm being micromanaged", "no room to grow") — signature of D4 receiving S1
• A new hire or person in a new role is struggling despite effort — signature of D1/D2 receiving insufficient structure
• A task or technology change resets development levels for experienced people
• AI adoption resets who's the expert — after rolling out AI coding tools / AI-native workflows amid the 2024–2026 AI capex race, a senior person is D1/D2 on the new tool even while D4 on the core work
• You are making a delegation decision for a specific person on a specific task

When NOT to use: incentive misalignment (principal-agent problem); acute crisis requiring uniform command; task is too vague to name (diagnosis requires a specific task).

Coaching Novices (Adaptive Front Door)

• Engine mode: user has a specific person and task → run The Process directly.
• Coach mode: user is unfamiliar or asks "what is situational leadership?" → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.

1. One-line what-it-is: there's no single best management style — what works depends on how much the person knows and how confident/motivated they feel on this task. The manager's job is to match style to that, and update as the person grows.
2. Check fit: is there a specific person and specific task where management is stuck? If the issue is incentives not capability, point to principal-agent.
3. Elicit the real case — get the specific task and specific person. Never assess development level for "the employee in general."

[WAIT — do not advance until user responds]

1. Run The Process one step at a time: start with competence — "Describe 2–3 things this person has done on this task. What was the quality?"

[WAIT — do not advance until user responds]

1. Close by naming the insight: which development level, which style, and one specific behavior the manager should change immediately.

[WAIT — do not advance until user responds]

The Process

Run the Development Diagnosis, then select and implement the Leadership Style.

1. Define the task precisely. State: "[Person] on [specific task]." If the task cannot be named, the diagnosis cannot run.
2. Assess competence on this specific task — Knowledge / Skill / Track record. Rate: Low / Medium / High.
3. Assess commitment on this specific task — Motivation / Confidence / Engagement. Rate: High / Variable / Low. Do not infer from behavior alone — ask directly.
4. Determine development level: D1 = Low competence + High commitment; D2 = Low-medium competence + Low commitment; D3 = Medium-high competence + Variable commitment; D4 = High competence + High commitment. Stop-rule: ambiguous level → default to lower (more structure).
5. Select and implement style: S1 Directing (D1) — clear steps, specific check-ins, no open-ended "how do you think?"; S2 Coaching (D2) — high directive + high supportive, acknowledge effort + give guidance; S3 Supporting (D3) — ask questions, explore confidence barriers, avoid deciding for them; S4 Delegating (D4) — assign outcomes not methods, check in periodically, express trust through reduced supervision.
6. Monitor, reassess, shift. Reassess when new responsibilities arrive, performance drops, or disengagement signals appear. Name style shifts explicitly: "I'm adding more structure on this new task — that's about the task, not my confidence in you."

Output: Development Diagnosis

# Development Diagnosis:  on 
Task: 
Competence: Knowledge / Skill / Track record → Overall: low/medium/high
Commitment: Motivation / Confidence / Engagement → Overall: high/variable/low
  (Assessment method: observation / conversation / inference)
Development level: D1/D2/D3/D4 — reasoning
Style recommendation: S1/S2/S3/S4
Immediate behavior changes: (1) (2) (3)
Reassessment trigger: 

→ Method in Action: Google's Project Oxygen (2009) → 2026 lens: Leading AI-native engineering teams (2024–2026)

Style Packs

Engineering teams: Most common error — treating technical seniority as a proxy for all tasks. A senior engineer may be D4 on Python and D1 on AI deployment. Maintain a task-level development map; separate legacy skills from AI-assisted tasks.

Startup scaling: Most dangerous failure — founder default to S4 as company grows, continuing S4 with incoming D1/D2 hires and producing confused new-hire failures. Reverse error: staying S1 with D4 executives who should be released.

Applying It Well

• Never assess development level globally — always for a specific named task. "She's a D4" is meaningless; "D4 on client management, D1 on data analysis" is actionable.
• Most dangerous mismatch: D4+S1. Symptoms: person stops raising ideas, stops initiating, starts mentioning other opportunities. When shifting S4→S1 on a new task, name the shift explicitly.
• Commitment is harder to assess than competence. Ask: "On a scale of 1–10, how confident do you feel?" The gap between inferred and stated confidence is the coaching starting point.
• Development arc (D1→D4) is not linear in time. Apply the style the current level calls for — don't rush the levels.

→ Primary sources: references/sources.md

Common Rationalizations

[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.

Red Flags

• Development level was assessed for a person overall, not for a specific task
• Commitment was inferred from behavior without direct conversation
• Manager has not changed style for a long-tenured member even as responsibilities evolved
• High performer is disengaging or citing "no growth opportunities" — likely D4+S1
• New hire is repeatedly failing — likely D1+S4
• Development level not updated after new tasks were assigned

Verification

• Task is precisely stated — not "her performance" but "her performance on [specific named task]"
• Competence assessed on all three dimensions: knowledge, skill, track record
• Commitment assessed through direct conversation, not only inferred
• Development level (D1–D4) stated with reasoning, not just the label
• Leadership style (S1–S4) matched to development level, with three specific behavior changes named
• Stop-rule applied: ambiguous level defaults to lower (more structure)
• Reassessment trigger defined

---

Part of deciqAI Knowledge Skills — 227 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/c/situational-leadership · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.

Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/situational-leadership.json