Framework · People leadership · 2 min read
Situational leadership
Adapt your style (direct, coach, support, delegate) to the person's competence and confidence on this specific task, instead of leading everyone the same way.
-
S1 Direct
- Their state
- New and enthusiastic
- You
- Clear instructions and examples
- Behaviour
- High directive, low supportive
-
S2 Coach
- Their state
- Some skill, low confidence
- You
- Explain why, encourage, review together
- Behaviour
- High directive, high supportive
-
S3 Support
- Their state
- Skilled, variable confidence
- You
- Ask, listen, back their decisions
- Behaviour
- Low directive, high supportive
-
S4 Delegate
- Their state
- Skilled and confident
- You
- Give the outcome, stay available
- Behaviour
- Low directive, low supportive
Match the style to the person on this specific task.
Use it when
- A junior designer feels lost with a task you gave them "full freedom" on.
- A senior designer feels micromanaged because you review every step.
- You hand a designer a new type of work and are unsure how closely to stay involved.
How to use it
- Name the task. Be specific: "run the stakeholder workshop for the export feature", not "stakeholder work". Output: one clearly named task.
- Assess their competence on this task. Ask what similar work they have done and how it went. Look at evidence, not job title. Output: new, some skill, or skilled.
- Assess their confidence on this task. Ask "How do you feel about taking this on?" Confidence can drop when the stakes rise, even for skilled people. Output: low, variable, or high confidence.
- Pick the matching style and say it. Direct, coach, support or delegate (see the diagram). Tell them why: "This is new for you, so I'll give you more structure on this one." Output: an agreed style for this task.
- Move up as they grow. Check after each piece of work and give less direction as competence rises. Write the matching Delegation levels in your 1:1 doc. Output: the style for the next similar task.
Worked example
A UX lead on an internal operations platform has four designers. The same lead uses four styles in the same week.
| Designer and task | Their state on this task | Style | What the lead does |
|---|---|---|---|
| Junior, first usability test | New and enthusiastic | Direct | Shares a test script and a past report as examples; reviews the plan before the session. |
| Mid, first stakeholder presentation | Some skill, low confidence | Coach | Explains why the deck should open with a decision; rehearses it together and encourages. |
| Senior, complex table redesign after a hard critique | Skilled, variable confidence | Support | Asks what they think the main risk is, listens and backs their call. |
| Senior, design system triage | Skilled and confident | Delegate | Gives the outcome ("keep the backlog under two weeks"), stays available. |
Watch out for
- One style per person. Labelling someone as "a delegate person" ignores that skill varies by task. Assess each task again.
- Directing a skilled person. Too much direction for a skilled, confident designer feels like micromanagement and lowers motivation.
- Delegating to someone who is new. "Full freedom" on a new task can feel like abandonment. Structure is a form of support.
- Not saying the style. If you change style without explaining why, people may read more direction as a loss of trust.
Template
Use this when you hand over a new piece of work.
Person: Task:
Competence on this task: new / some skill / skilled
Evidence:
Confidence on this task: low / variable / high
Style:
[ ] Direct clear instructions, examples
[ ] Coach explain why, encourage, review together
[ ] Support ask, listen, back their decisions
[ ] Delegate give the outcome, stay available
What I said about the style:
Review after: (date or milestone)
Saved only on this device.