Situational Leadership Style: Four Styles in Practice

A situational leadership style adjusts the direction and support a leader provides for a particular task. An experienced analyst may need little supervision when producing a familiar report and explicit instruction when chairing an unfamiliar meeting. The useful starting point is the work and the person's experience, rather than one permanent label for the employee.

This guide uses Blanchard's SLII terminology and distinguishes it from the separate Hersey-associated Performance Readiness model. It explains the concepts, their evidence limits and an original case in which instruction, listening, authority and autonomy solve different problems.

Coachful is our #1 recommendation for supporting the coaching work around these decisions: record the leader's assumptions, chosen support agreement, practice and actual review through worksheets, sessions and client conversations. This is our editorial workflow recommendation. Coachful does not automatically assess development levels, certify a leadership style or guarantee employee performance.

Keep the model and its versions clear

Paul Hersey and Kenneth Blanchard's early work appeared as Life Cycle Theory of Leadership in 1969, as recorded in the ERIC bibliographic record. Later models developed separately. Historical relatedness does not make their current terms interchangeable.

SLII uses task-specific competence and commitment, with development labels D1–D4 and styles Directing, Coaching, Supporting and Delegating. The Center for Leadership Studies' current Hersey-associated approach uses Performance Readiness and ability and willingness. Its R1 and R2 descriptions differ from SLII's D1 and D2 combinations. Do not copy a description from one model into a level from the other.

The discussion here is an explanatory overview, not a reproduction of proprietary training, an assessment or a scoring instrument. An organization using a licensed program should follow its current authorized materials. The original examples and planning process below are practical illustrations, not an official SLII exercise.

Distinguish direction from support

In Blanchard's account, directive behavior concerns specifying and showing task requirements, methods and checks. Supportive behavior concerns listening, encouraging participation and facilitating the person's thinking. They are two dimensions of behavior, not opposite ends of a kindness scale.

A leader can provide detailed instruction and still invite correction about an unsafe or impractical step. A leader can give substantial autonomy and still respond when the employee encounters a problem. “Less support” in the model does not authorize disrespect, withdrawal of accommodations or refusing necessary information.

For example, a clear requirement might be: “Use the approved owner register and mark an unresolved contact as unverified.” A supportive question might be: “Which part of the comparison do you want to work through together?” The first supplies a task boundary; the second creates room for judgment. Neither sentence tells you everything about the relationship.

Also separate behavior from authority. Listening closely does not transfer a budget. Asking someone to decide does not give them permission to allocate another department's hours. A support conversation must still identify who can authorize the actual choice.

Understand the four SLII styles

The model combines relatively higher or lower direction and support into four styles. The descriptions below summarize those combinations; the applications are original examples of how the distinctions can matter.

Directing is useful to discuss when the person genuinely lacks a necessary step or standard. However, repeating instructions they already understand can consume time without addressing the obstacle. Check what the person can actually demonstrate.

Coaching, as a management-style label, still involves the manager's task authority. It is different from an independent professional coaching relationship. A manager may explain a required standard and explore the person's concerns, but should not imply that a performance conversation has the same purpose or confidentiality as separate coaching.

Supporting places greater emphasis on the person's reasoning. That does not mean offering vague reassurance. A colleague may want a focused discussion of two options or feedback on one difficult judgment while retaining ownership of the solution.

Delegating requires an understandable boundary and a workable route for exceptions. “You own the draft within these criteria; bring any unverified source back before issue” gives more usable autonomy than “Just handle it.” The leader remains responsible for decisions they have retained and the conditions they control.

Interpret competence and commitment cautiously

Ken Blanchard's published explanation defines competence through knowledge and skills relevant to a goal or task, and commitment through motivation and confidence. His account emphasizes that development can differ between tasks. A job title or years of service cannot establish what someone needs for every activity.

In SLII's terminology, D1 describes low competence with high commitment; D2 describes low to some competence with low commitment; D3 combines moderate to high competence with variable commitment; D4 combines high competence and high commitment. The model pairs these with S1, S2, S3 and S4 respectively. These are the model's prescriptions, not a proven universal matching formula.

Use evidence and the person's account before adopting any interpretation. Demonstrated skill might include a completed comparable task, an explanation of the reasoning or an observed attempt. Ask what is unfamiliar and what support they want. Do not infer motivation from eye contact, a quiet manner, disability, disagreement or a request to check authority.

A person may know the procedure and want to perform it while lacking access, time or approval. Those conditions require action on the environment. Encouragement cannot grant an unavailable permission; more instructions cannot make another team's calendar yours to allocate.

Avoid treating the four descriptions as a compulsory ladder. This guide's case does not assign a permanent level or claim that an employee progresses through all four in a fortnight. Support is revised when the actual work changes, with room for the employee to disagree.

Put the evidence in proportion

Thompson and Vecchio's 2009 test of three versions analyzed survey data from 357 employees and eighty supervisors in ten Norwegian financial institutions. The published abstract reports that the revised 2007 theory predicted performance and attitudes less well than the original version. Their alternative autonomy-and-experience formulation did not add substantially to explained outcome variation. The official indexed discussion reports no clear overall support for the versions tested.

This was not a randomized trial of a coaching program, and it does not show that all instruction, support or delegation is ineffective. It does caution against presenting the exact style-to-level match as an established law. This guide uses the model to organize a support discussion and then tests the arrangement against actual work.

Keep the evidence question specific. Did the agreed demonstration address a real gap? Did a checkpoint catch an error? Did the person receive the promised authority? A favorable workplace example cannot validate the entire theory, and popularity or a provider's promotional claim does not settle the research.

Use six steps to agree the actual support

1. Define the activity. Specify the output, quality criteria, deadline and consequences. Separate facilitating a recommendation from approving it.
2. Check relevant evidence. Ask what the person has done before and observe the unfamiliar component where appropriate. Do not restart familiar work unnecessarily.
3. Hear the person's view. Ask about confidence, interest, uncertainty and the support they want. Record corrections to your own assumptions.
4. Check the conditions. Confirm access, priority, capacity and authority. Resolve a missing condition without labeling it a character or commitment problem.
5. Agree a bounded arrangement. Name instruction, discretion, check-ins, escalation and available time. Confirm the receiving person's actual acceptance of any additional work.
6. Review both the output and the support. Examine what happened, what the person found useful or intrusive and what remains unknown. Change only what the evidence justifies.

This is an original planning process. It does not generate a formal development score. The related guide to coaching as a leadership style develops the distinction between listening and avoiding a necessary management decision.

Worked example: familiar analysis, unfamiliar facilitation

All people, records and events in this case are fictional. Noa is a capable data analyst who independently produces a weekly metrics note. Elias, her manager, asks her to chair a thirty-five-minute planning meeting on 20 June 2029. It must allocate six hours of work to check six internal request-routing categories against the organization's approved owner register. The check uses synthetic examples and existing ownership records; it does not assign new duties to the departments listed.

Noa has done this kind of record comparison, but has not chaired the cross-team allocation discussion. Elias initially says, “You know the data, so just decide who does what.” Noa asks whether she can allocate Lin's time from another team. She cannot. That hesitation identifies an authority gap, not evidence of unwillingness to lead.

On 12 June Elias uses a forty-five-minute business-coaching session to examine his assumption that Noa's question showed unwillingness. He decides to check the actual permission boundary. They correct the assignment on 14 June. Elias retains approval of the work allocation within his remit. Lin controls whether her own protected time can be contributed. Noa will facilitate the options, check the evidence and record the authorized decision. Her familiar weekly note remains under its existing autonomous arrangement, without a new pre-approval requirement.

Protected paid capacity for this whole case is 480 minutes for Noa, 240 for Elias and 255 for Lin. Those limits include their preparation, exchanges, meeting, work and later review. Elias also has business coaching within his own allocation. The capacity is specific to each person, not a single pool anyone can consume.

Noa asks for a demonstration of how to distinguish a proposed allocation from an accepted one. During a thirty-minute demonstration and discussion on 15 June, Elias uses a synthetic record to show that distinction and the closing decision check. This adds direction to the unfamiliar component without taking over Noa's data-analysis method.

Give feedback on the demonstrated gap

In their forty-minute rehearsal on 16 June, Noa initially writes that Lin will perform all six mapping hours. Lin has not agreed. Elias also starts rewriting Noa's opening word for word. Noa says she needs help with the allocation check, not a new personality for presenting it.

Elias accepts the correction: “I over-directed the opening. Keep your own wording. The necessary check is whether each named person has accepted the amount and timing of the work.” He explains the constraint, asks Noa what evidence she needs and lets her rebuild that part.

The forty minutes include twenty for the first attempt, five for feedback and fifteen for the revised attempt. Noa's revised wording is: “This is a proposed allocation until Lin confirms her capacity and Elias approves the choice. If either condition is absent, the record will say pending.” Elias confirms that this now separates the states correctly.

The exchange combines explanation with discussion; it is not merely encouragement. It also produces evidence that Elias was intervening in an area where Noa did not need him. An SLII label would not excuse that intrusion.

Noa sends a bounded request to Lin. On 19 June Lin actually replies: “I cannot accept six mapping hours. Within my 255-minute allocation I can provide three hours on 21 June, 10:00–13:00 UTC, plus the agreed briefing, meeting and close-out. I cannot take the remaining three hours.” Noa acknowledges the limit and updates the proposal. An available funding or time allowance alone would not have established this personal acceptance.

Compare viable options and complete the decision

Noa prepares two options. Doing all six mapping hours herself would require 360 work minutes plus her 190 minutes of preparation, facilitation, integration and review: 550 minutes against a 480-minute limit. It exceeds her protected capacity by seventy minutes and is rejected. Noa's expertise does not create the missing time.

The second option allocates three mapping hours to each analyst. Noa confirms her own 21 June slot, 13:00–16:00 UTC. Lin's preceding three-hour slot is already accepted. Each retains their own method for checking the existing records; neither can invent an owner where the source is unresolved.

At the 20 June meeting, the actual thirty-five minutes are five for the purpose and authority, ten for the options, ten for the capacity checks, five for Elias's decision and five for responsibilities and the stop rule. Elias, Noa and Lin all attend.

Noa: The all-Noa option exceeds my allocation by seventy minutes. The shared option fits the named allocations, with Lin's three hours expressly accepted. Are those still the hours each of us can use?

Lin: Yes, three mapping hours from 10:00 to 13:00 on 21 June, with no extra mapping hours assumed.

Elias: I approve that shared allocation. Noa owns the combined record. If a route cannot be verified, record it as held rather than guessing. Send the honest result by 17:00 UTC on 21 June, even if a verification remains open.

Noa: Agreed. I will combine the records from 16:00 to 16:20 and send the status at 16:20. Approval of a staffing allocation does not validate any unverified route.

The completed decision record names Lin's three hours, Noa's three hours, Elias's approval, the retained source requirement, the explicit hold rule and the reporting deadline. Lin confirms her portion; Noa confirms ownership of the combined status. The original aim remains six verified categories, with honest reporting required if it is not achieved.

Follow the actual delivery and the remaining gap

Both analysts use their accepted three-hour windows on 21 June. Those periods include reading, comparing records, writing and testing synthetic examples, not three hours of pure typing. Noa integrates and sends the combined result at 16:20, before the 17:00 reporting deadline.

The table documents that fictional organization's existing routing information. It is not a general legal or administrative routing rule for readers. Lin checks the first three categories; Noa checks the latter three. Five are verified and one is held. Six records were delivered, but the six-verified-category aim was not met.

On 22 June Noa and Elias spend fifteen minutes reviewing the result. Elias accepts the accurate status and retains responsibility for resolving the conflicting owner records. He does not order Noa to relabel the sixth row complete. A response from the relevant authority and a verified replacement contact are still outstanding at this checkpoint.

Noa says the demonstrated allocation check was useful, but the rewritten opening felt like unnecessary control. Elias acknowledges this and agrees that Noa will own the next agenda draft and facilitation wording, subject to the same decision boundaries. Capacity approval stays with the actual owners. The next meeting has not happened, and they do not award Noa a permanent D4 rating.

On 24 June Elias and his business coach each use fifteen minutes for the later review: ten minutes in live discussion of his over-direction, then five minutes each for the private client-conversation follow-up described below. In those final five minutes the coach writes and sends the comment; Elias reads it and replies. The message handling is included in each person's fifteen-minute review allocation. The lesson is not that every employee needs less management. Noa needed a new procedural distinction, room to use existing skill and a real authority agreement. The unresolved source record required organizational correction, not a different motivational style.

Count support as real work

The following actual account includes the people receiving help, providing it and performing the shared task. It makes the rejected all-Noa option and the final capacity check inspectable.

Recorded work totals 920 person-minutes, or fifteen hours twenty minutes. Noa has 110 protected minutes unused, Elias twenty and Lin fifteen; the coach uses the agreed ninety. These reserves belong to the named people. They do not establish capacity in the department responsible for the unresolved record. Earlier routine reporting and future record repair are outside this account.

Use Coachful to review the leader's choices

A worksheet can hold the coaching client's task description, evidence, assumption, agreed support, authority and actual result. Elias's business coach receives a suitable de-identified account of his own leadership decisions, not a secret employee development rating or all of Lin's workplace messages.

Opened submissions support Coach review. That section is private to the authorized coach team and is not included in the client's response PDF. The coach sends Elias a separate message in his private client conversation, with the authorized coaching-team audience: “You corrected the allocation boundary, but you also rewrote a competent colleague's opening. What will you leave to her next time?” Elias replies that the agenda wording stays with Noa while capacity approval remains explicit. An internal Reviewed status alone would not deliver that comment.

Before summarized coaching sessions, check Session recaps and any session-type overrides. Recaps send automatically by default. Approve before sending holds material for review; then send the agreed version or keep it private. It cannot recall something already sent. Coachful's records support the review, but do not authorize workplace decisions or verify an SLII category.

For another management risk, see pacesetting leadership and the difference between maintaining a standard and repeatedly taking over. Explore Coachful's features for the preparation and client-feedback workflow.

Troubleshoot the support agreement

The person disputes your assessment. Examine the actual task evidence and their account. A model label is not a reason to dismiss relevant experience or impose a personality judgment.

More encouragement changes nothing. Check access, authority, time and competing priorities. If the problem is an unavailable source or owner, resolve that condition through its proper route.

Check-ins duplicate work. Identify what each check is meant to catch. Remove or change an unnecessary checkpoint while retaining those required by risk, policy or a demonstrated gap.

Delegation becomes abandonment. Restate the output, discretion, exception route and your retained decisions. Availability for a genuine obstacle does not require taking back the whole task.

Frequently asked questions

Are SLII and Hersey's current model identical?

No. They share historical roots but use distinct development/readiness terminology and combinations. This guide uses SLII labels; do not substitute an R-level description into its D-level categories.

Does the framework prove which style will work?

No. Its matching prescriptions face empirical limitations. Use them as a discussion lens, state the arrangement you are trying and review the actual effect.

Can an expert need detailed direction?

Yes, for an unfamiliar component. That does not cancel expertise in other activities. Discuss the specific gap instead of increasing supervision across the person's whole role.

Is a request for approval evidence of low commitment?

No. The person may correctly recognize a limit on their authority. Establish the decision rights before interpreting hesitation as a motivational issue.

Does delegation remove the leader's responsibility?

No. Retained approvals, necessary resources and organizational duties remain. Agree which choices the person actually owns and how unresolved conditions will be handled.