Fewer than two in a hundred leaders can lead in more than three ways. Hay Group research conducted over seven years to 2012 surveyed more than 14,000 leaders and compared their ability to use different management approaches with the workplace climates they created. It found that 38% had mastered none or only one leadership style, while only about 2% could use four or more. Among leaders who created high-performance climates, 48% were comfortable with four or more styles, against 9% of those running demotivating environments, as HR Magazine reported.
That gap is what situational leadership was built to close. Paul Hersey and Ken Blanchard developed the framework while writing Management of Organizational Behavior, and its central claim is unfashionably practical: leadership behaviour should follow the follower's development level on a specific task, not the leader's personality. Two variables do the work. Directive behaviour covers what needs doing, how and by when. Supportive behaviour covers listening, encouraging and involving. Combined, they produce four styles: directing (S1), coaching (S2), supporting (S3) and delegating (S4).
Those styles map onto four development levels. D1 is high commitment with low competence. D2 is some competence with commitment that fluctuates as reality bites. D3 is high competence with variable commitment, usually because confidence hasn't caught up. D4 is high competence and high commitment.
The eight situational leadership examples below work through each level in turn, then through mixed, change and development-pathway applications. They run from a graduate's first month to a system outage that forces a delegating manager back into telling.
Table of Contents
- 1. Directing a New Graduate Trainee (Telling, S1)
- 2. Coaching a Developing Analyst (Selling, S2)
- 3. Supporting an Experienced but Hesitant Project Manager (Participating, S3)
- 4. Delegating to a Self-Directed Team Leader (S4)
- 5. Shifting Style During a Crisis Response (Mixed Application)
- 6. Managing Change for a Reluctant, Previously Competent Team (Selling to Participating)
- 7. Re-engaging a Demotivated Mid-Level Manager (Coaching to Supporting)
- 8. Developing Future Leaders Through Progressive Delegation (Development Pathway)
- Situational Leadership Examples at a Glance
- From Model to Method, Putting Situational Leadership into Practice
1. Directing a New Graduate Trainee (Telling, S1)

A graduate joins a marketing team in September with a good degree, plenty of enthusiasm and no idea how the organisation writes a client presentation. On that task she sits at D1: high commitment, low competence.
Directing fits. The manager specifies the task, the deadline, the standard and the reporting routine. Nothing about that is authoritarian. It's the fastest route to a usable draft and the surest way to protect her motivation while her competence catches up.
What the leader actually says
Dialogue is where the style lives or dies. "Can you put together the client deck for Thursday?" gives a task without a standard. "Use the standard template, one message per slide, six slides maximum, and send me the draft by four on Wednesday so we can review it together" gives direction and support in the same breath.
A worked example. During the trainee's first month, the manager issues a written checklist for preparing client presentations and reviews every draft before it leaves the building. A hospitality supervisor runs the same sequence with a new starter on the reservations system: demonstration first, supervised operation second, solo operation third.
Why this matters more than it looks
Most UK organisations run on everyday line management rather than boardroom strategy. In the 2013 British Social Attitudes survey, 35% of people in employment in Britain reported formal responsibility for supervising at least one person, with comparable figures of 42% in the 2012 Skills and Employment Survey and 39% in the 2012 European Social Survey; CIPD research puts the share of UK employees with management or supervisory duties at roughly 30% to 45%.
Practical rule: Direct the task, not the person. The moment the trainee can hit the standard unprompted, directing has done its job and should start to recede.
Three tactics make it work. Diagnose competence task by task rather than role by role. Explain the reasoning behind each instruction so commitment holds. Set a review date at which the directive approach gets reassessed rather than drifting on by habit.
2. Coaching a Developing Analyst (Selling, S2)
An analyst has finished training and can produce the monthly reporting pack. Then a dataset arrives with inconsistent fields, a stakeholder challenges the conclusion, and confidence drops. That's D2: some competence, commitment wobbling.
A coaching leadership style fits because the gap is judgement, not effort. The manager still directs, but explains why, invites challenge and shares the reasoning behind decisions.
Talking through the model, not around it
Say the analyst has built a regression model that executives will see on Friday. The manager doesn't overwrite it. They sit with the analyst, ask which variables were excluded and why, and test the answer before the findings go upward. In a finance team, a leader facing an error in a forecast talks through the budgeting assumptions one at a time instead of issuing a correction.
The sequence matters. Ask for the analyst's reasoning first, then offer a view. Answering first closes the thinking down; asking first keeps ownership with the person who has to defend the work later.
Why coaching earns its cost. Career development support is thin in many UK workplaces. In 2025, 47% of UK respondents said managers lacked proper support for career development, according to the LinkedIn Workplace Learning Report UK. A manager who explains reasoning and builds judgement is filling a gap employees already notice.
When commitment dips, name it. "You've gone quiet on this one. What's making it harder than the last pack?" gets further than reassurance offered cold.
- Ask before telling: have the analyst articulate their reasoning before you supply a solution.
- Acknowledge progress specifically: "the way you flagged the outlier in table three" lands; "good work" doesn't.
- Withdraw input on a schedule: agree which sections of the next pack need no review at all.
3. Supporting an Experienced but Hesitant Project Manager (Participating, S3)
An experienced project manager has run delivery for a decade. She's now asked to lead a cross-departmental initiative with stakeholders she doesn't know, and she hesitates. Competence is high. Commitment has dipped because the demands of the role are unfamiliar.
That's D3, and more instruction is the wrong response. Supporting means shared problem solving, active listening and decisions the employee owns.

Facilitation with experts who disagree
An NHS England improvement case shows the pattern with a group of consultants setting referral criteria for patients suspected of having cancer. Their clinical thresholds differed, and discussions ran for weeks because each participant leant on a different form of evidence: published research, anecdotal experience, hypothetical scenarios. The project manager didn't impose one method. They summarised the areas of agreement, brought in criteria used by other hospitals, and used those examples to widen the frame of reference until consensus became possible.
That's supporting behaviour in its purest form. The expertise sits with the group, the alignment doesn't, and the leader's job is to build the conditions for alignment rather than supply the answer.
A second worked example. A senior engineer co-designs a rollout plan with their manager, who facilitates the discussion and tests options but leaves the technical choices with the engineer. A nurse manager supporting an experienced ward sister through a new triage protocol holds weekly problem-solving sessions instead of issuing a procedure note.
- Locate the hesitation: is it the stakeholders, the scope, the visibility or the time?
- Ask open questions: "What would need to be true for you to feel confident chairing that meeting?"
- Clarify decision rights: state plainly which calls are hers, so autonomy doesn't become ambiguity.
4. Delegating to a Self-Directed Team Leader (S4)
A team leader with a strong operations record has proved she can plan, troubleshoot and hold a team together through a difficult quarter. D4: high competence, high commitment. The appropriate style is delegating, which means authority over decisions and resources, with the manager available rather than absent.
What delegation looks like in practice
A regional director lets an experienced store manager set quarterly staffing and promotional plans, reviewing only the agreed performance indicators. A research director hands a senior scientist full control of a grant application and intervenes only when resources need reallocating. In both cases the boundary is agreed in advance: outcomes, spend limits, reporting interval.
Delegation is already a mainstream UK management mechanism rather than an abstract ideal. The CIPD People Profession 2023 survey reported that roughly three-quarters of UK people professionals delegated absence management, recruitment and performance-management activities to line managers, with approving time off, interviewing candidates, conducting reviews and managing sickness absence the most frequently handed over. Just over half of respondents in Ireland reported delegating comparable responsibilities, and UK small and medium-sized enterprises were significantly less likely to delegate than larger organisations.
Delegation isn't abandonment. Agree the outcome, the boundaries and the reporting interval in writing, then hold to them even when you'd have done it differently.
Hybrid working raises the stakes. In 2025, 74% of UK organisations reported having hybrid working, according to the CIPD Good Work Index, with effective team leadership, connection to purpose and culture named as the key challenges. Delegation built on agreed outputs rather than visible activity is the only version that survives a distributed week.
- Agree outcomes and limits first: what can be decided, what must be escalated, when you next speak.
- Stay reachable without reclaiming: answer the question; don't take the decision back.
- Credit publicly: reinforcement costs nothing and protects commitment.
5. Shifting Style During a Crisis Response (Mixed Application)
At 09:40 on a Tuesday the payment system goes down. The team is D4 in normal conditions. For the next ninety minutes the same team needs explicit roles, a single decision-maker and no debate about architecture.
Mixed application is where situational leadership earns its name. The manager moves from delegating to telling, then back to participative once the system is stable. Nothing about the team's competence has changed. The task has.

Making the shift visible
The failure mode isn't the shift itself, it's a shift nobody announces. Staff trusted with autonomy on Monday and told what to do on Tuesday morning read the change as mistrust unless the leader names it.
Say it out loud: "For the next hour I'm making the calls on failover. At four we go back to normal decision-making and I want your read on what happened." An IT operations manager assigning explicit roles during a data centre failure, then reverting to consultative planning for the post-incident review, is doing exactly this. A hotel general manager who takes direct control of guest relocations during a fire alarm and later invites staff input on service recovery is running the same pattern.
Communication is the mechanism, and employees say they value it. In 2024, 45% of UK employees identified transparent and strong communication as the most valued leadership trait in an ideal CEO, according to a Great Place to Work UK survey.
The wider map of leadership styles in management gives useful context, but the operational discipline here is narrower. State the shift, set the point at which normal decision-making resumes, and debrief afterwards so participation is restored rather than assumed. Leaders who skip the debrief find the directive hour becomes the new normal. Managers who want to rehearse the briefing, escalation and debrief conversations can work through them in our Communication Skills for Leaders course.
6. Managing Change for a Reluctant, Previously Competent Team (Selling to Participating)
A procurement team has run the supplier process for years and runs it well. A new platform arrives. Competence is fine; commitment to the change is close to zero. The barrier is willingness, not ability, which makes this a selling problem before it becomes a training problem.
Two moves, in order
Move one is the case for change, made clearly. Move two is handing over the design decisions that don't threaten the outcome: which features get piloted, how the configuration is set, and which team tests first.
A procurement manager explains the business case for a new supplier platform, then asks buyers to pilot features and recommend configuration changes. A school head introduces a revised assessment system by presenting the evidence for it, then invites teachers to shape the rubrics.
Change leadership is measured separately from day-to-day management, and the gap tells you why both styles are needed. In the UK Civil Service People Survey 2015 benchmark data, the employee engagement index stood at 58% and the "My manager" theme at 68%, while "Leadership and managing change" scored 43%, according to the Cabinet Office benchmark figures. Good line management doesn't automatically produce confidence in change.
Distinguish goal from process. Resistance to the platform is often resistance to the timetable, the training or the loss of a familiar routine. Name the loss before you sell the gain.
Birmingham City Council's Foundry Programme, launched in 2023 amid significant organisational pressure, shows the alternative to consultant-led change: collaborative diagnosis, open dialogue and distributed decision-making, with staff leading targeted improvements. Its measured results included an AI-powered mailbox-indexing system saving more than 5,500 staff hours annually and automated document redaction cutting processing time from 10 minutes to 90 seconds, an 85% reduction, as the Local Government Association case study records. Pilot groups remain the cheapest way to build that evidence and the early advocates who carry it. Our Leadership Fundamentals course opens our leadership pathway and covers the diagnostic groundwork a change programme depends on.
7. Re-engaging a Demotivated Mid-Level Manager (Coaching to Supporting)
A regional manager was the strongest performer in the business two years ago. After a restructuring she's quieter in meetings, slower to volunteer and visibly frustrated with the new reporting lines. Competence hasn't fallen. Commitment has.
Diagnosis matters most here, because the instinct is to re-train. Training a motivational problem wastes everyone's time and insults the person. The leader starts with coaching: clarifying expectations, linking current tasks to career goals, agreeing what good looks like in the restructured role. Support then takes over, validating contribution and inviting her to shape the role itself.
The conversation
Hold it privately and without a clock. "Since the restructure your patch has changed and I don't think we've talked properly about what you want from it. What's frustrating you most?" Then listen past the first answer, which is rarely the complete picture.
A marketing director meets a regional manager to redefine responsibilities after a restructuring, agreeing development objectives and check-in dates. An operations director reviews workload and growth opportunities with a shift supervisor who has disengaged following a reorganisation.
Why it's worth the time. Manager quality is unevenly distributed and employees know it. In 2025, 27% of surveyed UK employees rated their manager as highly effective and 37% as somewhat effective, according to Chartered Management Institute research involving 4,500 workers and managers reported by People Matters Global. Re-engagement is cheaper than replacement, and the manager in front of you sets the tone for everyone below her.
- Diagnose motivation, not skill: ask what changed, not what's missing.
- Link goals to visible progression: vague promises about development read as delay.
- Follow up on agreed actions: one broken commitment undoes a good conversation.
Coaching shifts to supporting once the frustration is named and the plan is shared. Keep the check-ins; drop the instruction.
8. Developing Future Leaders Through Progressive Delegation (Development Pathway)
A high-potential employee is being prepared for a supervisory role. Over twelve months the manager moves her from directing a first leadership project, through coaching when it goes badly, into supporting her decisions, and finally to delegating a small team.
That sequence treats the model as a development pathway rather than a single-point decision, which is how leadership development works.
Diagnostics that make progression defensible
Progression should rest on evidence, not elapsed time. A four-stage cycle keeps it honest: assess competence and commitment, select the matching behaviour, monitor the team's response, then recalibrate using outcome data. Useful measures include collaboration across merged units, decision-cycle time, escalation frequency and completion of shared objectives.
The NHS Professionals case study on University Hospitals Sussex describes a programme that used psychometric testing with around 70 senior clinical and non-clinical leaders to surface individual work styles, behavioural tendencies under pressure and team-level gaps. It ran after the merger of two legacy organisations, which made relationship-building an integration requirement rather than a soft goal. The diagnostic data let leaders adjust communication, influence and decision-making to the stakeholders in front of them.
A second example. A retail chain gives a shift supervisor a series of increasingly complex responsibilities over twelve months, reviewing progress at fixed intervals. A consultancy pairs a rising team leader with a senior partner who withdraws from client-facing decisions as the protégé demonstrates readiness.
- Set milestones tied to observable behaviour: chairing a review, owning a budget line, resolving an escalation unaided.
- Review readiness on evidence: a fixed timeline assumes development is linear, and it rarely is.
- Pair the plan with formal learning: structured study gives the vocabulary that makes feedback precise, which is the subject of our guide to how to become a leader.
Situational Leadership Examples at a Glance
| Scenario | Development Level | Leadership Style | Primary Constraint | Key Takeaway |
|---|---|---|---|---|
| Directing a New Graduate Trainee | D1: High commitment, low competence | Telling (S1) | Limited workplace experience and procedural knowledge | Give clear instructions and close guidance while building foundational skills. |
| Coaching a Developing Analyst | D2: Some competence, low or fluctuating commitment | Selling / coaching (S2) | Uncertainty and reduced confidence in complex situations | Combine explanation and encouragement to develop judgement and confidence. |
| Supporting an Experienced but Hesitant Project Manager | D3: High competence, variable commitment | Participating / supporting (S3) | Hesitation about unfamiliar role demands | Use collaboration and reassurance while preserving employee ownership. |
| Delegating to a Self-Directed Team Leader | D4: High competence, high commitment | Delegating (S4) | Need to avoid unnecessary oversight while maintaining accountability | Delegate authority with clear outcomes and periodic review. |
| Shifting Style During a Crisis Response | Varies by task and context | Flexible: telling during crisis, then participative | Urgent need for rapid action | Adapt leadership to immediate needs and explain when authority shifts. |
| Managing Change for a Reluctant, Previously Competent Team | Strong competence, low commitment to change | Selling, then participating | Resistance to a new workflow | Address concerns first, then involve the team in implementation. |
| Re-engaging a Demotivated Mid-Level Manager | High competence, declining commitment | Coaching, then supporting | Disengagement following restructuring | Diagnose motivational causes and pair clear expectations with support. |
| Developing Future Leaders Through Progressive Delegation | Progresses from low readiness toward high competence and commitment | Telling, coaching, supporting, then delegating | Developing leadership capability over time | Transfer responsibility gradually as readiness grows. |
From Model to Method, Putting Situational Leadership into Practice
Read together, the eight scenarios share one discipline. Each begins with a task, not a person. The graduate is capable in general and incompetent at client decks in particular. The project manager is expert at delivery and uncertain at cross-departmental influence. Diagnosing at the level of the task is what makes the style choice defensible, and it is what stops development levels hardening into labels people can't escape.
Three habits carry across all of them. Signal the shift. A leader who moves from delegating to telling without saying so creates the appearance of mistrust. Separate competence from commitment. Training solves the first, conversation and time solve the second, and mixing them up wastes both. Build in a reassessment point. Every style decision in these examples has a review date attached, because readiness changes and a manager who doesn't check is guessing.
Situational leadership fails less often because the framework is wrong than because diagnosis is rushed. The model asks for a judgement about a person and a task, then asks the manager to act on it and check the result.
Time and training are the binding constraints on that judgement. In the 2025 CIPD/YouGov UK Working Lives survey, only 60% of managers said they had the training and information needed to manage people well, and only 59% said they had enough time to do so, as the CIPD Good Work Index 2025 reports. A model that asks for task-level diagnosis has to be built into the working week: two diagnostic questions at the start of a task, a named review point, a note of what was agreed.
Formal credentials remain uneven too. In 2025, 52% of UK managers did not hold a formal management or leadership qualification, according to Chartered Management Institute figures. That isn't a reason to reach for a certificate before a conversation, but it explains why so many managers arrive at situational leadership through trial and error, reinventing a framework that has existed for decades.
Structured, CPD-accredited study closes part of that gap. London School of Business Administration's Leadership and Management Programme is an eight-course, CPD-accredited pathway delivered entirely online and self-paced over 160 hours, combining recorded lectures, structured learning materials and interactive assessments. Its design integrates real-world organisational scenarios, so frameworks such as situational leadership get tested against cases rather than memorised as a taxonomy.
The most replicable tactic across all eight examples costs nothing. Treat every delegation as a development decision with a review attached, and treat every directive intervention as temporary by design. Leaders who do both spend less time controlling and more time building the capability that makes control unnecessary.
If you want to move from reading about leadership styles to applying them under pressure, London School of Business Administration delivers online, self-paced courses across leadership, management and business, with interactive assessments and a verifiable certificate on completion. The Leadership and Management Programme builds the diagnostic and communication habits these eight scenarios depend on, from directing a first-week trainee to delegating a small team. Visit the site to compare the leadership pathway with our other programmes and choose the one that matches the role you're moving into.

